From Fedora Project Wiki

(More clean up.)
(13 intermediate revisions by 4 users not shown)
Line 2: Line 2:
{{header|docs}}
{{header|docs}}


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.
=== Task list ===
Current Tasks needing to be worked:
* [[User:Sparks]] requested [http://lists.fedoraproject.org/pipermail/docs/2010-June/012434.html a How-To wiki page for editing IP Tables] - [http://fedoraproject.org/wiki/SystemConfig/firewall the firewall wiki should help]
 
* [[User:chrisroberts]] requested a grep guide for versioned docdirs, file bugs and patches https://fedoraproject.org/wiki/Changes/UnversionedDocdirs
** Now completed by [[User: sclark]]. [https://lists.fedoraproject.org/pipermail/docs/2014-February/015525.html See docs mailing list announcement].
 
* The storage guide is out of date, and users regularly ask if it will be updated. Someone needs to coordinate updates of this document, starting with contacting the Guide owner to find out their plans.
** We need a section on SSD functionality and optimization.
** NFSv4 is default since last publishing of this doc


== What we are working on now. ==
* Kickstart options need to be updated for F20 Installation guide. Coordinate with [[User: pbokoc]]


=== Task list ===


{{:Docs_Project_guides_table}}
== Bugs ==
We use [http://bugzilla.redhat.com 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.
We use [http://bugzilla.redhat.com 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.


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


* [[Docs_Project_content_tasks_for_new_contributors]] if you are just getting started in Docs.  It presents tasks without assignments as well as tracking active tasks, including small team projects.
* If you are just getting started in Docs.  It presents tasks without assignments as well as tracking active tasks, including small team projects.[[Docs_Project_content_tasks_for_new_contributors]]
 
* [[Docs_Project_content_tasks_for_experienced_contributors]] is where your tasks are tracked.
* [[Docs_Project_content_tasks_for_experienced_contributors]] is where your tasks are tracked.
* [[Wiki_gardening_tasks]] are for contributors of all levels.
* [[Wiki_gardening_tasks]] are for contributors of all levels.
=== 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 [[User:Kwade|quaid]] 18:46, 3 September 2008 (UTC))''
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 [[User:Kwade|quaid]] 18:46, 3 September 2008 (UTC))''
Line 32: Line 42:
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 20:10, 31 March 2014

Cog.png
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:

  • The storage guide is out of date, and users regularly ask if it will be updated. Someone needs to coordinate updates of this document, starting with contacting the Guide owner to find out their plans.
    • We need a section on SSD functionality and optimization.
    • NFSv4 is default since last publishing of this doc
  • Kickstart options need to be updated for F20 Installation guide. Coordinate with User: pbokoc


Guides

The documentation system migrated from Publican to Asciidoc. The active project list can be found on Pagure : https://pagure.io/fedora-docs/

Old Guides


Bugs

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