On 7/3/07, Jeff Eaton <jeff@viapositiva.net> wrote:
On Jul 3, 2007, at 9:56 AM, Fernando Silva wrote:
8. core developers will start to do their job of commiting patches
This is a point of much contention, however. Your statement implies that a core committer is "The guy who's supposed to press the 'commit' button after everyone decides what should happen." With that line of thinking, yes, a core committer is 'not their job' if they don't commit RTBC patches.
From a list of points that could be work together as an idea to solve a (I admit) "time problem", you only pick the last to be defended? Were my ideas so bad, that only the point 8 deserves a comment?
Instead of picking the idea and saying "it's bad" or "it's good, and we should discuss it a bit", seems that it's preferable to defend the core commiters and let all go on as nothing should be done. Remember: it was not me that created the "Ready To Be Commited", so if it means something else than it's literal meaning, it's not my fault neither the fault of other simple developers that do not have the "force or the torch of power with them". Don't you think there is a problem that should be aligned and correct with newer perspectives for a better work? Don't you think that small human beings like us, deserve at least a little consideration for our work? Or are we just machines to do the hard work of testing, documentating and correcting things while "core developers" do the "good stuff"?!