Devguide - Add Communications Quick Start Section
I would like to add a "Communications Quick Start" section to the beginning of the Python Developer's Guide. Productive communication between each other will always be critical to future development of CPython and maintaining releases, infrastructure, documentation, and more. Unproductive communication saps energy of contributors, reduces engagement in the project, and limits creativity and fulfillment in contributing. As a contributor who finds great value in the power and zen of Python, I want to foster more effective and productive communication. I've been thinking about ways to do this since the PyCon sprints. New developers would benefit from understanding how to interact with the community and its norms. Existing contributors would hopefully benefit from less time reexplaining community communication norms. The Communications Quick Start section would be brief and practical much like the Quick Start section for downloading and testing the source code. Placing the Communications Quick Start section before the existing Quick Start section would emphasize the importance that productive communications has on CPython development. Thanks, Carol P.S. Thank you to all that devote time and energy to the development of CPython. I have posted this to the python-dev mailing list for feedback due to the recent discussions. Nick and Brett, please feel free to move this to python-ideas if you feel that would be a better place to discuss this addition to the devguide.
On Tue, Jul 21, 2015 at 11:05 AM Carol Willing < willingc@willingconsulting.com> wrote:
I would like to add a "Communications Quick Start" section to the beginning of the Python Developer's Guide.
Productive communication between each other will always be critical to future development of CPython and maintaining releases, infrastructure, documentation, and more.
Unproductive communication saps energy of contributors, reduces engagement in the project, and limits creativity and fulfillment in contributing. As a contributor who finds great value in the power and zen of Python, I want to foster more effective and productive communication. I've been thinking about ways to do this since the PyCon sprints. New developers would benefit from understanding how to interact with the community and its norms. Existing contributors would hopefully benefit from less time reexplaining community communication norms.
The Communications Quick Start section would be brief and practical much like the Quick Start section for downloading and testing the source code. Placing the Communications Quick Start section before the existing Quick Start section would emphasize the importance that productive communications has on CPython development.
Sounds great to me! Social norms are just as important to get to speed on as technical requirements when contributing to an open source community, so this seems like a worthy project.
Thanks, Carol
P.S. Thank you to all that devote time and energy to the development of CPython. I have posted this to the python-dev mailing list for feedback due to the recent discussions. Nick and Brett, please feel free to move this to python-ideas if you feel that would be a better place to discuss this addition to the devguide.
Nope, here is fine. This isn't a new idea and it affects people on this list more directly than the python-ideas folks.
On 22 July 2015 at 04:08, Brett Cannon <brett@python.org> wrote:
On Tue, Jul 21, 2015 at 11:05 AM Carol Willing <willingc@willingconsulting.com> wrote:
The Communications Quick Start section would be brief and practical much like the Quick Start section for downloading and testing the source code. Placing the Communications Quick Start section before the existing Quick Start section would emphasize the importance that productive communications has on CPython development.
Sounds great to me! Social norms are just as important to get to speed on as technical requirements when contributing to an open source community, so this seems like a worthy project.
+1 from me as well. The discussion of a more formal CoC on the python-committers list also highlighted for me that our main current problems don't appear to be with any ill-intent on anyone's part, but rather with well-intentioned messages that nevertheless have the effect of causing folks to feel unappreciated and resentful. A practical quick start guide is likely to be more effective in addressing that aspect than a more explicit CoC (although I still think the latter would be a good idea in the long run). Regards, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
On 7/21/15 9:31 PM, Nick Coghlan wrote:
On Tue, Jul 21, 2015 at 11:05 AM Carol Willing <willingc@willingconsulting.com> wrote:
The Communications Quick Start section would be brief and practical much like the Quick Start section for downloading and testing the source code. Placing the Communications Quick Start section before the existing Quick Start section would emphasize the importance that productive communications has on CPython development.
Sounds great to me! Social norms are just as important to get to speed on as technical requirements when contributing to an open source community, so this seems like a worthy project. +1 from me as well. The discussion of a more formal CoC on the
On 22 July 2015 at 04:08, Brett Cannon <brett@python.org> wrote: python-committers list also highlighted for me that our main current problems don't appear to be with any ill-intent on anyone's part, but rather with well-intentioned messages that nevertheless have the effect of causing folks to feel unappreciated and resentful. A practical quick start guide is likely to be more effective in addressing that aspect than a more explicit CoC (although I still think the latter would be a good idea in the long run).
Regards, Nick.
I have created an issue<http://bugs.python.org/issue24682> on the Quick Start: Communications section. Please feel free to add further suggestions there. Thanks for the support. Terry, I like your suggested wording :)
On 7/21/2015 1:06 PM, Carol Willing wrote:
I would like to add a "Communications Quick Start" section to the beginning of the Python Developer's Guide.
I would rename 'Quick Start' to 'Quick Start: Code Development' and add 'Quick Start: Communications' (or maybe 'Q S: Community Interaction'). I am not sure about the order. Unless there is opposition I do not expect, go ahead and open an issue. -- Terry Jan Reedy
On 21 July 2015 at 18:06, Carol Willing <willingc@willingconsulting.com> wrote:
The Communications Quick Start section would be brief and practical much like the Quick Start section for downloading and testing the source code. Placing the Communications Quick Start section before the existing Quick Start section would emphasize the importance that productive communications has on CPython development.
Sounds good. +1 from me. Paul
Carol Willing <willingc@willingconsulting.com> writes:
The Communications Quick Start section would be brief and practical much like the Quick Start section for downloading and testing the source code.
+1, thanks for the practical contribution! -- \ “Anyone who puts a small gloss on [a] fundamental technology, | `\ calls it proprietary, and then tries to keep others from | _o__) building on it, is a thief.” —Tim O'Reilly, 2000-01-25 | Ben Finney
participants (6)
-
Ben Finney -
Brett Cannon -
Carol Willing -
Nick Coghlan -
Paul Moore -
Terry Reedy