Contributing to Python: Difference between revisions

no edit summary
imported>Jesstess
No edit summary
imported>Jesstess
No edit summary
Line 18:
* [[Contributing_to_Python/OSX IRC|OS X]]
* [[Contributing_to_Python/Linux IRC|Linux]]
 
 
== Goal #2: practice navigating from the command line ==
Line 28 ⟶ 29:
* [[Contributing_to_Python/OSX command line|OS X]]
* [[Contributing_to_Python/Linux command line|Linux]]
 
 
== Goal #3: Get familiar with the Python bug tracker ==
Line 40 ⟶ 42:
# How many open issues need a patch?
# How many "critical"-level open issues are there?
 
 
== Goal #4: practice using version control ==
Line 46 ⟶ 49:
 
If you have not used Mercurial before, please go through this tutorial: http://hginit.com/
 
 
== Goal #5: practice creating patches ==
Line 54 ⟶ 58:
 
http://openhatch.org/missions/diffpatch
 
 
= Part II: contributing to Python =
Line 65 ⟶ 70:
 
The core-mentorship mailing list will be our focus as we get settled in, so please [[https://mail.python.org/mailman/listinfo/core-mentorship|join the list]] now.
 
 
== Goal #2: read the developer guide ==
Line 88 ⟶ 94:
 
Don't worry if this doesn't feel fully digested yet! The process will become clearer with practice.
 
 
== Goal #3: pick a bug to work on ==
Line 105 ⟶ 112:
 
Finally, you can always ask for help or suggestions on the core-mentorship mailing list or in the <tt>#pyladies</tt> IRC channel.
 
 
== Goal #4: submit a patch for a Python bug ==
Line 111 ⟶ 119:
 
Make sure to run the test suite first and that the tests all still pass!
 
 
== Goal #5: start working on your application ==
Anonymous user