I think the best would be where there is a committee to discuss and decide (usually), but the people who are in the committee are known and you can choose whom to reach out to individually if you do not want to reach out to the whole committee.
Google form is very impersonal and when you submit a report, via google form, you never know who is going to receive it. By telling people explicitly that there are few people willing to listen (and you tell who) you allow the person reporting it to pick that person who they trust most (or send it to the whole committee). At the same time, you do not put all the burden of handling the report on the shoulders of a single person, but a group of people who can make better decisions together. This also handles better a few cases: * the case where the problem is (potentially) with one of the committee members - you can pick another and tell them your issue without having the other committee member listening * the case where there is only one person gating all such code of conduct reports and - for example - being afraid of confrontation or when there were personal/professional relations that prevented such report from escalation J. On Fri, Jan 26, 2024 at 7:48 PM Briana Okyere <briana.oky...@astronomer.io.invalid> wrote: > Google form is a great idea. > > On Fri, Jan 26, 2024 at 10:45 AM Aritra Basu <aritrabasu1...@gmail.com> > wrote: > > > I added a comment, but would a Google form work. Responses can be shared > > with the committee. > > > > -- > > Regards, > > Aritra Basu > > > > On Sat, Jan 27, 2024, 12:06 AM Constance Martineau > > <consta...@astronomer.io.invalid> wrote: > > > > > Indeed, not having groups is a limitation of free slack. Maybe the > > > compromise is bookmarking the individuals who belong to that committee > > > somewhere? > > > > > > On Fri, Jan 26, 2024 at 1:26 PM Briana Okyere > > > <briana.oky...@astronomer.io.invalid> wrote: > > > > > > > I'm with you on having a committee take it over- although I'm not > sure > > > how > > > > we can ensure folks can anonymously submit a post as "breaking the > > > > guidelines" if they cannot DM an individual. > > > > > > > > On Fri, Jan 26, 2024 at 10:16 AM Constance Martineau > > > > <consta...@astronomer.io.invalid> wrote: > > > > > > > > > Wow Briana! This is fantastic, what a great idea! I added a few > > > comments. > > > > > > > > > > I also had a similar question as Jarek that I think merits a > > > discussion: > > > > > Should we have a committee or group to handle reported guideline > > > > > violations? If we single out one person to report violations to, > > we'll > > > > have > > > > > to continuously update the guidelines whenever someone else takes > up > > > the > > > > > job. > > > > > > > > > > On Thu, Jan 25, 2024 at 5:26 PM Briana Okyere > > > > > <briana.oky...@astronomer.io.invalid> wrote: > > > > > > > > > > > Hey All, > > > > > > > > > > > > While we currently have a Code of Conduct by the ASF. But, we do > > not > > > > have > > > > > > one that is tailored to Airflow Slack and our in-person Meetups. > > > > > > > > > > > > I propose we expand on our current Code of Conduct for these > > > additional > > > > > > places where community members communicate. > > > > > > > > > > > > For Slack, this would be a great way to acquaint folks with the > > space > > > > > when > > > > > > they join. As of now, there is no "onboarding" for when members > > join > > > > > Slack. > > > > > > This can leave people confused about how to engage. The same > > applies > > > to > > > > > > in-person Meetups. > > > > > > > > > > > > I invite everyone to take a look and let me know your thoughts: < > > > > > > > > > > > > > > > > > > > > > > > > > > > https://docs.google.com/document/d/1OfV2-UkoAVp_u8-DswZO9xNt3w14olgo4DujCiRi_Z4/edit?usp=sharing > > > > > > > > > > > > > > > > > > > -- > > > > > > Briana Okyere > > > > > > Community Manager > > > > > > *Astronomer Inc.* > > > > > > > > > > > > > > > > > > > > >
