What I had in mind most of all was a "soon to be a committer" developer, but I tried to open up to other designs as well. My thought may be more attached to the POI project, where greater selectivity is required in allowing committers. Basically most people who can do this kind of work do C not Java, and most Java programmers take some time learning the black arts of CVS, etc. We also have learned unit tests are essential. So our developer incubation stage is expanding not contracting and the project has been getting more and more publicity and the Word port is finally heating up (it just takes time to demystify and convince people "yes we can" and let them come to the realization that Microsoft brand brain teasers are the best and most fun in the world! It takes people to realize that these brain teasers are the best/most fun time waster since Sid Meyer's Civilization and the spawned series/project www.freeciv.org...No I'm not sick! ;-)). So we are likely to have a set of "soon to be" committers developers signing on. This is somewhat forward-looking on my part, but thats my purpose, not the "people who should be committers but aren't" case.
View 1: +1 Sam, Steven Noles
View 2: +1 Andy
+1
I see no reason to not have an open archive, but am fine with the list
being restricted, with exceptions on a case by case basis (although for
every exception I'm inclined to ask, so why isn't this valuable
contributor a committer? Oh yes, that can of worms again...)
-Andy
