Hi friends,
I almost fell in the trap to react to this by saying
"""hey, I could have reacted exactly as anatoly did""".
Guido's explainment is the first thing that was understandable to me.
The whole rest, hard to follow links to long chains of other links
to related documents, the unfriendly, burocratic treatment in the
issue-tracker, the closing of issue as a slap in the face - this made
me feel like it was myself:
It appears as he wanted to improve the PEP process and submit a patch to
the peps by a pull request that was not the way peps work.
My goodness, he was asked to discuss this first on python-ideas!
I think I know why I never submit peps.
I would like to know your opinion befor I start another fight for nothing.
I have the impression that people no longer realize how boring and
distracting
it is to even read all the stuff.
And I think the intent to avoid a discussion in the large on Python-dev
was a good
thing that should be honored.
Cheers -- Chris
--- Begin Message ---
Anatoly, the Python community is a lot more diverse than you think. "Pull
requests" (whatever that means) are not the way to start a PEP. You should
start by focusing on the contents, and the mechanics of editing it and
getting it formatted properly are secondary. The process is explained in
PEP one. Your bug report would have gotten a much better response if you
had simply asked "what is the process, I can't figure it out from the
repo's README" rather that (again) complaining that the core developers
don't care. Offending people is not the way to get them to help you.
On Thu, Nov 28, 2013 at 9:45 AM, anatoly techtonik <[email protected]>wrote:
> I wanted to help people who are trying to find out more
> about PEP submission process by providing relevant
> info (or a pointer) in README.rst that is located at the
> root of PEPs repository. You can see it here.
>
> https://bitbucket.org/rirror/peps
>
> I filled this issue with b.p.o
>
> http://bugs.python.org/issue19822
>
> However, as you may see, I met some resistance,
> which said me to discuss the matter here. So, I'd like
> to discuss two things:
>
> 1. is my README.rst enhancement request is wrong?
> 2. what makes people close tickets without providing
> arguments, but using stuff like "should"?
>
> It is not the first stuff that I personally find discouraging,
> which may be attributed to my reputation, but what's the
> point in doing this?
>
> The only logical explanation I find for resistance in this
> particular case is that people in core Python
> development don't take usability and user experience
> matters seriously. Most of core development is about
> systems, not about people, so everybody is scratching
> own itches. I wish that usability and UX was given at
> least some coverage in Python development regulations.
> --
> anatoly t.
> _______________________________________________
> Python-Dev mailing list
> [email protected]
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/guido%40python.org
>
--
--Guido van Rossum (python.org/~guido)
_______________________________________________
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/tismer%40stackless.com
--- End Message ---
_______________________________________________
Stackless mailing list
[email protected]
http://www.stackless.com/mailman/listinfo/stackless
