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