Raindrop/Hacking: Difference between revisions

Jump to navigation Jump to search
(Created page with '== Opportunities == Want to play with Raindrop code and make it better? Here are some resources that will help you get started along with specific notes about where we need the …')
 
Line 32: Line 32:


If the change is very small, then creating a patch file is sufficient, and let us know where to pick it up on the [[Raindrop/Community|Raindrop discussion list]].
If the change is very small, then creating a patch file is sufficient, and let us know where to pick it up on the [[Raindrop/Community|Raindrop discussion list]].
Be sure to match the [[Raindrop/CodeStyle|Code Style]].


If it is a larger change, be sure to sign a [http://www.mozilla.org/hacking/committer/ Mozilla Contributor Agreement] and do the following:
If it is a larger change, be sure to sign a [http://www.mozilla.org/hacking/committer/ Mozilla Contributor Agreement] and do the following:
* read about [http://stevelosh.com/blog/entry/2009/8/30/a-guide-to-branching-in-mercurial/ creating named branches in Mercurial].
* Create a clone of the repo, and do the changes.
* Do the work on your named branch.
* Push the code to a publicly-visible area, like [http://bitbucket.org/ BitBucket].
* Tell us the location of the branch so we can do pulls and iterate on changes.
* Tell us the location of the clone so we can do pulls and iterate on changes.
* Use hg commit --close-branch to kill the branch once your changes have been pulled into the main repository.


== Talking about the code ==
== Talking about the code ==


To talk about the code or ask questions, see the [[Raindrop/Community|Community]] page.
To talk about the code or ask questions, see the [[Raindrop/Community|Community]] page.
109

edits

Navigation menu