Submitting

Differences between revisions 2 and 4 (spanning 2 versions)
Revision 2 as of 2008-10-15 20:52:20
Size: 1823
Editor: 79-72-17-225
Comment: use sysdoc menubar
Revision 4 as of 2011-05-12 04:46:45
Size: 2607
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
= Making a patch = = Submitting your Changes =
Line 9: Line 9:
Preparing a patch is easy. You can make a patch for a single file or a group of files that have been modified. The first step is to save your changes locally.
Line 12: Line 12:
 1. Issue the {{{bzr update}}} command. This updates your working copy with changes from the repository. Check for conflicts and resolve them.
 1. Issue the {{{bzr status}}} command. This shows the status of files. Ensure that all conflicts are resolved.
 1. Issue the command {{{bzr diff > diffname.txt}}}
 (!) If you wish to include your own name and a narrative for your change, you should create a ''bundle'' rather than a patch. To do this, issue these commands instead of the command at step 4 above:{{{
$ bzr commit -m "your narrative here"
 1. Issue the {{{bzr update}}} command. This updates your working copy with changes from the repository. Check for conflicts and resolve them. It is a good idea to ensure that your branch is up to date before editing any files.
 1. Issue the {{{bzr status}}} command. This shows the status of files which you have edited. Ensure that all conflicts are resolved.
 1. Commit your changes locally by running:{{{
$ bzr commit}}}
  bzr will prompt you to give a narrative to describe your change. Please be as detailed as possible. If your change addresses a Launchpad bug, include the bug number in the format "LP: #123456".

The next step is to publish your changes for the Documentation Team to review.
There are a few ways to submit your changes for review, the first way is through the mailing list:

 1. If your change is a small one, the simplest way to publish it is to create a "bundle" and email it to the Documentation Team or attach it to a bug report:{{{
Line 18: Line 23:
  This creates the file {{{diffname.txt}}}, which contains the differences between the working copy and repository revisions of the modified files.
 1. You should send the patch/bundle to the team [[DocumentationTeam/Contact|mailing list]] or attach it to a relevant bug report. If you have a mentor, copy them into the email and ask them to review it.
Line 19: Line 26:
This creates the file {{{diffname.txt}}}, which contains the differences between the working copy and repository revisions of the modified files. Another way it to publish them as a branch on Launchpad:{{{
$ bzr push lp:~yourusername/ubuntu-docs/branchname}}}
  "branchname" should be a short word which describes the branch. Usually your username will suffice.
Line 21: Line 30:
You should send the patch/bundle to the team [[DocumentationTeam/Contact|mailing list]] or attach it to a relevant bug report. If you have a mentor, copy them into the email and ask them to review it. And to get the attention of the Committers you can email the [[DocumentationTeam/Contact|mailing list]], request a branch merge, or contact the team members in #ubuntu-doc on irc.freenode.net

Submitting your Changes

Once you have made a change to a document and checked your work, the next step is to submit your change to the DocumentationTeam.

Note: It is generally a better idea to make several small changes and send them individually than it is to make one big change.

The first step is to save your changes locally.

  1. Go to the top level of the branch you are working on.
  2. Issue the bzr update command. This updates your working copy with changes from the repository. Check for conflicts and resolve them. It is a good idea to ensure that your branch is up to date before editing any files.

  3. Issue the bzr status command. This shows the status of files which you have edited. Ensure that all conflicts are resolved.

  4. Commit your changes locally by running:

    $ bzr commit
    • bzr will prompt you to give a narrative to describe your change. Please be as detailed as possible. If your change addresses a Launchpad bug, include the bug number in the format "LP: #123456".

The next step is to publish your changes for the Documentation Team to review. There are a few ways to submit your changes for review, the first way is through the mailing list:

  1. If your change is a small one, the simplest way to publish it is to create a "bundle" and email it to the Documentation Team or attach it to a bug report:

    $ bzr bundle > diffname.txt
    • This creates the file diffname.txt, which contains the differences between the working copy and repository revisions of the modified files.

  2. You should send the patch/bundle to the team mailing list or attach it to a relevant bug report. If you have a mentor, copy them into the email and ask them to review it.

Another way it to publish them as a branch on Launchpad:

$ bzr push lp:~yourusername/ubuntu-docs/branchname
  • "branchname" should be a short word which describes the branch. Usually your username will suffice.

And to get the attention of the Committers you can email the mailing list, request a branch merge, or contact the team members in #ubuntu-doc on irc.freenode.net

For more information about working with bzr, see the bzr website.

After you get used to DocBook, bzr and the DocumentationTeam, you are very likely to be offered an account so that you can write to the repository as well.

DocumentationTeam/SystemDocumentation/Submitting (last edited 2014-07-02 21:59:17 by knome)