Re: [DISCUSS] json as new incubator project
Later On 3 Òkúdu 26 Heisei, at 3:47 Ọ̀sán, Bertrand Delacretaz bdelacre...@apache.org wrote: On Tuesday, June 3, 2014, Romain Manni-Bucau rmannibu...@gmail.com wrote: FYI I renamed the proposal fleece and here is the proposal: https://wiki.apache.org/incubator/Fleece. We'll be looking forward to those free Apache Fleece vests at the next ApacheCon ;-) -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] fleece as an incubator project
Ok On 4 Òkúdu 26 Heisei, at 5:12 Àárọ̀, Jake Farrell jfarr...@apache.org wrote: Hey Romain If you do not have a current users list externally in use for your project then I would recommend against requesting setup for a us...@fleece.incubator.apache.org mailing list when you enter into the incubator and just keep all the project conversations on the d...@fleece.incubator.apache.org mailing list until a us...@fleece.incubator.apache.org mailing list is needed. -Jake On Tue, Jun 3, 2014 at 4:59 PM, Romain Manni-Bucau rmannibu...@gmail.com wrote: Hi Jake, thanks, updated the doc. You mean migrating over dev@incubator? Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-06-03 20:59 GMT+02:00 Jake Farrell jfarr...@apache.org: Please change mailing lists to - us...@fleece.incubator.apache.org - d...@fleece.incubator.apache.org - comm...@fleece.incubator.apache.org - priv...@fleece.incubator.apache.org and do you currently have a very active user mailing list you are migrating? if not would recommend that you have all conversations on the dev@ initially. The git request should be changed to: - git.apache.org/incubator-fleece.git -Jake On Tue, Jun 3, 2014 at 2:40 PM, Romain Manni-Bucau rmannibu...@gmail.com wrote: Hi guys, To follow the incubator process and after the previous discuss thread here is the formal proposal mail. Feel free to comment it! Apache Fleece Proposal Abstract Apache Fleece is an implementation of JSR-353 (JavaTM API for JSON Processing). Proposal Apache Fleece will consist of a number of modules. Mainly an implementation of JSR-353 but also a set of usefule modules to help with the usage of JSR-353 (surely a mapping module and a jaxrs provider module). Background JSon being more and more important JavaEE 7 specified an API to read and create JSon objects/arrays. Apache Fleece builds on this specification a potential base to do Json at Apache (hopefully it will be integrated with CXF for instance). Rationale There is not yet a Json related project at Apache but a lot of projects rely on some specific implementions (jettison, jackson, others...). Proposing a default would be great. The other point is a set of Apache projects related to JavaEE (CXF, TomEE, Geronimo, Axis2...) will need an implementation. Having one built at Apache is a really nice to have. Initial Goals The initial goal of the Apache Fleece project is to get a JSR-353 compliant implementation Current Status Initial codebase was developped on github but designed to be integrated in Apache. Meritocracy Initial community will be mainly composed of already Apache committers so meritocracy is already something well known. Community Initial community will be composed of TomEE community for sure, hopefully CXF and potentially all JSon users of Apache. Initial committers - Romain Manni-Bucau (individual, ASF) - Jean-Louis Monteiro (individual, ASF) - Mark Struberg (individual, ASF member) - Gerhard Petracek (individual, ASF member) - David Blevins (individual, ASF member) - Sagara Gunathunga (ASF) Alignment Several Apache project will need a JSR-353 implementation. Having a project which can be shared is better than having a sub project of a particular project. Moreover this project makes sense alone since users can integrate it without any other dependencies and use it to read/generate Json in their project so it makes sense to create a dedicated project. Known Risks Main risk is to get a not so active project since the specification is not that big. Documentation There is no documentation to import today but it will be created using standard ASF tools (ASF CMS mainly). Initial Source Initial sources are on this git repository: https://github.com/rmannibucau/json-impl.git Source and IP Submission Plan Initial sources are under Apache license v2. Side note: it was really developed to be integrated in this project (without waiting it to be created). Required Resources Mailing Lists - fleece-us...@incubator.apache.org - fleece-...@incubator.apache.org - fleece-comm...@incubator.apache.org - fleece-priv...@incubator.apache.org Version Control It is proposed that the source code for the Apache Fleece project be hosted in the Apache Git repository, under the following directory: - incubator/fleece/ Issue Tracking The following JIRA project would be required to track issues for the Apache Fleece project: - FLEECE Initial Committers - Romain Manni-Bucau - Jean-Louis Monteiro - Mark Struberg - Gerhard Petracek - David Blevins Sponsors Champion - Mark Struberg Nominated
Re: [PROPOSAL] fleece as an incubator project
That was a my mistake... Sorry On 4 Òkúdu 26 Heisei, at 5:41 Àárọ̀, sebb seb...@gmail.com wrote: On 3 June 2014 22:19, Romain Manni-Bucau rmannibu...@gmail.com wrote: Hmm think users@ can be used quickly. Is it really an issue? Incubation should be used to build up the developer community. Adding a user list may lead to fragmentation. Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-06-03 23:12 GMT+02:00 Jake Farrell jfarr...@apache.org: Hey Romain If you do not have a current users list externally in use for your project then I would recommend against requesting setup for a us...@fleece.incubator.apache.org mailing list when you enter into the incubator and just keep all the project conversations on the d...@fleece.incubator.apache.org mailing list until a us...@fleece.incubator.apache.org mailing list is needed. -Jake On Tue, Jun 3, 2014 at 4:59 PM, Romain Manni-Bucau rmannibu...@gmail.com wrote: Hi Jake, thanks, updated the doc. You mean migrating over dev@incubator? Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-06-03 20:59 GMT+02:00 Jake Farrell jfarr...@apache.org: Please change mailing lists to - us...@fleece.incubator.apache.org - d...@fleece.incubator.apache.org - comm...@fleece.incubator.apache.org - priv...@fleece.incubator.apache.org and do you currently have a very active user mailing list you are migrating? if not would recommend that you have all conversations on the dev@ initially. The git request should be changed to: - git.apache.org/incubator-fleece.git -Jake On Tue, Jun 3, 2014 at 2:40 PM, Romain Manni-Bucau rmannibu...@gmail.com wrote: Hi guys, To follow the incubator process and after the previous discuss thread here is the formal proposal mail. Feel free to comment it! Apache Fleece Proposal Abstract Apache Fleece is an implementation of JSR-353 (JavaTM API for JSON Processing). Proposal Apache Fleece will consist of a number of modules. Mainly an implementation of JSR-353 but also a set of usefule modules to help with the usage of JSR-353 (surely a mapping module and a jaxrs provider module). Background JSon being more and more important JavaEE 7 specified an API to read and create JSon objects/arrays. Apache Fleece builds on this specification a potential base to do Json at Apache (hopefully it will be integrated with CXF for instance). Rationale There is not yet a Json related project at Apache but a lot of projects rely on some specific implementions (jettison, jackson, others...). Proposing a default would be great. The other point is a set of Apache projects related to JavaEE (CXF, TomEE, Geronimo, Axis2...) will need an implementation. Having one built at Apache is a really nice to have. Initial Goals The initial goal of the Apache Fleece project is to get a JSR-353 compliant implementation Current Status Initial codebase was developped on github but designed to be integrated in Apache. Meritocracy Initial community will be mainly composed of already Apache committers so meritocracy is already something well known. Community Initial community will be composed of TomEE community for sure, hopefully CXF and potentially all JSon users of Apache. Initial committers - Romain Manni-Bucau (individual, ASF) - Jean-Louis Monteiro (individual, ASF) - Mark Struberg (individual, ASF member) - Gerhard Petracek (individual, ASF member) - David Blevins (individual, ASF member) - Sagara Gunathunga (ASF) Alignment Several Apache project will need a JSR-353 implementation. Having a project which can be shared is better than having a sub project of a particular project. Moreover this project makes sense alone since users can integrate it without any other dependencies and use it to read/generate Json in their project so it makes sense to create a dedicated project. Known Risks Main risk is to get a not so active project since the specification is not that big. Documentation There is no documentation to import today but it will be created using standard ASF tools (ASF CMS mainly). Initial Source Initial sources are on this git repository: https://github.com/rmannibucau/json-impl.git Source and IP Submission Plan Initial sources are under Apache license v2. Side note: it was really developed to be integrated in this project (without waiting it to be created). Required Resources Mailing Lists - fleece-us...@incubator.apache.org - fleece-...@incubator.apache.org - fleece-comm...@incubator.apache.org -
Re: Call for Report Manager for June
Ok On 1 Òkúdu 26 Heisei, at 8:36 Ọ̀sán, Joe Brockmeier j...@zonker.net wrote: On Sun, Jun 1, 2014, at 07:31 AM, John D. Ament wrote: All, I'd like to up the ante on Roman's proposal. After doing this job last month, I'd like to propose to split the responsibilities with someone for this month: - Report Manager is responsible for getting the incubator stuff together. Legal, releases, new members, etc. - Shepherd Manager is responsible for keeping all the shepherds together and formatting any of their reports. Either side, and probably both, would need to help any podlings with getting their reports together. If anyone's interested in taking on some of the work, let us know. I'd be interested in helping this month, with an eye to doing the report manager work for July and perhaps onwards from there. Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - 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
