[issue13440] Explain the "status quo wins a stalemate" principle in the devguide

2012-10-19 Thread Roundup Robot
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 http://hg.python.org/devguide/

[issue13440] Explain the "status quo wins a stalemate" principle in the devguide

2012-10-12 Thread Mike Hoy
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 inco

[issue13440] Explain the "status quo wins a stalemate" principle in the devguide

2012-10-11 Thread Nick Coghlan
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

[issue13440] Explain the "status quo wins a stalemate" principle in the devguide

2012-10-11 Thread Chris Jerdonek
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, "W

[issue13440] Explain the "status quo wins a stalemate" principle in the devguide

2012-10-11 Thread Chris Jerdonek
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 capt

[issue13440] Explain the "status quo wins a stalemate" principle in the devguide

2012-10-10 Thread Mike Hoy
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 __

[issue13440] Explain the "status quo wins a stalemate" principle in the devguide

2012-09-26 Thread Mike Hoy
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 ___

[issue13440] Explain the "status quo wins a stalemate" principle in the devguide

2012-09-23 Thread Chris Jerdonek
Changes by Chris Jerdonek : -- nosy: +cjerdonek ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue13440] Explain the "status quo wins a stalemate" principle in the devguide

2012-09-23 Thread Terry J. Reedy
Terry J. Reedy added the comment: Maybe just add links to the two essays. -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue13440] Explain the "status quo wins a stalemate" principle in the devguide

2012-09-23 Thread Antoine Pitrou
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 ___ Pyt

[issue13440] Explain the "status quo wins a stalemate" principle in the devguide

2012-09-23 Thread Ezio Melotti
Changes by Ezio Melotti : -- keywords: +easy type: -> enhancement ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscrib

[issue13440] Explain the "status quo wins a stalemate" principle in the devguide

2012-01-11 Thread Tshepang Lekhonkhobe
Changes by Tshepang Lekhonkhobe : -- nosy: +tshepang ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue13440] Explain the "status quo wins a stalemate" principle in the devguide

2011-11-25 Thread Terry J. Reedy
Terry J. Reedy 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 some new developers

[issue13440] Explain the "status quo wins a stalemate" principle in the devguide

2011-11-22 Thread Éric Araujo
Éric Araujo added the comment: +1 -- nosy: +eric.araujo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:/

[issue13440] Explain the "status quo wins a stalemate" principle in the devguide

2011-11-20 Thread Nick Coghlan
New submission from Nick Coghlan : 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. It wouldn't hurt