Re: Guidance : Gitter --> Slack

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: > > &

Re: Guidance : Gitter --> Slack

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

Re: Guidance : Gitter --> Slack

t; 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

Re: Guidance : Gitter --> Slack

nfra 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) chos

Re: Guidance : Gitter --> Slack

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

Re: Guidance : Gitter --> Slack

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 >

Re: Guidance : Gitter --> Slack

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

Re: Guidance : Gitter --> Slack

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

Guidance : Gitter --> Slack

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

> 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, &qu

Re: [LAZY] Letting anyone invite on Slack

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 earlie

Re: [LAZY] Letting anyone invite on Slack

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

Re: [LAZY] Letting anyone invite on Slack

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&g

Re: [LAZY] Letting anyone invite on Slack

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 &

Re: [LAZY] Letting anyone invite on Slack

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

Re: [LAZY] Letting anyone invite on Slack

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 see

Re: [LAZY] Letting anyone invite on Slack

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

Re: [LAZY] Letting anyone invite on Slack

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

[LAZY] Letting anyone invite on Slack

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

Policies with respect to slack/github

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

Re: Slack Invites

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 ad

Re: Slack support?

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

Re: Slack support?

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

Re: Slack support?

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 > e

Re: Slack support?

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

Slack Invites

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?

ack 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 l

Re: Slack support?

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

Re: Slack support?

g 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

Re: Slack support?

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

Re: Slack support?

e: > > > 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 a

Re: Slack

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

Re: Slack support?

unn...@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, Gr

Re: Slack

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 o

Re: Slack

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

Re: Slack

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,

Re: Slack

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

Re: Slack

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

Re: Slack

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

Re: Slack

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

Re: Slack

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

Re: Slack

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

Re: Slack

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

Re: Slack

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

Re: Slack

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

Re: Slack

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

Re: Slack

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&q

Re: Slack

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:

Re: Slack

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

Re: Slack

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

Re: Slack support?

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

Re: Slack support?

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

Re: Slack support?

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

Re: Slack support?

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? &

Re: Slack

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,

Re: Slack support?

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

Re: Slack support?

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 inter

Re: Slack support?

+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. Amen

Re: Slack support?

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 app

Re: Slack support?

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 Incuba

Slack support?

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

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

Slack

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?