1 |
Nathan Zachary wrote: |
2 |
> Ben de Groot wrote: |
3 |
>> To me this sounds like an issue that needs to be brought to the |
4 |
>> attention of the council. Having good documentation has always been one |
5 |
>> of the strengths of Gentoo. It would be sad to see that wither away |
6 |
>> because of lack of manpower or lack of interest. Maybe we need to do |
7 |
>> some targeted recruiting for the documentation team. |
8 |
|
9 |
Eh, the council is a governing body for technical issues. They're all |
10 |
about setting policy for things like Portage and ebuilds. I'm not sure |
11 |
that they need to be bothered by what's going on in the GDP. |
12 |
|
13 |
> I have contributed a document to the documentation team. |
14 |
|
15 |
* Which, by the way, I'm examining today. :) |
16 |
|
17 |
> Two people actively working on documents is not enough either, but it |
18 |
> will hopefully offset some of the labour. I don't think that the team |
19 |
> would have any trouble finding volunteers to help out with editing, and |
20 |
> that an announcement should be made on the forum. |
21 |
|
22 |
Editing, or continual maintainance, is generally not a problem, assuming |
23 |
that any bugs filed aren't for obscure subjects of which no one has any |
24 |
knowledge. With the exception of big projects like updating all our docs |
25 |
for OpenRC/Baselayout-2, the handbooks for autobuilds, or the Xorg guide |
26 |
for xserver 1.5, even one person (me) can generally keep up with |
27 |
day-to-day maintenance. |
28 |
|
29 |
Where we really need help is in writing and maintaining *new* |
30 |
documentation. Nate's Openbox draft is just the sort of thing that we need. |
31 |
|
32 |
Now, on the forums and on our highly visible public mailing lists, I've |
33 |
continually asked for help for years, wanting to get in some fresh new |
34 |
talents to keep up with the English documentation. Unfortunately, since |
35 |
I started helping write docs in 2005, we haven't seen a single new |
36 |
dedicated English editor. Not someone who later becomes a developer, nor |
37 |
a regular user from the Gentoo community. |
38 |
|
39 |
Where we are more successful is in attracting new recruits for |
40 |
translation teams. Our Internationalization subproject gets all the new |
41 |
people. :) |
42 |
|
43 |
I don't know that *advertising* is the problem . . . the problem is that |
44 |
people just don't want to do the work. The most help we get is bug |
45 |
reports (to varying degrees of helpfulness where they include |
46 |
solutions), or occasional one-off new documents or substantial additions |
47 |
to an existing guide. |
48 |
|
49 |
I don't really blame folks for not wanting to do it, either -- there is |
50 |
a lot of work to do. And it's not always something that can be satisfied |
51 |
with a 30-second fix. Sure, in one weekend I may knock down our load of |
52 |
bugs from 50 to 34, but in a couple of months it'll be back up to 50 or 60. |
53 |
|
54 |
It takes a fair amount of dedicated time and effort to learn how |
55 |
GuideXML and our coding style work. We have several tools and resources |
56 |
available to help prospective recruits, but first someone has to show |
57 |
willingness to learn. Not just willingness to learn, but the drive and |
58 |
determination to improve our documentation by actually coming back and |
59 |
contributing. :) |
60 |
|
61 |
It's so extremely rare that it makes me think other distributions must |
62 |
have the same manpower issues we do: it's just a universal "given" that |
63 |
people don't want to write. |