My take (and that's just my personal opinion) is that you should gear for graduation as is and confront the shitstorm :) All arguments have been heard and while there are good ones on both sides, nobody has convinced anyone. The underlying idea that the IPMC could enforce a practice that's not necessarily valid for a given project or at least has not been really proven to be A Good Thing, even within Apache, is plain wrong if you ask me.
Worst case you get a -1 a can try again later. It happened before, it's painful but not the end of the world either. Matthieu On Mon, Nov 23, 2009 at 9:04 AM, Eric Evans <eev...@rackspace.com> wrote: > On Fri, 2009-11-20 at 13:09 +0000, ant elder wrote: > > > That being said, I don't think anyone in the "should be frowned > > > upon" camp were swayed, and we have to do what the IPMC tells us > > > to (if we want to graduate), so what choice do we have? > > > > The IPMC doesn't like telling poddlings what to do, they like them to > > work things out for themselves. > > I understand what you're saying, and I honestly believe that the > structure put in place and the the people involved are well-meaning, but > the simple fact of that matter is that the IPMC is in a position of > power over this project. > > > The question was asked and people gave they views, and some sounded > > like strongly held views. No one said they would -1 a graduation vote > > but that may just be because thats not what the question on general@ > > asked. You could ask that specific question, or you could just hold a > > graduation vote to see. Or you could first try to appease those not in > > favour of RTC by trying to make some changes > > ... and say that we worked it out for ourselves? :) > > > - could CTR be tried for a while to see how it goes? Or try CTR for > > just non-critical bits of code, or only for smaller changes? Maybe it > > will work now, but if it doesn't you can at least then say look we > > tried but it doesn't work for this project. > > We are using CTR for minor non-intrusive changes, build, scripts, > documentation, etc. > > -- > Eric Evans > eev...@rackspace.com > >
