Re: DebConf 21 Incident Response
Hi Molly, Am 09.05.21 um 15:27 schrieb M dB: Joining a meeting sounds like a good idea. When do you have meetings? currently every second Monday at 18:00 UTC. The next meeting is scheduled for 10 May 2021 (aka tomorrow), 18:00 UTC. Best regards, Daniel
Re: DebConf 21 Incident Response
Hi! We need to add Andy Carter to the list of people to reach out to, and remove peb. We'll make an MR. Joining a meeting sounds like a good idea. When do you have meetings? Cheers, On 5/9/21 7:45 AM, Stefano Rivera wrote: > Hi M (2021.05.09_03:09:20_+) >> Hello from the Community Team! With DebConf a few months away, we wanted >> to talk with you about incident response procedures, code of conduct >> enforcement, and how we can help DebConf be great. > Thanks for reaching out. > > So, I copied over the CoC and incident response page from DC20: > https://debconf21.debconf.org/about/coc/ > https://salsa.debian.org/debconf-team/public/websites/dc21/-/blob/master/pages/about/coc.md > > They seemed sensible and probably applicable again. Anything we want to > revise for DC21? Feel free to file MRs against it. > > Issues I can think of from DC20: > 1. Etherpad abuse that got reverted, and the author's account blocked in >Salsa. >We now have a mechanism to block accounts on the etherpad server >itself, that we can use to clamp down on these faster. Anyone in the >core video team should be able to take that action: > > https://salsa.debian.org/debconf-video-team/ansible/-/blob/master/roles/etherpad/templates/settings.json.j2#L375 > 2. Spam / offensive content on IRC. Was dealt with by speaking to the >offenders. Can't recall if we had to resort to kicks and bans. > > Nothing novel there that is of particular concern. > > Do you want to join our next team IRC meeting? Should we add an agenda > item for CoC enforcement? > > Thanks, >
Re: DebConf 21 Incident Response
--- crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68 On Sun, May 9, 2021 at 12:45 PM Stefano Rivera wrote: > > Hi M (2021.05.09_03:09:20_+) > > Hello from the Community Team! With DebConf a few months away, we wanted > > to talk with you about incident response procedures, code of conduct > > enforcement, and how we can help DebConf be great. > > Thanks for reaching out. > > So, I copied over the CoC and incident response page from DC20: > https://debconf21.debconf.org/about/coc/ > https://salsa.debian.org/debconf-team/public/websites/dc21/-/blob/master/pages/about/coc.md > > They seemed sensible and probably applicable again. https://www.debconf.org/codeofconduct.shtml ah. i remember reviewing this, and being stunned by the simplicity and clarity of the diversity statement, noting in particular the repetition of making people feel welcome. only much further down do we encounter the toxic list of behaviours which, when presented as the very first statement, typically poison an environment and cause everyone to live in fear, confusion and "treading on eggshells". my feeling is that this is the right approach and balance. l.
Re: DebConf 21 Incident Response
Hi M (2021.05.09_03:09:20_+) > Hello from the Community Team! With DebConf a few months away, we wanted > to talk with you about incident response procedures, code of conduct > enforcement, and how we can help DebConf be great. Thanks for reaching out. So, I copied over the CoC and incident response page from DC20: https://debconf21.debconf.org/about/coc/ https://salsa.debian.org/debconf-team/public/websites/dc21/-/blob/master/pages/about/coc.md They seemed sensible and probably applicable again. Anything we want to revise for DC21? Feel free to file MRs against it. Issues I can think of from DC20: 1. Etherpad abuse that got reverted, and the author's account blocked in Salsa. We now have a mechanism to block accounts on the etherpad server itself, that we can use to clamp down on these faster. Anyone in the core video team should be able to take that action: https://salsa.debian.org/debconf-video-team/ansible/-/blob/master/roles/etherpad/templates/settings.json.j2#L375 2. Spam / offensive content on IRC. Was dealt with by speaking to the offenders. Can't recall if we had to resort to kicks and bans. Nothing novel there that is of particular concern. Do you want to join our next team IRC meeting? Should we add an agenda item for CoC enforcement? Thanks, -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Re: DebConf 21 Incident Response
On 09/05/2021 04:09, M dB wrote: Dear DebConf Team, Hello from the Community Team! With DebConf a few months away, we wanted to talk with you about incident response procedures, code of conduct enforcement, and how we can help DebConf be great. Cheers, Molly Sounds a good idea, at Libreplanet we did have their Safe Space Policy as well as the GNU Kind communication guidelines. For room monitoring I did 2 x 2hour shifts over the weekend, so Saturday on mumble and Sunday on IRC, so mostly keeping an eye on the conversation, ensuring it stays reasonably on topic. These shift patterns worked really well for me at least, of course out side of that I would de-op and hang out in the rooms. but at the same time still be in the rooms, quite a few things that I responded to were technical questions or directing people to the right channel. Should we schedule one of the planning meetings for this? or at least to perhaps arrange a specific meeting to go through in more details. Next IRC meeting is Monday at 18:00 utc (19:00 UK Time) For the most part the codes of conduct are already written, it is just a case of making people aware and how we report concerns. Paul -- Paul Sutton, Cert Cont Sci (Open) https://personaljournal.ca/paulsutton/ OpenPGP : 4350 91C4 C8FB 681B 23A6 7944 8EA9 1B51 E27E 3D99 Pronoun : him/his/he
