On Fri, Jun 1, 2012 at 5:37 AM, Greg Stein <gst...@gmail.com> wrote: > On May 31, 2012 5:31 AM, "Greg Stein" <gst...@gmail.com> wrote: > >... > > (that said, I agree: this seems like it should be a proposal to > > Commons, so we just need to handle that redirection) > > And I didn't read the proposal closely enough, but took from Ralph's > comment that this was some Java code. ... but no, it is a C-based project. > Thus, I don't think Apache Commons has any bearing here. > > I'm +1 on the proposal. > > Technically I'm a +1. Where else does an Apache Httpd style configuration parser fit best? Immediately examples like Xerces come to mind of projects with similar technical merit. BTW to me this has nothing to do with Java vs. C code. The concept is sound.
My concern only rests on having enough committers to jell community around it, even in the incubator. If we can get a couple more people committed, not as mentors but as contributors (perhaps from local Apache communities), then any concerns I may have vanish. I'm wondering just how a PPMC will function. > Give it a shot to build a community. That is part of what the Incubator is > all about. > > True. However this feels like the corner case of corner cases with a single committer. I'd like to help Seungyoung get some committers first before rushing to incubate. Perhaps we can ask the community now, who else is interested as participating at the committer level? Maybe (off the top of my head) the code base is small enough for an IP clearance and this can be a contribution to the Apache Httpd project. This way it has a chance to grow there with the support from that TLP? Maybe this is a good Apache Labs project candidate. At this point the Incubator just seems like a heavy weight process. I'm thinking there's a better way. -- Best Regards, -- Alex
