From Fedora Project Wiki

Line 1: Line 1:
{{needs love}}
{{needs love}}
== What we are working on now. ==
Once you have [[Join the Docs Project|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 [[Docs_Project#How_to_communicate_with_the_Docs_Project|talk with us]] and we'll help point you in the correct direction.
Also feel free to come to the [ next meeting.]

=== Task list ===
=== Task list ===
Line 15: Line 10:


== Bugs ==
== Bugs ==

Revision as of 19:12, 6 August 2013

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.
DocsProject Header docTeam1.png

Task list

Current Tasks needing to be worked:

Current Guides that need to be worked:


The documentation system migrated from Publican to Asciidoc. The active project list can be found on Pagure :

Old Guides


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.

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