[issue24682] Add Quick Start: Communications section to devguide

Brett Cannon added the comment: Moved to https://github.com/python/devguide/issues/8 -- resolution: -> out of date status: open -> closed ___ Python tracker

[issue24682] Add Quick Start: Communications section to devguide

Ezio Melotti added the comment: FWIW when I added the quickstart (#13228), its main target wasn't newbies, but devs that already have experience with other open source projects and want to contribute to CPython. These people just need to know where is the repo and the bug tracker, how to

[issue24682] Add Quick Start: Communications section to devguide

R. David Murray added the comment: Carol: as part of requesting a commit you can set the stage to 'commit review' (I've done that for this one) and that may lead to at least a couple of us noticing it where we wouldn't otherwise :) -- nosy: +r.david.murray stage: patch review ->

[issue24682] Add Quick Start: Communications section to devguide

Carol Willing added the comment: R. David Murray wrote: > > R. David Murray added the comment: > > Carol: as part of requesting a commit you can set the stage to 'commit > review' (I've done that for this one) and that may lead to at least a > couple of us noticing it where we wouldn't

[issue24682] Add Quick Start: Communications section to devguide

R. David Murray added the comment: Looking over this...I'm -0. I really don't like the organization of the front page of the developers guide. The idea of a "quick start" section is fine, but is it appropriate? (I'm talking about the code quick start) The first pages of the document, to my

[issue24682] Add Quick Start: Communications section to devguide

R. David Murray added the comment: Well, you got agreement from Stephen :) But you are right, I had overlooked the fact that this was your patch. I also just gave Stephen Developer privs on the tracker so he can do it in the future on issues he thinks are ready. All that said, I don't think

[issue24682] Add Quick Start: Communications section to devguide

Carol Willing added the comment: David, I love the three paragraph intro. It captures the essence of the dev guide usage from newcomers to the project to experienced core devs. I really like the second paragraph and how it suggests focusing on the issue at hand. Thanks, and I will take these

[issue24682] Add Quick Start: Communications section to devguide

Changes by R. David Murray : -- stage: commit review -> needs patch ___ Python tracker ___

[issue24682] Add Quick Start: Communications section to devguide

Stephen J. Turnbull added the comment: I just reviewed again, and I agree it's ready for merge. I don't see any immediate need to add more. Unfortunately, I'm not a committer. -- ___ Python tracker

[issue24682] Add Quick Start: Communications section to devguide

Carol Willing added the comment: Stephen, Thanks for reviewing to make sure it's still current. I appreciate it. Core devs: Please merge and we'll close this one. Thanks. -- ___ Python tracker

[issue24682] Add Quick Start: Communications section to devguide

Carol Willing added the comment: Ezio, Brett, Stephen: Would one of you be able to merge this? Thanks. -- ___ Python tracker ___

[issue24682] Add Quick Start: Communications section to devguide

Brett Cannon added the comment: The patch overall LGTM, although it's hard to read in a browser due to the lack of code review integration with Rietveld (time to go email some people to keep the code process moving forward =). -- ___ Python tracker

[issue24682] Add Quick Start: Communications section to devguide

Ezio Melotti added the comment: I would also like to see a short section (perhaps in the form of a FAQ) that could be linked whenever someone asks for Python help on python-dev/python-ideas, or proposes an idea on python-dev, or misuses the lists in a similar fashion. These could then be

[issue24682] Add Quick Start: Communications section to devguide

Carol Willing added the comment: Ezio, thanks for the suggestions :D To clarify, the new Quick Start will be: - brief; - contain links to additional communication/community interaction info in the devguide; - guide a new contributor (or remind others) to information about ways to

[issue24682] Add Quick Start: Communications section to devguide

Stephen J. Turnbull added the comment: If the mailing list code of conduct is to be fleshed out, Paul Moore's post is a good place to start IMO: https://mail.python.org/pipermail/python-dev/2015-July/140872.html. -- nosy: +sjt ___ Python tracker

[issue24682] Add Quick Start: Communications section to devguide

Stephen J. Turnbull added the comment: I tend to disagree with Ezio about a FAQ for general questions. A pointer to appropriate alternatives for off-topic posts in the Mailman listinfo descriptions of the various list (which can be copied into the devguide, or linked from there) will be

[issue24682] Add Quick Start: Communications section to devguide

Carol Willing added the comment: Thanks Stephen for the additional links and suggestions. I would like to keep this issue focused on the Quick Start section added in the patch. I've opened Issue24689 to focus on tips for effective online communication. I have referenced the comments here

[issue24682] Add Quick Start: Communications section to devguide

Carol Willing added the comment: Here's the patch for adding the `Quick Start: Community workflow` section to the devguide. I made a few other minor edits to the index page (replacing beginner/advanced wording for starter/additional) since docs and testing are important. While docs and

[issue24682] Add Quick Start: Communications section to devguide

New submission from Carol Willing: Add a Quick Start: Communications section to devguide (or Q S: Community Interaction) as discussed on python-dev mailing list today. The Quick Start: Communications section should be brief, link to other sections in the devguide, and give contributor's