Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #61496 > unrolled thread
| Started by | Terry Reedy <tjreedy@udel.edu> |
|---|---|
| First post | 2013-12-10 13:39 -0500 |
| Last post | 2013-12-10 13:39 -0500 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Permission for contribution: http://bugs.python.org/issue19940 Terry Reedy <tjreedy@udel.edu> - 2013-12-10 13:39 -0500
| From | Terry Reedy <tjreedy@udel.edu> |
|---|---|
| Date | 2013-12-10 13:39 -0500 |
| Subject | Re: Permission for contribution: http://bugs.python.org/issue19940 |
| Message-ID | <mailman.3846.1386700788.18130.python-list@python.org> |
On 12/10/2013 6:35 AM, shankha wrote: > I wish to make contribution to Python source code. I have studied the > developers guide and made myself familiar with mercurial. I wish to > start of with some doc bugs as this will give me insight into > how the whole process(review, tests, patches) works. Is it okay if to take: > > http://bugs.python.org/issue19940. Follow the suggestion to join the core-mentorship list. I will just add here that issues are 'assigned' for review and commitment to one of the core developers with commit rights to the python.org repository. Anyone can submit a patch to the tracker. It is ok to post that you are working on an issue, if indeed you are. Perhaps about half the commits involve contributions from non-core developers. -- Terry Jan Reedy
Back to top | Article view | comp.lang.python
csiph-web