Joe, To be clear: forks or branches for this discussion sake is the same thing, a copy of the source tree to demonstrate a concept. It is not a competition or animosity simply a practical method of doing what you would like to do, allow others to see the stuff, and if it is interesting enough the community will pick it up on it's merit. There is no better way to show something than to do it.
Aron On Sun, Aug 15, 2010 at 8:14 PM, Joe Schaefer <joe_schae...@yahoo.com> wrote: > ----- Original Message ---- > >> From: Aron Sogor <big...@gmail.com> >> To: thrift-dev@incubator.apache.org >> Sent: Sun, August 15, 2010 10:55:12 PM >> Subject: Re: sharing knowledge means sharing control >> >> Tight control is ok for with me. In fact I prefer the option of: >> >> - big company uses the thing a lot to deliver real service >> - big company finds issues and fixes them >> - big company put's it's neck on the line to test it very well by real >> usage. > > Unfortunately this isn't the model of a typical Apache project. It's > more typical of something like MySQL, or lots of corporate backed GPL > projects. At Apache every committer is an equal, with equal say in > what goes in and what doesn't go in to the codebase. Leadership is > informal and defined by who is doing the work, not based on where someone > works or how big their production deployment is. > >> I think real usage, practical experience on a high volume system is >> invaluable. Hence the dudes who work, and have exposure to such system >> should make the decision, demonstrate leadership and given more >> freedom over perceived benefits. >> >> For my selfish reasons I trust more the pressure of keeping a system >> running and "battle testing" than an essay competition on a mailing >> list. >> >> Apache "sprit" or not, I would like to complement a strong and >> visionary leadership, accepting practical patches. If it does not fit >> the Apache style, find another repo rather than discourage access to >> "battle tested" goodness. >> >> If your feel your input is not taken: fork and demonstrate. > > I believe that's what happened with the c-thrift fork. I don't follow > it well enough to know how well it works in practice or how much development > activity it enjoys, but I still hope there isn't animosity about the > design decisions between the respective projects. Collaboration is > a better strategy than competition, even in the case of a justifiable fork. > >> The Apache license is sweet, allows easy forking, when I needed the >> AS3 patch I forked for a while, I still maintain it, once there is a >> demand for fresh AS3 goodness I will make a new patch, and I expect >> popular demand will float it into the the HEAD. > >> It is evolution, simple economics not democracy and that is a OK with me. > > Lots of people equate Apache with the Switzerland of open source. > Perhaps you might want to consider what those people might mean, > and how democracy fits into the picture here. > > > >
