On 7/21/15 9:31 PM, Nick Coghlan wrote: > On 22 July 2015 at 04:08, Brett Cannon <brett at python.org> wrote: >> On Tue, Jul 21, 2015 at 11:05 AM Carol Willing >> <willingc at 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. > 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 :)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4