Hey Zachary,

I'm curious myself about how you select committers.  I suspect there
are many people on this list who are responsible enough and interested
in being a committer.  Especially these people who work on the forks;
I bet they would love to push relevant and appropriate code upstream.

While this might not apply to ioquake3, sometimes it seems like
projects get stuck with their own bureaucracy.  The old hats in a
project build a lot of trust in their team and as time passes, some of
that team leaves and it is hard for the project leads to build trust
in newer contributers.  From what I can tell, that is what happened to
Gentoo anyway.

While I know I am not ready yet, I do intend to learn and hack at this
code base enough to get committer status.  Unlike Mad Professor, I do
have the time.  I work only 8 hours a day and have a 3 hours commute
to and from work where I can hack at stuff.  Point is, it would be
nice to know what you look for in a potential committer so I can be
sure to do those things.

Thanks,
EJ


On Fri, Oct 8, 2010 at 4:37 PM, |ALPHA| Mad Professor
<[email protected]> wrote:
> On Fri, Oct 8, 2010 at 5:32 PM, Zachary <[email protected]> wrote:
>> Finding responsible people who are still interested in quake 3 tech has been 
>> difficult as of late.
>
> I consider myself responsible, but I don't have time. :-/ Otherwise
> our fork would be further along. :-D How do you evaluate people for
> this? I guess you need to be able to trust them not to throw the basic
> ideals over board, i.e. tech preservation and compatibility vs.
> forward development? Without someone keeping track for a while, that's
> hard to do I guess. Maybe that hg or git or whatever DVCS move would
> really help. At least then the forks could be organized a little and
> patches could move from branches to mainline a bit easier than right
> now.
> --
> |ALPHA| Mad Professor <[email protected]>
> http://www.urtalphaclan.com/ <><><> Home of El Guapo!
> _______________________________________________
> ioquake3 mailing list
> [email protected]
> http://lists.ioquake.org/listinfo.cgi/ioquake3-ioquake.org
> By sending this message I agree to love ioquake3 and libsdl.
>
_______________________________________________
ioquake3 mailing list
[email protected]
http://lists.ioquake.org/listinfo.cgi/ioquake3-ioquake.org
By sending this message I agree to love ioquake3 and libsdl.

Reply via email to