Public bug reported:

I'd like to change the intro from this:
If you followed the instructions to get set up with Ubuntu Development, you 
should be all set and ready to go.
(process to fix a bug image)
As you can see in the image above, there is no surprises in the process of 
fixing bugs in Ubuntu: you found a problem, you get the code, work on the fix, 
test it, push your changes to Launchpad and ask for it to be reviewed and 
merged. In this guide we will go through all the necessary steps one by one.


to this:
Once you're done Getting Set Up, you're ready to learn how to start fixing bugs.
<process to fix a bug image>
As you can see in the image above, the process of fixing bugs in Ubuntu is very 
simple:
        1) You find a problem
        2) You retrieve the relevant Ubuntu source code
        3) You fix the problem in the Ubuntu source code
        4) You test your fix
        5) You push your changes to Launchpad and ask for it to be reviewed, 
then merged.
In this guide, we will guide you through those steps.

This would improve readability of the section.

Additionally, 3.3 through 3.6 come between step 1 (find problem) and
step 2 (retrieve code). I'd like to make these sections sub-sections of
3.2.

** Affects: ubuntu-packaging-guide
     Importance: Undecided
     Assignee: Patrick Burke (tabbycat45)
         Status: New

** Changed in: ubuntu-packaging-guide
     Assignee: (unassigned) => Patrick Burke (tabbycat45)

-- 
You received this bug notification because you are a member of Ubuntu
Packaging Guide Team, which is subscribed to Ubuntu Packaging Guide.
https://bugs.launchpad.net/bugs/2000438

Title:
  3.1 - Intro - Clarity and Organization Improvements

Status in Ubuntu Packaging Guide:
  New

Bug description:
  I'd like to change the intro from this:
  If you followed the instructions to get set up with Ubuntu Development, you 
should be all set and ready to go.
  (process to fix a bug image)
  As you can see in the image above, there is no surprises in the process of 
fixing bugs in Ubuntu: you found a problem, you get the code, work on the fix, 
test it, push your changes to Launchpad and ask for it to be reviewed and 
merged. In this guide we will go through all the necessary steps one by one.

  
  to this:
  Once you're done Getting Set Up, you're ready to learn how to start fixing 
bugs.
  <process to fix a bug image>
  As you can see in the image above, the process of fixing bugs in Ubuntu is 
very simple:
        1) You find a problem
        2) You retrieve the relevant Ubuntu source code
        3) You fix the problem in the Ubuntu source code
        4) You test your fix
        5) You push your changes to Launchpad and ask for it to be reviewed, 
then merged.
  In this guide, we will guide you through those steps.

  This would improve readability of the section.

  Additionally, 3.3 through 3.6 come between step 1 (find problem) and
  step 2 (retrieve code). I'd like to make these sections sub-sections
  of 3.2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-packaging-guide/+bug/2000438/+subscriptions


_______________________________________________
Mailing list: https://launchpad.net/~ubuntu-packaging-guide-team
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~ubuntu-packaging-guide-team
More help   : https://help.launchpad.net/ListHelp

Reply via email to