RE: participation & contribution [was: Latest changes with lisp/uni-*.el and leim/quail]

[Drew Adams]

> others may not want to waste time on commiting patches that are
> not useful to them.

Nothing wrong with that.  Perfectly understandable.

> If one says "I'm helping, but I'll never learn bzr and you have to
> commit my patches if you want them", they bring a delibarate
> minus to the project, decreasing other developer's time.

Not at all.  *If someone wants the patch* included, then it
eventually needs to be committed.  That's all.  If no one wants it
to be included, it need never be committed.

No patch available to commit = zero.  Patch available to commit = +1,
if it has any interest at all.  Patch never committed is still +1.
If committed, and if the patch does any good and no harm, then +2.

Nothing negative anywhere.  The only negative would be if the patch
got committed and did harm.

No one is required to commit a patch.  No one is required to review
a patch.  No one is required to even acknowledge that a patch has
been provided, or to thank the submitter for it (believe me).

> It's hard to judge for me, a newcomer, whether Dani's pluses
> largely outweight minuses, 

What minuses?  None have been shown.  I'm not sure any have even been
claimed.  In any case, I haven't seen any.  Can you point to any from
this thread, for instance?  Or do you take the position that simply
requesting a commit politely is a minus?  It's not.

> but in general a developer should be able to work on their own.

Should be able to?  Maybe, maybe not.  Should have to?  No.

There is nothing wrong with people working together.  Nothing
wrong with person A signaling a problem, person B proposing a
solution, person C improving on that, and person D committing it.

> Still exceptions may be done for some honorable or valueable
> people.

Who is going to decide who is honorable or valuable?  Emacs
contributions, including some that are worthwhile, come as gifts
from people of all sorts.  Who knows which of those individuals
are honorable or "valuable" people?

It is the gift that should be judged for inclusion, not the giver.

> It would be best if one of the developer's declared: "I'll be
> commiting every patch of Dani. My time is worth less than his, so
> I'll be doing it instead of him".

Why every patch?  Why must one person's time be "worth less" than
another's, in order for the one to commit something contributed by
the other?  That makes no sense at all.

RMS, whose time I think no one would claim is worth less than
anyone else's around here, routinely fixed minor bugs, including
doc bugs.  He spent lots of his time on mundane cleanup and
"unimportant" fixes.  Likewise, Eli, BTW.

> On the other hand, saying: "**someone** should be commiting it,
> because his work is good" is unfair too.

In this thread, NO ONE has said that ANYONE *should* commit Dani's
patch.  (No, I take that back.  Some have insisted that it is only
Dani who should commit Dani's patch.)

Dani *requested* that his patch be committed, IF someone agrees
that it is worthwhile.  To quote Dani's request again:

  "It [the patch] is ok?  If so, please commit it.  TIA."

Translation: Please review it.  If you like it, you are welcome
to it.  Thank you in advance, if you commit it.

Things are being turned around, to make it sound like it is Dani
who is *demanding* that someone commit his patch.  Eli accuses
him of treating others "as his dutiful servants".  Nothing could
be further from the truth, based on what we can see in this
thread, at least.

Can you point to one piece of this thread that shows Dani
arrogantly expecting or demanding that someone commit his patch?
AFAICS, if any arrogance has been shown it has not been from
Dani's corner.

One might wonder why things are being turned around so.  I, for
one, do not know.  Why paint Dani as the bad guy here?  Perhaps
there is a backstory that explains more (dunno), but nothing in
this thread, at least, warranted the aggression dumped on him,
AFAICT.