Hey all,

While discussing on how to be more welcoming for the community, Tomek found
something really interesting on the devcomm list.

Tomek's email:
https://lists.apache.org/thread.html/r0192c6932e1bae8300ef50ac9284d7c609bca022bb7edc83ed35bf1d%40%3Cdev.airflow.apache.org%3E

"We have set up Mahout's slack space to forward directly to
> d...@mahout.apache.org. We will now be able to plan publicly on slack. This
> a bi-directional connection, all messages to d...@mahout.apache.org will
> show up in Slack. No one will be left out of planning."
>
> https://lists.apache.org/thread.html/rbc1c1c2a289accb40e7e3967f7c08213f13fea46013f73cf881c74c0%40%3Cdev.community.apache.org%3E


I think this is a very good find.

We can do something similar.
2 things I have in mind:

1) A separate list sl...@airflow.apache.org where we forward all Slack
communication

2) A selective forward (filter certain channels to different list). Some of
them can go to dev@ but some belong to users@ list


I see (1) being more relevant.

I have separated that thread to discuss the specifics of Slack as this can
be independent of that thread.

What do you guys think about this?

Regards,
Kaxil

Reply via email to