From Fedora Project Wiki

(→‎Admin tasks: Cleaned up some wiki-links here)
Line 36: Line 36:
These tasks make Docs happen -- tools, project management, leadership
These tasks make Docs happen -- tools, project management, leadership


* [[Docs_Project_admin_tasks_for_new_contributors]]
* [[Docs_Project_admin_tasks_for_new_contributors|Tasks for new contributors]]
* [[Docs_Project_admin_tasks_for_experienced_contributors]]
* [[Docs_Project_admin_tasks_for_experienced_contributors|Tasks for experienced contributors]]


[[Category:Docs Project]]
[[Category:Docs Project]]

Revision as of 23:37, 9 July 2010

This page needs some love
This page should be revised or reconstructed to be more helpful. Problems may include being out of step with current team or project status or process.

Once you have joined the Docs Project you are free to work on any project or task we might have. If you aren't sure where you'd best fit please feel free to talk with us and we'll help point you in the correct direction.

What we are working on now.

Come to the next meeting. Here we update the task list weekly.

Task list

We use Red Hat's Bugzilla instance for tracking issues and tasks within the Docs Project. It is always helpful to provide input and patches to bugs.

You can query Bugzilla or use one of the following links to find tickets that are open:


Content tasks

These tasks are for the creation of content -- research, writing, editing, and publishing.

Tasks for students

The page for these tasks pulls in lists from the content and admin tasks. Students are equal contributors so do not have a separate task/tracking page. This page is an aggregate to draw attention to specific areas for interested students. This list is currently focused toward students involved in a class using open source in the curriculum. (Experimental idea quaid 18:46, 3 September 2008 (UTC))

Admin tasks

These tasks make Docs happen -- tools, project management, leadership