I agree with the bot idea- does anyone on this thread have the ability to implement it?
On Mon, Feb 5, 2024 at 8:58 AM Bishundeo, Rajeshwar <rbish...@amazon.com.invalid> wrote: > The bot idea is great and being able to be anonymous is important! I'm not > a fan of filling out forms and that could be a deterrent for people trying > expressing their concerns, especially if they misinterpret the form > structure/criteria. So def in favor of a #2 type approach with a bot. > > -- Rajesh > > > > > > > On 2024-02-05, 10:13 AM, "Jarek Potiuk" <ja...@potiuk.com <mailto: > ja...@potiuk.com>> wrote: > > > CAUTION: This email originated from outside of the organization. Do not > click links or open attachments unless you can confirm the sender and know > the content is safe. > > > > > > > AVERTISSEMENT: Ce courrier électronique provient d’un expéditeur externe. > Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe si vous ne pouvez > pas confirmer l’identité de l’expéditeur et si vous n’êtes pas certain que > le contenu ne présente aucun risque. > > > > > > > I think the bot would be best. It would be great if the reports are made to > a private channel (the bot that Andrey posted seems to be doing just that) > where it can be discussed between the admin channels and action taken. Plus > some way of knowing who is in the admin channel and invitation to contact > them privately in case someone feels it's not good to post to the channel > (reasons explained before). > > > J. > > > > > On Sun, Feb 4, 2024 at 1:42 AM Wei Lee <weilee...@gmail.com <mailto: > weilee...@gmail.com>> wrote: > > > > I believe that anonymity is important in this case. It would be great if > > we could have the bot suggested by Aritra, and option #2 is favorable. > > Alternatively, I would prefer option #1. Thanks! > > > > Best regards, > > Wei Lee > > > > > On Feb 4, 2024, at 12:37 AM, Aritra Basu <aritrabasu1...@gmail.com > <mailto:aritrabasu1...@gmail.com>> > > wrote: > > > > > > I'm very much for anonymity here, so if we could have some kind of bot > > > that'd be great. Though even without that I think the combination of > > > channel and form also works out fine for talking to a person vs wanting > > > anonymity. > > > > > > -- > > > Regards, > > > Aritra Basu > > > > > > On Sat, Feb 3, 2024, 9:12 PM Andrey Anshin <andrey.ans...@taragol.is > <mailto:andrey.ans...@taragol.is>> > > wrote: > > > > > >> I’m also for some bot/application, after quick search I’ve found this > > one > > >> https://github.com/slackapi/slack-reporting-tool < > https://github.com/slackapi/slack-reporting-tool> > > >> > > >> > > >> I’m not sure is it suits our requirements and it required instance > where > > >> this code would be deployed but it worthwhile to check it, especially > if > > >> someone familiar with Typescript > > >> > > >>> On 3 Feb 2024, at 19:19, Amogh Desai <amoghdesai....@gmail.com > <mailto:amoghdesai....@gmail.com>> wrote: > > >>> > > >>> I would also like to go with #2. > > >>> > > >>> But just to bring up, how easy / hard is it to have a slack bot that > > >> users > > >>> can use to report > > >>> bad users or spam users. Never done it before myself, but it would > be a > > >>> great interface to report issues. > > >>> > > >>> The issues would then come to few admins who can take regulatory > > action. > > >>> (Might be an overkill, but thinking out loud here) > > >>> > > >>> Thanks & Regards, > > >>> Amogh Desai > > >>> > > >>>> On Sat, Feb 3, 2024 at 2:55 AM Briana Okyere > > >>>> <briana.oky...@astronomer.io.inva <mailto: > briana.oky...@astronomer.io.inva>lid> wrote: > > >>>> > > >>>> Hey All, > > >>>> > > >>>> I'm breaking this out into another conversation because I think it > > >> warrants > > >>>> its own decision before we move forward. > > >>>> > > >>>> Last week, I proposed we add a code of conduct for Airflow Slack and > > >>>> in-person meetups. > > >>>> Thread: < > > >> https://lists.apache.org/thread/jy16tb09qoc7lxb03pdj3dfnmrsmjq87> < > https://lists.apache.org/thread/jy16tb09qoc7lxb03pdj3dfnmrsmjq87>> > > >>>> > > >>>> In the Code of Conduct I shared, there is a conversation taking > place > > >> about > > >>>> HOW to report someone in Slack if their message does not abide by > the > > >> code > > >>>> of conduct. > > >>>> > > >>>> There is a general consensus that a committee should be formed that > > >> people > > >>>> can report code of conduct violations to. > > >>>> > > >>>> Two options were proposed about the reporting process: > > >>>> 1. Create a google form that people can fill out anonymously to > report > > >> code > > >>>> of conduct violations > > >>>> 2. Create a channel in slack called #slack-admins where people can > > post > > >> and > > >>>> report a violation. > > >>>> > > >>>> I would like to know which option you all vote for. I vote for > option > > >> #2. > > >>>> With the addition that we should have a #slack-admins channel that > > >> links to > > >>>> the google form for anonymous reporting, but also serves as a space > > >> where > > >>>> people can post questions about the code of conduct and receive > > clarity > > >> and > > >>>> answers. But I strongly feel there should be an option to > anonymously > > >>>> report, which I think a form would solve. > > >>>> > > >>>> Curious what others think, or if you have additional ideas! > > >>>> > > >>>> --- > > >>>> Briana Okyere > > >>>> Community Manager > > >>>> Astronomer > > >>>> > > >> > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org <mailto: > dev-unsubscr...@airflow.apache.org> > > For additional commands, e-mail: dev-h...@airflow.apache.org <mailto: > dev-h...@airflow.apache.org> > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org > For additional commands, e-mail: dev-h...@airflow.apache.org >
