Jump to content

Contributing to Python: Difference between revisions

no edit summary
imported>Jesstess
No edit summary
imported>Jesstess
No edit summary
Line 81:
Don't worry if this doesn't feel fully digested yet! The process will become clearer with practice.
 
== Goal #3: submitpick a patchbug forto awork Python bugon ==
 
It's time to pick a Python bug to work on! Visit http://bugs.python.org/ and browse for one that looks good.
 
It's a bit of an art to determine if a bug is good for a new contributor, so here are some suggestions:
 
First, the developer guide suggests 2 good areas for first-time contributors:
 
# Documentation: http://docs.python.org/devguide/docquality.html
# Test coverage: http://docs.python.org/devguide/coverage.html
 
If those sound interesting to you, look for issues in those areas.
 
Next, for the office hours on Sunday, March 9th, we'll have a list of beginner-friendly bugs. Check back in here on Sunday to review that list.
 
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 ==
 
Submit a patch for a Python bug.
 
== Goal #45: start working on your application ==
 
Let the core mentorship mailing list know that you've submitted your patch and are ready to work on your application. We'll craft an application together for a project that fits your background and interests and what you want to learn this summer!
Anonymous user
Cookies help us deliver our services. By using our services, you agree to our use of cookies.