I do agree that a gentler tone would be better here. Of course. Also
less "Welcome to the Internet" sarcasm!
But I've never liked the idea that if you're going to make a suggestion,
you should provide a patch. Separate issue. False dichotomy.
Do you really only want suggestions, or even solutions, from people that
can provide patches? I doubt most open source projects actually expect
that of their end-users, let alone the developers themselves.
A few months ago I thought of an a small way Celery, the Python
distributed task queue, could be improved. It would have probably
involved only one line of production code. Ask Solem, Celery's author,
said he'd incorporate any patch I submitted. Of course, then I had to
find exactly where the line should go, and figure out how to test it,
and figure out how to fix the few unit tests that would perhaps break as
a result of the change. So I'd come up with an /idea/, that Ask liked,
and came up with a /solution/, being my one line of code, but never got
round to providing the /patch/ because my client and I figured a
workaround and it's a whole other thing and I've not yet been able to
justify the time.
Even though I feel bad about not getting my sh*t together to provide the
patch, I doubt Ask is irritated about this. He has the idea (I should
file a ticket though).
I was very nice about it all though, of course. No swearing or
complaining. If I /had/ done that, I expect I'd have been [hunted down
or] asked to stop swearing and complaining. Not to provide a patch.
Toby
On 12/01/2011 08:46 AM, Lee Fisher wrote:
On 12/1/11 7:24 AM, Gary Hawkins wrote:
How incredibly lame of you Python people to repeatedly be sending
passwords
around in plain text. You should not even know what anyone's
passwords are!
You should instead store them only represented as SHA2 and only
programmatically check to see if their inputs match, and only be able
to reset
passwords, not read them back.
Wake the hell up.
Gary,
Welcome to the Internet. Glad to see things are going well on your
first month.
You're blaming the wrong people, and talking on the wrong place.
Your observation about mailing list software is a general mailing list
software issue, nothing to do with "Python people", or the SeaPIG list.
You should be talking on the mailing lists where mailing list software
is discussed.
Lastly, this is an open source community, if you have a solution, you
need to be providing a patch, not simply swear and complain and the
nearest group that uses mailing lists.
Thanks.
