|
Size: 4269
Comment:
|
Size: 3868
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 19: | Line 19: |
| Please also note the following deadlines:https://wiki.gnome.org/OutreachProgramForWomen/2014/MayAugust#Schedule | Please also note the following deadlines: |
| Line 29: | Line 29: |
| 2. Read the Python developer guide: http://docs.python.org/devguide/ 3. Create an account on the Python bug tracker: http://bugs.python.org/ 4. Submit a patch for a Python bug (see the next section for help getting started) 5. 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! |
1. Read the Python developer guide: http://docs.python.org/devguide/ 1. Create an account on the Python bug tracker: http://bugs.python.org/ 1. Submit a patch for a Python bug (see the next section for help getting started) 1. 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! |
| Line 34: | Line 34: |
| = Preparing to apply = | = Submitting a patch for a Python bug = |
| Line 36: | Line 36: |
| Here are some of the tools we use: | == The tools of Python development == |
| Line 38: | Line 38: |
| IRC the Trac issue tracker the svn revision control system the diff and patch utilities If you have not used IRC before, please go through this short tutorial on installing and using an IRC client: https://openhatch.org/wiki/Open_Source_Comes_to_Campus/UMD/Laptop_setup#Goal_.233:_install_an_IRC_client |
Before you submit a patch, here are some of the tools we use that you may want to review or practice: |
| Line 44: | Line 40: |
| Please familiarize yourself with how Twisted uses Trac by exploring the reports from this link: http://twistedmatrix.com/trac/report | * IRC * bug trackers * the mercurial (hg) revision control system * the diff and patch utilities |
| Line 46: | Line 45: |
| With sufficient exploration you should be able to answer the following questions (you don't have to tell me the answers, just make sure you know how to find them): | === IRC === |
| Line 48: | Line 47: |
| What is the oldest open Twisted ticket? How many tickets are currently waiting on review? How do we denote tickets waiting on a review (hint: look at the keyword) Using the custom query page at http://twistedmatrix.com/trac/query, find out how many open tickets we have that have the "documentation" keyword. |
IRC is a real-time group chat system popular with many open source projects. Developers ask questions and discuss patches on IRC, and users also ask questions on IRC. Learn more about how Python uses IRC here: http://www.python.org/community/irc/. There are 3 main Python IRC channels, all on the Freenode IRC network, that you may be interested in: 1. <tt>#python-dev</tt>: for discussing the development of Python itself 1. <tt>#python</tt>: for asking and answering general Python questions 1. <tt>#pyladies</tt>: the main PyLadies IRC channel === Bug trackers === Python tracks bugs and features at http://bugs.python.org/. Please familiarize yourself with how Python uses its bug tracker by exploring and finding answers to the following questions: 1. What is the oldest open Python ticket? 1. How many open issues need a patch? 1. How many "critical"-level open issues are there? Also have a look at the Python bugs tagged as particularly good for new contributors: http://bugs.python.org/issue?status=1&@sort=-activity&@columns=id,activity,title,creator,status&@dispname=Easy%20issues&@startwith=0&@group=priority&keywords=6&@action=search&@filter=&@pagesize=50&priority=2 === Mercurial === |
| Line 53: | Line 74: |
| If you have not used diff and patch before, please go through the diff and patch training mission at: http://openhatch.org/missions/diffpatch | === diff and patch === |
| Line 55: | Line 76: |
| If you have any questions while going through this material, don't hesitate to ask for help in #twisted on IRC or on the twisted-python mailing list. | If you have not used diff and patch before, please go through the diff and patch training mission at: |
| Line 57: | Line 78: |
| Once you've gone through this material, the next steps will be to: Meet up on IRC (stop by the #twisted channel) Check out and explore the Twisted source code Read a few parts of the Twisted core documentation and run some example Twisted scripts Run the Twisted test suite - cd into the checkout folder and run "bin/trial twisted". And then you'll be in great shape to start working on your first Twisted ticket. We'll suggest a first ticket when you get in touch over email; you'd want to fix it in your Twisted svn checkout, run svn diff, upload the resulting patch to the ticket and then add the "review" keyword to the ticket. This process is described in detail here: http://twistedmatrix.com/trac/wiki/TwistedDevelopment#SubmittingaPatch |
http://openhatch.org/missions/diffpatch |
Join Python this summer!
This page coordinates the Python projects for the Summer 2014 session of the GNOME Outreach Program For Women.
What: Earn a $5500 USD stipend while contributing to the CPython language interpreter and related core packages.
When: This is a full-time summer internship lasting from May 19 - August 18.
Where: Anywhere! This is remote internship, with most communication happening on mailing lists, bug trackers, and IRC.
Who: This internship is open to anyone who identifies as a woman. Note that unlike Google Summer of Code, you do not need to be a student.
Applications are due by March 19th.
Prospective Applicants
If you are a woman interested in a paid summer internship doing core Python development, we'd love to have you apply to work with us in this summer's GNOME Outreach Program for Women!
Please read carefully through https://wiki.gnome.org/OutreachProgramForWomen for the full details on how the GNOME Outreach Program for Women works.
Please also note the following deadlines:
* until March 19: join the community and make at least 1 contribution * March 19: application deadline at 7pm UTC * April 21: accepted participants announced at 7pm UTC * May 19 - August 18: internship period
How to apply
1. Join the Python core mentorship mailing list and introduce yourself: https://mail.python.org/mailman/listinfo/core-mentorship. 1. Read the Python developer guide: http://docs.python.org/devguide/ 1. Create an account on the Python bug tracker: http://bugs.python.org/ 1. Submit a patch for a Python bug (see the next section for help getting started) 1. 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!
Submitting a patch for a Python bug
The tools of Python development
Before you submit a patch, here are some of the tools we use that you may want to review or practice:
* IRC * bug trackers * the mercurial (hg) revision control system * the diff and patch utilities
IRC
IRC is a real-time group chat system popular with many open source projects. Developers ask questions and discuss patches on IRC, and users also ask questions on IRC.
Learn more about how Python uses IRC here: http://www.python.org/community/irc/.
There are 3 main Python IRC channels, all on the Freenode IRC network, that you may be interested in:
1. <tt>#python-dev</tt>: for discussing the development of Python itself 1. <tt>#python</tt>: for asking and answering general Python questions 1. <tt>#pyladies</tt>: the main PyLadies IRC channel
Bug trackers
Python tracks bugs and features at http://bugs.python.org/.
Please familiarize yourself with how Python uses its bug tracker by exploring and finding answers to the following questions:
1. What is the oldest open Python ticket? 1. How many open issues need a patch? 1. How many "critical"-level open issues are there?
Also have a look at the Python bugs tagged as particularly good for new contributors: http://bugs.python.org/issue?status=1&@sort=-activity&@columns=id,activity,title,creator,status&@dispname=Easy%20issues&@startwith=0&@group=priority&keywords=6&@action=search&@filter=&@pagesize=50&priority=2
Mercurial
If you have not used svn before, please go through the svn training mission at: http://openhatch.org/missions/svn
diff and patch
If you have not used diff and patch before, please go through the diff and patch training mission at: