1 |
Rich Freeman posted on Tue, 16 Aug 2011 08:34:09 -0400 as excerpted: |
2 |
|
3 |
> Considering that we still haven't finished doing all of this for OpenRC |
4 |
> yet, I wouldn't worry about the changes hitting you anytime soon. I'd |
5 |
> consider a lessons-learned from OpenRC that we shouldn't stabilize |
6 |
> packages until AFTER the docs are updated. Otherwise it can tend to |
7 |
> never happen. |
8 |
|
9 |
As a follower and user of baselayout2/openrc from way back when it was |
10 |
still baselayout-1.13 (who BTW did my own share of bug tracing and |
11 |
filing, sometimes with suggested patches or partial-patches, along the |
12 |
way), and a CC on both the main and docs stabilization bugs, that |
13 |
actually rather mystified me. |
14 |
|
15 |
Originally, all the documentation was supposed to be a blocker for the |
16 |
openrc/baselayout2 stabilization bug, and that made sense. |
17 |
|
18 |
But then the docs folks said the policy was only to document stable, and |
19 |
that they weren't going to document openrc until it was going stable. |
20 |
Which didn't seem to make sense as everybody knew it was a big job, too |
21 |
big to happen in a final push, without "mistakes being made". Plus, by |
22 |
the time the final push came, for a change that big, there would be all |
23 |
sorts of other bugs blocking on openrc going stable, so there'd be no |
24 |
real way to do it properly, particularly with docs as understaffed as it |
25 |
is. |
26 |
|
27 |
I never did see how it was going to work, but shutup, because I was "just |
28 |
a user", and I couldn't see the devs being /that/ stupid, to stabilize |
29 |
without in-place docs or to rush them at the last minute, when so many |
30 |
users would be depending on the docs and the reputation Gentoo /used/ to |
31 |
have for being a Linux bright-spot, in terms of documentation, to the |
32 |
point that users from other distros used to seek out Gentoo docs, and I |
33 |
know that was one of the reason /I/ found Gentoo, particularly since |
34 |
Gentoo and its users were so early out the gate in the xfree86/xorg |
35 |
switchup. |
36 |
|
37 |
But then I saw it happen, and there's STILL openrc docs-related bugs |
38 |
open. I guess that really brought home to me how far Gentoo has fallen |
39 |
from its once exalted status, resting on its laurels... until they've all |
40 |
wilted and been thrown out and there's no more to rest on. |
41 |
|
42 |
That's the real bright spot (aside from his hardened activities which |
43 |
only have a relatively indirect affect on anything I follow closely) I |
44 |
see to swift's return as well, as he has already started tackling some of |
45 |
the related docs bugs. Nothing against the folks, nightmorph in |
46 |
particular, that have been holding down the fort -- I've been on projects |
47 |
when it seemed to be only me at times myself and it NOT easy -- but being |
48 |
the only real active member IS hard, and certainly DOES lead to burnout |
49 |
after awhile, and nightmorph has been exhibiting signs of burnout for two |
50 |
years or more (IIRC council even debated what might be done to help at |
51 |
one point, but without real volunteers, there's not a lot that they could |
52 |
do, except back off a bit on the pressure nightmorph was under, to the |
53 |
extent they could help there). So swift must certainly be a welcome |
54 |
relief for nightmorph, and for the rest of us, even in just the couple |
55 |
days he has been back, there's some docs changes, etc. =:^) |
56 |
|
57 |
-- |
58 |
Duncan - List replies preferred. No HTML msgs. |
59 |
"Every nonfree program has a lord, a master -- |
60 |
and if you use the program, he is your master." Richard Stallman |