[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

bugzilla questions aka: more docs tasks TODO for (or before) F12 cycle



Greetings,

There was some IRC discussion today about bugzilla and docs.
Along with a request to put it to the list for more conversation and
feedback from the "been there, done that" and "here's why" crowd.
The result is and will be more tasks TODO before or during the F12 cycle.

Take a look at the components that exist:
https://bugzilla.redhat.com/describecomponents.cgi?product=Fedora%20Documentation

Notice that Paul and Karsten get most of the assignments.
That doesn't seem right with so many new leaders and authors.

ITEM 1:
Questions that I see:
which docs are dead and need to be removed?
which docs are missing and need to be added?

how do we best change a component name when something has changed?
[this refers to desktop-user-guide having been just user-guide for a
long time now]

And before sparks starts reassigning things, it would be nice if the
doc owners knew it was coming.
Some of the more obvious assignees might consider this a heads up :)
but I do not have the power so you are safe for now.

ITEM 2:
The other part of this issue is that more people need to be closing bugs.
Some of this is triage work - not a bug or filed in the wrong place.
Some is fixing the doc at the source - usually git (or shouldn't be a filed bug)

So - I would suggest that anyone who has write to a doc in git should
also make sure they have the ability to close the related bug in
bugzilla.
Here's how:
1. get a bugzilla account if you do not have one.  https://bugzilla.redhat.com/
2. make sure the email you list in bugzilla matches the email you list in fas
3. request sponsorship to the fas group fedorabugs
4. ask stickster to approve fedorabugs and ask sparks to start
assigning you bugs :)
5.  starting fixing and closing bugs.

You do NOT need to own the bug to close it.  When it is closed the
assignee and the person that opened the bug will be notified, along
with anyone else on the cc list.  They will have the option to reopen
the bug if they have more information or do not believe it should have
been closed.

Do try to be polite and helpful when closing the ancient ones.  It is
ok to close as the doc is end of life but it is also nice to point out
the link to the current version and encourage more review and
reporting as needed.

I seem to recall some of this info in the wiki but not really easy to
find....  so fixing the docs on how to manage docs is also still a
needed....

>From the peanut gallery,
-Susan

-- 
Susan Lauber, (RHCX, RHCA, RHCSS)
Lauber System Solutions, Inc.
http://www.laubersolutions.com
gpg: 15AC F794 A3D9 64D1 D9CE  4C26 EFC3 11C2 BFA1 0974


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]