You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airflow.apache.org by Briana Okyere <br...@astronomer.io.INVALID> on 2024/02/02 21:24:28 UTC
[VOTE] Add the ability to report slack messages that don't meet code of conduct
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>
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
Re: [VOTE] Add the ability to report slack messages that don't meet code of conduct
Posted by Briana Okyere <br...@astronomer.io.INVALID>.
Just following up on this. I spoke to Amogh and Jed about this, and it
looks like adding this bot requires us to deploy this into the airflow aws.
So, this will require more involvement from the PMC.
I think we should continue to work on the bot in the background. But
temporarily, I think we should tell community members to DM a PMC member if
a Code of Conduct violation occurs in Slack, or email
private@airflow.apache.org.
I'll post a separate Lazy Consensus about this.
On Wed, Feb 7, 2024 at 1:26 PM Briana Okyere <br...@astronomer.io>
wrote:
> Let me see if we can get you access
>
> On Tue, Feb 6, 2024 at 8:45 PM Amogh Desai <am...@gmail.com>
> wrote:
>
>> I was trying on a rough POC but it looks like I need to deploy my
>> application against a webserver on the internet.
>>
>> I also do not have the access to create a private channel on Airflow
>> Slack.
>>
>> Thanks & Regards,
>> Amogh Desai
>>
>>
>> On Wed, Feb 7, 2024 at 9:43 AM Amogh Desai <am...@gmail.com>
>> wrote:
>>
>> > Thank you, I will try to work on some POC soon
>> >
>> > On Tue, Feb 6, 2024 at 10:47 PM Briana Okyere
>> > <br...@astronomer.io.invalid> wrote:
>> >
>> >> Would love your help on this Amogh!
>> >>
>> >> On Mon, Feb 5, 2024 at 9:40 PM Amogh Desai <am...@gmail.com>
>> >> wrote:
>> >>
>> >> > Let us try to summarise and see what the bot has to do. Summarising:
>> >> > 1. The bot should allow users to report issues - anonymously too (or
>> >> maybe
>> >> > an option)
>> >> > 2. These issues should get redirected to an admin channel / private
>> >> channel
>> >> > 3. Some command in the bot that could allow users to find out the
>> >> people in
>> >> > that channel so that they can be contacted
>> >> > privately too
>> >> >
>> >> > Havent deployed a bot ever, but would be willing to try
>> >> >
>> >> > Thanks & Regards,
>> >> > Amogh Desai
>> >> >
>> >> > On Tue, Feb 6, 2024 at 12:58 AM Briana Okyere
>> >> > <br...@astronomer.io.invalid> wrote:
>> >> >
>> >> > > 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
>> >> > > <rb...@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" <jarek@potiuk.com
>> <mailto:
>> >> > > > jarek@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.rx@gmail.com
>> >> <mailto:
>> >> > > > weilee.rx@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 <
>> >> aritrabasu1999@gmail.com
>> >> > > > <ma...@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.anshin@taragol.is
>> >> > > > <ma...@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.oss@gmail.com
>> >> > > > <ma...@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.okyere@astronomer.io.inva <mailto:
>> >> > > > briana.okyere@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-unsubscribe@airflow.apache.org
>> >> <mailto:
>> >> > > > dev-unsubscribe@airflow.apache.org>
>> >> > > > > For additional commands, e-mail: dev-help@airflow.apache.org
>> >> > <mailto:
>> >> > > > dev-help@airflow.apache.org>
>> >> > > > >
>> >> > > > >
>> >> > > >
>> >> > > >
>> >> > > >
>> >> > > >
>> >> > > >
>> >> ---------------------------------------------------------------------
>> >> > > > To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org
>> >> > > > For additional commands, e-mail: dev-help@airflow.apache.org
>> >> > > >
>> >> > >
>> >> >
>> >>
>> >
>>
>
Re: [VOTE] Add the ability to report slack messages that don't meet code of conduct
Posted by Briana Okyere <br...@astronomer.io.INVALID>.
Let me see if we can get you access
On Tue, Feb 6, 2024 at 8:45 PM Amogh Desai <am...@gmail.com> wrote:
> I was trying on a rough POC but it looks like I need to deploy my
> application against a webserver on the internet.
>
> I also do not have the access to create a private channel on Airflow Slack.
>
> Thanks & Regards,
> Amogh Desai
>
>
> On Wed, Feb 7, 2024 at 9:43 AM Amogh Desai <am...@gmail.com>
> wrote:
>
> > Thank you, I will try to work on some POC soon
> >
> > On Tue, Feb 6, 2024 at 10:47 PM Briana Okyere
> > <br...@astronomer.io.invalid> wrote:
> >
> >> Would love your help on this Amogh!
> >>
> >> On Mon, Feb 5, 2024 at 9:40 PM Amogh Desai <am...@gmail.com>
> >> wrote:
> >>
> >> > Let us try to summarise and see what the bot has to do. Summarising:
> >> > 1. The bot should allow users to report issues - anonymously too (or
> >> maybe
> >> > an option)
> >> > 2. These issues should get redirected to an admin channel / private
> >> channel
> >> > 3. Some command in the bot that could allow users to find out the
> >> people in
> >> > that channel so that they can be contacted
> >> > privately too
> >> >
> >> > Havent deployed a bot ever, but would be willing to try
> >> >
> >> > Thanks & Regards,
> >> > Amogh Desai
> >> >
> >> > On Tue, Feb 6, 2024 at 12:58 AM Briana Okyere
> >> > <br...@astronomer.io.invalid> wrote:
> >> >
> >> > > 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
> >> > > <rb...@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" <jarek@potiuk.com
> <mailto:
> >> > > > jarek@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.rx@gmail.com
> >> <mailto:
> >> > > > weilee.rx@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 <
> >> aritrabasu1999@gmail.com
> >> > > > <ma...@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.anshin@taragol.is
> >> > > > <ma...@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.oss@gmail.com
> >> > > > <ma...@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.okyere@astronomer.io.inva <mailto:
> >> > > > briana.okyere@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-unsubscribe@airflow.apache.org
> >> <mailto:
> >> > > > dev-unsubscribe@airflow.apache.org>
> >> > > > > For additional commands, e-mail: dev-help@airflow.apache.org
> >> > <mailto:
> >> > > > dev-help@airflow.apache.org>
> >> > > > >
> >> > > > >
> >> > > >
> >> > > >
> >> > > >
> >> > > >
> >> > > >
> >> ---------------------------------------------------------------------
> >> > > > To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org
> >> > > > For additional commands, e-mail: dev-help@airflow.apache.org
> >> > > >
> >> > >
> >> >
> >>
> >
>
Re: [VOTE] Add the ability to report slack messages that don't meet code of conduct
Posted by Amogh Desai <am...@gmail.com>.
I was trying on a rough POC but it looks like I need to deploy my
application against a webserver on the internet.
I also do not have the access to create a private channel on Airflow Slack.
Thanks & Regards,
Amogh Desai
On Wed, Feb 7, 2024 at 9:43 AM Amogh Desai <am...@gmail.com> wrote:
> Thank you, I will try to work on some POC soon
>
> On Tue, Feb 6, 2024 at 10:47 PM Briana Okyere
> <br...@astronomer.io.invalid> wrote:
>
>> Would love your help on this Amogh!
>>
>> On Mon, Feb 5, 2024 at 9:40 PM Amogh Desai <am...@gmail.com>
>> wrote:
>>
>> > Let us try to summarise and see what the bot has to do. Summarising:
>> > 1. The bot should allow users to report issues - anonymously too (or
>> maybe
>> > an option)
>> > 2. These issues should get redirected to an admin channel / private
>> channel
>> > 3. Some command in the bot that could allow users to find out the
>> people in
>> > that channel so that they can be contacted
>> > privately too
>> >
>> > Havent deployed a bot ever, but would be willing to try
>> >
>> > Thanks & Regards,
>> > Amogh Desai
>> >
>> > On Tue, Feb 6, 2024 at 12:58 AM Briana Okyere
>> > <br...@astronomer.io.invalid> wrote:
>> >
>> > > 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
>> > > <rb...@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" <jarek@potiuk.com <mailto:
>> > > > jarek@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.rx@gmail.com
>> <mailto:
>> > > > weilee.rx@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 <
>> aritrabasu1999@gmail.com
>> > > > <ma...@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.anshin@taragol.is
>> > > > <ma...@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.oss@gmail.com
>> > > > <ma...@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.okyere@astronomer.io.inva <mailto:
>> > > > briana.okyere@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-unsubscribe@airflow.apache.org
>> <mailto:
>> > > > dev-unsubscribe@airflow.apache.org>
>> > > > > For additional commands, e-mail: dev-help@airflow.apache.org
>> > <mailto:
>> > > > dev-help@airflow.apache.org>
>> > > > >
>> > > > >
>> > > >
>> > > >
>> > > >
>> > > >
>> > > >
>> ---------------------------------------------------------------------
>> > > > To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org
>> > > > For additional commands, e-mail: dev-help@airflow.apache.org
>> > > >
>> > >
>> >
>>
>
Re: [VOTE] Add the ability to report slack messages that don't meet code of conduct
Posted by Amogh Desai <am...@gmail.com>.
Thank you, I will try to work on some POC soon
On Tue, Feb 6, 2024 at 10:47 PM Briana Okyere
<br...@astronomer.io.invalid> wrote:
> Would love your help on this Amogh!
>
> On Mon, Feb 5, 2024 at 9:40 PM Amogh Desai <am...@gmail.com>
> wrote:
>
> > Let us try to summarise and see what the bot has to do. Summarising:
> > 1. The bot should allow users to report issues - anonymously too (or
> maybe
> > an option)
> > 2. These issues should get redirected to an admin channel / private
> channel
> > 3. Some command in the bot that could allow users to find out the people
> in
> > that channel so that they can be contacted
> > privately too
> >
> > Havent deployed a bot ever, but would be willing to try
> >
> > Thanks & Regards,
> > Amogh Desai
> >
> > On Tue, Feb 6, 2024 at 12:58 AM Briana Okyere
> > <br...@astronomer.io.invalid> wrote:
> >
> > > 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
> > > <rb...@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" <jarek@potiuk.com <mailto:
> > > > jarek@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.rx@gmail.com <mailto:
> > > > weilee.rx@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 <
> aritrabasu1999@gmail.com
> > > > <ma...@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.anshin@taragol.is
> > > > <ma...@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.oss@gmail.com
> > > > <ma...@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.okyere@astronomer.io.inva <mailto:
> > > > briana.okyere@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-unsubscribe@airflow.apache.org
> <mailto:
> > > > dev-unsubscribe@airflow.apache.org>
> > > > > For additional commands, e-mail: dev-help@airflow.apache.org
> > <mailto:
> > > > dev-help@airflow.apache.org>
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org
> > > > For additional commands, e-mail: dev-help@airflow.apache.org
> > > >
> > >
> >
>
Re: [VOTE] Add the ability to report slack messages that don't meet code of conduct
Posted by Briana Okyere <br...@astronomer.io.INVALID>.
Would love your help on this Amogh!
On Mon, Feb 5, 2024 at 9:40 PM Amogh Desai <am...@gmail.com> wrote:
> Let us try to summarise and see what the bot has to do. Summarising:
> 1. The bot should allow users to report issues - anonymously too (or maybe
> an option)
> 2. These issues should get redirected to an admin channel / private channel
> 3. Some command in the bot that could allow users to find out the people in
> that channel so that they can be contacted
> privately too
>
> Havent deployed a bot ever, but would be willing to try
>
> Thanks & Regards,
> Amogh Desai
>
> On Tue, Feb 6, 2024 at 12:58 AM Briana Okyere
> <br...@astronomer.io.invalid> wrote:
>
> > 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
> > <rb...@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" <jarek@potiuk.com <mailto:
> > > jarek@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.rx@gmail.com <mailto:
> > > weilee.rx@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 <aritrabasu1999@gmail.com
> > > <ma...@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.anshin@taragol.is
> > > <ma...@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.oss@gmail.com
> > > <ma...@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.okyere@astronomer.io.inva <mailto:
> > > briana.okyere@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-unsubscribe@airflow.apache.org <mailto:
> > > dev-unsubscribe@airflow.apache.org>
> > > > For additional commands, e-mail: dev-help@airflow.apache.org
> <mailto:
> > > dev-help@airflow.apache.org>
> > > >
> > > >
> > >
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org
> > > For additional commands, e-mail: dev-help@airflow.apache.org
> > >
> >
>
Re: [VOTE] Add the ability to report slack messages that don't meet code of conduct
Posted by Amogh Desai <am...@gmail.com>.
Let us try to summarise and see what the bot has to do. Summarising:
1. The bot should allow users to report issues - anonymously too (or maybe
an option)
2. These issues should get redirected to an admin channel / private channel
3. Some command in the bot that could allow users to find out the people in
that channel so that they can be contacted
privately too
Havent deployed a bot ever, but would be willing to try
Thanks & Regards,
Amogh Desai
On Tue, Feb 6, 2024 at 12:58 AM Briana Okyere
<br...@astronomer.io.invalid> wrote:
> 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
> <rb...@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" <jarek@potiuk.com <mailto:
> > jarek@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.rx@gmail.com <mailto:
> > weilee.rx@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 <aritrabasu1999@gmail.com
> > <ma...@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.anshin@taragol.is
> > <ma...@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.oss@gmail.com
> > <ma...@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.okyere@astronomer.io.inva <mailto:
> > briana.okyere@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-unsubscribe@airflow.apache.org <mailto:
> > dev-unsubscribe@airflow.apache.org>
> > > For additional commands, e-mail: dev-help@airflow.apache.org <mailto:
> > dev-help@airflow.apache.org>
> > >
> > >
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org
> > For additional commands, e-mail: dev-help@airflow.apache.org
> >
>
Re: [VOTE] Add the ability to report slack messages that don't meet code of conduct
Posted by Briana Okyere <br...@astronomer.io.INVALID>.
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
<rb...@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" <jarek@potiuk.com <mailto:
> jarek@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.rx@gmail.com <mailto:
> weilee.rx@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 <aritrabasu1999@gmail.com
> <ma...@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.anshin@taragol.is
> <ma...@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.oss@gmail.com
> <ma...@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.okyere@astronomer.io.inva <mailto:
> briana.okyere@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-unsubscribe@airflow.apache.org <mailto:
> dev-unsubscribe@airflow.apache.org>
> > For additional commands, e-mail: dev-help@airflow.apache.org <mailto:
> dev-help@airflow.apache.org>
> >
> >
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org
> For additional commands, e-mail: dev-help@airflow.apache.org
>
Re: [VOTE] Add the ability to report slack messages that don't meet code of conduct
Posted by "Bishundeo, Rajeshwar" <rb...@amazon.com.INVALID>.
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" <jarek@potiuk.com <ma...@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.rx@gmail.com <ma...@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 <aritrabasu1999@gmail.com <ma...@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.anshin@taragol.is <ma...@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.oss@gmail.com <ma...@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.okyere@astronomer.io.inva <ma...@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-unsubscribe@airflow.apache.org <ma...@airflow.apache.org>
> For additional commands, e-mail: dev-help@airflow.apache.org <ma...@airflow.apache.org>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@airflow.apache.org
For additional commands, e-mail: dev-help@airflow.apache.org
Re: [VOTE] Add the ability to report slack messages that don't meet code of conduct
Posted by Jarek Potiuk <ja...@potiuk.com>.
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 <we...@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 <ar...@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 <an...@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
> >>
> >>
> >> 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 <am...@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
> >>>> <br...@astronomer.io.invalid> 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>
> >>>>
> >>>> 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-unsubscribe@airflow.apache.org
> For additional commands, e-mail: dev-help@airflow.apache.org
>
>
Re: [VOTE] Add the ability to report slack messages that don't meet code of conduct
Posted by Wei Lee <we...@gmail.com>.
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 <ar...@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 <an...@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
>>
>>
>> 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 <am...@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
>>>> <br...@astronomer.io.invalid> 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>
>>>>
>>>> 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-unsubscribe@airflow.apache.org
For additional commands, e-mail: dev-help@airflow.apache.org
Re: [VOTE] Add the ability to report slack messages that don't meet code of conduct
Posted by Aritra Basu <ar...@gmail.com>.
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 <an...@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
>
>
> 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 <am...@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
> >> <br...@astronomer.io.invalid> 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>
> >>
> >> 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
> >>
>
Re: [VOTE] Add the ability to report slack messages that don't meet code of conduct
Posted by Andrey Anshin <an...@taragol.is>.
I’m also for some bot/application, after quick search I’ve found this one 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 <am...@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
>> <br...@astronomer.io.invalid> 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>
>>
>> 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
>>
Re: [VOTE] Add the ability to report slack messages that don't meet code of conduct
Posted by Amogh Desai <am...@gmail.com>.
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
<br...@astronomer.io.invalid> 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>
>
> 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
>