SystemDocumentation

Differences between revisions 32 and 33
Revision 32 as of 2014-07-02 21:24:43
Size: 4679
Editor: belkinsa
Comment:
Revision 33 as of 2014-07-02 21:33:22
Size: 3281
Editor: knome
Comment:
Deletions are marked like this. Additions are marked like this.
Line 13: Line 13:
 * '''Proof-reading''' is an important and easy way to help. You only need to follow the instructions, click the links and check spelling and grammar! Once you find a mistake, report a bug so the team can start working on it. Also see the [[DocumentationTeam/TechReview|Technical Review page]] for information on technical reviewing and proof-reading.

==== Making Suggestions ====

You can file bug reports on [[https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/|Launchpad]] if you find a problem. See [[https://help.ubuntu.com/community/ReportingBugs|Reporting Bugs]] for more information on how to file bugs correctly.

Alternatively, you can make suggestions on improving the documentation on the [[https://lists.ubuntu.com/mailman/listinfo/ubuntu-doc|Documentation Team mailing list]].

==== Submitting Material ====

To submit new material for a particular part of the system documentation, you can simply send the text that you propose to submit to our [[DocumentationTeam/Contact|mailing list]]. One of the team members will take care of adapting the text that you submit to the format that we use for System Documentation. In this way, you don't need to learn our tools to contribute regularly. However, to effectively contribute to the system documentation, you are encouraged to learn tools that the team uses.

Please remember when submitting material for transcription to DocBook or [[http://projectmallard.org/index.html|Mallard]] that it will take time for a member to convert your materials. In most cases, your contribution will be in the next release of Ubuntu.

It is also helpful to [[https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs|file a bug]] and post your material there. That way, we can't miss it!

==== Submitting Patches ====

To submit your work for direct incorporation into the Ubuntu documentation, you need to get hold of the raw materials that we work with. With these materials, you can make changes and submit your changes to the team.

Download the [[attachment:BugsPlaybook.pdf | Playbook]] - a single sheet guide to fixing bugs!

For more details about how to contribute directly to the System Documentation, read the following sections and the pages linked there!
 * '''Proof-reading''' is an important and easy way to help. You only need to follow the instructions, click the links and check spelling and grammar! Also see the [[DocumentationTeam/TechReview|Technical Review page]] for information on technical reviewing and proof-reading.
 * '''File bug reports''' on the documentation when you find mistakes. See [[https://help.ubuntu.com/community/ReportingBugs|Reporting Bugs]] for more information on reporting bugs.
 * '''Submit patches''' to fix bugs in the documentation.
 * '''Submit new material''' to the documentation. If you are just getting started, ask for help from other contributors and work with them to get your improvements in the next release of Ubuntu. If you start contributing regularly, you can learn to use the tools and ultimately be able to merge others' new material.

Inclusion deadlines for ImpishString Freeze: September 16, 2021 / Non-language packs: September 30, 2021

System Documentation

One of the major tasks of the Documentation Team is to take care of the documentation which comes with every Ubuntu system. This documentation is also available on https://help.ubuntu.com/.

In order to contribute to the system documentation, you need to know a bit about the tools and processes the team uses to maintain the documentation. Don't worry if you don't know any of our tools yet. They are very easy to learn and it's possible to make useful contributions before learning how to use all the tools.

How can I help?

The ways to help the Ubuntu Documentation team are almost limitless, but here's a short list of things you can start with:

  • Proof-reading is an important and easy way to help. You only need to follow the instructions, click the links and check spelling and grammar! Also see the Technical Review page for information on technical reviewing and proof-reading.

  • File bug reports on the documentation when you find mistakes. See Reporting Bugs for more information on reporting bugs.

  • Submit patches to fix bugs in the documentation.

  • Submit new material to the documentation. If you are just getting started, ask for help from other contributors and work with them to get your improvements in the next release of Ubuntu. If you start contributing regularly, you can learn to use the tools and ultimately be able to merge others' new material.

Getting Started

There are plenty of ways to get started with the team. For a quick summary of the process for each type of system documentation, refer to:

Repository

To make changes to the system documentation, you need to download the repository which stores the latest copy of the documentation. Like most Ubuntu projects, we store our material using the Bazaar (or bzr) version control system.

  • Detailed information on using the Bazaar branches and getting to our repository is on the /Repository page.

Docbook or Mallard?

While the serverguide is written in DocBook, the system documentation is written in Mallard. Both are similar to HTML and easy to learn and use.

  • The /Editing page details how to edit the documents.

  • The /Checking page explains how to view the files you have edited and to check your work.

Submitting Your Contribution

Once you have made a change to a document and checked your work, the next step is to send your contribution to the Documentation Team.

  • The /Submitting page explains how to send your contribution to the Documentation Team by creating a patch.

Tasks

The /Tasks page contains some ideas for working on the system documentation.

DocumentationTeam/SystemDocumentation (last edited 2015-01-09 18:41:02 by petermatulis)