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 ro
On Mon, Oct 23, 2017 at 4:12 PM, Misty Stanley-Jones
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
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.
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
some
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-se
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 t
