3 ms·

This has already existed in the form of Stack Overflow Enterprise [1]. One major difference is that the company I was at managed and maintained their instance o

This has already existed in the form of Stack Overflow Enterprise [1]. One major difference is that the company I was at managed and maintained their instance of Stack Overflow (it involved a lot of work). I wonder what else is different (or maybe this is just a replacement for Enterprise?) [1] https://www.stackoverflowbusiness.com/enterprise https://www.stackoverflowbusiness.com/enterprise

cheath 9y ago
It's very similar to Enterprise. The big difference is that for Enterprise you need to have a big enough user base to sustain a community. Channels is geared towards smaller orgs, with more hooks to get Qs answered and built into the core stackoverflow.com experience.
davnicwil 9y ago
When was this launched?
- azhenley 9y ago
  It has been around since at least 2010 [1], and there was a more official release in mid 2013 [2]. [1] https://meta.stackexchange.com/a/69436/169404 https://meta.stackexchange.com/a/69436/169404 [2] https://meta.stackexchange.com/a/197549/169404 https://meta.stackexchange.com/a/197549/169404
- cheath 9y ago
  We tried it a while ago, but we re-launched it with a much more updated solution about a year and a half ago. And it now has a dedicated ongoing team.
alexlmiller 9y ago
For context, I'm the GM of the Enterprise Team at Stack Overflow and have been working on it since we launched our full Enterprise product about 18 months ago. Enterprise is intended for large teams (at least 500 tech staff) who want to have their own completely isolated and standalone Stack Overflow community that can be run on-prem or in a private cloud. Enterprise deployments have full control over the system and also get support from our Customer Success team to build up their community using all the lessons we've learned in 8+ years of building communities. As part of this we have all those features you'd expect like integration with SSO, audibility, massive 50 page contracts, etc Channels on the other hand is meant for smaller teams (all the way down to just 2 people) who want to store their own knowledge (privately and securely) alongside the the public knowledgebase at stackoverflow.com. Any size team will be able to just walk up, put down their credit card and instantly be sharing knowledge with each other. So the two products are very complimentary to each other, just depends on your team size and exactly what you're looking for feature wise.
- 659087 9y ago
  > store their own knowledge (privately and securely) alongside the the public knowledgebase at stackoverflow.com I know this won't go over well here, since many depend on Stackoverflow for their "programming skills", but this sounds about as believable as Google pushing companies to store their secrets "privately" using Google Docs.
  - deleted 9y ago
    [deleted]

cheath 9y ago

It's very similar to Enterprise. The big difference is that for Enterprise you need to have a big enough user base to sustain a community. Channels is geared towards smaller orgs, with more hooks to get Qs answered and built into the core stackoverflow.com experience.

davnicwil 9y ago

When was this launched?

azhenley 9y ago
It has been around since at least 2010 [1], and there was a more official release in mid 2013 [2]. [1] https://meta.stackexchange.com/a/69436/169404 https://meta.stackexchange.com/a/69436/169404 [2] https://meta.stackexchange.com/a/197549/169404 https://meta.stackexchange.com/a/197549/169404
cheath 9y ago
We tried it a while ago, but we re-launched it with a much more updated solution about a year and a half ago. And it now has a dedicated ongoing team.

alexlmiller 9y ago

For context, I'm the GM of the Enterprise Team at Stack Overflow and have been working on it since we launched our full Enterprise product about 18 months ago. Enterprise is intended for large teams (at least 500 tech staff) who want to have their own completely isolated and standalone Stack Overflow community that can be run on-prem or in a private cloud. Enterprise deployments have full control over the system and also get support from our Customer Success team to build up their community using all the lessons we've learned in 8+ years of building communities. As part of this we have all those features you'd expect like integration with SSO, audibility, massive 50 page contracts, etc Channels on the other hand is meant for smaller teams (all the way down to just 2 people) who want to store their own knowledge (privately and securely) alongside the the public knowledgebase at stackoverflow.com. Any size team will be able to just walk up, put down their credit card and instantly be sharing knowledge with each other. So the two products are very complimentary to each other, just depends on your team size and exactly what you're looking for feature wise.

659087 9y ago
> store their own knowledge (privately and securely) alongside the the public knowledgebase at stackoverflow.com I know this won't go over well here, since many depend on Stackoverflow for their "programming skills", but this sounds about as believable as Google pushing companies to store their secrets "privately" using Google Docs.
- deleted 9y ago
  [deleted]