Timeline for answer to Warlords of Documentation: A Proposed Expansion of Stack Overflow by Has QUIT--Anony-Mousse
Current License: CC BY-SA 3.0
Post Revisions
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 16, 2015 at 19:42 | comment | added | Alan McBee | MSDN, at one point, was a lot more encouraging of community content. The typical contribution consisted of a technical support question, rather than helpful content. I'm sure the cost of moderating sealed the fate of community content on MSDN. | |
| Sep 6, 2015 at 4:04 | comment | added | tacaswell | As a dev of a major project (matplotlib) I think this is the best response. Effort that goes into SO based documentation should be directed upstream. | |
| Sep 4, 2015 at 22:05 | comment | added | Pekka | How would this work in the real world, with thousands of different platforms, documentation standards, hierarchies, etc., without everyone migrating their docs to one unified platform? | |
| Sep 3, 2015 at 13:30 | comment | added | sevenseacat | I came to say this - we should be encouraging fixing the documentation itself wherever possible, instead of simply creating a new set. That way all users of the libraries/languages/frameworks benefit, not just those that use StackOverflow. | |
| Sep 2, 2015 at 18:16 | comment | added | Seldom 'Where's Monica' Needy | You're right. jQ is another example of which I was reminded reading through here, plus Java docs for the folks who work in the larger shops which still use and build Java-tools heavily. I had a decent idea for addressing the effort-duplication issue... (see my response). But the copyright issues are a much harder thing to solve (partly because the courts have not really caught up to the idea of what coders do, and just how much of what they do is the same no matter who does it – see "copyright trolls" who succeed esp. in the software realm) | |
| Sep 2, 2015 at 1:33 | comment | added | Has QUIT--Anony-Mousse | But MSDN is just a subset. Think of jQuery, Java and such. JavaDoc never allowed comments. MSDN is a single provider, so to speak. That would be a warlords of MSDN. | |
| Sep 1, 2015 at 20:15 | comment | added | Seldom 'Where's Monica' Needy | Counterpoint: MSDN is enormous, sprawling, and most if not all of it is closed to comment. I think I agree with you that duplication of effort is bad, and would in general think this whole idea is silly if not for MSDN. The ideal outcome for all this in my mind would just be that Microsoft open up its docs to comments that provide useful examples, descriptions of edge-cases, etc. After that, Warlords of Documentation can go away as far as I'm concerned. | |
| Sep 1, 2015 at 3:46 | history | answered | Has QUIT--Anony-Mousse | CC BY-SA 3.0 |