On Dec 17, 2006, at 5:39 PM, Carl Karsten wrote:
> "hmm, it seems to work. I wonder if the rest of the gang will like
> it?"
> moment of reason..
> "what if they don't?"
> moment passes...
> "I'll just commit it and see what happens."
>
> This has 2 implications:
> 1. maybe I shouldn't be committing so whilly nilly.
> 2. someone else may take the other path and not commit something
> useful.
First step would be to post your concerns here. There may be valid
reasons why something works the way it does, or it may indeed be a
shortcoming that needs addressing.
> Personally, I would think each dev should get their own branch, and
> use some
> sort of buddy system to have changes reviewed before merged. or
> maybe some
> unit testing... I du no. that has it's pros and cons too.
Back in a former life as a carpenter, the motto was "measure twice;
cut once". IOW, make sure that what you are doing is what you really
want to do.
Paul and I have been immersed in Dabo for nearly 3 years. You're
coming in relatively cold. If there's something you either want
changed or added, post it here, and we can discuss it first so that
if there is something already in place, you don't waste your time
duplicating it, or if there are other places that could use the same
improvement, we can address them all at once.
Discussion is good. Hell, even argument is good! It goes without
saying that Paul and I have not seen eye to eye on all the design
decisions we've made, and we've had some pretty heated disagreements
(see: http://leafe.com/archives/showFullThd/298063).
In the end, though, we both are striving to achieve the same goal,
so it works out. Perhaps we should anoint ourselves the BDCDFL
(Benevolent Dabo Co-Dictators For Life). Hmm... doesn't roll off the
tongue that easily, huh?
-- Ed Leafe
-- http://leafe.com
-- http://dabodev.com
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
