expectations from the community

[Andrey Somov]

Not exactly. Apparently, I was not clear enough.
Another attempt. While reading the Python code I have found a few
imperfections which I think shall be reported to the community. Since I
think a patch is the best way to show my idea, I send it.
My contribution is not to fix or to improve production code but merely to
indicate the problem and help others to find the proper solution.

My expectation: my job is done. The issue is known and those who know the
code better and feel responsible may do whatever they wish

What happens: the patch is rejected with comments that it should be
improved. (Even though the reviewer can clear see the place to be improved
!)

I am confused. What shall I do ? Does the community expects me to re-send
the patch until it is accepted ?
What is the community expectation ?

I hope, I was clear enough.

-
Andrey

On Mon, Feb 6, 2012 at 8:42 PM, Augie Fackler <durin42 at gmail.com> wrote:

>
>
> Bug reporters are certainly welcome, but bugs tend to be fixed when
> there's someone contributing that's bitten by the bug. Not everything is
> that way, but most of us are doing this as a side project, and it's not
> what pays the bills. A bug sitting unfixed isn't an indicator that we
> dislike the reporter, merely that nobody has bothered to pick it up.
> Sometimes, bugs are obscure enough that the only way to get them fixed is
> to either pay someone to become a contributor, or become one yourself.
>
> Does that help?
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20120207/09721cd3/attachment.html>