Re: [PROPOSAL] fleece as an incubator project
Hi Not at all First goal is to implement json specification (parsing, writing, building of json object/array...). Then having a small mapper and some jaxrs providers just makes the project complete IMHO and allows apache projects to avoid to import jackson, boon, jettison or gson by default. Le 9 juin 2014 05:36, Konstantin Boudnik c...@apache.org a écrit : A small clarification point: is the intention of the project to essentially implement the functionality of Groovy's JsonSlurper? http://groovy.codehaus.org/gapi/groovy/json/JsonSlurper.html for the reference Thanks, Cos On Tue, Jun 03, 2014 at 08:40PM, Romain Manni-Bucau 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 Mentors - Justin Mclean - Christian Grobmeier - Daniel Kulp Project Name Seems *Fleece* is the name which satisfies most of people but we can still ask for a new name if we feel it needed before being graduated. Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Board Report Reminder
The Drill group just produced a report that I posted and signed off. Is this too late to include? On Sun, Jun 8, 2014 at 1:14 PM, Konstantin Boudnik c...@apache.org wrote: I am going to post my Drill Shepherd review to the June2014 page in a moment, but I wanted to reflect here that Drill project didn't reported after I have nudged them on the dev@ list and Ted Dunning forwarded the reminder from the board. Cos On Sat, Jun 07, 2014 at 10:50AM, John D. Ament wrote: Hi all Don't forget, board reports were due on June 04. Shepherd reports are due tomorrow. The following podlings are considered to not have reported this month, thus far: Brooklyn DeviceMap Drill Kalumet MRQL S4 Sentry Tajo John - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Call for Report Manager for June
Thanks for all the hard work John! - Henry On Sun, Jun 1, 2014 at 5:31 AM, John D. Ament john.d.am...@gmail.com 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. John On Sat, May 31, 2014 at 10:12 AM, Roman Shaposhnik r...@apache.org wrote: Hi! John has been doing a splendid work helping out as a report manager. I really hope he can help along a few more times. That said, if there's anybody else who would want to through his or her hat in the ring and help out with the report -- please let us know by Monday. Thanks, Roman. - 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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[RESULT][VOTE] fleece as new incubator project
Hi guys, the vote has passed with 20 +1s (13 bindings) and no -1 or 0 votes. : - Bertrand Delacretaz - Javier Abrego - Chip Childers - Daniel Kulp - Christian Grobmeier - John Chambers - Jean-Louis Monteiro - Mark Struberg - Sagara Gunathunga - Enrico Daga - Justin Mclean - Daniel Stefan Haischt - John D. Ament - Henry Saputra - Mattmann, Chris A - Jake Farrell - Roman Shaposhnik - Arvind Prabhakar - David Blevins - Romain Manni-Bucau Congrats to all involved! Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-06-09 4:05 GMT+02:00 David Blevins david.blev...@gmail.com: +1 (binding) -David On Jun 6, 2014, at 12:31 AM, Romain Manni-Bucau rmannibu...@gmail.com wrote: Following the discussion earlier, I'm calling a vote to accept Fleece as a new Incubator project. The proposal draft is available at: https://wiki.apache.org/incubator/Fleece, and is also included below. Vote is open for at least 72h and closes at the earliest on 09 June 09:30 GMT. [ ] +1 accept Fleece in the Incubator [ ] +/-0 [ ] -1 because... Here's my +1. 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 - - d...@fleece.incubator.apache.org - comm...@fleece.incubator.apache.org - priv...@fleece.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: - git.apache.org/incubator-fleece.git 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 Mentors - Justin Mclean - Christian Grobmeier - Daniel Kulp Project Name Seems *Fleece* is the name which satisfies most of people but we can still ask for a new name if we feel it needed before being graduated. Romain Manni-Bucau Twitter: @rmannibucau Blog:
Re: Flink's report
The reasoning behind this was that our project was ready to release a new version but the Apache infrastructure was not yet set up. Therefore, we decided (together with our mentors) to make a release outside Apache, while being formally accepted into the incubator. On Mon, Jun 9, 2014 at 5:12 AM, Ted Dunning ted.dunn...@gmail.com wrote: Also, with a very new project, it is important to know that they have done releases before coming to Apache. On Sun, Jun 8, 2014 at 6:46 PM, Marvin Humphrey mar...@rectangular.com wrote: On Sun, Jun 8, 2014 at 6:08 PM, John D. Ament john.d.am...@gmail.com wrote: If anyone from Flink can answer... as well as IPMC members. You have this listed in your report: Date of last release: 2014-05-31 (no incubator release yet) I don't think we can list non-incubator releases in the report. It's true that that pre-Apache releases are not what the IPMC or the Board is looking for, and though it's not a big deal it's probably better not to list such releases in the future. But at least Flink made it clear that they weren't talking about an Apache release. My vote would be to keep it in because I think we should leave the Podling's work intact if we can. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Board Report Reminder
I'll leave it to others to weigh in, but I'm fine with adding an approved Drill report at this point in time. On Mon, Jun 9, 2014 at 2:28 AM, Ted Dunning ted.dunn...@gmail.com wrote: The Drill group just produced a report that I posted and signed off. Is this too late to include? On Sun, Jun 8, 2014 at 1:14 PM, Konstantin Boudnik c...@apache.org wrote: I am going to post my Drill Shepherd review to the June2014 page in a moment, but I wanted to reflect here that Drill project didn't reported after I have nudged them on the dev@ list and Ted Dunning forwarded the reminder from the board. Cos On Sat, Jun 07, 2014 at 10:50AM, John D. Ament wrote: Hi all Don't forget, board reports were due on June 04. Shepherd reports are due tomorrow. The following podlings are considered to not have reported this month, thus far: Brooklyn DeviceMap Drill Kalumet MRQL S4 Sentry Tajo John - 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
Re: Call for Report Manager for June
On Sun, Jun 8, 2014 at 10:09 PM, Marvin Humphrey mar...@rectangular.com wrote: On Sun, Jun 8, 2014 at 5:57 PM, John D. Ament john.d.am...@gmail.com wrote: - For podlings that don't report, do we remove or leave them in? If the podling hasn't reported, we should remove the empty template. If there's no shepherding review either, we should remove their entry entirely, so that the podling's only mention is in the summary under Did not report, expected next month. mechanical -- Send shepherding email. - Done A little bit ago we discussed sending out a draft version of the report instead of the shepherding email in the future. I've updated report_runbook.py accordingly. Here's the new output: ## # Once the deadline has passed for the editorial and shepherding # tasks, a draft of the report should be sent to # general@incubator for review. # # It is important to send this email in a timely manner so that # there is an adequate window for review. If the report is # incomplete, send out the draft anyway. # # Suggested subject: # #Draft Report June 2014 - please review # ## Can you take care of that tomorrow? I thought about that. I think what makes sense is once Joe's filled in some of the header stuff to send that out (or at least that was my interpretation of this). If you think we should go ahead with the current I can clean up shortly. PS: I'm enjoying this Sunday Evening Report Sprint. :) Marvin Humphrey - 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
DRAFT Board Report June 2014
All,
Please find the draft board report which includes all podlings that
have submitted reports thus far below.
John
= Incubator PMC report for June 2014 =
=== Timeline ===
||Wed June 04 ||Podling reports due by end of day ||
||Sun June 08 ||Shepherd reviews due by end of day ||
||Sun June 08 ||Summary due by end of day ||
||Tue June 10 ||Mentor signoff due by end of day ||
||Wed June 11 ||Report submitted to Board ||
||Wed June 18 ||Board meeting ||
=== Shepherd Assignments ===
||Alan D. Cabrera ||Brooklyn ||
||Andrei Savu ||Slider ||
||Andrei Savu ||Streams ||
||Dave Fisher ||S4 ||
||John Ament ||Storm ||
||Justin Mclean ||Kalumet ||
||Matthew Franklin ||Falcon ||
||Konstantin Boudnik ||Flink ||
||Matthew Franklin ||MRQL ||
||Raphael Bircher ||Wave ||
||Konstantin Boudnik ||Drill ||
||Ross Gardler ||DeviceMap ||
||Suresh Marru ||Sentry ||
||Suresh Marru ||log4cxx2 ||
=== Report content ===
{{{
Incubator PMC report for June 2014
The Apache Incubator is the entry path into the ASF for projects and codebases
wishing to become part of the Foundation's efforts.
narrative
* Community
New IPMC members:
People who left the IPMC:
* New Podlings
* Graduations
The board has motions for the following:
* Releases
The following releases were made since the last Incubator report:
* IP Clearance
* Legal / Trademarks
* Infrastructure
* Miscellaneous
Summary of podling reports
* Still getting started at the Incubator
* Not yet ready to graduate
No release:
Community growth:
* Ready to graduate
The Board has motions for the following:
* Did not report, expected next month
--
Table of Contents
Brooklyn
DeviceMap
Drill
Falcon
Flink (formerly Stratosphere)
Kalumet
log4cxx2
MRQL
Parquet
S4
Sentry
Slider
Storm
Streams
Wave
--
Brooklyn
Brooklyn is a framework for modeling, monitoring, and managing applications
through autonomic blueprints.
Brooklyn has been incubating since 2014-05-01.
No report submitted this month by Brooklyn.
DeviceMap
Apache DeviceMap is a data repository containing device information, images
and other relevant information for all sorts of mobile devices, e.g.
smartphones and tablets. While the focus is initially on that data, APIs will
also be created to use and manage it.
DeviceMap has been incubating since 2012-01-03.
No report submitted this month.
Drill
Description:
Apache Drill is a distributed system for interactive analysis of large-scale
datasets that is based on Google's Dremel. Its goal is to efficiently
process nested data, scale to 10,000 servers or more and to be able to
process petabyes of data and trillions of records in seconds.
Drill has been incubating since 2012-08-11.
Three Issues to Address in Move to Graduation:
Complete the 1.0 feature set (team targets next release and graduation
in the month of July)
Continue to attract new developers/contributors with a variety of
skills and viewpoints
Continue the outreach activities to build the early user community for
the technology
Issues to Call to Attention of PMC or ASF Board:
None
How community has developed since last report:
Community awareness and outreach were strengthened in multiple forums as below
First Apache Drill Hackathon was organized on 4/24. Over 40
participants including members from Visa, Linkedin, Cisco, Hortonworks
worked to harden/enhance Drill project. Several new features have been
added to Drill product Array reference functions, enhanced Optiq
support, Kafka storage plugin, robust testing framework etc
Hive big data think tank meet up on 5/14- Talk by MC Srivas, with ~200
member participation
Open Source Cloud meet up on 4/23 - Talk by Keys Botzum
Apache Conference session on 4/8 - Talk by Neeraja Rentachintala, with
~100 members participation
Apache Drill is also showcased at the Hadoop Summit 6/3-6/5
Mailing list discussions:
Activity summary for the user mailing list:
http://mail-archives.apache.org/mod_mbox/incubator-drill-user/
June to date 6/10: 28
May 2014, 82
March 2013, 15
Activity summary for the dev mailing list:
http://mail-archives.apache.org/mod_mbox/incubator-drill-dev/
June to date 6/10: 87 (jira focussed discussions were removed from
this thread recently)
May 2014, 1183(jira, focused discussions)
April 2014, 772 (jira; focused discussions)
For details of code commits, see
https://github.com/apache/incubator-drill/graphs/commit-activity (
about 300 commits in the past 3 months)
26 contributors have participated in GitHUB code activity; there have been
142 forks.
Community Interactions
Weekly Drill hangout continues, conducted remotely through Google hangouts
Tuesday mornings 10am
Re: Board Report Reminder
yup. lets just go ahead and add it. On Mon, Jun 9, 2014 at 9:02 AM, John D. Ament john.d.am...@gmail.com wrote: I'll leave it to others to weigh in, but I'm fine with adding an approved Drill report at this point in time. On Mon, Jun 9, 2014 at 2:28 AM, Ted Dunning ted.dunn...@gmail.com wrote: The Drill group just produced a report that I posted and signed off. Is this too late to include? On Sun, Jun 8, 2014 at 1:14 PM, Konstantin Boudnik c...@apache.org wrote: I am going to post my Drill Shepherd review to the June2014 page in a moment, but I wanted to reflect here that Drill project didn't reported after I have nudged them on the dev@ list and Ted Dunning forwarded the reminder from the board. Cos On Sat, Jun 07, 2014 at 10:50AM, John D. Ament wrote: Hi all Don't forget, board reports were due on June 04. Shepherd reports are due tomorrow. The following podlings are considered to not have reported this month, thus far: Brooklyn DeviceMap Drill Kalumet MRQL S4 Sentry Tajo John - 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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Board Report Reminder
I've gotten the DeviceMap Community to generate the following report. Sorry for the delay. Bertrand and I have been pretty busy. If any spare mentor-energy is available, I'm sure we'd welcome the help with the community... We need to move the community forward or consider the alternatives... DeviceMap Apache DeviceMap is a data repository containing device information, images and other relevant information for all sorts of mobile devices, e.g. smartphones and tablets. While the focus is initially on that data, APIs will also be created to use and manage it. DeviceMap has been incubating since 2012-01-03. Three most important issues to address in the move towards graduation: 1. Grow community. 2. Generate a release. 3. Explore options to allow contributions through a Web based interface/API to add new device specs. 4. Improved support for additional languages/platform (.NET, PHP,...) Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? How has the community developed since the last report? Tangentially, there have been presentations at conferences like JavaLand raised awareness. A Mobile Development MeetUp group in Germany is looking into the code, and where they might contribute. How has the project developed since the last report? Syncing device data with OpenDDR in regular intervals when relevant changes occur. Update of the Java DDR Simple API and other libraries. Date of last release: N/A When were the last committers or PMC members elected? N/A On Sat, Jun 7, 2014 at 7:50 AM, John D. Ament john.d.am...@gmail.com wrote: Hi all Don't forget, board reports were due on June 04. Shepherd reports are due tomorrow. The following podlings are considered to not have reported this month, thus far: Brooklyn DeviceMap Drill Kalumet MRQL S4 Sentry Tajo John - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Board Report Reminder
Are you going to enter this report on the wiki? On Mon, Jun 9, 2014 at 2:06 PM, Kevan Miller kevan.mil...@gmail.com wrote: I've gotten the DeviceMap Community to generate the following report. Sorry for the delay. Bertrand and I have been pretty busy. If any spare mentor-energy is available, I'm sure we'd welcome the help with the community... We need to move the community forward or consider the alternatives... DeviceMap Apache DeviceMap is a data repository containing device information, images and other relevant information for all sorts of mobile devices, e.g. smartphones and tablets. While the focus is initially on that data, APIs will also be created to use and manage it. DeviceMap has been incubating since 2012-01-03. Three most important issues to address in the move towards graduation: 1. Grow community. 2. Generate a release. 3. Explore options to allow contributions through a Web based interface/API to add new device specs. 4. Improved support for additional languages/platform (.NET, PHP,...) Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? How has the community developed since the last report? Tangentially, there have been presentations at conferences like JavaLand raised awareness. A Mobile Development MeetUp group in Germany is looking into the code, and where they might contribute. How has the project developed since the last report? Syncing device data with OpenDDR in regular intervals when relevant changes occur. Update of the Java DDR Simple API and other libraries. Date of last release: N/A When were the last committers or PMC members elected? N/A On Sat, Jun 7, 2014 at 7:50 AM, John D. Ament john.d.am...@gmail.com wrote: Hi all Don't forget, board reports were due on June 04. Shepherd reports are due tomorrow. The following podlings are considered to not have reported this month, thus far: Brooklyn DeviceMap Drill Kalumet MRQL S4 Sentry Tajo John - 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
Wiki access
Hi, Could RichardDowner be granted access to write to the Incubator wiki? Thanks! - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Wiki access
On Mon, 9 Jun 2014, Richard Downer wrote: Could RichardDowner be granted access to write to the Incubator wiki? Karma granted, enjoy! Nick - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Board Report Reminder
On Mon, Jun 9, 2014 at 11:11 AM, John D. Ament john.d.am...@gmail.com wrote: Are you going to enter this report on the wiki? I've taken the liberty of adding it. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Call for Report Manager for June
On Mon, Jun 9, 2014 at 9:05 AM, John D. Ament john.d.am...@gmail.com wrote: I thought about that. I think what makes sense is once Joe's filled in some of the header stuff to send that out (or at least that was my interpretation of this). If you think we should go ahead with the current I can clean up shortly. Thanks for sending it promptly. It's important that we provide enough time for review and that we keep to our own schedule. There is always *somebody* lagging on the Incubator report -- typically ~1-4 podlings reporting late or not at all. We should not let the long tail wag the dog. I wish that we would consistently encourage podlings who miss the filing deadline to just file the following month rather than scramble to file late. There's little harm in delaying a month. In my view, we are applying the wrong kind of leniency by accepting reports late enough to interfere with shepherding or mentor signoff. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Call for Report Manager for June
Joe, On Thu, Jun 5, 2014 at 11:20 PM, Joe Brockmeier j...@zonker.net wrote: On 06/01/2014 01:31 PM, Marvin Humphrey wrote: Joe Brockmeier wrote: I'd be interested in helping this month, with an eye to doing the report manager work for July and perhaps onwards from there. Wow, what a recruit -- thanks for stepping up, Joe! With your background in tech journalism, you're extremely overqualified for the Report Manager's editorial aspects. I look forward to supporting you this month and in July as well. As far as ongoing, let's revisit after the July report. The report is a pretty big production, and we've been working towards building a pool of people who can rotate in so that no one person burns out. John D. Ament replied to Joe: Great to hear! Do you want to do the report manager piece or the shepherd manager piece? John, I'm not totally clear on how you envision divvying up responsibility. Here's how we've done things before: mechanical -- Send report timeline email. mechanical -- Assign podlings which do not report to monthly. editorial -- Assemble list of releases. editorial -- Create podling summary. editorial -- Write narrative, misc, legal, infrastructure, etc. sections. mechanical -- Normalize report formatting mechanical -- Send shepherding email. Chair -- Deliver report to Board. mechanical -- Prepare next month's report template. It seems to me that your shepherd manager partially overlaps the mechanical responsibilities laid out here. Joe, what would you like to take on? Out of this list, I can take on: editorial -- Assemble list of releases. editorial -- Create podling summary. editorial -- Write narrative, misc, legal, infrastructure, etc. sections. Just wanted to point out, the report's due to the board on Wednesday and the VP should review prior to submission in case there are any edits. If you need help getting any of this together, let me know I can lend a hand. John 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
Re: Call for Report Manager for June
On 06/09/2014 07:48 PM, John D. Ament wrote: Just wanted to point out, the report's due to the board on Wednesday and the VP should review prior to submission in case there are any edits. If you need help getting any of this together, let me know I can lend a hand. Working on this tonight, will let you know tomorrow morning if I run into any snags. (Or, alternately, it'll be done!) (Apologies for delay - travelling yesterday, at DockerCon today.) 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
[DISCUSS] Graduate Apache Celix as TLP
Hi All, Since entering Incubation in November 2010, the Celix podling been working towards graduation. The community has grown, releases have been made and new committers have been added. Over the last couple of months all items on the checklist for graduation have been ticked of [1]. This resulted in a, positive, vote on te dev list of Celix itself [2]. Also the namesearch has been performed [3]. As far as we can tell the project status is up to date [4], and Celix is ready for graduation. This thread is to start the IPMC discussion for the graduation of Apache Celix. The proposed resolution can be found at the bottom of this email. Any feedback is appreciated, and where needed we will any remaining issues as soon as possible. Thanks in advance Alexander Broekhuis (PPMC member of Apache Celix) [1]: http://incubator.apache.org/guides/graduation.html#checklist [2]: http://markmail.org/thread/7y3a2l6qqm56cvud [3]: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-50 [4]: http://incubator.apache.org/projects/celix.html === Board Resolution == X. Establish the Apache Celix Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to a native implementation of the OSGi specification. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Celix Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Celix Project be and hereby is responsible for the creation and maintenance of software related to a native implementation of the OSGi specification; and be it further RESOLVED, that the office of Vice President, Apache Celix be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Celix Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Celix Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Celix Project: * Alexander Broekhuis abro...@apache.org * Pepijn Noltes pnol...@apache.org * Bjoern Petribpe...@apache.org * Erik Jansman ejan...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Alexander Broekhuis be appointed to the office of Vice President, Apache Celix, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Celix PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Celix Project; and be it further RESOLVED, that the Apache Celix Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Celix podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Celix podling encumbered upon the Apache Incubator Project are hereafter discharged. -- Met vriendelijke groet, Alexander Broekhuis
