Hi,
after the meeting on sunday people said it was probably best to carry out discussions about the DUG and the Admin Guide on the list so...
I was wondering what the current state of these guides is? What needs doing? etc
Also, what needs doing to create the new "todo" list style page?
Kind regards,
Jon
Hi Jon:
I joined the project to work on Administration Guide 10 days ago, but before start writing, I'm getting skills on emacs, doc book and knowledge about Red Hat documentation rules and other issues. If you want, we can split topics and write the manual together.
Robert Pereira
Em Ter, 2007-04-24 às 15:21 +0100, Jonathan Roberts escreveu:
Hi,
after the meeting on sunday people said it was probably best to carry out discussions about the DUG and the Admin Guide on the list so...
I was wondering what the current state of these guides is? What needs doing? etc
Also, what needs doing to create the new "todo" list style page?
Kind regards,
Jon
I joined the project to work on Administration Guide 10 days ago, but before start writing, I'm getting skills on emacs, doc book and knowledge about Red Hat documentation rules and other issues. If you want, we can split topics and write the manual together.
I'm not sure how far my skills will stretch with regard to admin tasks, my level of ability is more desktop and some lighter admin tasks - though I like to think improving all the time :D
I'm quite willing to help out however I'm needed with the admin guide though so if you do need any help post here and let us know!
Jon
On Tue, 2007-04-24 at 15:21 +0100, Jonathan Roberts wrote:
Also, what needs doing to create the new "todo" list style page?
Let me address just this one; I've been too busy this week to make progress on it.
We have two pages:
http://fedoraproject.org/wiki/DocsProject/SteeringCommittee/TaskSchedule http://fedoraproject.org/wiki/DocsProject/Tasks
What needs to happen is:
1. DocsProject/SteeringCommittee/TaskSchedule (DP/SC/TS) needs to be combined into a new DocsProject/Task (DP/T) list. The new list (which can use the similar table format) should have "skill" or "experience" level as a column, so we can identify items that require e.g. FDSCo action. Otherwise, it is a master, project-wide list
2. DP/SC/TS then needs to be setup for redirect to DP/T
3. The content currently on DP/T needs to be: i. Reviewed for relevancy ii. Relevant content moved to DocsProject/WorkFlow
4. We need to populate DP/T
5. If a task has sub-tasks, it can get a page in the same namespace, then have another table of all the sub-tasks; this keeps the main task page clean. E.g., DocsProject/Tasks/WikiCleanup
I think that's it. Anything I missed?
- Karsten