[pugworthy]

You are assuming this is a tool for developers. It can be for anyone organized as a team, or based around a product.

A product for example has sales, marketing, support, development, and more. They could all coexist in a single stack centered around the product for example.

[makecheck]

Those all sound like things that should be in perfect sync with the implementation. It would kind of suck if Marketing started talking about one way things work, when they actually work differently. The company sure as hell shouldn’t have Sales selling people based on things that aren’t true.

As I said in another comment, information extracted from code can be made more pretty but ideally the code is king.

[pugworthy]

No you totally want marketing to be talking about something in the same place, even if they are wrong. It would absolutely not suck if they posted something incorrect, because then the people that know better can post alternative answers and/or comment and help correct the information.

If you put them in separate stacks, the bad information will just persist and live in isolation, and never get corrected.

You basically want to do everything you can to prevent silo'ing of people as well as knowledge. You want people talking.

Consider too that not everything posted has to be about technology. It can be recommendations for a good restaurant near a customer site, or where office supplies can be found in a large, multi-site office, or how to request facilities to come fix a leaking faucet.

[monkeydust]

Lol. Your kidding right. This would definitely be useful as a communication layer between business and sales with perhaps engineering involved.