[issue24689] Add tips for effective online communication to devguide

[Brett Cannon]

Brett Cannon added the comment:

Moved to https://github.com/python/devguide/issues/9

--
resolution:  -> out of date
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24689] Add tips for effective online communication to devguide

[Carol Willing]

Carol Willing added the comment:

Ezio and Stephen, The "content" that you are brainstorming here is very 
helpful, and I'm learning new resources and detail from it. 

I've learned something from Ezio's link to Nick's post on python-committers. 
I'm not a core developer so I'm not subscribed to this list (kudos for the 
archives being public). When Stephen mentioned "if mailing list code of conduct 
is to be fleshed out" in msg247162, I was confused by the comment since I had 
not intended these tracker issues to be the place to develop a mailing list 
CoC. That's a bigger task :D and I want to stay focused on small, practical 
patches that are iterated over time.

[Note: A good takeaway from this is that there will be times that core 
developers believe that a topic has been extensively discussed i.e. mailing 
list CoC. Yet, the contributors without core developer status would not be 
aware that the topic has been extensively discussed unless they regularly read 
the python-committer archives.]

As a group, I think it would be helpful to step back for a moment and remind 
ourselves the improving mailing list communications will use a number of 
resources (FAQs, CoCs, devguide, helpful model messages, useful info from other 
projects, etc.).

As a next step on this issue, I will take the action item of editing 12.1 
Mailing Lists to provide better description of each list's purpose. I will also 
draft section 12.4 Tips for effective online communication (more CPython 
focused than general). When I post the patch, I will also suggest updates that 
may be helpful to include in the communications section of the FAQ.

Thanks to each of you for caring about being welcoming and considerate to our 
community members and for lending your experience to improving the complex and 
fluid blob of communication between people.

P.S. Please keep your ideas and suggestions flowing. We can roll them over into 
new issues as we feel is helpful.

--
assignee:  -> willingc

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24689] Add tips for effective online communication to devguide

[Ezio Melotti]

Ezio Melotti added the comment:

> msg247162
> It's not like we don't have several people who have macros to say the
> above (and more politely than I did) who typically respond within hours
> to off-topic posts.  What more could a FAQ say?

A FAQ would explain the "mistakes" and suggest solutions.  The content of the 
FAQ could also be copy-pasted directly in the reply, but at least we have 
standard replies for common cases that everyone can use, rather than private 
macros (with different wording) that just a few can use.

Off the top of my head, the common cases are:
* mails asking for help on python-dev/ideas that should go on python-list and 
similar;
* mails proposing ideas on python-dev that should go to python-ideas;
* mails reporting bugs or including patches should go to the bug tracker;
* mails suggesting the inclusion of a feature that doesn't belong to the stdlib;
* mails suggesting the inclusion of a feature that should be submitted and 
tested on PyPI first;
* mails suggesting the inclusion of an existing package that is better off on 
PyPI rather than in the stdlib;
* mails suggesting ideas that have already been discussed/submitted;

I think a FAQ covering these would help solve these threads quickly and save 
developers time.

Note that something similar was already being discussed by Nick in 
https://mail.python.org/pipermail/python-committers/2015-July/003454.html

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue24689] Add tips for effective online communication to devguide

[Carol Willing]

New submission from Carol Willing:

To keep the scope of issue<24682> focused on the Quick Start sections of the 
devguide, I am creating this issue to add a new subsection 12.4 ("Tips for 
effective online communication") to devguide/communication.

The following are suggestions for this new subsection:
* msg<247161> email tips from python-dev post
* msg<247162> content and links to mailman
* msg<247096> suggestions for python-dev and python-ideas
* link to devguide/coredev#responsibilities
* link to devguide/faq#communications

--
components: Devguide
messages: 247165
nosy: brett.cannon, ezio.melotti, sjt, willingc
priority: normal
severity: normal
stage: needs patch
status: open
title: Add tips for effective online communication to devguide
type: enhancement

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com