So maybe it would be a good idea to know how one becomes a committer!
"that unless you
are a committer and you have written the code yourself, it doesn't
get into "
Is it just by new modules? working close to the actual comitters? how
does that work?
And FYI - the Mailer issue isn't really that critical, I'm just using
it as an example.
Just to let you know: This policy (and the form it is stated) seems
overly strict to me when we are talking about small fixes/typos and
instantly discourages me from sending in any more of them (i.e.
perhaps I will do it anyway but with a bad feeling).
I know and understand: It is your project and in the first place the
committers owe nothing to Us, The Users. I can understand (and do
value) the overall decision to let the concensus of committers drive
the development instead of the quickest patch sent to the ML.
Still, for small contributions this policy looks for me like a lost
opportunity to let the broader community polish up little things noone
else noticed yet.
Actually, I just started using lift and I really liked what I've seen
so far. The question is if I'll still actively and openly try to fix
things which occur to me (as a beginner) or if I fix things quitely
and stay a passive user.
Or am I completely mistaken and misunderstood the policy?
thanks for your thorough and comprehensive answer. I think I can now
better understand the decisions you made for the project. In my eyes
the fact alone that a conscious decision was made on this difficult
topic is one that deserves credit.
Still, it feels unfortunate that legal issues get in the way of free
collaboration so easily and that enthusiasm about a piece of software
(and I still think Lift kicks ass in many respects) cannot directly
flow into a stream of positive output in terms of code -- but that
belongs to a greater debate.
Nevertheless, thanks for all the work of the lift team!