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