kudu-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Percy <mpe...@apache.org>
Subject Re: [DISCUSS] Move Slack discussions to ASF official slack?
Date Tue, 24 Oct 2017 03:19:45 GMT
Users will likely be confused if they have to switch Slack instances. We switched over to ASF
mailing lists over a year ago and we still get requests to join the old pre-ASF user mailing
list sometimes.

Unfortunately the Slack-In inviter bot doesn’t allow you to invite people to a particular
room without a paid account. It has to go to the default room for the whole instance. Maybe
we could ask Slack if it’s possible to get an exception for the ASF.

That said, if it’s not strictly better than what we have then I don’t see a real benefit
in switching.

Mike

> On Oct 24, 2017, at 8:22 AM, Todd Lipcon <todd@cloudera.com> wrote:
> 
>> On Mon, Oct 23, 2017 at 4:12 PM, Misty Stanley-Jones <misty@apache.org> wrote:
>> 1.  I have no idea, but you could enable the @all at-mention in the eisting #kudu-general
and let people know that way. Also see my next answer.
>> 
> 
> Fair enough.
>  
>> 2.  It looks like if you have an apache.org email address you don't need an invite,
but otherwise an existing member needs to invite you. If you can somehow get all the member
email addresses, you can invite them all at once as a comma-separated list.
> 
> I'm not sure if that's doable but potentially.
> 
> I'm concerned though if we don't have auto-invite for arbitrary community members who
just come by a link from our website. A good portion of our traffic is users, rather than
developers, and by-and-large they don't have apache.org addresses. If we closed the Slack
off to them I think we'd lose a lot of the benefit.
>  
>> 
>> 3.  I can't tell what access there is to integrations. I can try to find out who
administers that on ASF infra and get back with you. I would not be surprised if integrations
with the ASF JIRA were already enabled.
>> 
>> I pre-emptively grabbed #kudu on the ASF slack in case we decide to go forward with
this. If we don't decide to go forward with it, it's a good idea to hold onto the channel
and pin a message in there about how to get to the "official" Kudu slack.
>> 
>>> On Mon, Oct 23, 2017 at 3:00 PM, Todd Lipcon <todd@cloudera.com> wrote:
>>> A couple questions about this:
>>> 
>>> - is there any way we can email out to our existing Slack user base to invite
them to move over? We have 866 members on our current slack and would be a shame if people
got confused as to where to go for questions.
>>> 
>>> - does the ASF slack now have a functioning self-serve "auto-invite" service?
>>> 
>>> - will we still be able to set up integrations like JIRA/github?
>>> 
>>> -Todd
>>> 
>>>> On Mon, Oct 23, 2017 at 2:53 PM, Misty Stanley-Jones <misty@apache.org>
wrote:
>>>> When we first started using Slack, I don't think the ASF Slack instance
>>>> existed. Using our own Slack instance means that we have limited access to
>>>> message archives (unless we pay) and that people who work on multiple ASF
>>>> projects need to add the Kudu slack in addition to any other Slack
>>>> instances they may be on. I propose that we instead create one or more
>>>> Kudu-related channels on the official ASF slack (http://the-asf.slack.com/)
>>>> and migrate our discussions there. What does everyone think?
>>> 
>>> 
>>> 
>>> -- 
>>> Todd Lipcon
>>> Software Engineer, Cloudera
>> 
> 
> 
> 
> -- 
> Todd Lipcon
> Software Engineer, Cloudera

Mime
View raw message