Please add notes and discussion here

Self-organizing team (not DPL delegated)
- new name: Community team (previously: Anti-Harassment)
- Composed by:
  - Molly
  - Tina
  - Steve (sledge)

What do we as Debian want from the Community Team?
- Ian: also support services/service maintainers
- discussion on pro-active vs. reactive
- community team being brought into an issue when someone sees a situation where maybe the CT can help
- doing mediation? might be difficult for volunteers. get training paid by debian?
  ian explains common meaning of 'mediation' and its challenges
- foz proposes and volunteers to help with giving talks, informations … about topics like diversity and priviledge

What can the community do to help the Community Team?
- making Debian a more welcoming place is a task for all, Community Team can help
- team needs more members
  joining starts with a trial period
  ideas for internal team structures, like "front desk of the week"
  trying to prevent team member burnout; being able to retire after not too long
  Suggestion: More talks about Diversity and privileges
  No DDs helping in the team
  No education work right now
  Question from Ian: Will there be any help from the Community Team in case someone needs to talk to a  maintainer about some questions or if they are not nice
  If the Debian Technical Commitee does not answer can you go to the Debian Community Team ?
Warnings on ML? Warnings
  team should be more divirse
  (core) team members must be DDs (privacy in incidents)
  CT doesn't want to take on serious educational tasks
  
What kind of powers should the CT have?
CT prefers to have (emergency) contacts in other teams
DLange proposes a public "ladder of escalation" (fairness, transparency)
Talk to the FTP-masters, ML people, Planet people, ircops etc if someone misbehaves 

Work on a Scope document has been started will be sent out to the ML when its done 
send an email to antiharassment@debian.org with ideas