FWIW, I'm more than happy with granting one or two additional committers with proven track records, even if you mainly work on the web app or mainly work elsewhere.
We do need somebody to be able to make the big calls, to release, and to coordinate others -- and to appreciate what release quality is and what patches make the cut and which do not. I can think of no one better to do this than James seeing (I think, not checking, he's probably at the top in the git statistics). Anyone else what to throw their hat in for core commit access and taking on a bigger share of the work? Even just smacking the bug queue down every few weeks would be very welcome, as well as answering the hard questions that require code research and experimentation. (Folks that just focus not the web app are welcome to. You don't have to be an expert in the whole thing, though it helps. I know we have some very good folks that have done a ton of work there.) --Michael On Tuesday, February 28, 2012 at 6:26 PM, James Cammarata wrote: > > I'm looking to make ownership of Cobbler more democratic. In short, I'm > > wanting to disappear and let someone else take Cobbler in whatever direction > > they would like to take it -- not having the need to use it everyday means > > I'm not really in the mode to test and fix things, which is holding us back. > > > > We have made progress in opening things up on github and making a better > > environment for people to more easily contribute, but there is more to do. > > > > Namely we have to fix bugs. People assume I'm going to fix them, and I > > don't… and as a result, they do not get fixed. OSS is not really > > "community please help" sort of thing, it takes people to drive and do a > > large amount of work. I knew this, but … well, I've confirmed it more. > > We need drivers. > > > > > I'll go ahead and throw my hat in the ring. > > For those who may not know me, I've been a contributor since 2008 and > have written/rewritten large portions of the code (import modules, > esx/esxi support, alternate template support, and the basis for the > web GUI to name a few). I've contributed patches to just about every > portion of the code, so I know the internal workings of cobbler pretty > well. > > My company is fairly strict about not accessing personal mail during > work hours, so that means my hacking/irc/email answering time is > pretty much limited to evenings. I don't see that changing any time > soon, so that would be one negative. I was also recently promoted to > an architect position, so I'm not using cobbler day to day quite as > much as I was as an engineer. > > I have too many hours dedicated to cobbler to let it die easily, so > I'm not going anywhere no matter what happens, and will continue > contributing for the foreseeable future no matter who's leading the > project. > _______________________________________________ > cobbler mailing list > cobbler@lists.fedorahosted.org (mailto:cobbler@lists.fedorahosted.org) > https://fedorahosted.org/mailman/listinfo/cobbler > >
_______________________________________________ cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler
