I didn't realize that and perhaps I should have wrapped up that discussion more clearly. Apologies.
I thought Mark's suggestion was very good. All would take place at the official Apache slack channel. I set up a commons-gsoc channel and invited Ben and Abhishek. Certainly, that solves all the issues I had. I just wanted a communication channel. Welcome Ben and Abhishek, please find the commons-gsoc and let's communicate there. I will check in today, by end of California workday. On Mon, May 6, 2019 at 11:18 AM Rob Tompkins <chtom...@gmail.com> wrote: > > > > On May 6, 2019, at 2:13 PM, Udit Arora <udit18...@iiitd.ac.in> wrote: > > > > Congrats Ben. > > +1 Congrats, Ben. > > I think we’re trying to sort out what messaging system we’re going to use. > > -Rob > > > > > On Mon, 6 May 2019, 11:42 pm Ben Nguyen, <bennguye...@gmail.com> wrote: > > > >> Hello, > >> > >> Any update on which communication tool will be used? Slack, Zulip? I’m > >> excited to get started! > >> > >> Ben > >> > >> From: Mark Thomas > >> Sent: Wednesday, May 1, 2019 4:21 PM > >> To: Commons Developers List > >> Subject: Re: [numbers][GSoC] Slack for GSoC mentees > >> > >> On 01/05/2019 22:09, Eric Barnhill wrote: > >>> Thanks Mark, > >>> > >>> It looks like an apache.org domain email is required to register, and > I > >>> don't think my mentees are going to have one of those, so I may still > >> open > >>> a Zulip on the side. I am happy to have joined the commons slack there > >>> though! > >> > >> You should be able to invite folks without @apache.org addresses > >> > >> Mark > >> > >> > >>> > >>> Eric > >>> > >>> On Wed, May 1, 2019 at 1:58 PM Mark Thomas <ma...@apache.org> wrote: > >>> > >>>> On 01/05/2019 21:54, Eric Barnhill wrote: > >>>>> On Wed, May 1, 2019 at 1:49 PM Mark Thomas <ma...@apache.org> wrote: > >>>>> > >>>>>> On 01/05/2019 21:38, Eric Barnhill wrote: > >>>>>>> Actually some objections have been raised to using Slack because it > >> is > >>>>>> not > >>>>>>> open source. So the options will be either zulipchat if a group of > >>>> people > >>>>>>> want to use it, or Riot if it is just me. > >>>>>> > >>>>>> Better stop using GitHub as well then. > >>>>>> > >>>>>> There is no ASF policy that requires the tools we use to be open > >> source. > >>>>>> > >>>>>> > >>>>> Thanks for clarifying. > >>>>> > >>>>> > >>>>>> There is an ASF slack instance - you could request (create?) a > >>>>>> commons-gsoc channel there. > >>>>>> > >>>>> > >>>>> Knock me over with a feather. This not appear to be mentioned at > >>>>> community.apache.org . Is it asf.slack.com? > >>>> > >>>> the-asf.slack.com > >>>> There is already a commons channel. I think you can create > commons-gsoc > >>>> if you need it. If not, I look to be able to create channels. Just > ping > >> me. > >>>> > >>>> Mark > >>>> > >>>> --------------------------------------------------------------------- > >>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > >>>> For additional commands, e-mail: dev-h...@commons.apache.org > >>>> > >>>> > >>> > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > >> For additional commands, e-mail: dev-h...@commons.apache.org > >> > >> > >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
