| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Jack Dark wrote: |
| 5 |
> Just so I can get this straight--having already accidentally filed a |
| 6 |
> bug with the wrong team (sorry!)--I need explicit clarification on |
| 7 |
> where "documentation" bugs go; I'm a little shaky on anything found in |
| 8 |
> /proj/en/. I've begun to figure out that not all documents are in fact |
| 9 |
> handled by the gentoo-doc team. So, on that basis, is the following |
| 10 |
> assignment guess correct: |
| 11 |
|
| 12 |
That's the ideal world scenario, and someday *all* docs on gentoo.org |
| 13 |
might be handled by the docs team. But as of now, that's not the way it |
| 14 |
works. |
| 15 |
|
| 16 |
> If I find an error on one of the pages listed on |
| 17 |
> http://www.gentoo.org/doc/en/index.xml?catid=project , does a fix/bug |
| 18 |
> report go to the team listed in purple above each individual section? |
| 19 |
|
| 20 |
Simple rule of thumb that I use....look at the URL of the doc which has |
| 21 |
the issue. |
| 22 |
|
| 23 |
a) If it is something like http://g.o/*doc*/lang/foobar, it goes to the |
| 24 |
docs-team. |
| 25 |
b) If it is something like http://g.o/*proj*/lang/foobar, it goes to |
| 26 |
that respective team. like releng or devrel... |
| 27 |
|
| 28 |
Although there are some project team members who watch docs-team bugs, I |
| 29 |
guess it is good practice to assign bugs to specific teams, since all |
| 30 |
members usually have access and will prolly fix it faster. |
| 31 |
|
| 32 |
Regards, |
| 33 |
|
| 34 |
- -- |
| 35 |
Shyam Mani | <fox2mike@g.o> |
| 36 |
docs-team | http://gdp.gentoo.org |
| 37 |
GPG key | 0xFDD0E345 |
| 38 |
-----BEGIN PGP SIGNATURE----- |
| 39 |
Version: GnuPG v1.4.1 (GNU/Linux) |
| 40 |
|
| 41 |
iD8DBQFCzi2uYZNYgP3Q40URAs7KAJ4g2apaAz5o4rhPpbtRowiD+I/09gCeN6iw |
| 42 |
q3JoXO3K+4p7FvajHEVj9hk= |
| 43 |
=AJ+O |
| 44 |
-----END PGP SIGNATURE----- |
| 45 |
-- |
| 46 |
gentoo-doc@g.o mailing list |
Archives