Timeline for answer to Warlords of Documentation: Your Quest(ions Answered) by jscs
Current License: CC BY-SA 3.0
Post Revisions
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 2, 2015 at 21:46 | history | edited | Peter Mortensen | CC BY-SA 3.0 |
Expansion, etc.
|
| Oct 1, 2015 at 16:22 | comment | added | jscs | Yes, the key word being "useful", @Suragch. | |
| Oct 1, 2015 at 9:59 | comment | added | Suragch | If someone wants to spend their time making useful documentation in order to "farm rep", I say let them. | |
| Sep 17, 2015 at 21:14 | comment | added | Ajedi32 | As with self-answered questions, I don't think there's any pressing need to prevent self-created articles, so long as there's an opportunity for the rest of the community to review their content. | |
| Sep 17, 2015 at 20:28 | comment | added | Governa | Why not put a documentation request up to voting, and only allowing it after some threshold? | |
| Sep 16, 2015 at 20:47 | comment | added | D. Ben Knoble | Hallelujah for greek references. Scylla and Charybdis. | |
| Sep 16, 2015 at 20:45 | comment | added | jscs | Ah ha; that would neatly sail between the rock and the whirlpool, @BenKnoble. Great clarification. | |
| Sep 16, 2015 at 20:38 | comment | added | D. Ben Knoble | It sounds to me like doing the things people request gets you rep, and getting up votes when people find it helpful gets you rep, i.e. making the page from scratch = no rep, but people up-voting its usefulness = rep | |
| Sep 16, 2015 at 20:01 | comment | added | Shotgun Ninja | I'm not sure if making from-scratch page creation restricted to the ivory tower of high-rep users is a good thing; rep != expertise, especially when it's low. | |
| Sep 16, 2015 at 19:56 | comment | added | duplode | Off-the-cuff suggestions: (a) Make creating pages from scratch a somewhat hard to attain privilege (e.g. require 10k rep or a silver tag badge); (b) Allow recognised experts (e.g. major contributors to relevant projects) to create new pages; (c) Set up a migration path for self-answered questions. These workarounds are complementary to each other. Some potential objections: (a) would exclude experts who are not interested in building up rep, (b) might lead to bureaucracy and drama, while (c) would require some extra editing work. | |
| Sep 16, 2015 at 19:56 | comment | added | Shotgun Ninja | Yeah, what if I just want to write a document to fill in something I already know how to do, but for which there's not really any quality documentation out there to direct users to? Take, for example, game development libraries. There are a huge number of topics in game development, many of which can be realized with a specific language by using a specific library. However, game development is hard enough that most people won't take the effort to make a working tutorial of some game mechanic/technique with some library... but goddamnit, I want rendering-to-texture in Ruby, and I want to share. | |
| Sep 16, 2015 at 18:44 | history | answered | jscs | CC BY-SA 3.0 |