RE: Some missing things for the December report
-Original Message- From: Benson Margulies [mailto:bimargul...@gmail.com] hcatalog: no report! [Dropped other podling dev lists] HCatalog still has no report for December and no discussion about it on the DEV list. The last Shepherd also recommended in September that the podling look toward Graduation; but I did not find any discussion of the topic on the list. Aside from the immediate need for a report, I don't see anything alarming about the community health. I strongly recommend the community put together a graduation plan and present it as part of the board report (this or next). One minor nit, the downloads page needs to list links for the signature and checksum files for each release. -Matt
RE: [VOTE] Graduate OpenMeetings from Incubator
+1 -Original Message- From: seba.wag...@gmail.com [mailto:seba.wag...@gmail.com] Sent: Sunday, December 02, 2012 1:51 AM To: general@incubator.apache.org Cc: openmeetings-...@incubator.apache.org Subject: [VOTE] Graduate OpenMeetings from Incubator Dear Incubation members, During incubation, OpenMeetings has : * Produced 1 Release * Added 5 new Committer/PPMC members and shows constant community activities * Cleared IP on all code * Developed Roadmap(s) for the next major and minor releases in a community process and started working on that Given these accomplishments, I propose that we submit the following graduation resolution to the incubator PMC. We organized already a community vote: http://markmail.org/thread/wnxvkvukdqgdddpn The vote received: 1x +1 Yegor IPMC 5x +1 solomax, aaf, sebawagner, greenes PMC 1x +1 Irina Please VOTE over the next 72 hours on the resolution below: [ ] +1 Graduate OpenMeetings from the Incubator per the resolution below. [ ] +0 Don't care. [ ] -1 Don't graduate OpenMeetings from the Incubator because: === == Charter here: https://cwiki.apache.org/confluence/display/OPENMEETINGS/Draft+Charter and copied below: X. Establish the Apache OpenMeetings 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 OpenMeetings Web-Conferencing tool. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache OpenMeetings Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache OpenMeetings Project be and hereby is responsible for the creation and maintenance of software related to the OpenMeetings Web-Conferencing tool; and be it further RESOLVED, that the office of Vice President, Apache OpenMeetings 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 OpenMeetings Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache OpenMeetings 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 OpenMeetings Project: * Alexei Fedotova...@apache.org * Sebastian Wagner sebawag...@apache.org * Maxim Solodovnik solo...@apache.org * Oliver Becherer smoe...@apache.org * Rodion Volkovrc...@apache.org * Eugen Schwert eschw...@apache.org * German Grekhovggrek...@apache.org * Timur Tleukenov ti...@apache.org * Alvaro Bustos Ruiz al...@apache.org * George Kirkham gkirk...@apache.org * Stephen Cotthammegatroni...@apache.org * Sascha Xander sxan...@apache.org * Evgeny Rovinskyrovin...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Sebastian Wagner be appointed to the office of Vice President, Apache OpenMeetings, 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 OpenMeetings 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 OpenMeetings Project; and be it further RESOLVED, that the Apache OpenMeetings Project be and hereby is tasked with the migration and rationalization of the Apache Incubator OpenMeetings podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator OpenMeetings podling encumbered upon the Apache Incubator Project are hereafter discharged. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: checking on the shepherd inventory (or, 3.14159 IPMC members ...)
From: Dave Fisher [mailto:dave2w...@comcast.net] I liked that Jukka assigned me to random podlings as this exposes me to new ideas. +1 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: Incubator report reminders sent for Dec 2012
-Original Message-
From: Daniel Shahaf [mailto:danie...@apache.org]
Sent: Saturday, December 01, 2012 1:41 PM
To: general@incubator.apache.org
Subject: Re: Incubator report reminders sent for Dec 2012
On Sat, Dec 01, 2012 at 07:20:35PM +0100, Christian Grobmeier wrote:
I miss Onami and Ripple from the reminders.
Helix and HDT are also missing; these four are all set up as
${podling}.incubator.apache.org - related?
Streams has the same e-mail format and was not listed either.
But they are listed here:
http://incubator.apache.org/report-next-month.html#onami
What do I need to fix to get these reminders?
I just know the old wiki-styled process
On Sat, Dec 1, 2012 at 4:26 PM, Marvin no-re...@apache.org wrote:
The next board meeting is scheduled for Wed, 19 December 2012, 10:00:00
PST.
I have just sent reminder emails to the below addresses, requesting them
to supply board reports 2 weeks before the above date (Wed, Dec 5th).
Please recall that the Incubator report is due Wed, Dec 12th.
Allura Developers allura-...@incubator.apache.org
Bloodhound Developers bloodhound-...@incubator.apache.org
Blur Developers blur-...@incubator.apache.org
cTAKES Developers ctakes-...@incubator.apache.org
Drill Developersdrill-...@incubator.apache.org
Etch Developers etch-...@incubator.apache.org
Flex Developers flex-...@incubator.apache.org
Hadoop Development Tools Developers
general@incubator.apache.org
HCatalog Developers hcatalog-...@incubator.apache.org
Kalumet Developers kalumet-...@incubator.apache.org
Openmeetings Developers openmeetings-
d...@incubator.apache.org
S4 Developers s4-...@incubator.apache.org
Wave Developers wave-...@incubator.apache.org
-
To unsubscribe, e-mail: private-unsubscr...@incubator.apache.org
For additional commands, e-mail: private-h...@incubator.apache.org
--
http://www.grobmeier.de
https://www.timeandbill.de
-
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: [VOTE] Retire Chukwa from incubation
+1 -Original Message- From: Alan Cabrera [mailto:l...@toolazydogs.com] Sent: Sunday, November 25, 2012 6:00 PM To: general@incubator.apache.org Subject: [VOTE] Retire Chukwa from incubation Hi, The Chukwa community has voted to retire the project. Following the retirement guide [1], I now call the Incubator PMC to vote on confirming this decision. [ ] +1 Retire the Chukwa project [ ] -1 Do not retire the project, because ... [1] http://incubator.apache.org/guides/retirement.html Regards, Alan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Sub-projects - when are they acceptable? (was Re: [VOTE] Graduate Nuvem as a sub-project under Apache Tuscany)
On 11/21/12 7:26 AM, Benson Margulies bimargul...@gmail.com wrote: On Wed, Nov 21, 2012 at 5:40 AM, Ross Gardler rgard...@opendirective.com wrote: On 21 November 2012 10:36, Bertrand Delacretaz bdelacre...@apache.orgwrote: On Tue, Nov 20, 2012 at 3:47 PM, Mattmann, Chris A (388J) chris.a.mattm...@jpl.nasa.gov wrote: ...sub-products, or the ability for a PMC to release multiple products, like e.g., like Lucene does now (Lucene-Java is a product; Solr is a product; PyLucene is a product), that works b/c the sets of individuals that make up those interested in the sub products are not separate communities, they just release different portions of the software that they scratch their itch on Agreed, that's what I meant - a PMC that groups multiple communities is not good, whereas one that oversees several products is fine. +1 this is a good way of restating my intention too. Seems we have lots of agreement so far. So, permit me to ask another, related, question. It seems to me that the IPMC is concerned with the fact that a project is ready to leave, but not so much which where it is going. A proposal to form a new TLP is, I think, a straightforward question to the board, and the IPMC's action is to make a recommendation to the board. A proposal to be integrated into an existing project is, I think, within the authority of the existing product's PMC. If Project A wishes to invite the members of Podling B to join and integrate their code, then this looks to me like it could just happen without any approval in advance from the board or even the IPMC. Voting in committers is a PMC task, voting in PMC members is a PMC task with board lazy approval, and copying (ip-cleared) code from one place in ASF source control to another is a PMC task. I think that IPMC graduation votes in this case are a nice thing, but it seems by this logic that they are not necessary. Does this make sense? I think your statement makes sense, but I see the votes as a way for IPMC members to assert that they believe all due diligence in IP clearance has been performed and that a sanity check has been done as to whether or not the podling is to be fully integrated into the PMC of the target project. From this perspective the Incubator serves to provide a convenience to the target PMC in regards to releasability of code they are assuming and as a foundation preventative measure for ensuring we don't end up with massive, disconnected umbrellas comprised of former incubator podlings. Ross -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Ross Gardler (@rgardler) Programme Leader (Open Development) OpenDirective http://opendirective.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
Re: November reports
On 11/14/12 6:14 AM, Jukka Zitting jukka.zitt...@gmail.com wrote: Hi, We still have two missing reports: Helix and Syncope. Helix, since you're only just starting, a very simple report like the one from Ripple is quite enough for now. Syncope, you already passed the graduation vote, so there isn't that much to report anymore, but for the record it would still be nice if you could mention the graduation process as having been completed on your side. I finally got around to assigning shepherds for this months podling reports: Dave Fisher - Amber Jukka Zitting- Ambari, NPanday Matt Franklin- Clerezza, PhotArk Somehow I missed my assignments for November. Thanks for covering Jukka. Matt Hogstrom- Crunch, Wink Ross Gardler - DeltaSpike Benson Margulies - Droids, Wookie Roman Shaposhnik - Nuvem It would be great if you could review the reports by tomorrow, Thursday, so that we can submit the Incubator report on Friday. Luckily we don't have too many reports to review this month, so just let me know if you won't have time for the reviews and I'm sure we'll find a replacement. When reviewing, note especially any progress from previous reports: Starting: Crunch No release: Ambari Low activity: Clerezza, Droids, Nuvem, NPanday Low diversity: PhotArk Ready to graduate: Amber, DeltaSpike, Wink, Wookie BR, Jukka Zitting - 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: [VOTE] Accept Apache Streams as an Incubator Project
+1 (binding) On 11/14/12 7:37 AM, Franklin, Matthew B. mfrank...@mitre.org wrote: Given the feedback received so far I think the Streams proposal is in good shape so I am calling for a vote to accept Streams into the Incubator. The proposal is at: http://wiki.apache.org/incubator/StreamsProposal and also copied as text below. Please vote. [ ] +1 Accept Streams into the incubator [ ] +0 Don't care' [ ] -1 Reject for the following reason: I'll close the vote at Monday morning on November 19th EST. - COPY OF PROPOSAL FROM http://wiki.apache.org/incubator/StreamsProposal - Apache Streams Proposal == Abstract == Apache Streams will be a lightweight server for ActivityStreams. The role of Apache Streams is to provide a central point of aggregation, filtering and querying for Activities that have been submitted by disparate systems. Apache Streams also intends to include a mechanism for intelligent filtering and recommendation to reduce the noise to end users. == Proposal == Apache Streams will bring together individuals who are or are looking to increase and centralize the production, consumption and federation of ActivityStreams throughout enterprise organizations and the Internet as a whole. The target features include: * Publication of Activities from multiple systems via HTTP * Aggregation and syndication of streams * Support for security trimming of streams by social graph * Noise reduction and intelligent filtering * Federation of streams across disparate systems * Provide libraries for easy integration in source systems == Background == The ActivityStreams specification standardizes a generic format for describing event-based data. Many social web companies have adopted the format and it has been included in the OpenSocial specification as the preferred method for delivery of activity data. During discussions of ActivityStreams at OpenSocial events earlier in the year, it became clear that multiple organizations are facing similar issues as to the publication and filtering of their activities and would benefit from a commonly-developed, open-source ActivityStreams server. == Rationale == In deployment, activities are generated from multiple sources. This is particularly true within the enterprise where disparate systems create and manage activities in stove pipes. What is needed is a central point for consumption, aggregation and exposure of activities generated within these systems. == Initial Goals == The initial goal of the project is to survey donated code and develop a common, high-level architecture for an initial release. The project will then work toward that release in a new code base, pulling in pieces of donated code as necessary. == Current Status == The MITRE Corporation will donate its prototype code to the project. Aside from this, the project is new and will need bootstrap time to develop an initial architecture and roadmap. Meritocracy As a new project with many team members who are seasoned Apache veterans, Apache Streams is prepared to build the project under the Apache Way. Community The Apache Streams community combines multiple individuals from different organizations, many of which have collaborated before in an open environment. Apache Streams is committed to expanding this community and adhering to Apache principles of openness and collaboration. == Known Risks == An exercise in self-knowledge. Risks don't mean that a project is unacceptable. If they are recognized and noted then they can be addressed during incubation. Inexperience with Open Source Most of the initial committers have worked in open source and many are familiar with the ASF and the Apache Way; but, not all. Additionally, many of the committers have not worked on a software project together and will need time to familiarize themselves with each other. Speed of Development This project is dependent upon contributions made on company time. For this approach to succeed, the project must deliver a workable system in a timeframe acceptable to those companies. The initial parties have the intention of releasing a first version within 6 months after starting the Incubator. Failure to do so could prevent the project reaching critical mass, and could prevent the project from being in a position to attract new developers. Reliance on Salaried Developers At present, the vast majority of contributors will be doing so as a part of their day jobs. Therefore, as already alluded to, there is a risk that the project won't gain enough traction to be of use to their employers. However, given the centrality of these codebases to the participating companies, it is clearly in their best interests to transition to an openly developed alternative. Relationships with Other Apache Products Many of the initial committers will be integrating this software with Apache Rave Apache Shindig. A possibility exists
RE: [PROPOSAL] Apache Steams Project
-Original Message- From: Jason Letourneau [mailto:jletournea...@gmail.com] Sent: Thursday, November 08, 2012 8:19 AM To: general@incubator.apache.org Subject: Re: [PROPOSAL] Apache Steams Project Hi Andrew - Sounds great - we'd love to have you onboard. Just add your name to the proposal as an initial committer. The current MITRE prototype is Java/Spring based and leveraging the Shindig and Rave projects. We are also using a reference implementation of the pubsubhubbub protocol. Jason On Wed, Nov 7, 2012 at 7:03 PM, Andrew Hart ah...@apache.org wrote: Hi Matt, I've worked on several side projects over the years that utilize the Activity Streams specification, and I would love to get involved and help out with this. Out of curiousity, what language(s) is the Mitre prototype implemented in? Cheers, - Andrew On 11/06/2012 09:06 AM, Franklin, Matthew B. wrote: I would like to propose a new Activity Streams server project to the Incubator. The proposal is on the wiki at the following location: http://wiki.apache.org/incubator/StreamsProposal Streams is a collaborative effort from multiple organizations and individuals working with and around the Activity Streams specification (http://activitystrea.ms). We are looking forward to your feedback and suggestions. -Matt Franklin - COPY OF PROPOSAL FROM http://wiki.apache.org/incubator/StreamsProposal - Apache Streams Proposal == Abstract == Apache Streams will be a lightweight server for ActivityStreams. The role of Apache Streams is to provide a central point of aggregation, filtering and querying for Activities that have been submitted by disparate systems. Apache Streams also intends to include a mechanism for intelligent filtering and recommendation to reduce the noise to end users. == Proposal == Apache Streams will bring together individuals who are or are looking to increase and centralize the production, consumption and federation of ActivityStreams throughout enterprise organizations and the Internet as a whole. The target features include: * Publication of Activities from multiple systems via HTTP * Aggregation and syndication of streams * Support for security trimming of streams by social graph * Noise reduction and intelligent filtering * Federation of streams across disparate systems * Provide libraries for easy integration in source systems == Background == The ActivityStreams specification standardizes a generic format for describing event-based data. Many social web companies have adopted the format and it has been included in the OpenSocial specification as the preferred method for delivery of activity data. During discussions of ActivityStreams at OpenSocial events earlier in the year, it became clear that multiple organizations are facing similar issues as to the publication and filtering of their activities and would benefit from a commonly-developed, open-source ActivityStreams server. == Rationale == In deployment, activities are generated from multiple sources. This is particularly true within the enterprise where disparate systems create and manage activities in stove pipes. What is needed is a central point for consumption, aggregation and exposure of activities generated within these systems. == Initial Goals == The initial goal of the project is to survey donated code and develop a common, high-level architecture for an initial release. The project will then work toward that release in a new code base, pulling in pieces of donated code as necessary. == Current Status == The MITRE Corporation will donate its prototype code to the project. Aside from this, the project is new and will need bootstrap time to develop an initial architecture and roadmap. Meritocracy As a new project with many team members who are seasoned Apache veterans, Apache Streams is prepared to build the project under the Apache Way. Community The Apache Streams community combines multiple individuals from different organizations, many of which have collaborated before in an open environment. Apache Streams is committed to expanding this community and adhering to Apache principles of openness and collaboration. == Known Risks == An exercise in self-knowledge. Risks don't mean that a project is unacceptable. If they are recognized and noted then they can be addressed during incubation. Inexperience with Open Source Most of the initial committers have worked in open source and many are familiar with the ASF and the Apache Way; but, not all. Additionally, many of the committers have not worked on a software project together and will need time to familiarize themselves with each other. Speed of Development This project is dependent upon contributions made on company time. For this approach to succeed, the project must deliver a workable system in a timeframe acceptable
RE: [PROPOSAL] Apache Steams Project
-Original Message- From: Davide Palmisano [mailto:dpalmis...@gmail.com] Sent: Tuesday, November 06, 2012 12:17 PM To: general@incubator.apache.org Subject: Re: [PROPOSAL] Apache Steams Project Hi there, I'm working to something[1] (not yet fully open source released) which could somehow overlap with Streams. I'm also one of the authors of the Activity Streams Ontology[2] which is the rdf-ish version of activitystrea.ms. I'll be really happy to contribute on Streams. Feel free to add yourself as an initial committer to the proposal on the wiki. cheers, [1] http://www.slideshare.net/dpalmisano/semtech2012-finalpdf [2] http://xmlns.notu.be/aair/ On Tue, Nov 6, 2012 at 6:06 PM, Franklin, Matthew B. mfrank...@mitre.org wrote: I would like to propose a new Activity Streams server project to the Incubator. The proposal is on the wiki at the following location: http://wiki.apache.org/incubator/StreamsProposal Streams is a collaborative effort from multiple organizations and individuals working with and around the Activity Streams specification (http://activitystrea.ms). We are looking forward to your feedback and suggestions. -Matt Franklin - COPY OF PROPOSAL FROM http://wiki.apache.org/incubator/StreamsProposal - Apache Streams Proposal == Abstract == Apache Streams will be a lightweight server for ActivityStreams. The role of Apache Streams is to provide a central point of aggregation, filtering and querying for Activities that have been submitted by disparate systems. Apache Streams also intends to include a mechanism for intelligent filtering and recommendation to reduce the noise to end users. == Proposal == Apache Streams will bring together individuals who are or are looking to increase and centralize the production, consumption and federation of ActivityStreams throughout enterprise organizations and the Internet as a whole. The target features include: * Publication of Activities from multiple systems via HTTP * Aggregation and syndication of streams * Support for security trimming of streams by social graph * Noise reduction and intelligent filtering * Federation of streams across disparate systems * Provide libraries for easy integration in source systems == Background == The ActivityStreams specification standardizes a generic format for describing event-based data. Many social web companies have adopted the format and it has been included in the OpenSocial specification as the preferred method for delivery of activity data. During discussions of ActivityStreams at OpenSocial events earlier in the year, it became clear that multiple organizations are facing similar issues as to the publication and filtering of their activities and would benefit from a commonly-developed, open-source ActivityStreams server. == Rationale == In deployment, activities are generated from multiple sources. This is particularly true within the enterprise where disparate systems create and manage activities in stove pipes. What is needed is a central point for consumption, aggregation and exposure of activities generated within these systems. == Initial Goals == The initial goal of the project is to survey donated code and develop a common, high-level architecture for an initial release. The project will then work toward that release in a new code base, pulling in pieces of donated code as necessary. == Current Status == The MITRE Corporation will donate its prototype code to the project. Aside from this, the project is new and will need bootstrap time to develop an initial architecture and roadmap. Meritocracy As a new project with many team members who are seasoned Apache veterans, Apache Streams is prepared to build the project under the Apache Way. Community The Apache Streams community combines multiple individuals from different organizations, many of which have collaborated before in an open environment. Apache Streams is committed to expanding this community and adhering to Apache principles of openness and collaboration. == Known Risks == An exercise in self-knowledge. Risks don't mean that a project is unacceptable. If they are recognized and noted then they can be addressed during incubation. Inexperience with Open Source Most of the initial committers have worked in open source and many are familiar with the ASF and the Apache Way; but, not all. Additionally, many of the committers have not worked on a software project together and will need time to familiarize themselves with each other. Speed of Development This project is dependent upon contributions made on company time. For this approach to succeed, the project must deliver a workable system in a timeframe acceptable to those companies. The initial parties have the intention of releasing a first version within 6 months after starting the Incubator. Failure to do so could
[VOTE] Accept Apache Streams as an Incubator Project
Given the feedback received so far I think the Streams proposal is in good shape so I am calling for a vote to accept Streams into the Incubator. The proposal is at: http://wiki.apache.org/incubator/StreamsProposal and also copied as text below. Please vote. [ ] +1 Accept Streams into the incubator [ ] +0 Don't care' [ ] -1 Reject for the following reason: I'll close the vote at Monday morning on November 19th EST. - COPY OF PROPOSAL FROM http://wiki.apache.org/incubator/StreamsProposal - Apache Streams Proposal == Abstract == Apache Streams will be a lightweight server for ActivityStreams. The role of Apache Streams is to provide a central point of aggregation, filtering and querying for Activities that have been submitted by disparate systems. Apache Streams also intends to include a mechanism for intelligent filtering and recommendation to reduce the noise to end users. == Proposal == Apache Streams will bring together individuals who are or are looking to increase and centralize the production, consumption and federation of ActivityStreams throughout enterprise organizations and the Internet as a whole. The target features include: * Publication of Activities from multiple systems via HTTP * Aggregation and syndication of streams * Support for security trimming of streams by social graph * Noise reduction and intelligent filtering * Federation of streams across disparate systems * Provide libraries for easy integration in source systems == Background == The ActivityStreams specification standardizes a generic format for describing event-based data. Many social web companies have adopted the format and it has been included in the OpenSocial specification as the preferred method for delivery of activity data. During discussions of ActivityStreams at OpenSocial events earlier in the year, it became clear that multiple organizations are facing similar issues as to the publication and filtering of their activities and would benefit from a commonly-developed, open-source ActivityStreams server. == Rationale == In deployment, activities are generated from multiple sources. This is particularly true within the enterprise where disparate systems create and manage activities in stove pipes. What is needed is a central point for consumption, aggregation and exposure of activities generated within these systems. == Initial Goals == The initial goal of the project is to survey donated code and develop a common, high-level architecture for an initial release. The project will then work toward that release in a new code base, pulling in pieces of donated code as necessary. == Current Status == The MITRE Corporation will donate its prototype code to the project. Aside from this, the project is new and will need bootstrap time to develop an initial architecture and roadmap. Meritocracy As a new project with many team members who are seasoned Apache veterans, Apache Streams is prepared to build the project under the Apache Way. Community The Apache Streams community combines multiple individuals from different organizations, many of which have collaborated before in an open environment. Apache Streams is committed to expanding this community and adhering to Apache principles of openness and collaboration. == Known Risks == An exercise in self-knowledge. Risks don't mean that a project is unacceptable. If they are recognized and noted then they can be addressed during incubation. Inexperience with Open Source Most of the initial committers have worked in open source and many are familiar with the ASF and the Apache Way; but, not all. Additionally, many of the committers have not worked on a software project together and will need time to familiarize themselves with each other. Speed of Development This project is dependent upon contributions made on company time. For this approach to succeed, the project must deliver a workable system in a timeframe acceptable to those companies. The initial parties have the intention of releasing a first version within 6 months after starting the Incubator. Failure to do so could prevent the project reaching critical mass, and could prevent the project from being in a position to attract new developers. Reliance on Salaried Developers At present, the vast majority of contributors will be doing so as a part of their day jobs. Therefore, as already alluded to, there is a risk that the project won't gain enough traction to be of use to their employers. However, given the centrality of these codebases to the participating companies, it is clearly in their best interests to transition to an openly developed alternative. Relationships with Other Apache Products Many of the initial committers will be integrating this software with Apache Rave Apache Shindig. A possibility exists that code is developed by either or both of the projects to support integration with
Re: [VOTE] Release Apache Bloodhound 0.2 (incubating)
Apologies for the delay, the conference wifi was taken down before I could send the e-mail. Unfortunately, when I ran a license header check, the report came back with some minified css js files in the source release. As far as I am aware, minified files are not considered source and therefore should not be in the distribution. -Matt On 10/29/12 10:22 AM, Joachim Dreimann joachim.dreim...@wandisco.com wrote: Hi, I would like to request the beginning of the vote for the second release of Apache Bloodhound in the incubator following the successful vote by the Bloodhound PPMC. The result of the vote is summarised here: http://markmail.org/thread/zrgkleendiqvanzs The artefacts for the release including the source distribution and KEYS can be found here: https://dist.apache.org/repos/dist/dev/incubator/bloodhound/ The release itself is created from: https://svn.apache.org/repos/asf/incubator/bloodhound/branches/0.2 (r1394550) Issues identified to be fixed for the next release are listed here: https://issues.apache.org/bloodhound/ticket/246 https://issues.apache.org/bloodhound/ticket/245 The vote will be open for at least 72 hours. [ ] +1 Release this package as Apache Bloodhound 0.2 [ ] +0 Don't care [ ] -1 Do not release this package (please explain) Cheers, Joe - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Bloodhound 0.2 (incubating)
On 11/5/12 6:38 AM, Joachim Dreimann joachim.dreim...@wandisco.com wrote: +1 (non-binding) Is there precedent on releasing with less than three +1s from IPMC members if there are no 0s or -1s from anyone at all? The minimum required 72 hours have also passed. Unfortunately, a release requires at least 3 IPMC members to vote +1. I am looking at it now and will cast a vote when I have properly reviewed the release. We'd really like to establish a frequent release cycle, Bloodhound 0.3 is already ready to be packaged up as soon as 0.2 has been released. Thanks, Joe On 31 October 2012 21:49, Marvin Humphrey mar...@rectangular.com wrote: On Mon, Oct 29, 2012 at 7:22 AM, Joachim Dreimann joachim.dreim...@wandisco.com wrote: The result of the vote is summarised here: http://markmail.org/thread/zrgkleendiqvanzs This message didn't include an IPMC tally, but I see that Mentor Branko Čibej voted on the bloodhound-dev thread. That makes one IPMC member voting +1; two more are needed. The vote will be open for at least 72 hours. Less than a day left... any takers? Marvin Humphrey -- Joe Dreimann UX Designer | WANdisco http://www.wandisco.com/ * * *Transform your software development department. Register for a free SVN HealthCheck http://go.wandisco.com/HealthCheck-Sig.html * - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [VOTE] [PROPOSAL] Apache Steams Project
Hi Jason, It is a little early for the vote. We want to make sure everyone has sufficient time to comment. The vote will be held shortly. Matt Sent from a mobile device -Original Message- From: Jason Letourneau [jletournea...@gmail.commailto:jletournea...@gmail.com] Sent: Wednesday, November 07, 2012 05:18 PM Eastern Standard Time To: general@incubator.apache.org Subject: [VOTE] [PROPOSAL] Apache Steams Project +1 (non-binding)
[PROPOSAL] Apache Steams Project
I would like to propose a new Activity Streams server project to the Incubator. The proposal is on the wiki at the following location: http://wiki.apache.org/incubator/StreamsProposal Streams is a collaborative effort from multiple organizations and individuals working with and around the Activity Streams specification (http://activitystrea.ms). We are looking forward to your feedback and suggestions. -Matt Franklin - COPY OF PROPOSAL FROM http://wiki.apache.org/incubator/StreamsProposal - Apache Streams Proposal == Abstract == Apache Streams will be a lightweight server for ActivityStreams. The role of Apache Streams is to provide a central point of aggregation, filtering and querying for Activities that have been submitted by disparate systems. Apache Streams also intends to include a mechanism for intelligent filtering and recommendation to reduce the noise to end users. == Proposal == Apache Streams will bring together individuals who are or are looking to increase and centralize the production, consumption and federation of ActivityStreams throughout enterprise organizations and the Internet as a whole. The target features include: * Publication of Activities from multiple systems via HTTP * Aggregation and syndication of streams * Support for security trimming of streams by social graph * Noise reduction and intelligent filtering * Federation of streams across disparate systems * Provide libraries for easy integration in source systems == Background == The ActivityStreams specification standardizes a generic format for describing event-based data. Many social web companies have adopted the format and it has been included in the OpenSocial specification as the preferred method for delivery of activity data. During discussions of ActivityStreams at OpenSocial events earlier in the year, it became clear that multiple organizations are facing similar issues as to the publication and filtering of their activities and would benefit from a commonly-developed, open-source ActivityStreams server. == Rationale == In deployment, activities are generated from multiple sources. This is particularly true within the enterprise where disparate systems create and manage activities in stove pipes. What is needed is a central point for consumption, aggregation and exposure of activities generated within these systems. == Initial Goals == The initial goal of the project is to survey donated code and develop a common, high-level architecture for an initial release. The project will then work toward that release in a new code base, pulling in pieces of donated code as necessary. == Current Status == The MITRE Corporation will donate its prototype code to the project. Aside from this, the project is new and will need bootstrap time to develop an initial architecture and roadmap. Meritocracy As a new project with many team members who are seasoned Apache veterans, Apache Streams is prepared to build the project under the Apache Way. Community The Apache Streams community combines multiple individuals from different organizations, many of which have collaborated before in an open environment. Apache Streams is committed to expanding this community and adhering to Apache principles of openness and collaboration. == Known Risks == An exercise in self-knowledge. Risks don't mean that a project is unacceptable. If they are recognized and noted then they can be addressed during incubation. Inexperience with Open Source Most of the initial committers have worked in open source and many are familiar with the ASF and the Apache Way; but, not all. Additionally, many of the committers have not worked on a software project together and will need time to familiarize themselves with each other. Speed of Development This project is dependent upon contributions made on company time. For this approach to succeed, the project must deliver a workable system in a timeframe acceptable to those companies. The initial parties have the intention of releasing a first version within 6 months after starting the Incubator. Failure to do so could prevent the project reaching critical mass, and could prevent the project from being in a position to attract new developers. Reliance on Salaried Developers At present, the vast majority of contributors will be doing so as a part of their day jobs. Therefore, as already alluded to, there is a risk that the project won't gain enough traction to be of use to their employers. However, given the centrality of these codebases to the participating companies, it is clearly in their best interests to transition to an openly developed alternative. Relationships with Other Apache Products Many of the initial committers will be integrating this software with Apache Rave Apache Shindig. A possibility exists that code is developed by either or both of the projects to support integration with
Re: [VOTE][PROPOSAL] Hadoop Development Tools
+1 (binding) On 11/6/12 10:57 AM, Adam Berry ambe...@yahoo-inc.com wrote: Hello, This proposal has been open for discussion for a a few weeks, so now submitting for a vote for this project to be accepted into the incubator. Cheers, Adam Berry = HDT (Hadoop Development Tools) = == Abstract == Tools to support developing applications that use Apache Hadoop from within Eclipse. == Proposal == Hadoop Development Tools are a set of extensions to Eclipse providing support for creating, launching and debugging distributed applications, as well as interacting with HDFS filesystems. This work will build on the existing Map Reduce Tools present in the Apache Hadoop project. == Background == Map Reduce Tools have existed as part of contrib for Apache Hadoop. Unfortunately they are source tied to a single version of Hadoop, and development has stalled, with little movement past the Hadoop 0.20 line. == Rationale == Support for newer versions of Hadoop from within Eclipse is regularly raised on the Hadoop mailing lists, so there is a clear need to drive these tools forward. Development tools generally are worked on separate from the target tools/platform, separating the tools out will allow for supporting multiple versions, so a developer could work with a heterogeneous environment. == Initial Goals == * Give the tools project a home of its own. * Port current MapReduce tools feature set to all current release lines of Hadoop in a single Eclipse install. * Documentation and tutorials for all features. * Publish Eclipse update site, and join Eclipse marketplace listing. * Establish release cycle that combines support for Hadoop and Eclipse release cycles. * Look to build support for YARN, MRUnit and possibly other Hadoop-related projects. == Current Status == The source for the current MapReduceTools lives in the contrib section of the Hadoop source. In its current implementation it is tied to the version of Hadoop against which it is compiled. The layout and API that it was developed with means that it can only be used with the 0.20 or 1.0 Hadoop releases, the new layout and YARN api introduced with the 0.23 and 2.0 lines are not supported. === Meritocracy === Several people and companies have already expressed an interest in contributing to this project, and we hope to attract additional interest during the proposal discussion. We plan to invest and support a meritocracy that attracts, invites, and supports newcomers to build a vibrant and diverse community. === Community === The target community is developers who are working developing Map/Reduce applications against Hadoop. Given the success of Hadoop the target group is likely to be quite large. Separation from the Hadoop community would make it easier to support multiple versions of hadoop, as well as merging the release cycles of Hadoop and Eclipse to provide predictable iteration and improvement in the toolset. === Core Developers === The initial list of developers includes people experienced with Hadoop and developing against the Eclipse platform. * Adam Berry (amberry at yahoo-inc dot com) * Jeffrey Zemerick (jeffrrey at mtnfog dot com) * Evert Lammerts (Evert dot Lammerts at sara dot nl) * Simone Gianni (simoneg at apache dot org) === Alignment === Hadoop Development Tools aligns with both Hadoop and Eclipse. Hadoop as the platform for the development target, and Eclipse as the IDE platform used as the base for the tools. == Known Risks == === Orphaned Products === === Inexperience with Open Source === The committers have experience with Apache and Eclipse open source development. === Reliance on Salaried Developers === Hadoop Development Tools will be developed with a mix of salaried and volunteer time. === Relationships with Other Apache Projects === Hadoop Development Tools is closely related to Apache Hadoop. === An Excessive Fascination with the Apache Brand === Given the success of Hadoop and associated projects, Apache is the natural place for the Hadoop Development Tools. Chris Mattman suggested the Apache Incubator as appropriate on the Hadoop general mailing list following the success that MRUnit had taking the path from Hadoop contrib to an Apache top level project. == Documentation == Documentation for the current tools can be found at http://wiki.apache.org/hadoop/EclipsePlugIn == Initial Source == http://svn.apache.org/repos/asf/hadoop/common/trunk/hadoop-mapreduce-proje ct/src/contrib/eclipse-plugin/ == Source and Intellectual Property Submission Plan == The source, and any suggested initial patches, are already hosted either in Apache¹s Subversion or JIRA. == External Dependencies == Eclipse Platform Eclipse Java Development Tools == Cryptography == Hadoop Development Tools likely does not fall into this area. == Required Resources == === Mailing lists === * hdt-dev * hdt-commits * hdt-user === Git Repository === * git://git.apache.org/incubator-hdt.git === Issue Tracking === *
RE: [VOTE] Graduate Wookie podling from the incubator
+1 -Original Message- From: Scott Wilson [mailto:scott.bradley.wil...@gmail.com] Sent: Wednesday, October 24, 2012 2:33 PM To: general@incubator.apache.org Subject: [VOTE] Graduate Wookie podling from the incubator This is a call for vote to graduate the Wookie podling from Apache Incubator. Wookie entered the Incubator in July of 2009. During incubation, Wookie has: * Produced 5 releases * Added 3 new Committer/PPMC members * Cleared IP on all donations * Learned to self-govern and engage the community * Received and applied multiple community patches The Wookie community has voted to proceed with graduation [1] and the result can be found at [2]. Please VOTE on the resolution below: [ ] +1 Graduate Wookie from the Incubator per the resolution below. [ ] +0 Don't care. [ ] -1 Don't graduate Wookie from the Incubator because.. This vote will be open for at least 72 hours. [1] http://markmail.org/message/jcgdcacn535jqwqy [2] http://markmail.org/message/hp2bggjhec7vpdch == X. Establish the Apache Wookie 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 related to an implementation of the W3C Widgets family of specifications for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Wookie Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Wookie Project be and hereby is responsible for the creation and maintenance of software related to implementation of the W3C Widgets family of specifications; and be it further RESOLVED, that the office of Vice President, Apache Wookie 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 Wookie Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Wookie 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 Wookie Project: * Scott Wilsonscot...@apache.org * Ate Douma a...@apache.org * Ross Gardlerrgard...@apache.org * Matt Franklin mfrank...@apache.org * Paul Sharples psharp...@apache.org * Kris Popat krispo...@apache.org * Raido Kuli ra...@apache.org * Hoang Minh Tien h...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Scott Wilson be appointed to the office of Vice President, Apache Wookie, 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 Wookie 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 Wookie Project; and be it further RESOLVED, that the Apache Wookie Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Wookie podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Wookie podling encumbered upon the Apache Incubator Project are hereafter discharged. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [VOTE] Ripple Emulator to be admitted to the incubator
+1 (binding) -Original Message- From: Gord Tanner [mailto:gtan...@gmail.com] Sent: Thursday, October 11, 2012 12:04 PM To: general@incubator.apache.org Subject: [VOTE] Ripple Emulator to be admitted to the incubator Please cast your votes! [ ] +1, recommend Ripple to move into the incubator [ ] +0, abstain/don't care [ ] -1, do not recommend Ripple to move into the incubator,because... Ripple, A Mobile Environment Emulator = Abstract Ripple is a browser based mobile phone emulator designed to aid in the development of HTML5 based mobile applications. Ripple is a cross platform and cross runtime testing/debugging tool. It currently supports such runtimes as Cordova, WebWorks and the Mobile Web. Proposal Ripple is going to be (in some circles already is) the goto emulator for rapid development of mobile web applications. This will be accomplished by quickly keeping up with the mobile web platforms as they arise (Cordova, Tizen, WAC, WebWorks, etc). Background == Ripple started as a product of tinyHippos and was aquired by Research in Motion in late March 2011. Ripple was then open sourced under the Apache 2.0 License and hosted on the blackberry github account (http://github.com/blackberry/Ripple-UI). Ripple is a browser based mobile phone emulator that runs as a chrome extension. It fills the gap for developers between developing on their desktops/laptops and having to test on platform specific emulators or physical devices. Ripple allows develors to quickly edit-refresh-test in Chrome on their desktops/laptops while working on web content that will be embedded and distributed as a native application. Rationale = The project is currently opensourced and managed by a small team at Research in Motion. We are starting to have some more community engagement but the project could benefit from greater exposure in the open source cummunity. Our team overlaps highly with the Cordova group. Watching the success for that project in Apache has inspired us to contribute Ripple to the ASF as well. Ripple fills a large gap in the toolset for most mobile web developers between development on the desktop and testing on the physical device. Current Status == Currently all development is managed on github via the issues and the direction of the project is strongly influenced by Research in Motion. A more clear project plan and more open communication will be needed by this project to abide by the apache guidelines. Metriocracy === Ripple has been very accepting of letting in patches from 3rd party developers and has been functioning like apache in requiring a CLA for code to be pulled in. The core team is hoping to grow and include more developers. Community = The development community of Ripple is a small but tight knit group but the users of the project number more than 40,000. With the launch ofemulate.phonegap.com (which is a portal for installing ripple) we are getting approx 5000 hits a day to that site. Core Developers === See Inital Committers below. Alignment = Apache is a good match for this project due to it's close ties to the Cordova Project. Cordova has been very successful as a project since joining Apache and we hope Ripple will follow suit. Known Risks === Orphaned Products - Ripple is a core component to the toolset at RIM and the Cordova / Phonegap community has embrased ripple into their tooling as well. This project has been under active development for 3 years and a lot of vested interest from both RIM and the community is already present to keep the tool up to date. Inexperience with Open Source - Ripple has been opensourced at RIM for the last year. All of the work is done in the open. There are a few extra measures we need to learn how to take (mailing lists, project planning) for working within the ASF community. However the team has a good understanding of what needs to happen, as some of the team are also contributers to the Apache Cordova Incubator project. Homogenous Developers -- Ripple's core team currently all works at RIM with contributions for some features done by third parties. There is a backlog of features currently done / being put in by third parties such as Adobe and IBM. Reliance on Salaried Developers --- Most of the developers are paid by their employer to contribute to this project but are all highly involved on a personal level with this project as well as the mobile web community. Relationships with Other Apache Products There is a strong overlap and relationship between the ripple and cordova teams. Gord Tanner is an active commiter in both project and has been ensuring that both projects progress together. An Excessive Fascination with the Apache Brand.
Tashi: A Shepherd's View
I am concerned about the lack of mail list and JIRA activity for the podling since the last reporting period. There has been very little activity, but the report indicates a lot of work was completed. I did see a bunch of commits in August, but the only e-mails on the list were from the committing developer and there were only 2 at that. In short, it appears that Tashi does not currently have sufficient community activity to be on a path to graduation. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: Preparing for the October reports
-Original Message- From: Franklin, Matthew B. [mailto:mfrank...@mitre.org] Sent: Wednesday, October 10, 2012 9:18 PM To: general Subject: RE: Preparing for the October reports -Original Message- From: Jukka Zitting [mailto:jukka.zitt...@gmail.com] Sent: Wednesday, October 10, 2012 7:28 PM To: general Subject: Re: Preparing for the October reports Hi, On Mon, Sep 24, 2012 at 10:34 PM, Jukka Zitting jukka.zitt...@gmail.com wrote: It would be nice if we had all reviews ready by Tuesday, October 9th, to give one extra day for unexpected delays. I'm again running a bit late on completing the Incubator report. I hope to have it finished and submitted already tomorrow, but for that we still need the following shepherd reviews: Dave Fisher - Celix Jukka Zitting- EasyAnt Matt Franklin- CloudStack, Tashi Matt Hogstrom- VXQuery Ross Gardler - DeviceMap, JSPWiki Let us know if you won't have time to do the review by tomorrow, so I or someone else can jump in where needed. I will have mine in tomorrow morning. Apologies for the tardiness. I have reviewed both communities and sent notes regarding Tashi. Cloudstack looks to be settling in nicely. BR, Jukka Zitting - 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: Preparing for the October reports
-Original Message- From: Jukka Zitting [mailto:jukka.zitt...@gmail.com] Sent: Wednesday, October 10, 2012 7:28 PM To: general Subject: Re: Preparing for the October reports Hi, On Mon, Sep 24, 2012 at 10:34 PM, Jukka Zitting jukka.zitt...@gmail.com wrote: It would be nice if we had all reviews ready by Tuesday, October 9th, to give one extra day for unexpected delays. I'm again running a bit late on completing the Incubator report. I hope to have it finished and submitted already tomorrow, but for that we still need the following shepherd reviews: Dave Fisher - Celix Jukka Zitting- EasyAnt Matt Franklin- CloudStack, Tashi Matt Hogstrom- VXQuery Ross Gardler - DeviceMap, JSPWiki Let us know if you won't have time to do the review by tomorrow, so I or someone else can jump in where needed. I will have mine in tomorrow morning. Apologies for the tardiness. BR, Jukka Zitting - 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: key signing
-Original Message- From: Marvin Humphrey [mailto:mar...@rectangular.com] Sent: Friday, October 05, 2012 8:54 PM To: general@incubator.apache.org Subject: Re: key signing On Fri, Oct 5, 2012 at 8:55 AM, Jukka Zitting jukka.zitt...@gmail.com wrote: It's good to recommend people to get their keys signed by someone in the Apache web of trust and I think we could do more in that area, Maybe if we didn't insist on face-to-face meetings we'd get better adoption rates. Apache dev docs: http://www.apache.org/dev/openpgp.html#wot-link-in How To Link Into A Public Web Of Trust In short, expect that: * this will involve a face-to-face meeting GnuPG docs: http://www.gnupg.org/gph/en/manual.html#AEN84 A key's fingerprint is verified with the key's owner. This may be done in person or over the phone or through any other means as long as you can guarantee that you are communicating with the key's true owner. +1. I think with technologies like Skype Google Hangout, we can get the same level of assurance of a person's identity as a physical key signing party. What if we held a regular Google Hangout Key Signing party? We can always ask participants to show IDs :) 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
Isis: A Shepherd's View
Good report. Two questions/comments: - Why not just propose the committers and see what the PPMC thinks before holding an official vote? Is there a reason for waiting? - The incubator status page needs to be completed. It appears that more has happened than the page reflects. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Wave: A Shepherd's View
Is there anything that could be released, even in alpha/beta form? Code completeness or maturity is not a barrier to graduation so long as the community can demonstrate an understanding of the Apache release process. IMO, it is best to get early, alpha releases out on a regular basis. You don't have to advertise them as completely ready for prime time. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
NPanday: A Shepherd's View
I am concerned about the level of engagement of the community. The vast majority of mail traffic has been from automated build failures and even a question from a potential user saw no response from the committers/PPMC. IMHO, there needs to be a significant increase in engagement over time before the project would be ready to graduate. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: September Reports
-Original Message- From: Franklin, Matthew B. [mailto:mfrank...@mitre.org] Sent: Thursday, September 13, 2012 11:58 AM To: general@incubator.apache.org Subject: RE: September Reports -Original Message- From: Jukka Zitting [mailto:jukka.zitt...@gmail.com] Sent: Thursday, September 13, 2012 10:54 AM To: general@incubator.apache.org Subject: Re: September Reports Hi, On Thu, Sep 13, 2012 at 12:53 PM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: I have some time tonight is there something I can help in ? Sure, thanks! It would be great if you could take a look at some of the following reports unless the previously assigned shepherds beat you to it: Matt Franklin- Isis, NPanday, Wave I am in progress with these and will have reviewed them by end of day. Additional eyes don't hurt though. Apologies. Yesterday turned out to be impractical for me. I have finished my reviews and posted to the wiki list. Matt Hogstrom- Bigtop, Openmeetings BR, Jukka Zitting - 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: September Reports
-Original Message- From: Jukka Zitting [mailto:jukka.zitt...@gmail.com] Sent: Thursday, September 13, 2012 10:54 AM To: general@incubator.apache.org Subject: Re: September Reports Hi, On Thu, Sep 13, 2012 at 12:53 PM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: I have some time tonight is there something I can help in ? Sure, thanks! It would be great if you could take a look at some of the following reports unless the previously assigned shepherds beat you to it: Matt Franklin- Isis, NPanday, Wave I am in progress with these and will have reviewed them by end of day. Additional eyes don't hurt though. Matt Hogstrom- Bigtop, Openmeetings BR, Jukka Zitting - 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: Usage of JRebel in Apache projects
-Original Message- From: seba.wag...@gmail.com [mailto:seba.wag...@gmail.com] Sent: Wednesday, September 12, 2012 3:06 AM To: general@incubator.apache.org Cc: openmeetings-...@incubator.apache.org Subject: Usage of JRebel in Apache projects Hi, JRebel already offers a 1 year for free license for OSS projects. But I wonder if there is already a License for the Apache Foundation that committers can use? My understanding of their terms is that it is a per-project license. Unless other IPMC members have better information, I think you can just request a license on behalf of your project and manage its distribution via a private SVN location. Thanks! Sebastian -- Sebastian Wagner https://twitter.com/#!/dead_lock http://www.webbase-design.de http://www.wagner-sebastian.com seba.wag...@gmail.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
RE: [VOTE] Graduate Airavata from the incubator
+1 -Original Message- From: Suresh Marru [mailto:sma...@apache.org] Sent: Friday, September 07, 2012 6:59 AM To: general@incubator.apache.org Subject: [VOTE] Graduate Airavata from the incubator Hi All, Since entering Incubation in May 2011, the Airavata community has evolved and has been steadily growing. The project has made 3 releases, added 6 new committers and PPMC members. The podling has been very actively using mailing list and JIRA and all communication is in open. Thanks to very hands-on mentors, the project has learned to self-govern and has been following the Apache Way. The project incubator status page [1] is up to date and trademarks has approved Airavata as a name for TLP [2]. The community has discussed graduation and prepared a board charter [3]. The initial PMC has been opted in on the private mailing list and PMC chair has been elected on the dev list [4]. The community feels ready to graduate [5] and voted 19 positives votes and no negative votes. We request the IPMC to vote on the resolution to establish Airavata and to recommend the resolution to the board. Please cast your vote : [ ] +1 Graduate Airavata podling from Apache Incubator [ ] -1 Airavata podling is not yet ready to graduate because This vote will be open for at least 72 hours. Please find the proposed board resolution below. Cheers, Suresh [1] http://incubator.apache.org/projects/airavata.html [2] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-14 [3] http://markmail.org/message/gsq3jnwi6lpnz7tq [4] http://markmail.org/message/7ngzcbvpzhl2phlp [5] http://markmail.org/message/s3tubyx7bpxwbqiz X. Establish the Apache Airavata 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 related to executing and managing computational jobs on distributed computing resources including local clusters, supercomputers, national grids, academic and commercial clouds and for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Airavata Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Airavata Project be and hereby is responsible for the creation and maintenance of software related to executing and managing computational jobs on distributed computing resources including local clusters, supercomputers, national grids, academic and commercial clouds; and be it further RESOLVED, that the office of Vice President, Apache Airavata 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 Airavata Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Airavata 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 Airavata Project: Aleksander Slominski as...@apache.org Ate Douma a...@apache.org Chathura Herath chath...@apache.org Eran Chinthakachinth...@apache.org Srinath Pererahemap...@apache.org Heshan Suriyaarachchi hes...@apache.org Lahiru Gunathilakelah...@apache.org Marlon Pierce mpie...@apache.org Patanachai Tangchaisinpatanac...@apache.org Raminderjeet Singhramin...@apache.org Saminda Wijeratne sami...@apache.org Shahani Weerawarana shah...@apache.org Suresh Marru sma...@apache.org Thilina Gunarathnethil...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Suresh Marru be appointed to the office of Vice President, Apache Airavata, 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 Airavata 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 Airavata Project; and be it further RESOLVED, that the Apache Airavata Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Airavata podling; and be it
Re: [VOTE] Apache OpenMeetings Moodle Plugin 1.4 Incubating Release Candidate 1
+1 (binding) for the release. On 8/10/12 7:47 AM, Franklin, Matthew B. mfrank...@mitre.org wrote: If no one else beats me to it, I will review this before the end of the weekend. s/the weekend/Monday (apologies) -Matt -Original Message- From: seba.wag...@gmail.com [mailto:seba.wag...@gmail.com] Sent: Friday, August 10, 2012 7:28 AM To: general@incubator.apache.org Cc: openmeetings-...@incubator.apache.org Subject: Re: [VOTE] Apache OpenMeetings Moodle Plugin 1.4 Incubating Release Candidate 1 Thanks Alexei! Still 1 IPMC vote missing Thanks Sebastian 2012/8/10 Alexei Fedotov alexei.fedo...@gmail.com +1 -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Fri, Aug 10, 2012 at 11:32 AM, seba.wag...@gmail.com seba.wag...@gmail.com wrote: Yegor Jukka thanks for review and voting! We still need one IPMC vote to approve that release. Those are just integration plugins for the ELearning Platform Moodle. roughly 20 files zipped to packages, ~40KByte each, zero dependencies, 2 minutes to check :) Release artefacts: http://people.apache.org/~sebawagner/moodle-plugin-1.4-incubating/ Thanks! Sebastian 2012/8/9 Yegor Kozlov yegor.koz...@dinom.ru +1 Yegor On Mon, Aug 6, 2012 at 4:44 PM, seba.wag...@gmail.com seba.wag...@gmail.com wrote: Dear Incubator Members, I would like to start a vote about releasing Apache OpenMeetings Moodle Plugin 1.4 Incubating Release Candidate 1 There was already a positive vote on the developer mailing list: +1 PPMC: solomax, albus, eschwert, german, aaf(mentor), sebawagner Vote Thread: http://markmail.org/thread/db4bhkroe6yun5bi Changes are in the Changelog: http://svn.apache.org/repos/asf/incubator/openmeetings/tags/plugins/moo dle/1.4RC1/CHANGELOG Release artefacts: http://people.apache.org/~sebawagner/moodle-plugin-1.4- incubating/ Tag: http://svn.apache.org/repos/asf/incubator/openmeetings/tags/plugins/moo dle/1.4RC1/ PGP release keys (signed using 93A30395): http://www.apache.org/dist/incubator/openmeetings/KEYS Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks! Sebastian -- Sebastian Wagner https://twitter.com/#!/dead_lock http://www.webbase-design.de http://www.wagner-sebastian.com seba.wag...@gmail.com -- Sebastian Wagner https://twitter.com/#!/dead_lock http://www.webbase-design.de http://www.wagner-sebastian.com seba.wag...@gmail.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Sebastian Wagner https://twitter.com/#!/dead_lock http://www.webbase-design.de http://www.wagner-sebastian.com seba.wag...@gmail.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
RE: [VOTE] Apache OpenMeetings Moodle Plugin 1.4 Incubating Release Candidate 1
If no one else beats me to it, I will review this before the end of the weekend. -Matt -Original Message- From: seba.wag...@gmail.com [mailto:seba.wag...@gmail.com] Sent: Friday, August 10, 2012 7:28 AM To: general@incubator.apache.org Cc: openmeetings-...@incubator.apache.org Subject: Re: [VOTE] Apache OpenMeetings Moodle Plugin 1.4 Incubating Release Candidate 1 Thanks Alexei! Still 1 IPMC vote missing Thanks Sebastian 2012/8/10 Alexei Fedotov alexei.fedo...@gmail.com +1 -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Fri, Aug 10, 2012 at 11:32 AM, seba.wag...@gmail.com seba.wag...@gmail.com wrote: Yegor Jukka thanks for review and voting! We still need one IPMC vote to approve that release. Those are just integration plugins for the ELearning Platform Moodle. roughly 20 files zipped to packages, ~40KByte each, zero dependencies, 2 minutes to check :) Release artefacts: http://people.apache.org/~sebawagner/moodle-plugin-1.4-incubating/ Thanks! Sebastian 2012/8/9 Yegor Kozlov yegor.koz...@dinom.ru +1 Yegor On Mon, Aug 6, 2012 at 4:44 PM, seba.wag...@gmail.com seba.wag...@gmail.com wrote: Dear Incubator Members, I would like to start a vote about releasing Apache OpenMeetings Moodle Plugin 1.4 Incubating Release Candidate 1 There was already a positive vote on the developer mailing list: +1 PPMC: solomax, albus, eschwert, german, aaf(mentor), sebawagner Vote Thread: http://markmail.org/thread/db4bhkroe6yun5bi Changes are in the Changelog: http://svn.apache.org/repos/asf/incubator/openmeetings/tags/plugins/moo dle/1.4RC1/CHANGELOG Release artefacts: http://people.apache.org/~sebawagner/moodle-plugin-1.4- incubating/ Tag: http://svn.apache.org/repos/asf/incubator/openmeetings/tags/plugins/moo dle/1.4RC1/ PGP release keys (signed using 93A30395): http://www.apache.org/dist/incubator/openmeetings/KEYS Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks! Sebastian -- Sebastian Wagner https://twitter.com/#!/dead_lock http://www.webbase-design.de http://www.wagner-sebastian.com seba.wag...@gmail.com -- Sebastian Wagner https://twitter.com/#!/dead_lock http://www.webbase-design.de http://www.wagner-sebastian.com seba.wag...@gmail.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Sebastian Wagner https://twitter.com/#!/dead_lock http://www.webbase-design.de http://www.wagner-sebastian.com seba.wag...@gmail.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [VOTE] Accept Drill into the Apache Incubator
+1 (binding) -Original Message- From: Ted Dunning [mailto:ted.dunn...@gmail.com] Sent: Tuesday, August 07, 2012 10:41 PM To: general@incubator.apache.org Subject: [VOTE] Accept Drill into the Apache Incubator I would like to call a vote for accepting Drill for incubation in the Apache Incubator. The full proposal is available below. Discussion over the last few days has been quite positive. Please cast your vote: [ ] +1, bring Drill into Incubator [ ] +0, I don't care either way, [ ] -1, do not bring Drill into Incubator, because... This vote will be open for 72 hours and only votes from the Incubator PMC are binding. The start of the vote is just before 3AM UTC on 8 August so the closing time will be 3AM UTC on 11 August. Thank you for your consideration! Ted http://wiki.apache.org/incubator/DrillProposal = Drill = == Abstract == Drill is a distributed system for interactive analysis of large-scale datasets, inspired by [[http://research.google.com/pubs/pub36632.html|Google's Dremel]]. == Proposal == Drill is a distributed system for interactive analysis of large-scale datasets. Drill is similar to Google's Dremel, with the additional flexibility needed to support a broader range of query languages, data formats and data sources. It is designed to efficiently process nested data. It is a design goal to scale to 10,000 servers or more and to be able to process petabyes of data and trillions of records in seconds. == Background == Many organizations have the need to run data-intensive applications, including batch processing, stream processing and interactive analysis. In recent years open source systems have emerged to address the need for scalable batch processing (Apache Hadoop) and stream processing (Storm, Apache S4). In 2010 Google published a paper called Dremel: Interactive Analysis of Web-Scale Datasets, describing a scalable system used internally for interactive analysis of nested data. No open source project has successfully replicated the capabilities of Dremel. == Rationale == There is a strong need in the market for low-latency interactive analysis of large-scale datasets, including nested data (eg, JSON, Avro, Protocol Buffers). This need was identified by Google and addressed internally with a system called Dremel. In recent years open source systems have emerged to address the need for scalable batch processing (Apache Hadoop) and stream processing (Storm, Apache S4). Apache Hadoop, originally inspired by Google's internal MapReduce system, is used by thousands of organizations processing large-scale datasets. Apache Hadoop is designed to achieve very high throughput, but is not designed to achieve the sub-second latency needed for interactive data analysis and exploration. Drill, inspired by Google's internal Dremel system, is intended to address this need. It is worth noting that, as explained by Google in the original paper, Dremel complements MapReduce-based computing. Dremel is not intended as a replacement for MapReduce and is often used in conjunction with it to analyze outputs of MapReduce pipelines or rapidly prototype larger computations. Indeed, Dremel and MapReduce are both used by thousands of Google employees. Like Dremel, Drill supports a nested data model with data encoded in a number of formats such as JSON, Avro or Protocol Buffers. In many organizations nested data is the standard, so supporting a nested data model eliminates the need to normalize the data. With that said, flat data formats, such as CSV files, are naturally supported as a special case of nested data. The Drill architecture consists of four key components/layers: * Query languages: This layer is responsible for parsing the user's query and constructing an execution plan. The initial goal is to support the SQL-like language used by Dremel and [[https://developers.google.com/bigquery/docs/query-reference|Google BigQuery]], which we call DrQL. However, Drill is designed to support other languages and programming models, such as the [[http://www.mongodb.org/display/DOCS/Mongo+Query+Language|Mongo Query Language]], [[http://www.cascading.org/|Cascading]] or [[https://github.com/tdunning/Plume|Plume]]. * Low-latency distributed execution engine: This layer is responsible for executing the physical plan. It provides the scalability and fault tolerance needed to efficiently query petabytes of data on 10,000 servers. Drill's execution engine is based on research in distributed execution engines (eg, Dremel, Dryad, Hyracks, CIEL, Stratosphere) and columnar storage, and can be extended with additional operators and connectors. * Nested data formats: This layer is responsible for supporting various data formats. The initial goal is to support the column-based format used by Dremel. Drill is designed to support schema-based formats such as Protocol Buffers/Dremel, Avro/AVRO-806/Trevni and CSV, and schema-less formats such as JSON, BSON or YAML. In addition, it is designed to support
RE: Preparing for August report
I reviewed droids and thought their report adequately represented the project state. -Original Message- From: Jukka Zitting [jukka.zitt...@gmail.commailto:jukka.zitt...@gmail.com] Sent: Wednesday, August 08, 2012 06:37 PM Eastern Standard Time To: general Subject: Re: Preparing for August report Hi, On Mon, Aug 6, 2012 at 12:14 PM, Jukka Zitting jukka.zitt...@gmail.com wrote: That leaves only the reviews to be done. Here's the latest TODO list: And an updated one: Benson Margulies - Syncope, Nuvem Dave Fisher - DeltaSpike Matt Franklin- Droids Matt Hogstrom- SIS, Wookie Mohammad Nour- Airavata Ross Gardler - Wink That's quite a few reports still to review and the report deadline is close. Please let me know if you're still on it (or update the wiki page directly), otherwise I'll take over tomorrow to review any remaining reports. BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [PROPOSAL] Drill for the Apache Incubator
-Original Message- From: Marvin Humphrey [mailto:mar...@rectangular.com] Sent: Monday, August 06, 2012 12:25 PM To: general@incubator.apache.org Cc: Grant Ingersoll; Isabel Drost Subject: Re: [PROPOSAL] Drill for the Apache Incubator On Thu, Aug 2, 2012 at 3:12 PM, Ted Dunning ted.dunn...@gmail.com wrote: Initial Source == There is no initial source code. All source code will be developed within the Apache Incubator. Coming in without any source code is going to pose a challenge to this podling. http://www.apache.org/foundation/how-it-works.html#incubator The incubator filters projects on the basis of the likeliness of them becoming successful meritocratic communities. The basic requirements for incubation are: * a working codebase -- over the years and after several failures, the foundation came to understand that without an initial working codebase, it is generally hard to bootstrap a community. This is because merit is not well recognized by developers without a working codebase. Also, the friction that is developed during the initial design stage is likely to fragment the community. It seems like there could be flexibility in this requirement, based on a few factors. In this case, a design discussion has been ongoing; but I would also think that any community coming in with enough people who know the Apache way may also not need as much of a solid starting point code wise. That last line in particular seems like something to watch out for. 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
Amber - A Shepherd's View
Community looks well on the way to graduation. Congratulations on the recent release. There are a few things on the status page that need to be filled in and processes [1] like suitable name search need to be completed prior to graduation vote at the IPMC level. [1]:http://incubator.apache.org/guides/graduation.html#checklist - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [VOTE] Release Apache Amber 0.22-incubating
+1. Good job Amber team. The sigs check out, headers look good with the exception of the .json files (as expected), LICENSE NOTICE look like due diligence was performed. One note to Simone You need to get your key signed :) -Matt -Original Message- From: simone.trip...@gmail.com [mailto:simone.trip...@gmail.com] On Behalf Of Simone Tripodi Sent: Wednesday, July 18, 2012 3:34 AM To: general@incubator.apache.org Subject: [VOTE] Release Apache Amber 0.22-incubating Good morning IPMC, I'm writing today to submit you the VOTE of the first release ever of Apache Amber 0.22 under the Incubator. PPMC vote already passed on amber-dev@ http://s.apache.org/Ulr with already 1 IPMC binding vote. We solved 28 issues: http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311100; styleName=Htmlversion=12322240 There are still 14 issues left in JIRA: http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=truepid=12 311100status=1 SVN source tag (r1359173): https://svn.apache.org/repos/asf/incubator/amber/tags/amber-0.22- incubating/ Staging repo: https://repository.apache.org/content/repositories/orgapacheamber-039/ Staging binaries: http://people.apache.org/builds/incubator/amber/ Staging site: http://incubator.apache.org/amber/0.22-incubating/ PGP release keys (signed using 19FEA27D): http://www.apache.org/dist/incubator/amber/KEYS Vote will be open for 72 hours and will close ~ on July the 21th at 7:30am GMT [ ] +1, let's get it rmblee!!! [ ] +/-0, fine, but consider to fix few issues before... [ ] -1, nope, because... (and please explain why) Many thanks in advance, all the best! -Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.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: [VOTE] Release Apache Amber 0.22-incubating
-Original Message- From: Tommaso Teofili [mailto:tommaso.teof...@gmail.com] Sent: Wednesday, July 25, 2012 3:55 AM To: general@incubator.apache.org Subject: Re: [VOTE] Release Apache Amber 0.22-incubating Anyone else from the IPMC willing to review this ? I will try to review this before the weekend. Thanks in advance, Tommaso 2012/7/21 Raymond Feng enjoyj...@gmail.com +1 from me. Thanks, Raymond On Jul 18, 2012, at 12:33 AM, Simone Tripodi wrote: Good morning IPMC, I'm writing today to submit you the VOTE of the first release ever of Apache Amber 0.22 under the Incubator. PPMC vote already passed on amber-dev@ http://s.apache.org/Ulr with already 1 IPMC binding vote. We solved 28 issues: http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311100; styleName=Htmlversion=12322240 There are still 14 issues left in JIRA: http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=truepid=12 311100status=1 SVN source tag (r1359173): https://svn.apache.org/repos/asf/incubator/amber/tags/amber-0.22- incubating/ Staging repo: https://repository.apache.org/content/repositories/orgapacheamber- 039/ Staging binaries: http://people.apache.org/builds/incubator/amber/ Staging site: http://incubator.apache.org/amber/0.22-incubating/ PGP release keys (signed using 19FEA27D): http://www.apache.org/dist/incubator/amber/KEYS Vote will be open for 72 hours and will close ~ on July the 21th at 7:30am GMT [ ] +1, let's get it rmblee!!! [ ] +/-0, fine, but consider to fix few issues before... [ ] -1, nope, because... (and please explain why) Many thanks in advance, all the best! -Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: Celix: A Shepherd's View
Adding correct list for Celix. -Original Message- From: Franklin, Matthew B. [mailto:mfrank...@mitre.org] Sent: Monday, July 09, 2012 9:57 PM To: general@incubator.apache.org Cc: 'celix-...@apache.org' Subject: Celix: A Shepherd's View Sorry for the late shepherd notes, but I have reviewed the Celix community and it looks like the Celix community is continuing to progress, albeit slowly. A couple of notes: 1) I would recommend trying to accelerate release plans. It takes a lot of work up front, but cutting releases is a critical part of incubation. After 2 years , I would think you should have been able to make at least one release. 2) I would also recommend looking at the branding guidelines[1]. The website seems to be missing a couple of things (like links to Apache homepage [1] http://www.apache.org/foundation/marks/pmcs.html - 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
VXQuery: A Mentor's View
I wanted to echo the recent thread regarding the need for additional mentorship for VXQuery. Cezar only needs to request IPMC membership to become a mentor; but event hen he would be the only mentor that I can find recent activity for. In addition to the need for mentors, there a couple of things that need attention: 1) The website does not follow branding guidelines and it looks like hrefs for images CSS might be incorrect. 2) Someone needs to sign off on the report. I recommend Cezar do this after requesting IPMC membership. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Kafka: A Shepherd's view
Report and community look great. I look forward to a future graduation VOTE :) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: Board will be proposing a new TLP
+1 for straight to TLP given the individuals and code provenance. -Original Message- From: Jim Jagielski [mailto:j...@jagunet.com] Sent: Saturday, June 30, 2012 8:24 AM To: general@incubator.apache.org Subject: Board will be proposing a new TLP For those not following board@, the board is proposing the creation of a new TLP (tentatively called Apache Steve) which will serve as the project behind our STV and voting tools. The impetus behind this was when I suggested to the OpenStack people to use STV for their voting system, which kind of re-kicked the idea in my head that our voting tools were too good to not provide as releasable code to the world at large. Since all code was developed w/i the ASF, by ASF people, and is under the ALv2 (either implied/confirmed by the authors or explicit in the code itself), there is some debate on whether or not Incubation is even required... The board would like to recommend to the Incubator that the board simply proceed with the creation of this project at the next board meeting. Thx. - 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: [VOTE] Retire Kato
+1 -Original Message- From: Benson Margulies [mailto:bimargul...@gmail.com] Sent: Tuesday, June 26, 2012 7:30 PM To: general@incubator.apache.org Subject: [VOTE] Retire Kato Based on the status of this podling as reported in the June board report, I propose that the IPMC retire the Kato podling. I'm not sure how long a vote for this should remain open. here is my +1. - 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: [VOTE] [PROPOSAL] Allura to enter the Incubator
+1 (binding) On 6/21/12 12:34 PM, Rich Bowen rbo...@rcbowen.com wrote: Hi, We are proposing Allura to be admitted to the Apache Incubator, and would like to request that the IPMC votes on this issue. The requisite 72 hours has passed since the initial proposal. The proposal may be found at http://wiki.apache.org/incubator/AlluraProposal Please cast your vote. [ ] +1 I recommend that Allura becomes an Apache Incubator project [ ] 0 Abstain or don't care [ ] -1 No, I do not recommend that Allura becomes an Apache Incubator project yet (because ...) -- Rich Bowen rbo...@rcbowen.com :: @rbowen rbo...@apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Bigtop - A Shepherd's View
I think the Bigtop report is in good shape. From my viewpoint, Bigtop is getting close to graduating; but, I would defer to the mentors who know the project best. It would be nice to see some activity from more of the committers though... - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Flex - A Shepherd's View
Great report. The only comment I have after reviewing the community is that the incubator status page needs to be updated as it is completely empty. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
OpenMeetings - A Shepard's View
The report does not list the top issues for graduation. Also, it appears that there were some practices that are not quite inline with recommendations; though, the mentors have appeared to address this. Other than that, activity and community appear to be strong. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: JIRA and communities
-Original Message- From: Benson Margulies [mailto:bimargul...@gmail.com] Sent: Saturday, May 26, 2012 10:51 AM To: general@incubator.apache.org Subject: Re: JIRA and communities So, what message here should the incubator send a podling, or the foundation send a TLP? I really don't mean this as a rhetorical question at all, I'm honestly puzzled. In the case of Lucene, I've been hanging out for months, and I feel perfectly confident that it's a healthy community by any foundation standard. At the same time, you all are perfectly correct: watching them means dealing with a tsunami of trivia. I'm stumped at what suggestion, let alone demand, I'd deliver to such a community. IMO, we wouldn't want to force a single workflow into each community just because it appears to lower the barrier of entry. I fully understand how JIRA and ReviewBoard can pollute a mail list; however, if that is how the community wants to operate, why stop them? Since everything gets forwarded to the dev list, IMO JIRA and ReviewBoard are perfectly legitimate tools for managing workflows within communities. We can always suggest changes and simplifications, or try out new processes and workflows, but forcing a community to operate a specific way doesn't seem appropriate. One thing I have seen a few podlings do is add a users mail list that offers a lower barrier of entry and allows newcomers to gradually become more immersed in the daily operations of the project. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [VOTE] Accept Crunch into the Apache Incubator
+1 (binding) -Original Message- From: Josh Wills [mailto:jwi...@cloudera.com] Sent: Wednesday, May 23, 2012 2:46 PM To: general@incubator.apache.org Subject: [VOTE] Accept Crunch into the Apache Incubator I would like to call a vote for accepting Apache Crunch for incubation in the Apache Incubator. The full proposal is available below. We ask the Incubator PMC to sponsor it, with phunt as Champion, and phunt, tomwhite, and acmurthy volunteering to be Mentors. Please cast your vote: [ ] +1, bring Crunch into Incubator [ ] +0, I don't care either way, [ ] -1, do not bring Crunch into Incubator, because... This vote will be open for 72 hours and only votes from the Incubator PMC are binding. http://wiki.apache.org/incubator/CrunchProposal Proposal text from the wiki: --- --- = Crunch - Easy, Efficient MapReduce Pipelines in Java and Scala = == Abstract == Crunch is a Java library for writing, testing, and running pipelines of !MapReduce jobs on Apache Hadoop. == Proposal == Crunch is a Java library for writing, testing, and running pipelines of !MapReduce jobs on Apache Hadoop. Its main goal is to provide a high-level API for writing and testing complex !MapReduce jobs that require multiple processing stages. It has a simple, flexible, and extensible data model that makes it ideal for processing data that does not naturally fit into a relational structure, such as time series and serialized object formats like JSON and Avro. It supports running pipelines either as a series of !MapReduce jobs on an Apache Hadoop cluster or in memory on a single machine for fast testing and debugging. == Background == Crunch was initially developed by Cloudera to simplify the process of creating sequences of dependent !MapReduce jobs, especially jobs that processed non-relational data like time series. Its design was based on a paper Google published about a Java library they developed called !FlumeJava that was created in order to solve a similar class of problems. Crunch was open-sourced by Cloudera on !GitHub as an Apache 2.0 licensed project in October 2011. During this time Crunch has been formally released twice, as versions 0.1.0 (October 2010) and 0.2.0 (February 2012), with an incremental update to version 0.2.1 (March 2012) . These releases are also distributed by Cloudera as source and binaries from Cloudera's Maven repository. == Rationale == Most of the interesting analytical and data processing tasks that are run on an Apache Hadoop cluster require a series of !MapReduce jobs to be executed in sequence. Developers who are creating these pipelines today need to manually assign the sequence of tasks to perform in a dependent chain of !MapReduce jobs, even though there are a number of well-known patterns for fusing dependent computations together into a single !MapReduce stage and for performing common types of joins and aggregations. This results in !MapReduce pipelines that are more difficult to test, maintain, and extend to support new functionality. Furthermore, the type of data that is being stored and processed using Apache Hadoop is evolving. Although Hadoop was originally used for storing large volumes of structured text in the form of webpages and log files, it is now common for Hadoop to store complex, structured data formats such as JSON, Apache Avro, and Apache Thrift. These formats allow developers to work with serialized objects in programming languages like Java, C++, and Python, and allow for new types of analysis to be performed on complex data types. Hadoop has also been adopted by the scientific research community, who are using Hadoop to process time series data, structured binary files in the HDF5 format, and large medical and satellite images. Crunch addresses these challenges by providing a lightweight and extensible Java API for defining the stages of a data processing pipeline, which can then be run on an Apache Hadoop cluster as a sequence of dependent !MapReduce jobs, or in-memory on a single machine to facilitate fast testing and debugging. Crunch relies on a small set of primitive abstractions that represent immutable, distributed collections of objects. Developers define functions that are applied to those objects in order to generate new immutable, distributed collections of objects. Crunch also provides a library of common !MapReduce patterns for performing efficient joins and aggregation operations over these distributed collections that developers may integrate into their own pipelines. Crunch also provides native support for processing structured binary data formats like JSON, Apache Avro, and Apache Thrift, and is designed to be extensible to support working with any kind of data format that Java supports in its native form. == Initial Goals == Crunch is currently in its first major release with a considerable number of enhancement
RE: Ambari Status
-Original Message- From: sebb [mailto:seb...@gmail.com] Sent: Thursday, May 10, 2012 6:47 AM To: general@incubator.apache.org Subject: Re: Ambari Status On 10 May 2012 06:05, Owen O'Malley omal...@apache.org wrote: On Wed, May 9, 2012 at 5:56 PM, Franklin, Matthew B. mfrank...@mitre.org wrote: In reviewing the Amabari report, I have a couple of notes/concerns: * The community IMHO is in serious risk of failure to launch. A recent code change has sparked project interest, but list activity was non existent after January. Ambari's code base isn't functional yet and until it is and it is difficult to build a community until a version works. All of the contributors are employed by Hortonworks, which exposes the project to the whims of the company's priorities. There's a new code base that has been checked in on a branch that is close to working. Once there is a working version, I hope that community will build. *As Ambari went nearly 2 months without a single e-mail to the list, I think an issue for graduation should be added that the community must demonstrate viability for X more reporting periods (where x IMO is 2). I agree that Ambari is no where close to graduation and was close to being dead. I hope the new code base will revitalize it. * The list of completed JIRA issues is not very telling of anything and might give the impression that the community is more vibrant than it is It was very active for September to January. I explicitly called out that the project had been dormant since January. Also, I noticed that ddas signed off on it as a mentor. I don't see him listed as an Apache member or IPMC member. He was added to the IPMC. The message from Noel was dated 6 Oct 2011. Note: he is currently listed in committee-info.txt as a member of the IPMC. Missed that yesterday. Thanks for the clarification. Can we update the podling status page to reflect his mentorship of Ambari? -- Owen - 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: Shepherds for podling reports
-Original Message- From: Ross Gardler [mailto:rgard...@opendirective.com] Sent: Thursday, May 10, 2012 8:32 AM To: general@incubator.apache.org Subject: Re: Shepherds for podling reports Thanks Jukka, One of the issues to address for next time is where to record shepherds comments (if any). I suggest we do it directly in the reports, in the Wiki. This requires no additional processes to implement. I thought that the discussions that sprung up around the shepherd comments were very valuable. While in the wiki, we might get to an out of sight, out of mind scenario with these comments and lose the discussions Incubator awareness that they brought. Once the shepherd process is working smoothly I'd also suggest that we think about changing the whole submission process to one identical to that followed by TLPs (i.e. commit to SVN, notify the general@ mailing list). This means that projects are learning how it is done for TLPs whilst also allowing the IPMC to adopt some of the same processes as the board does in providing the IPMC report. +1 Furthermore, once this is also in place for IPMC reports we can use (slightly modified) Whimsy scripts to make shepherds work easier and the posting of reports here provides a place for shepherds/mentors and project members to discuss issues. Ross On 10 May 2012 13:24, Jukka Zitting jukka.zitt...@gmail.com wrote: Hi, I just submitted our May report to the board. Thanks a lot to anyone who chimed in with reviews and other help! Very much appreciated. Let's try this again for the next report, perhaps in a bit more timely and organized manner now that we're through the initial setup and have more volunteers lined up already in advance. Some good comments and ideas were brought up in this thread. Feel free to just go ahead and start implementing any incremental improvements that you think will help. I'm not too concerned about the particular mechanics or processes we use as long as they help generate constructive feedback to and increased dialogue with our podlings. BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Ross Gardler (@rgardler) Programme Leader (Open Development) OpenDirective http://opendirective.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
RE: Shepherds for podling reports
-Original Message- From: Ross Gardler [mailto:rgard...@opendirective.com] Sent: Thursday, May 10, 2012 8:42 AM To: general@incubator.apache.org Subject: Re: Shepherds for podling reports On 10 May 2012 13:39, Franklin, Matthew B. mfrank...@mitre.org wrote: -Original Message- From: Ross Gardler [mailto:rgard...@opendirective.com] Sent: Thursday, May 10, 2012 8:32 AM To: general@incubator.apache.org Subject: Re: Shepherds for podling reports Thanks Jukka, One of the issues to address for next time is where to record shepherds comments (if any). I suggest we do it directly in the reports, in the Wiki. This requires no additional processes to implement. I thought that the discussions that sprung up around the shepherd comments were very valuable. While in the wiki, we might get to an out of sight, out of mind scenario with these comments and lose the discussions Incubator awareness that they brought. I am only talking about where they are *recorded*, they should still be discussed in the same way. OK. Thanks for clarifying. Ross - 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: Flex Status
-Original Message- From: Dave Fisher [mailto:dave2w...@comcast.net] Sent: Thursday, May 10, 2012 10:44 AM To: general@incubator.apache.org Subject: Re: Flex Status On May 10, 2012, at 2:57 AM, Jukka Zitting wrote: Hi, On Thu, May 10, 2012 at 7:03 AM, Dave Fisher dave2w...@comcast.net wrote: I think we'll be able to persuade the PPMC that they don't really want to manage their own JIRA instance once that is done. So, they have a little infra delay. There's a bit of history behind this. Flex was getting a bit frustrated at the slow migration progress, so last month I suggested [1] an external server as an interim solution. I totally agree that it's not an ideal or in any way final solution, but without some progress on this Flex will soon hit six months without effective development infrastructure. That's horrible. If not an external server, can we provision a new ASF server for this, perhaps just a virtual one to start with? Infrastructure is working on a JIRA upgrade and Flex can participate. Help is needed with the ASF license checkbox code. I'm hoping to have cycles to help with that next week. I have to standup JIRA at work About the fall off on the dev list. Two factors. - The group has a lot of energy and there was a huge amount of discussion at the start. - This was followed by a Logo contest with over 50 entries and two rounds of voting on the flex-dev list. This was significant volume. Sounds like the contest was a great success. As I noted, the traffic is still high for a podling, there just happened to be a relative drop from the beginning. I don't think anyone should be worried about activity in a podling with ~250 e-mails in the first 10 days of the month I'll certainly try to suggest another report author when report time truly arrives. Having more people with experience in writing board reports is definitely useful, but I don't see particular problems with this report. It's informative and highlights problems that the podling is facing. What's more to ask? I agree with Greg that we should remove this report. There's no harm in extra out-of-cycle reports, so let's keep it. I see, no problem, other than no signatures. Regards, Dave [1] http://markmail.org/message/q3aagw5jhqz5m6b5 BR, Jukka Zitting - 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: Flex Status
-Original Message- From: Greg Reddin [mailto:gred...@gmail.com] Sent: Thursday, May 10, 2012 12:29 PM To: general@incubator.apache.org Subject: Re: Flex Status On Thu, May 10, 2012 at 10:37 AM, Dave Fisher dave2w...@comcast.net wrote: Some day I'll write about the differences between AOO and Flex as large incubating projects, the contrasts are amazing. That would be very interesting. +1 Greg - 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
Ambari Status
In reviewing the Amabari report, I have a couple of notes/concerns: * The community IMHO is in serious risk of failure to launch. A recent code change has sparked project interest, but list activity was non existent after January. *As Ambari went nearly 2 months without a single e-mail to the list, I think an issue for graduation should be added that the community must demonstrate viability for X more reporting periods (where x IMO is 2). * The list of completed JIRA issues is not very telling of anything and might give the impression that the community is more vibrant than it is Also, I noticed that ddas signed off on it as a mentor. I don't see him listed as an Apache member or IPMC member. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Flex Status
I have reviewed the flex report and community and didn't find any major issues. The small things I found are: 1) The report appears to be written by a single person 2) This person appears to be disheartened a bit (We expect the initial RC's to be rejected as we finalize licensing and other policy issues). I don't think the negativity belongs in the report. This isn't a big problem unless it is representative of the general community's state of mind, which I saw no evidence of in my short scan of the mail list. 3) No mentors have signed off on the report 4) The mail list has been decreasing steadily since the beginning, but still well within normal levels IMO - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [VOTE] retire zeta components from incubation
+1 -Original Message- From: Julien Vermillard [mailto:jvermill...@gmail.com] Sent: Thursday, May 03, 2012 4:13 AM To: general@incubator.apache.org Subject: [VOTE] retire zeta components from incubation Hi, As discussed earlier the Zeta components community has voted to retire the project. Following the retirement guide [1], I now call the Incubator PMC to vote on confirming this decision. This vote is open for the next 72 hours. [ ] +1 Retire the Zeta components project [ ] -1 Do not retire the project, because ... [1] http://incubator.apache.org/guides/retirement.html Cheers, Julien -- Forwarded message -- From: Julien Vermillard jvermill...@gmail.com Date: Fri, Apr 20, 2012 at 3:05 PM Subject: [RESULT] Re: [VOTE] retire zeta components from incubation To: zeta-...@incubator.apache.org Cc: general@incubator.apache.org So let's close the vote : +1 binding : grobmeier, beberlei, derick, jpic, oms, rolandb, +0 binding : kore, toby -1 none So let's close this podling. Julien - 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: Mentor cleanup
I do think it is fair to ask mentors to sign into the wiki and put their name against 1-2 reports for projects they are monitoring. +1 Having said that just ask is exactly what Jukka has done here. Lets work together to make it easier for him and his eventual successor. If mentors are actively monitoring/engaging in their podlings, the act of signing a report is a trivial amount of time compared to what has to have been a significant, though necessary, investment on Jukka's part to dig through all the mail lists. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: Shepherds for podling reports
-Original Message- From: Jukka Zitting [mailto:jukka.zitt...@gmail.com] Sent: Wednesday, May 02, 2012 4:54 AM To: general Subject: Shepherds for podling reports Hi, In order to better share the effort of reviewing podling reports and giving constructive feedback where needed, I'd like to propose something like the shepherd model the ASF board is using for project reports. For each report a single shepherd [*] is assigned responsibility for a deeper review of the report and any followups that may be needed. Of course anyone within the IPMC is still welcome to help in the review, and in any case the mentors of a podling should review and sign off on the reports of their podlings. Any volunteer shepherds? Please sign up by adding your name to [1]. +1. Added my name [1] http://wiki.apache.org/incubator/IncubatorShepherds [*] A shepherd watching over a podling... Perhaps someone has a better agricultural term in mind? :-) BR, Jukka Zitting - 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: Shepherds for podling reports
-Original Message- From: Ross Gardler [mailto:rgard...@opendirective.com] Sent: Wednesday, May 02, 2012 7:24 AM To: general@incubator.apache.org Subject: Re: Shepherds for podling reports On 2 May 2012 10:19, Jukka Zitting jukka.zitt...@gmail.com wrote: Hi, On Wed, May 2, 2012 at 10:59 AM, Ross Gardler rgard...@opendirective.com wrote: This is a good idea. I have signed up. Excellent, thanks! I only ask you bear one thing in mind. Some months active people here have lots of their own podlings reporting, which takes quite a bit of time if done diligently. When assigning shepherd each month please bear in mind how many reports they are already signing off on. Good point. How about we start with an approximation that being a mentor of one of the reporting podlings is equivalent to reviewing the reports of three other podlings? We can tweak that down the line based on experience. +1 Looking a little further forward i.e. not suggesting this initial small step should be transformed into a larger step but rather looking at what the next small step might be... I'd like to revisit the idea of grouping projects, e.g. big data, content, semantic, social etc. I imagine that people willing to be Shepherds will also have specific areas of interest. I imagine that shepherds would get more value from their time, and projects would get more cross-community feedback, if try to match shepherds to projects. For example, as a mentor on Wookie I'm interested in the progress of, and potential for collaboration with, Wave. My interest isn't sufficiently strong for me to dive into the dev list, but I'd certainly be willing to help the IPMC and myself by Shepherding that projects reports periodically. The only (small) issue with bucketing podlings is what do we do when one fits in more than one category? I think the idea would be useful in general, so long as we clearly define the rules for cross-cutting projects (ie they exist in both, they choose one, etc) Ross - 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: Shepherds for podling reports
-Original Message- From: Ross Gardler [mailto:rgard...@opendirective.com] Sent: Wednesday, May 02, 2012 8:09 AM To: general@incubator.apache.org Subject: Re: Shepherds for podling reports On 2 May 2012 12:50, Franklin, Matthew B. mfrank...@mitre.org wrote: -Original Message- From: Ross Gardler [mailto:rgard...@opendirective.com] ... Looking a little further forward i.e. not suggesting this initial small step should be transformed into a larger step but rather looking at what the next small step might be... I'd like to revisit the idea of grouping projects, e.g. big data, content, semantic, social etc. I imagine that people willing to be Shepherds will also have specific areas of interest. I imagine that shepherds would get more value from their time, and projects would get more cross-community feedback, if try to match shepherds to projects. For example, as a mentor on Wookie I'm interested in the progress of, and potential for collaboration with, Wave. My interest isn't sufficiently strong for me to dive into the dev list, but I'd certainly be willing to help the IPMC and myself by Shepherding that projects reports periodically. The only (small) issue with bucketing podlings is what do we do when one fits in more than one category? I think the idea would be useful in general, so long as we clearly define the rules for cross-cutting projects (ie they exist in both, they choose one, etc) I don't imagine the bucketing to be enshrined in written process, or even be fixed. More of a convenience. We might do it by, for example, asking Shepherds to identify the projects they would *prefer* to shepherd and why. To continue my example above I might say I have an interest in any social related podling so I would prefer to shepherd Wave which is one such project I'm not a mentor on. Someone else might say I'm really interested in communications protocols and so I will shepherd Wave. Fair enough. I think that makes a lot of sense then. I'm not suggesting formality, just a semblance of structure. I think the best way to proceed is to get out list of shepherds, do a couple of months and then discuss whether this proposed next step will add anything to the process. My goal is to have more cross-community awareness in the incubator projects as I've observed that those projects that have someone actively seeking relationships tend to build critical mass sooner. My proposed approach is only one thing that might help in this regard. Ross Ross - 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: including external code under apache 2.0
-Original Message- From: itamar.synhers...@gmail.com [mailto:itamar.synhers...@gmail.com] On Behalf Of Itamar Syn-Hershko Sent: Saturday, April 28, 2012 5:16 PM To: lucene-net-...@lucene.apache.org Cc: general@incubator.apache.org Subject: Re: including external code under apache 2.0 That mail from Stephan got lost in my inbox, so I never followed up on that. I guess now would be a good chance to tie up all loose ends. How do I do the ICLA? http://www.apache.org/licenses/#clas On Sat, Apr 28, 2012 at 1:11 AM, Troy Howard thowar...@gmail.com wrote: My understanding is that we can include the code as long as we have a ICLA from Itamar. This was discussed at length in January for another contribution that the same contributor wanted to donate. Stephan (Bodewig, our Incubation mentor) laid out what needed to be done really clearly in that context. Here's the link to the final message on that thread where Stephan recaps the relevant points: http://s.apache.org/HZa I don't know if Itamar ever followed up after that and filed a ICLA. If he did, we're good and just need to commit the code.. Otherwise, we'll need him to do the ICLA first. Thanks, Troy On Fri, Apr 27, 2012 at 2:30 PM, Prescott Nasser geobmx...@hotmail.com wrote: Hey all, We've had a community member port a library for Lucene.Net that we'd like to include in our contrib packages. The package is under the apache 2.0 license, so we think we are in the clear to include the code into our contrib package - but we weren't sure and just wanted to double check. The contrib project is located here: https://github.com/synhershko/Spatial4n Thanks for your guidance~Prescott - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: Spam on the Incubator wiki
Can you please grant my account (MattFranklin) edit karma for the wiki? Thanks. -Original Message- From: Gavin McDonald [mailto:ga...@16degrees.com.au] Sent: Thursday, April 12, 2012 1:21 AM To: general@incubator.apache.org Subject: RE: Spam on the Incubator wiki -Original Message- From: Jukka Zitting [mailto:jukka.zitt...@gmail.com] Sent: Wednesday, 11 April 2012 3:05 AM To: general@incubator.apache.org Subject: Re: Spam on the Incubator wiki Hi Gavin, On Tue, Apr 10, 2012 at 11:36 AM, Gavin McDonald ga...@16degrees.com.au wrote: I'm seeing more and more spam appear, just give me the nod and it'll be done. You're the man! With no objections raised, please make the change. Done, let me know if any issues. Someone should change the greeting/edit instructions On the incubator home page to state that a once off email to general@ is enough to be Granted wiki write access. HTH Gav... Thanks! BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.2126 / Virus Database: 2411/4925 - Release Date: 04/09/12 - 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: Spam on the Incubator wiki
-Original Message- From: Jukka Zitting [mailto:jukka.zitt...@gmail.com] Sent: Monday, April 30, 2012 8:20 AM To: general@incubator.apache.org Subject: Re: Spam on the Incubator wiki Hi, On Mon, Apr 30, 2012 at 1:53 PM, Franklin, Matthew B. mfrank...@mitre.org wrote: Can you please grant my account (MattFranklin) edit karma for the wiki? Done. Thanks BR, Jukka Zitting - 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: Adding Syncope IPMC member in the incubator group
-Original Message- From: simone.trip...@gmail.com [mailto:simone.trip...@gmail.com] On Behalf Of Simone Tripodi Sent: Wednesday, April 18, 2012 8:31 AM To: general@incubator.apache.org Subject: Adding Syncope IPMC member in the incubator group Good morning all! :) new guys of Apache Syncope are experiencing issues on deploying SNAPSHOT artifacts because looks like they are not in the incubator group, have a look at INFRA-4675 issue[1]. What is the procedure to request to join? You need to create a ticket for INFRA to manually grant the committers the correct Role [1][2] [1]: https://issues.apache.org/jira/browse/INFRA-2939 [2]: https://issues.apache.org/jira/browse/INFRA-3718 Many thanks in advance, all the best! -Simo [1] https://issues.apache.org/jira/browse/INFRA-4675 http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: Adding Syncope IPMC member in the incubator group
-Original Message- From: simone.trip...@gmail.com [mailto:simone.trip...@gmail.com] On Behalf Of Simone Tripodi Sent: Wednesday, April 18, 2012 8:47 AM To: general@incubator.apache.org Subject: Re: Adding Syncope IPMC member in the incubator group Thanks a lot Matthew, much more than appreciated! No problem. This really should be in the incubator documentation somewhere. I will try to find time this week to get it added. -Matt Have a nice day, all the best, -Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Wed, Apr 18, 2012 at 2:42 PM, Franklin, Matthew B. mfrank...@mitre.org wrote: -Original Message- From: simone.trip...@gmail.com [mailto:simone.trip...@gmail.com] On Behalf Of Simone Tripodi Sent: Wednesday, April 18, 2012 8:31 AM To: general@incubator.apache.org Subject: Adding Syncope IPMC member in the incubator group Good morning all! :) new guys of Apache Syncope are experiencing issues on deploying SNAPSHOT artifacts because looks like they are not in the incubator group, have a look at INFRA-4675 issue[1]. What is the procedure to request to join? You need to create a ticket for INFRA to manually grant the committers the correct Role [1][2] [1]: https://issues.apache.org/jira/browse/INFRA-2939 [2]: https://issues.apache.org/jira/browse/INFRA-3718 Many thanks in advance, all the best! -Simo [1] https://issues.apache.org/jira/browse/INFRA-4675 http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: Problem with Olio Java Setup
Hi Kim,
Glad to see you are reaching out for help, but this list isn't the right place
for this question. Please direct this question to the Olio user list
(olio-u...@incubator.apache.org).
general@ is used for cross-project incubator discussions. The vast majority of
us on general don't have enough working knowledge of Olio to offer much help.
-Matt
-Original Message-
From: Kim Rohner [mailto:rohner@googlemail.com]
Sent: Tuesday, April 17, 2012 10:11 AM
To: general@incubator.apache.org
Subject: Problem with Olio Java Setup
Hi all,
i'm currently installing olio using the olio_java_setup:
https://svn.apache.org/repos/asf/incubator/olio/docs/java_setup.html
I installed within the setup JDK 1.7, ANT 1.8.3, FABAN 1.0.1 and
Glassfish v3.
I finished all previous steps of the setup and i am stuck in step 7 of
Building the Web Application.
When i enter the ant command in the terminal the Build fails with the
following output:
kim@ubuntu:~/olio/webapp/java/trunk/ws/apps/webapp$ ant
Buildfile: /home/kim/olio/webapp/java/trunk/ws/apps/webapp/build.xml
default-ear:
init:
-pre-compile:
bpp-actual-compilation:
[echo] Compiling webapp
[javac]
/home/kim/olio/webapp/java/trunk/ws/bp-project/command-line-ant-
tasks.xml:96:
warning: 'includeantruntime' was not set, defaulting to
build.sysclasspath=last; set to false for repeatable builds
[javac] Compiling 9 source files to
/home/kim/olio/webapp/java/trunk/ws/apps/webapp/build/classes
BUILD FAILED
/home/kim/olio/webapp/java/trunk/ws/bp-project/command-line-ant-
tasks.xml:96:
/home/kim/olio/webapp/java/trunk/ws/apps/webapp/${javaee.lib.dir} does
not exist.
Can somebody please tell me where my mistake is and how i can fix it?
Kind regards,
Kim
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release ManifoldCF 0.5-incubating, RC6
On 4/12/12 3:35 PM, Karl Wright daddy...@gmail.com wrote: I should also mention that Jukka voted +1 during the community voting on this RC, so his vote should be binding here as well. For future reference, it is a best practice to include a link to the PPMC VOTE thread [1]. It has also been suggested that the RM include in the IPMC VOTE thread any IPMC members who have voted +1 on the PPMC VOTE thread. [1] : http://incubator.apache.org/guides/releasemanagement.html#best-practice-inc ubator-release-vote Karl On Thu, Apr 12, 2012 at 5:45 AM, Tommaso Teofili tommaso.teof...@gmail.com wrote: +1 (binding), Tommaso 2012/4/12 Karl Wright daddy...@gmail.com +1 from me (binding). Karl On Wed, Apr 11, 2012 at 11:16 PM, Shinichiro Abe shinichiro.ab...@gmail.com wrote: Hi, Please vote on whether or not to release ManifoldCF 0.5-incubating, RC6. This RC has passed our podling vote and awaits your inspection. You can download the release candidate from http://people.apache.org/~shinichiro/apache-manifoldcf-0.5-incubating-RC 6/ and there is also a tag in svn under https://svn.apache.org/repos/asf/incubator/lcf/tags/release-0.5-incubati ng-RC6/ . It has done improvements for its distribution(bin,lib,src) and build process as to core dependencies. Thank you, Shinichiro Abe - 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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [VOTE] CloudStack for Apache Incubator
+1 (binding) -Original Message- From: Kevin Kluge [mailto:kevin.kl...@citrix.com] Sent: Monday, April 09, 2012 9:32 PM To: general@incubator.apache.org Subject: [VOTE] CloudStack for Apache Incubator Hi All. I'd like to call for a VOTE for CloudStack to enter the Incubator. The proposal is available at [1] and I have also included it below. Please vote with: +1: accept CloudStack into Incubator +0: don't care -1: do not accept CloudStack into Incubator (please explain the objection) The vote is open for at least 72 hours from now (until at least 19:00 US-PST on April 12, 2012). Thanks for the consideration. -kevin [1] http://wiki.apache.org/incubator/CloudStackProposal Abstract CloudStack is an IaaS (Infrastracture as a Service) cloud orchestration platform. Proposal CloudStack provides control plane software that can be used to create an IaaS cloud. It includes an HTTP-based API for user and administrator functions and a web UI for user and administrator access. Administrators can provision physical infrastructure (e.g., servers, network elements, storage) into an instance of CloudStack, while end users can use the CloudStack self-service API and UI for the provisioning and management of virtual machines, virtual disks, and virtual networks. Citrix Systems, Inc. submits this proposal to donate the CloudStack source code, documentation, websites, and trademarks to the Apache Software Foundation (ASF). Background Amazon and other cloud pioneers invented IaaS clouds. Typically these clouds provide virtual machines to end users. CloudStack additionally provides baremetal OS installation to end users via a self-service interface. The management of physical resources to provide the larger goal of cloud service delivery is known as orchestration. IaaS clouds are usually described as elastic -- an elastic service is one that allows its user to rapidly scale up or down their need for resources. A number of open source projects and companies have been created to implement IaaS clouds. Cloud.com started CloudStack in 2008 and released the source under GNU General Public License version 3 (GPL v3) in 2010. Citrix acquired Cloud.com, including CloudStack, in 2011. Citrix re-licensed the CloudStack source under Apache License v2 in April, 2012. Rationale IaaS clouds provide the ability to implement datacenter operations in a programmable fashion. This functionality is tremendously powerful and benefits the community by providing: - More efficient use of datacenter personnel - More efficient use of datacenter hardware - Better responsiveness to user requests - Better uptime/availability through automation While there are several open source IaaS efforts today, none are governed by an independent foundation such as ASF. Vendor influence and/or proprietary implementations may limit the community's ability to choose the hardware and software for use in the datacenter. The community at large will benefit from the ability to enhance the orchestration layer as needed for particular hardware or software support, and to implement algorithms and features that may reduce cost or increase user satisfaction for specific use cases. In this respect the independent nature of the ASF is key to the long term health and success of the project. Initial Goals The CloudStack project has two initial goals after the proposal is accepted and the incubation has begun. The Cloudstack Project's first goal is to ensure that the CloudStack source includes only third party code that is licensed under the Apache License or open source licenses that are approved by the ASF for use in ASF projects. The CloudStack Project has begun the process of removing third party code that is not licensed under an ASF approved license. This is an ongoing process that will continue into the incubation period. Third party code contributed to CloudStack under the CloudStack contribution agreement was assigned to Cloud.com in exchange for distributing CloudStack under GPLv3. The CloudStack project has begun the process of amending the previous CloudStack contribution agreements to obtain consent from existing contributors to change the CloudStack project's license. In the event that an existing contributor does not consent to this change, the project is prepared to remove that contributor's code. Additionally, there are binary dependencies on redistributed libraries that are not provided with an ASF- approved license. Finally, the CloudStack has source files incorporated from third parties that were not provided with an ASF-approved license. We have begun the process of re-writing this software. This is an ongoing process that will extend into the incubation period. These issues are discussed in more detail later in the proposal. Although CloudStack is open source, many design documents and discussions that should have been publicly available and accessible were not publicized. The Project's second goal will be to fix this lack
Re: ERR 0194 ...StreamResult of target/current.ent building incubator.a.o site
On 4/9/12 9:38 PM, David Crossley cross...@apache.org wrote: Shane Curcuru wrote: Tips on building the main incubator.a.o site appreciated. There is some doc at [1] http://incubator.apache.org/guides/website.html but since moving to use the Apache Content Management System (CMS) that page might need some revision. Here is how i do it: * Local checkout of the incubator SVN https://svn.apache.org/repos/asf/incubator/public/trunk For the record, you can also use the web UI accessible by clicking Get Incubator Working Copy on https://cms.apache.org/incubator/ or using the bookmarklet from http://incubator.apache.org/ * Make source changes in the content directory. * Do 'svn diff', review, commit those. * Wait a bit. * Visit https://cms.apache.org/incubator/publish * Review the generated diffs, press the button. * Wait a bit, then see the published site. The notes at [1], and some linked notes, do explain how to review the CMS generated stuff at a staging site. They also show how to build the site locally for review. -David I'm hoping to cleanup some links and better describe the PMC things, along with figuring where to include the branding requirements for graduation. Using two different versions of IBM Java (tried a 1.6 and a 1.7) I get errors trying to process podling.xml: [xslt] : Fatal Error! [ERR 0194] The javax.xml.transform.stream.StreamResult associated with the xsl:result-document with href 'target/current.ent' and base output URI 'file:/C:/a/incubator/public/target/index.tmp' has neither its Writer nor its OutputStream set. [xslt] : Fatal Error! [ERR 0629] A redirect instruction failed to create a file. Cause: [ERR 0629] A redirect instruction failed to create a file. [xslt] Failed to process C:\a\incubator\public\content\podlings.xml Thanks! - Shane C:\a\incubator\publicver Microsoft Windows [Version 6.1.7601] C:\a\incubator\publicjava -version java version 1.7.0 Java(TM) SE Runtime Environment (build pwa6470-20110906_01) IBM J9 VM (build 2.6, JRE 1.7.0 Windows 7 amd64-64 20110810_88604 (JIT enabled, AOT enabled) J9VM - R26_Java726_GA_20110810_1208_B88592 JIT - r11_20110810_20466 GC - R26_Java726_GA_20110810_1208_B88592 J9CL - 20110810_88604) JCL - 20110809_01 based on Oracle 7b147 C:\a\incubator\publicbuild CLASSPATH=.\lib\werken-xpath-0.9.4.jar;.\lib\velocity-tools-generic-1.4. jar;.\l ib\velocity-1.6.1.jar;.\lib\texen-1.0.jar;.\lib\oro-2.0.8.jar;.\lib\log4j -1.2.12 .jar;.\lib\jdom-1.0.jar;.\lib\commons-logging-1.1.jar;.\lib\commons-lang- 2.4.jar ;.\lib\commons-collections-3.2.1.jar;.\lib\avalon-logkit-2.1.jar;.\lib\an tlr-2.7 .5.jar;.\lib\ant-trax-1.7.1.jar;.\lib\ant-launcher-1.7.1.jar;.\lib\ant-ja vamail- 1.7.1.jar;.\lib\ant-1.7.1.jar;.\lib\anakia-1.0.jar; Buildfile: build.xml prepare: prepare-error: _prepare-texen: generate-site-map: [delete] Deleting directory C:\a\incubator\public\target\texen [mkdir] Created dir: C:\a\incubator\public\target\texen [xslt] Transforming into C:\a\incubator\public\target\texen [xslt] Processing C:\a\incubator\public\content\clutch.xml to C:\a\incubato r\public\target\texen\clutch.xml [xslt] Loading stylesheet C:\a\incubator\public\content\stylesheets\sitemap \index.xsl [xslt] Processing C:\a\incubator\public\content\faq.xml to C:\a\incubator\p ublic\target\texen\faq.xml [xslt] Processing C:\a\incubator\public\content\guides\branding.xml to C:\a \incubator\public\target\texen\guides\branding.xml [xslt] Processing C:\a\incubator\public\content\guides\chair.xml to C:\a\in cubator\public\target\texen\guides\chair.xml [xslt] Processing C:\a\incubator\public\content\guides\committer.xml to C:\ a\incubator\public\target\texen\guides\committer.xml [xslt] Processing C:\a\incubator\public\content\guides\community.xml to C:\ a\incubator\public\target\texen\guides\community.xml [xslt] Processing C:\a\incubator\public\content\guides\entry.xml to C:\a\in cubator\public\target\texen\guides\entry.xml [xslt] Processing C:\a\incubator\public\content\guides\graduation.xml to C: \a\incubator\public\target\texen\guides\graduation.xml [xslt] Processing C:\a\incubator\public\content\guides\index.xml to C:\a\in cubator\public\target\texen\guides\index.xml [xslt] Processing C:\a\incubator\public\content\guides\lists.xml to C:\a\in cubator\public\target\texen\guides\lists.xml [xslt] Processing C:\a\incubator\public\content\guides\mentor.xml to C:\a\i ncubator\public\target\texen\guides\mentor.xml [xslt] Processing C:\a\incubator\public\content\guides\names.xml to C:\a\in cubator\public\target\texen\guides\names.xml [xslt] Processing C:\a\incubator\public\content\guides\participation.xml to C:\a\incubator\public\target\texen\guides\participation.xml [xslt] Processing C:\a\incubator\public\content\guides\pmc.xml to C:\a\incu
RE: [IMPC] [VOTE] Graduate Apache Jena as a Top Level Project
+1. Congrats -Original Message- From: Andy Seaborne [mailto:andy.seaborne.apa...@gmail.com] On Behalf Of Andy Seaborne Sent: Monday, April 02, 2012 5:11 AM To: general@incubator.apache.org Subject: [IMPC] [VOTE] Graduate Apache Jena as a Top Level Project This is a call for vote to graduate the Apache Jena podling from Apache Incubator to be a top level project. Jena entered incubation in November 2010. The project has added two new committers and PPMC members, made several releases and has a diverse committer base. The user and development communities are active. The PPMC has indicated [1,2,3] that it believes the project is ready to graduate as a top-level project with the resolution draft below. We ask that the IPMC approve this graduation request though this VOTE. [1] Vote: http://s.apache.org/jena-graduation-vote [2] Result: http://s.apache.org/jena-graduation [3] Request for comments: http://mail-archives.apache.org/mod_mbox/incubator- general/201203.mbox/%3C5C4A33CB-B122-43A8-B082- CBD63B526DE7%40cray.com%3E On behalf of the Apache Jena PPMC, Andy - [ ] +1 Recommend to the ASF Board that Apache Jena Proposal is ready to graduate to being a top level project. [ ] 0 [ ] -1 Do not graduate Apache Jena because ... The vote will be tallied no earlier than: Thursday April 5th, at 23:59 UTC. - X. Establish the Apache Jena 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 related to accessing, storing, querying, publishing and reasoning with semantic web data while adhering to relevant W3C and community standards. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Jena Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Jena Project be and hereby is responsible for the creation and maintenance of software related to accessing, storing, querying, publishing and reasoning with semantic web data while adhering to relevant W3C and community standards; and be it further RESOLVED, that the office of Vice President, Apache Jena 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 Jena Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Jena 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 Jena Project: * Andy Seaborne (andy) * Benson Marguilies (bimargulies) * Chris Dollin (chrisdollin) * Damian Steer (damian) * Dave Reynolds (der) * Ian Dickinson (ijd) * Paolo Castagna (castagna) * Rob Vesse (rvesse) * Stephen Allen (sallen) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Andy Seaborne be appointed to the office of Vice President, Apache Jena, 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 Jena 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 Jena Project; and be it further RESOLVED, that the Apache Jena Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Jena podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Jena podling encumbered upon the Apache Incubator Project are hereafter discharged. - 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: Question about downloading binaries
-Original Message- From: Karl Wright [mailto:daddy...@gmail.com] Sent: Tuesday, April 03, 2012 1:24 PM To: general@incubator.apache.org Subject: Re: Question about downloading binaries Also, making sure the other comments on NOTICEs are addressed as well. I have gotten extremely confusing advice in this area in the past, and the available documentation does not help. I believe I am adhering to Roy's principles, but before we spin another release candidate, I'd like it very much if someone with a (hopefully accurate) idea of how things are supposed to work reviewed our license and notice files. You can find them here: https://svn.apache.org/repos/asf/incubator/lcf/trunk/LICENSE.txt https://svn.apache.org/repos/asf/incubator/lcf/trunk/NOTICE.txt Just looking quickly, the LICENSE file contains a lot of licenses for the jars you were distributing. For the source release, the ONLY LN attributions needed are the ones for code that you are including in your source. If, like many projects, you have no 3rd party source inclusion, the LICENSE file should only contain ASL 2.0 and the NOTICE should have the standard developed at apache note. For the binary releases, we have been adding entries for any jars we include, as you have done. There are a couple of tweaks I would suggest, I propose that you get an agreeable source LN first as I think there is (yet again) a wider discussion to be had regarding convenience binaries... Thanks! Karl On Tue, Apr 3, 2012 at 1:11 PM, Matt Hogstrom m...@hogstrom.org wrote: Hope that helps... The question is, will Roy (or anyone else) be unwilling to vote for the first option? Having been one of the people that commented and started the thread, I feel like I was wearing loose clothing while operating machinery, per Roy's guidance on the source being the thing that is voted on and the other binaries are merely convenience items, I would support the first option. Also, making sure the other comments on NOTICEs are addressed as well. Unfortunate that you god dog piled on but hopefully we're all better prepared going forward. Matt Hogstrom m...@hogstrom.org A Day Without Nuclear Fusion Is a Day Without Sunshine On Apr 3, 2012, at 11:04 AM, Karl Wright wrote: - 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: [VOTE][IPMC] Graduate RAT as Apache Creadur Project
+1 (binding) -Original Message- From: Robert Burrell Donkin [mailto:rdon...@apache.org] Sent: Sunday, March 11, 2012 3:42 PM To: general@incubator.apache.org Cc: rat-...@incubator.apache.org Subject: [VOTE][IPMC] Graduate RAT as Apache Creadur Project As recommended[1]: * the Rat community has indicated that its readiness[2] to graduate as the Apache Creadur Project * the proposed charter has been reviewed[3] The penultimate stage is this VOTE by the incubator community. The VOTE is open to all but only IPMC votes are binding. I will tally the results no earlier than noon UTC on Thursday, March 22, 2012[4]. Robert [1] http://incubator.apache.org/guides/graduation.html#toplevel [2] http://mail-archives.apache.org/mod_mbox/incubator- general/201203.mbox/%3C4F53968D.7070908%40apache.org%3E [3] http://mail-archives.apache.org/mod_mbox/incubator- general/201203.mbox/%3C4F53B9FB.4030404%40apache.org%3E [4] http://www.worldtimeserver.com/convert_time_in_UTC.aspx?y=2012mo= 3d=22h=12mn=0 -8--- [ ] +1 Recommend The Apache Creadur Proposal To The Board (below) [ ] +0 [ ] -0 [ ] -1 Do not graduate Rat podling -- -8-- 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 related to the comprehension and auditing of software distributions for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Creadur Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Creadur Project be and hereby is responsible for the creation and maintenance of open-source software related to the comprehension and auditing of software distributions; and be it further RESOLVED, that the office of Vice President, Apache Creadur 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 Creadur Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Creadur 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 Creadur Project: * Stefan Bodewig bode...@apache.org * Brian E Fox bri...@apache.org * David Crossley cross...@apache.org * David Blevins dblev...@apache.org * Dennis Lundberg denn...@apache.org * Gavin McDonald gmcdon...@apache.org * Jochen Wiedmann joc...@apache.org * Niall Pemberton nia...@apache.org * Robert Burrell Donkin rdon...@apache.org * Ross Duncan Gardler rgard...@apache.org * Sebastian Bazley s...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Robert Burrell Donkin be appointed to the office of Vice President, Apache Creadur, 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 Creadur 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 Creadur Project; and be it further RESOLVED, that the Apache Creadur Project be and hereby is tasked with the migration and rationalization of the Apache Incubator RAT podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator RAT podling encumbered upon the Apache Incubator Project are hereafter discharged. - 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] Release Apache Rave 0.9-incubating
The voting period is now closed. Result Summary for this List: Binding IPMC Member Votes +1 [0] 0 [0] -1[0] With the three IPMC member votes on the dev list, the vote succeeds. IPMC member voting record: * Ate Douma: +1 * Matt Franklin: +1 * Ross Gardler: +1 *Denotes an IPMC member vote cast on the rave-dev list On 3/10/12 7:49 PM, Franklin, Matthew B. mfrank...@mitre.org wrote: This is the eighth incubator release for Apache Rave, with the artifacts being versioned as 0.9-incubating. We are requesting a lazy consensus vote, as we have already received 3 binding IPMC +1 votes during the release voting on rave-dev - VOTE: http://markmail.org/message/3ipmolpl66j3dc34 RESULT: http://markmail.org/message/7udo2duh75gjylle Release notes: http://svn.apache.org/repos/asf/incubator/rave/tags/0.9-incubating/CHANGEL O G SVN source tag (r1296695): https://svn.apache.org/repos/asf/incubator/rave/tags/0.9-incubating/ Maven staging repo: https://repository.apache.org/content/repositories/orgapacherave-049/ Source release: https://repository.apache.org/content/repositories/orgapacherave-049/org/a p ache/rave/rave-project/0.9-incubating/rave-project-0.9-incubating-source-r e lease.zip Binary releases http://people.apache.org/builds/incubator/rave/0.9-incubating/apache-rave- 0 .9-incubating-bin.tar.gz http://people.apache.org/builds/incubator/rave/0.9-incubating/apache-rave- 0 .9-incubating-bin.zip PGP release keys: https://svn.apache.org/repos/asf/incubator/rave/KEYS Lazy consensus, vote open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) - 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
[VOTE] Release Apache Rave 0.9-incubating
This is the eighth incubator release for Apache Rave, with the artifacts being versioned as 0.9-incubating. We are requesting a lazy consensus vote, as we have already received 3 binding IPMC +1 votes during the release voting on rave-dev - VOTE: http://markmail.org/message/3ipmolpl66j3dc34 RESULT: http://markmail.org/message/7udo2duh75gjylle Release notes: http://svn.apache.org/repos/asf/incubator/rave/tags/0.9-incubating/CHANGELO G SVN source tag (r1296695): https://svn.apache.org/repos/asf/incubator/rave/tags/0.9-incubating/ Maven staging repo: https://repository.apache.org/content/repositories/orgapacherave-049/ Source release: https://repository.apache.org/content/repositories/orgapacherave-049/org/ap ache/rave/rave-project/0.9-incubating/rave-project-0.9-incubating-source-re lease.zip Binary releases http://people.apache.org/builds/incubator/rave/0.9-incubating/apache-rave-0 .9-incubating-bin.tar.gz http://people.apache.org/builds/incubator/rave/0.9-incubating/apache-rave-0 .9-incubating-bin.zip PGP release keys: https://svn.apache.org/repos/asf/incubator/rave/KEYS Lazy consensus, vote open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [VOTE] RAT Ready To Graduate As Apache Creadur Top Level Project
+1 -Original Message- From: Robert Burrell Donkin [mailto:rdon...@apache.org] Sent: Sunday, February 26, 2012 11:03 AM To: rat-...@incubator.apache.org Cc: general@incubator.apache.org Subject: [VOTE] RAT Ready To Graduate As Apache Creadur Top Level Project The graduation guide[1] recommends that the Rat community demonstrates it's willingness to govern itself through a free VOTE before asking the IPMC to approve graduation. So, here it is :-) See [2] for a draft of the charter, excluding the list of initial committers. Unless anyone jumps into this thread, I'll assume that the current list of committers would be fine. Please read, review and jump in - but this is a vote on the principle of graduating now. This VOTE is open to all, and I'll tally this no early than Wednesday, 29 Feb 2012 17:00 UTC. Robert --8--- [ ] +1 the RAT community feels ready to graduate as Apache Creadur [ ] +0 [ ] -0 [ ] -1 Do not graduate RAT at this time --- [1] http://incubator.apache.org/guides/graduation.html#toplevel [2] Suggested Draft Charter: 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 related to the comprehension and auditing of software distributions for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Creadur Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Creadur Project be and hereby is responsible for the creation and maintenance of open-source software related to the comprehension and auditing of software distributions for distribution at no charge to the public RESOLVED, that the office of Vice President, Apache Creadur 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 Creadur Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Creadur 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 Creadur Project: ... NOW, THEREFORE, BE IT FURTHER RESOLVED, that Robert Burrell Donkin be appointed to the office of Vice President, Apache Creadur, 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 Creadur 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 Creadur Project; and be it further RESOLVED, that the Apache Creadur Project be and hereby is tasked with the migration and rationalization of the Apache Incubator RAT podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator RAT podling encumbered upon the Apache Incubator Project are hereafter discharged. - 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: [VOTE] Release Apache Hama 0.4-incubating RC6
For the packaging, a clean source package and a separate binary release is preferred [1]. This isn't the blocker in my opinion, but something that you should look at. [1]: http://incubator.apache.org/guides/releasemanagement.html#best-practice-typ es On 2/25/12 2:52 AM, Edward J. Yoon edwardy...@apache.org wrote: The LICENSE file in the binary distribution needs to include 3rd party licenses included in the libs that are being re-distributed as part of your release. Your binary release artifacts include ant 1.7 (and potentially others) that has source covered by 3rd party licenses which I don't see in your LICENSE file. The ant is released under the Apache Software License and LICENSE.txt file contains the Apache license v2.0. http://svn.apache.org/repos/asf/incubator/hama/tags/0.4-RC6/LICENSE.txt I don't see any missed 3rd party licenses. Could you please check it again? Ant itself includes code under a separate license. Since your binary release includes the Ant jar, you are redistributing that code and need to include its license. http://svn.apache.org/repos/asf/ant/core/tags/ANT_171/LICENSE And, the distributions contains both source code and compiled jar files. Anyways, if we have to go to a RC7, let's merge the new jiras from trunk to 0.4.0, compression and stuff can be great improvement. I don't think we have to create new one. Moreover, new stuffs are not tested enough yet. On Sat, Feb 25, 2012 at 3:44 PM, Thomas Jungblut thomas.jungb...@googlemail.com wrote: Hmm- I always thought it is Apache Ant and therefore Apache 2.0 license. If we have to add all transitive licenses we are going to release until the overnext year. What is wrong packaging the source within a binary distribution? Anyways, if we have to go to a RC7, let's merge the new jiras from trunk to 0.4.0, compression and stuff can be great improvement. 2012/2/25 Franklin, Matthew B. mfrank...@mitre.org -1 at the moment due to source distribution and license concerns noted below. On 2/20/12 8:54 AM, Edward J. Yoon edwardy...@apache.org wrote: Hi, I've create RC6 for the Apache Hama 0.4-incubating release. This fixes the license header issue and adds rat-plugin. Signing KEYS: http://svn.apache.org/repos/asf/incubator/hama/trunk/src/site/resources/ fi les/KEYS Artifacts: http://people.apache.org/~edwardyoon/dist/0.4-RC6/ Do you have a source artifact that is a simple archive of the SVN? Also, you can stage your artifacts at http://people.apache.org/builds/incubator/ rather than your own public html folder, but this is not required. Tag: http://svn.apache.org/repos/asf/incubator/hama/tags/0.4-RC6/ NOTICE.txt: http://svn.apache.org/repos/asf/incubator/hama/tags/0.4-RC6/NOTICE.txt LICENSE.txt: http://svn.apache.org/repos/asf/incubator/hama/tags/0.4-RC6/LICENSE.txt The LICENSE file in the binary distribution needs to include 3rd party licenses included in the libs that are being re-distributed as part of your release. Your binary release artifacts include ant 1.7 (and potentially others) that has source covered by 3rd party licenses which I don't see in your LICENSE file. Staging website: http://people.apache.org/~edwardyoon/site/ You can run the mvn apache-rat:check command to check for license headers. I tested this RC6 builds, single mode, and distributed mode on my 16 nodes cluster and 5 VMs with EC2. Please retry, check signatures, licenses, and vote! I hope this will be a final, and +1. Thanks. -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thomas Jungblut Berlin thomas.jungb...@gmail.com -- Best Regards, Edward J. Yoon @eddieyoon - 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: [VOTE] Release Apache Hama 0.4-incubating RC6
On 2/25/12 8:12 PM, Edward J. Yoon edwardy...@apache.org wrote: Thanks. Actually we're trying to separate them but there's some issues related with packaging web resources e.g., https://issues.apache.org/jira/browse/HAMA-494 If it's not a blocker, I'd like to fix this issue in the next release. As I understand it the only requirement is that you have a source release; which your combined one does. As I said it isn't optimal. The blocker as I see it is that the LICENSE file is incomplete as I mentioned earlier. On Sat, Feb 25, 2012 at 9:22 PM, Franklin, Matthew B. mfrank...@mitre.org wrote: For the packaging, a clean source package and a separate binary release is preferred [1]. This isn't the blocker in my opinion, but something that you should look at. [1]: http://incubator.apache.org/guides/releasemanagement.html#best-practice-t yp es On 2/25/12 2:52 AM, Edward J. Yoon edwardy...@apache.org wrote: The LICENSE file in the binary distribution needs to include 3rd party licenses included in the libs that are being re-distributed as part of your release. Your binary release artifacts include ant 1.7 (and potentially others) that has source covered by 3rd party licenses which I don't see in your LICENSE file. The ant is released under the Apache Software License and LICENSE.txt file contains the Apache license v2.0. http://svn.apache.org/repos/asf/incubator/hama/tags/0.4-RC6/LICENSE.txt I don't see any missed 3rd party licenses. Could you please check it again? Ant itself includes code under a separate license. Since your binary release includes the Ant jar, you are redistributing that code and need to include its license. http://svn.apache.org/repos/asf/ant/core/tags/ANT_171/LICENSE And, the distributions contains both source code and compiled jar files. Anyways, if we have to go to a RC7, let's merge the new jiras from trunk to 0.4.0, compression and stuff can be great improvement. I don't think we have to create new one. Moreover, new stuffs are not tested enough yet. On Sat, Feb 25, 2012 at 3:44 PM, Thomas Jungblut thomas.jungb...@googlemail.com wrote: Hmm- I always thought it is Apache Ant and therefore Apache 2.0 license. If we have to add all transitive licenses we are going to release until the overnext year. What is wrong packaging the source within a binary distribution? Anyways, if we have to go to a RC7, let's merge the new jiras from trunk to 0.4.0, compression and stuff can be great improvement. 2012/2/25 Franklin, Matthew B. mfrank...@mitre.org -1 at the moment due to source distribution and license concerns noted below. On 2/20/12 8:54 AM, Edward J. Yoon edwardy...@apache.org wrote: Hi, I've create RC6 for the Apache Hama 0.4-incubating release. This fixes the license header issue and adds rat-plugin. Signing KEYS: http://svn.apache.org/repos/asf/incubator/hama/trunk/src/site/resource s/ fi les/KEYS Artifacts: http://people.apache.org/~edwardyoon/dist/0.4-RC6/ Do you have a source artifact that is a simple archive of the SVN? Also, you can stage your artifacts at http://people.apache.org/builds/incubator/ rather than your own public html folder, but this is not required. Tag: http://svn.apache.org/repos/asf/incubator/hama/tags/0.4-RC6/ NOTICE.txt: http://svn.apache.org/repos/asf/incubator/hama/tags/0.4-RC6/NOTICE.tx t LICENSE.txt: http://svn.apache.org/repos/asf/incubator/hama/tags/0.4-RC6/LICENSE.t xt The LICENSE file in the binary distribution needs to include 3rd party licenses included in the libs that are being re-distributed as part of your release. Your binary release artifacts include ant 1.7 (and potentially others) that has source covered by 3rd party licenses which I don't see in your LICENSE file. Staging website: http://people.apache.org/~edwardyoon/site/ You can run the mvn apache-rat:check command to check for license headers. I tested this RC6 builds, single mode, and distributed mode on my 16 nodes cluster and 5 VMs with EC2. Please retry, check signatures, licenses, and vote! I hope this will be a final, and +1. Thanks. -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thomas Jungblut Berlin thomas.jungb...@gmail.com -- Best Regards, Edward J. Yoon @eddieyoon - 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, Edward J. Yoon @eddieyoon
Re: [VOTE] Release Apache Hama 0.4-incubating RC6
-1 at the moment due to source distribution and license concerns noted below. On 2/20/12 8:54 AM, Edward J. Yoon edwardy...@apache.org wrote: Hi, I've create RC6 for the Apache Hama 0.4-incubating release. This fixes the license header issue and adds rat-plugin. Signing KEYS: http://svn.apache.org/repos/asf/incubator/hama/trunk/src/site/resources/fi les/KEYS Artifacts: http://people.apache.org/~edwardyoon/dist/0.4-RC6/ Do you have a source artifact that is a simple archive of the SVN? Also, you can stage your artifacts at http://people.apache.org/builds/incubator/ rather than your own public html folder, but this is not required. Tag: http://svn.apache.org/repos/asf/incubator/hama/tags/0.4-RC6/ NOTICE.txt: http://svn.apache.org/repos/asf/incubator/hama/tags/0.4-RC6/NOTICE.txt LICENSE.txt: http://svn.apache.org/repos/asf/incubator/hama/tags/0.4-RC6/LICENSE.txt The LICENSE file in the binary distribution needs to include 3rd party licenses included in the libs that are being re-distributed as part of your release. Your binary release artifacts include ant 1.7 (and potentially others) that has source covered by 3rd party licenses which I don't see in your LICENSE file. Staging website: http://people.apache.org/~edwardyoon/site/ You can run the mvn apache-rat:check command to check for license headers. I tested this RC6 builds, single mode, and distributed mode on my 16 nodes cluster and 5 VMs with EC2. Please retry, check signatures, licenses, and vote! I hope this will be a final, and +1. Thanks. -- Best Regards, Edward J. Yoon @eddieyoon - 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
[VOTE] Release Apache Rave 0.8-incubating
We still need one more IPMC member vote for the release. Does anyone have time to take a look? Thanks in advance, -Matt On 2/12/12 9:29 PM, Franklin, Matthew B. mfrank...@mitre.org wrote: This is the seventh incubator release for Apache Rave, with the artifacts being versioned as 0.8-incubating. We are requesting at least one additional IPMC member vote, as we have received 2 binding IPMC +1 votes during the release voting on rave-dev - VOTE: http://s.apache.org/U8G RESULT: http://s.apache.org/Fcv IPMC member votes from the rave-dev list: Ate Douma: +1 Ross Gardler: +1 Release notes: http://svn.apache.org/repos/asf/incubator/rave/tags/0.8-incubating/CHANGEL O G SVN source tag (r1163402): https://svn.apache.org/repos/asf/incubator/rave/rave-master-pom/tags/0.8-i n cubating/ SVN source tag (r1163411): https://svn.apache.org/repos/asf/incubator/rave/tags/0.8-incubating/ Maven staging repos: https://repository.apache.org/content/repositories/orgapacherave-195/ Source releases: https://repository.apache.org/content/repositories/orgapacherave-195/org/a p ache/rave/rave-master/0.8-incubating/rave-master-0.8-incubating-source-rel e ase.zip https://repository.apache.org/content/repositories/orgapacherave-195/org/a p ache/rave/rave-project/0.8-incubating/rave-project-0.8-incubating-source-r e lease.zip Binary releases http://people.apache.org/builds/incubator/rave/0.8-incubating/apache-rave- 0 .8-incubating-bin.tar.gz http://people.apache.org/builds/incubator/rave/0.8-incubating/apache-rave- 0 .8-incubating-bin.zip PGP release keys: https://svn.apache.org/repos/asf/incubator/rave/KEYS Vote open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) - 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: [VOTE] Release Apache Rave 0.8-incubating
We only distribute that jar as part of the binary release and the LICENCE NOTICE files have the appropriate attribution and license. -Matt -Original Message- From: Karl Wright [mailto:daddy...@gmail.com] Sent: Thursday, February 16, 2012 10:05 AM To: general@incubator.apache.org Subject: Re: [VOTE] Release Apache Rave 0.8-incubating What is the license on ecj-3.7.jar (Eclipse JDT Java compiler)? If you are going to redistribute it you should provide that info somewhere unless it's Apache licensed. Thanks, Karl On Thu, Feb 16, 2012 at 10:00 AM, Karl Wright daddy...@gmail.com wrote: I'll have a look at it. Stay tuned... Karl On Thu, Feb 16, 2012 at 9:20 AM, Franklin, Matthew B. mfrank...@mitre.org wrote: We still need one more IPMC member vote for the release. Does anyone have time to take a look? Thanks in advance, -Matt On 2/12/12 9:29 PM, Franklin, Matthew B. mfrank...@mitre.org wrote: This is the seventh incubator release for Apache Rave, with the artifacts being versioned as 0.8-incubating. We are requesting at least one additional IPMC member vote, as we have received 2 binding IPMC +1 votes during the release voting on rave-dev - VOTE: http://s.apache.org/U8G RESULT: http://s.apache.org/Fcv IPMC member votes from the rave-dev list: Ate Douma: +1 Ross Gardler: +1 Release notes: http://svn.apache.org/repos/asf/incubator/rave/tags/0.8- incubating/CHANGEL O G SVN source tag (r1163402): https://svn.apache.org/repos/asf/incubator/rave/rave-master- pom/tags/0.8-i n cubating/ SVN source tag (r1163411): https://svn.apache.org/repos/asf/incubator/rave/tags/0.8-incubating/ Maven staging repos: https://repository.apache.org/content/repositories/orgapacherave-195/ Source releases: https://repository.apache.org/content/repositories/orgapacherave- 195/org/a p ache/rave/rave-master/0.8-incubating/rave-master-0.8-incubating- source-rel e ase.zip https://repository.apache.org/content/repositories/orgapacherave- 195/org/a p ache/rave/rave-project/0.8-incubating/rave-project-0.8-incubating- source-r e lease.zip Binary releases http://people.apache.org/builds/incubator/rave/0.8-incubating/apache- rave- 0 .8-incubating-bin.tar.gz http://people.apache.org/builds/incubator/rave/0.8-incubating/apache- rave- 0 .8-incubating-bin.zip PGP release keys: https://svn.apache.org/repos/asf/incubator/rave/KEYS Vote open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) - 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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [VOTE] Release Apache Rave 0.8-incubating
-Original Message- From: Karl Wright [mailto:daddy...@gmail.com] Sent: Thursday, February 16, 2012 10:32 AM To: general@incubator.apache.org Subject: Re: [VOTE] Release Apache Rave 0.8-incubating Thanks - I did not realize that the source LICENSE and the binary LICENSE were different. ;-) +1 from me (binding) Thanks Karl! Karl On Thu, Feb 16, 2012 at 10:17 AM, Ate Douma a...@douma.nu wrote: On 02/16/2012 04:05 PM, Karl Wright wrote: What is the license on ecj-3.7.jar (Eclipse JDT Java compiler)? If you are going to redistribute it you should provide that info somewhere unless it's Apache licensed. The ecj is EPL 1.0 license, and explicitly mentioned and covered in the root LICENSE file of the binary distribution. Thanks, Karl On Thu, Feb 16, 2012 at 10:00 AM, Karl Wrightdaddy...@gmail.com wrote: I'll have a look at it. Stay tuned... Karl On Thu, Feb 16, 2012 at 9:20 AM, Franklin, Matthew B. mfrank...@mitre.org wrote: We still need one more IPMC member vote for the release. Does anyone have time to take a look? Thanks in advance, -Matt On 2/12/12 9:29 PM, Franklin, Matthew B.mfrank...@mitre.org wrote: This is the seventh incubator release for Apache Rave, with the artifacts being versioned as 0.8-incubating. We are requesting at least one additional IPMC member vote, as we have received 2 binding IPMC +1 votes during the release voting on rave- dev - VOTE: http://s.apache.org/U8G RESULT: http://s.apache.org/Fcv IPMC member votes from the rave-dev list: Ate Douma: +1 Ross Gardler: +1 Release notes: http://svn.apache.org/repos/asf/incubator/rave/tags/0.8- incubating/CHANGEL O G SVN source tag (r1163402): https://svn.apache.org/repos/asf/incubator/rave/rave-master- pom/tags/0.8-i n cubating/ SVN source tag (r1163411): https://svn.apache.org/repos/asf/incubator/rave/tags/0.8-incubating/ Maven staging repos: https://repository.apache.org/content/repositories/orgapacherave- 195/ Source releases: https://repository.apache.org/content/repositories/orgapacherave- 195/org/a p ache/rave/rave-master/0.8-incubating/rave-master-0.8-incubating- source-rel e ase.zip https://repository.apache.org/content/repositories/orgapacherave- 195/org/a p ache/rave/rave-project/0.8-incubating/rave-project-0.8-incubating- source-r e lease.zip Binary releases http://people.apache.org/builds/incubator/rave/0.8- incubating/apache-rave- 0 .8-incubating-bin.tar.gz http://people.apache.org/builds/incubator/rave/0.8- incubating/apache-rave- 0 .8-incubating-bin.zip PGP release keys: https://svn.apache.org/repos/asf/incubator/rave/KEYS Vote open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) - 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 - 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] Release Apache Rave 0.8-incubating
The voting period is now closed. Thanks to everyone who took the time to review the release. Result Summary for this List: Binding IPMC Member Votes +1 [1] 0[0] -1[0] With the vote from this list and the two IPMC member votes from mentors on the dev list, the vote succeeds. IPMC member voting record: * Ate Douma: +1 * Ross Gardler: +1 Karl Wright: +1 *Denotes an IPMC member vote cast on the rave-dev list -Original Message- From: Franklin, Matthew B. [mailto:mfrank...@mitre.org] Sent: Sunday, February 12, 2012 9:30 PM To: general@incubator.apache.org Subject: [VOTE] Release Apache Rave 0.8-incubating This is the seventh incubator release for Apache Rave, with the artifacts being versioned as 0.8-incubating. We are requesting at least one additional IPMC member vote, as we have received 2 binding IPMC +1 votes during the release voting on rave-dev - VOTE: http://s.apache.org/U8G RESULT: http://s.apache.org/Fcv IPMC member votes from the rave-dev list: Ate Douma: +1 Ross Gardler: +1 Release notes: http://svn.apache.org/repos/asf/incubator/rave/tags/0.8- incubating/CHANGELO G SVN source tag (r1163402): https://svn.apache.org/repos/asf/incubator/rave/rave-master- pom/tags/0.8-in cubating/ SVN source tag (r1163411): https://svn.apache.org/repos/asf/incubator/rave/tags/0.8-incubating/ Maven staging repos: https://repository.apache.org/content/repositories/orgapacherave-195/ Source releases: https://repository.apache.org/content/repositories/orgapacherave- 195/org/ap ache/rave/rave-master/0.8-incubating/rave-master-0.8-incubating-source- rele ase.zip https://repository.apache.org/content/repositories/orgapacherave- 195/org/ap ache/rave/rave-project/0.8-incubating/rave-project-0.8-incubating-source-re lease.zip Binary releases http://people.apache.org/builds/incubator/rave/0.8-incubating/apache-rave- 0 .8-incubating-bin.tar.gz http://people.apache.org/builds/incubator/rave/0.8-incubating/apache-rave- 0 .8-incubating-bin.zip PGP release keys: https://svn.apache.org/repos/asf/incubator/rave/KEYS Vote open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) - 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
[VOTE] Release Apache Rave 0.8-incubating
This is the seventh incubator release for Apache Rave, with the artifacts being versioned as 0.8-incubating. We are requesting at least one additional IPMC member vote, as we have received 2 binding IPMC +1 votes during the release voting on rave-dev - VOTE: http://s.apache.org/U8G RESULT: http://s.apache.org/Fcv IPMC member votes from the rave-dev list: Ate Douma: +1 Ross Gardler: +1 Release notes: http://svn.apache.org/repos/asf/incubator/rave/tags/0.8-incubating/CHANGELO G SVN source tag (r1163402): https://svn.apache.org/repos/asf/incubator/rave/rave-master-pom/tags/0.8-in cubating/ SVN source tag (r1163411): https://svn.apache.org/repos/asf/incubator/rave/tags/0.8-incubating/ Maven staging repos: https://repository.apache.org/content/repositories/orgapacherave-195/ Source releases: https://repository.apache.org/content/repositories/orgapacherave-195/org/ap ache/rave/rave-master/0.8-incubating/rave-master-0.8-incubating-source-rele ase.zip https://repository.apache.org/content/repositories/orgapacherave-195/org/ap ache/rave/rave-project/0.8-incubating/rave-project-0.8-incubating-source-re lease.zip Binary releases http://people.apache.org/builds/incubator/rave/0.8-incubating/apache-rave-0 .8-incubating-bin.tar.gz http://people.apache.org/builds/incubator/rave/0.8-incubating/apache-rave-0 .8-incubating-bin.zip PGP release keys: https://svn.apache.org/repos/asf/incubator/rave/KEYS Vote open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [VOTE] Jukka Zitting for IPMC Chair (was Re: NOMINATIONS for Incubator PMC Chair)
+1 -Original Message- From: Mattmann, Chris A (388J) [mailto:chris.a.mattm...@jpl.nasa.gov] Sent: Thursday, February 09, 2012 10:16 AM To: general@incubator.apache.org Subject: [VOTE] Jukka Zitting for IPMC Chair (was Re: NOMINATIONS for Incubator PMC Chair) Hi Folks, OK there has been enough discussion here. It's time to VOTE for a new IPMC chair and it looks like the remaining folks (including me) that were in the running have aligned beyond the following nominee: Jukka Zitting. Suffice to say, he was *my first choice* :) In the interest of moving the current discussion matters forward, please VOTE on this recommendation to the board by the IPMC. I'll leave the VOTE open for at least the next 72 hours: [ ] +1 Recommend Jukka Zitting for the IPMC chair position. [ ] +0 Don't care. [ ] -1 Don't recommend Jukka Zitting for the IPMC chair position because... Note that only VOTEs from the Incubator PMC members are binding, but all are welcome to voice their opinion and it will be recorded in the final tallies. Finally, just to note, these VOTEs on personnel are normally the only thing in Apache that is discussed in private (human/social issues), but in the interest of openness and transparency that has been demonstrated here during these discussions, I will hold this VOTE on the public list. Thanks! Cheers, Chris P.S. Here's my +1. Thanks buddy. On Feb 8, 2012, at 3:11 PM, Benson Margulies wrote: I am happy to step out of the way for Jukka. He was clever enough to stay out of the email s*** storm, and that alone, in my mind, renders him most qualified. On Wed, Feb 8, 2012 at 6:02 PM, Christian Grobmeier grobme...@gmail.com wrote: I already mentioned that I would have nominated you, and so I am delighted to read your message. It will be very difficult to choose between all these strong candidates. Cheers On Wed, Feb 8, 2012 at 11:49 PM, Jukka Zitting jukka.zitt...@gmail.com wrote: Hi, After consideration and some convincing (thanks!), I've decided to throw also my hat into the ring as a candidate to be the next chairman of the IPMC. I believe in that role I could be more effective in focusing more of our collective attention at where I think it would do most good - at the actual podlings we're here to help. That said, the current incubation process clearly has problems and I very much support efforts to improve the way we work (even if the result is to replace the Incubator with something better). However, I'd like to leave the leadership on these efforts to others and, as mentioned elsewhere, rather try to act as a balancing force that helps achieve consensus where possible. Should I be elected, I'd resign as the chairman of the Jackrabbit PMC. In fact I think it's in any case high time for Jackrabbit to be rotating that role. Finally, if elected (and assuming the IPMC still exists), I'd serve for at most two years before calling for a re-election, or possibly much less if I don't find enough free cycles to perform the duty as well as it should. BR, Jukka Zitting +++ +++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ +++ +++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA +++ +++ - 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: Evolution instead of a revolution (Was: Time to vote the chair?)
On 2/4/12 12:28 AM, William A. Rowe Jr. wr...@rowe-clan.net wrote: On 2/3/2012 9:01 PM, Franklin, Matthew B. wrote: Personally, I feel that walking in the door as a full PMC with authority could be just as problematic in the long run as not granting it once the community has demonstrated viability. I think that everyone here agrees. These would not be 'full PMC's... the ASF has a general 'set your own policies, hands off until it's broke' policy towards projects. Nobody is suggesting that an incoming 'project under incubation' would be free of such rules, policies or oversight. Where usual TLP's are free to set the most flexible policies that suit their participants, any project under incubation has a more stringent set of ComDev defined 'best practices' that they must and will follow. If as a full TLP they decide a tweak here or there help their community, it's up to the board to permit that. And generally, the board is flexibly permissive. But with one Champion not of the project itself, but of the ASF, and several additional mentors/overseers/ombudsmen, no incubating effort is going to enjoy the free reign that TLP's have. If only all projects had that sort of supervision, the foundation would be quite secure in knowing that all projects are running as non-factional, non-partisan and non-commercial efforts to create software for the public good. I think the disconnect I was trying to point out is that the proposal itself assumes that the new PMC is fully functional so long as at least 3 ASF members are a part of it and the PMC chair is the champion. Taking Rave as an example, we walked in the door with ~20 non-ASF member PPMC members. Not that it would have happened in our instance, but I can envision a case where a project enters the ASF and isn't forced to understand how things are done here (bad releases, policies, etc). At that point, the board is forced to step in and rectify the situation, when the same outcome could have been avoided by gradually stepping the community up in authority. I have no real opinion as to whether the IPMC stays, or changes structure, or any of the other possibilities discussed; but, I do think there is an important oversight mechanism that can't be lost. If you were to tell me that the incoming PMC would ONLY be comprised of ASF members, and new community members are voted in as they demonstrate an understanding of the Apache Way, then that is a different story. However, that is not what the proposal in the wiki states. Also, if that were to be the case, what happens when the mentors aren't available for release voting (A case that has happened to us 3 times even with 5 ASF member mentors)? Again, I am not saying change isn't important or needed, just that we need to take a breath and look at what we are trying to solve and why. To that end, I intend on putting together a counter proposal and posting it to the wiki that addresses some of the concerns I (and others) have voiced. Good concerns to raise, but i think they are unfounded in light of the current proposal[s]. Bill - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: TL;DR
On 2/4/12 1:11 AM, Scott Wilson scott.bradley.wil...@gmail.com wrote: On 3 Feb 2012, at 23:17, Benson Margulies wrote: A number of people are asking for the incubator PMC to take a deep breath and allow room to digest and contemplate the various issues that have led to a bumper crop of email. These are complex questions, and even if we could avoid intemperate exchanges, there is still going to be a lot to read and think about. +1 I'm a committer on 3 incubator projects, so I have quite a lot of ASF-related email already. I don't understand most of the points being discussed on the general list as I don't really have time to read and make sense of it all The incubator doesn't feel particularly broken and in need of fixing at my level of engagement, so most of the tone of the conversation does little other than give me a nagging worry that I'm missing something important that might affect the projects I work on. I expect many more on this list will just filter these discussions out and trust everyone concerned to do whats sensible. So, slow down please, there's no need to rush. +1 I think quite a few people have suggested we slow down. This is an important step that needs to be thought out fully. One way to make the load lighter is to try to make one decision at a time. Entirely selfishly, I suggest looking at the chair election first. +1 - 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: Evolution instead of a revolution (Was: Time to vote the chair?)
-Original Message- From: Jukka Zitting [mailto:jukka.zitt...@gmail.com] Sent: Friday, February 03, 2012 12:27 PM To: general@incubator.apache.org Subject: Evolution instead of a revolution (Was: Time to vote the chair?) Hi, [Forking a new thread thread to make this easier to track.] On Fri, Feb 3, 2012 at 5:22 PM, Mattmann, Chris A (388J) chris.a.mattm...@jpl.nasa.gov wrote: http://wiki.apache.org/incubator/IncubatorDeconstructionProposal As already mentioned by others, instead of deconstructing everything in one go, wouldn't it make more sense to gradually shift into a new way of doing things? +1 You're proposing that podlings should start as full TLPs (with ASF members on board for mentoring) right from the beginning. Instead of changing the rules on all podlings at the same time, how about we try this out by giving interested podlings (or new proposals) this direct to TLP option? If that works out better than the current Incubator model, we can stop accepting more old-style podlings and just direct them into TLPs right from the beginning. Meanwhile any existing podlings should have a chance to graduate under the existing rules unless they rather choose to use this direct to TLP option. If as a result there's no more podlings in the Incubator, that's IMHO then the right time to shut down the IPMC, not before. And if it turns out that the proposed new model doesn't work as expected, we still have the current processes and structures to fall back to. The current Incubator model certainly has flaws, but it also does a lot of things right. There are good reasons for things like the extra publicity and release constraints placed on podlings, and the proposed model doesn't address how such restrictions would still work without the incubator. I note that many of the original constraints of the Incubator (no releases, etc.) turned out to be unnecessarily strict in practice, so it could well be that everything will work out smoothly also without the extra red tape. But small, reversible steps into such unknown territory are clearly preferable to major leaps of faith. In my year working in an incubator podling, I have come to see that there are a lot of very valuable aspects to the organization; some IMO critical to the success and growth of Apache as a whole. IMHO, any changes made must be cognizant of all aspects of the incubator and not be a reaction to specific pain points. That isn't to say that new things shouldn't be tried and new direction isn't important. Likewise, these revolution style proposals themselves hold value as they explore out-of-the-box approaches that can be incorporated into an evolutionary roadmap or maybe even adopted wholesale if the entire community agrees on the approach. From what I can tell from the 4+ threads, thousands of written words and multitudes of opinions there is a need to address some issues that haven't scaled with the incubator. I think Leo in a different thread attempted to catalog some invariants and desires that highlight these points. I personally favor the evolutionary approach Jukka is suggesting; but I am having a hard time keeping up with where, how and when to participate in these discussions. So that everyone affected by these proposals has the opportunity to engage in the discussion, I recommend that we pull these out of e-mail for a while and ask everyone who has a new plan for the incubator to draft proposals on the wiki as Chris did. At that point, we could have a bake-off discussion where the community has the ability to evaluate and chime in with their concerns/comments/suggestions. Thoughts? BR, Jukka Zitting - 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: Evolution instead of a revolution (Was: Time to vote the chair?)
-Original Message- From: Greg Stein [mailto:gst...@gmail.com] Sent: Friday, February 03, 2012 2:13 PM To: general@incubator.apache.org Subject: Re: Evolution instead of a revolution (Was: Time to vote the chair?) On Fri, Feb 3, 2012 at 14:04, William A. Rowe Jr. wr...@rowe-clan.net wrote: On 2/3/2012 12:51 PM, Franklin, Matthew B. wrote: So that everyone affected by these proposals has the opportunity to engage in the discussion, I recommend that we pull these out of e-mail for a while and ask everyone who has a new plan for the incubator to draft proposals on the wiki as Chris did. At that point, we could have a bake-off discussion where the community has the ability to evaluate and chime in with their concerns/comments/suggestions. Funny you mention it, the Incubator itself was the product of a bake off between two proposed resolutions, still recorded in the board minutes :) http://www.apache.org/foundation/records/minutes/2002/board_minutes_ 2002_10_16.txt Interesting. What are your thoughts on using this approach for our current discussion? As I said, staying abreast of all the threads where these discussions are occurring is difficult at best and I feel like some are treating certain ideas as foregone conclusions because the entire community hasn't been given the time and opportunity to engage without joining the melee. In the end, I imagine we will end up compromising, but I think it is important to take a step back and let others propose a few strategies without it adding to the current frenzy. - 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: Evolution instead of a revolution (Was: Time to vote the chair?)
On 2/3/12 9:28 PM, Mattmann, Chris A (388J) chris.a.mattm...@jpl.nasa.gov wrote: On Feb 3, 2012, at 6:11 PM, Ralph Goers wrote: On Feb 3, 2012, at 6:05 PM, William A. Rowe Jr. wrote: On 2/3/2012 7:40 PM, Ralph Goers wrote: My interest goes beyond any of those topics, though. Incubator is very tedious. Very little is resolved. Deck chairs are shuffled. But at the end of the day, projects don't have ownership of their code, many micro-managers do, we aren't necessarily creating better projects than Chris's proposed structure, and the entire process and participation is simply not enjoyable (except to the sadists or masochists). As Ross said, while the proposal gets rid of the tediousness it also removes much of the oversight and practically all of the help and support. One of my problems is that most of the biggest fans of micromanagement and endless debate here at incubator spend nearly no time looking over the graduated projects throughout the foundation to ensure they are being overseen. If that doesn't happen, the ASF will suffer the death of 1000 fractures. This proposal suggests that every project throughout the ASF needs the support of the ASF's members, that incubating projects simply need to pay extra attentions to each and every one of those requirements at first, in order to prove they are likely to succeed. Then they can move on to operating as a full TLP, going back to the very same resources they enjoyed during their incubation during the rough patches. Your statement above could just as easily be applied to having each podling be a subproject of the IPMC (as it is today), but be given the authority and responsibility they are missing today. You don't need to blow away the IPMC to fix this problem. So, let me get this straight. Make incoming projects have the authority and responsibility that they are missing today? Sounds a ton like my existing proposal. With some kitchen sink (the IPMC) added in. If incoming projects have the authority and responsibility that they lack have today, there is no IPMC. Personally, I feel that walking in the door as a full PMC with authority could be just as problematic in the long run as not granting it once the community has demonstrated viability. Having watched the Rave community (and myself) grow into the Apache way under the incubator, I can tell you that we needed time to figure out who we as a community were before we were ready to have any authority. I will also say that we wouldn't have been able to grow as quickly if there wasn't something like this community to watch and engage with as needed. If every project came as essentially a TLP, we lose some of the teaching advantages that the incubator currently offers. I do agree with some of your concerns and feel that we moved through this early phase quickly and were ready to assume some authority; but, I can't say that we were ready day 0. I think your proposal perfectly targets communities that have demonstrated that they are engaging in the Apache Way; but, if you assume that, then what we need is a restructuring of the incubator, not a dismantling of it. In the end, I think you can meet your goals and maybe even reach some approximation of for proposal, so long as you don't forget the valuable parts of the incubator while planning the future. Cheers, Chris ++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++ - 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: [DISCUSSION] Regular rotation PMC chair
-Original Message- From: Bertrand Delacretaz [mailto:bdelacre...@apache.org] Sent: Monday, January 30, 2012 7:30 AM To: general@incubator.apache.org Subject: Re: [DISCUSSION] Regular rotation PMC chair On Mon, Jan 30, 2012 at 11:46 AM, Ate Douma a...@douma.nu wrote: ...I just realize something not clear from this proposal: are we *only* talking about the Incubator PMC Chair here, or is this a proposal for every PMC Chair? I presumed (and propose) the latter, but maybe that wasn't the intend (yet)... We're talking only about the Incubator PMC chair, no need to generalize this IMO and this list wouldn't be the right place anyway. I can understand why you wouldn't want to generalize this to existing PMCs; but, IMO there is value in graduating podlings following this example. If the IPMC institutes this policy I think it should recommend the model to the podlings undergoing the transition to TLP PMC. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [DISCUSSION] Regular rotation PMC chair
-Original Message- From: Ross Gardler [mailto:rgard...@opendirective.com] Sent: Monday, January 30, 2012 8:21 AM To: general@incubator.apache.org Subject: Re: [DISCUSSION] Regular rotation PMC chair On 30 January 2012 13:00, Franklin, Matthew B. mfrank...@mitre.org wrote: -Original Message- From: Bertrand Delacretaz [mailto:bdelacre...@apache.org] Sent: Monday, January 30, 2012 7:30 AM To: general@incubator.apache.org Subject: Re: [DISCUSSION] Regular rotation PMC chair On Mon, Jan 30, 2012 at 11:46 AM, Ate Douma a...@douma.nu wrote: ...I just realize something not clear from this proposal: are we *only* talking about the Incubator PMC Chair here, or is this a proposal for every PMC Chair? I presumed (and propose) the latter, but maybe that wasn't the intend (yet)... We're talking only about the Incubator PMC chair, no need to generalize this IMO and this list wouldn't be the right place anyway. I can understand why you wouldn't want to generalize this to existing PMCs; but, IMO there is value in graduating podlings following this example. If the IPMC institutes this policy I think it should recommend the model to the podlings undergoing the transition to TLP PMC. We try to avoid one-size-fits-all policies in the ASF, usually for good reason. The IPMC is a special case and, speaking personally, I don't want to set precedents for podlings based on that special case. It really needs to be up to individual communities, with the guidance of their mentors, to decide on their chair appointment policy. I agree that it shouldn't be a requirement, which is why I was thinking recommendation; but, I see your point that the new PMCs need to be self-determining. I was looking more for exposure to the concept for the new PMCs; which, as you noted, is something that the mentors can work to provide. Ross - 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] Release Apache Rave 0.7-incubating
The voting period is now closed. Thanks to everyone who took the time to review the release. Result Summary for this List: Binding IPMC Member Votes +1 [0] 0[0] -1[0] Non-binding Community Votes +1 [1] 0[0] -1[0] With the three IPMC member votes from mentors on the dev list the vote succeeds. IPMC member voting record: * Ate Douma: +1 * Hadrian Zbarcea : +1 * Ross Gardler: +1 Community voting record: Andreas Kuckartz: +1 *Denotes an IPMC member vote cast on the rave-dev list -Original Message- From: Franklin, Matthew B. Sent: Monday, January 23, 2012 10:18 AM To: general@incubator.apache.org Subject: [VOTE] Release Apache Rave 0.7-incubating This is the sixth incubator release for Apache Rave, with the artifacts being versioned as 0.7-incubating. We are requesting a lazy consensus vote, as we have already received 3 binding IPMC +1 votes during the release voting on rave-dev - VOTE: http://s.apache.org/xqH RESULT: http://s.apache.org/rg Release notes: http://svn.apache.org/repos/asf/incubator/rave/tags/0.7- incubating/CHANGELOG SVN source tag (r1227377): https://svn.apache.org/repos/asf/incubator/rave/tags/0.7-incubating/ Maven staging repo: https://repository.apache.org/content/repositories/orgapacherave-015/ Source release: https://repository.apache.org/content/repositories/orgapacherave- 015/org/apache/rave/rave-project/0.7-incubating/rave-project-0.7- incubating-source-release.zip Binary releases http://people.apache.org/builds/incubator/rave/0.7-incubating/apache-rave- 0.7-incubating-bin.tar.gz http://people.apache.org/builds/incubator/rave/0.7-incubating/apache-rave- 0.7-incubating-bin.zip PGP release keys: https://svn.apache.org/repos/asf/incubator/rave/KEYS Lazy consensus, vote open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Release Apache Rave 0.7-incubating
This is the sixth incubator release for Apache Rave, with the artifacts being versioned as 0.7-incubating. We are requesting a lazy consensus vote, as we have already received 3 binding IPMC +1 votes during the release voting on rave-dev - VOTE: http://s.apache.org/xqH RESULT: http://s.apache.org/rg Release notes: http://svn.apache.org/repos/asf/incubator/rave/tags/0.7-incubating/CHANGELOG SVN source tag (r1227377): https://svn.apache.org/repos/asf/incubator/rave/tags/0.7-incubating/ Maven staging repo: https://repository.apache.org/content/repositories/orgapacherave-015/ Source release: https://repository.apache.org/content/repositories/orgapacherave-015/org/apache/rave/rave-project/0.7-incubating/rave-project-0.7-incubating-source-release.zip Binary releases http://people.apache.org/builds/incubator/rave/0.7-incubating/apache-rave-0.7-incubating-bin.tar.gz http://people.apache.org/builds/incubator/rave/0.7-incubating/apache-rave-0.7-incubating-bin.zip PGP release keys: https://svn.apache.org/repos/asf/incubator/rave/KEYS Lazy consensus, vote open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Rave 0.7-incubating
On 1/23/12 3:29 PM, sebb seb...@gmail.com wrote: On 23 January 2012 15:17, Franklin, Matthew B. mfrank...@mitre.org wrote: This is the sixth incubator release for Apache Rave, with the artifacts being versioned as 0.7-incubating. We are requesting a lazy consensus vote, as we have already received 3 binding IPMC +1 votes during the release voting on rave-dev - VOTE: http://s.apache.org/xqH RESULT: http://s.apache.org/rg Release notes: http://svn.apache.org/repos/asf/incubator/rave/tags/0.7-incubating/CHANGE LOG SVN source tag (r1227377): https://svn.apache.org/repos/asf/incubator/rave/tags/0.7-incubating/ NOTICE file says: Apache Rave Copyright 2011 The Apache Software Foundation Is this still correct? The release was spun on January 4th of 2012 and there were 4 minor changes made between 2012 the release. Based on prior discussions on this list, minor changes don't seem to be a blocker [1]. Additionally, I have created a JIRA ticket for updating the copyright date on all NOTICE files [2]. [1] : http://markmail.org/message/3b776xpdzijynypc [2] : https://issues.apache.org/jira/browse/RAVE-439 Maven staging repo: https://repository.apache.org/content/repositories/orgapacherave-015/ Source release: https://repository.apache.org/content/repositories/orgapacherave-015/org/ apache/rave/rave-project/0.7-incubating/rave-project-0.7-incubating-sourc e-release.zip Binary releases http://people.apache.org/builds/incubator/rave/0.7-incubating/apache-rave -0.7-incubating-bin.tar.gz http://people.apache.org/builds/incubator/rave/0.7-incubating/apache-rave -0.7-incubating-bin.zip PGP release keys: https://svn.apache.org/repos/asf/incubator/rave/KEYS Lazy consensus, vote open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) - 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: [VOTE] Release Apache Rave 0.7-incubating
-Original Message- From: Ate Douma [mailto:a...@douma.nu] Sent: Monday, January 23, 2012 5:14 PM To: rave-...@incubator.apache.org Cc: general@incubator.apache.org Subject: Re: [VOTE] Release Apache Rave 0.7-incubating On 01/23/2012 10:56 PM, Ate Douma wrote: On 01/23/2012 10:30 PM, Franklin, Matthew B. wrote: On 1/23/12 3:29 PM, sebbseb...@gmail.com wrote: On 23 January 2012 15:17, Franklin, Matthew B.mfrank...@mitre.org wrote: This is the sixth incubator release for Apache Rave, with the artifacts being versioned as 0.7-incubating. We are requesting a lazy consensus vote, as we have already received 3 binding IPMC +1 votes during the release voting on rave-dev - VOTE: http://s.apache.org/xqH RESULT: http://s.apache.org/rg Release notes: http://svn.apache.org/repos/asf/incubator/rave/tags/0.7- incubating/CHANGE LOG SVN source tag (r1227377): https://svn.apache.org/repos/asf/incubator/rave/tags/0.7-incubating/ NOTICE file says: Apache Rave Copyright 2011 The Apache Software Foundation Is this still correct? The release was spun on January 4th of 2012 and there were 4 minor changes made between 2012 the release. Based on prior discussions on this list, minor changes don't seem to be a blocker [1]. Additionally, I have created a JIRA ticket for updating the copyright date on all NOTICE files [2]. [1] : http://markmail.org/message/3b776xpdzijynypc [2] : https://issues.apache.org/jira/browse/RAVE-439 Besides this being a minor and certainly non-blocker issue, a similar question came up just last week on legal-discuss@ where the question was if every copyright statement would need to be 'bumped' to adjust for the new year. Greg Stein provided IMO a nice and clear (follow up) answer about the importance of how and when to do this [3]: quote Actually, the shorter answer is get it close, but don't worry about it. (per a lawyer friend of mine) What you put in the header is advisory. If you end up in court, it has zero impact compared to the actual commit history that demonstrates it is your work. Your work is the operative issue; not when you happened to do that work. /quote Original message and thread link: http://markmail.org/message/v3n7vyd4anxmgzbn On second thought, the above quote might not be relevant in *this* context, as in this case it concerns the NOTICE file, not some copyrighted resource itself. Nonetheless, the fact this was a release cut on January 4th, I think it truely isn't of much concern anyway, and for subsequent releases we'll adjust the copyright date. I do however very much appreciate the proper review and feedback from sebb, and others on general@ alike, because all these tiny issues are soo easy to overlook! +1. Much better to catch it on January 23rd, 2012 than on January 23rd, 2015. Thanks, Sebb. Thanks, Ate So I see no reason at all to worry about these now. And, for the record, none of the NOTICE files in this release themselves were modified since 2011. Ate Maven staging repo: https://repository.apache.org/content/repositories/orgapacherave- 015/ Source release: https://repository.apache.org/content/repositories/orgapacherave- 015/org/ apache/rave/rave-project/0.7-incubating/rave-project-0.7-incubating- sourc e-release.zip Binary releases http://people.apache.org/builds/incubator/rave/0.7- incubating/apache-rave -0.7-incubating-bin.tar.gz http://people.apache.org/builds/incubator/rave/0.7- incubating/apache-rave -0.7-incubating-bin.zip PGP release keys: https://svn.apache.org/repos/asf/incubator/rave/KEYS Lazy consensus, vote open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) - 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
[ANNOUNCE] Apache Rave 0.6-INCUBATING Release
The Apache Rave (Incubating) team is pleased to announce the immediate availability of the Rave 0.6-INCUBATING Alpha release. Apache Rave is a new web and social mashup engine. It will provide an out-of-the-box, as well as extendible, lightweight Java platform to host, serve and manage OpenSocial, W3C and other web widgets. Rave is targeted as an engine for internet and intranet portals and as a building block to provide context-aware personalization and collaboration features for multi-site/multi-channel (mobile) oriented and content driven websites. The release can be obtained from the Apache Rave download page (http://incubator.apache.org/rave/downloads.html). Release Notes for this release are available at http://s.apache.org/ZZY. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[RESULT] [VOTE] Release Apache Rave 0.6-incubating
The voting period is now closed. Thanks to everyone who took the time to review the release. Result Summary for this List: +1 [1] 0[1] -1[0] With the two IPMC member votes from mentors on the dev list and the +1 from this list, the vote succeeds. IPMC member voting record: * Ate Douma:+1 * Ross Gardler: +1 Ant Elder: +1 *Denotes an IPMC member vote cast on the rave-dev list -Original Message- From: ant elder [mailto:ant.el...@gmail.com] Sent: Friday, January 13, 2012 3:53 AM To: general@incubator.apache.org Subject: Re: [1 IPMC VOTE NEEDED] [VOTE] Release Apache Rave 0.6- incubating I've had a look, the only issue i see is I don't think the NOTICE file in the binary distribution is correct as it has many things which i expect are not required. When we last discussed this on general@ we said this is not strictly a blocking problem, so +1 but i think you should do a complete review of whats in the NOTICE file with your mentors and remove everything which doesn't need to be there. ...ant On Thu, Jan 12, 2012 at 2:16 PM, Franklin, Matthew B. mfrank...@mitre.org wrote: We still need to get one more IPMC vote to close this vote. If someone could take a look, it would be greatly appreciated. -Matt -Original Message- From: Franklin, Matthew B. [mailto:mfrank...@mitre.org] Sent: Wednesday, January 11, 2012 8:03 AM To: general@incubator.apache.org Subject: RE: [VOTE] Release Apache Rave 0.6-incubating -Original Message- From: Franklin, Matthew B. [mailto:mfrank...@mitre.org] Sent: Monday, January 09, 2012 8:45 AM To: general@incubator.apache.org Cc: rave-...@incubator.apache.org Subject: RE: [VOTE] Release Apache Rave 0.6-incubating -Original Message- From: sebb [mailto:seb...@gmail.com] Sent: Monday, January 09, 2012 8:21 AM To: general@incubator.apache.org Subject: Re: [VOTE] Release Apache Rave 0.6-incubating On 9 January 2012 13:09, Franklin, Matthew B. mfrank...@mitre.org wrote: Does my answer below suffice? It would be nice to close this vote out one way or another The answer describes what happened. However, it does not fix the problem, which is that the end-user sees a file with conflicting information. Thanks. This is what I was looking for, so that we can have the discussion as to whether or not to cancel the release (we won't do a re-release). Not a blocker, but you may find it takes less time overall to fix the issue before release rather than dealing with user queries afterwards. It may also lessen confidence in the release: if there is such an obvious error, what other errors are lurking? While I agree that it doesn't look great, the CHANGELOG is distributed with the source release and is probably not viewed as much as the release notes sent out with the announcement (which will be the JIRA list I linked). I will take this back to our dev list, but if they don't see it as a blocker, would you be comfortable voting +1? The community was presented with the issue and via lazy consensus agreed to move forward with the release, even though the CHANGELOG file is incorrect. We still need 1 final IPMC vote to release. [ Community discussion on proceeding: http://markmail.org/message/tp5nyqh24tdpybw6 ] -Original Message- From: Franklin, Matthew B. [mailto:mfrank...@mitre.org] Sent: Tuesday, January 03, 2012 12:19 PM To: general@incubator.apache.org Subject: RE: [VOTE] Release Apache Rave 0.6-incubating -Original Message- From: sebb [mailto:seb...@gmail.com] Sent: Tuesday, January 03, 2012 7:06 AM To: general@incubator.apache.org Subject: Re: [VOTE] Release Apache Rave 0.6-incubating On 28 December 2011 19:15, Franklin, Matthew B. mfrank...@mitre.org wrote: This is the fifth incubator release for Apache Rave, with the artifacts being versioned as 0.6-incubating. We are requesting at least one additional IPMC member vote, as we have received 2 binding IPMC +1 votes during the release voting on rave- dev - VOTE: http://s.apache.org/Czr RESULT: http://s.apache.org/yIQ IPMC member votes from the rave-dev list: Ate Douma: +1 Ross Gardler: +1 Release notes: http://svn.apache.org/repos/asf/incubator/rave/tags/0.6- incubating/CHANGELOG Apparently, I didn't commit back the CHANGELOG for 0.6 . Here is the issue list from JIRA https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12 31 1 2 90 version=12317563 which says: Release Notes - Rave - Version 0.5-INCUBATING So what was changed for 0.6? SVN source tag (r1208867): https://svn.apache.org/repos/asf/incubator/rave/tags/0.6- incubating/ Maven staging repos: https://repository.apache.org/content/repositories/orgapacherave- 278/ https://repository.apache.org/content/repositories/orgapacherave- 279/ Source release: https://repository.apache.org/content/repositories/orgapacherave- 278/org/apache/rave/rave-project/0.6-incubating/rave-project-0.6- incubating-source-release.zip Binary releases http
RE: [1 IPMC VOTE NEEDED] [VOTE] Release Apache Rave 0.6-incubating
I've had a look, the only issue i see is I don't think the NOTICE file in the binary distribution is correct as it has many things which i expect are not required. When we last discussed this on general@ we said this is not strictly a blocking problem, so +1 but i think you should do a complete review of whats in the NOTICE file with your mentors and remove everything which doesn't need to be there. Thanks for taking a look. I will take your suggestion back to the DEV list and see if our mentors find any changes that need to be made. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[1 IPMC VOTE NEEDED] [VOTE] Release Apache Rave 0.6-incubating
We still need to get one more IPMC vote to close this vote. If someone could take a look, it would be greatly appreciated. -Matt -Original Message- From: Franklin, Matthew B. [mailto:mfrank...@mitre.org] Sent: Wednesday, January 11, 2012 8:03 AM To: general@incubator.apache.org Subject: RE: [VOTE] Release Apache Rave 0.6-incubating -Original Message- From: Franklin, Matthew B. [mailto:mfrank...@mitre.org] Sent: Monday, January 09, 2012 8:45 AM To: general@incubator.apache.org Cc: rave-...@incubator.apache.org Subject: RE: [VOTE] Release Apache Rave 0.6-incubating -Original Message- From: sebb [mailto:seb...@gmail.com] Sent: Monday, January 09, 2012 8:21 AM To: general@incubator.apache.org Subject: Re: [VOTE] Release Apache Rave 0.6-incubating On 9 January 2012 13:09, Franklin, Matthew B. mfrank...@mitre.org wrote: Does my answer below suffice? It would be nice to close this vote out one way or another The answer describes what happened. However, it does not fix the problem, which is that the end-user sees a file with conflicting information. Thanks. This is what I was looking for, so that we can have the discussion as to whether or not to cancel the release (we won't do a re-release). Not a blocker, but you may find it takes less time overall to fix the issue before release rather than dealing with user queries afterwards. It may also lessen confidence in the release: if there is such an obvious error, what other errors are lurking? While I agree that it doesn't look great, the CHANGELOG is distributed with the source release and is probably not viewed as much as the release notes sent out with the announcement (which will be the JIRA list I linked). I will take this back to our dev list, but if they don't see it as a blocker, would you be comfortable voting +1? The community was presented with the issue and via lazy consensus agreed to move forward with the release, even though the CHANGELOG file is incorrect. We still need 1 final IPMC vote to release. [ Community discussion on proceeding: http://markmail.org/message/tp5nyqh24tdpybw6 ] -Original Message- From: Franklin, Matthew B. [mailto:mfrank...@mitre.org] Sent: Tuesday, January 03, 2012 12:19 PM To: general@incubator.apache.org Subject: RE: [VOTE] Release Apache Rave 0.6-incubating -Original Message- From: sebb [mailto:seb...@gmail.com] Sent: Tuesday, January 03, 2012 7:06 AM To: general@incubator.apache.org Subject: Re: [VOTE] Release Apache Rave 0.6-incubating On 28 December 2011 19:15, Franklin, Matthew B. mfrank...@mitre.org wrote: This is the fifth incubator release for Apache Rave, with the artifacts being versioned as 0.6-incubating. We are requesting at least one additional IPMC member vote, as we have received 2 binding IPMC +1 votes during the release voting on rave-dev - VOTE: http://s.apache.org/Czr RESULT: http://s.apache.org/yIQ IPMC member votes from the rave-dev list: Ate Douma: +1 Ross Gardler: +1 Release notes: http://svn.apache.org/repos/asf/incubator/rave/tags/0.6- incubating/CHANGELOG Apparently, I didn't commit back the CHANGELOG for 0.6 . Here is the issue list from JIRA https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=1231 1 2 90 version=12317563 which says: Release Notes - Rave - Version 0.5-INCUBATING So what was changed for 0.6? SVN source tag (r1208867): https://svn.apache.org/repos/asf/incubator/rave/tags/0.6- incubating/ Maven staging repos: https://repository.apache.org/content/repositories/orgapacherave- 278/ https://repository.apache.org/content/repositories/orgapacherave- 279/ Source release: https://repository.apache.org/content/repositories/orgapacherave- 278/org/apache/rave/rave-project/0.6-incubating/rave-project-0.6- incubating-source-release.zip Binary releases http://people.apache.org/builds/incubator/rave/0.6- incubating/apache- rave-0.6-incubating-bin.tar.gz http://people.apache.org/builds/incubator/rave/0.6- incubating/apache- rave-0.6-incubating-bin.zip PGP release keys: https://svn.apache.org/repos/asf/incubator/rave/KEYS Vote open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) - 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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
RE: [VOTE] Release Apache Rave 0.6-incubating
-Original Message- From: Franklin, Matthew B. [mailto:mfrank...@mitre.org] Sent: Monday, January 09, 2012 8:45 AM To: general@incubator.apache.org Cc: rave-...@incubator.apache.org Subject: RE: [VOTE] Release Apache Rave 0.6-incubating -Original Message- From: sebb [mailto:seb...@gmail.com] Sent: Monday, January 09, 2012 8:21 AM To: general@incubator.apache.org Subject: Re: [VOTE] Release Apache Rave 0.6-incubating On 9 January 2012 13:09, Franklin, Matthew B. mfrank...@mitre.org wrote: Does my answer below suffice? It would be nice to close this vote out one way or another The answer describes what happened. However, it does not fix the problem, which is that the end-user sees a file with conflicting information. Thanks. This is what I was looking for, so that we can have the discussion as to whether or not to cancel the release (we won't do a re-release). Not a blocker, but you may find it takes less time overall to fix the issue before release rather than dealing with user queries afterwards. It may also lessen confidence in the release: if there is such an obvious error, what other errors are lurking? While I agree that it doesn't look great, the CHANGELOG is distributed with the source release and is probably not viewed as much as the release notes sent out with the announcement (which will be the JIRA list I linked). I will take this back to our dev list, but if they don't see it as a blocker, would you be comfortable voting +1? The community was presented with the issue and via lazy consensus agreed to move forward with the release, even though the CHANGELOG file is incorrect. We still need 1 final IPMC vote to release. [ Community discussion on proceeding: http://markmail.org/message/tp5nyqh24tdpybw6 ] -Original Message- From: Franklin, Matthew B. [mailto:mfrank...@mitre.org] Sent: Tuesday, January 03, 2012 12:19 PM To: general@incubator.apache.org Subject: RE: [VOTE] Release Apache Rave 0.6-incubating -Original Message- From: sebb [mailto:seb...@gmail.com] Sent: Tuesday, January 03, 2012 7:06 AM To: general@incubator.apache.org Subject: Re: [VOTE] Release Apache Rave 0.6-incubating On 28 December 2011 19:15, Franklin, Matthew B. mfrank...@mitre.org wrote: This is the fifth incubator release for Apache Rave, with the artifacts being versioned as 0.6-incubating. We are requesting at least one additional IPMC member vote, as we have received 2 binding IPMC +1 votes during the release voting on rave-dev - VOTE: http://s.apache.org/Czr RESULT: http://s.apache.org/yIQ IPMC member votes from the rave-dev list: Ate Douma: +1 Ross Gardler: +1 Release notes: http://svn.apache.org/repos/asf/incubator/rave/tags/0.6- incubating/CHANGELOG Apparently, I didn't commit back the CHANGELOG for 0.6 . Here is the issue list from JIRA https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311 2 90 version=12317563 which says: Release Notes - Rave - Version 0.5-INCUBATING So what was changed for 0.6? SVN source tag (r1208867): https://svn.apache.org/repos/asf/incubator/rave/tags/0.6-incubating/ Maven staging repos: https://repository.apache.org/content/repositories/orgapacherave- 278/ https://repository.apache.org/content/repositories/orgapacherave- 279/ Source release: https://repository.apache.org/content/repositories/orgapacherave- 278/org/apache/rave/rave-project/0.6-incubating/rave-project-0.6- incubating-source-release.zip Binary releases http://people.apache.org/builds/incubator/rave/0.6- incubating/apache- rave-0.6-incubating-bin.tar.gz http://people.apache.org/builds/incubator/rave/0.6- incubating/apache- rave-0.6-incubating-bin.zip PGP release keys: https://svn.apache.org/repos/asf/incubator/rave/KEYS Vote open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) - 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 - 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
