diff options
Diffstat (limited to 'doc/contributing.rst')
-rw-r--r-- | doc/contributing.rst | 26 |
1 files changed, 9 insertions, 17 deletions
diff --git a/doc/contributing.rst b/doc/contributing.rst index 1a74ca8..ac96fcb 100644 --- a/doc/contributing.rst +++ b/doc/contributing.rst @@ -2,26 +2,19 @@ Contributing to nose ==================== You'd like to contribute to nose? Great! Now that nose is hosted under -`Mercurial <http://selenic.com/mercurial/>`__, contributing is even easier. +`GitHub <http://github.com/>`__, contributing is even easier. Get the code! ------------- -Start by getting a local working copy of nose, either stable, from google code:: +Start by getting a local working copy of nose from github:: - hg clone http://python-nose.googlecode.com/hg/ nose-stable - -or unstable, from bitbucket:: - - hg clone http://bitbucket.org/jpellerin/nose/ nose-unstable + git clone https://github.com/nose-devs/nose If you plan to submit changes back to the core repository, you should set up a -public repository of your own somewhere. `Bitbucket <http://bitbucket.org>`__ -is a good place to do that. Once you've set up your bitbucket nose repository, -if working from **stable**, pull from your working copy of nose-stable, and push -to bitbucket. That (with occasional merging) will be your normal practice for -keeping your repository up to date. If you're on bitbucket and working from -**unstable**, just **fork** http://bitbucket.org/jpellerin/nose/. +public fork of your own somewhere (`GitHub <http://github.com/>`__ is a good +place to do that). See GitHub's `help <http://help.github.com/>`__ for details +on how to contribute to a Git hosted project like nose. Running nose's tests -------------------- @@ -42,11 +35,10 @@ low-traffic and mostly signal. What to work on? ---------------- -You can find a list of open issues at nose's `google code repository -<http://code.google.com/p/python-nose/issues>`__. If you'd like to +You can find a list of open issues at nose's `issue tracker +<http://github.com/nose-devs/nose/issues>`__. If you'd like to work on an issue, leave a comment on the issue detailing how you plan -to fix it, and where to find the Mercurial repository where you will -publish your changes. +to fix it, or simply submit a pull request. I have a great idea for a plugin... ----------------------------------- |