[Python-ideas] Civility on this mailing list

[Nick Coghlan]

On 22 October 2016 at 01:07, Paul Moore <p.f.moore at gmail.com> wrote:
> I wonder. Would there be value in adding a sign-up email to the list
> (supported by a posting of that email to the list, to catch existing
> contributors) that set out some of the basic principles of how changes
> are judged for inclusion in Python? We could cover things like:
>
> * The fact that the default answer is typically "no", along with an
> overview of the reasons *why* the status quo wins by default.
> * Some of the simple "rules of thumb" like "not every 2-line function
> should be a builtin.
> * Basic reminders that Python is used by a very diverse set of users,
> and proposals that are only beneficial for a limited group need to be
> weighed against the disruption to the majority who get no benefit.
> * The above comment, that we welcome ideas because it's important that
> we don't stagnate and having assumptions challenged is valuable, even
> if the bar for getting such ideas accepted is (necessarily) high.
>
> Maybe even make it a regular informational posting, if it seems that a
> reminder would be useful.
>
> It's possible that this would come across as too bureaucratic for new
> users, though, so I'm not sure...

We have a bit of that kind of content in the developer guide (although
I don't think we have anything written down anywhere regarding "Usage
scenarios to keep in mind"):

* https://docs.python.org/devguide/langchanges.html#langchanges
* https://docs.python.org/devguide/faq.html#suggesting-changes

Those could potentially be linked from the python-ideas list overview
at https://mail.python.org/mailman/listinfo/python-ideas for folks
that hit the mailing list sign-up page directly, rather than
encountering the Developer Guide first.

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia