Line 24: | Line 24: | ||
{{admon/tip|Use The List|If you have ''any'' problems with the following steps, post a question to the [https://listman.redhat.com/mailman/listinfo/fedora-docs-list list] . The members are happy to help you with any problems you might have, and you will likely get an answer in just a few minutes or hours.}} | {{admon/tip|Use The List|If you have ''any'' problems with the following steps, post a question to the [https://listman.redhat.com/mailman/listinfo/fedora-docs-list list] . The members are happy to help you with any problems you might have, and you will likely get an answer in just a few minutes or hours.}} | ||
=== For beginners === | |||
To get started make sure you've complete these steps: | To get started make sure you've complete these steps: | ||
* Join the [https://www.redhat.com/mailman/listinfo/fedora-docs-list mailing list] and send a [[DocsProject/SelfIntroduction| self introduction]] | * Join the [https://www.redhat.com/mailman/listinfo/fedora-docs-list mailing list] and send a [[DocsProject/SelfIntroduction| self introduction]] to tell the list who you are, your skills and abilities, and what you'd like to help accomplish. | ||
* Register for a [https://bugzilla.redhat.com/ Bugzilla] account. | * Register for a [https://bugzilla.redhat.com/ Bugzilla] account. This account gives you the ability to file and respond to documentation bugs. | ||
* Register for a Project account at https://admin.fedoraproject.org/accounts/ | * Register for a Fedora Project account at https://admin.fedoraproject.org/accounts/ using the same email address as your Bugzilla account. This account gives you the ability to edit this wiki, as well as other benefits and the ability to collaborate on other teams. | ||
=== For more advanced contributors === | |||
* Make a SSH (RSA) keypair and a GPG keypair. Visit the [[Cryptography]] page for more information and instructions. These keys let you communicate securely with Fedora Project servers, which helps you work directly on source code and documentation kept there. | |||
<!-- Why is a further checklist needed? --> | |||
To read the whole checklist of steps at once, visit [[DocsProject/Join/CheckList| the checklist]] . | To read the whole checklist of steps at once, visit [[DocsProject/Join/CheckList| the checklist]] . | ||
Revision as of 23:06, 30 December 2008
Joining the Fedora Documentation Project
The DocsProject adheres to the same standards as the rest of the Fedora Project, which means there is a certain amount of formal process. Don't let this put you off, however. Whatever your goals or skill level, you are more than welcome on the list or in any of our other forums.
How You Can Help
There are plenty of ways you can help:
- Joining the authors already working on our current documents in progress
- Writing new documents
- Volunteering to edit draft documents
- Providing feedback on current documents: final, draft or otherwise
Still undecided about whether to join? Read Why you should join the Docs Project!
Signing Up
For beginners
To get started make sure you've complete these steps:
- Join the mailing list and send a self introduction to tell the list who you are, your skills and abilities, and what you'd like to help accomplish.
- Register for a Bugzilla account. This account gives you the ability to file and respond to documentation bugs.
- Register for a Fedora Project account at https://admin.fedoraproject.org/accounts/ using the same email address as your Bugzilla account. This account gives you the ability to edit this wiki, as well as other benefits and the ability to collaborate on other teams.
For more advanced contributors
- Make a SSH (RSA) keypair and a GPG keypair. Visit the Cryptography page for more information and instructions. These keys let you communicate securely with Fedora Project servers, which helps you work directly on source code and documentation kept there.
To read the whole checklist of steps at once, visit the checklist .
Familiarize Yourself
To maintain a consistent style across all the docs, all contributors follow certain guidelines in our writings. The Docs Project also has work flows which help avoid clashing when working on docs together. Take some time to familiarize yourself with these practices before committing any changes, to make collaboration easy:
These are the important guidelines that will help you get started quickly. For a comprehensive collection of links relating to the DocsProject methods visit DocsProject/CompleteReference .