Follow-up Comment #2:
I'm open to this idea of having a project for
anybody's patches; this isn't some ego trip of
mine to have my own. What I want to avoid,
however, is either:
-- having to spend more time managing other
people's contributions (including the web
pages that describe them) than writing and
contributing my own code;
-- ending up being managed by others and
having to cut through a red tape of
getting each contribution accepted, which
would reintroduce the delay problem I'm
trying to avoid in the first place. (I
make sure myself that the quality of
whatever code I put up is high enough,
if I want people to come back.)
It seems to me that it comes down to
minimizing the total amount of efforts by
everybody that's involved. My assumption,
and I may have been wrong, is that it was
simplest for anybody who want to do this
(and there aren't necessarily tons) to
have his/her own very modest size project,
with no elitism connotation about it.
This way, nobody's stepping on anyone
else's toes.
_______________________________________________________
This item URL is:
<http://gna.org/task/?func=detailitem&item_id=1172>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
