Roundup Robot added the comment:
New changeset ec52e044421d by Nick Coghlan in branch 'default':
Close #13440 by linking to a couple of blog posts from the dev FAQ. Also
rearrange the main page a bit to address some other concerns that came up on
the tracker issue
Mike Hoy added the comment:
Patch affects faq.rst/index.rst. In faq I put the two links along with some
text as Chris suggested. In index I changed resources to Additional Resources
and split up the old 'Resources' into 'Additional Resources/Essential Reading'.
Feedback appreciated I will
Chris Jerdonek added the comment:
I'll say it again, the devguide should be short enough to be practical for
someone learning to contribute.
Better organization could help here. I could see the devguide being a
combination of (1) a brief document meant to be read cover to cover that
Chris Jerdonek added the comment:
Would this be the appropriate place for the links to the two essays:
Personally, I would start out with a question in the FAQ. It could be called
something like, When is a change to Python justified? and go after or in the
same section as the question,
Nick Coghlan added the comment:
I'd suggest two things:
Clearly separate Essential Reading and Additional Resources headings on
the main page.
Add Tips Tricks and Design Philosophy sections somewhere.
--
___
Python tracker rep...@bugs.python.org
Mike Hoy added the comment:
Would this be the appropriate place for the links to the two essays:
http://docs.python.org/devguide/#proposing-changes-to-python-itself
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13440
Mike Hoy added the comment:
I'd be willing to make a patch for this if you are agreed to just adding a
couple of links to it (or otherwise).
--
nosy: +mikehoy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13440
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
keywords: +easy
type: - enhancement
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13440
___
Antoine Pitrou added the comment:
What would be the benefit of adding this to the devguide?
I'll say it again, the devguide should be short enough to be practical for
someone learning to contribute. It is quite wordy already.
--
nosy: +pitrou
___
Terry J. Reedy added the comment:
Maybe just add links to the two essays.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13440
___
___
Changes by Chris Jerdonek chris.jerdo...@gmail.com:
--
nosy: +cjerdonek
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13440
___
___
Changes by Tshepang Lekhonkhobe tshep...@gmail.com:
--
nosy: +tshepang
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13440
___
___
Terry J. Reedy tjre...@udel.edu added the comment:
Or expand 'Reporting Bugs' to 'Reporting Bugs and Requesting Features', perhaps
renamed to 'Suggesting Improvements'. My point is that aspiring developers are
not the only one that need to read the guideline, not withstanding the fact the
Éric Araujo mer...@netwok.org added the comment:
+1
--
nosy: +eric.araujo
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13440
___
___
New submission from Nick Coghlan ncogh...@gmail.com:
I've linked
http://www.boredomandlaziness.org/2011/02/status-quo-wins-stalemate.html in
response to enough tracker issues and python-ideas threads now, that I'm
convinced it (or at least something along those lines) belongs in the devguide.
15 matches
Mail list logo