Submitting change requests through correct channels (was: Why not just show the out-of-range index?)
Ben Finney
bignose+hates-spam at benfinney.id.au
Tue Dec 5 02:35:04 EST 2006
"Russ" <uymqlp502 at sneakemail.com> writes:
> At this point I don't even plan to submit a formal request. I have too
> many accounts and passwords already.
If the implication here (that submitting a change request requires an
account on the server) is true, then I must concur with Russ that it's
a significant barrier to entry against a user who has one suggestion
to make.
We all use software from many different vendors (or projects, or
whatever), so requiring separate, rarely-used accounts on each one's
tracking system is plenty enough to ensure that a great deal of
suggestions never go through that channel.
I hope that, instead, it's possible to perform the research needed to
describe the requested change, submit it as an email or online form,
and never have to care about an account and password on a server that
likely will never be visited again. This way, the mechanics of
submitting the request are a low enough burden that it's reasonable to
encourage people to go through that channel.
--
\ "I know you believe you understood what you think I said, but I |
`\ am not sure you realize that what you heard is not what I |
_o__) meant." -- Robert J. McCloskey |
Ben Finney
More information about the Python-list
mailing list