Fork us on GitHub Follow us on Facebook Follow us on Twitter

Changes between Version 7 and Version 8 of HowToContribute


Ignore:
Timestamp:
2010-01-06T22:33:43Z (9 years ago)
Author:
Jiri Svoboda
Comment:

Grammar etc.

Legend:

Unmodified
Added
Removed
Modified
  • HowToContribute

    v7 v8  
    11= How to contribute =
    22
    3 We are welcoming any effort to make HelenOS a better operating system. Here are some tips on what to do when you feel like contributing code.
     3We welcome any effort to make HelenOS a better operating system. Here are some tips on what to do when you feel like contributing code.
    44
    55== Ideas to work on ==
     
    1717== Working on your branch ==
    1818
    19 Now that you know what to do, you should go and create your private [wiki:BazaarWorkflow bzr branch] of HelenOS. This is essential so that we can later merge your changes together with your initials in the development history of the branch. During the coding phase, bare in mind that we will require your changes to meet our coding style standards. It will happen to you from time to time that you will need to consult something with the other people from the project. Don't be shy and feel free to discuss things with us either in the mailing list or on the IRC. For example, you can create a merge directive in bzr and send it to the mailing list for code review. Make smaller, logically related changesets rather than one huge. Make sure that each changeset is accompanied by a clear commit log in English.
     19Now that you know what to do, you should go and create your private [wiki:BazaarWorkflow Bazaar branch] of HelenOS. This is essential so that we can later merge your changes together with your initials in the development history of the branch. During the coding phase, keep in mind that we will require your changes to meet our coding style standards. It will happen to you from time to time that you will need to consult something with the other people from the project. Don't be shy and feel free to discuss things with us either in the mailing list or on IRC. For example, you can create a merge directive in Bazaar and send it to the mailing list for code review. Make smaller, logically related changesets rather than one huge changeset. Make sure that each changeset is accompanied by a clear commit message in English.
    2020
    2121== Integrating your changes ==
    2222
    23 When you tested your changes carefully and are confident enough that there are no bugs, you can ask someone from us to merge your changes. For that, you need to do one of two things. You either send us your final bzr merge directive or publish your branch in a publicly accessible location (e.g. Launchpad) so that we can merge from there. Note that publishing your branch is a good idea anyway because others can see your progress and your changes are backed up. Eventually, if your changes look good to us, we will merge them and you will become part of the history.
     23When you have tested your changes carefully and are confident enough that there are no bugs, you can ask one of us to merge your changes to our official repository. For that, you need to do one of two things. Either send us your final Bazaar merge directive or publish your branch in a publicly accessible location (e.g. Launchpad) so that we can merge from there. Note that publishing your branch is a good idea anyway because others can see your progress and your changes are backed up. Eventually, if your changes look good to us, we will merge them and you will become part of the history.