| 1 |
Alexander Plank wrote: |
| 2 |
> Maybe a good idea would be a type of system in which edits would need |
| 3 |
> to be certified as accurate by a developer before added to the site. Or |
| 4 |
> maybe we could have a system where the "unstable version" is editable by |
| 5 |
> anyone, but the stable version (the one that people read if they want to |
| 6 |
> follow a guide) needs to be fact checked by a developer. These solutions |
| 7 |
> tend to take too much time away from developers who'd probably rather be |
| 8 |
> writing the documentation themselves or actually developing (god |
| 9 |
> forbid). Would we still want an officially sanctioned wiki? I think |
| 10 |
> this might be bad because there would be accuracy problems which are |
| 11 |
> common in basically most wikis (look at the wikipedia project, for |
| 12 |
> example). Our accuracy problems might be worse than wikipedia since we |
| 13 |
> probably won't have as many obsessive compulsive people refreshing the |
| 14 |
> recent changes page every second. |
| 15 |
|
| 16 |
This could easily be implemented in <insert your favorite scripting |
| 17 |
language here>. I do feel that public contribution of documentation is |
| 18 |
extremely important for Gentoo for Mac OS X, as well as any other gentoo |
| 19 |
project in this stage of such youth. |
| 20 |
|
| 21 |
Perhaps the easiest way to implement this is to not change anything at |
| 22 |
all - use what's already there. For example, you could use bugzilla to |
| 23 |
allow people to post change/update requests for documentation, and then |
| 24 |
have a developer close bugs as necessary just as any other sort of |
| 25 |
change/update request is handled, documentation or not. This means we |
| 26 |
could stick to one source for documentation, and have less redundancy. |
| 27 |
All this stable and unstable branch stuff seems to be real redundant, |
| 28 |
and I agree that perhaps a wiki is more maintenance (for QA purposes) |
| 29 |
than we're up for. But then again, perhaps we just need to take a look |
| 30 |
at how much quality we really assure with a public-writable wiki (I.E. |
| 31 |
do we assure any quality?). |
| 32 |
|
| 33 |
> |
| 34 |
> With that said, I'm currently running a wiki for the macos |
| 35 |
> documentation. I'd like to establish this as an official guide-xml soon. |
| 36 |
|
| 37 |
Write the guide-xml for the Gentoo for Mac OS X project now, and ask |
| 38 |
questions [about getting official space for it on gentoo.org] later. |
| 39 |
Having something firm to push behind always helps when trying to get |
| 40 |
something done (like having the actual page already when asking for |
| 41 |
space on gentoo.org). There is a great guide-xml howto on the Gentoo |
| 42 |
docs section. |
| 43 |
|
| 44 |
-- |
| 45 |
|
| 46 |
Hasan Khalil <gongloo@g.o> |
| 47 |
Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x707B8F18 |
Archives