1 |
Corey Shields wrote: |
2 |
> On Tuesday 17 August 2004 06:23 pm, Jeremy Maitin-Shepard wrote: |
3 |
> |
4 |
>>>Okay, I wasn't aware of that, but I haven't actually visited |
5 |
>>>gentoo-wiki.com either. Regardless of the state of that particular |
6 |
>>>wiki, I think a wiki would simply be more useful than a weblog, since a |
7 |
>>>wiki allows for greater flexibility generally. It might make sense to |
8 |
>>>make parts of it or all of it writable only by developers. I think |
9 |
>>>allowing users to modify parts of it would be advantageous though, since |
10 |
>>>it would provide a better home for the sort of tutorials currently found |
11 |
>>>in the forums. |
12 |
> |
13 |
> I really can't support an official wiki. |
14 |
|
15 |
An «official wiki» ? Isn't that a contradiction in itself? |
16 |
|
17 |
> If our current method of |
18 |
> documentation and support totally sucked then it would be a different story, |
19 |
> but we are known for excellent documentation, and there is a system of checks |
20 |
> and balances in the documentation process that you just don't get from a |
21 |
> wiki. Otherwise, you end up with phrases like "While most poeple use would |
22 |
> use this : " which makes no sense (taken from the first page I visited at |
23 |
> the above url). I feel that a wiki would be taking a step backwards.. |
24 |
|
25 |
I dont think it was suggested the current docs should be replaced by a wiki, |
26 |
that would indeed be a major step backwards. |
27 |
|
28 |
> If there is a piece of documentation that someone has written and feels it |
29 |
> should be included, by all means, post it to bugs.gentoo.org. While I can't |
30 |
> speak for them, I'm pretty sure that the documentation team would love the |
31 |
> contribution. |
32 |
|
33 |
A wiki would be much more handy than the forums for user-contributed docs. |
34 |
IMHO it would allow more users to find what they need, more users to share |
35 |
their knowledge and eventually allow the docdevs to integrate that knowledge |
36 |
into the current docs or create new ones. |
37 |
Writing docs about things the author knows is useful, writing docs about |
38 |
things users don't know is even better. A wiki would let us assess the latter |
39 |
in a better way. |
40 |
|
41 |
|
42 |
And now, something completely different, blogs. |
43 |
|
44 |
On the one hand, if I ever wanted to post my own personal blog, I would |
45 |
definitely *not* host it on Gentoo so it can be _personal_, i.e. I could write |
46 |
anything I want any way I like without embarrassing, implicating or causing |
47 |
any liability to Gentoo. |
48 |
Wouldn't a planet be a good choice? Given devs, or anybody else, do not really |
49 |
need Gentoo to publish a blog in the first place, why not show us the blogs |
50 |
first? The main problem now is we don't know where the blogs are. A planet |
51 |
would give them visibility, Gentoo would keep the choice of which blogs are |
52 |
'planeted' (just in case) and it would not require too much resources, hopefully. |
53 |
On the other hand, I would be very interested in official *project blogs*. |
54 |
Some teams post a status page once in a while, some might not. A project blog |
55 |
would be more dynamic and wouldn't require status page writers to keep tabs. |
56 |
See it as a way of publishing all sorts of little bits of information that are |
57 |
not big enough to make it to our home page. |
58 |
Besides, a planet of those blogs would give a neat overview of everything that |
59 |
is happening within Gentoo. |
60 |
|
61 |
|
62 |
My 0,02€ |
63 |
-- |
64 |
/ Xavier Neys |
65 |
\_ Gentoo Documentation Project |
66 |
/ French & Internationalisation Lead |
67 |
\ http://www.gentoo.org/doc/en |
68 |
/\ |