From Fedora Project Wiki

The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
DocsProject Header docTeam1.png


Procedure

  1. Search Bugzilla for bugs that need to be fixed.
  2. Once you have found a bug you want to work on, assign the ticket to yourself and update the status to ASSIGNED.
  3. Pull the source of the guide. All guides are in git on fedorahosted.org. To pull the code simply git clone git+ssh://<fasid>@git.fedorahosted.org/git/docs/<guide>.git.
  4. Create a new branch (you can replace bugfix with the bugzilla number or a name): git checkout -b bugfix
  5. edit the file appropriately
  6. Add the edited file: git add <file>
  7. Commit the file: git commit <file>
  8. Create the patch: git format-patch master
  9. Submit the patch to the bugzilla ticket and state that the ticket is ready for QA. Change the status to ON_QA.
  10. (Optional) delete your new branch with: git branch -d bugfix

The bug will now be in the hands of the QA people who will check the text for spelling and grammar problems, DocBook tags, and check procedures. Once complete the guide owner, or you, can publish the change and close the bug.

Retrieved from "https://fedoraproject.org/w/index.php?title=Fixing_documentation_bugs&oldid=269235"