unsubscribe
On 2/12/19, 9:07 PM, "Ash Berlin-Taylor" <[email protected]> wrote:
Ah good to know.
Still, for me the biggest downsides against migrating is cost - we've got
about 3-400 active users a week which would cost the ASF almost $28,000 a year.
That seems like a lot for chat history; and secondly the hassle of migrating
everyone to a new chat workspace - there are still people on Gitter ;)
-ash
> On 12 Feb 2019, at 21:03, Pablo Estrada <[email protected]> wrote:
>
> The ASF slack has two ways of auto-invites:
>
> - For people with @apache.org emails, they can request an invitation
> directly in the-asf.slack.com <http://the-asf.slack.com/>.
> - For people without @apache.org, the ASF slack admins need to renew an
> open invitation that anyone can use. Short link:
> https://s.apache.org/slack-invite <https://s.apache.org/slack-invite>
>
> We've been using it in Beam, and we've generally had no problem. We used
to
> have to ask ASF Slack admins to renew the open invitation link every now
> and then, but I think now it's permanent (dont quote me on that. I didnt
> check it consistently over time).
>
> I understand that it's good to have control of the invite within the
> Airflow community, so it's definitely a tradeoff to consider.
>
> Best
> -P.
>
> On Tue, Feb 12, 2019 at 1:15 AM Ash Berlin-Taylor <[email protected]
<mailto:[email protected]>> wrote:
>
>> Automatic invitations only work if you have an @apache.org email address
>> I think, so that is going to be of use to almost no one.
>>
>>
>>
>>> On 12 Feb 2019, at 08:03, Kaxil Naik <[email protected]> wrote:
>>>
>>> Sounds good actually. How's does automatic invitation works ?
>>>
>>> On Tue, Feb 12, 2019, 01:09 Aizhamal Nurmamat kyzy
>>> <[email protected]> wrote:
>>>
>>>> Hi Kaxil,
>>>>
>>>> As Austin mentioned above, it is possible to create separate channels
>> per
>>>> topic in the ASF. You can see in the first screenshot that I attached.
>>>>
>>>> And yes, ASF slacks keep full history and ASF pays to have that
feature.
>>>> However slack history is not used as platform for decision making. It
>> more
>>>> for people to go check for tips / links / etc in old conversations.
>>>>
>>>> Airflow seems not to keep a full history atm, see the second screenshot
>>>> for reference. Slack keeps the history up until 4 months and then it
>> gets
>>>> deleted.
>>>>
>>>> I'm not pushing for one or the other, but I think it's worth for the
>>>> community to consider the options : )
>>>>
>>>> Thank you!
>>>> -A.
>>>> [image: Screen Shot 2019-02-11 at 4.46.27 PM.png]
>>>> [image: Screen Shot 2019-02-11 at 4.48.11 PM.png]
>>>>
>>>> On Mon, Feb 11, 2019 at 9:33 AM Austin Bennett <
>>>> [email protected]> wrote:
>>>>
>>>>> Hi Kaxil,
>>>>>
>>>>> Not suggesting that a migration to ASF slack is the right move (don't
>> have
>>>>> a strong opinion).
>>>>>
>>>>> I disagree with your premise that separation of channels per topic is
>>>>> impossible in the ASF
>>>>>
>>>>> Seems could have channels in the ASF Slack :
>>>>> #Airflow-announce
>>>>> #Airflow-users-bay-area
>>>>> #Airflow-github
>>>>> #Airflow-random
>>>>> #Airflow-creative
>>>>>
>>>>>
>>>>> As an example, Beam has many different slack channels for many
>> different
>>>>> topics.
>>>>>
>>>>>
>>>>> Another point to consider, message history: Do either Airflow and/or
>> ASF
>>>>> Slack's keep full history? And/or would one or the other allow or
make
>>>>> easier the ability to keep history for archive of ongoing record (if
>>>>> desired)? I have seen slack being 'mirrored'/synced, with other
>> messaging
>>>>> platforms for either alternate interface or archive/history.
>>>>>
>>>>> Cheers,
>>>>> Austin
>>>>>
>>>>>
>>>>>
>>>>>> On Mon, Feb 11, 2019 at 12:04 AM Kaxil Naik <[email protected]>
>> wrote:
>>>>>>
>>>>>> Currently, we have a good separation of channels per topic. A
separate
>>>>>> channel for announcement etc. This won't be possible if we move to
ASF
>>>>>> slack.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Mon, Feb 11, 2019, 07:45 Aizhamal Nurmamat kyzy
>>>>>> <[email protected]> wrote:
>>>>>>
>>>>>>> Hello everybody!
>>>>>>>
>>>>>>> I was wondering what the community thinks of migrating Apache
Airflow
>>>>>> slack
>>>>>>> channel [1] to the official ASF slack [2]?
>>>>>>>
>>>>>>> Some advantages would be:
>>>>>>>
>>>>>>> 1. It would allow for Airflow community to interact/chat with the
>>>>>>> communities of many other Apache projects
>>>>>>> 2. It would make Airflow remain consistent with ASF projects
>>>>>>> 3. It would allow to auto join for ASF commun
>>
<https://maps.google.com/?q=would+allow+to+auto+join+for+ASF+commun&entry=gmail&source=g
<https://maps.google.com/?q=would+allow+to+auto+join+for+ASF+commun&entry=gmail&source=g>>ity
>> members
>>>>>>>
>>>>>>> A possible disadvantage would be that we will depend on Apache
>>>>> members to
>>>>>>> renew the invite link.
>>>>>>>
>>>>>>> What are your thoughts?
>>>>>>>
>>>>>>> [1] https://apache-airflow.slack.com
<https://apache-airflow.slack.com/>
>>>>>>> [2] https://the-asf.slack.com <https://the-asf.slack.com/>
>>>>>>>
>>>>>>> --
>>>>>>>
>>>>>>> *Aizhamal Nurmamat kyzy*
>>>>>>>
>>>>>>> Open Source Program Manager
>>>>>>>
>>>>>>> 646-355-9740 <(646)%20355-9740> Mobile
>>>>>>>
>>>>>>> 601 North 34th Street, Seattle, WA 98103
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> *Aizhamal Nurmamat kyzy*
>>>>
>>>> Open Source Program Manager
>>>>
>>>> 646-355-9740 <(646)%20355-9740> Mobile
>>>>
>>>> 601 North 34th Street, Seattle, WA 98103
