Thanks all of you for taking time for reviewing my proposal. I understand there maybe a confusion or a conflict between Commons Configuration and my proposal. But I think there is a fundamental difference between two projects.
From my understanding, Apache Commons and its sub modules are mostly dedicated to Java area. We have Apache STDCXX project for C++ language and, in concept, Apache Commons can be categorized as a sort of STDCXX in Java language. As both projects have their own direction, I think my proposal, Apache Parser, stands differently with Commons Configuration and has a unique purpose. Basically, it's in C code base so it can be exported to many other languages. And it will be only dedicated to Apache-style configuration syntax and advocating how Apache-style syntax is versatile. The main targets are C, C++ language, additionally Python and PHP languages. Java language engineers doesn't necessarily need this much desire in terms of new flexible configuration syntax and format. Java already has many of them naturally and it's a kind of de facto standard they got used to using it. About the number of committers. It's my absence I didn't know I should have found people to work with before I ask for incubating. I was expecting I could find nice people from here if this project interests them. If that's the only blocking factor rather than the this project itself, I will be happy to go out finding committers. But if it can be processed during the process of incubation it would be much easier to get people involved in. I don't know if this project is too small or focused to be an Apache project. But I believe this is somewhat useful in terms of advocating Apache-style configuration syntax as a one of open-source de facto standard format. I like this Apache-style syntax and think this syntax is simple and extremely flexible. People can go as simple as key-value style INI format at the beginning and also can go as complex as multiple layered syntax like XML style. Seungyoung On Thu, May 31, 2012 at 2:20 AM, Alex Karasulu <akaras...@apache.org> wrote: > On Thu, May 31, 2012 at 9:37 AM, Ralph Goers > <ralph.go...@dslextreme.com>wrote: > >> My initial reaction is that there may be some confusion between this >> project and Commons Configuration, at least from a naming standpoint. >> However, I don't believe Commons Configuration currently supports this >> format of configuration. >> >> > > Because the proposal sites a single committer, and because it overlaps with > Commons Configuration as you suggest above, perhaps it's best that this not > be considered as a Incubator Proposal but a contribution to Commons > Configuration. Seungyoung can worth there with Commons Configuration folks. > Perhaps the different bindings can result in different Commons > Configuration bindes, who knows. But the bottom line here is that there's > insufficient mass (from the committer perspective). We need a minimum of 3 > committers to consider this a community applying to the Incubator. > > > >> Ralph >> >> On May 30, 2012, at 11:18 PM, Seungyoung Kim wrote: >> >> > Apache Parser >> > =========== >> > >> > General Purpose Apache-style Configuration File Parser >> > >> > * Definition >> > >> > - Apache-style Configuration: >> > A configuration file syntax and format originally introduced and >> used >> > in Apache HTTPd. >> > >> > * Abstract >> > >> > Apache-style configuration syntax provides powerful, versatile and >> flexible >> > representation of data which can be adopted by many other applications. >> > >> > * Proposal >> > >> > We're proposing a developer library of General Purpose Configuration >> Parser >> > based on and expanding Apache-style syntax. >> > >> > * Background >> > >> > One of common file format is INI-style configuration which provides >> key-value >> > pairs and 1-depth section. This format is simple but does not provide >> much >> > flexibility. >> > >> > XML and JSON format is another one which are used wided, but little bit >> > too complecated and heavy from application's stand point of view. >> > >> > Apache-style syntax can cover both simple and complex layerd >> configuration. >> > The syntax is very versatile to represent almost data format and the >> callback >> > mechanism adds flexibility. >> > >> > Many cases, software engineers pay much of their time to define their >> > configuration syntax. Apache-style configuration can be a good >> suggestion. >> > >> > * Rationale >> > >> > Apache configuration has originally introduced by Apache HTTPd. When >> this >> > project is provided as a one of Apache projects, we believe this project >> can >> > grow up with strong community and use base. >> > >> > It also helps future apache projects adopt this syntax for their new >> projects. >> > >> > * Initial Goals >> > >> > Initial goal is providing core library logic in C implementation. >> > Other language bindings will be provided after that. >> > >> > Initially, configuration parser will provide two way access of parsed >> > entries. One is callback model which is the model Apache HTTPd is using. >> > The other way is key-value model, primary for simple use and for other >> > language bindings. >> > >> > * Current Status >> > >> > At this point, initial base codes has written. >> > >> > * Community >> > >> > This project needs engineers for other language bindings. This is one of >> > reasons we want this project to be a Apache project. >> > >> > * Inexperience with Open Source >> > >> > The core developer, Seungyoung Kim, has been driven and involved in >> > several open-source projects such as qDecoder, qLibc, qHttpd and RingFS. >> > >> > * Required Resources >> > >> > - Mailing lists: >> > apacheparser-dev >> > apacheparser-commits >> > >> > - Subversion Directory: >> > https://svn.apache.org/repos/asf/incubator/apacheparser >> > >> > - Issue Tracking: >> > Bugzilla >> > >> > - Other Resources: >> > WIKI page >> > >> > * Initial Committers >> > >> > Seungyoung Kim (wolkykim at gmail dot com) >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> > For additional commands, e-mail: general-h...@incubator.apache.org >> > >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> >> > > > -- > Best Regards, > -- Alex --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
