Re: [VOTE] Release celix-0.0.1-incubating
Hi, Great. Please make it available in SVN so that I can review. Done. The files in SVN are already a little bit further then the source in the release. So there will probably be some small changes. http://svn.apache.org/viewvc?view=revisionrevision=1408711 http://svn.apache.org/viewvc?view=revisionrevision=1408708 -- Met vriendelijke groet, Alexander Broekhuis
Re: Shepherd Assignments?
Hi, On Tue, Nov 13, 2012 at 3:36 AM, Dave Fisher dave2w...@comcast.net wrote: I'm waiting for my shepherd assignments. Good, I'll get to that in a moment! BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: November reports
On 14/11/2012 12:14, Jukka Zitting 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. Hi Jukka, I've just added something in this respect to Syncope November report and also notified our mentors to get it signed off. Regards. -- Francesco Chicchiriccò ASF Member, Apache Cocoon PMC and Apache Syncope PPMC Member http://people.apache.org/~ilgrosso/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: November reports
Wookie is graduated? Shouldn't they be reporting as a TLP, even if they haven't moved all their stuff yet? On Wed, Nov 14, 2012 at 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 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: November reports
Droids seems to be a really easy shepherding assignment. They are on the watch list for low activity, they are self-aware of this, and they are having a conversation with the commons TLP about perhaps becoming a component there. I don't know if there is any contribution any of the rest of us could make to increasing the likelihood of a positive outcome of that conversation. On Wed, Nov 14, 2012 at 6:35 AM, Francesco Chicchiriccò ilgro...@apache.org wrote: On 14/11/2012 12:14, Jukka Zitting 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. Hi Jukka, I've just added something in this respect to Syncope November report and also notified our mentors to get it signed off. Regards. -- Francesco Chicchiriccò ASF Member, Apache Cocoon PMC and Apache Syncope PPMC Member http://people.apache.org/~ilgrosso/ - 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
OK, their report was misleading. I'll improve it slightly :-) On Wed, Nov 14, 2012 at 6:54 AM, Jukka Zitting jukka.zitt...@gmail.com wrote: Hi, On Wed, Nov 14, 2012 at 1:52 PM, Benson Margulies bimargul...@gmail.com wrote: Wookie is graduated? Shouldn't they be reporting as a TLP, even if they haven't moved all their stuff yet? Their graduation vote passed, but until the board establishes the TLP in the next meeting they (like Syncope) report through the Incubator. 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: November reports
Hi, On Wed, Nov 14, 2012 at 1:54 PM, Jukka Zitting jukka.zitt...@gmail.com wrote: On Wed, Nov 14, 2012 at 1:52 PM, Benson Margulies bimargul...@gmail.com wrote: Wookie is graduated? Shouldn't they be reporting as a TLP, even if they haven't moved all their stuff yet? Their graduation vote passed, but until the board establishes the TLP in the next meeting they (like Syncope) report through the Incubator. In fact, since we already did pass the graduation vote, there isn't much need for any more detailed reviews, so like Syncope I moved Wookie directly to the Ready to graduate category and removed it from the shepherd TODOs. BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: November reports
Ignore my message, my eyeballs were clearly not awake the first time I read their report. It was fine. On Wed, Nov 14, 2012 at 6:57 AM, Benson Margulies bimargul...@gmail.com wrote: OK, their report was misleading. I'll improve it slightly :-) On Wed, Nov 14, 2012 at 6:54 AM, Jukka Zitting jukka.zitt...@gmail.com wrote: Hi, On Wed, Nov 14, 2012 at 1:52 PM, Benson Margulies bimargul...@gmail.com wrote: Wookie is graduated? Shouldn't they be reporting as a TLP, even if they haven't moved all their stuff yet? Their graduation vote passed, but until the board establishes the TLP in the next meeting they (like Syncope) report through the Incubator. 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: [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 to
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: [PROPOSAL] Apache Steams Project
Thanks Matthew, but the page is an immutable one. how can I do? cheers, Davide On Wed, Nov 14, 2012 at 12:14 PM, Franklin, Matthew B. mfrank...@mitre.org wrote: -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
Re: [VOTE] Accept Apache Streams as an Incubator Project
+1 (non-binding) On Wed, Nov 14, 2012 at 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
Re: [VOTE] Accept Apache Streams as an Incubator Project
+ 1 (binding) All the best, Suresh On Nov 14, 2012, at 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
Re: [VOTE] Accept Apache Streams as an Incubator Project
Hi, On Wed, Nov 14, 2012 at 2:37 PM, Franklin, Matthew B. mfrank...@mitre.org wrote: Please vote. [x] +1 Accept Streams into the incubator Though I do think there's some life also in the alternative name, Apache Screams, that came up in discussion during ACEU. ;-) BR, Jukka Zitting - 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 (Love the idea of Apache Screams, we could then have a Wookie Scream in a Rave) Ross -Original Message- From: Jukka Zitting [mailto:jukka.zitt...@gmail.com] Sent: 14 November 2012 14:49 To: general Subject: Re: [VOTE] Accept Apache Streams as an Incubator Project Hi, On Wed, Nov 14, 201a 2 at 2:37 PM, Franklin, Matthew B. mfrank...@mitre.org wrote: Please vote. [x] +1 Accept Streams into the incubator Though I do think there's some life also in the alternative name, Apache Screams, that came up in discussion during ACEU. ;-) 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 Sander On Wed, Nov 14, 2012 at 3:24 PM, Ross Gardler rgard...@opendirective.comwrote: +1 (Love the idea of Apache Screams, we could then have a Wookie Scream in a Rave) Ross -Original Message- From: Jukka Zitting [mailto:jukka.zitt...@gmail.com] Sent: 14 November 2012 14:49 To: general Subject: Re: [VOTE] Accept Apache Streams as an Incubator Project Hi, On Wed, Nov 14, 201a 2 at 2:37 PM, Franklin, Matthew B. mfrank...@mitre.org wrote: Please vote. [x] +1 Accept Streams into the incubator Though I do think there's some life also in the alternative name, Apache Screams, that came up in discussion during ACEU. ;-) 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 On 14 Nov 2012, at 15:24, Ross Gardler wrote: +1 (Love the idea of Apache Screams, we could then have a Wookie Scream in a Rave) +100 Ross -Original Message- From: Jukka Zitting [mailto:jukka.zitt...@gmail.com] Sent: 14 November 2012 14:49 To: general Subject: Re: [VOTE] Accept Apache Streams as an Incubator Project Hi, On Wed, Nov 14, 201a 2 at 2:37 PM, Franklin, Matthew B. mfrank...@mitre.org wrote: Please vote. [x] +1 Accept Streams into the incubator Though I do think there's some life also in the alternative name, Apache Screams, that came up in discussion during ACEU. ;-) 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: [VOTE] Release JSPWiki version 2.9.0-incubating
Great work! I've got the following questions concerning the ./LICENSE file for the source release: There is a list of jar files in the ./LICENSE file of the following form: activation-1.1.jar doc/LICENSE.cddl What is the point of including licenses for files which are absent in the source release? Why license texts appear twice (both in the ./LICENSE file and ./doc/ folder)? That provides more place for possible errors. I believe the list is good to exist in the ./LICENSE file for the binary release. Why it does not mention all licenses from the source release ./LICENSE file, e.g. Mozilla license? How to understand Copyright (c) year copyright holders in MIT license. The template style cannot appear in final version of the LICENSE. Also, IMHO, copyright attribution does not belong to the license (unless you use a copyrighted license). -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Wed, Nov 14, 2012 at 5:03 AM, Florian Holeczek flori...@apache.org wrote: Hi all, I'd like to start a vote on an incubator release for Apache JSPWiki, version 2.9.0-incubating. Apache JSPWiki (incubating) is a leading open source WikiWiki engine, feature-rich and built around standard J2EE components (Java, servlets, JSP). A vote was held on the developer mailing list [1] and passed with 9 +1s [2], two of them from our mentors. This release candidate fixes the following issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310732version=12319521 The tag to be voted upon: https://svn.apache.org/repos/asf/incubator/jspwiki/tags/jspwiki_2_9_0_incubating Source and binary files: http://people.apache.org/~florianh/jspwiki-2.9.0-incubating/ Checksums: JSPWiki-2.9.0-incubating-src.zip MD5:287e75857b03b41dca769211591c6144 SHA1: 74b24e526177b7ddf5394b4b96b67bb9081628a4 SHA512: 9a080ed994e4308e4ff6386f6e5e88e42d27fc8a8abe37d2874d3c8477fe097037017fffdd03430cdb0ca7a73efba91bf58e70c1943e08c9565170809daa953a JSPWiki-2.9.0-incubating-bin.zip MD5:7e774dc46c112ca895aad60fb607dc60 SHA1: e529eb02d13f4061534d85dd0e78d67c5dfe29a5 SHA512: 575eae72390178005bf7cf57332af9a1da85515d6fc10cf9c8b3548f50743c0e57c0c6f46bc99b70cd1328ef083fb4a4fe9f3867e9ec7c7e4a640b845a2e2ee4 JSPWiki's KEYS file containing PGP keys we use to sign the release: http://www.apache.org/dist/incubator/jspwiki/KEYS For convenience, this directory includes a binary distribution and a RAT report on the cited tag. You can manually generate the RAT report from a clean source by running the rat-report Ant target. Please vote: [ ] +1 approve, release Apache JSPWiki 2.9.0-incubating [ ] +0 no opinion [ ] -1 disapprove (and giving a reason) The vote will be open for at least 72 hours. Best regards Florian Holeczek [1] http://markmail.org/message/gksvnjnru2nhhenf [2] http://markmail.org/message/mht24dwvpmm7xgft - 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 -Andrew On 11/14/2012 04:37 AM, Franklin, Matthew B. 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 that code is developed
Re: [VOTE] Accept Apache Streams as an Incubator Project
+1 On Wed, Nov 14, 2012 at 7:24 AM, Ross Gardler rgard...@opendirective.comwrote: +1 (Love the idea of Apache Screams, we could then have a Wookie Scream in a Rave) Ross -Original Message- From: Jukka Zitting [mailto:jukka.zitt...@gmail.com] Sent: 14 November 2012 14:49 To: general Subject: Re: [VOTE] Accept Apache Streams as an Incubator Project Hi, On Wed, Nov 14, 201a 2 at 2:37 PM, Franklin, Matthew B. mfrank...@mitre.org wrote: Please vote. [x] +1 Accept Streams into the incubator Though I do think there's some life also in the alternative name, Apache Screams, that came up in discussion during ACEU. ;-) 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: Karma for incubator wiki
Hi, On Wed, Nov 14, 2012 at 5:13 PM, Andrew Hart ah...@apache.org wrote: Could someone please grant me karma to edit the incubator wiki? I'd like to add my name to a proposal. My wiki username is 'AndrewHart'. Done. Incidentally, it looks like Davide Palmisano (see below) is in the same situation. What's his wikiname? BR, Jukka Zitting - 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 (non-binding) On Wed, Nov 14, 2012 at 11:16 AM, James M Snell jasn...@gmail.com wrote: +1 On Wed, Nov 14, 2012 at 7:24 AM, Ross Gardler rgard...@opendirective.com wrote: +1 (Love the idea of Apache Screams, we could then have a Wookie Scream in a Rave) Ross -Original Message- From: Jukka Zitting [mailto:jukka.zitt...@gmail.com] Sent: 14 November 2012 14:49 To: general Subject: Re: [VOTE] Accept Apache Streams as an Incubator Project Hi, On Wed, Nov 14, 201a 2 at 2:37 PM, Franklin, Matthew B. mfrank...@mitre.org wrote: Please vote. [x] +1 Accept Streams into the incubator Though I do think there's some life also in the alternative name, Apache Screams, that came up in discussion during ACEU. ;-) 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] Release Apache Bloodhound 0.2 (incubating)
+1 to release (IPMC, binding) [ apologies for the extreme delay :-( ] On Mon, Oct 29, 2012 at 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)
Oh. Forgot one item: so the below is conditional on resolving: the .md5 does not match the .tar.gz. (I did not examine the signature (.asc) to see if it matches the .tar.gz) On Wed, Nov 14, 2012 at 12:52 PM, Greg Stein gst...@gmail.com wrote: +1 to release (IPMC, binding) [ apologies for the extreme delay :-( ] On Mon, Oct 29, 2012 at 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] Accept Apache Streams as an Incubator Project
+1 (binding) Sent from my Samsung Galaxy S3 Apologies for any typos On Nov 14, 2012 6:36 PM, Ryan Baxter rbaxte...@apache.org wrote: +1 (non-binding) On Wed, Nov 14, 2012 at 11:16 AM, James M Snell jasn...@gmail.com wrote: +1 On Wed, Nov 14, 2012 at 7:24 AM, Ross Gardler rgard...@opendirective.com wrote: +1 (Love the idea of Apache Screams, we could then have a Wookie Scream in a Rave) Ross -Original Message- From: Jukka Zitting [mailto:jukka.zitt...@gmail.com] Sent: 14 November 2012 14:49 To: general Subject: Re: [VOTE] Accept Apache Streams as an Incubator Project Hi, On Wed, Nov 14, 201a 2 at 2:37 PM, Franklin, Matthew B. mfrank...@mitre.org wrote: Please vote. [x] +1 Accept Streams into the incubator Though I do think there's some life also in the alternative name, Apache Screams, that came up in discussion during ACEU. ;-) 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) Ate On 11/14/2012 01:37 PM, Franklin, Matthew B. 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 that code is
Re: [VOTE] Release Apache Bloodhound 0.2 (incubating)
Hi, 2012/11/14 Greg Stein gst...@gmail.com Oh. Forgot one item: so the below is conditional on resolving: the .md5 does not match the .tar.gz. (I did not examine the signature (.asc) to see if it matches the .tar.gz) I haven't checked the files, but they are placed in svn, and when downloading using chrome or firefox the files are double gzipped. We (Celix) had the same problem. See [1] for more info. This sounds like a similar problem.. Did you try downloading the file using wget? [1]: https://issues.apache.org/jira/browse/INFRA-5445 -- Met vriendelijke groet, Alexander Broekhuis
[RESULT][VOTE] Accept Onami proposal in the Incubator
Hi all, more than 72h passed and that vote can be closed and passes with the following resolution: six +1 binding votes from following IPMC members: * Christian Grobmeier * Alan Cabrera * Mohammad Nour El-Din * Roman Shaposhnik * Bertrand Delacretaz * Olivier Lamy two +1 non-binding votes from: * Simone Tripodi * Eric Charles I'm filling issues on INFRA to setup the new podling tomorrow morning - many thanks to everybody who took part to the proposal review! 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 Sun, Nov 11, 2012 at 8:44 PM, Simone Tripodi simonetrip...@apache.org wrote: Hi all guys, I am submitting a proposal that has been open for discussion for some days (with the former name of Mayhem), so now submitting for a vote for this project to be accepted into the incubator. Vote will be open for at least 72 hours and closes approximately on Nov 14th, 2012 at 7:45pm GMT Many thanks in advance, have a nice day! -Simo Adam Berry ~ = Onami = == Abstract == The following proposal is about Onami, a project focused on all aspects of Google Guice[1] extensions. The name takes inspiration from Great Waves (O-nami, in Japanese) Zen Story[2]. == Proposal == Apache Onami aims to create a community focused on the development and maintenance of a set of Google Guice extensions not provided out of the box by the library itself nor the Google developers team, such as integration with 3rd part frameworks or extra functionalities. == Background == Google Guice is a modern, lightweight and fast Dependency Injection Open Source Java library developed by Google, released for the first time on 2006, which is developed under the Google governance. A small group of people, specifically ASF committers Davide Palmisano, Marco Spearanza and Simone Tripodi, that define themselves The 99 Software Foundation[3] (also 99soft for brevity), with the help of some contributors, has developed and maintained a good number of Open Source Google Guice extensions[4], that have been adopted in some (Open Source) projects. Since the community clearly demonstrated the sign of growing participation, they thought times were mature enough to move the components to a real community-driven environment such as the Apache Software Foundation. == Rationale == Actually, there are no projects hosted by the ASF focused on providing Google Guice extensions and even if Google provides some extensions and allows people participating by submitting issues/patches/... there is no real community involvement, so moving the existing 99soft components under the Apache umbrella would mean create a real community-driven project around Guice where people can become active part of the development. = Current Status = == Meritocracy == The historical 99soft team believes in meritocracy and always acted as a community. Mailing list, open issue tracker and other communication channels have always been adopted since its first releases. The adoption in a larger community, such as Apache, is the natural evolution for 99soft components. Moreover, the Apache standards will enforce the existing 99soft community practices and will be a foundation for future committers involvement. == Core Developers == In alphabetical order: * Christian Grobmeier grobmeier at apache dot org * Daniel Manzke daniel dot manzke at googlemail dot com * Davide Palmisano dpalmisano at apache dot org * Marco Speranza marcosperanza at apache dot org * Nino Martinez Wael nino dot martinez dot wael at gmail dot com * Simone Tripodi simonetripodi at apache dot org === Regular Contributors === In alphabetical order: * Cody Ray cray at brighttag dot com * Ghislain Picpoc Touratier ghislain dot touratier at gmail dot com * Ioannis Canellos iocanel at apache dot org * Jordi Gerona jordi at donky dot org * Marzia Forli marzia dot forli at yahoo.com * Pawel Poltorak pawel dot poltorak at gmail.com * Thilo-Alexander Ginkel thilo at ginkel dot com == Alignment == The Apache Onami project is intended to be portable and be fully compatible with Google Guice. To promote the adoption of this project, we believe that it is important that it remains free from corporate association and is perceived by the community to be vendor neutral. To this end, the Apache Software Foundation with its values of transparency and community makes it an excellent fit for this project, not to mention that project creators are already Apache Members/Committers. = Known Risks = == Orphaned Products == The increasing number of Google Guice adopters and the raising interest for its extensions let us believe that there is a minimal risk for this work to being abandoned from the community. == Inexperience with Open Source == All of the
Re: [RESULT][VOTE] Accept Onami proposal in the Incubator
Quick followup: couldn't resist so I started creating the main issue (with subtaks) for Onami, please follow https://issues.apache.org/jira/browse/INFRA-5521 best, -Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Wed, Nov 14, 2012 at 11:19 PM, Simone Tripodi simonetrip...@apache.org wrote: Hi all, more than 72h passed and that vote can be closed and passes with the following resolution: six +1 binding votes from following IPMC members: * Christian Grobmeier * Alan Cabrera * Mohammad Nour El-Din * Roman Shaposhnik * Bertrand Delacretaz * Olivier Lamy two +1 non-binding votes from: * Simone Tripodi * Eric Charles I'm filling issues on INFRA to setup the new podling tomorrow morning - many thanks to everybody who took part to the proposal review! 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 Sun, Nov 11, 2012 at 8:44 PM, Simone Tripodi simonetrip...@apache.org wrote: Hi all guys, I am submitting a proposal that has been open for discussion for some days (with the former name of Mayhem), so now submitting for a vote for this project to be accepted into the incubator. Vote will be open for at least 72 hours and closes approximately on Nov 14th, 2012 at 7:45pm GMT Many thanks in advance, have a nice day! -Simo Adam Berry ~ = Onami = == Abstract == The following proposal is about Onami, a project focused on all aspects of Google Guice[1] extensions. The name takes inspiration from Great Waves (O-nami, in Japanese) Zen Story[2]. == Proposal == Apache Onami aims to create a community focused on the development and maintenance of a set of Google Guice extensions not provided out of the box by the library itself nor the Google developers team, such as integration with 3rd part frameworks or extra functionalities. == Background == Google Guice is a modern, lightweight and fast Dependency Injection Open Source Java library developed by Google, released for the first time on 2006, which is developed under the Google governance. A small group of people, specifically ASF committers Davide Palmisano, Marco Spearanza and Simone Tripodi, that define themselves The 99 Software Foundation[3] (also 99soft for brevity), with the help of some contributors, has developed and maintained a good number of Open Source Google Guice extensions[4], that have been adopted in some (Open Source) projects. Since the community clearly demonstrated the sign of growing participation, they thought times were mature enough to move the components to a real community-driven environment such as the Apache Software Foundation. == Rationale == Actually, there are no projects hosted by the ASF focused on providing Google Guice extensions and even if Google provides some extensions and allows people participating by submitting issues/patches/... there is no real community involvement, so moving the existing 99soft components under the Apache umbrella would mean create a real community-driven project around Guice where people can become active part of the development. = Current Status = == Meritocracy == The historical 99soft team believes in meritocracy and always acted as a community. Mailing list, open issue tracker and other communication channels have always been adopted since its first releases. The adoption in a larger community, such as Apache, is the natural evolution for 99soft components. Moreover, the Apache standards will enforce the existing 99soft community practices and will be a foundation for future committers involvement. == Core Developers == In alphabetical order: * Christian Grobmeier grobmeier at apache dot org * Daniel Manzke daniel dot manzke at googlemail dot com * Davide Palmisano dpalmisano at apache dot org * Marco Speranza marcosperanza at apache dot org * Nino Martinez Wael nino dot martinez dot wael at gmail dot com * Simone Tripodi simonetripodi at apache dot org === Regular Contributors === In alphabetical order: * Cody Ray cray at brighttag dot com * Ghislain Picpoc Touratier ghislain dot touratier at gmail dot com * Ioannis Canellos iocanel at apache dot org * Jordi Gerona jordi at donky dot org * Marzia Forli marzia dot forli at yahoo.com * Pawel Poltorak pawel dot poltorak at gmail.com * Thilo-Alexander Ginkel thilo at ginkel dot com == Alignment == The Apache Onami project is intended to be portable and be fully compatible with Google Guice. To promote the adoption of this project, we believe that it is important that it remains free from corporate association and is perceived by the community to be vendor neutral. To this end, the Apache Software Foundation with its values of transparency and
Re: [VOTE] Release Apache Bloodhound 0.2 (incubating)
On Nov 14, 2012 2:13 PM, Alexander Broekhuis a.broekh...@gmail.com wrote: Hi, 2012/11/14 Greg Stein gst...@gmail.com Oh. Forgot one item: so the below is conditional on resolving: the .md5 does not match the .tar.gz. (I did not examine the signature (.asc) to see if it matches the .tar.gz) I haven't checked the files, but they are placed in svn, and when downloading using chrome or firefox the files are double gzipped. We (Celix) had the same problem. See [1] for more info. This sounds like a similar problem.. Did you try downloading the file using wget? Ooh! I used Chrome. Will try wget when I get home. Thanks! -g
Re: [VOTE] Release JSPWiki version 2.9.0-incubating
Hi Alexei, activation-1.1.jar et al are downloaded as part of the build. They're not included in the source because that's contrary to the Apache principles. That was noted in our July report (and tracked at [#1]). Regarding the LICENSE / doc/LICENSE.* files: initially, we kept each license in a separate file (doc/LICENSE.*), while ./LICENSE contained only the AL. This raised some concerns, noted on our 3rd RC vote [#2], which led to ./LICENSE file also having verbatim copies of all used licenses. As for the Mozilla license, it's in the ./LICENSE file (line 1090 onwards), we use custom-rhino in some of the tests, which uses that license. cheers, juan pablo p.d.: your vote being..? O:-D [#1]: https://issues.apache.org/jira/browse/JSPWIKI-738https://issues.apache.org/jira/browse/JSPWIKI-738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419501#comment-13419501 [#2]: http://mail-archives.apache.org/mod_mbox/incubator-general/201210.mbox/%3c80852492-ac42-4f8d-82ca-760eefccd...@oracle.com%3E On Wed, Nov 14, 2012 at 4:36 PM, Alexei Fedotov alexei.fedo...@gmail.comwrote: Great work! I've got the following questions concerning the ./LICENSE file for the source release: There is a list of jar files in the ./LICENSE file of the following form: activation-1.1.jar doc/LICENSE.cddl What is the point of including licenses for files which are absent in the source release? Why license texts appear twice (both in the ./LICENSE file and ./doc/ folder)? That provides more place for possible errors. I believe the list is good to exist in the ./LICENSE file for the binary release. Why it does not mention all licenses from the source release ./LICENSE file, e.g. Mozilla license? How to understand Copyright (c) year copyright holders in MIT license. The template style cannot appear in final version of the LICENSE. Also, IMHO, copyright attribution does not belong to the license (unless you use a copyrighted license). -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Wed, Nov 14, 2012 at 5:03 AM, Florian Holeczek flori...@apache.org wrote: Hi all, I'd like to start a vote on an incubator release for Apache JSPWiki, version 2.9.0-incubating. Apache JSPWiki (incubating) is a leading open source WikiWiki engine, feature-rich and built around standard J2EE components (Java, servlets, JSP). A vote was held on the developer mailing list [1] and passed with 9 +1s [2], two of them from our mentors. This release candidate fixes the following issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310732version=12319521 The tag to be voted upon: https://svn.apache.org/repos/asf/incubator/jspwiki/tags/jspwiki_2_9_0_incubating Source and binary files: http://people.apache.org/~florianh/jspwiki-2.9.0-incubating/ Checksums: JSPWiki-2.9.0-incubating-src.zip MD5:287e75857b03b41dca769211591c6144 SHA1: 74b24e526177b7ddf5394b4b96b67bb9081628a4 SHA512: 9a080ed994e4308e4ff6386f6e5e88e42d27fc8a8abe37d2874d3c8477fe097037017fffdd03430cdb0ca7a73efba91bf58e70c1943e08c9565170809daa953a JSPWiki-2.9.0-incubating-bin.zip MD5:7e774dc46c112ca895aad60fb607dc60 SHA1: e529eb02d13f4061534d85dd0e78d67c5dfe29a5 SHA512: 575eae72390178005bf7cf57332af9a1da85515d6fc10cf9c8b3548f50743c0e57c0c6f46bc99b70cd1328ef083fb4a4fe9f3867e9ec7c7e4a640b845a2e2ee4 JSPWiki's KEYS file containing PGP keys we use to sign the release: http://www.apache.org/dist/incubator/jspwiki/KEYS For convenience, this directory includes a binary distribution and a RAT report on the cited tag. You can manually generate the RAT report from a clean source by running the rat-report Ant target. Please vote: [ ] +1 approve, release Apache JSPWiki 2.9.0-incubating [ ] +0 no opinion [ ] -1 disapprove (and giving a reason) The vote will be open for at least 72 hours. Best regards Florian Holeczek [1] http://markmail.org/message/gksvnjnru2nhhenf [2] http://markmail.org/message/mht24dwvpmm7xgft - 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 Bloodhound 0.2 (incubating)
I've confirmed this discrepancy is the same as what Alexander Broekhuis posted about, as noted in INFRA-5445. So 0.2 is all good to go!! On Wed, Nov 14, 2012 at 12:57 PM, Greg Stein gst...@gmail.com wrote: Oh. Forgot one item: so the below is conditional on resolving: the .md5 does not match the .tar.gz. (I did not examine the signature (.asc) to see if it matches the .tar.gz) On Wed, Nov 14, 2012 at 12:52 PM, Greg Stein gst...@gmail.com wrote: +1 to release (IPMC, binding) [ apologies for the extreme delay :-( ] On Mon, Oct 29, 2012 at 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] Accept Apache Streams as an Incubator Project
+1 (binding) Ralph On Nov 14, 2012, at 4:37 AM, Franklin, Matthew B. 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
