On 12/2/05, Frank W. Zammetti <[EMAIL PROTECTED]> wrote: > Preach on, brother :)
:) My own favorite sermon is also an ASF motto: "Be the change you want to see in the world." Or, the more popular, sometimes sardonic: "Thanks for volunteering". :) On 12/2/05, Frank W. Zammetti <[EMAIL PROTECTED]> wrote: > But still, I wonder if it might not be better to simply offer people a > (potentially) incompatible choice, I'm reminded of an old Yogi Bear cartoon. People are yelling "A bear! A bear!" And so Yogi joins in by yelling "A bear! A bear!" himself. After a moment, Yogi stops and says "Wait a minute, I *am* a bear!". :) We are users: (people == us). Here's the rub: When a PMC member casts a +1 for a release, we're not just saying "It's cool!", we're saying "I will support this release by applying patches and answering posts on the lists." Since we are all volunteers, realistically, this usually means that we will be using the release at work. (Or that we have way too much free time on our hands!) Migration is important because a sufficient number of PMC members have to be able to migrate their own applications. I agree that binary migration is only so useful, since many applications are maintained without ambitious upgrades. More importantly, we must be able to migrate our own *skill sets*. It must be easier for PMC members to use Ti in our next project than it would be to use Action 1.x. Otherwise, it will be difficult for us to vote +1 and mean it. What I see coming out of the migration layer is a bunch of ways to map conventional Action 1.x idioms to Action 2.x idioms. Not so much to use in the old applications, but to use in the application that we ourselves are coding today. -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
