Re: Guidance : Gitter --> Slack

[Greg Stein]

John (cc'd) set up the workspace. I dunno how it is configured.

On Sat, Sep 1, 2018 at 9:04 PM Sid Anand  wrote:

> I see the channel now. I could not find it earlier, hence my trying to
> create it. Yes, it seems like someone set this up.
>
> So, am I correct in assuming that anyone can register an account on this
> slack workspace using any email account (e.g. does not need to be
> Apache.org emails)? Is that correct?
>
> -s
>
> On Sat, Sep 1, 2018 at 6:32 PM Greg Stein  wrote:
>
> > On Sat, Sep 1, 2018 at 8:04 PM Sid Anand  wrote:
> >
> > > Hi Greg,
> > > Interesting. I just tried that and was shown "airflow is already taken
> > by a
> > > channel, user, or user group".
> > >
> >
> > Seems somebody in your community already set it up?
> >
> >
> > > However, apache-airflow is available.
> > >
> >
> > Why create something new, instead of just using #airflow?? Please stop
> > trying to create a new area, and instead join *existing* areas to
> converse.
> > And specifically stay with your dev@ mailing list.
> >
> >
> > > I noticed channels for general.  I figured general would be limited to
> > the
> > > ASF mailing lists.
> >
> >
> > Hunh? Slack is unrelated to mailing lists. That was my point about
> avoiding
> > chat, and sticking to dev@ mailing lists. And the #general channel is
> > totally unrelated to this, or any other mailing list.
> >
> > -g
> >
>

Re: Guidance : Gitter --> Slack

[Sid Anand]

I see the channel now. I could not find it earlier, hence my trying to
create it. Yes, it seems like someone set this up.

So, am I correct in assuming that anyone can register an account on this
slack workspace using any email account (e.g. does not need to be
Apache.org emails)? Is that correct?

-s

On Sat, Sep 1, 2018 at 6:32 PM Greg Stein  wrote:

> On Sat, Sep 1, 2018 at 8:04 PM Sid Anand  wrote:
>
> > Hi Greg,
> > Interesting. I just tried that and was shown "airflow is already taken
> by a
> > channel, user, or user group".
> >
>
> Seems somebody in your community already set it up?
>
>
> > However, apache-airflow is available.
> >
>
> Why create something new, instead of just using #airflow?? Please stop
> trying to create a new area, and instead join *existing* areas to converse.
> And specifically stay with your dev@ mailing list.
>
>
> > I noticed channels for general.  I figured general would be limited to
> the
> > ASF mailing lists.
>
>
> Hunh? Slack is unrelated to mailing lists. That was my point about avoiding
> chat, and sticking to dev@ mailing lists. And the #general channel is
> totally unrelated to this, or any other mailing list.
>
> -g
>

Re: Guidance : Gitter --> Slack

[Greg Stein]

On Sat, Sep 1, 2018 at 8:04 PM Sid Anand  wrote:

> Hi Greg,
> Interesting. I just tried that and was shown "airflow is already taken by a
> channel, user, or user group".
>

Seems somebody in your community already set it up?


> However, apache-airflow is available.
>

Why create something new, instead of just using #airflow?? Please stop
trying to create a new area, and instead join *existing* areas to converse.
And specifically stay with your dev@ mailing list.


> I noticed channels for general.  I figured general would be limited to the
> ASF mailing lists.


Hunh? Slack is unrelated to mailing lists. That was my point about avoiding
chat, and sticking to dev@ mailing lists. And the #general channel is
totally unrelated to this, or any other mailing list.

-g

Re: Guidance : Gitter --> Slack

[Sid Anand]

Hi Greg,
Interesting. I just tried that and was shown "airflow is already taken by a
channel, user, or user group".

However, apache-airflow is available.

I noticed channels for general.  I figured general would be limited to the
ASF mailing lists.

-s

On Sat, Sep 1, 2018 at 2:23 PM Greg Stein  wrote:

> I would suggest an #airflow channel on the-asf.slack.com
>
>
> On Sat, Sep 1, 2018, 15:36 Sid Anand  wrote:
>
> > How would I establish airflow.slack.com? Would I just go ahead and
> create
> > the workspace? Or is there a preference to have Apache Infra create and
> own
> > it?
> >
> > -s
> >
> > On Fri, Aug 31, 2018 at 7:08 PM Greg Stein  wrote:
> >
> > > Slack has no F/OSS discounts, but they *do* have a discount for
> charities
> > > like the ASF. The ASF has not (yet) chosen to purchase a license,
> though,
> > > as we encourage mailing lists rather than synchronous chat services. We
> > > also want the discussions *recorded* on ASF hardware for
> archival/review
> > > purposes. Mailing lists are easily archived, but not so easily for
> chat.
> > >
> > > At Apache, chat services should be viewed as *supplemental* to a
> > project's
> > > dev@ list. This is why we're not spending $$ on them. Projects should
> be
> > > more concerned about keeping discussion on-list, rather than what chat
> > > service to use.
> > >
> > > Cheers,
> > > -g
> > >
> > >
> > > On Fri, Aug 31, 2018 at 8:59 PM Abhishek Tiwari 
> wrote:
> > >
> > > > Are you okay with message count limitation with Slack? or is there
> any
> > > > license that they have for open source projects?
> > > >
> > > > Abhishek
> > > >
> > > > On Fri, Aug 31, 2018 at 3:48 PM Sid Anand  wrote:
> > > >
> > > > > Hi Folks!
> > > > > The Airflow community would like to move to Slack from Gitter. Is
> > there
> > > > any
> > > > > guidance on this list on how to do that? We would essentially like
> to
> > > > > shutdown Gitter.
> > > > >
> > > > > -s
> > > > >
> > > >
> > >
> >
>

Re: Guidance : Gitter --> Slack

[Greg Stein]

I would suggest an #airflow channel on the-asf.slack.com


On Sat, Sep 1, 2018, 15:36 Sid Anand  wrote:

> How would I establish airflow.slack.com? Would I just go ahead and create
> the workspace? Or is there a preference to have Apache Infra create and own
> it?
>
> -s
>
> On Fri, Aug 31, 2018 at 7:08 PM Greg Stein  wrote:
>
> > Slack has no F/OSS discounts, but they *do* have a discount for charities
> > like the ASF. The ASF has not (yet) chosen to purchase a license, though,
> > as we encourage mailing lists rather than synchronous chat services. We
> > also want the discussions *recorded* on ASF hardware for archival/review
> > purposes. Mailing lists are easily archived, but not so easily for chat.
> >
> > At Apache, chat services should be viewed as *supplemental* to a
> project's
> > dev@ list. This is why we're not spending $$ on them. Projects should be
> > more concerned about keeping discussion on-list, rather than what chat
> > service to use.
> >
> > Cheers,
> > -g
> >
> >
> > On Fri, Aug 31, 2018 at 8:59 PM Abhishek Tiwari  wrote:
> >
> > > Are you okay with message count limitation with Slack? or is there any
> > > license that they have for open source projects?
> > >
> > > Abhishek
> > >
> > > On Fri, Aug 31, 2018 at 3:48 PM Sid Anand  wrote:
> > >
> > > > Hi Folks!
> > > > The Airflow community would like to move to Slack from Gitter. Is
> there
> > > any
> > > > guidance on this list on how to do that? We would essentially like to
> > > > shutdown Gitter.
> > > >
> > > > -s
> > > >
> > >
> >
>

Re: Guidance : Gitter --> Slack

[Sid Anand]

How would I establish airflow.slack.com? Would I just go ahead and create
the workspace? Or is there a preference to have Apache Infra create and own
it?

-s

On Fri, Aug 31, 2018 at 7:08 PM Greg Stein  wrote:

> Slack has no F/OSS discounts, but they *do* have a discount for charities
> like the ASF. The ASF has not (yet) chosen to purchase a license, though,
> as we encourage mailing lists rather than synchronous chat services. We
> also want the discussions *recorded* on ASF hardware for archival/review
> purposes. Mailing lists are easily archived, but not so easily for chat.
>
> At Apache, chat services should be viewed as *supplemental* to a project's
> dev@ list. This is why we're not spending $$ on them. Projects should be
> more concerned about keeping discussion on-list, rather than what chat
> service to use.
>
> Cheers,
> -g
>
>
> On Fri, Aug 31, 2018 at 8:59 PM Abhishek Tiwari  wrote:
>
> > Are you okay with message count limitation with Slack? or is there any
> > license that they have for open source projects?
> >
> > Abhishek
> >
> > On Fri, Aug 31, 2018 at 3:48 PM Sid Anand  wrote:
> >
> > > Hi Folks!
> > > The Airflow community would like to move to Slack from Gitter. Is there
> > any
> > > guidance on this list on how to do that? We would essentially like to
> > > shutdown Gitter.
> > >
> > > -s
> > >
> >
>

Re: Guidance : Gitter --> Slack

[Greg Stein]

Slack has no F/OSS discounts, but they *do* have a discount for charities
like the ASF. The ASF has not (yet) chosen to purchase a license, though,
as we encourage mailing lists rather than synchronous chat services. We
also want the discussions *recorded* on ASF hardware for archival/review
purposes. Mailing lists are easily archived, but not so easily for chat.

At Apache, chat services should be viewed as *supplemental* to a project's
dev@ list. This is why we're not spending $$ on them. Projects should be
more concerned about keeping discussion on-list, rather than what chat
service to use.

Cheers,
-g


On Fri, Aug 31, 2018 at 8:59 PM Abhishek Tiwari  wrote:

> Are you okay with message count limitation with Slack? or is there any
> license that they have for open source projects?
>
> Abhishek
>
> On Fri, Aug 31, 2018 at 3:48 PM Sid Anand  wrote:
>
> > Hi Folks!
> > The Airflow community would like to move to Slack from Gitter. Is there
> any
> > guidance on this list on how to do that? We would essentially like to
> > shutdown Gitter.
> >
> > -s
> >
>

Re: Guidance : Gitter --> Slack

[Abhishek Tiwari]

Are you okay with message count limitation with Slack? or is there any
license that they have for open source projects?

Abhishek

On Fri, Aug 31, 2018 at 3:48 PM Sid Anand  wrote:

> Hi Folks!
> The Airflow community would like to move to Slack from Gitter. Is there any
> guidance on this list on how to do that? We would essentially like to
> shutdown Gitter.
>
> -s
>

Guidance : Gitter --> Slack

[Sid Anand]

Hi Folks!
The Airflow community would like to move to Slack from Gitter. Is there any
guidance on this list on how to do that? We would essentially like to
shutdown Gitter.

-s

Re: [LAZY] Letting anyone invite on Slack

[Mike Drob]

Anybody with an @apache.org email address can self-register

On Thu, Oct 19, 2017 at 2:38 PM, Gang(Gary) Wang <ga...@apache.org> wrote:

> Can I get an invitation? Thanks.
>
> On Thu, Oct 19, 2017 at 12:14 PM, Anu Engineer <aengin...@hortonworks.com>
> wrote:
>
> > Thank you very much, greatly appreciate it.
> >
> > We are using slack and this allows even non-committers to participate,
> > which was an issue earlier
> >
> > Thanks
> > Anu
> >
> >
> >
> >
> > On 10/19/17, 11:47 AM, "Hen" <bay...@apache.org> wrote:
> >
> > Done. Anyone on TheAsf slack workspace can invite someone to the
> > workspace.
> >
> > On Sat, Oct 14, 2017 at 03:28 Greg Stein <gst...@gmail.com> wrote:
> >
> > > Fair enough... then open it up. Not even sure why that's a question
> > :-)
> > >
> > > On Sat, Oct 14, 2017 at 1:52 AM, Hen <bay...@apache.org> wrote:
> > >
> > > > While I lean to the 'not seeing the value of Slack', we have many
> > > channels
> > > > on Slack now (mostly driven by Incubator projects I think; John
> > seems to
> > > > have taken the lead on the workspace), so this isn't a thread for
> > getting
> > > > rid of slack :)
> > > >
> > > > Hen
> > > >
> > > > On Fri, Oct 13, 2017 at 11:06 PM, Craig Russell <
> > apache@gmail.com>
> > > > wrote:
> > > >
> > > > > Hi Henri,
> > > > >
> > > > > We tried to use slack with the Juneau project and never got it
> > to work
> > > > > "the Apache Way". Inviting people instead of self-service, no
> > ability
> > > to
> > > > > monitor discussions, no archive of discussions.
> > > > >
> > > > > We gave up and now use the wiki whenever mail doesn't serve.
> > Common
> > > > > editing of documents, diagrams, etc. are all easily done on
> > confluence
> > > > > where email doesn't allow sharing documents.
> > > > >
> > > > > I frankly do not see slack filling a need here.
> > > > >
> > > > > Craig
> > > > >
> > > > > > On Oct 13, 2017, at 9:51 PM, Henri Yandell <
> bay...@apache.org>
> > > wrote:
> > > > > >
> > > > > > Currently only 'admins' can invite people to the ASF Slack:
> > > > > >
> > > > > >  https://the-asf.slack.com/
> > > > > >
> > > > > > If we view it as an IRC equivalent, having to invite people
> at
> > all is
> > > > > > weird. We can, via a checkbox, change it so anyone on the ASF
> > Slack
> > > > > (except
> > > > > > 'guests') can invite someone to the Slack workspace:
> > > > > >
> > > > > > 
> > > > > >
> > > > > > Invitations
> > > > > >
> > > > > > Choose whether to allow non-admins to invite new people to
> > *ASF*.
> > > > > >
> > > > > > Allow everyone (except guests) to invite new members.
> > > > > > 
> > > > > >
> > > > > > I can't see why we'd have an issue there, so I'm planning to
> > turn
> > > that
> > > > > > checkbox on at the end of next week (Thursday or whenever I
> > remember
> > > to
> > > > > > after that :) ).
> > > > > >
> > > > > > If this is a bad idea, please object and let me know why :)
> > > > > >
> > > > > > Hen
> > > > >
> > > > > Craig L Russell
> > > > > c...@apache.org
> > > > >
> > > > >
> > > > > 
> > -
> > > > > To unsubscribe, e-mail: general-unsubscribe@incubator.
> apache.org
> > > > > For additional commands, e-mail: general-help@incubator.apache.
> > org
> > > > >
> > > > >
> > > >
> > >
> >
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>

Re: [LAZY] Letting anyone invite on Slack

[Gang(Gary) Wang]

Can I get an invitation? Thanks.

On Thu, Oct 19, 2017 at 12:14 PM, Anu Engineer <aengin...@hortonworks.com>
wrote:

> Thank you very much, greatly appreciate it.
>
> We are using slack and this allows even non-committers to participate,
> which was an issue earlier
>
> Thanks
> Anu
>
>
>
>
> On 10/19/17, 11:47 AM, "Hen" <bay...@apache.org> wrote:
>
> Done. Anyone on TheAsf slack workspace can invite someone to the
> workspace.
>
> On Sat, Oct 14, 2017 at 03:28 Greg Stein <gst...@gmail.com> wrote:
>
> > Fair enough... then open it up. Not even sure why that's a question
> :-)
> >
> > On Sat, Oct 14, 2017 at 1:52 AM, Hen <bay...@apache.org> wrote:
> >
> > > While I lean to the 'not seeing the value of Slack', we have many
> > channels
> > > on Slack now (mostly driven by Incubator projects I think; John
> seems to
> > > have taken the lead on the workspace), so this isn't a thread for
> getting
> > > rid of slack :)
> > >
> > > Hen
>     > >
> > > On Fri, Oct 13, 2017 at 11:06 PM, Craig Russell <
> apache@gmail.com>
> > > wrote:
> > >
> > > > Hi Henri,
> > > >
> > > > We tried to use slack with the Juneau project and never got it
> to work
> > > > "the Apache Way". Inviting people instead of self-service, no
> ability
> > to
> > > > monitor discussions, no archive of discussions.
> > > >
> > > > We gave up and now use the wiki whenever mail doesn't serve.
> Common
> > > > editing of documents, diagrams, etc. are all easily done on
> confluence
> > > > where email doesn't allow sharing documents.
> > > >
> > > > I frankly do not see slack filling a need here.
> > > >
> > > > Craig
> > > >
> > > > > On Oct 13, 2017, at 9:51 PM, Henri Yandell <bay...@apache.org>
> > wrote:
> > > > >
> > > > > Currently only 'admins' can invite people to the ASF Slack:
> > > > >
> > > > >  https://the-asf.slack.com/
> > > > >
> > > > > If we view it as an IRC equivalent, having to invite people at
> all is
> > > > > weird. We can, via a checkbox, change it so anyone on the ASF
> Slack
> > > > (except
> > > > > 'guests') can invite someone to the Slack workspace:
> > > > >
> > > > > 
> > > > >
> > > > > Invitations
> > > > >
> > > > > Choose whether to allow non-admins to invite new people to
> *ASF*.
> > > > >
> > > > > Allow everyone (except guests) to invite new members.
> > > > > 
> > > > >
> > > > > I can't see why we'd have an issue there, so I'm planning to
> turn
> > that
> > > > > checkbox on at the end of next week (Thursday or whenever I
> remember
> > to
> > > > > after that :) ).
> > > > >
> > > > > If this is a bad idea, please object and let me know why :)
> > > > >
> > > > > Hen
> > > >
> > > > Craig L Russell
> > > > c...@apache.org
> > > >
> > > >
> > > > 
> -
> > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > For additional commands, e-mail: general-help@incubator.apache.
> org
> > > >
> > > >
> > >
> >
>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

Re: [LAZY] Letting anyone invite on Slack

[Anu Engineer]

Thank you very much, greatly appreciate it. 

We are using slack and this allows even non-committers to participate, which 
was an issue earlier

Thanks
Anu




On 10/19/17, 11:47 AM, "Hen" <bay...@apache.org> wrote:

Done. Anyone on TheAsf slack workspace can invite someone to the workspace.

On Sat, Oct 14, 2017 at 03:28 Greg Stein <gst...@gmail.com> wrote:

> Fair enough... then open it up. Not even sure why that's a question :-)
>
> On Sat, Oct 14, 2017 at 1:52 AM, Hen <bay...@apache.org> wrote:
>
> > While I lean to the 'not seeing the value of Slack', we have many
> channels
> > on Slack now (mostly driven by Incubator projects I think; John seems to
> > have taken the lead on the workspace), so this isn't a thread for 
getting
> > rid of slack :)
> >
> > Hen
> >
> > On Fri, Oct 13, 2017 at 11:06 PM, Craig Russell <apache....@gmail.com>
> > wrote:
> >
> > > Hi Henri,
> > >
> > > We tried to use slack with the Juneau project and never got it to work
> > > "the Apache Way". Inviting people instead of self-service, no ability
> to
> > > monitor discussions, no archive of discussions.
> > >
> > > We gave up and now use the wiki whenever mail doesn't serve. Common
> > > editing of documents, diagrams, etc. are all easily done on confluence
> > > where email doesn't allow sharing documents.
> > >
> > > I frankly do not see slack filling a need here.
> > >
> > > Craig
> > >
> > > > On Oct 13, 2017, at 9:51 PM, Henri Yandell <bay...@apache.org>
> wrote:
> > > >
> > > > Currently only 'admins' can invite people to the ASF Slack:
> > > >
> > > >  https://the-asf.slack.com/
> > > >
> > > > If we view it as an IRC equivalent, having to invite people at all 
is
> > > > weird. We can, via a checkbox, change it so anyone on the ASF Slack
> > > (except
> > > > 'guests') can invite someone to the Slack workspace:
> > > >
> > > > 
> > > >
> > > > Invitations
> > > >
> > > > Choose whether to allow non-admins to invite new people to *ASF*.
> > > >
> > > > Allow everyone (except guests) to invite new members.
> > > > 
> > > >
> > > > I can't see why we'd have an issue there, so I'm planning to turn
> that
> > > > checkbox on at the end of next week (Thursday or whenever I remember
> to
> > > > after that :) ).
> > > >
> > > > If this is a bad idea, please object and let me know why :)
> > > >
> > > > Hen
> > >
> > > Craig L Russell
> > > c...@apache.org
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
>



-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [LAZY] Letting anyone invite on Slack

[Hen]

Done. Anyone on TheAsf slack workspace can invite someone to the workspace.

On Sat, Oct 14, 2017 at 03:28 Greg Stein <gst...@gmail.com> wrote:

> Fair enough... then open it up. Not even sure why that's a question :-)
>
> On Sat, Oct 14, 2017 at 1:52 AM, Hen <bay...@apache.org> wrote:
>
> > While I lean to the 'not seeing the value of Slack', we have many
> channels
> > on Slack now (mostly driven by Incubator projects I think; John seems to
> > have taken the lead on the workspace), so this isn't a thread for getting
> > rid of slack :)
> >
> > Hen
> >
> > On Fri, Oct 13, 2017 at 11:06 PM, Craig Russell <apache....@gmail.com>
> > wrote:
> >
> > > Hi Henri,
> > >
> > > We tried to use slack with the Juneau project and never got it to work
> > > "the Apache Way". Inviting people instead of self-service, no ability
> to
> > > monitor discussions, no archive of discussions.
> > >
> > > We gave up and now use the wiki whenever mail doesn't serve. Common
> > > editing of documents, diagrams, etc. are all easily done on confluence
> > > where email doesn't allow sharing documents.
> > >
> > > I frankly do not see slack filling a need here.
> > >
> > > Craig
> > >
> > > > On Oct 13, 2017, at 9:51 PM, Henri Yandell <bay...@apache.org>
> wrote:
> > > >
> > > > Currently only 'admins' can invite people to the ASF Slack:
> > > >
> > > >  https://the-asf.slack.com/
> > > >
> > > > If we view it as an IRC equivalent, having to invite people at all is
> > > > weird. We can, via a checkbox, change it so anyone on the ASF Slack
> > > (except
> > > > 'guests') can invite someone to the Slack workspace:
> > > >
> > > > 
> > > >
> > > > Invitations
> > > >
> > > > Choose whether to allow non-admins to invite new people to *ASF*.
> > > >
> > > > Allow everyone (except guests) to invite new members.
> > > > 
> > > >
> > > > I can't see why we'd have an issue there, so I'm planning to turn
> that
> > > > checkbox on at the end of next week (Thursday or whenever I remember
> to
> > > > after that :) ).
> > > >
> > > > If this is a bad idea, please object and let me know why :)
> > > >
> > > > Hen
> > >
> > > Craig L Russell
> > > c...@apache.org
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
>

Re: [LAZY] Letting anyone invite on Slack

[John D. Ament]

On Sat, Oct 14, 2017 at 8:03 AM Wade Chandler <wadechand...@apache.org>
wrote:

> We do this with ours:
>
> https://netbeans.signup.team
>
>
Seems like this service is going to be retired soon.


> The Slack guys are the ones who even told us to. There is no theoretical
> limit according to them. You just have to manage the outstanding invites,
> and clean them up if there are a bunch where folks did not finish out the
> process. If you do not, then invites won't work until you do after some
> critical mass.
>
> We also use a bot to do this, which the Slack folks recommended us do:
> https://netbeans.slackarchive.io
>
>
Huh.  This solves the issue I have which is archiving.  We tried DigestAI,
it randomly just stops and the content is not very useful.  Let me try this
out.


> There are probably some OSS bots ASF could use to do this and other things
> for such systems to keep full data logs inside ASF; own the data forever.
>
> We also have a channel linked to our IRC channel where we can monitor and
> help with it from Slack.
>
> Anyways, it all seems to work great so far.
>
> Thanks
>
> Wade
>
>
> On Oct 13, 2017 23:52, "Henri Yandell" <bay...@apache.org> wrote:
>
> Currently only 'admins' can invite people to the ASF Slack:
>
>   https://the-asf.slack.com/
>
> If we view it as an IRC equivalent, having to invite people at all is
> weird. We can, via a checkbox, change it so anyone on the ASF Slack (except
> 'guests') can invite someone to the Slack workspace:
>
> 
>
> Invitations
>
> Choose whether to allow non-admins to invite new people to *ASF*.
>
>  Allow everyone (except guests) to invite new members.
> 
>
> I can't see why we'd have an issue there, so I'm planning to turn that
> checkbox on at the end of next week (Thursday or whenever I remember to
> after that :) ).
>
> If this is a bad idea, please object and let me know why :)
>
> Hen
>

Re: [LAZY] Letting anyone invite on Slack

[Wade Chandler]

We do this with ours:

https://netbeans.signup.team

The Slack guys are the ones who even told us to. There is no theoretical
limit according to them. You just have to manage the outstanding invites,
and clean them up if there are a bunch where folks did not finish out the
process. If you do not, then invites won't work until you do after some
critical mass.

We also use a bot to do this, which the Slack folks recommended us do:
https://netbeans.slackarchive.io

There are probably some OSS bots ASF could use to do this and other things
for such systems to keep full data logs inside ASF; own the data forever.

We also have a channel linked to our IRC channel where we can monitor and
help with it from Slack.

Anyways, it all seems to work great so far.

Thanks

Wade


On Oct 13, 2017 23:52, "Henri Yandell" <bay...@apache.org> wrote:

Currently only 'admins' can invite people to the ASF Slack:

  https://the-asf.slack.com/

If we view it as an IRC equivalent, having to invite people at all is
weird. We can, via a checkbox, change it so anyone on the ASF Slack (except
'guests') can invite someone to the Slack workspace:



Invitations

Choose whether to allow non-admins to invite new people to *ASF*.

 Allow everyone (except guests) to invite new members.


I can't see why we'd have an issue there, so I'm planning to turn that
checkbox on at the end of next week (Thursday or whenever I remember to
after that :) ).

If this is a bad idea, please object and let me know why :)

Hen

Re: [LAZY] Letting anyone invite on Slack

[Greg Stein]

Fair enough... then open it up. Not even sure why that's a question :-)

On Sat, Oct 14, 2017 at 1:52 AM, Hen <bay...@apache.org> wrote:

> While I lean to the 'not seeing the value of Slack', we have many channels
> on Slack now (mostly driven by Incubator projects I think; John seems to
> have taken the lead on the workspace), so this isn't a thread for getting
> rid of slack :)
>
> Hen
>
> On Fri, Oct 13, 2017 at 11:06 PM, Craig Russell <apache@gmail.com>
> wrote:
>
> > Hi Henri,
> >
> > We tried to use slack with the Juneau project and never got it to work
> > "the Apache Way". Inviting people instead of self-service, no ability to
> > monitor discussions, no archive of discussions.
> >
> > We gave up and now use the wiki whenever mail doesn't serve. Common
> > editing of documents, diagrams, etc. are all easily done on confluence
> > where email doesn't allow sharing documents.
> >
> > I frankly do not see slack filling a need here.
> >
> > Craig
> >
> > > On Oct 13, 2017, at 9:51 PM, Henri Yandell <bay...@apache.org> wrote:
> > >
> > > Currently only 'admins' can invite people to the ASF Slack:
> > >
> > >  https://the-asf.slack.com/
> > >
> > > If we view it as an IRC equivalent, having to invite people at all is
> > > weird. We can, via a checkbox, change it so anyone on the ASF Slack
> > (except
> > > 'guests') can invite someone to the Slack workspace:
> > >
> > > 
> > >
> > > Invitations
> > >
> > > Choose whether to allow non-admins to invite new people to *ASF*.
> > >
> > > Allow everyone (except guests) to invite new members.
> > > 
> > >
> > > I can't see why we'd have an issue there, so I'm planning to turn that
> > > checkbox on at the end of next week (Thursday or whenever I remember to
> > > after that :) ).
> > >
> > > If this is a bad idea, please object and let me know why :)
> > >
> > > Hen
> >
> > Craig L Russell
> > c...@apache.org
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [LAZY] Letting anyone invite on Slack

[Hen]

While I lean to the 'not seeing the value of Slack', we have many channels
on Slack now (mostly driven by Incubator projects I think; John seems to
have taken the lead on the workspace), so this isn't a thread for getting
rid of slack :)

Hen

On Fri, Oct 13, 2017 at 11:06 PM, Craig Russell <apache@gmail.com>
wrote:

> Hi Henri,
>
> We tried to use slack with the Juneau project and never got it to work
> "the Apache Way". Inviting people instead of self-service, no ability to
> monitor discussions, no archive of discussions.
>
> We gave up and now use the wiki whenever mail doesn't serve. Common
> editing of documents, diagrams, etc. are all easily done on confluence
> where email doesn't allow sharing documents.
>
> I frankly do not see slack filling a need here.
>
> Craig
>
> > On Oct 13, 2017, at 9:51 PM, Henri Yandell <bay...@apache.org> wrote:
> >
> > Currently only 'admins' can invite people to the ASF Slack:
> >
> >  https://the-asf.slack.com/
> >
> > If we view it as an IRC equivalent, having to invite people at all is
> > weird. We can, via a checkbox, change it so anyone on the ASF Slack
> (except
> > 'guests') can invite someone to the Slack workspace:
> >
> > 
> >
> > Invitations
> >
> > Choose whether to allow non-admins to invite new people to *ASF*.
> >
> > Allow everyone (except guests) to invite new members.
> > 
> >
> > I can't see why we'd have an issue there, so I'm planning to turn that
> > checkbox on at the end of next week (Thursday or whenever I remember to
> > after that :) ).
> >
> > If this is a bad idea, please object and let me know why :)
> >
> > Hen
>
> Craig L Russell
> c...@apache.org
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [LAZY] Letting anyone invite on Slack

[Craig Russell]

Hi Henri,

We tried to use slack with the Juneau project and never got it to work "the 
Apache Way". Inviting people instead of self-service, no ability to monitor 
discussions, no archive of discussions. 

We gave up and now use the wiki whenever mail doesn't serve. Common editing of 
documents, diagrams, etc. are all easily done on confluence where email doesn't 
allow sharing documents.

I frankly do not see slack filling a need here.

Craig

> On Oct 13, 2017, at 9:51 PM, Henri Yandell <bay...@apache.org> wrote:
> 
> Currently only 'admins' can invite people to the ASF Slack:
> 
>  https://the-asf.slack.com/
> 
> If we view it as an IRC equivalent, having to invite people at all is
> weird. We can, via a checkbox, change it so anyone on the ASF Slack (except
> 'guests') can invite someone to the Slack workspace:
> 
> 
> 
> Invitations
> 
> Choose whether to allow non-admins to invite new people to *ASF*.
> 
> Allow everyone (except guests) to invite new members.
> 
> 
> I can't see why we'd have an issue there, so I'm planning to turn that
> checkbox on at the end of next week (Thursday or whenever I remember to
> after that :) ).
> 
> If this is a bad idea, please object and let me know why :)
> 
> Hen

Craig L Russell
c...@apache.org


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[LAZY] Letting anyone invite on Slack

[Henri Yandell]

Currently only 'admins' can invite people to the ASF Slack:

  https://the-asf.slack.com/

If we view it as an IRC equivalent, having to invite people at all is
weird. We can, via a checkbox, change it so anyone on the ASF Slack (except
'guests') can invite someone to the Slack workspace:



Invitations

Choose whether to allow non-admins to invite new people to *ASF*.

 Allow everyone (except guests) to invite new members.


I can't see why we'd have an issue there, so I'm planning to turn that
checkbox on at the end of next week (Thursday or whenever I remember to
after that :) ).

If this is a bad idea, please object and let me know why :)

Hen

Policies with respect to slack/github

[Sebastian Schelter]

Hi,

I'm a mentor of MXNet and one of the things I plan to address is how to
integrate development via github and communication via slack with Apache's
more established infrastructure (mailinglists + apache's git). Is there an
official policy or recommendation of best practices on how to setup such an
integration? Do we know of another project, which successfully managed such
a transition/integration?

Best,
Sebastian

Re: Slack Invites

[Ted Dunning]

Jfdi in action.  Cool!

On Mar 29, 2017 6:55 AM, "John D. Ament" <johndam...@apache.org> wrote:

> All,
>
> Based on the on-going discussions, I decided to move ahead with a single
> organization for Slack.  I've opened up registrations to all @apache.org
> email addresses.  To get set up, please use https://the-asf.slack.com/
> signup to
> get your account up and running.
>
> Happy Slacking!
>
> John
>

Re: Slack support?

[Ted Dunning]

On Wed, Mar 29, 2017 at 10:53 AM, Roman Shaposhnik 
wrote:

> On Wed, Mar 29, 2017 at 10:32 AM, Ted Dunning 
> wrote:
> > Reference to the twitter account situation just recently. We luckily
> still
> > had access (I was the contact), but the risk was obvious. The admin email
> > is not private@i.a.o to remediate that.
>
> You meant now (as in "is now...") right?



Correct.  "is now private@i.a.o"

Thanks for the correction, sorry for the typo.

Re: Slack support?

[Roman Shaposhnik]

On Wed, Mar 29, 2017 at 10:32 AM, Ted Dunning  wrote:
> Reference to the twitter account situation just recently. We luckily still
> had access (I was the contact), but the risk was obvious. The admin email
> is not private@i.a.o to remediate that.

You meant now (as in "is now...") right?

Thanks,
Roman.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Slack support?

[Ted Dunning]

Reference to the twitter account situation just recently. We luckily still
had access (I was the contact), but the risk was obvious. The admin email
is not private@i.a.o to remediate that.



On Wed, Mar 29, 2017 at 7:44 AM, James Bognar <james.bog...@salesforce.com>
wrote:

> I apologize in advance for muddying the waters here with yet ANOTHER
> external tool suggestion, but I'd like to point out the existence of Quip.
> It's virtually identical to Slack in capabilities and look-and-feel, but
> also includes google-doc style docs and a Confluence-style collaborative
> environment.  The docs are especially suited for software development since
> you can embed code examples with automatic syntax highlighting.  I was
> skeptical at first, but I've been using it for a couple of months, and it's
> a REALLY easy tool to use (WAY easier than Confluence which is annoyingly
> buggy).  I was skeptical about yet another chat tool, but it really is a
> nice overall collaborative environment.
>
> https://quip.com/about/tour
>
> Quip is now owned by Salesforce which donates 1% of it's profits through
> free licensing/hosting of its products to non-profit organizations.  I'm
> confident that we could get free hosting for Apache.  And it really is an
> awesome product IMHO.
>
>
>
>
> On Wed, Mar 29, 2017 at 9:17 AM, John D. Ament <johndam...@apache.org>
> wrote:
>
> > On Wed, Mar 29, 2017 at 9:15 AM Bertrand Delacretaz <
> > bdelacre...@codeconsult.ch> wrote:
> >
> > > On Wed, Mar 29, 2017 at 1:29 PM, John D. Ament <johndam...@apache.org>
> > > wrote:
> > > > ...I wouldn't mind listing my name as a contact for such a need, and
> > > having
> > > > back ups on other email lists (e.g. creating a
> slack-ad...@apache.org
> > > list)..
> > >
> > > If this is about sharing credentials of an admin account, you can also
> > > encrpyt it with the keys of a number of trusted members and store it
> > > in a private svn area.
> > >
> > >
> > Yes & no.  There's no limit to the admin accounts, its more of a place to
> > be able to reset the account in case all of the admins disappear.
> >
> >
> > > -Bertrand
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
>
>
>
> --
> James Bognar
>

Re: Slack support?

[James Bognar]

I apologize in advance for muddying the waters here with yet ANOTHER
external tool suggestion, but I'd like to point out the existence of Quip.
It's virtually identical to Slack in capabilities and look-and-feel, but
also includes google-doc style docs and a Confluence-style collaborative
environment.  The docs are especially suited for software development since
you can embed code examples with automatic syntax highlighting.  I was
skeptical at first, but I've been using it for a couple of months, and it's
a REALLY easy tool to use (WAY easier than Confluence which is annoyingly
buggy).  I was skeptical about yet another chat tool, but it really is a
nice overall collaborative environment.

https://quip.com/about/tour

Quip is now owned by Salesforce which donates 1% of it's profits through
free licensing/hosting of its products to non-profit organizations.  I'm
confident that we could get free hosting for Apache.  And it really is an
awesome product IMHO.




On Wed, Mar 29, 2017 at 9:17 AM, John D. Ament <johndam...@apache.org>
wrote:

> On Wed, Mar 29, 2017 at 9:15 AM Bertrand Delacretaz <
> bdelacre...@codeconsult.ch> wrote:
>
> > On Wed, Mar 29, 2017 at 1:29 PM, John D. Ament <johndam...@apache.org>
> > wrote:
> > > ...I wouldn't mind listing my name as a contact for such a need, and
> > having
> > > back ups on other email lists (e.g. creating a slack-ad...@apache.org
> > list)..
> >
> > If this is about sharing credentials of an admin account, you can also
> > encrpyt it with the keys of a number of trusted members and store it
> > in a private svn area.
> >
> >
> Yes & no.  There's no limit to the admin accounts, its more of a place to
> be able to reset the account in case all of the admins disappear.
>
>
> > -Bertrand
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>



-- 
James Bognar

Slack Invites

[John D. Ament]

All,

Based on the on-going discussions, I decided to move ahead with a single
organization for Slack.  I've opened up registrations to all @apache.org
email addresses.  To get set up, please use https://the-asf.slack.com/signup to
get your account up and running.

Happy Slacking!

John

Re: Slack support?

[John D. Ament]

On Wed, Mar 29, 2017 at 9:15 AM Bertrand Delacretaz <
bdelacre...@codeconsult.ch> wrote:

> On Wed, Mar 29, 2017 at 1:29 PM, John D. Ament <johndam...@apache.org>
> wrote:
> > ...I wouldn't mind listing my name as a contact for such a need, and
> having
> > back ups on other email lists (e.g. creating a slack-ad...@apache.org
> list)..
>
> If this is about sharing credentials of an admin account, you can also
> encrpyt it with the keys of a number of trusted members and store it
> in a private svn area.
>
>
Yes & no.  There's no limit to the admin accounts, its more of a place to
be able to reset the account in case all of the admins disappear.


> -Bertrand
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Slack support?

[Bertrand Delacretaz]

On Wed, Mar 29, 2017 at 1:29 PM, John D. Ament <johndam...@apache.org> wrote:
> ...I wouldn't mind listing my name as a contact for such a need, and having
> back ups on other email lists (e.g. creating a slack-ad...@apache.org list)..

If this is about sharing credentials of an admin account, you can also
encrpyt it with the keys of a number of trusted members and store it
in a private svn area.

-Bertrand

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Slack support?

[Pierre Smits]

I suggest using the private@incubator.a.o (and if that is regarded to be
not secure enough involving the secretary of the ASF in this as the office
of the secretary will prevail longer than people might be in office as the
Chair of the Incubator PMC)

Best regards,

Pierre Smits

ORRTIZ.COM <http://www.orrtiz.com>
OFBiz based solutions & services

OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/

On Wed, Mar 29, 2017 at 1:29 PM, John D. Ament <johndam...@apache.org>
wrote:

> Ted,
>
> So far it looks like the key components are:
>
> - Registering the org
> - Creating a sign up page/setting up a valid domain name for emails.
>
> I would recommend the sign up is ASF committers only.  After that, its all
> automated (similar to hipchat). Assuming that we create a single org, and
> limit the automatic registrations to @apache.org then I think there's
> really not much extra administration effort.
>
> I wouldn't mind listing my name as a contact for such a need, and having
> back ups on other email lists (e.g. creating a slack-ad...@apache.org
> list)
>
> John
>
> On Tue, Mar 28, 2017 at 11:12 AM Ted Dunning <ted.dunn...@gmail.com>
> wrote:
>
> > A single org would be fine if we have foundation-wide buy-in and central
> > administration.
> >
> > We don't have that now, so individual organizations makes more sense.
> >
> >
> >
> > On Tue, Mar 28, 2017 at 5:03 AM, John D. Ament <johndam...@apache.org>
> > wrote:
> >
> > > I feel like its a bit different.  I would rather see one apache
> > > organization (and would expect users would see this as well).  I don't
> > mind
> > > if the call is to use separate accounts, but feel like it makes more
> > sense
> > > as a single organization.
> > >
> > > On Thu, Mar 23, 2017 at 1:56 AM Ted Dunning <ted.dunn...@gmail.com>
> > wrote:
> > >
> > > > If you have a podling who wants to use slack, have them register
> under
> > > > their podling name and deal with it. No impact on infra needed. It's
> > like
> > > > having yet another twitter account.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > On Wed, Mar 22, 2017 at 10:18 PM, Greg Stein <gst...@gmail.com>
> wrote:
> > > >
> > > > > On Wed, Mar 22, 2017 at 9:59 PM, Evan Hughes <
> wisebald...@apache.org
> > >
> > > > > wrote:
> > > > >
> > > > > > Another option could be asking infra to host a rocket.chat server
> > so
> > > we
> > > > > can
> > > > > > control the instances.
> > > > > >
> > > > >
> > > > > Sorry, Evan, but hosting a chat service is not an option for
> > > > > Infrastructure. That would be contrary to our work on consolidating
> > > > > services.
> > > > >
> > > > > We can have HipChat rooms for any/all projects. A simple Jira
> > request,
> > > > and
> > > > > you're all set.
> > > > >
> > > > > In short, the ASF is happy to have duplicative topics/projects
> > because
> > > > each
> > > > > community may approach a problem in different ways, with different
> > > > focuses.
> > > > > But our Infra resources are limited, so we can't/won't stand up
> > > duplicate
> > > > > services. And even better when they can be outsourced (like
> HipChat,
> > > and
> > > > > increasingly GitHub).
> > > > >
> > > > > Cheers,
> > > > > Greg Stein
> > > > > Infrastructure Administrator, ASF
> > > > >
> > > >
> > >
> >
>

Re: Slack support?

[John D. Ament]

Ted,

So far it looks like the key components are:

- Registering the org
- Creating a sign up page/setting up a valid domain name for emails.

I would recommend the sign up is ASF committers only.  After that, its all
automated (similar to hipchat). Assuming that we create a single org, and
limit the automatic registrations to @apache.org then I think there's
really not much extra administration effort.

I wouldn't mind listing my name as a contact for such a need, and having
back ups on other email lists (e.g. creating a slack-ad...@apache.org list)

John

On Tue, Mar 28, 2017 at 11:12 AM Ted Dunning <ted.dunn...@gmail.com> wrote:

> A single org would be fine if we have foundation-wide buy-in and central
> administration.
>
> We don't have that now, so individual organizations makes more sense.
>
>
>
> On Tue, Mar 28, 2017 at 5:03 AM, John D. Ament <johndam...@apache.org>
> wrote:
>
> > I feel like its a bit different.  I would rather see one apache
> > organization (and would expect users would see this as well).  I don't
> mind
> > if the call is to use separate accounts, but feel like it makes more
> sense
> > as a single organization.
> >
> > On Thu, Mar 23, 2017 at 1:56 AM Ted Dunning <ted.dunn...@gmail.com>
> wrote:
> >
> > > If you have a podling who wants to use slack, have them register under
> > > their podling name and deal with it. No impact on infra needed. It's
> like
> > > having yet another twitter account.
> > >
> > >
> > >
> > >
> > >
> > > On Wed, Mar 22, 2017 at 10:18 PM, Greg Stein <gst...@gmail.com> wrote:
> > >
> > > > On Wed, Mar 22, 2017 at 9:59 PM, Evan Hughes <wisebald...@apache.org
> >
> > > > wrote:
> > > >
> > > > > Another option could be asking infra to host a rocket.chat server
> so
> > we
> > > > can
> > > > > control the instances.
> > > > >
> > > >
> > > > Sorry, Evan, but hosting a chat service is not an option for
> > > > Infrastructure. That would be contrary to our work on consolidating
> > > > services.
> > > >
> > > > We can have HipChat rooms for any/all projects. A simple Jira
> request,
> > > and
> > > > you're all set.
> > > >
> > > > In short, the ASF is happy to have duplicative topics/projects
> because
> > > each
> > > > community may approach a problem in different ways, with different
> > > focuses.
> > > > But our Infra resources are limited, so we can't/won't stand up
> > duplicate
> > > > services. And even better when they can be outsourced (like HipChat,
> > and
> > > > increasingly GitHub).
> > > >
> > > > Cheers,
> > > > Greg Stein
> > > > Infrastructure Administrator, ASF
> > > >
> > >
> >
>

Re: Slack support?

[Ted Dunning]

A single org would be fine if we have foundation-wide buy-in and central
administration.

We don't have that now, so individual organizations makes more sense.



On Tue, Mar 28, 2017 at 5:03 AM, John D. Ament <johndam...@apache.org>
wrote:

> I feel like its a bit different.  I would rather see one apache
> organization (and would expect users would see this as well).  I don't mind
> if the call is to use separate accounts, but feel like it makes more sense
> as a single organization.
>
> On Thu, Mar 23, 2017 at 1:56 AM Ted Dunning <ted.dunn...@gmail.com> wrote:
>
> > If you have a podling who wants to use slack, have them register under
> > their podling name and deal with it. No impact on infra needed. It's like
> > having yet another twitter account.
> >
> >
> >
> >
> >
> > On Wed, Mar 22, 2017 at 10:18 PM, Greg Stein <gst...@gmail.com> wrote:
> >
> > > On Wed, Mar 22, 2017 at 9:59 PM, Evan Hughes <wisebald...@apache.org>
> > > wrote:
> > >
> > > > Another option could be asking infra to host a rocket.chat server so
> we
> > > can
> > > > control the instances.
> > > >
> > >
> > > Sorry, Evan, but hosting a chat service is not an option for
> > > Infrastructure. That would be contrary to our work on consolidating
> > > services.
> > >
> > > We can have HipChat rooms for any/all projects. A simple Jira request,
> > and
> > > you're all set.
> > >
> > > In short, the ASF is happy to have duplicative topics/projects because
> > each
> > > community may approach a problem in different ways, with different
> > focuses.
> > > But our Infra resources are limited, so we can't/won't stand up
> duplicate
> > > services. And even better when they can be outsourced (like HipChat,
> and
> > > increasingly GitHub).
> > >
> > > Cheers,
> > > Greg Stein
> > > Infrastructure Administrator, ASF
> > >
> >
>

Re: Slack

[Jean-Baptiste Onofré]

Hi Wade,

actually, we were right: the limit was due to number of pending invitation.

Discarding invitations helped.

Sorry about the noise.

Regards
JB

On 03/27/2017 05:32 PM, Wade Chandler wrote:

The 90 member thing is really odd to me. I think you should write Slack help to ask 
for details about your issue. The agreement does mention invites where people don’t 
accept, and too many of those, could reduce your ability to add more members, but 
this has been really rare in my experience, and we have way more for NetBeans, and 
other than perhaps 10 people, our over 300+ members were self invited using 
https://netbeans.signup.team/ <https://netbeans.signup.team/> Too, before I set 
all this up, one of the questions I specifically asked Slack was related to 
limitations, members, etc as it was a worry for us, and they said there is no real 
limit on the number of members, but did mention the message limits on logging etc, 
and directed us to setup a log bot while taking our request for some other OSS 
subscription models.

Hope it helps,

Wade




On Mar 27, 2017, at 01:37, Jean-Baptiste Onofré <j...@nanthrax.net> wrote:

Yes, but they will be member anyway, so it won't change the limit we have today 
(90), right ?

Regards
JB

On 03/27/2017 06:56 AM, Yaniv Rodenski wrote:

Hi JB,

A common practice/hack is to create a small web app that allows people to
send themselves invitations using the Slack API.
For example:
http://www.skill-space.com/blog/2015/11/16/create-an-auto-invite-channel-using-slack-heroku1

Cheers,
Yaniv


On Mon, 27 Mar 2017 at 3:40 pm, Jean-Baptiste Onofré <j...@nanthrax.net>
wrote:


Hi Wade,

You are right: invite people on Slack means adding them as member.

However, how can we accept Slack participants without inviting them ? Is it
possible ?

Thanks !
Regards
JB

On 03/26/2017 07:05 PM, Wade Chandler wrote:

My understanding is there isn’t a max limit on Slack for users for free,

and I have confirmed this with Slack there is not supposed to be a
limitation on numbers of members. NetBeans for instance has 320 members.
Did someone tell you this or did you run into some issue? If so, you might
write them to ask what is the deal.. It could be the difference in setup;
we use a registration page which sends invitations
https://netbeans.signup.team/ <https://netbeans.signup.team/> and is
using bots from https://stacktodo.com/ <https://stacktodo.com/> Or, it
could be something about when it was setup and differences in plans over
time.


It doesn’t change the limits on the log and file storage, but we explain

to folks it is for ephemeral real time communication and never to be
considered historic, but we are looking into setting up a log bot which
Slack personnel told us could also be helpful for OSS use. Slack said they
don’t have plans for more features for OSS specific projects at the moment
as one request from us was they make some new individual/personal low pay
option which could help communities with dedicated membership to pay for
their own personal use, but they said no plans at this time, but would take
it into consideration as an idea.


Thanks,

Wade



On Mar 26, 2017, at 01:58, Jean-Baptiste Onofré <j...@nanthrax.net>

wrote:


Hi,

Slack is very convenient for quick communication, but clearly, it

doesn't change that the mailing list is the first communication channel. If
discussions happen on Slack, minute notes/discussion has to be forwarded on
the mailing list.


I wonder if we plan to ask for some "pro" Slack account for Apache

projects (as we have license for IntelliJ for example). Now, at Apache
Beam, we reached the max capacity of the Slack free version (90 Slack users
on Beam channel and limited history). We already received new member
request that we can't accept for now.


Thoughts ?

Regards
JB

On 03/22/2017 10:37 PM, Craig Russell wrote:

Hi James,

There was a pretty extensive discussion on the netbeans dev list. I’d

encourage you to review this thread https://lists.apache.org/thread.html/
2dce365d03334c82d31b12c8b3dcad1a925a2f71af75658b8d8a5a07@%
3Cdev.netbeans.apache.org%3E


You can get all of the messages in the thread by doing a quick search

for “slack” on the d...@netbeans.apache.org list in lists.apache.org.


My takeaway is that Slack not a substitute for email. But it is useful

for ping-pong communication when people are in the heat of development.


But no decisions are made on Slack, and any discussion there (aside

from “add a semicolon there” and “let’s get lunch") needs to be brought
back to the dev list.


The underlying principle is that “if it didn’t happen on dev, then it

didn’t happen”. We strive for open, inclusive communications at Apache and
that means attempting to encourage participation by everyone who wants to,
regardless of primary language, time zone, and availability of tools. (We
assume everyone has a device that handles email clients).


Hope this helps.

Craig

Re: Slack support?

[John D. Ament]

I feel like its a bit different.  I would rather see one apache
organization (and would expect users would see this as well).  I don't mind
if the call is to use separate accounts, but feel like it makes more sense
as a single organization.

On Thu, Mar 23, 2017 at 1:56 AM Ted Dunning <ted.dunn...@gmail.com> wrote:

> If you have a podling who wants to use slack, have them register under
> their podling name and deal with it. No impact on infra needed. It's like
> having yet another twitter account.
>
>
>
>
>
> On Wed, Mar 22, 2017 at 10:18 PM, Greg Stein <gst...@gmail.com> wrote:
>
> > On Wed, Mar 22, 2017 at 9:59 PM, Evan Hughes <wisebald...@apache.org>
> > wrote:
> >
> > > Another option could be asking infra to host a rocket.chat server so we
> > can
> > > control the instances.
> > >
> >
> > Sorry, Evan, but hosting a chat service is not an option for
> > Infrastructure. That would be contrary to our work on consolidating
> > services.
> >
> > We can have HipChat rooms for any/all projects. A simple Jira request,
> and
> > you're all set.
> >
> > In short, the ASF is happy to have duplicative topics/projects because
> each
> > community may approach a problem in different ways, with different
> focuses.
> > But our Infra resources are limited, so we can't/won't stand up duplicate
> > services. And even better when they can be outsourced (like HipChat, and
> > increasingly GitHub).
> >
> > Cheers,
> > Greg Stein
> > Infrastructure Administrator, ASF
> >
>

Re: Slack

[Greg Stein]

Phil,

Tools are very different from what the ASF *produces* ... tools are just a
mechanism to assist the community. Choose the right tools, and move on. If
the community likes them, then what does it matter what the license is? I
recognize some people want OSS tools for their entire stack, but the
Foundation has decided to be pragmatic about its tool choices, and to use
donated tools/licenses to stretch our donated dollars further.

If you would like to *run* a chat tool, then go ahead, and invite any/all
communities to use it. Excellent. The Foundation clearly allows its
communities to use external tools, to support those communities. But I will
state that the ASF will not be standing up a chat tool. We have a HipChat
open source community license available, and will provide Rooms for any
project that needs one. And that means we don't have to maintain it.

Cheers,
Greg Stein
Infrastructure Administrator, ASF


On Mon, Mar 27, 2017 at 11:57 AM, Phillip Rhodes <motley.crue@gmail.com>
wrote:

> I don't understand the desire to use a closed-source, proprietary,
> locked-down walled-garden application like Slack to begin with.   Why
> not use one of the several open-source look-a-like versions that are
> available?  Or use Gitter, which is about to go Open Source[1].
>
> [1]: https://venturebeat.com/2017/03/15/gitlab-acquires-
> software-chat-startup-gitter-will-open-source-the-code/
>
>
> Phil
> This message optimized for indexing by NSA PRISM
>
>
> On Mon, Mar 27, 2017 at 11:32 AM, Wade Chandler <wadechand...@apache.org>
> wrote:
> > The 90 member thing is really odd to me. I think you should write Slack
> help to ask for details about your issue. The agreement does mention
> invites where people don’t accept, and too many of those, could reduce your
> ability to add more members, but this has been really rare in my
> experience, and we have way more for NetBeans, and other than perhaps 10
> people, our over 300+ members were self invited using
> https://netbeans.signup.team/ <https://netbeans.signup.team/> Too, before
> I set all this up, one of the questions I specifically asked Slack was
> related to limitations, members, etc as it was a worry for us, and they
> said there is no real limit on the number of members, but did mention the
> message limits on logging etc, and directed us to setup a log bot while
> taking our request for some other OSS subscription models.
> >
> > Hope it helps,
> >
> > Wade
> >
> >
> >
> >> On Mar 27, 2017, at 01:37, Jean-Baptiste Onofré <j...@nanthrax.net>
> wrote:
> >>
> >> Yes, but they will be member anyway, so it won't change the limit we
> have today (90), right ?
> >>
> >> Regards
> >> JB
> >>
> >> On 03/27/2017 06:56 AM, Yaniv Rodenski wrote:
> >>> Hi JB,
> >>>
> >>> A common practice/hack is to create a small web app that allows people
> to
> >>> send themselves invitations using the Slack API.
> >>> For example:
> >>> http://www.skill-space.com/blog/2015/11/16/create-an-
> auto-invite-channel-using-slack-heroku1
> >>>
> >>> Cheers,
> >>> Yaniv
> >>>
> >>>
> >>> On Mon, 27 Mar 2017 at 3:40 pm, Jean-Baptiste Onofré <j...@nanthrax.net>
> >>> wrote:
> >>>
> >>>> Hi Wade,
> >>>>
> >>>> You are right: invite people on Slack means adding them as member.
> >>>>
> >>>> However, how can we accept Slack participants without inviting them ?
> Is it
> >>>> possible ?
> >>>>
> >>>> Thanks !
> >>>> Regards
> >>>> JB
> >>>>
> >>>> On 03/26/2017 07:05 PM, Wade Chandler wrote:
> >>>>> My understanding is there isn’t a max limit on Slack for users for
> free,
> >>>> and I have confirmed this with Slack there is not supposed to be a
> >>>> limitation on numbers of members. NetBeans for instance has 320
> members.
> >>>> Did someone tell you this or did you run into some issue? If so, you
> might
> >>>> write them to ask what is the deal.. It could be the difference in
> setup;
> >>>> we use a registration page which sends invitations
> >>>> https://netbeans.signup.team/ <https://netbeans.signup.team/> and is
> >>>> using bots from https://stacktodo.com/ <https://stacktodo.com/> Or,
> it
> >>>> could be something about when it was setup and differences in plans
> over
> >>>> time.
> >>>>>
> >

Re: Slack

[Ted Dunning]

Slack works incredibly well is the basic reason. Some of the aspect that
work well include:

- very effective UI

- great integration with email so that i hear about messages that I didn't
seem to see

- great notification. An alert appears on the platform I am using. That is,
I hear clicks on my laptop or a tone on my phone depending on which I am
using, but I don't hear notifications from every platform I *might* be
using. That means that when a notification happens I tend to actually hear
it rather than tuning it out.

- great sonic UI. The sounds are distinctive and penetrate cluttered
soundscapes well without being painful.

It may be that any given person doesn't care, but this sort of UI driven
discussion often comes up an not uncommonly comes out in favor of non open
alternatives. I try gimp again every few years, but every time I have done
it, I go back to photoshop due to quality of results and productivity. I
occasionally check out alternatives to IntelliJ, but they keep making it
better and more multi-lingual and more useful.

Where commercial products really are better, using them is a fine choice.
But I really do think that commercial vendors have to keep jumping the bar
set by OSS and they (we, actually) have to clear that bar and more.


(obligatory note: I work for a company that makes software that we sell.
The revenues from that pay for my groceries)



On Mon, Mar 27, 2017 at 4:07 PM, Edward Capriolo <edlinuxg...@gmail.com>
wrote:

> On Mon, Mar 27, 2017 at 3:08 PM, Wade Chandler <wadechand...@apache.org>
> wrote:
>
> > I have used Gitter; not a good product honestly; not really comparable.
> IRC
> > has limitations in the editing and group experience. The others require
> > keeping up infrastructure. Slack just works, and works well for what it
> > does. Some of us in the NB community discussed these points while setting
> > it up and choosing. Too, they have been letting communities use it for
> free
> > a long time. We use Atlassian products too, but don't get me going on
> > hipchat differences; one of which is the sed like comment editing
> oddness.
> >
> > Thanks
> >
> > Wade
> >
> > On Mar 27, 2017 12:57 PM, "Phillip Rhodes" <motley.crue@gmail.com>
> > wrote:
> >
> > > I don't understand the desire to use a closed-source, proprietary,
> > > locked-down walled-garden application like Slack to begin with.   Why
> > > not use one of the several open-source look-a-like versions that are
> > > available?  Or use Gitter, which is about to go Open Source[1].
> > >
> > > [1]: https://venturebeat.com/2017/03/15/gitlab-acquires-
> > > software-chat-startup-gitter-will-open-source-the-code/
> > >
> > >
> > > Phil
> > > This message optimized for indexing by NSA PRISM
> > >
> > >
> > > On Mon, Mar 27, 2017 at 11:32 AM, Wade Chandler <
> wadechand...@apache.org
> > >
> > > wrote:
> > > > The 90 member thing is really odd to me. I think you should write
> Slack
> > > help to ask for details about your issue. The agreement does mention
> > > invites where people don’t accept, and too many of those, could reduce
> > your
> > > ability to add more members, but this has been really rare in my
> > > experience, and we have way more for NetBeans, and other than perhaps
> 10
> > > people, our over 300+ members were self invited using
> > > https://netbeans.signup.team/ <https://netbeans.signup.team/> Too,
> > before
> > > I set all this up, one of the questions I specifically asked Slack was
> > > related to limitations, members, etc as it was a worry for us, and they
> > > said there is no real limit on the number of members, but did mention
> the
> > > message limits on logging etc, and directed us to setup a log bot while
> > > taking our request for some other OSS subscription models.
> > > >
> > > > Hope it helps,
> > > >
> > > > Wade
> > > >
> > > >
> > > >
> > > >> On Mar 27, 2017, at 01:37, Jean-Baptiste Onofré <j...@nanthrax.net>
> > > wrote:
> > > >>
> > > >> Yes, but they will be member anyway, so it won't change the limit we
> > > have today (90), right ?
> > > >>
> > > >> Regards
> > > >> JB
> > > >>
> > > >> On 03/27/2017 06:56 AM, Yaniv Rodenski wrote:
> > > >>> Hi JB,
> > > >>>
> > > >>> A common practice/hack is to create a small web app that allows
> > people
> > > to

Re: Slack

[Edward Capriolo]

On Mon, Mar 27, 2017 at 3:08 PM, Wade Chandler <wadechand...@apache.org>
wrote:

> I have used Gitter; not a good product honestly; not really comparable. IRC
> has limitations in the editing and group experience. The others require
> keeping up infrastructure. Slack just works, and works well for what it
> does. Some of us in the NB community discussed these points while setting
> it up and choosing. Too, they have been letting communities use it for free
> a long time. We use Atlassian products too, but don't get me going on
> hipchat differences; one of which is the sed like comment editing oddness.
>
> Thanks
>
> Wade
>
> On Mar 27, 2017 12:57 PM, "Phillip Rhodes" <motley.crue@gmail.com>
> wrote:
>
> > I don't understand the desire to use a closed-source, proprietary,
> > locked-down walled-garden application like Slack to begin with.   Why
> > not use one of the several open-source look-a-like versions that are
> > available?  Or use Gitter, which is about to go Open Source[1].
> >
> > [1]: https://venturebeat.com/2017/03/15/gitlab-acquires-
> > software-chat-startup-gitter-will-open-source-the-code/
> >
> >
> > Phil
> > This message optimized for indexing by NSA PRISM
> >
> >
> > On Mon, Mar 27, 2017 at 11:32 AM, Wade Chandler <wadechand...@apache.org
> >
> > wrote:
> > > The 90 member thing is really odd to me. I think you should write Slack
> > help to ask for details about your issue. The agreement does mention
> > invites where people don’t accept, and too many of those, could reduce
> your
> > ability to add more members, but this has been really rare in my
> > experience, and we have way more for NetBeans, and other than perhaps 10
> > people, our over 300+ members were self invited using
> > https://netbeans.signup.team/ <https://netbeans.signup.team/> Too,
> before
> > I set all this up, one of the questions I specifically asked Slack was
> > related to limitations, members, etc as it was a worry for us, and they
> > said there is no real limit on the number of members, but did mention the
> > message limits on logging etc, and directed us to setup a log bot while
> > taking our request for some other OSS subscription models.
> > >
> > > Hope it helps,
> > >
> > > Wade
> > >
> > >
> > >
> > >> On Mar 27, 2017, at 01:37, Jean-Baptiste Onofré <j...@nanthrax.net>
> > wrote:
> > >>
> > >> Yes, but they will be member anyway, so it won't change the limit we
> > have today (90), right ?
> > >>
> > >> Regards
> > >> JB
> > >>
> > >> On 03/27/2017 06:56 AM, Yaniv Rodenski wrote:
> > >>> Hi JB,
> > >>>
> > >>> A common practice/hack is to create a small web app that allows
> people
> > to
> > >>> send themselves invitations using the Slack API.
> > >>> For example:
> > >>> http://www.skill-space.com/blog/2015/11/16/create-an-
> > auto-invite-channel-using-slack-heroku1
> > >>>
> > >>> Cheers,
> > >>> Yaniv
> > >>>
> > >>>
> > >>> On Mon, 27 Mar 2017 at 3:40 pm, Jean-Baptiste Onofré <
> j...@nanthrax.net>
> > >>> wrote:
> > >>>
> > >>>> Hi Wade,
> > >>>>
> > >>>> You are right: invite people on Slack means adding them as member.
> > >>>>
> > >>>> However, how can we accept Slack participants without inviting them
> ?
> > Is it
> > >>>> possible ?
> > >>>>
> > >>>> Thanks !
> > >>>> Regards
> > >>>> JB
> > >>>>
> > >>>> On 03/26/2017 07:05 PM, Wade Chandler wrote:
> > >>>>> My understanding is there isn’t a max limit on Slack for users for
> > free,
> > >>>> and I have confirmed this with Slack there is not supposed to be a
> > >>>> limitation on numbers of members. NetBeans for instance has 320
> > members.
> > >>>> Did someone tell you this or did you run into some issue? If so, you
> > might
> > >>>> write them to ask what is the deal.. It could be the difference in
> > setup;
> > >>>> we use a registration page which sends invitations
> > >>>> https://netbeans.signup.team/ <https://netbeans.signup.team/> and
> is
> > >>>> using bots from ht

Re: Slack

[Carlos Santana]

I use Slack everyday internally for my work. 
I like Slack and the fact that I can use one tool for open source and internal 
company things. 

Apache Cordova (1400 members)and Apache Incubating OpenWhisk (175 members) both 
use Slack there is no limit on number of users and there is an open invite from 
the website from both projects. 

PS: I also use Slack for Ionic open source project with 3000 members also free 
tier. 

- Carlos Santana
@csantanapr

> On Mar 27, 2017, at 3:08 PM, Wade Chandler <wadechand...@apache.org> wrote:
> 
> I have used Gitter; not a good product honestly; not really comparable. IRC
> has limitations in the editing and group experience. The others require
> keeping up infrastructure. Slack just works, and works well for what it
> does. Some of us in the NB community discussed these points while setting
> it up and choosing. Too, they have been letting communities use it for free
> a long time. We use Atlassian products too, but don't get me going on
> hipchat differences; one of which is the sed like comment editing oddness.
> 
> Thanks
> 
> Wade
> 
> On Mar 27, 2017 12:57 PM, "Phillip Rhodes" <motley.crue@gmail.com>
> wrote:
> 
>> I don't understand the desire to use a closed-source, proprietary,
>> locked-down walled-garden application like Slack to begin with.   Why
>> not use one of the several open-source look-a-like versions that are
>> available?  Or use Gitter, which is about to go Open Source[1].
>> 
>> [1]: https://venturebeat.com/2017/03/15/gitlab-acquires-
>> software-chat-startup-gitter-will-open-source-the-code/
>> 
>> 
>> Phil
>> This message optimized for indexing by NSA PRISM
>> 
>> 
>> On Mon, Mar 27, 2017 at 11:32 AM, Wade Chandler <wadechand...@apache.org>
>> wrote:
>>> The 90 member thing is really odd to me. I think you should write Slack
>> help to ask for details about your issue. The agreement does mention
>> invites where people don’t accept, and too many of those, could reduce your
>> ability to add more members, but this has been really rare in my
>> experience, and we have way more for NetBeans, and other than perhaps 10
>> people, our over 300+ members were self invited using
>> https://netbeans.signup.team/ <https://netbeans.signup.team/> Too, before
>> I set all this up, one of the questions I specifically asked Slack was
>> related to limitations, members, etc as it was a worry for us, and they
>> said there is no real limit on the number of members, but did mention the
>> message limits on logging etc, and directed us to setup a log bot while
>> taking our request for some other OSS subscription models.
>>> 
>>> Hope it helps,
>>> 
>>> Wade
>>> 
>>> 
>>> 
>>>> On Mar 27, 2017, at 01:37, Jean-Baptiste Onofré <j...@nanthrax.net>
>> wrote:
>>>> 
>>>> Yes, but they will be member anyway, so it won't change the limit we
>> have today (90), right ?
>>>> 
>>>> Regards
>>>> JB
>>>> 
>>>>> On 03/27/2017 06:56 AM, Yaniv Rodenski wrote:
>>>>> Hi JB,
>>>>> 
>>>>> A common practice/hack is to create a small web app that allows people
>> to
>>>>> send themselves invitations using the Slack API.
>>>>> For example:
>>>>> http://www.skill-space.com/blog/2015/11/16/create-an-
>> auto-invite-channel-using-slack-heroku1
>>>>> 
>>>>> Cheers,
>>>>> Yaniv
>>>>> 
>>>>> 
>>>>> On Mon, 27 Mar 2017 at 3:40 pm, Jean-Baptiste Onofré <j...@nanthrax.net>
>>>>> wrote:
>>>>> 
>>>>>> Hi Wade,
>>>>>> 
>>>>>> You are right: invite people on Slack means adding them as member.
>>>>>> 
>>>>>> However, how can we accept Slack participants without inviting them ?
>> Is it
>>>>>> possible ?
>>>>>> 
>>>>>> Thanks !
>>>>>> Regards
>>>>>> JB
>>>>>> 
>>>>>>> On 03/26/2017 07:05 PM, Wade Chandler wrote:
>>>>>>> My understanding is there isn’t a max limit on Slack for users for
>> free,
>>>>>> and I have confirmed this with Slack there is not supposed to be a
>>>>>> limitation on numbers of members. NetBeans for instance has 320
>> members.
>>>>>> Did someone tell you this or did you run into some issue? If so, you
>> might

Re: Slack

[Wade Chandler]

I have used Gitter; not a good product honestly; not really comparable. IRC
has limitations in the editing and group experience. The others require
keeping up infrastructure. Slack just works, and works well for what it
does. Some of us in the NB community discussed these points while setting
it up and choosing. Too, they have been letting communities use it for free
a long time. We use Atlassian products too, but don't get me going on
hipchat differences; one of which is the sed like comment editing oddness.

Thanks

Wade

On Mar 27, 2017 12:57 PM, "Phillip Rhodes" <motley.crue@gmail.com>
wrote:

> I don't understand the desire to use a closed-source, proprietary,
> locked-down walled-garden application like Slack to begin with.   Why
> not use one of the several open-source look-a-like versions that are
> available?  Or use Gitter, which is about to go Open Source[1].
>
> [1]: https://venturebeat.com/2017/03/15/gitlab-acquires-
> software-chat-startup-gitter-will-open-source-the-code/
>
>
> Phil
> This message optimized for indexing by NSA PRISM
>
>
> On Mon, Mar 27, 2017 at 11:32 AM, Wade Chandler <wadechand...@apache.org>
> wrote:
> > The 90 member thing is really odd to me. I think you should write Slack
> help to ask for details about your issue. The agreement does mention
> invites where people don’t accept, and too many of those, could reduce your
> ability to add more members, but this has been really rare in my
> experience, and we have way more for NetBeans, and other than perhaps 10
> people, our over 300+ members were self invited using
> https://netbeans.signup.team/ <https://netbeans.signup.team/> Too, before
> I set all this up, one of the questions I specifically asked Slack was
> related to limitations, members, etc as it was a worry for us, and they
> said there is no real limit on the number of members, but did mention the
> message limits on logging etc, and directed us to setup a log bot while
> taking our request for some other OSS subscription models.
> >
> > Hope it helps,
> >
> > Wade
> >
> >
> >
> >> On Mar 27, 2017, at 01:37, Jean-Baptiste Onofré <j...@nanthrax.net>
> wrote:
> >>
> >> Yes, but they will be member anyway, so it won't change the limit we
> have today (90), right ?
> >>
> >> Regards
> >> JB
> >>
> >> On 03/27/2017 06:56 AM, Yaniv Rodenski wrote:
> >>> Hi JB,
> >>>
> >>> A common practice/hack is to create a small web app that allows people
> to
> >>> send themselves invitations using the Slack API.
> >>> For example:
> >>> http://www.skill-space.com/blog/2015/11/16/create-an-
> auto-invite-channel-using-slack-heroku1
> >>>
> >>> Cheers,
> >>> Yaniv
> >>>
> >>>
> >>> On Mon, 27 Mar 2017 at 3:40 pm, Jean-Baptiste Onofré <j...@nanthrax.net>
> >>> wrote:
> >>>
> >>>> Hi Wade,
> >>>>
> >>>> You are right: invite people on Slack means adding them as member.
> >>>>
> >>>> However, how can we accept Slack participants without inviting them ?
> Is it
> >>>> possible ?
> >>>>
> >>>> Thanks !
> >>>> Regards
> >>>> JB
> >>>>
> >>>> On 03/26/2017 07:05 PM, Wade Chandler wrote:
> >>>>> My understanding is there isn’t a max limit on Slack for users for
> free,
> >>>> and I have confirmed this with Slack there is not supposed to be a
> >>>> limitation on numbers of members. NetBeans for instance has 320
> members.
> >>>> Did someone tell you this or did you run into some issue? If so, you
> might
> >>>> write them to ask what is the deal.. It could be the difference in
> setup;
> >>>> we use a registration page which sends invitations
> >>>> https://netbeans.signup.team/ <https://netbeans.signup.team/> and is
> >>>> using bots from https://stacktodo.com/ <https://stacktodo.com/> Or,
> it
> >>>> could be something about when it was setup and differences in plans
> over
> >>>> time.
> >>>>>
> >>>>> It doesn’t change the limits on the log and file storage, but we
> explain
> >>>> to folks it is for ephemeral real time communication and never to be
> >>>> considered historic, but we are looking into setting up a log bot
> which
> >>>> Slack personnel told us could also be helpful for OSS use. Slack said
> they
> >>

Re: Slack

[Phillip Rhodes]

I don't understand the desire to use a closed-source, proprietary,
locked-down walled-garden application like Slack to begin with.   Why
not use one of the several open-source look-a-like versions that are
available?  Or use Gitter, which is about to go Open Source[1].

[1]: 
https://venturebeat.com/2017/03/15/gitlab-acquires-software-chat-startup-gitter-will-open-source-the-code/


Phil
This message optimized for indexing by NSA PRISM


On Mon, Mar 27, 2017 at 11:32 AM, Wade Chandler <wadechand...@apache.org> wrote:
> The 90 member thing is really odd to me. I think you should write Slack help 
> to ask for details about your issue. The agreement does mention invites where 
> people don’t accept, and too many of those, could reduce your ability to add 
> more members, but this has been really rare in my experience, and we have way 
> more for NetBeans, and other than perhaps 10 people, our over 300+ members 
> were self invited using https://netbeans.signup.team/ 
> <https://netbeans.signup.team/> Too, before I set all this up, one of the 
> questions I specifically asked Slack was related to limitations, members, etc 
> as it was a worry for us, and they said there is no real limit on the number 
> of members, but did mention the message limits on logging etc, and directed 
> us to setup a log bot while taking our request for some other OSS 
> subscription models.
>
> Hope it helps,
>
> Wade
>
>
>
>> On Mar 27, 2017, at 01:37, Jean-Baptiste Onofré <j...@nanthrax.net> wrote:
>>
>> Yes, but they will be member anyway, so it won't change the limit we have 
>> today (90), right ?
>>
>> Regards
>> JB
>>
>> On 03/27/2017 06:56 AM, Yaniv Rodenski wrote:
>>> Hi JB,
>>>
>>> A common practice/hack is to create a small web app that allows people to
>>> send themselves invitations using the Slack API.
>>> For example:
>>> http://www.skill-space.com/blog/2015/11/16/create-an-auto-invite-channel-using-slack-heroku1
>>>
>>> Cheers,
>>> Yaniv
>>>
>>>
>>> On Mon, 27 Mar 2017 at 3:40 pm, Jean-Baptiste Onofré <j...@nanthrax.net>
>>> wrote:
>>>
>>>> Hi Wade,
>>>>
>>>> You are right: invite people on Slack means adding them as member.
>>>>
>>>> However, how can we accept Slack participants without inviting them ? Is it
>>>> possible ?
>>>>
>>>> Thanks !
>>>> Regards
>>>> JB
>>>>
>>>> On 03/26/2017 07:05 PM, Wade Chandler wrote:
>>>>> My understanding is there isn’t a max limit on Slack for users for free,
>>>> and I have confirmed this with Slack there is not supposed to be a
>>>> limitation on numbers of members. NetBeans for instance has 320 members.
>>>> Did someone tell you this or did you run into some issue? If so, you might
>>>> write them to ask what is the deal.. It could be the difference in setup;
>>>> we use a registration page which sends invitations
>>>> https://netbeans.signup.team/ <https://netbeans.signup.team/> and is
>>>> using bots from https://stacktodo.com/ <https://stacktodo.com/> Or, it
>>>> could be something about when it was setup and differences in plans over
>>>> time.
>>>>>
>>>>> It doesn’t change the limits on the log and file storage, but we explain
>>>> to folks it is for ephemeral real time communication and never to be
>>>> considered historic, but we are looking into setting up a log bot which
>>>> Slack personnel told us could also be helpful for OSS use. Slack said they
>>>> don’t have plans for more features for OSS specific projects at the moment
>>>> as one request from us was they make some new individual/personal low pay
>>>> option which could help communities with dedicated membership to pay for
>>>> their own personal use, but they said no plans at this time, but would take
>>>> it into consideration as an idea.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Wade
>>>>>
>>>>>
>>>>>> On Mar 26, 2017, at 01:58, Jean-Baptiste Onofré <j...@nanthrax.net>
>>>> wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> Slack is very convenient for quick communication, but clearly, it
>>>> doesn't change that the mailing list is the first communication channel. If
>>>> discussions happen on Slack, minute notes/discussion has to be forwarded o

Re: Slack

[Wade Chandler]

The 90 member thing is really odd to me. I think you should write Slack help to 
ask for details about your issue. The agreement does mention invites where 
people don’t accept, and too many of those, could reduce your ability to add 
more members, but this has been really rare in my experience, and we have way 
more for NetBeans, and other than perhaps 10 people, our over 300+ members were 
self invited using https://netbeans.signup.team/ 
<https://netbeans.signup.team/> Too, before I set all this up, one of the 
questions I specifically asked Slack was related to limitations, members, etc 
as it was a worry for us, and they said there is no real limit on the number of 
members, but did mention the message limits on logging etc, and directed us to 
setup a log bot while taking our request for some other OSS subscription models.

Hope it helps,

Wade



> On Mar 27, 2017, at 01:37, Jean-Baptiste Onofré <j...@nanthrax.net> wrote:
> 
> Yes, but they will be member anyway, so it won't change the limit we have 
> today (90), right ?
> 
> Regards
> JB
> 
> On 03/27/2017 06:56 AM, Yaniv Rodenski wrote:
>> Hi JB,
>> 
>> A common practice/hack is to create a small web app that allows people to
>> send themselves invitations using the Slack API.
>> For example:
>> http://www.skill-space.com/blog/2015/11/16/create-an-auto-invite-channel-using-slack-heroku1
>> 
>> Cheers,
>> Yaniv
>> 
>> 
>> On Mon, 27 Mar 2017 at 3:40 pm, Jean-Baptiste Onofré <j...@nanthrax.net>
>> wrote:
>> 
>>> Hi Wade,
>>> 
>>> You are right: invite people on Slack means adding them as member.
>>> 
>>> However, how can we accept Slack participants without inviting them ? Is it
>>> possible ?
>>> 
>>> Thanks !
>>> Regards
>>> JB
>>> 
>>> On 03/26/2017 07:05 PM, Wade Chandler wrote:
>>>> My understanding is there isn’t a max limit on Slack for users for free,
>>> and I have confirmed this with Slack there is not supposed to be a
>>> limitation on numbers of members. NetBeans for instance has 320 members.
>>> Did someone tell you this or did you run into some issue? If so, you might
>>> write them to ask what is the deal.. It could be the difference in setup;
>>> we use a registration page which sends invitations
>>> https://netbeans.signup.team/ <https://netbeans.signup.team/> and is
>>> using bots from https://stacktodo.com/ <https://stacktodo.com/> Or, it
>>> could be something about when it was setup and differences in plans over
>>> time.
>>>> 
>>>> It doesn’t change the limits on the log and file storage, but we explain
>>> to folks it is for ephemeral real time communication and never to be
>>> considered historic, but we are looking into setting up a log bot which
>>> Slack personnel told us could also be helpful for OSS use. Slack said they
>>> don’t have plans for more features for OSS specific projects at the moment
>>> as one request from us was they make some new individual/personal low pay
>>> option which could help communities with dedicated membership to pay for
>>> their own personal use, but they said no plans at this time, but would take
>>> it into consideration as an idea.
>>>> 
>>>> Thanks,
>>>> 
>>>> Wade
>>>> 
>>>> 
>>>>> On Mar 26, 2017, at 01:58, Jean-Baptiste Onofré <j...@nanthrax.net>
>>> wrote:
>>>>> 
>>>>> Hi,
>>>>> 
>>>>> Slack is very convenient for quick communication, but clearly, it
>>> doesn't change that the mailing list is the first communication channel. If
>>> discussions happen on Slack, minute notes/discussion has to be forwarded on
>>> the mailing list.
>>>>> 
>>>>> I wonder if we plan to ask for some "pro" Slack account for Apache
>>> projects (as we have license for IntelliJ for example). Now, at Apache
>>> Beam, we reached the max capacity of the Slack free version (90 Slack users
>>> on Beam channel and limited history). We already received new member
>>> request that we can't accept for now.
>>>>> 
>>>>> Thoughts ?
>>>>> 
>>>>> Regards
>>>>> JB
>>>>> 
>>>>> On 03/22/2017 10:37 PM, Craig Russell wrote:
>>>>>> Hi James,
>>>>>> 
>>>>>> There was a pretty extensive discussion on the netbeans dev list. I’d
>>> encourage you to review this thread h

Re: Slack

[Jean-Baptiste Onofré]

Yes, but they will be member anyway, so it won't change the limit we have today 
(90), right ?


Regards
JB

On 03/27/2017 06:56 AM, Yaniv Rodenski wrote:

Hi JB,

A common practice/hack is to create a small web app that allows people to
send themselves invitations using the Slack API.
For example:
http://www.skill-space.com/blog/2015/11/16/create-an-auto-invite-channel-using-slack-heroku1

Cheers,
Yaniv


On Mon, 27 Mar 2017 at 3:40 pm, Jean-Baptiste Onofré <j...@nanthrax.net>
wrote:


Hi Wade,

You are right: invite people on Slack means adding them as member.

However, how can we accept Slack participants without inviting them ? Is it
possible ?

Thanks !
Regards
JB

On 03/26/2017 07:05 PM, Wade Chandler wrote:

My understanding is there isn’t a max limit on Slack for users for free,

and I have confirmed this with Slack there is not supposed to be a
limitation on numbers of members. NetBeans for instance has 320 members.
Did someone tell you this or did you run into some issue? If so, you might
write them to ask what is the deal.. It could be the difference in setup;
we use a registration page which sends invitations
https://netbeans.signup.team/ <https://netbeans.signup.team/> and is
using bots from https://stacktodo.com/ <https://stacktodo.com/> Or, it
could be something about when it was setup and differences in plans over
time.


It doesn’t change the limits on the log and file storage, but we explain

to folks it is for ephemeral real time communication and never to be
considered historic, but we are looking into setting up a log bot which
Slack personnel told us could also be helpful for OSS use. Slack said they
don’t have plans for more features for OSS specific projects at the moment
as one request from us was they make some new individual/personal low pay
option which could help communities with dedicated membership to pay for
their own personal use, but they said no plans at this time, but would take
it into consideration as an idea.


Thanks,

Wade



On Mar 26, 2017, at 01:58, Jean-Baptiste Onofré <j...@nanthrax.net>

wrote:


Hi,

Slack is very convenient for quick communication, but clearly, it

doesn't change that the mailing list is the first communication channel. If
discussions happen on Slack, minute notes/discussion has to be forwarded on
the mailing list.


I wonder if we plan to ask for some "pro" Slack account for Apache

projects (as we have license for IntelliJ for example). Now, at Apache
Beam, we reached the max capacity of the Slack free version (90 Slack users
on Beam channel and limited history). We already received new member
request that we can't accept for now.


Thoughts ?

Regards
JB

On 03/22/2017 10:37 PM, Craig Russell wrote:

Hi James,

There was a pretty extensive discussion on the netbeans dev list. I’d

encourage you to review this thread https://lists.apache.org/thread.html/
2dce365d03334c82d31b12c8b3dcad1a925a2f71af75658b8d8a5a07@%
3Cdev.netbeans.apache.org%3E


You can get all of the messages in the thread by doing a quick search

for “slack” on the d...@netbeans.apache.org list in lists.apache.org.


My takeaway is that Slack not a substitute for email. But it is useful

for ping-pong communication when people are in the heat of development.


But no decisions are made on Slack, and any discussion there (aside

from “add a semicolon there” and “let’s get lunch") needs to be brought
back to the dev list.


The underlying principle is that “if it didn’t happen on dev, then it

didn’t happen”. We strive for open, inclusive communications at Apache and
that means attempting to encourage participation by everyone who wants to,
regardless of primary language, time zone, and availability of tools. (We
assume everyone has a device that handles email clients).


Hope this helps.

Craig


On Mar 22, 2017, at 1:27 PM, James Bognar <jamesbog...@apache.org>

wrote:


Can someone remind me?  I thought there was a discussion a couple of

months

ago about allowing incubator projects to use Slack for

communication.  What

was the final decision?


Craig L Russell
c...@apache.org









--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org






--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Slack

[Yaniv Rodenski]

Hi JB,

A common practice/hack is to create a small web app that allows people to
send themselves invitations using the Slack API.
For example:
http://www.skill-space.com/blog/2015/11/16/create-an-auto-invite-channel-using-slack-heroku1

Cheers,
Yaniv


On Mon, 27 Mar 2017 at 3:40 pm, Jean-Baptiste Onofré <j...@nanthrax.net>
wrote:

> Hi Wade,
>
> You are right: invite people on Slack means adding them as member.
>
> However, how can we accept Slack participants without inviting them ? Is it
> possible ?
>
> Thanks !
> Regards
> JB
>
> On 03/26/2017 07:05 PM, Wade Chandler wrote:
> > My understanding is there isn’t a max limit on Slack for users for free,
> and I have confirmed this with Slack there is not supposed to be a
> limitation on numbers of members. NetBeans for instance has 320 members.
> Did someone tell you this or did you run into some issue? If so, you might
> write them to ask what is the deal.. It could be the difference in setup;
> we use a registration page which sends invitations
> https://netbeans.signup.team/ <https://netbeans.signup.team/> and is
> using bots from https://stacktodo.com/ <https://stacktodo.com/> Or, it
> could be something about when it was setup and differences in plans over
> time.
> >
> > It doesn’t change the limits on the log and file storage, but we explain
> to folks it is for ephemeral real time communication and never to be
> considered historic, but we are looking into setting up a log bot which
> Slack personnel told us could also be helpful for OSS use. Slack said they
> don’t have plans for more features for OSS specific projects at the moment
> as one request from us was they make some new individual/personal low pay
> option which could help communities with dedicated membership to pay for
> their own personal use, but they said no plans at this time, but would take
> it into consideration as an idea.
> >
> > Thanks,
> >
> > Wade
> >
> >
> >> On Mar 26, 2017, at 01:58, Jean-Baptiste Onofré <j...@nanthrax.net>
> wrote:
> >>
> >> Hi,
> >>
> >> Slack is very convenient for quick communication, but clearly, it
> doesn't change that the mailing list is the first communication channel. If
> discussions happen on Slack, minute notes/discussion has to be forwarded on
> the mailing list.
> >>
> >> I wonder if we plan to ask for some "pro" Slack account for Apache
> projects (as we have license for IntelliJ for example). Now, at Apache
> Beam, we reached the max capacity of the Slack free version (90 Slack users
> on Beam channel and limited history). We already received new member
> request that we can't accept for now.
> >>
> >> Thoughts ?
> >>
> >> Regards
> >> JB
> >>
> >> On 03/22/2017 10:37 PM, Craig Russell wrote:
> >>> Hi James,
> >>>
> >>> There was a pretty extensive discussion on the netbeans dev list. I’d
> encourage you to review this thread https://lists.apache.org/thread.html/
> 2dce365d03334c82d31b12c8b3dcad1a925a2f71af75658b8d8a5a07@%
> 3Cdev.netbeans.apache.org%3E
> >>>
> >>> You can get all of the messages in the thread by doing a quick search
> for “slack” on the d...@netbeans.apache.org list in lists.apache.org.
> >>>
> >>> My takeaway is that Slack not a substitute for email. But it is useful
> for ping-pong communication when people are in the heat of development.
> >>>
> >>> But no decisions are made on Slack, and any discussion there (aside
> from “add a semicolon there” and “let’s get lunch") needs to be brought
> back to the dev list.
> >>>
> >>> The underlying principle is that “if it didn’t happen on dev, then it
> didn’t happen”. We strive for open, inclusive communications at Apache and
> that means attempting to encourage participation by everyone who wants to,
> regardless of primary language, time zone, and availability of tools. (We
> assume everyone has a device that handles email clients).
> >>>
> >>> Hope this helps.
> >>>
> >>> Craig
> >>>
> >>>> On Mar 22, 2017, at 1:27 PM, James Bognar <jamesbog...@apache.org>
> wrote:
> >>>>
> >>>> Can someone remind me?  I thought there was a discussion a couple of
> months
> >>>> ago about allowing incubator projects to use Slack for
> communication.  What
> >>>> was the final decision?
> >>>
> >>> Craig L Russell
> >>> c...@apache.org
> >>>
> >>>
> >>
> >
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Slack

[Jean-Baptiste Onofré]

Hi Wade,

You are right: invite people on Slack means adding them as member.

However, how can we accept Slack participants without inviting them ? Is it 
possible ?


Thanks !
Regards
JB

On 03/26/2017 07:05 PM, Wade Chandler wrote:

My understanding is there isn’t a max limit on Slack for users for free, and I have 
confirmed this with Slack there is not supposed to be a limitation on numbers of members. 
NetBeans for instance has 320 members. Did someone tell you this or did you run into some 
issue? If so, you might write them to ask what is the deal.. It could be the difference in 
setup; we use a registration page which sends invitations https://netbeans.signup.team/ 
<https://netbeans.signup.team/> and is using bots from https://stacktodo.com/ 
<https://stacktodo.com/> Or, it could be something about when it was setup and 
differences in plans over time.

It doesn’t change the limits on the log and file storage, but we explain to 
folks it is for ephemeral real time communication and never to be considered 
historic, but we are looking into setting up a log bot which Slack personnel 
told us could also be helpful for OSS use. Slack said they don’t have plans for 
more features for OSS specific projects at the moment as one request from us 
was they make some new individual/personal low pay option which could help 
communities with dedicated membership to pay for their own personal use, but 
they said no plans at this time, but would take it into consideration as an 
idea.

Thanks,

Wade



On Mar 26, 2017, at 01:58, Jean-Baptiste Onofré <j...@nanthrax.net> wrote:

Hi,

Slack is very convenient for quick communication, but clearly, it doesn't 
change that the mailing list is the first communication channel. If discussions 
happen on Slack, minute notes/discussion has to be forwarded on the mailing 
list.

I wonder if we plan to ask for some "pro" Slack account for Apache projects (as 
we have license for IntelliJ for example). Now, at Apache Beam, we reached the max 
capacity of the Slack free version (90 Slack users on Beam channel and limited history). 
We already received new member request that we can't accept for now.

Thoughts ?

Regards
JB

On 03/22/2017 10:37 PM, Craig Russell wrote:

Hi James,

There was a pretty extensive discussion on the netbeans dev list. I’d encourage 
you to review this thread 
https://lists.apache.org/thread.html/2dce365d03334c82d31b12c8b3dcad1a925a2f71af75658b8d8a5a07@%3Cdev.netbeans.apache.org%3E

You can get all of the messages in the thread by doing a quick search for 
“slack” on the d...@netbeans.apache.org list in lists.apache.org.

My takeaway is that Slack not a substitute for email. But it is useful for 
ping-pong communication when people are in the heat of development.

But no decisions are made on Slack, and any discussion there (aside from “add a 
semicolon there” and “let’s get lunch") needs to be brought back to the dev 
list.

The underlying principle is that “if it didn’t happen on dev, then it didn’t 
happen”. We strive for open, inclusive communications at Apache and that means 
attempting to encourage participation by everyone who wants to, regardless of 
primary language, time zone, and availability of tools. (We assume everyone has 
a device that handles email clients).

Hope this helps.

Craig


On Mar 22, 2017, at 1:27 PM, James Bognar <jamesbog...@apache.org> wrote:

Can someone remind me?  I thought there was a discussion a couple of months
ago about allowing incubator projects to use Slack for communication.  What
was the final decision?


Craig L Russell
c...@apache.org









--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Slack

[Wade Chandler]

My understanding is there isn’t a max limit on Slack for users for free, and I 
have confirmed this with Slack there is not supposed to be a limitation on 
numbers of members. NetBeans for instance has 320 members. Did someone tell you 
this or did you run into some issue? If so, you might write them to ask what is 
the deal.. It could be the difference in setup; we use a registration page 
which sends invitations https://netbeans.signup.team/ 
<https://netbeans.signup.team/> and is using bots from https://stacktodo.com/ 
<https://stacktodo.com/> Or, it could be something about when it was setup and 
differences in plans over time.

It doesn’t change the limits on the log and file storage, but we explain to 
folks it is for ephemeral real time communication and never to be considered 
historic, but we are looking into setting up a log bot which Slack personnel 
told us could also be helpful for OSS use. Slack said they don’t have plans for 
more features for OSS specific projects at the moment as one request from us 
was they make some new individual/personal low pay option which could help 
communities with dedicated membership to pay for their own personal use, but 
they said no plans at this time, but would take it into consideration as an 
idea.

Thanks,

Wade


> On Mar 26, 2017, at 01:58, Jean-Baptiste Onofré <j...@nanthrax.net> wrote:
> 
> Hi,
> 
> Slack is very convenient for quick communication, but clearly, it doesn't 
> change that the mailing list is the first communication channel. If 
> discussions happen on Slack, minute notes/discussion has to be forwarded on 
> the mailing list.
> 
> I wonder if we plan to ask for some "pro" Slack account for Apache projects 
> (as we have license for IntelliJ for example). Now, at Apache Beam, we 
> reached the max capacity of the Slack free version (90 Slack users on Beam 
> channel and limited history). We already received new member request that we 
> can't accept for now.
> 
> Thoughts ?
> 
> Regards
> JB
> 
> On 03/22/2017 10:37 PM, Craig Russell wrote:
>> Hi James,
>> 
>> There was a pretty extensive discussion on the netbeans dev list. I’d 
>> encourage you to review this thread 
>> https://lists.apache.org/thread.html/2dce365d03334c82d31b12c8b3dcad1a925a2f71af75658b8d8a5a07@%3Cdev.netbeans.apache.org%3E
>> 
>> You can get all of the messages in the thread by doing a quick search for 
>> “slack” on the d...@netbeans.apache.org list in lists.apache.org.
>> 
>> My takeaway is that Slack not a substitute for email. But it is useful for 
>> ping-pong communication when people are in the heat of development.
>> 
>> But no decisions are made on Slack, and any discussion there (aside from 
>> “add a semicolon there” and “let’s get lunch") needs to be brought back to 
>> the dev list.
>> 
>> The underlying principle is that “if it didn’t happen on dev, then it didn’t 
>> happen”. We strive for open, inclusive communications at Apache and that 
>> means attempting to encourage participation by everyone who wants to, 
>> regardless of primary language, time zone, and availability of tools. (We 
>> assume everyone has a device that handles email clients).
>> 
>> Hope this helps.
>> 
>> Craig
>> 
>>> On Mar 22, 2017, at 1:27 PM, James Bognar <jamesbog...@apache.org> wrote:
>>> 
>>> Can someone remind me?  I thought there was a discussion a couple of months
>>> ago about allowing incubator projects to use Slack for communication.  What
>>> was the final decision?
>> 
>> Craig L Russell
>> c...@apache.org
>> 
>> 
> 

Re: Slack

[Evan Hughes]

On a slack channel for a uni club, might just be worth emailing them to
increase the limit on a per project basis as we have around 900 free users.

Also the cost of slack is extremely high. Even though communication is
important for a community, the cost is per user.

On 26 Mar 2017 4:18 PM, "Yaniv Rodenski" <roa...@gmail.com> wrote:

> Hi,
>
> Having a "pro" slack subscription will defiantly help projects that are
> using it.
>
> Also, Slack can integrate with the mailing list, for example using this app
> https://get.slack.help/hc/en-us/articles/206819278-Send-emails-to-Slack, I
> think that if nothing else, this can be seen as another form of a mail
> client, from a "pure" mailing list point of view.
>
> Cheers,
> Yaniv
>
> On Sun, 26 Mar 2017 at 4:58 pm, Jean-Baptiste Onofré <j...@nanthrax.net>
> wrote:
>
> > Hi,
> >
> > Slack is very convenient for quick communication, but clearly, it doesn't
> > change
> > that the mailing list is the first communication channel. If discussions
> > happen
> > on Slack, minute notes/discussion has to be forwarded on the mailing
> list.
> >
> > I wonder if we plan to ask for some "pro" Slack account for Apache
> > projects (as
> > we have license for IntelliJ for example). Now, at Apache Beam, we
> reached
> > the
> > max capacity of the Slack free version (90 Slack users on Beam channel
> and
> > limited history). We already received new member request that we can't
> > accept
> > for now.
> >
> > Thoughts ?
> >
> > Regards
> > JB
> >
> > On 03/22/2017 10:37 PM, Craig Russell wrote:
> > > Hi James,
> > >
> > > There was a pretty extensive discussion on the netbeans dev list. I’d
> > encourage you to review this thread https://lists.apache.org/
> thread.html/
> > 2dce365d03334c82d31b12c8b3dcad1a925a2f71af75658b8d8a5a07@%
> > 3Cdev.netbeans.apache.org%3E
> > >
> > > You can get all of the messages in the thread by doing a quick search
> > for “slack” on the d...@netbeans.apache.org list in lists.apache.org.
> > >
> > > My takeaway is that Slack not a substitute for email. But it is useful
> > for ping-pong communication when people are in the heat of development.
> > >
> > > But no decisions are made on Slack, and any discussion there (aside
> from
> > “add a semicolon there” and “let’s get lunch") needs to be brought back
> to
> > the dev list.
> > >
> > > The underlying principle is that “if it didn’t happen on dev, then it
> > didn’t happen”. We strive for open, inclusive communications at Apache
> and
> > that means attempting to encourage participation by everyone who wants
> to,
> > regardless of primary language, time zone, and availability of tools. (We
> > assume everyone has a device that handles email clients).
> > >
> > > Hope this helps.
> > >
> > > Craig
> > >
> > >> On Mar 22, 2017, at 1:27 PM, James Bognar <jamesbog...@apache.org>
> > wrote:
> > >>
> > >> Can someone remind me?  I thought there was a discussion a couple of
> > months
> > >> ago about allowing incubator projects to use Slack for communication.
> > What
> > >> was the final decision?
> > >
> > > Craig L Russell
> > > c...@apache.org
> > >
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> >
> > --
> > Jean-Baptiste Onofré
> > jbono...@apache.org
> > http://blog.nanthrax.net
> > Talend - http://www.talend.com
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: Slack

[Yaniv Rodenski]

Hi,

Having a "pro" slack subscription will defiantly help projects that are
using it.

Also, Slack can integrate with the mailing list, for example using this app
https://get.slack.help/hc/en-us/articles/206819278-Send-emails-to-Slack, I
think that if nothing else, this can be seen as another form of a mail
client, from a "pure" mailing list point of view.

Cheers,
Yaniv

On Sun, 26 Mar 2017 at 4:58 pm, Jean-Baptiste Onofré <j...@nanthrax.net>
wrote:

> Hi,
>
> Slack is very convenient for quick communication, but clearly, it doesn't
> change
> that the mailing list is the first communication channel. If discussions
> happen
> on Slack, minute notes/discussion has to be forwarded on the mailing list.
>
> I wonder if we plan to ask for some "pro" Slack account for Apache
> projects (as
> we have license for IntelliJ for example). Now, at Apache Beam, we reached
> the
> max capacity of the Slack free version (90 Slack users on Beam channel and
> limited history). We already received new member request that we can't
> accept
> for now.
>
> Thoughts ?
>
> Regards
> JB
>
> On 03/22/2017 10:37 PM, Craig Russell wrote:
> > Hi James,
> >
> > There was a pretty extensive discussion on the netbeans dev list. I’d
> encourage you to review this thread https://lists.apache.org/thread.html/
> 2dce365d03334c82d31b12c8b3dcad1a925a2f71af75658b8d8a5a07@%
> 3Cdev.netbeans.apache.org%3E
> >
> > You can get all of the messages in the thread by doing a quick search
> for “slack” on the d...@netbeans.apache.org list in lists.apache.org.
> >
> > My takeaway is that Slack not a substitute for email. But it is useful
> for ping-pong communication when people are in the heat of development.
> >
> > But no decisions are made on Slack, and any discussion there (aside from
> “add a semicolon there” and “let’s get lunch") needs to be brought back to
> the dev list.
> >
> > The underlying principle is that “if it didn’t happen on dev, then it
> didn’t happen”. We strive for open, inclusive communications at Apache and
> that means attempting to encourage participation by everyone who wants to,
> regardless of primary language, time zone, and availability of tools. (We
> assume everyone has a device that handles email clients).
> >
> > Hope this helps.
> >
> > Craig
> >
> >> On Mar 22, 2017, at 1:27 PM, James Bognar <jamesbog...@apache.org>
> wrote:
> >>
> >> Can someone remind me?  I thought there was a discussion a couple of
> months
> >> ago about allowing incubator projects to use Slack for communication.
> What
> >> was the final decision?
> >
> > Craig L Russell
> > c...@apache.org
> >
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Slack

[Jean-Baptiste Onofré]

Hi,

Slack is very convenient for quick communication, but clearly, it doesn't change 
that the mailing list is the first communication channel. If discussions happen 
on Slack, minute notes/discussion has to be forwarded on the mailing list.


I wonder if we plan to ask for some "pro" Slack account for Apache projects (as 
we have license for IntelliJ for example). Now, at Apache Beam, we reached the 
max capacity of the Slack free version (90 Slack users on Beam channel and 
limited history). We already received new member request that we can't accept 
for now.


Thoughts ?

Regards
JB

On 03/22/2017 10:37 PM, Craig Russell wrote:

Hi James,

There was a pretty extensive discussion on the netbeans dev list. I’d encourage 
you to review this thread 
https://lists.apache.org/thread.html/2dce365d03334c82d31b12c8b3dcad1a925a2f71af75658b8d8a5a07@%3Cdev.netbeans.apache.org%3E

You can get all of the messages in the thread by doing a quick search for 
“slack” on the d...@netbeans.apache.org list in lists.apache.org.

My takeaway is that Slack not a substitute for email. But it is useful for 
ping-pong communication when people are in the heat of development.

But no decisions are made on Slack, and any discussion there (aside from “add a 
semicolon there” and “let’s get lunch") needs to be brought back to the dev 
list.

The underlying principle is that “if it didn’t happen on dev, then it didn’t 
happen”. We strive for open, inclusive communications at Apache and that means 
attempting to encourage participation by everyone who wants to, regardless of 
primary language, time zone, and availability of tools. (We assume everyone has 
a device that handles email clients).

Hope this helps.

Craig


On Mar 22, 2017, at 1:27 PM, James Bognar <jamesbog...@apache.org> wrote:

Can someone remind me?  I thought there was a discussion a couple of months
ago about allowing incubator projects to use Slack for communication.  What
was the final decision?


Craig L Russell
c...@apache.org



-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Slack

[Bertrand Delacretaz]

On Thu, Mar 23, 2017 at 12:11 PM, Marvin Humphrey
 wrote:
> ...Apologies, and kudos for the great post...

No apologies needed and thanks!

-Bertrand

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Slack

[Marvin Humphrey]

On Thu, Mar 23, 2017 at 2:29 AM, Bertrand Delacretaz
 wrote:
> On Thu, Mar 23, 2017 at 2:56 AM, Marvin Humphrey  
> wrote:
>> ...Efficient asynchronous decision making over email is a skill, and 
>> mastering it
>> is key to success as an Apache community
>
> Indeed, this is one of the topics of our recent "success at Apache"
> blog posts series,
> https://blogs.apache.org/foundation/category/SuccessAtApache

Whoa! Obviously it made an impact on me, Bertrand! The phrasing is too
close, and if I had realized I would have linked myself. Apologies,
and kudos for the great post.

Marvin Humphrey

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Slack

[Bertrand Delacretaz]

On Thu, Mar 23, 2017 at 2:56 AM, Marvin Humphrey  wrote:
> ...Efficient asynchronous decision making over email is a skill, and 
> mastering it
> is key to success as an Apache community

Indeed, this is one of the topics of our recent "success at Apache"
blog posts series,
https://blogs.apache.org/foundation/category/SuccessAtApache

-Bertrand

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Slack support?

[Ted Dunning]

If you have a podling who wants to use slack, have them register under
their podling name and deal with it. No impact on infra needed. It's like
having yet another twitter account.





On Wed, Mar 22, 2017 at 10:18 PM, Greg Stein <gst...@gmail.com> wrote:

> On Wed, Mar 22, 2017 at 9:59 PM, Evan Hughes <wisebald...@apache.org>
> wrote:
>
> > Another option could be asking infra to host a rocket.chat server so we
> can
> > control the instances.
> >
>
> Sorry, Evan, but hosting a chat service is not an option for
> Infrastructure. That would be contrary to our work on consolidating
> services.
>
> We can have HipChat rooms for any/all projects. A simple Jira request, and
> you're all set.
>
> In short, the ASF is happy to have duplicative topics/projects because each
> community may approach a problem in different ways, with different focuses.
> But our Infra resources are limited, so we can't/won't stand up duplicate
> services. And even better when they can be outsourced (like HipChat, and
> increasingly GitHub).
>
> Cheers,
> Greg Stein
> Infrastructure Administrator, ASF
>

Re: Slack support?

[Greg Stein]

On Wed, Mar 22, 2017 at 9:59 PM, Evan Hughes  wrote:

> Another option could be asking infra to host a rocket.chat server so we can
> control the instances.
>

Sorry, Evan, but hosting a chat service is not an option for
Infrastructure. That would be contrary to our work on consolidating
services.

We can have HipChat rooms for any/all projects. A simple Jira request, and
you're all set.

In short, the ASF is happy to have duplicative topics/projects because each
community may approach a problem in different ways, with different focuses.
But our Infra resources are limited, so we can't/won't stand up duplicate
services. And even better when they can be outsourced (like HipChat, and
increasingly GitHub).

Cheers,
Greg Stein
Infrastructure Administrator, ASF

Re: Slack support?

[Evan Hughes]

Another option could be asking infra to host a rocket.chat server so we can
control the instances.

On 23 Mar 2017 12:03 PM, "John D. Ament" <johndam...@apache.org> wrote:

> On Wed, Mar 22, 2017 at 6:08 PM Ted Dunning <ted.dunn...@gmail.com> wrote:
>
> > Does the Incubator actually have to *do* anything to allow Slack support?
> >
> > If not, and if the normal rules for chat are followed (echoing to the
> > mailing list), then is there any need to ask?
> >
> >
> Basically, what it comes down to is having a PMC own it for a trial period,
> and if we see benefits moving it into a more supportable means.  All TBD.
>
> This email is an example of the type of summary I expect to see podlings
> have.  A quick chat happened on hipchat with Greg and Shane basically
> saying "no objections" but pointing out it wouldn't be an infra owned
> item.  We'd have to come up with ways to support it.  I just looked, turns
> out someone else already took apache.slack.com so we'd have to do
> something
> else (or figure out who created it; that something else could be
> asf.slack.com).
>
>
> >
> >
> > On Wed, Mar 22, 2017 at 5:40 PM, John D. Ament <johndam...@apache.org>
> > wrote:
> >
> > > Hey guys
> > >
> > > Just wondering, would there be interest within the Incubator allow
> Slack
> > > support?  Presently ASF has support for HipChat and Gitter, but I see
> > more
> > > podlings coming in asking for Slack support.
> > >
> > > John
> > >
> >
>

Re: Slack support?

[John D. Ament]

On Wed, Mar 22, 2017 at 6:08 PM Ted Dunning <ted.dunn...@gmail.com> wrote:

> Does the Incubator actually have to *do* anything to allow Slack support?
>
> If not, and if the normal rules for chat are followed (echoing to the
> mailing list), then is there any need to ask?
>
>
Basically, what it comes down to is having a PMC own it for a trial period,
and if we see benefits moving it into a more supportable means.  All TBD.

This email is an example of the type of summary I expect to see podlings
have.  A quick chat happened on hipchat with Greg and Shane basically
saying "no objections" but pointing out it wouldn't be an infra owned
item.  We'd have to come up with ways to support it.  I just looked, turns
out someone else already took apache.slack.com so we'd have to do something
else (or figure out who created it; that something else could be
asf.slack.com).


>
>
> On Wed, Mar 22, 2017 at 5:40 PM, John D. Ament <johndam...@apache.org>
> wrote:
>
> > Hey guys
> >
> > Just wondering, would there be interest within the Incubator allow Slack
> > support?  Presently ASF has support for HipChat and Gitter, but I see
> more
> > podlings coming in asking for Slack support.
> >
> > John
> >
>

Re: Slack

[Marvin Humphrey]

On Wed, Mar 22, 2017 at 2:37 PM, Craig Russell <craig.russ...@oracle.com> wrote:

> My takeaway is that Slack not a substitute for email. But it is useful for
> ping-pong communication when people are in the heat of development.
>
> But no decisions are made on Slack, and any discussion there (aside from
> “add a semicolon there” and “let’s get lunch") needs to be brought back to
> the dev list.
>
> The underlying principle is that “if it didn’t happen on dev, then it didn’t
> happen”. We strive for open, inclusive communications at Apache and that
> means attempting to encourage participation by everyone who wants to,
> regardless of primary language, time zone, and availability of tools. (We
> assume everyone has a device that handles email clients).

+1

I would add one more criteria: availability.  Real-time communication
channels, should they be used for development (as opposed to user support),
privilege core devs who follow the project every waking minute and exclude
everyone on the periphery.

Efficient asynchronous decision making over email is a skill, and mastering it
is key to success as an Apache community.  It takes practice, because the way
you present ideas for asynchronous consumption is not the same as the way
you'd do it in real-time.

The question I always have when podlings ask about Slack, IRC, videochat,
face-to-face convos in meatspace, or any real-time communication channel, is
whether they appreciate why they need to master email.

Marvin Humphrey

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Slack support?

[Ted Dunning]

Does the Incubator actually have to *do* anything to allow Slack support?

If not, and if the normal rules for chat are followed (echoing to the
mailing list), then is there any need to ask?



On Wed, Mar 22, 2017 at 5:40 PM, John D. Ament <johndam...@apache.org>
wrote:

> Hey guys
>
> Just wondering, would there be interest within the Incubator allow Slack
> support?  Presently ASF has support for HipChat and Gitter, but I see more
> podlings coming in asking for Slack support.
>
> John
>

Re: Slack support?

[Tom Barber]

I don't see why its any different to other IRC channels. Apache Drill has
been using it officially or unofficially for a while now (I assume they
still do its been a while since I was there).

On Thu, Mar 23, 2017 at 12:43 AM, James Bognar <james.bog...@salesforce.com>
wrote:

> There's interest from me personally.  Slack appears to be becoming
> popular.  HipChat appears to be slowing down in interest.
>
> On Wed, Mar 22, 2017 at 5:40 PM, John D. Ament <johndam...@apache.org>
> wrote:
>
> > Hey guys
> >
> > Just wondering, would there be interest within the Incubator allow Slack
> > support?  Presently ASF has support for HipChat and Gitter, but I see
> more
> > podlings coming in asking for Slack support.
> >
> > John
> >
>
>
>
> --
> James Bognar
>



-- 
Tom Barber
CTO Spicule LTD
t...@spicule.co.uk

http://spicule.co.uk

@spiculeim <http://twitter.com/spiculeim>

Schedule a meeting with me <http://meetme.so/spicule>

GB: +44(0)5603641316
US: +18448141689

<https://leanpub.com/juju-cookbook>

Re: Slack support?

[Sterling Hughes]

+1

> On Mar 22, 2017, at 5:43 PM, James Bognar <james.bog...@salesforce.com> wrote:
> 
> There's interest from me personally.  Slack appears to be becoming
> popular.  HipChat appears to be slowing down in interest.
> 
> On Wed, Mar 22, 2017 at 5:40 PM, John D. Ament <johndam...@apache.org>
> wrote:
> 
>> Hey guys
>> 
>> Just wondering, would there be interest within the Incubator allow Slack
>> support?  Presently ASF has support for HipChat and Gitter, but I see more
>> podlings coming in asking for Slack support.
>> 
>> John
>> 
> 
> 
> 
> -- 
> James Bognar

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Slack support?

[Gregory Chase]

Slack is becoming a standard in many non ASF communities.

RabbitMQ recently switched from IRC to Slack as its "real time"
conversation.

On Wed, Mar 22, 2017 at 5:43 PM, James Bognar <james.bog...@salesforce.com>
wrote:

> There's interest from me personally.  Slack appears to be becoming
> popular.  HipChat appears to be slowing down in interest.
>
> On Wed, Mar 22, 2017 at 5:40 PM, John D. Ament <johndam...@apache.org>
> wrote:
>
> > Hey guys
> >
> > Just wondering, would there be interest within the Incubator allow Slack
> > support?  Presently ASF has support for HipChat and Gitter, but I see
> more
> > podlings coming in asking for Slack support.
> >
> > John
> >
>
>
>
> --
> James Bognar
>



-- 
Greg Chase

Product team
http://www.pivotal.io/big-data

Pivotal Software
http://www.pivotal.io/

650-215-0477
@GregChase
Blog: http://geekmarketing.biz/

Re: Slack support?

[James Bognar]

There's interest from me personally.  Slack appears to be becoming
popular.  HipChat appears to be slowing down in interest.

On Wed, Mar 22, 2017 at 5:40 PM, John D. Ament <johndam...@apache.org>
wrote:

> Hey guys
>
> Just wondering, would there be interest within the Incubator allow Slack
> support?  Presently ASF has support for HipChat and Gitter, but I see more
> podlings coming in asking for Slack support.
>
> John
>



-- 
James Bognar

Slack support?

[John D. Ament]

Hey guys

Just wondering, would there be interest within the Incubator allow Slack
support?  Presently ASF has support for HipChat and Gitter, but I see more
podlings coming in asking for Slack support.

John

Re: Slack

[Craig Russell]

Hi James,

There was a pretty extensive discussion on the netbeans dev list. I’d encourage 
you to review this thread 
https://lists.apache.org/thread.html/2dce365d03334c82d31b12c8b3dcad1a925a2f71af75658b8d8a5a07@%3Cdev.netbeans.apache.org%3E

You can get all of the messages in the thread by doing a quick search for 
“slack” on the d...@netbeans.apache.org list in lists.apache.org.

My takeaway is that Slack not a substitute for email. But it is useful for 
ping-pong communication when people are in the heat of development.

But no decisions are made on Slack, and any discussion there (aside from “add a 
semicolon there” and “let’s get lunch") needs to be brought back to the dev 
list.

The underlying principle is that “if it didn’t happen on dev, then it didn’t 
happen”. We strive for open, inclusive communications at Apache and that means 
attempting to encourage participation by everyone who wants to, regardless of 
primary language, time zone, and availability of tools. (We assume everyone has 
a device that handles email clients).

Hope this helps.

Craig

> On Mar 22, 2017, at 1:27 PM, James Bognar <jamesbog...@apache.org> wrote:
> 
> Can someone remind me?  I thought there was a discussion a couple of months
> ago about allowing incubator projects to use Slack for communication.  What
> was the final decision?

Craig L Russell
c...@apache.org



-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Slack

[James Bognar]

Can someone remind me?  I thought there was a discussion a couple of months
ago about allowing incubator projects to use Slack for communication.  What
was the final decision?