1 |
Jan Kundrát wrote: |
2 |
> Camille Huot wrote: |
3 |
>> As a workaround, I would suggest to bump the date when an old document |
4 |
>> has been checked, tested and certified with current material. |
5 |
|
6 |
> If I were yoswink, I'd kill you for such a change. |
7 |
|
8 |
|
9 |
Well this all depends on your viewpoint. If you want a set of |
10 |
documents, that folks with deep gentoo experience can use, |
11 |
then stay the coarse. If you (we being the larger gentoo community |
12 |
including noobs, novices and nerds) then the last date of |
13 |
checking or updating is fundamentally important. We all know the |
14 |
internet is full of outdated and erroneous information. |
15 |
|
16 |
I find Camile's points very consistent with what the average user or |
17 |
noob will need. I would also 'simplify' the process, (see touch below) |
18 |
So ask yourself who do the documents need |
19 |
to be focused on, the gentoo elite, or the average gentoo |
20 |
hack....? |
21 |
|
22 |
|
23 |
It should not be that hard (internally) to track the last date |
24 |
the file was touched using 'touch' or whatever mechanism floats |
25 |
your boat, to provide the average user some comfort as to the |
26 |
usability, related to the age of the last check for accuracy the |
27 |
doc has undergone. If we use the last date the doc was 'touch-ed' be |
28 |
one of the gentoo elite, then the mechanism is simple. Surely this |
29 |
sort of mechanism would be heralded |
30 |
as a gentoo point of excellence among a sea of mediocre distros. |
31 |
|
32 |
I would suggest keeping the mechanism for updating the date, simple |
33 |
as in the use of 'touch' or such simple means. If you make it |
34 |
elaborate and complex, then it will be a nightmare. Not changing |
35 |
the date, except for a blue moon occurrence, instills doubt |
36 |
and those confused do not posses the skills of accurate document |
37 |
differentiation. If they did, they would not need the document |
38 |
to resolve their ignorance of the particular issue which they |
39 |
seek help, guidance or just a cookbook set of command examples. |
40 |
|
41 |
|
42 |
On another note, I think what is needed is something simple and bold |
43 |
at the top of the official gentoo docs that clearly let folks know |
44 |
that the doc is an official gentoo maintained doc. If you google for |
45 |
help you get all sorts of gentoo-ish looking docs and the average |
46 |
user may not know how to distinguish the official (maintained docs) |
47 |
from the rest. My thoughts here are some sort of 'gentoo-certified' |
48 |
symbol that is hyperlinked to a page that delineates (clearly |
49 |
explains) the nature of the officially maintained docs. Maybe the |
50 |
symbol could be Dali-ish artistic GC for Gentoo Certified. |
51 |
|
52 |
|
53 |
just random thoughts, nothing that should incite folks to anger |
54 |
(hopefully) |
55 |
|
56 |
|
57 |
James |