1 |
On Thu, Aug 25, 2011 at 1:41 AM, Joshua Saddler <nightmorph@g.o> wrote: |
2 |
> On Tue, 23 Aug 2011 09:43:51 -0400 |
3 |
> Matt Turner <mattst88@g.o> wrote: |
4 |
> |
5 |
>> On Tue, Aug 23, 2011 at 4:52 AM, Sven Vermeulen <swift@g.o> |
6 |
>> wrote: |
7 |
>> > On Mon, Aug 22, 2011 at 08:16:59PM -0400, Matt Turner wrote: |
8 |
>> >> The information on this page is very irrelevant and confusing to |
9 |
>> >> me, as a developer. |
10 |
>> >> |
11 |
>> >> I don't know how many non-developer documenters we have. I don't |
12 |
>> >> know what needs to happen to that text itself, but a section |
13 |
>> >> about how current developers join the documentation team is |
14 |
>> >> important. Looking at the page, a person must complete the staff |
15 |
>> >> and doc quizzes. For a developer, it seems that the requirements |
16 |
>> >> should simply be 1) to have become a developer and 2) completed |
17 |
>> >> the doc quiz. |
18 |
>> > |
19 |
>> > Documentation developers are also developers, but they do not |
20 |
>> > need to be an ebuild-developer. If I look at the GDP current |
21 |
>> > staffing, there are 8 developers that are also ebuild developers |
22 |
>> > (or infrastructure or another function within Gentoo) and 11 |
23 |
>> > developers on the documentation (and translations) only. |
24 |
>> > |
25 |
>> > Requiring documentation developers to also take the ebuild and |
26 |
>> > end quiz would be overshooting, as that is not something they |
27 |
>> > require. |
28 |
>> > |
29 |
>> > Wkr, |
30 |
>> > Sven Vermeulen |
31 |
>> |
32 |
>> Right, I'm saying for people who are already developers, they should |
33 |
>> really only have to complete the doc quiz. |
34 |
>> |
35 |
>> Matt |
36 |
>> |
37 |
> |
38 |
> You want to contribute ebuilds, you have to go through a process that |
39 |
> teaches you what you need to know, and shows your mentor that know |
40 |
> what you're doing; that you're not going to screw up everyone's |
41 |
> boxes. |
42 |
> |
43 |
> You want to write documentation, you have to go through a process |
44 |
> that teaches you what you need to know, and shows your mentor that |
45 |
> you know what you're doing; that you're not going to screw up |
46 |
> everyone's boxes ... *or the Gentoo websites*. (via bad commits that |
47 |
> break layouts, links, XML, CSS, etc.) |
48 |
> |
49 |
> Everyone has to go through a process when wanting to join a team. |
50 |
> What's so hard about this? Why should ebuild developers get a free |
51 |
> pass to get write access? Over the years, I've talked with several |
52 |
> different ebuild team leads, as I was interested in what it took to |
53 |
> get access to gentoo-x86. There's no free pass for longtime doc |
54 |
> writers, either, even those that have run their own private overlay |
55 |
> for a long time. I don't just take the ebuild quiz and get commit |
56 |
> access. There's a process that I have to go through, too. |
57 |
> |
58 |
> Maybe I'm just reading this wrong, but it sounds like you want to set |
59 |
> things up so that anyone who wants to change a doc can overwrite it |
60 |
> directly. That's fine for stuff in /proj/ -- the GDP doesn't care |
61 |
> about that; documents in /proj/ are solely the responsibility of those |
62 |
> projects. And that's why, overall, the quality of stuff in /proj/ is |
63 |
> not as good as what's in /doc/. |
64 |
|
65 |
I appear to have touched a nerve. |
66 |
|
67 |
Let me revise my previous email. I think an existing (ebuild) |
68 |
developer should do the following things to join the doc team: |
69 |
- doc quiz; |
70 |
- CSS knowledge is a plus; |
71 |
- have some documentation patches to prove he's not a doofus. |
72 |
|
73 |
I don't intend to belittle the doc team, but while your point about |
74 |
having to go through mentoring for an ebuild developer and therefore |
75 |
why not also a doc developer is well taken, I have a hard time |
76 |
believing that there's nearly as much knowledge to take in to become a |
77 |
documentation developer. Learning GuideXML can be done in a day or |
78 |
two. Being a good writer is something not easily learned. |
79 |
|
80 |
But whatever. I'll just post patches in bug reports. It's not worth |
81 |
the time to go through a second recruitment process to that I can |
82 |
modify a couple pieces of documentation about the architecture teams |
83 |
I'm a member of. Maybe these documents should be under /proj anyway; |
84 |
they certainly weren't looking very healthy under /doc. |
85 |
|
86 |
Matt |