Re: [VOTE] Accept Provisionr into the Apache Incubator
+1 (binding) Sent from my Samsung Galaxy S3 Apologies for any typos On Mar 4, 2013 8:07 AM, kishore g g.kish...@gmail.com wrote: +1 (non-binding) Good luck On Sun, Mar 3, 2013 at 11:05 PM, Ashish paliwalash...@gmail.com wrote: +1 (non-binding) On Sun, Mar 3, 2013 at 5:05 AM, Andrei Savu as...@apache.org wrote: Hi Guys, I'd like to call a VOTE for acceptance of Provisionr into the Apache Incubator. The vote will close on March 8. [] +1 Accept Provisionr into the Apache incubator [] +0 Don't care. [] -1 Don't accept Provisionr into the incubator because... Full proposal is pasted at the bottom on this email, and the corresponding wiki is http://wiki.apache.org/incubator/ProvisionrProposal Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. Thanks, Andrei Savu -- Provisionr Proposal == Abstract == Provisionr is an effort to develop a service that can be used to create and manage pools of virtual machines on multiple clouds. Our focus is on semi-automated workflows and cloud portability. == Proposal == Provisionr solves the problem of cloud portability by hiding completely the APIs and only focusing on building a cluster that matches the same set of assumptions on all clouds, assumptions like: running a specific operating system (e.g. Ubuntu 12.04 LTS), having the same set of pre-installed packages and binaries, sane dns settings (forward reverse ip resolution - as needed for Hadoop), ntp settings, networking settings, firewall, ssh admin access, vpn access etc. As a secondary goal Provisionr should also provide primitives for building automatic or semi-automatic workflows for configuring services, workflows that assume that all the machines share a common set of characteristics as described above. == Background == Creating clusters on cloud infrastructure is non-trivial because careful orchestration is required. To make it easy to deploy services we need to start from a foundation that matches a common set of assumptions on multiple providers. == Rationale == This project started as a re-write of the core of Apache Whirr but has a different target being more focused on semi-automated workflows and cloud portability. == Initial Goals == * Build a community * Provide an excellent user experience for semi-automatic workflows (e.g. using Rundeck) * Implement a REST service and a Web Console * Add support for more providers == Current Status == Provisionr had four releases on [[ https://github.com/axemblr/axemblr-provisionr/wiki|GitHub]] and it's used to deploy Hadoop clusters on-demand at Axemblr and infrastructure for testing / QA. === Meritocracy === We plan to invest in supporting a meritocracy. We will discuss the requirements in an open forum. Several companies have already expressed interest in this project, and we intend to invite additional developers to participate. We will encourage and monitor community participation so that privileges can be extended to those that contribute. === Community === The community interested in cloud service infrastructure is currently spread across many smaller projects, and one of the main goals of this project is to build a vibrant community to share best practices and build common infrastructure. === Core developers === Core developers are very experienced in the Apache ecosystem. To achieve more diversity of developers, we will be eager to recruit developers from diverse companies. * Andrei Savu - asavu at apache dot org (Apache Whirr PMC) * Ioan Eugen Stan - ieugen at apache dot org (Apache James PMC) * Alex Ciminian - alex.ciminian at gmail dot org === Alignment === Provisionr complements Apache Whirr and later on it should provide a robust foundation for more advanced functionalities. == Known Risks == === Orphaned products === The contributors have significant open source experience and the project is being used as part of a commercial product, so the risk of being orphaned is relatively low. We plan to mitigate this risk by recruiting additional committers. === Inexperience with Open Source === Most of the initial committers have experience working on open source projects. Andrei Savu and Ioan Eugen Stan have experience as committers and PMC members on other Apache projects. === Homogenous Developers === We are committed to recruiting additional committers from other companies based on their contributions to the project. === Reliance on Salaried Developers === It is expected that Provisionr development will occur on both salaried time and on volunteer time, after hours. The majority
Re: [VOTE] Accept Provisionr into the Apache Incubator
On 03/02/2013 03:35 PM, Andrei Savu wrote: Hi Guys, I'd like to call a VOTE for acceptance of Provisionr into the Apache Incubator. The vote will close on March 8. [] +1 Accept Provisionr into the Apache incubator [] +0 Don't care. [] -1 Don't accept Provisionr into the incubator because... Full proposal is pasted at the bottom on this email, and the corresponding wiki is http://wiki.apache.org/incubator/ProvisionrProposal Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. Thanks, Andrei Savu +1 (non binding) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: No more existing-TLP graduations (was: [PROPOSAL] Curator for the Apache Incubator)
On Sat, Mar 2, 2013 at 2:08 AM, Daniel Shahaf d...@daniel.shahaf.name wrote: ...I suppose if a new product + its community want to become part of a PMC, coding could happen under that PMC (so for example: in a branch of their repository, releases require 3 +1's by that PMC), but with IPMC or comdev watching from the sidelines and helping if needed As Greg says, neither IPMC or comdev have staff, so watching from the sidelines is a very vague concept. OTOH, a PMC could very well ask individuals to sign up as community mentors temporarily (and probably recruit them here) to keep an eye on such things. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Provisionr into the Apache Incubator
On Sat, Mar 2, 2013 at 3:35 PM, Andrei Savu as...@apache.org wrote: I'd like to call a VOTE for acceptance of Provisionr into the Apache Incubator. +1 -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] MRQL for the Apache Incubator
On Sat, Mar 2, 2013 at 7:12 AM, Leonidas Fegaras fega...@cse.uta.edu wrote: == Champion == * Edward J. Yoon edwardyoon AT apache DOT org == Nominated Mentors == * Alex Karasulu akarasulu AT apache DOT org ... Is Edward going to stay on as a mentor as well? Two (active) mentors is the bare minimum IMO. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] MRQL for the Apache Incubator
On Mon, Mar 4, 2013 at 12:31 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Sat, Mar 2, 2013 at 7:12 AM, Leonidas Fegaras fega...@cse.uta.edu wrote: == Champion == * Edward J. Yoon edwardyoon AT apache DOT org == Nominated Mentors == * Alex Karasulu akarasulu AT apache DOT org ... Is Edward going to stay on as a mentor as well? Two (active) mentors is the bare minimum IMO. I suspect so but let's hear from Edward himself. Best Regards, -- Alex
Re: [PROPOSAL] MRQL for the Apache Incubator
Sure I can. :) Of course, we'll welcome more mentors from incubator IPMC if there're volunteers. On Mon, Mar 4, 2013 at 7:34 PM, Alex Karasulu akaras...@apache.org wrote: On Mon, Mar 4, 2013 at 12:31 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Sat, Mar 2, 2013 at 7:12 AM, Leonidas Fegaras fega...@cse.uta.edu wrote: == Champion == * Edward J. Yoon edwardyoon AT apache DOT org == Nominated Mentors == * Alex Karasulu akarasulu AT apache DOT org ... Is Edward going to stay on as a mentor as well? Two (active) mentors is the bare minimum IMO. I suspect so but let's hear from Edward himself. Best Regards, -- Alex -- 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
Patches from contributors: missing ASF license inclusion?
Hi, In the S4 project we have some recent patches from non-committers, but we have doubts on how to integrate them. In the past, the Jira system had a clearly defined way for the contributor to mark the patch as granted to the ASF. Typically (wording from the hbase book): The patch should be attached to the associated Jira ticket More Actions - Attach Files. Make sure you click the ASF license inclusion, otherwise the patch can't be considered for inclusion. Unfortunately it seems that with the latest Jira updates, this option is not available anymore to contributors. So, now, what is the proper way to ensure a patch can be included in the codebase of an Apache (incubator) project? Do we need contributors, even casual ones, to file an ICLA? Thanks for any clarification! Matthieu - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Patches from contributors: missing ASF license inclusion?
Hi On Mon, Mar 4, 2013 at 12:19 PM, Matthieu Morel mmo...@apache.org wrote: Hi, In the S4 project we have some recent patches from non-committers, but we have doubts on how to integrate them. In the past, the Jira system had a clearly defined way for the contributor to mark the patch as granted to the ASF. Typically (wording from the hbase book): The patch should be attached to the associated Jira ticket More Actions - Attach Files. Make sure you click the ASF license inclusion, otherwise the patch can't be considered for inclusion. Unfortunately it seems that with the latest Jira updates, this option is not available anymore to contributors. So, now, what is the proper way to ensure a patch can be included in the codebase of an Apache (incubator) project? Do we need contributors, even casual ones, to file an ICLA? I believe that should be the way. The positive side is that it will be one step less when they are recommended as committers in the future :) Thanks for any clarification! Matthieu - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Incubator PMC/Board report for Mar 2013 ([ppmc])
Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 20 March 2013, 10:30:00:00 PST. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, Mar 6th). Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/March2013 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Incubator PMC/Board report for Mar 2013 ([ppmc])
Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 20 March 2013, 10:30:00:00 PST. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, Mar 6th). Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/March2013 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] MRQL for the Apache Incubator
Nice proposal indeed, I'd say having 3 mentors is usually better to avoid release headaches. Regards, Tommaso 2013/3/4 Edward J. Yoon edwardy...@apache.org Sure I can. :) Of course, we'll welcome more mentors from incubator IPMC if there're volunteers. On Mon, Mar 4, 2013 at 7:34 PM, Alex Karasulu akaras...@apache.org wrote: On Mon, Mar 4, 2013 at 12:31 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Sat, Mar 2, 2013 at 7:12 AM, Leonidas Fegaras fega...@cse.uta.edu wrote: == Champion == * Edward J. Yoon edwardyoon AT apache DOT org == Nominated Mentors == * Alex Karasulu akarasulu AT apache DOT org ... Is Edward going to stay on as a mentor as well? Two (active) mentors is the bare minimum IMO. I suspect so but let's hear from Edward himself. Best Regards, -- Alex -- 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
[jira] [Resolved] (PODLINGNAMESEARCH-22) Establish whether Apache Bloodhound is a suitable name
[ https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Martin resolved PODLINGNAMESEARCH-22. -- Resolution: Fixed Establish whether Apache Bloodhound is a suitable name - Key: PODLINGNAMESEARCH-22 URL: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-22 Project: Podling Suitable Names Search Issue Type: Suitable Name Search Reporter: Gary Martin A suitable name search is required in order for Bloodhound to graduate from incubation. The bloodhound is a breed of dog with a strong tracking instinct. Bloodhound as an Apache incubator project is an issue tracker. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (PODLINGNAMESEARCH-22) Establish whether Apache Bloodhound is a suitable name
[ https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13592158#comment-13592158 ] Gary Martin commented on PODLINGNAMESEARCH-22: -- After guidance from trademarks@ in interpreting the results, the Bloodhound PPMC has decided to continue with the name Bloodhound. Establish whether Apache Bloodhound is a suitable name - Key: PODLINGNAMESEARCH-22 URL: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-22 Project: Podling Suitable Names Search Issue Type: Suitable Name Search Reporter: Gary Martin A suitable name search is required in order for Bloodhound to graduate from incubation. The bloodhound is a breed of dog with a strong tracking instinct. Bloodhound as an Apache incubator project is an issue tracker. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Patches from contributors: missing ASF license inclusion?
Usual IANAL clause, but, reading the AL2.0 itself, it says: Contribution shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, submitted means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as Not a Contribution. By *using* Apache licensed software, you are agreeing to these terms. Therefore, by submitting code to an ASF system (JIRA, mailing list, whatever) and not explicitly stating Not a Contribution, your code can be taken by the project to be an implicit contribution under the terms of the Apache License that you agreed to when you started using the code. Of course, for anything substantive, we'll want an ICLA to add a further of provenance guarantee, but for smaller fixes, the above should, as I understand it, be sufficient. That is my understanding of the discussion that happened around the time when the JIRA tick-box was removed: it isn't needed. Upayavira On Mon, Mar 4, 2013, at 12:13 PM, Mohammad Nour El-Din wrote: Hi On Mon, Mar 4, 2013 at 12:19 PM, Matthieu Morel mmo...@apache.org wrote: Hi, In the S4 project we have some recent patches from non-committers, but we have doubts on how to integrate them. In the past, the Jira system had a clearly defined way for the contributor to mark the patch as granted to the ASF. Typically (wording from the hbase book): The patch should be attached to the associated Jira ticket More Actions - Attach Files. Make sure you click the ASF license inclusion, otherwise the patch can't be considered for inclusion. Unfortunately it seems that with the latest Jira updates, this option is not available anymore to contributors. So, now, what is the proper way to ensure a patch can be included in the codebase of an Apache (incubator) project? Do we need contributors, even casual ones, to file an ICLA? I believe that should be the way. The positive side is that it will be one step less when they are recommended as committers in the future :) Thanks for any clarification! Matthieu - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Patches from contributors: missing ASF license inclusion?
You DO NOT NEED AN ICLA from these people. Under the terms of the AL, any contribution made back to the ASF on ASF infrastructure, such as via a mailing list, JIRA, or Bugzilla, is licensed to the foundation. The JIRA checkbox existed to give people an easy way to _avoid_ contributing something. There is no need to ask casual patchers for ICLAs. On Mon, Mar 4, 2013 at 3:19 AM, Matthieu Morel mmo...@apache.org wrote: Hi, In the S4 project we have some recent patches from non-committers, but we have doubts on how to integrate them. In the past, the Jira system had a clearly defined way for the contributor to mark the patch as granted to the ASF. Typically (wording from the hbase book): The patch should be attached to the associated Jira ticket More Actions - Attach Files. Make sure you click the ASF license inclusion, otherwise the patch can't be considered for inclusion. Unfortunately it seems that with the latest Jira updates, this option is not available anymore to contributors. So, now, what is the proper way to ensure a patch can be included in the codebase of an Apache (incubator) project? Do we need contributors, even casual ones, to file an ICLA? Thanks for any clarification! Matthieu - 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: Patches from contributors: missing ASF license inclusion?
On Mon, Mar 4, 2013 at 5:42 AM, Benson Margulies bimargul...@gmail.com wrote: You DO NOT NEED AN ICLA from these people. Under the terms of the AL, any contribution made back to the ASF on ASF infrastructure, such as via a mailing list, JIRA, or Bugzilla, is licensed to the foundation. The JIRA checkbox existed to give people an easy way to _avoid_ contributing something. There is no need to ask casual patchers for ICLAs. +1 Here's Roy: http://s.apache.org/roy-on-contributions-and-git Yes, that opinion comes from me speaking as a board member and author of the Apache License, and has previously been cleared with Apache's legal team for a long ago discussion with Incubator. We don't need a CLA on file to accept contributions from non-committers. We just need a clear intent by the author to contribute under our normal terms. ... We have archives on all of our communication channels. We don't need the silly checkbox. We never have. ... ... The authors do not need to have a CLA on file even if the contribution is massive -- CLAs are only required for the people who want an account at Apache and thus are allowed to make the decision to push those bits into our repository. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Patches from contributors: missing ASF license inclusion?
This is clear now, there is no room for doubt. Thanks ! Matthieu On Mar 4, 2013, at 14:42 , Benson Margulies wrote: You DO NOT NEED AN ICLA from these people. Under the terms of the AL, any contribution made back to the ASF on ASF infrastructure, such as via a mailing list, JIRA, or Bugzilla, is licensed to the foundation. The JIRA checkbox existed to give people an easy way to _avoid_ contributing something. There is no need to ask casual patchers for ICLAs. On Mon, Mar 4, 2013 at 3:19 AM, Matthieu Morel mmo...@apache.org wrote: Hi, In the S4 project we have some recent patches from non-committers, but we have doubts on how to integrate them. In the past, the Jira system had a clearly defined way for the contributor to mark the patch as granted to the ASF. Typically (wording from the hbase book): The patch should be attached to the associated Jira ticket More Actions - Attach Files. Make sure you click the ASF license inclusion, otherwise the patch can't be considered for inclusion. Unfortunately it seems that with the latest Jira updates, this option is not available anymore to contributors. So, now, what is the proper way to ensure a patch can be included in the codebase of an Apache (incubator) project? Do we need contributors, even casual ones, to file an ICLA? Thanks for any clarification! Matthieu - 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: Patches from contributors: missing ASF license inclusion?
Sorry about my false answer then, I take it back On Mon, Mar 4, 2013 at 3:01 PM, Matthieu Morel mmo...@apache.org wrote: This is clear now, there is no room for doubt. Thanks ! Matthieu On Mar 4, 2013, at 14:42 , Benson Margulies wrote: You DO NOT NEED AN ICLA from these people. Under the terms of the AL, any contribution made back to the ASF on ASF infrastructure, such as via a mailing list, JIRA, or Bugzilla, is licensed to the foundation. The JIRA checkbox existed to give people an easy way to _avoid_ contributing something. There is no need to ask casual patchers for ICLAs. On Mon, Mar 4, 2013 at 3:19 AM, Matthieu Morel mmo...@apache.org wrote: Hi, In the S4 project we have some recent patches from non-committers, but we have doubts on how to integrate them. In the past, the Jira system had a clearly defined way for the contributor to mark the patch as granted to the ASF. Typically (wording from the hbase book): The patch should be attached to the associated Jira ticket More Actions - Attach Files. Make sure you click the ASF license inclusion, otherwise the patch can't be considered for inclusion. Unfortunately it seems that with the latest Jira updates, this option is not available anymore to contributors. So, now, what is the proper way to ensure a patch can be included in the codebase of an Apache (incubator) project? Do we need contributors, even casual ones, to file an ICLA? Thanks for any clarification! Matthieu - 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 -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: [VOTE] Accept Provisionr into the Apache Incubator
+1 Tommaso 2013/3/4 Olivier Lamy ol...@apache.org +1 2013/3/3 Andrei Savu as...@apache.org: Hi Guys, I'd like to call a VOTE for acceptance of Provisionr into the Apache Incubator. The vote will close on March 8. [] +1 Accept Provisionr into the Apache incubator [] +0 Don't care. [] -1 Don't accept Provisionr into the incubator because... Full proposal is pasted at the bottom on this email, and the corresponding wiki is http://wiki.apache.org/incubator/ProvisionrProposal Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. Thanks, Andrei Savu -- Provisionr Proposal == Abstract == Provisionr is an effort to develop a service that can be used to create and manage pools of virtual machines on multiple clouds. Our focus is on semi-automated workflows and cloud portability. == Proposal == Provisionr solves the problem of cloud portability by hiding completely the APIs and only focusing on building a cluster that matches the same set of assumptions on all clouds, assumptions like: running a specific operating system (e.g. Ubuntu 12.04 LTS), having the same set of pre-installed packages and binaries, sane dns settings (forward reverse ip resolution - as needed for Hadoop), ntp settings, networking settings, firewall, ssh admin access, vpn access etc. As a secondary goal Provisionr should also provide primitives for building automatic or semi-automatic workflows for configuring services, workflows that assume that all the machines share a common set of characteristics as described above. == Background == Creating clusters on cloud infrastructure is non-trivial because careful orchestration is required. To make it easy to deploy services we need to start from a foundation that matches a common set of assumptions on multiple providers. == Rationale == This project started as a re-write of the core of Apache Whirr but has a different target being more focused on semi-automated workflows and cloud portability. == Initial Goals == * Build a community * Provide an excellent user experience for semi-automatic workflows (e.g. using Rundeck) * Implement a REST service and a Web Console * Add support for more providers == Current Status == Provisionr had four releases on [[ https://github.com/axemblr/axemblr-provisionr/wiki|GitHub]] and it's used to deploy Hadoop clusters on-demand at Axemblr and infrastructure for testing / QA. === Meritocracy === We plan to invest in supporting a meritocracy. We will discuss the requirements in an open forum. Several companies have already expressed interest in this project, and we intend to invite additional developers to participate. We will encourage and monitor community participation so that privileges can be extended to those that contribute. === Community === The community interested in cloud service infrastructure is currently spread across many smaller projects, and one of the main goals of this project is to build a vibrant community to share best practices and build common infrastructure. === Core developers === Core developers are very experienced in the Apache ecosystem. To achieve more diversity of developers, we will be eager to recruit developers from diverse companies. * Andrei Savu - asavu at apache dot org (Apache Whirr PMC) * Ioan Eugen Stan - ieugen at apache dot org (Apache James PMC) * Alex Ciminian - alex.ciminian at gmail dot org === Alignment === Provisionr complements Apache Whirr and later on it should provide a robust foundation for more advanced functionalities. == Known Risks == === Orphaned products === The contributors have significant open source experience and the project is being used as part of a commercial product, so the risk of being orphaned is relatively low. We plan to mitigate this risk by recruiting additional committers. === Inexperience with Open Source === Most of the initial committers have experience working on open source projects. Andrei Savu and Ioan Eugen Stan have experience as committers and PMC members on other Apache projects. === Homogenous Developers === We are committed to recruiting additional committers from other companies based on their contributions to the project. === Reliance on Salaried Developers === It is expected that Provisionr development will occur on both salaried time and on volunteer time, after hours. The majority of initial committers are paid by their employer to contribute to this project. However, they are all passionate about the project, and we are confident that the project will continue even if no salaried developers contribute to the project. We are committed to recruiting additional committers including non-salaried developers. === Relationships with Other
Re: Would you please give me a write access to http://wiki.apache.org/incubator ?
Thanks Daniel, I made it a link using '[[' and ']]'. Thanks! Cheers, Chris On 2/27/13 3:40 PM, Daniel Shahaf d...@daniel.shahaf.name wrote: I think you need to edit ContributorsGroup to make the [[username a link]] Mattmann, Chris A (388J) wrote on Wed, Feb 27, 2013 at 23:06:44 +: Hi there Joe, I went ahead and granted karma. Please let me know if it works. It might not since there are spaces in your wiki username, so if it doesn't work let me know. Cheers, Chris On 2/27/13 3:04 PM, H. Joe Lee hyok...@hdfgroup.org wrote: Hi, I'd like to work on an incubation proposal through wiki. Would you please give me a write access? My wiki user name is H. Joe Lee. Thanks, -- HDF: Software that Powers Science - 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] Accept Tajo into the Apache Incubator
+1 (binding) from me. Cheers, Chris On 2/28/13 10:11 AM, Hyunsik Choi hyun...@apache.org wrote: Hi Folks, I'd like to call a VOTE for acceptance of Tajo into the Apache incubator. The vote will close on Mar 7 at 6:00 PM (PST). [] +1 Accept Tajo into the Apache incubator [] +0 Don't care. [] -1 Don't accept Tajo into the incubator because... Full proposal is pasted at the bottom on this email, and the corresponding wiki is http://wiki.apache.org/incubator/TajoProposal. Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. Thanks, Hyunsik PS: From the initial discussion, the main changes are that I've added 4 new committers. Also, I've revised some description of Known Risks because the initial committers have been diverse. Tajo Proposal = Abstract = Tajo is a distributed data warehouse system for Hadoop. = Proposal = Tajo is a relational and distributed data warehouse system for Hadoop. Tajo is designed for low-latency and scalable ad-hoc queries, online aggregation and ETL on large-data sets by leveraging advanced database techniques. It supports SQL standards. Tajo is inspired by Dryad, MapReduce, Dremel, Scope, and parallel databases. Tajo uses HDFS as a primary storage layer, and it has its own query engine which allows direct control of distributed execution and data flow. As a result, Tajo has a variety of query evaluation strategies and more optimization opportunities. In addition, Tajo will have a native columnar execution and and its optimizer. Tajo will be an alternative choice to Hive/Pig on the top of MapReduce. = Background = Big data analysis has gained much attention in the industrial. Open source communities have proposed scalable and distributed solutions for ad-hoc queries on big data. However, there is still room for improvement. Markets need more faster and efficient solutions. Recently, some alternatives (e.g., Cloudera's Impala and Amazon Redshift) have come out. = Rationale = There are a variety of open source distributed execution engines (e.g., hive, and pig) running on the top of MapReduce. They are limited by MR framework. They cannot directly control distributed execution and data flow, and they just use MR framework. So, they have limited query evaluation strategies and optimization opportunities. It is hard for them to be optimized for a certain type of data processing. = Initial Goals = The initial goal is to write more documents to describe Tajo's internal. It will be helpful to recruit more committers and to build a solid community. Then, we will make milestones for short/long term plans. = Current Status = Tajo is in the alpha stage. Users can execute usual SQL queries (e.g., selection, projection, group-by, join, union and sort) except for nested queries. Tajo provides various row/column storage formats, such as CSV, RowFile (a row-store file we have implemented), RCFile, and Trevni, and it also has a rudimentary ETL feature to transform one data format to another data format. In addition, Tajo provides hash and range repartitions. By using both repartition methods, Tajo processes aggregation, join, and sort queries over a number of cluster nodes. To evaluate the performance, we have carried out benchmark test using TPC-H 1TB on 32 cluster nodes. == Meritocracy == We will discuss the milestone and the future plan in an open forum. We plan to encourage an environment that supports a meritocracy. The contributors will have different privileges according to their contributions. == Community == Big data analysis has gained attention from open source communities, industrial and academic areas. Some projects related to Hadoop already have very large and active communities. We expect that Tajo also will establish an active community. Since Tajo already works for some features and is in the alpha stage, it will attract a large community soon. == Core Developers == Core developers are a diverse group of developers, many of which are very experienced in open source and the Apache Hadoop ecosystem. * Eli Reisman ereisman AT apache DOT org * Henry Saputra hsaputra AT apache DOT org * Hyunsik Choi hyunsik AT apache DOT org * Jae Hwa Jung jhjung AT gruter DOT com * Jihoon Son ghoonson AT gmail DOT com * Jin Ho Kim jhkim AT gruter DOT com * Roshan Sumbaly rsumbaly AT gmail DOT com * Sangwook Kim swkim AT inervit DOT com * Yi A Liu yi DOT a DOT liu AT intel DOT com == Alignment == Tajo employs Apache Hadoop Yarn as a resource management platform for large clusters. It uses HDFS as a primary storage layer. It already supports Hadoop-related data formats (RCFile, Trevni) and will support ORC file. In addition, we have a plan to integrate Tajo with other products of Hadoop ecosystem. Tajo's modules are well organized, and these modules can also be used for other projects. = Known Risks = == Orphaned Products == Most of codes have been developed by only two core
Re: [VOTE] Release Apache Mesos 0.10.0-incubating (RC4)
Hi Ben, +1 Worked for me see below. balrog:~ pramirez$ wget http://people.apache.org/~benh/mesos-0.10.0-incubating-RC4/mesos-0.10.0-inc ubating.tar.gz ... 2013-03-04 09:19:41 (3.14 MB/s) - `mesos-0.10.0-incubating.tar.gz' saved [26184035/26184035] balrog:~ pramirez$ wget http://people.apache.org/~benh/mesos-0.10.0-incubating-RC4/mesos-0.10.0-inc ubating.tar.gz.md5 ... 2013-03-04 09:20:01 (4.83 MB/s) - `mesos-0.10.0-incubating.tar.gz.md5' saved [81/81] balrog:~ pramirez$ wget http://people.apache.org/~benh/mesos-0.10.0-incubating-RC4/mesos-0.10.0-inc ubating.tar.gz.asc ... 2013-03-04 09:20:20 (95.9 KB/s) - `mesos-0.10.0-incubating.tar.gz.asc' saved [881/881] balrog:~ pramirez$ md5 mesos-0.10.0-incubating.tar.gz MD5 (mesos-0.10.0-incubating.tar.gz) = 6aa70e04902d4f27d30f74a142206dd4 balrog:~ pramirez$ more mesos-0.10.0-incubating.tar.gz.md5 mesos-0.10.0-incubating.tar.gz: 6A A7 0E 04 90 2D 4F 27 D3 0F 74 A1 42 20 6D D4 balrog:~ pramirez$ wget http://svn.apache.org/repos/asf/incubator/mesos/dist/KEYS ... 2013-03-04 09:23:52 (218 KB/s) - `KEYS' saved [7192/7192] balrog:~ pramirez$ gpg --import KEYS gpg: key F6FB762C: public key Benjamin Hindman b...@apache.org imported gpg: key 1B207A4D: public key Andy Konwinski (CODE SIGNING KEY) and...@apache.org imported gpg: Total number processed: 2 gpg: imported: 2 (RSA: 2) balrog:~ pramirez$ gpg --verify mesos-0.10.0-incubating.tar.gz.asc gpg: Signature made Thu Feb 7 22:22:30 2013 PST using RSA key ID F6FB762C gpg: Good signature from Benjamin Hindman b...@apache.org gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: 4BF2 061E 7300 3185 CA06 E30F F99D 6AD0 F6FB 762C balrog:~ pramirez$ tar xzvf mesos-0.10.0-incubating.tar.gz balrog:~ pramirez$ cd mesos-0.10.0 balrog:mesos-0.10.0 pramirez$ ./configure --disable-java ... configure: creating ./config.status config.status: creating Makefile config.status: creating third_party/Makefile config.status: executing depfiles commands config.status: executing libtool commands balrog:mesos-0.10.0 pramirez$ make cd . /bin/sh ./config.status src/java/mesos.pom config.status: creating src/java/mesos.pom Making all in . ... Long interlude while mesos builds to _success_ ... Then a drumroll ... copying src/mesos.egg-info/PKG-INFO - build/bdist.macosx-10.6-universal/egg/EGG-INFO copying src/mesos.egg-info/SOURCES.txt - build/bdist.macosx-10.6-universal/egg/EGG-INFO copying src/mesos.egg-info/dependency_links.txt - build/bdist.macosx-10.6-universal/egg/EGG-INFO copying src/mesos.egg-info/top_level.txt - build/bdist.macosx-10.6-universal/egg/EGG-INFO writing build/bdist.macosx-10.6-universal/egg/EGG-INFO/native_libs.txt zip_safe flag not set; analyzing archive contents... creating dist creating 'dist/mesos-0.10.0-py2.6-macosx-10.6-universal.egg' and adding 'build/bdist.macosx-10.6-universal/egg' to it removing 'build/bdist.macosx-10.6-universal/egg' (and everything under it) Making all in ec2 make[1]: Nothing to be done for `all'. Making all in hadoop make[1]: Nothing to be done for `all'. Thanks, Paul Ramirez On 2/7/13 10:32 PM, Benjamin Hindman b...@berkeley.edu wrote: Please vote on releasing the following candidate as Apache Mesos (incubating) version 0.10.0. This will be the second incubator release for Mesos in Apache. -- --- Changes since last release candidate: * Updated configure.ac to work better on OS X 10.8. * Added missing license (the only blocker on the previous candidate). -- --- The candidate for Mesos 0.10.0-incubating release is available at: http://people.apache.org/~benh/mesos-0.10.0-incubating-RC4/mesos-0.10.0-in cubating.tar.gz The tag to be voted on: https://svn.apache.org/repos/asf/incubator/mesos/tags/release-0.10.0-incub ating-RC4 The MD5 checksum of the tarball can be found at: http://people.apache.org/~benh/mesos-0.10.0-incubating-RC4/mesos-0.10.0-in cubating.tar.gz.md5 The signature of the tarball can be found at: http://people.apache.org/~benh/mesos-0.10.0-incubating-RC4/mesos-0.10.0-in cubating.tar.gz.asc Mesos' KEYS file, containing the PGP keys used to sign the release: http://svn.apache.org/repos/asf/incubator/mesos/dist/KEYS Please vote on releasing this package as Apache Mesos 0.10.0-incubating! The vote is open until Monday, February 11th at 5:00 pm (PST) and passes if a majority of at least 3 +1 IPMC votes are cast. [ ] +1 Release this package as Apache Mesos 0.10.0-incubating [ ] -1 Do not release this package because ... To learn more about Apache Mesos, please see http://www.mesosproject.org. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail:
Re: [VOTE] Accept Provisionr into the Apache Incubator
+1 Tom On Sat, Mar 2, 2013 at 11:35 PM, Andrei Savu as...@apache.org wrote: Hi Guys, I'd like to call a VOTE for acceptance of Provisionr into the Apache Incubator. The vote will close on March 8. [] +1 Accept Provisionr into the Apache incubator [] +0 Don't care. [] -1 Don't accept Provisionr into the incubator because... Full proposal is pasted at the bottom on this email, and the corresponding wiki is http://wiki.apache.org/incubator/ProvisionrProposal Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. Thanks, Andrei Savu -- Provisionr Proposal == Abstract == Provisionr is an effort to develop a service that can be used to create and manage pools of virtual machines on multiple clouds. Our focus is on semi-automated workflows and cloud portability. == Proposal == Provisionr solves the problem of cloud portability by hiding completely the APIs and only focusing on building a cluster that matches the same set of assumptions on all clouds, assumptions like: running a specific operating system (e.g. Ubuntu 12.04 LTS), having the same set of pre-installed packages and binaries, sane dns settings (forward reverse ip resolution - as needed for Hadoop), ntp settings, networking settings, firewall, ssh admin access, vpn access etc. As a secondary goal Provisionr should also provide primitives for building automatic or semi-automatic workflows for configuring services, workflows that assume that all the machines share a common set of characteristics as described above. == Background == Creating clusters on cloud infrastructure is non-trivial because careful orchestration is required. To make it easy to deploy services we need to start from a foundation that matches a common set of assumptions on multiple providers. == Rationale == This project started as a re-write of the core of Apache Whirr but has a different target being more focused on semi-automated workflows and cloud portability. == Initial Goals == * Build a community * Provide an excellent user experience for semi-automatic workflows (e.g. using Rundeck) * Implement a REST service and a Web Console * Add support for more providers == Current Status == Provisionr had four releases on [[ https://github.com/axemblr/axemblr-provisionr/wiki|GitHub]] and it's used to deploy Hadoop clusters on-demand at Axemblr and infrastructure for testing / QA. === Meritocracy === We plan to invest in supporting a meritocracy. We will discuss the requirements in an open forum. Several companies have already expressed interest in this project, and we intend to invite additional developers to participate. We will encourage and monitor community participation so that privileges can be extended to those that contribute. === Community === The community interested in cloud service infrastructure is currently spread across many smaller projects, and one of the main goals of this project is to build a vibrant community to share best practices and build common infrastructure. === Core developers === Core developers are very experienced in the Apache ecosystem. To achieve more diversity of developers, we will be eager to recruit developers from diverse companies. * Andrei Savu - asavu at apache dot org (Apache Whirr PMC) * Ioan Eugen Stan - ieugen at apache dot org (Apache James PMC) * Alex Ciminian - alex.ciminian at gmail dot org === Alignment === Provisionr complements Apache Whirr and later on it should provide a robust foundation for more advanced functionalities. == Known Risks == === Orphaned products === The contributors have significant open source experience and the project is being used as part of a commercial product, so the risk of being orphaned is relatively low. We plan to mitigate this risk by recruiting additional committers. === Inexperience with Open Source === Most of the initial committers have experience working on open source projects. Andrei Savu and Ioan Eugen Stan have experience as committers and PMC members on other Apache projects. === Homogenous Developers === We are committed to recruiting additional committers from other companies based on their contributions to the project. === Reliance on Salaried Developers === It is expected that Provisionr development will occur on both salaried time and on volunteer time, after hours. The majority of initial committers are paid by their employer to contribute to this project. However, they are all passionate about the project, and we are confident that the project will continue even if no salaried developers contribute to the project. We are committed to recruiting additional committers including non-salaried developers. === Relationships with Other Apache Products === Provisionr is closely integrated with CloudStack, Karaf, CXF, BigTop in a numerous ways. We look forward to collaborating with those communities,
Re: [VOTE] Accept Provisionr into the Apache Incubator
+1 - binding Regards, Alan On Mar 2, 2013, at 3:35 PM, Andrei Savu wrote: Hi Guys, I'd like to call a VOTE for acceptance of Provisionr into the Apache Incubator. The vote will close on March 8. [] +1 Accept Provisionr into the Apache incubator [] +0 Don't care. [] -1 Don't accept Provisionr into the incubator because... Full proposal is pasted at the bottom on this email, and the corresponding wiki is http://wiki.apache.org/incubator/ProvisionrProposal Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. Thanks, Andrei Savu -- Provisionr Proposal == Abstract == Provisionr is an effort to develop a service that can be used to create and manage pools of virtual machines on multiple clouds. Our focus is on semi-automated workflows and cloud portability. == Proposal == Provisionr solves the problem of cloud portability by hiding completely the APIs and only focusing on building a cluster that matches the same set of assumptions on all clouds, assumptions like: running a specific operating system (e.g. Ubuntu 12.04 LTS), having the same set of pre-installed packages and binaries, sane dns settings (forward reverse ip resolution - as needed for Hadoop), ntp settings, networking settings, firewall, ssh admin access, vpn access etc. As a secondary goal Provisionr should also provide primitives for building automatic or semi-automatic workflows for configuring services, workflows that assume that all the machines share a common set of characteristics as described above. == Background == Creating clusters on cloud infrastructure is non-trivial because careful orchestration is required. To make it easy to deploy services we need to start from a foundation that matches a common set of assumptions on multiple providers. == Rationale == This project started as a re-write of the core of Apache Whirr but has a different target being more focused on semi-automated workflows and cloud portability. == Initial Goals == * Build a community * Provide an excellent user experience for semi-automatic workflows (e.g. using Rundeck) * Implement a REST service and a Web Console * Add support for more providers == Current Status == Provisionr had four releases on [[ https://github.com/axemblr/axemblr-provisionr/wiki|GitHub]] and it's used to deploy Hadoop clusters on-demand at Axemblr and infrastructure for testing / QA. === Meritocracy === We plan to invest in supporting a meritocracy. We will discuss the requirements in an open forum. Several companies have already expressed interest in this project, and we intend to invite additional developers to participate. We will encourage and monitor community participation so that privileges can be extended to those that contribute. === Community === The community interested in cloud service infrastructure is currently spread across many smaller projects, and one of the main goals of this project is to build a vibrant community to share best practices and build common infrastructure. === Core developers === Core developers are very experienced in the Apache ecosystem. To achieve more diversity of developers, we will be eager to recruit developers from diverse companies. * Andrei Savu - asavu at apache dot org (Apache Whirr PMC) * Ioan Eugen Stan - ieugen at apache dot org (Apache James PMC) * Alex Ciminian - alex.ciminian at gmail dot org === Alignment === Provisionr complements Apache Whirr and later on it should provide a robust foundation for more advanced functionalities. == Known Risks == === Orphaned products === The contributors have significant open source experience and the project is being used as part of a commercial product, so the risk of being orphaned is relatively low. We plan to mitigate this risk by recruiting additional committers. === Inexperience with Open Source === Most of the initial committers have experience working on open source projects. Andrei Savu and Ioan Eugen Stan have experience as committers and PMC members on other Apache projects. === Homogenous Developers === We are committed to recruiting additional committers from other companies based on their contributions to the project. === Reliance on Salaried Developers === It is expected that Provisionr development will occur on both salaried time and on volunteer time, after hours. The majority of initial committers are paid by their employer to contribute to this project. However, they are all passionate about the project, and we are confident that the project will continue even if no salaried developers contribute to the project. We are committed to recruiting additional committers including non-salaried developers. === Relationships with Other Apache Products === Provisionr is closely integrated with CloudStack, Karaf, CXF, BigTop in a numerous ways. We look forward to
Re: [PROPOSAL] Curator for the Apache Incubator
The discussion on this seems to have finished. Is now a good time to ask for a vote? -Jordan On Mar 1, 2013, at 4:00 AM, Jordan Zimmerman jzimmer...@netflix.com wrote: http://www.mail-archive.com/general@incubator.apache.org/msg38991.html Jordan Zimmerman - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Provisionr into the Apache Incubator
+1 non-binding Good luck On Sat, Mar 2, 2013 at 3:35 PM, Andrei Savu as...@apache.org wrote: Hi Guys, I'd like to call a VOTE for acceptance of Provisionr into the Apache Incubator. The vote will close on March 8. [] +1 Accept Provisionr into the Apache incubator [] +0 Don't care. [] -1 Don't accept Provisionr into the incubator because... Full proposal is pasted at the bottom on this email, and the corresponding wiki is http://wiki.apache.org/incubator/ProvisionrProposal Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. Thanks, Andrei Savu -- Provisionr Proposal == Abstract == Provisionr is an effort to develop a service that can be used to create and manage pools of virtual machines on multiple clouds. Our focus is on semi-automated workflows and cloud portability. == Proposal == Provisionr solves the problem of cloud portability by hiding completely the APIs and only focusing on building a cluster that matches the same set of assumptions on all clouds, assumptions like: running a specific operating system (e.g. Ubuntu 12.04 LTS), having the same set of pre-installed packages and binaries, sane dns settings (forward reverse ip resolution - as needed for Hadoop), ntp settings, networking settings, firewall, ssh admin access, vpn access etc. As a secondary goal Provisionr should also provide primitives for building automatic or semi-automatic workflows for configuring services, workflows that assume that all the machines share a common set of characteristics as described above. == Background == Creating clusters on cloud infrastructure is non-trivial because careful orchestration is required. To make it easy to deploy services we need to start from a foundation that matches a common set of assumptions on multiple providers. == Rationale == This project started as a re-write of the core of Apache Whirr but has a different target being more focused on semi-automated workflows and cloud portability. == Initial Goals == * Build a community * Provide an excellent user experience for semi-automatic workflows (e.g. using Rundeck) * Implement a REST service and a Web Console * Add support for more providers == Current Status == Provisionr had four releases on [[ https://github.com/axemblr/axemblr-provisionr/wiki|GitHub]] and it's used to deploy Hadoop clusters on-demand at Axemblr and infrastructure for testing / QA. === Meritocracy === We plan to invest in supporting a meritocracy. We will discuss the requirements in an open forum. Several companies have already expressed interest in this project, and we intend to invite additional developers to participate. We will encourage and monitor community participation so that privileges can be extended to those that contribute. === Community === The community interested in cloud service infrastructure is currently spread across many smaller projects, and one of the main goals of this project is to build a vibrant community to share best practices and build common infrastructure. === Core developers === Core developers are very experienced in the Apache ecosystem. To achieve more diversity of developers, we will be eager to recruit developers from diverse companies. * Andrei Savu - asavu at apache dot org (Apache Whirr PMC) * Ioan Eugen Stan - ieugen at apache dot org (Apache James PMC) * Alex Ciminian - alex.ciminian at gmail dot org === Alignment === Provisionr complements Apache Whirr and later on it should provide a robust foundation for more advanced functionalities. == Known Risks == === Orphaned products === The contributors have significant open source experience and the project is being used as part of a commercial product, so the risk of being orphaned is relatively low. We plan to mitigate this risk by recruiting additional committers. === Inexperience with Open Source === Most of the initial committers have experience working on open source projects. Andrei Savu and Ioan Eugen Stan have experience as committers and PMC members on other Apache projects. === Homogenous Developers === We are committed to recruiting additional committers from other companies based on their contributions to the project. === Reliance on Salaried Developers === It is expected that Provisionr development will occur on both salaried time and on volunteer time, after hours. The majority of initial committers are paid by their employer to contribute to this project. However, they are all passionate about the project, and we are confident that the project will continue even if no salaried developers contribute to the project. We are committed to recruiting additional committers including non-salaried developers. === Relationships with Other Apache Products === Provisionr is closely integrated with CloudStack, Karaf, CXF, BigTop in a numerous ways. We look forward to collaborating with
Fwd: Incubator PMC/Board report for Mar 2013 ([ppmc])
Hey Folks, Etch has graduated and is now a TLP, correct? It's board reports should now go directly to board@ from the PMC chair. Regards, Dave Begin forwarded message: From: Marvin no-re...@apache.org Date: March 4, 2013 4:18:48 AM PST To: d...@etch.incubator.apache.org Subject: Incubator PMC/Board report for Mar 2013 ([ppmc]) Reply-To: d...@etch.apache.org delivered-to: mailing list d...@etch.apache.org delivered-to: moderator for d...@etch.apache.org Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 20 March 2013, 10:30:00:00 PST. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, Mar 6th). Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/March2013 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Incubator PMC/Board report for Mar 2013 ([ppmc])
Has the procedure been followed to update the metadata to reflect the graduation? On Mon, Mar 4, 2013 at 2:40 PM, Dave Fisher dave2w...@comcast.net wrote: Hey Folks, Etch has graduated and is now a TLP, correct? It's board reports should now go directly to board@ from the PMC chair. Regards, Dave Begin forwarded message: From: Marvin no-re...@apache.org Date: March 4, 2013 4:18:48 AM PST To: d...@etch.incubator.apache.org Subject: Incubator PMC/Board report for Mar 2013 ([ppmc]) Reply-To: d...@etch.apache.org delivered-to: mailing list d...@etch.apache.org delivered-to: moderator for d...@etch.apache.org Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 20 March 2013, 10:30:00:00 PST. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, Mar 6th). Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/March2013 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC - 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: Fwd: Incubator PMC/Board report for Mar 2013 ([ppmc])
Dave Fisher wrote: Hey Folks, Etch has graduated and is now a TLP, correct? It's board reports should now go directly to board@ from the PMC chair. As explained in the Incubator graduation docs, the Etch project needs to finalise their graduation steps. http://incubator.apache.org/clutch.html#etch http://incubator.apache.org/clutch.html#other http://incubator.apache.org/clutch.html#h-Graduate -David Regards, Dave Begin forwarded message: From: Marvin no-re...@apache.org Date: March 4, 2013 4:18:48 AM PST To: d...@etch.incubator.apache.org Subject: Incubator PMC/Board report for Mar 2013 ([ppmc]) Reply-To: d...@etch.apache.org delivered-to: mailing list d...@etch.apache.org delivered-to: moderator for d...@etch.apache.org Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 20 March 2013, 10:30:00:00 PST. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, Mar 6th). Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/March2013 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC - 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: Incubator PMC/Board report for Mar 2013 ([ppmc])
These are for the new podlings Knox and Tez. The system has not yet detected that their mail lists are established. so the default is to general@ -David Marvin wrote: Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 20 March 2013, 10:30:00:00 PST. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, Mar 6th). Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/March2013 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC - 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
Markdown issue
Hi all, probably is a dumb issue and I'm missing something obvious, but so far, I haven't been able to solve it: Is there an easy way to tell a markdown link to use a specific css class? I'd like to render links pointing outside the incubator site with an external css class. I know I can write the html equivalent, but that feels unnatural, so I'd better avoid that option. I've been poking at a few site's sources, but haven't had any luck yet.. thx in advance! br, juan pablo
Re: [VOTE] Accept Tajo into the Apache Incubator
On Sat, Mar 2, 2013 at 3:48 AM, Alex Karasulu akaras...@apache.org wrote: +1 (binding) Just as an FYI, I'm also a mentor of this project. -- Best Regards, -- Alex
Re: Incubator PMC/Board report for Mar 2013 ([ppmc])
Daniel Shahaf wrote: @(tez|knox).incubator.apache.org lists had been created. Thanks. When Clutch detects that messages are flowing to the mbox then it flags the list as ready. They are not yet at the index page of http://mail-archives.apache.org/mod_mbox/ -David David Crossley wrote on Tue, Mar 05, 2013 at 09:04:11 +1100: These are for the new podlings Knox and Tez. The system has not yet detected that their mail lists are established. so the default is to general@ -David Marvin wrote: Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 20 March 2013, 10:30:00:00 PST. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, Mar 6th). Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/March2013 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC - 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: Markdown issue
Hello Juan Pablo, Just inline HTML. Markdown allows it. [1] [1] http://daringfireball.net/projects/markdown/syntax#html Regards, -- Ioan Eugen Stan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Markdown issue
See if this helps: http://michelf.ca/projects/php-markdown/extra/#spe-attr Which is linked from: http://www.apache.org/dev/cmsref.html#markdown - Shane On 3/4/2013 6:46 PM, Juan Pablo Santos Rodríguez wrote: Hi all, probably is a dumb issue and I'm missing something obvious, but so far, I haven't been able to solve it: Is there an easy way to tell a markdown link to use a specific css class? I'd like to render links pointing outside the incubator site with an external css class. I know I can write the html equivalent, but that feels unnatural, so I'd better avoid that option. I've been poking at a few site's sources, but haven't had any luck yet.. thx in advance! br, juan pablo - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Mesos 0.10.0-incubating (RC4)
Great. We just need 1 more IPMC +1 here. Anyone willing to contribute a review of Mesos 0.10.0-incubating RC4? Cheers, Chris On 3/4/13 9:57 AM, Benjamin Hindman b...@eecs.berkeley.edu wrote: Yes, my vote is a +1. On Sat, Mar 2, 2013 at 4:40 PM, Mattmann, Chris A (388J) chris.a.mattm...@jpl.nasa.gov wrote: Ben, just FYI on this, is your VOTE +1? The current tally I have is: +1 Chris Mattmann* * - IPMC We need probably a couple VOTEs from the Mesos community here (PPMC members), can you poke Vinod, as well as anyone else that has time to build and test and review the RC? IPMC folks -- a review and a couple more binding VOTEs would really help out Mesos here. Can folks try it out and VOTE? Thank you. Cheers, Chris Vote Wrangler Mattmann On 2/7/13 10:32 PM, Benjamin Hindman b...@berkeley.edu wrote: Please vote on releasing the following candidate as Apache Mesos (incubating) version 0.10.0. This will be the second incubator release for Mesos in Apache. -- --- Changes since last release candidate: * Updated configure.ac to work better on OS X 10.8. * Added missing license (the only blocker on the previous candidate). -- --- The candidate for Mesos 0.10.0-incubating release is available at: http://people.apache.org/~benh/mesos-0.10.0-incubating-RC4/mesos-0.10.0-i n cubating.tar.gz The tag to be voted on: https://svn.apache.org/repos/asf/incubator/mesos/tags/release-0.10.0-incu b ating-RC4 The MD5 checksum of the tarball can be found at: http://people.apache.org/~benh/mesos-0.10.0-incubating-RC4/mesos-0.10.0-i n cubating.tar.gz.md5 The signature of the tarball can be found at: http://people.apache.org/~benh/mesos-0.10.0-incubating-RC4/mesos-0.10.0-i n cubating.tar.gz.asc Mesos' KEYS file, containing the PGP keys used to sign the release: http://svn.apache.org/repos/asf/incubator/mesos/dist/KEYS Please vote on releasing this package as Apache Mesos 0.10.0-incubating! The vote is open until Monday, February 11th at 5:00 pm (PST) and passes if a majority of at least 3 +1 IPMC votes are cast. [ ] +1 Release this package as Apache Mesos 0.10.0-incubating [ ] -1 Do not release this package because ... To learn more about Apache Mesos, please see http://www.mesosproject.org. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Ripple, Streams, Onami, HDT need to fix your metadata
Ripple, Streams, Onami, Hadoop Development Tools ... Those projects would have received the email reminder about reporting. You need to care for your podling metadata in the content/podlings.xml file to take yourself off the monthly schedule and onto quarterly. (Unless you do want to keep doing monthly.) See column C and the help notes below the table: http://incubator.apache.org/clutch.html This file http://incubator.apache.org/report-groups.txt and http://incubator.apache.org/report_due_3.txt are generated from that content/podlings.xml file and are used to automate the reminders and other stuff. -David David Crossley wrote: Dave Fisher wrote: Hey Folks, Etch has graduated and is now a TLP, correct? It's board reports should now go directly to board@ from the PMC chair. As explained in the Incubator graduation docs, the Etch project needs to finalise their graduation steps. http://incubator.apache.org/clutch.html#etch http://incubator.apache.org/clutch.html#other http://incubator.apache.org/clutch.html#h-Graduate -David Regards, Dave Begin forwarded message: From: Marvin no-re...@apache.org Date: March 4, 2013 4:18:48 AM PST To: d...@etch.incubator.apache.org Subject: Incubator PMC/Board report for Mar 2013 ([ppmc]) Reply-To: d...@etch.apache.org delivered-to: mailing list d...@etch.apache.org delivered-to: moderator for d...@etch.apache.org Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 20 March 2013, 10:30:00:00 PST. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, Mar 6th). Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/March2013 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC - 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: Fwd: Incubator PMC/Board report for Mar 2013 ([ppmc])
Hi all, thanks for showing me the missing steps. I will update the status right now. I think the rest of the graduation steps have been completed so far, we have already reported to the board in January. Regards, Martin -Original Message- From: David Crossley [mailto:cross...@apache.org] Sent: Monday, March 04, 2013 10:57 PM To: general@incubator.apache.org Cc: d...@etch.apache.org Subject: Re: Fwd: Incubator PMC/Board report for Mar 2013 ([ppmc]) Dave Fisher wrote: Hey Folks, Etch has graduated and is now a TLP, correct? It's board reports should now go directly to board@ from the PMC chair. As explained in the Incubator graduation docs, the Etch project needs to finalise their graduation steps. http://incubator.apache.org/clutch.html#etch http://incubator.apache.org/clutch.html#other http://incubator.apache.org/clutch.html#h-Graduate -David Regards, Dave Begin forwarded message: From: Marvin no-re...@apache.org Date: March 4, 2013 4:18:48 AM PST To: d...@etch.incubator.apache.org Subject: Incubator PMC/Board report for Mar 2013 ([ppmc]) Reply-To: d...@etch.apache.org delivered-to: mailing list d...@etch.apache.org delivered-to: moderator for d...@etch.apache.org Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 20 March 2013, 10:30:00:00 PST. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, Mar 6th). Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/March2013 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC - 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: Ripple, Streams, Onami, HDT need to fix your metadata
Hi David, I'll fix HDT's. Cheers, Chris On 3/4/13 11:15 PM, David Crossley cross...@apache.org wrote: Ripple, Streams, Onami, Hadoop Development Tools ... Those projects would have received the email reminder about reporting. You need to care for your podling metadata in the content/podlings.xml file to take yourself off the monthly schedule and onto quarterly. (Unless you do want to keep doing monthly.) See column C and the help notes below the table: http://incubator.apache.org/clutch.html This file http://incubator.apache.org/report-groups.txt and http://incubator.apache.org/report_due_3.txt are generated from that content/podlings.xml file and are used to automate the reminders and other stuff. -David David Crossley wrote: Dave Fisher wrote: Hey Folks, Etch has graduated and is now a TLP, correct? It's board reports should now go directly to board@ from the PMC chair. As explained in the Incubator graduation docs, the Etch project needs to finalise their graduation steps. http://incubator.apache.org/clutch.html#etch http://incubator.apache.org/clutch.html#other http://incubator.apache.org/clutch.html#h-Graduate -David Regards, Dave Begin forwarded message: From: Marvin no-re...@apache.org Date: March 4, 2013 4:18:48 AM PST To: d...@etch.incubator.apache.org Subject: Incubator PMC/Board report for Mar 2013 ([ppmc]) Reply-To: d...@etch.apache.org delivered-to: mailing list d...@etch.apache.org delivered-to: moderator for d...@etch.apache.org Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 20 March 2013, 10:30:00:00 PST. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, Mar 6th). Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/March2013 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC - 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: [PROPOSAL] Curator for the Apache Incubator
Hi Jordan, Yep, thank you. I will be suggesting at graduation time barring any epiphanies all around that you guys go the TLP route. Good luck. Cheers, Chris On 3/1/13 6:29 AM, Jordan Zimmerman jor...@jordanzimmerman.com wrote: Chris, I added a line to the Alignment section. Let me know if it's OK. -JZ On Feb 26, 2013, at 1:23 PM, Mattmann, Chris A (388J) chris.a.mattm...@jpl.nasa.gov wrote: I would appreciate at some level a note in your proposal regarding at least the concern by one member of the IPMC that Curator should grow into its own TLP rather than be a part of ZK should it be accepted. - 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
