• Delegation update for the Community Team

    From Jonathan Carter@21:1/5 to All on Fri Aug 7 17:40:02 2020
    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA512


    Dear Debian Developers

    I hereby appoint Molly de Blanc and Sruthi Chandran as
    members of the Debian Community Team. The delegation
    remains unchanged otherwise and is included below.

    The current members of the team are thus:

    * Steve McIntyre (93sam)
    * Jean-Philippe Mengual (jpmengual)
    * Luke Faraone (lfaraone)
    * Molly de Blanc (mollydb)
    * Pierre-Elliott Bécue (peb)
    * Andy Simpkins (rattusrattus)
    * Sruthi Chandran (srud)

    The goal of the Community Team (CT) is to help Debian be
    a welcoming place, focusing on response to difficult or
    contentious communications, as well as other negative
    experiences and Code of Conduct violations. It aims
    to encourage and foster a respectful, productive, and
    inclusive atmosphere throughout the Debian community.

    The responsibilities of the team are:

    * To respond to concerns directed to the Community Team,
    raised by members of the project or people interacting
    with them, working with individuals to help them.

    * To work with teams responsible for communications
    channels within the community such as listmasters, the
    owner of the Bug Tracking System, administrators of
    Debian Planet and others to provide advice; where
    desired by these teams, helping to deal with
    contentious and difficult issues that impact the
    community.

    * To work with the DPL, Debian Account Managers and
    others to provide advice on interpreting the Code of
    Conduct. Such advice may form the basis of interpretations
    of the Code of Conduct that help teams in the project
    set policy around community standards.

    * To coordinate responses (both inside and outside the
    project) to ongoing harassment of the Debian community as
    a whole or portions there-of; including working with
    additional volunteers when the community team's members
    are insufficient.

    * To work with event organisers to make sure that Debian
    Events have adequate incident response teams to respond to
    any concerns.

    * To write reports to other teams such as the Planet
    Admins, Listmasters, or Debian Account Managers in response
    to extreme incidents or repeated patterns of problematic
    behavior.

    The team recognises that technical development can lead
    to arguments and passionate discussions. Where desired,
    the team will work with contributors to help them express
    disagreement without violating the CoC. When people do
    breach the CoC, the team will give guidance on better ways
    to interact in the future. We will attempt to consult
    with those on all sides of issues when possible.
    Nevertheless, protection of the vulnerable and the community
    as a whole is the ultimate goal of the team.

    If things do not work out, and in cases with a pattern
    of repeating problems, the team will raise concerns with
    other teams as appropriate.

    Maintaining the respect of the community is critical.
    The most important facet of this is responding in a timely
    manner when reports are brought to the team's attention.
    Other important examples include sensitivity to conflict
    of interest and balancing trade-offs around confidentiality.

    The Community Team role has traditionally been emotionally
    challenging and resulting in high turnover. Because of this
    potentially high turnover, recruiting new members is even
    more important for the CT than for some other delegations.
    The DPL and CT will work together to have a robust, diverse
    group of volunteers available to join the CT and help out
    when more effort is required.

    This delegation grants no explicit power to the Community
    Team to enforce decisions; the power granted by this
    delegation is advisory. However, other teams may work with
    the Community Team as they choose and may allow the community team to
    have power within their channels. As an example,
    at the time of this delegation, some community team members
    are involved in list moderation. Within the rules
    established by listmaster for the use of this moderation
    power, it is appropriate for community team members to use
    such power in furtherance of the Community Team mission.

    - -Jonathan, Debian Project Leader

    - --
    ⢀⣴⠾⠻⢶⣦⠀ Jonathan Carter (highvoltage) <jcc>
    ⣾⠁⢠⠒⠀⣿⡁ https://wiki.debian.org/highvoltage
    ⢿⡄⠘⠷⠚⠋ https://debian.org | https://jonathancarter.org
    ⠈⠳⣄⠀⠀⠀⠀ Debian, the universal operating system.
    -----BEGIN PGP SIGNATURE-----

    iQIzBAEBCgAdFiEExyA8CpIGcL+U8AuxsB0acqyNyaEFAl8tdM4ACgkQsB0acqyN yaFzmw//bJlF4ECqAkiIN2yzIhAWP4lGrCuM40CP/cddcnZjdAeDVVlrInZpAM9s TQ4OUSd8VO3Yo3Yk1JrzOcqK3OsCuogX/3SIa+k1enHinfpyauFFutAdRsLk6n1e Gin4M6dIP6cNS4j87wUYUcNJmYdN9T+ym71JG9IrChbHKyOVozgpYFqaURBX3YQh esGeq6DJrZCRIRwM6dWkgSUNkHOfo77ZiXjngKxN3t+NHzNSHmvFRw5WK9R/Q1vy YIi2xfPUPwkOsvIKyU+jFsDC1IwkPWEeopKOYTeo19qI33FjTTS2znSq/9u6bEdI qn3s6GRLuxyqWfUdSG0dAzpcderPODZJcBK749Vr82NzaU46Hz6p4sROheoUzk7y CGh5gsFDEkSPvNd/mx/78vVUUv8wjuoB6X2xFiLXCdQ5nvylPnWD39eMNlNponSb j8jYMWtV8+l1J7607fMChAViqAvWESf7CXSk4q5uDedIpCMQhOfvxyX3dQ6hpTH6 UVGCrpXEvcp72+owTMXzKkS/+NQg8L3XHzs8nDGLO3SQOt5rCkTk2DMnIZ3pdRkF HZGeQf0Cfzl/uBPrGYB4bnllUSx6MmbwrWKyygQM/obnwKE6ssUanAPCSAnHHlF5 lFWfFoqkE7SX3ZXnOgAw3Yd8LFGQ+Xr0mUOL5VMOSeRAyIndqJE=
    =jz/E
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From jcc@debian.org@21:1/5 to All on Fri Jan 14 19:10:01 2022
    Dear Debian Developers

    I hereby appoint Andrew Cater as a member
    of the Debian Community Team.

    Andy Simpkins and Pierre-Elliott Bcue
    have stepped down from the team, we thank
    them for their contributions to this team.

    The delegation remains unchanged otherwise
    and is included below:

    The current members of the team are thus:

    * Steve McIntyre (93sam)
    * Jean-Philippe Mengual (jpmengual)
    * Luke Faraone (lfaraone)
    * Molly de Blanc (mollydb)
    * Sruthi Chandran (srud)
    * Andrew Cater (amacater)

    The goal of the Community Team (CT) is to help Debian be
    a welcoming place, focusing on response to difficult or
    contentious communications, as well as other negative
    experiences and Code of Conduct violations. It aims
    to encourage and foster a respectful, productive, and
    inclusive atmosphere throughout the Debian community.

    The responsibilities of the team are:

    * To respond to concerns directed to the Community Team,
    raised by members of the project or people interacting
    with them, working with individuals to help them.

    * To work with teams responsible for communications
    channels within the community such as listmasters, the
    owner of the Bug Tracking System, administrators of
    Debian Planet and others to provide advice; where
    desired by these teams, helping to deal with
    contentious and difficult issues that impact the
    community.

    * To work with the DPL, Debian Account Managers and
    others to provide advice on interpreting the Code of
    Conduct. Such advice may form the basis of interpretations
    of the Code of Conduct that help teams in the project
    set policy around community standards.

    * To coordinate responses (both inside and outside the
    project) to ongoing harassment of the Debian community as
    a whole or portions there-of; including working with
    additional volunteers when the community team's members
    are insufficient.

    * To work with event organisers to make sure that Debian
    Events have adequate incident response teams to respond to
    any concerns.

    * To write reports to other teams such as the Planet
    Admins, Listmasters, or Debian Account Managers in response
    to extreme incidents or repeated patterns of problematic
    behavior.

    The team recognises that technical development can lead
    to arguments and passionate discussions. Where desired,
    the team will work with contributors to help them express
    disagreement without violating the CoC. When people do
    breach the CoC, the team will give guidance on better ways
    to interact in the future. We will attempt to consult
    with those on all sides of issues when possible.
    Nevertheless, protection of the vulnerable and the community
    as a whole is the ultimate goal of the team.

    If things do not work out, and in cases with a pattern
    of repeating problems, the team will raise concerns with
    other teams as appropriate.

    Maintaining the respect of the community is critical.
    The most important facet of this is responding in a timely
    manner when reports are brought to the team's attention.
    Other important examples include sensitivity to conflict
    of interest and balancing trade-offs around confidentiality.

    The Community Team role has traditionally been emotionally
    challenging and resulting in high turnover. Because of this
    potentially high turnover, recruiting new members is even
    more important for the CT than for some other delegations.
    The DPL and CT will work together to have a robust, diverse
    group of volunteers available to join the CT and help out
    when more effort is required.

    This delegation grants no explicit power to the Community
    Team to enforce decisions; the power granted by this
    delegation is advisory. However, other teams may work with
    the Community Team as they choose and may allow the community team to
    have power within their channels. As an example,
    at the time of this delegation, some community team members
    are involved in list moderation. Within the rules
    established by listmaster for the use of this moderation
    power, it is appropriate for community team members to use
    such power in furtherance of the Community Team mission.

    - -Jonathan, Debian Project Leader

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEExyA8CpIGcL+U8AuxsB0acqyNyaEFAmHhuj8ACgkQsB0acqyN yaELqw/9GfMQxklOG6vU2r//GBdfLYs9yS+/0yNSiwqWCfDAsp6U7UWtF/BuOetN 2wJHiuLJzNJSuGCf5kyPUtYwWVJ6bjhWILnpB1eD7ELNrTjfIQE9OA+LVd2jvsDM ed97rUFMn1mXQRoJrcSfUogimO8mXuSg2ypAOwLXRJPZhBoKXPhVcreHKaNfxuZe F9HJM+4geUdfTRlfxFP4bZ57Mwcc4xCfKglqbjRV7NvJU2jeISirmWFIyhmYKabF 4AJ3NTwY+xvT2mngiKyql9WHki8NoHNW+R1Bk+KU4BgYlT3RrgJEXVqfdNC2WSy/ 0Mfy2jEnMnyLRfb4ECrT3YK+0sUNmR3RxiyMdd69tXbxj3X/+/pO+R1rfLaam7oX 1oBFMioOqn0XZFHDU9PkQRPpq/92DneFXhWDVZFc1Wwce3PKKYMuyMQUVeH5TC2U WS6odin23ikEADR4NBqYenTqlc+kQ0ii3QZ4S0Z7vaGIaVOSDkX6fV1/OqVflX21 hL+644WwAbgfhfOtqgYbWLanofk40HupP/38gY+UVxobydedkvO+EYnSInoSQUv7 5Y2uIIxiJYGqxl15VP/p6rVMeo6/jmAftrEMgBKNzUcmQZeFvGTo7Zbobx5n0jE0 d12dgQc14SomJQoRau/Hu0rFwYN0quzFMOV72m1FfC9oAvlOIEE=
    =myqR
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)