Docs Project tasks for students
From FedoraProject
Easy - Content focused tasks
These are content tasks ...
- Research
- Writing
- Editing
- Testing
- Publishing
... of Fedora-specific content on the wiki and as formal, translated guides.
Wiki gardening
Having a great wiki is like having a great garden. It needs regular care and maintenance, and occasional big pruning jobs.
Wiki_gardening_tasks is a master task list arranged by difficulty. Some highlights from there are:
Fact check a document
Installation Guide
This guide takes a reader through the flow of installation. It is mainly textual instructions and no screenshots. This makes it more useful, easier to translate, and more encompassing of the topic. The guide is maintained in DocBook XML, but guide testing and fact checking can be done without editing the XML.
Team: User:????
Task tracking: https://fedorahosted.org/install-guide
User Guide
The User_Guide focuses on common features and tasks such as email, web browsing, office productivity, managing software, using cameras, and other desktop applications. The content includes coverage of the three Fedora desktop environments: GNOME, KDE, and XFCE. In addition, the command line may be covered. Most of the tasks do not require the root password.
Work is currently underway to complete and publish a Fedora 9 User Guide. Then the content is reused, updated, and expanded for the Fedora 10 User Guide.
Team: User:????
Task tracking:User Guide tasks
Release Notes
Fedora release notes are the best release notes of any Linux distribution. This is accomplished by gathering the work of many contributors via the wiki, then converting that work to DocBook XML for translation and building in to HTML, PDF, text, and the fedora-release-notes package.
Team: User:????
Task tracking: https://fedorahosted.org/release-notes
Packaging Guide
The PackagingGuidelines need reorganizating, rewriting, and probably conversion to XML for translation. This work includes working closely with the Packaging Committee.
Team: User:????
Task tracking: https://fedorahosted.org/packaging-guide (not created yet)
Virtualization Guide
This is a proposed guide needing a team to work on it.
Team: User:????
Task tracking: https://fedorahosted.org/virtualization-guide (not created yet)
README -- from fedora-release package
This small but important document appears in the fedora-release
Team: User:????
Task tracking: https://fedorahosted.org/readme
Readme-burning-isos -- ISO burning how-to
Team: User:????
Task tracking: https://fedorahosted.org/readme-burning-isos
Readme-live-image -- README for live image
Team: User:????
Task tracking: https://fedorahosted.org/readme-live-image
homepage -- offline default page in browser
Team: User:????
Task tracking: https://fedorahosted.org/homepage
Document may be deprecated, research needed - quaid 23:45, 23 September 2008 (UTC)
Installation Guide testing
Team: User:????
Task tracking:Installation Guide tasks#Installation testing
How to file a bug report
A bugzilla guide for Fedora. Good task to learn from for a new user.
Writer"" User:danielsmw
Easy - Project admin tasks
Docs Project admin tasks for new contributors
Hard - Content focused tasks
These writing, editing, and publishing tasks require some familiarity with Fedora and/or the Docs Project. These are highlights of the most important currently. Check Category:Docs Project content tasks for experienced contributors for additional tasks and details not highlighted here.
Release notes - lead writer
Assignee:None
Team: Jason Taylor
Task tracking: https://fedorahosted.org/release-notes
Installation Guide - lead writer
Assignee:David Nalley
Task tracking: https://fedorahosted.org/install-guide
Packaging Guide
Docs Project Lead: Susan Lauber
Team:
Task tracking:Docs tasks for Packaging Guide and related materials
User Guide - lead writer
Assignee:Matthew Daniels
Task tracking:User Guide tasks
Bug triage
Assignee: Jason Taylor
Team:
Task tracking:Docs bug triage tasks
Virtualization Guide
'Assignee:
Task Tracking:Virtualization Guide Tasks
RPM Guide
This content has languished for a while, still has relevant bits, and can be picked up as a contribution with the upstream http://rpm.org.
http://docs.fedoraproject.org/drafts/rpm-guide-en/
This outdated guide continues to be the top hit for the search 'rpm guide' at google.com.
http://www.google.com/search?q=rpm+guide
Team:
Task Tracking: https://fedorahosted.org/rpm-guide
Linux Security Guide - Sparks
Task Tracking:
Hard - Project admin tasks
Task table
This table may be transcluded in other locations, but originates at Docs_Project_admin_tasks_for_experienced_contributors#Task_table.
| Task | Assignee | Due date | Next milestone | Status |
|---|---|---|---|---|
| Update helping-hand docs | quaid, stickster, jsmith | Overdue | ? | Review, organize, rewrite, simplify, and categorize Docs team helper docs -- waiting on page renaming and categorization |
| Toolchain next steps | quaid, stickster, jsmith | Ongoing | ? | Sorting out what fedora-doc-utils does, where to use Publican, etc. -- Principals to discuss status, progress, direction on IRC. |
| CMS for docs.fp.org | ke4qqq | Overdue | ? | Zikula chosen, working on test instances and project plan with Zikula team |
| Student mentoring | quaid, ke4qqq | Ongoing | Ongoing | Focus on wiki and entry tasks; regular check-ins; keep scope and choices narrow where there is lots of room to succeed and learn; FLOSS Proj Mgmt session at FUDCon? |
Migrating away from Docs CVS and into Fedora Hosted
- Create a bug in bugzilla for each guide currently in Docs CVS that hasn't been migrated
- Make new project for each guide (follow Release Notes model)
- Follow the guide for porting docs to Publican (Do we need this guide? I think everything is ported to Publican although lots of stuff is still languishing in CVS)--McD
- Close bug
