Update: Discourse for Teams is live! Visit https://teams.discourse.com to learn more and to spin up a 30-day free trial. Still welcome feedback but the alpha testing stage is over so I am closing this topic. Thanks everyone who helped us get across the finish line!
You may have noticed that my profile here now flaunts flair - I spend half my life here on meta anyway so it’s only natural that I’ve now joined the CDCK team! I am working primarily on Discourse for Teams, a new hosted product we are building that uses the same open source Discourse software we know and love, but with some secret sauce added to make it even more amazing for team collaboration.
We’re now looking for some volunteers to trial Discourse for Teams and give us real world feedback on the experience. Specifically, we need teams of 5 or more people, some of whom have never seen Discourse before, willing to take Teams though its paces by using it to collaborate internally.
Teams ships with a large number of unique features and a careful curation of plugins we find are very effective in a team environment such as policy, end to end encryption, checklist, calendar, knowledge explorer and more.
If you’re interested in committing to a trial, send me a PM or email support<at>teams.discourse.com
In exchange, we will provide you up with a free site and extensive support. We will also add you to a private category here on meta where you can mix with other alpha testers and discuss ways to improve Teams.
Second, I’m excited to hear about Discourse for Teams.
I work with Discourse a whole bunch, and non-public instances are split between work teams and “faerie rings”.
Faerie rings are groups of folks that are working together for a short amount of time, but primarily have flat hierarchies. For “normal” work teams, it’s still most me and one or two people using Discourse as our CRM/PM suite, ya know the whole category-per-project/client deal.
So… is Discourse for Teams Alpha Testing of interest to me? “5 to 12” people is like the one range I can’t accommodate.
So I will give the same similar suggestion, students in high school and undergraduates often will not ask for help in the real world or when they do want to hide their identify because they think they will look like ???
It seems that StackOverflow for such is very popular.
Personally I think this is a better fit for groups than StackOverflow. Many people want help but often need a discussion at different levels. Also as many of us know the entire StackOverflow documents thing was a crash and burn but I personally liked it. So with Discourse as we see here especially with the PostgreSQL upgrade post, Q&A are coalesced into meaning/useful and quick to find info.
Hmm, this is interesting. I had previously suggested the ability for users to create their own teams (preferably 5-15). If this is like that, I’m in and would love to beta test it. We use it a lot in our gaming community.
Thanks all! Appreciate the warm welcome to the CDCK team and interest in the Teams trial. If you’re interested, please send me a PM with your use case and we can talk. I also updated the OP with the following - we are looking for a good faith, hardcore trial by a team of 5-12 people.
Given that I’m still in the midst of establishing my Discourse community, I can’t at this point commit 100% to abandon other forms of communication (Discord). I shall however, reference what I was talking about with regards to users with a specific role or trust level to be able to create their own team (user group), and invite others to join their team or have users request to join that team.
I’m now working in a 9-10 person team that might fit very well into what you’re making here. It’s open source and all-remote. My main question is whether this Teams package is intended to be used exclusively for a team, or if it can also accommodate a community forum alongside it. We don’t want to split our community forum and internals forum (i.e. Teams instance) into two different instances.
After a moment of thought a logical conclusion is that the seat would be tied to a pay structure. Yes/No? By extension that leads to what is the relation between a seat and a user. Is a new user tied to a specific seat, or are the seats dynamically assigned in that as teams are constructed and destroyed the seats go back into a central location for reuse?
We will certainly announce our pricing structure at great detail once we launch, no point really talking about this now. If you are looking for similar models have a look at the pricing models on Slack and GitHub.
This is a really interesting development! Congrats to y’all on getting this work built and into testing!
I’m really curious to know more about it!
This is a really great collection of features! You say they’re unique - as someone less-versed in what’s possible in a normal Discourse, can you talk about whether/why they wouldn’t be otherwise available for a self-run Discourse instance? If they are possible already, is it the feature bundle along with a support contract a big part of the per-seat cost?
Are y’all planning on some integrations moving forward - I know that talking about that sort of stuff can be a bit difficult but it’d be neat to hear what y’all are thinking about there if you feel like you can share.
Not sure what @lessless means by “community edition”. Teams is Discourse so many of the improvements we are adding to make it awesome for collaboration are also going into the same open source core software and official plugins for everyone’s benefit. But there are some closed source features that will only be available on Teams.
Actually, most Teams features including these are available as Discourse official plugins, which you can add to a self-run Discourse instance. What makes Teams special is the careful curation of these plugins and their settings so it “just works” out of the box. It is also far less configurable so you will find it easier to maintain. We provide an opinionated, purpose-built theme with a sidebar that puts collaboration features at your fingertips. Teams also has other functionality built-in relevant to per-user pricing, including the ability to invite guest users who only have access to specific guest-only categories.
What do you have in mind? Discourse already offers SSO and SAML, and Official Slack integration for Discourse. These will also be available on Teams, though some (like SAML) will require an enterprise plan.
Are you still looking for Alpha Testers? I’m the CTO of carwow.com
I literally typed Discourse for Teams in google because I’m looking for alternatives to long threads in Slack to discuss architectural/technical topics with the team. We are a team of about 25 engineers.