To co-ordinate the project, Launchpad is used. Launchpad can be found at http://launchpad.net, for Systers project on Launchpad, please visit https://launchpad.net/systers
To be able to begin using Launchpad, you need to register an account or a login. This can be done entering https://launchpad.net/systers/+login After having an account, let Jennifer know so that she can add you to the Systers-dev group. After registring, you need to add a SSH key to be able to upload code to a branch. This can be done from your user account, editing the user. For example, adding another SSH key could (for me) be done entering https://launchpad.net/~anna-granudd/+editsshkeys
Combined with using Launchpad, Bazaar is used. The commands for Bazaar all begin with bzr followed by the command requested. For instance, to get a certain branch, users can enter bzr branch or bzr checkout followed by, for instance, lp:systers for the main branch. More information about this can be found under http://systers.org/systers-dev/doku.php/tips_and_tricks_for_using_bazaar and http://systers.org/systers-dev/doku.php/commits_pulls_merges_and_pushes_to_bazaar To see the difference between diffrent pieces of code, the diff command can be used. Just typing bzr diff will show the difference between the code in the directory you currently are and the corresponding branch on Launchpad (it only works if you have created a branch to this directory). The diff command can also be used, for instance, to see the difference between certain revisions of the code or locall files.
Commits can be done locally but generally needs to be done globally. For more information how to do this, see http://systers.org/systers-dev/doku.php/commits_pulls_merges_and_pushes_to_bazaar
The different branches of Systers code can be found under https://code.launchpad.net/systers Merging diffrent branches of code is done by Jen. You might get a request to approve of a suggested merge if you stand as owner of a branch but she is normally responsible for this. To regiser a branch (might be good if, for instance, a certain fix for a bug needs to be done separatley), visit https://code.launchpad.net/systers/+addbranch and follow the instructions. Revisions done in a branch can be viewed online. By clicking on the numbers related to each revision the files that were changed will be visible and again clicking on a certain file will show the changes done to that file.
The bugs related to Systers can be found under https://bugs.launchpad.net/systers, it is likely a good idea to filter them and view those marked as open. Please subscribe to bugs of interest, for instance if you intend to work on one. This will make sure you get a email notification each time a change to that bug was done. If something is unclear or if you have thoughts or ideas for a bug, you can leave a comment in it. In the comments you can also attach files. If you have fixed a bug, please attach a test, possibly a manuell one, so that others can test your solution as well. In the status bar of a bug, you can change its assignee or its status. After fixing a bug and making a commit with it, please change the status of the bug to be “Fix commited”. If you discover a new bug, you can register it at https://code.launchpad.net/systers/+filebug Try to be as precise in your description of the bug as you can and if you can, explain how to reproduce it. If you have any ideas how to solve the bug or what might be the cause of it you can include that as well.
To get more tips on how to use Launchpad, please visit http://help.launchpad.net/