Thanks Jake and Vinod! Given the lack of a strong objection, trying it out in the irc-shadow mode sounds reasonable to me.
On Wed, Aug 3, 2016 at 3:52 PM, Jake Farrell <jfarr...@apache.org> wrote: > A number of people where starting to jump on mesos.slack.com #aurora and I > did not want to start having segmented communication occurring so I asked > Vinod to bridge our irc and the slack rooms with the same bot they are > using currently for #mesos. Thanks Vinod, appreciate the help. > > This will let us test out slack and see what the community thinks without > giving up irc, and still maintain all existing logging. If we think this is > a good solution we can look at using our own aurora.slack.com and move the > bridge. thoughts? > > -Jake > > > > On Wed, Aug 3, 2016 at 1:43 PM, Zameer Manji <zma...@apache.org> wrote: > > > I'm also +0 for the same reasons that John listed. > > > > On Tue, Aug 2, 2016 at 2:44 PM, John Sirois <john.sir...@gmail.com> > wrote: > > > >> I'm also +0. > >> > >> I am not a Slack fan, but that said, the barrier to entry on the face is > >> the same if we publicize self-signup like mesos has on their community > >> page > >> [1]: https://mesos-slackin.herokuapp.com/ > >> On the negative, we hurt folks like Jake who are connected to many > >> projects > >> via IRC and on the positive (maybe) we cater to the burgeoning set of > >> corporate contributors who are connected to many projects via Slack. > >> > >> Being paired with mesos is what tilits me +0 instead of -0. > >> > >> [1] http://mesos.apache.org/community/ > >> > >> On Tue, Aug 2, 2016 at 3:14 PM, Joshua Cohen <jco...@apache.org> wrote: > >> > >> > I'm +0 on this. I agree that Slack is in many ways superior to IRC, > but > >> it > >> > also feels like the barrier to entry for Slack is much higher than it > is > >> > for IRC which is potentially problematic for an open source community. > >> > > >> > On Tue, Aug 2, 2016 at 4:08 PM, Jake Farrell <jfarr...@apache.org> > >> wrote: > >> > > >> > > There is an irc bridge which relays all messages back as well as an > >> > archive > >> > > bot. Not a huge fan of slack due to it being yet another chat > client I > >> > have > >> > > in the background, but if it helps the community stay connected and > >> grow > >> > > and makes things easier then +1 for whatever it is. > >> > > > >> > > Might make sense for us to use the mesos.slack.com #aurora channel > >> that > >> > > way > >> > > the two communities stay close and its easier for users to find and > >> ask > >> > > questions rather than having multiple slacks they have to join and > >> keep > >> > > track of > >> > > > >> > > -Jake > >> > > > >> > > > >> > > > >> > > > >> > > On Tue, Aug 2, 2016 at 4:48 PM, Steve Niemitz <sniem...@apache.org> > >> > wrote: > >> > > > >> > > > +1, I pretty much never remember to open my IRC client anymore. > >> I've > >> > > been > >> > > > using the Mesos Slack for a few weeks now and its way better than > >> > IRC. I > >> > > > believe they have chat logging still via a bot of some type too? > >> > > > > >> > > > On Tue, Aug 2, 2016 at 4:45 PM, Maxim Khutornenko < > ma...@apache.org > >> > > >> > > > wrote: > >> > > > > >> > > > > Mesos community has recently moved to Slack as their canonical > >> chat > >> > > > channel > >> > > > > [1]. Thanks to Stephan, we already have some presence there via > >> > #aurora > >> > > > > channel in Apache Mesos team. > >> > > > > > >> > > > > Should we move our IRC discussions to Slack too? > >> > > > > > >> > > > > [1] - http://markmail.org/message/azd37j64wsozmuhe > >> > > > > > >> > > > > >> > > > >> > > >> > > > > >
