Re: [DISCUSS] Commons RDF to join the Apache Incubator
Hi Folks, On Wed, Feb 11, 2015 at 2:03 AM, general-digest-h...@incubator.apache.org wrote: ATTENTION IPMC! If anybody is out there wants a low-stress Mentoring gig, this is it. And if you're an RDF neutral outsider, you'll be helping this project to achieve its goals, just by showing up. I've added myself a potentially a Champion for the Commons RDF. I've also added Apache Any23 as a potential sponsoring entity. For context, Any23 was sponsored through the incubator by Apache Tika. Upom graduation, Any23 then then came to be a TLP. I would be very willing to see Commons RDF through the incubator and would appreciate if people consider me for both Champion and for Any23 as a sponsoring entity (if one is required). Best Lewis
Re: [DISCUSS] Commons RDF to join the Apache Incubator
+1 while I can’t commit to mentoring, I will be actively and eagerly watching this. Good work guys. ++ Chris Mattmann, Ph.D. Chief Architect Instrument Software and Science Data Systems Section (398) NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 168-519, Mailstop: 168-527 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Associate Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++ -Original Message- From: Lewis John Mcgibbney lewis.mcgibb...@gmail.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Wednesday, February 11, 2015 at 8:51 AM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: [DISCUSS] Commons RDF to join the Apache Incubator Hi Folks, On Wed, Feb 11, 2015 at 2:03 AM, general-digest-h...@incubator.apache.org wrote: ATTENTION IPMC! If anybody is out there wants a low-stress Mentoring gig, this is it. And if you're an RDF neutral outsider, you'll be helping this project to achieve its goals, just by showing up. I've added myself a potentially a Champion for the Commons RDF. I've also added Apache Any23 as a potential sponsoring entity. For context, Any23 was sponsored through the incubator by Apache Tika. Upom graduation, Any23 then then came to be a TLP. I would be very willing to see Commons RDF through the incubator and would appreciate if people consider me for both Champion and for Any23 as a sponsoring entity (if one is required). Best Lewis
Re: [DISCUSS] Commons RDF to join the Apache Incubator
On Wed, Feb 11, 2015 at 8:51 AM, Lewis John Mcgibbney lewis.mcgibb...@gmail.com wrote: I've added myself a potentially a Champion for the Commons RDF. I've also added Apache Any23 as a potential sponsoring entity. For context, Any23 was sponsored through the incubator by Apache Tika. Upom graduation, Any23 then then came to be a TLP. I would be very willing to see Commons RDF through the incubator and would appreciate if people consider me for both Champion and for Any23 as a sponsoring entity (if one is required). Awesome! These days, the Sponsoring Entity is rarely anything other than the Incubator. It means that a TLP other than the Incubator has voted to take charge of incubating the project, supervising mentoring and monitoring progress. http://incubator.apache.org/guides/proposal.html#template-sponsoring-entity If the Any23 PMC has such plans, let's talk -- otherwise, it's great to see this proposal receive support from members of the Any23 community! There is some question as to whether you're also signing on to be a Mentor in addition to taking the Champion role, Lewis. The proposal wiki page changed several times this morning but currently lists you as both. What's your status? I feel like one more formal Incubator Mentor besides Rob Vesse would make this a very strong proposal. Rob is extremely capable, but a first-time Mentor shouldn't have to be the only one listed and the community has related that giving outsiders formal roles will help them in their outreach to other RDF projects. This is going to be a fun and easy job. Sergio is deeply committed, Andy is one of the IPMC's best, Benedikt has signed on to represent Commons, and the sophistication of the emails in this thread speaks for itself. Who's in? Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Slider 0.61.0-incubating
After a quick email exchange with our mentors, I'm going to publish the 0.61.0-incubating release as voted through, with the 0.7x release process to begin shortly —the latter to address all licensing inconsistencies in .py dependencies. Announcement to follow. -Steve
[RESULT][VOTE] Apache Slider 0.61.0-incubating
The Slider 0.61.0-incubating vote is complete. This is a re-release of the 0.60.0-incubating source tree along with the POM files enhancements needed to publish the binary artifacts to a maven repository; as a convenience these artifacts will now be published to the central repository. The VOTE passes with 4 +1 votes from IPMC. Jean-Baptiste Onofré +1 (binding) Jakob Homan +1 (binding) Steve Loughran +1 (binding) Billie Rinaldi +1 (binding) -Steve
Re: [DISCUSS] Commons RDF to join the Apache Incubator
On 11/02/15 05:03, Marvin Humphrey wrote: The Champion's main work is to help formulate the proposal. That work is essentially done -- so it doesn't matter too much who takes that role, now. Are Andy and Reto opting out out as a gesture of openness to Sesame? Sergio has effectively been the Champion for this proposal, but I guess he's not technically admissible as the Champion needs to be a Member or Director. It's not uncommon for someone other than the Champion to do most of the hard work of drawing up the proposal, honestly. Lewis John McGibbney (lewismc) has accepted and signed off as our Champion :-) https://wiki.apache.org/incubator/CommonsRDF#Champion We already have two mentors: Benedikt Ritter (britter) and Rob Vesse (rvesse). For Rob everything is fine. But Benedikt recently joined incubator on behalf Commons because this proposal, and he would need to join the IPMC for actually act as a mentor. In the meantime we short this off, we can stay looking for a third mentor, although not blocking us to move forward. Thanks all of you guys for your support to this proposal! -- Sergio Fernández Partner Technology Manager Redlink GmbH m: +43 660 2747 925 e: sergio.fernan...@redlink.co w: http://redlink.co - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Draft Report February 2015 - please review
On Wed, Feb 11, 2015 at 3:56 AM, Stian Soiland-Reyes st...@apache.org wrote: Not sure if this is too late.. I added the Taverna's completed Name Search under the Legal / Trademarks summary. That's fine -- it's not a controversial item. I didn't add Taverna under IP Clearance - although it's been sent to secretary@, it's not been confirmed by the secretary - probably something fell over with email + attachments + interweb. :-/ There's no hurry. The Incubator files a report every month, and it is never up-to-the-minute accurate. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: -incubator in versions of podling maven artifacts
On Wed, Feb 11, 2015 at 1:01 AM, Stian Soiland-Reyes st...@apache.org wrote: An incubator release is a kind of pre-release - community wise. But perhaps you mean this is not ideal for mature projects who were codewise stable before joining the incubator? To me the biggest signaling that needs to happen has little to do with the quality/maturity of the code (which is a subjective metric anyway) but with the fact that something coming out of org.apache.* groupID is NOT YET a full member of ASF family (and worse case scenario may never be). Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Fwd: Google Summer of Code 2015 is coming
FYI in case this email hasn't reached you. Forwarded Message Subject: Google Summer of Code 2015 is coming Date: Mon, 02 Feb 2015 23:44:52 +0100 From: Ulrich Stärk u...@apache.org Reply-To: ment...@community.apache.org To: ment...@community.apache.org Hello PMCs (incubator Mentors, please forward this email to your podlings), Google Summer of Code [1] is a program sponsored by Google allowing students to spend their summer working on open source software. Students will receive stipends for developing open source software full-time for three months. Projects will provide mentoring and project ideas, and in return have the chance to get new code developed and - most importantly - to identify and bring in new committers. The ASF will apply as a participating organization meaning individual projects don't have to apply separately. If you want to participate with your project we ask you to do the following things by no later than 2015-02-13 19:00 UTC (applications from organizations close a week later) 1. understand what it means to be a mentor [2]. 2. record your project ideas. Just create issues in JIRA, label them with gsoc2015, and they will show up at [3]. Please be as specific as possible when describing your idea. Include the programming language, the tools and skills required, but try not to scare potential students away. They are supposed to learn what's required before the program starts. Use labels, e.g. for the programming language (java, c, c++, erlang, python, brainfuck, ...) or technology area (cloud, xml, web, foo, bar, ...) and record them at [5]. Please use the COMDEV JIRA project for recording your ideas if your project doesn't use JIRA (e.g. httpd, ooo). Contact d...@community.apache.org if you need assistance. [4] contains some additional information (will be updated for 2015 shortly). 3. subscribe to ment...@community.apache.org; restricted to potential mentors, meant to be used as a private list - general discussions on the public d...@community.apache.org list as much as possible please). Use a recognized address when subscribing (@apache.org or one of your alias addresses on record). Note that the ASF isn't accepted as a participating organization yet, nevertheless you *have to* start recording your ideas now or we might not get accepted. Over the years we were able to complete hundreds of projects successfully. Some of our prior students are active contributors now! Let's make this year a success again! Cheers, Uli P.S.: Except for the private parts (label spreadsheet mostly), this email is free to be shared publicly if you want to. [1] http://www.google-melange.com/gsoc/homepage/google/gsoc2015 [2] http://community.apache.org/guide-to-being-a-mentor.html [3] http://s.apache.org/gsoc2015ideas [4] http://community.apache.org/gsoc.html [5] http://s.apache.org/gsoclabels - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Commons RDF to join the Apache Incubator
On 11/02/15 10:02, Rob Vesse wrote: Marvin Yes I would be willing to be a mentor for this podling if there isn't sufficient volunteers and they would be willing to have me Thank you - added! (before you change your mind :-)) I agree that there is a tendency then to make the podling Jena heavy but I have had zero involvement in the Commons RDF effort to date and the API they are talking about currently is at a level of a stack that I have historically contributed nothing to nor do I particularly use so hopefully I would be seen as relatively neutral. To be honest I wouldn't have the bandwidth to get actively involved in the code design) efforts (nor do I particularly want to) and thus would only want to be a mentor. Understood. As you said this would probably be a relatively easy mentoring gig with most of the effort being around just keeping an eye on the community to sign off and comment on reports and to review release as and when they come around. I hope you'll bring in your experience from other projects, inside and outside Apache. On 10/02/2015 20:31, Marvin Humphrey mar...@rectangular.com wrote: (sorry to chop but it's a long way down) The Champion's main work is to help formulate the proposal. That work is essentially done -- so it doesn't matter too much who takes that role, now. Ack. Are Andy and Reto opting out out as a gesture of openness to Sesame? Sergio has done a great job of pulling the proposal together. I have a one-podling-at-a-time policy and Taverna is already filling the slot. In my experience, champion also gets involved in the initial bootstrap tasks, and in this case I would hope we can easily share those tasks around. Andy Rob On 10/02/2015 20:31, Marvin Humphrey mar...@rectangular.com wrote: On Tue, Feb 10, 2015 at 7:21 AM, Stian Soiland-Reyes st...@apache.org wrote: The natural path to Apache Commons Sandbox has been studied, but we think that in this phase of the project, which focuses on the API design and actively involves the developers of existing toolkits, it is better to have a more focused community and infrastructure. Rather than a new Top-Level Project, the goal is still to graduate as part of Apache Commons, that is when API has achieve the required maturity and the project goes into maintenance mode. If Commons is OK with this, I imagine this is a fine plan -- good enough for entering incubation. I also think it would be OK for the project to decide it wants to become a TLP. Whether the project joins Commons or becomes its own TLP won't impact the number of people qualified to work on it. Some Apache TLPs are effectively in maintenance mode and have very low activity, but still have PMC members willing to answer user questions, make security releases and file still here quarterly reports. That seems like a legitimate aspiration for this project. A potential Jena destination also seems as though it would have certain advantages, though my naive speculation is that it might be sub-optimal in terms of providing neutral territory for negotiating a common API for Jena and Sesame. In any case it seems likely that if the project achieves its design goal, there will be people willing to work on it as long as both Jena and Sesame remain viable. That makes it different from other potential maintenance mode TLPs which are in danger of stagnation because they cannot renew their communities. Is that take roughly accurate, Sergio et al? === Mailing lists === * commons-rdf-dev * commons-rdf-commits Those sound like final mailing lists rather than Incubator ones. I might have expected these instead: d...@commons-rdf.incubator.apache.org comm...@commons-rdf.incubator.apache.org Do you expect to keep separate mailing lists after graduation, or will traffic be shunted onto existing Commons mailing list like d...@commons.apache.org and comm...@commons.apache.org? * Sergio Fernández (wikier dot apache dot org) * Andy Seaborne (andy dot apache dot org) * Peter Ansell (ansell dot apache dot org) * Stian Soiland-Reyes (stain at apache dot org) * Reto Gmür (reto at apache dot org) Lots of Apache experience in this group. Four are PMC members of at least one Apache project. Andy and Reto are ASF Members. Andy and Sergio are both IPMC members. Stian is a core contributor of the Taverna podling. You probably haven't been getting much feedback because there's a lot going on in the Incubator right now and everybody figures that with a group like that you're in good shape. :) === Champion === * TBD The Champion's main work is to help formulate the proposal. That work is essentially done -- so it doesn't matter too much who takes that role, now. Are Andy and Reto opting out out as a gesture of openness to Sesame? === Nominated Mentors === * Benedikt Ritter (britter at apache dot org) * TBD Benedikt is a member of the Commons PMC, but he's not a member of the IPMC nor an Apache Member --
Re: [DISCUSS] Commons RDF to join the Apache Incubator
On 10/02/15 21:31, Marvin Humphrey wrote: If Commons is OK with this, I imagine this is a fine plan -- good enough for entering incubation. I also think it would be OK for the project to decide it wants to become a TLP. Whether the project joins Commons or becomes its own TLP won't impact the number of people qualified to work on it. Some Apache TLPs are effectively in maintenance mode and have very low activity, but still have PMC members willing to answer user questions, make security releases and file still here quarterly reports. That seems like a legitimate aspiration for this project. A potential Jena destination also seems as though it would have certain advantages, though my naive speculation is that it might be sub-optimal in terms of providing neutral territory for negotiating a common API for Jena and Sesame. In any case it seems likely that if the project achieves its design goal, there will be people willing to work on it as long as both Jena and Sesame remain viable. That makes it different from other potential maintenance mode TLPs which are in danger of stagnation because they cannot renew their communities. Is that take roughly accurate, Sergio et al? Completely :-) -- Sergio Fernández Partner Technology Manager Redlink GmbH m: +43 660 2747 925 e: sergio.fernan...@redlink.co w: http://redlink.co - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Commons RDF to join the Apache Incubator
Hi, On 11/02/15 05:03, Marvin Humphrey wrote: How good a fit is this project for Commons? Is it similar in scope and size to other Commons components? Any comments from current members of the Commons community? Should we be concerned about potential umbrella project issues, such as degrading signal-to-noise ratio on the Commons lists? We already discussed that at dev@commons.a.o. Commons does not want to be an umbrella project, and I completely agree on that. But we cannot (yet) consider Commons RDF as a component that fits there (or sandbox), since we have to grow the community and evolve the design before been prepared to be there. Peter, who I see is active in Sesame, indicates that either Reto or Andy would be acceptable. If it would suit the community to have an outsider Champion, though, I'm willing to serve. Personally I'd prefer an outsider. The larger representation of Apache Commons here (either as Champion or Mentors) the better for the success of the proposal. We were hoping to also get some RDF neutral mentors. +++1 Thanks for the very good feedback, Marvin. -- Sergio Fernández Partner Technology Manager Redlink GmbH m: +43 660 2747 925 e: sergio.fernan...@redlink.co w: http://redlink.co - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: -incubator in versions of podling maven artifacts
When you say break, do you mean some software is unable to compare version numbers correctly, or that we don't comply with the text of http://semver.org ? A pre-release version MAY be denoted by appending a hyphen and a series of dot separated identifiers immediately following the patch version. Identifiers MUST comprise only ASCII alphanumerics and hyphen [0-9A-Za-z-]. Identifiers MUST NOT be empty. Numeric identifiers MUST NOT include leading zeroes. Pre-release versions have a lower precedence than the associated normal version. A pre-release version indicates that the version is unstable and might not satisfy the intended compatibility requirements as denoted by its associated normal version. Examples: 1.0.0-alpha, 1.0.0-alpha.1, 1.0.0-0.3.7, 1.0.0-x.7.z.92. An incubator release is a kind of pre-release - community wise. But perhaps you mean this is not ideal for mature projects who were codewise stable before joining the incubator? On 10 Feb 2015 23:29, Julien Le Dem jul...@ledem.net wrote: Hi Incubator, I'd like some context about the requirement of adding -incubating in the file name of podling releases. http://incubator.apache.org/guides/releasemanagement.html http://incubator.apache.org/guides/release-java.html#best-practice-maven It seems we require adding -incubating in the version for maven artifacts which breaks Semantic versioning as hyphen is used for pre-releases. It is also confusing as we vote on a version number but that's not what we use as the artifact version. We are already publishing the source release in the incubator project and have incubating in its file name as well as DISCLAIMER files. So it seems to me that adding it in the maven artifact is a bit overkill. Every release as to get through the vote of the IPMC anyway so it's not like podlings releases are not vetted appropriately. opinions from the IPMC? Julien
Re: [DISCUSS] Commons RDF to join the Apache Incubator
Marvin Yes I would be willing to be a mentor for this podling if there isn't sufficient volunteers and they would be willing to have me I agree that there is a tendency then to make the podling Jena heavy but I have had zero involvement in the Commons RDF effort to date and the API they are talking about currently is at a level of a stack that I have historically contributed nothing to nor do I particularly use so hopefully I would be seen as relatively neutral. To be honest I wouldn't have the bandwidth to get actively involved in the code design) efforts (nor do I particularly want to) and thus would only want to be a mentor. As you said this would probably be a relatively easy mentoring gig with most of the effort being around just keeping an eye on the community to sign off and comment on reports and to review release as and when they come around. Rob On 10/02/2015 20:31, Marvin Humphrey mar...@rectangular.com wrote: On Tue, Feb 10, 2015 at 7:21 AM, Stian Soiland-Reyes st...@apache.org wrote: The natural path to Apache Commons Sandbox has been studied, but we think that in this phase of the project, which focuses on the API design and actively involves the developers of existing toolkits, it is better to have a more focused community and infrastructure. Rather than a new Top-Level Project, the goal is still to graduate as part of Apache Commons, that is when API has achieve the required maturity and the project goes into maintenance mode. If Commons is OK with this, I imagine this is a fine plan -- good enough for entering incubation. I also think it would be OK for the project to decide it wants to become a TLP. Whether the project joins Commons or becomes its own TLP won't impact the number of people qualified to work on it. Some Apache TLPs are effectively in maintenance mode and have very low activity, but still have PMC members willing to answer user questions, make security releases and file still here quarterly reports. That seems like a legitimate aspiration for this project. A potential Jena destination also seems as though it would have certain advantages, though my naive speculation is that it might be sub-optimal in terms of providing neutral territory for negotiating a common API for Jena and Sesame. In any case it seems likely that if the project achieves its design goal, there will be people willing to work on it as long as both Jena and Sesame remain viable. That makes it different from other potential maintenance mode TLPs which are in danger of stagnation because they cannot renew their communities. Is that take roughly accurate, Sergio et al? === Mailing lists === * commons-rdf-dev * commons-rdf-commits Those sound like final mailing lists rather than Incubator ones. I might have expected these instead: d...@commons-rdf.incubator.apache.org comm...@commons-rdf.incubator.apache.org Do you expect to keep separate mailing lists after graduation, or will traffic be shunted onto existing Commons mailing list like d...@commons.apache.org and comm...@commons.apache.org? * Sergio Fernández (wikier dot apache dot org) * Andy Seaborne (andy dot apache dot org) * Peter Ansell (ansell dot apache dot org) * Stian Soiland-Reyes (stain at apache dot org) * Reto Gmür (reto at apache dot org) Lots of Apache experience in this group. Four are PMC members of at least one Apache project. Andy and Reto are ASF Members. Andy and Sergio are both IPMC members. Stian is a core contributor of the Taverna podling. You probably haven't been getting much feedback because there's a lot going on in the Incubator right now and everybody figures that with a group like that you're in good shape. :) === Champion === * TBD The Champion's main work is to help formulate the proposal. That work is essentially done -- so it doesn't matter too much who takes that role, now. Are Andy and Reto opting out out as a gesture of openness to Sesame? === Nominated Mentors === * Benedikt Ritter (britter at apache dot org) * TBD Benedikt is a member of the Commons PMC, but he's not a member of the IPMC nor an Apache Member -- so although Commons input is important, unfortunately it's not a valid nomination. I'd nudge newly elected IPMC member Rob Vesse, but maybe the roster is already Jena-heavy? 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
Re: [DISCUSS] Commons RDF to join the Apache Incubator
On 11/02/15 08:14, Sergio Fernández wrote: On 10/02/15 21:31, Marvin Humphrey wrote: If Commons is OK with this, I imagine this is a fine plan -- good enough for entering incubation. I also think it would be OK for the project to decide it wants to become a TLP. Whether the project joins Commons or becomes its own TLP won't impact the number of people qualified to work on it. Some Apache TLPs are effectively in maintenance mode and have very low activity, but still have PMC members willing to answer user questions, make security releases and file still here quarterly reports. That seems like a legitimate aspiration for this project. A potential Jena destination also seems as though it would have certain advantages, though my naive speculation is that it might be sub-optimal in terms of providing neutral territory for negotiating a common API for Jena and Sesame. In any case it seems likely that if the project achieves its design goal, there will be people willing to work on it as long as both Jena and Sesame remain viable. That makes it different from other potential maintenance mode TLPs which are in danger of stagnation because they cannot renew their communities. Is that take roughly accurate, Sergio et al? Completely :-) Yes. Personally, I'd keep the destination open for both TLP and Apache Commons, then see where we are at graduation time. A lot of (good) things can happen during incubation. Andy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Practical next steps for pTLP experiment
On Tue, Feb 10, 2015 at 4:01 PM, Sam Ruby ru...@intertwingly.net wrote: On Tue, Feb 10, 2015 at 3:35 PM, Greg Stein gst...@gmail.com wrote: Who ever said the Incubator has the exclusive Right to be the only way to become part of the Apache Software Foundation? New approaches can be discussed anywhere. At the end of the day, it will be the Board who votes on a pTLP resolution. Resolution R2, paragraph 3: http://apache.org/foundation/records/minutes/2002/board_minutes_2002_10_16.txt Well aware, Sam. I voted on that. ... and again: it doesn't assign *exclusive* management of incoming projects. It is flat out impossible for such. The Board can write a resolution saying that one day, and then accept a contravening resolution the next. *shrug* ... what you're missing is that pTLP is not part of the Incubator. Nothing against it, but it has zero bearing upon these proposals. All of that is left to the Board. ... Cheers, -g
Re: Draft Report February 2015 - please review
Not sure if this is too late.. I added the Taverna's completed Name Search under the Legal / Trademarks summary. I didn't add Taverna under IP Clearance - although it's been sent to secretary@, it's not been confirmed by the secretary - probably something fell over with email + attachments + interweb. :-/ On 9 February 2015 at 17:30, Marvin Humphrey mar...@rectangular.com wrote: Incubator PMC report for February 2015 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: Mentors who didn't sign off on the reports: * New Podlings * Graduations The board has motions for the following: * Releases The following releases were made since the last Incubator report: johnzon-0.5-incubating apache-reef-0.10.0-incubating htrace-3.1.0-incubating apache-usergrid-1.0.1-incubating nifi-nar-maven-plugin 1.0.0 nifi 0.0.1 (incubating) streams-project-0.1-incubating The Incubator continues to use discretion when enforcing release policy. * Numerous releases have been approved despite having an out of date copyright year in the NOTICE file. Fixing for the next release has been considered a sufficient remedy. * The REEF release was approved with an incomplete incubation disclaimer in README (there was also a disclaimer on the podling website). * IP Clearance CouchDB Mango -- IBM Corporation have built a MongoDB API Layer for CouchDB and are donating it to the CouchDB project. This consists of of a module that exposes a set of actions that are similar to what MongoDB exposes. * Legal / Trademarks * Infrastructure * Miscellaneous Summary of podling reports * Still getting started at the Incubator TinkerPop Zeppelin (delayed software grant) * Not yet ready to graduate No release: Corinthia Kylin Lens SAMOA Tamaya Taverna Community growth: Droids HTrace NiFi REEF Slider Twill * Ready to graduate Blur * Did not report, expected next month BatchEE Ripple (2 months) * Retired Podlings NPanday * Report incomplete Sirona -- Table of Contents BatchEE Blur Corinthia Droids HTrace Kylin Lens NiFi REEF Ripple SAMOA Sirona Slider Tamaya Taverna TinkerPop Twill Zeppelin -- BatchEE BatchEE projects aims to provide a JBatch implementation (aka JSR352) and a set of useful extensions for this specification. BatchEE has been incubating since 2013-10-03. Three most important issues to address in the move towards graduation: 1. 2. 3. 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? How has the project developed since the last report? Date of last release: -XX-XX When were the last committers or PMC members elected? Signed-off-by: [ ](batchee) Jean-Baptiste Onofré [ ](batchee) Olivier Lamy [ ](batchee) Mark Struberg Shepherd/Mentor notes: Blur Blur is a search platform capable of searching massive amounts of data in a cloud computing environment. Blur has been incubating since 2012-07-24. Three most important issues to address in the move towards graduation: 1. We anticipate pursuing graduation after our upcoming release. 2. 3. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? None. How has the community developed since the last report? We continue to be small but active. - Subscriptions: user@ - 60[0]; dev@ - 66[0] How has the project developed since the last report? The majority of effort has been around stabilization for the upcoming release. We're pleased to have seen some new folks show up and contribute bug reports and patches. Date of last release: 2014-07-29 When were the last committers or PMC members elected? 2014-07-28 Signed-off-by: [ ](blur) Doug Cutting [X](blur) Patrick Hunt [X](blur) Tim Williams Shepherd/Mentor notes: Corinthia Corinthia is a toolkit/application for converting between and editing common office file formats, with an initial focus on word processing. It is designed to cater for multiple classes of platforms - desktop, web, and mobile - and relies heavily on web technologies such as HTML, CSS, and JavaScript for representing and manipulating documents. The toolkit is small, portable, and flexible, with minimal dependencies. The target audience is developers wishing to
Re: [DISCUSS] Commons RDF to join the Apache Incubator
Cool! Thanks, Rob. On 11/02/15 11:02, Rob Vesse wrote: Marvin Yes I would be willing to be a mentor for this podling if there isn't sufficient volunteers and they would be willing to have me I agree that there is a tendency then to make the podling Jena heavy but I have had zero involvement in the Commons RDF effort to date and the API they are talking about currently is at a level of a stack that I have historically contributed nothing to nor do I particularly use so hopefully I would be seen as relatively neutral. To be honest I wouldn't have the bandwidth to get actively involved in the code design) efforts (nor do I particularly want to) and thus would only want to be a mentor. As you said this would probably be a relatively easy mentoring gig with most of the effort being around just keeping an eye on the community to sign off and comment on reports and to review release as and when they come around. Rob On 10/02/2015 20:31, Marvin Humphrey mar...@rectangular.com wrote: On Tue, Feb 10, 2015 at 7:21 AM, Stian Soiland-Reyes st...@apache.org wrote: The natural path to Apache Commons Sandbox has been studied, but we think that in this phase of the project, which focuses on the API design and actively involves the developers of existing toolkits, it is better to have a more focused community and infrastructure. Rather than a new Top-Level Project, the goal is still to graduate as part of Apache Commons, that is when API has achieve the required maturity and the project goes into maintenance mode. If Commons is OK with this, I imagine this is a fine plan -- good enough for entering incubation. I also think it would be OK for the project to decide it wants to become a TLP. Whether the project joins Commons or becomes its own TLP won't impact the number of people qualified to work on it. Some Apache TLPs are effectively in maintenance mode and have very low activity, but still have PMC members willing to answer user questions, make security releases and file still here quarterly reports. That seems like a legitimate aspiration for this project. A potential Jena destination also seems as though it would have certain advantages, though my naive speculation is that it might be sub-optimal in terms of providing neutral territory for negotiating a common API for Jena and Sesame. In any case it seems likely that if the project achieves its design goal, there will be people willing to work on it as long as both Jena and Sesame remain viable. That makes it different from other potential maintenance mode TLPs which are in danger of stagnation because they cannot renew their communities. Is that take roughly accurate, Sergio et al? === Mailing lists === * commons-rdf-dev * commons-rdf-commits Those sound like final mailing lists rather than Incubator ones. I might have expected these instead: d...@commons-rdf.incubator.apache.org comm...@commons-rdf.incubator.apache.org Do you expect to keep separate mailing lists after graduation, or will traffic be shunted onto existing Commons mailing list like d...@commons.apache.org and comm...@commons.apache.org? * Sergio Fernández (wikier dot apache dot org) * Andy Seaborne (andy dot apache dot org) * Peter Ansell (ansell dot apache dot org) * Stian Soiland-Reyes (stain at apache dot org) * Reto Gmür (reto at apache dot org) Lots of Apache experience in this group. Four are PMC members of at least one Apache project. Andy and Reto are ASF Members. Andy and Sergio are both IPMC members. Stian is a core contributor of the Taverna podling. You probably haven't been getting much feedback because there's a lot going on in the Incubator right now and everybody figures that with a group like that you're in good shape. :) === Champion === * TBD The Champion's main work is to help formulate the proposal. That work is essentially done -- so it doesn't matter too much who takes that role, now. Are Andy and Reto opting out out as a gesture of openness to Sesame? === Nominated Mentors === * Benedikt Ritter (britter at apache dot org) * TBD Benedikt is a member of the Commons PMC, but he's not a member of the IPMC nor an Apache Member -- so although Commons input is important, unfortunately it's not a valid nomination. I'd nudge newly elected IPMC member Rob Vesse, but maybe the roster is already Jena-heavy? 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 -- Sergio Fernández Partner Technology Manager Redlink GmbH m: +43 660 2747 925 e: sergio.fernan...@redlink.co w: http://redlink.co
Re: Draft Report February 2015 - please review
On Mon, Feb 9, 2015 at 3:35 PM, Marvin Humphrey mar...@rectangular.com wrote: It's my understanding that Droids is basically a mature product with no pressing need for further development, not unlike some dormant Apache TLPs who neverthess still have PMC members hanging around able to make releases and respond to user inquiries. I think the greater IPMC ought to stay aware, though, that Droids has very, very low activity: 3 dev list emails in the last quarter (39 in the last year), no user list, and no commits since April 2013. The only thing between Droids and retirement is our deference to Richard and Thorsten. They form the potential core of a community, but it has yet to develop in 6 years of incubation. Very much +1 to that! I think Richard and Thorsten need to come up with the trajectory for the project. As I see it -- it can go either way. One thing is certain though: I don't think incubation is serving its purpose for the project any longer. SAMOA SAMOA provides a collection of distributed streaming algorithms for the most common data mining and machine learning tasks such as classification, clustering, and regression, as well as programming abstractions to develop new algorithms that run on top of distributed stream processing engines (DSPEs). It features a pluggable architecture that allows it to run on several DSPEs such as Apache Storm, Apache S4, and Apache Samza. SAMOA has been incubating since 2014-12-15. Three most important issues to address in the move towards graduation: 1. Create bylaws for the project I'm a little surprised to see creation of bylaws listed as the top priority for a brand new podling. Bylaws limit flexibility; I would have thought it better to wait until near graduation to perform such a task (if at all). Have other podlings done this? Is there something unusual about SAMOA? That jumped at me as well (great minds... ;-)). However, looking at the matter further it appears that bylaws may be too grand a term here. The community seems to be simply seeking a 'modus operandi' if you will. Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
