Re: More and better report nagging
Tim Williams wrote: On Mon, Dec 17, 2012 at 7:48 PM, Benson Margulies bimargul...@gmail.com wrote: On Mon, Dec 17, 2012 at 7:35 PM, Marvin Humphrey mar...@rectangular.com wrote: On Mon, Dec 17, 2012 at 4:04 PM, Tim Williams william...@gmail.com wrote: FWIW, I feel the same. I'd rather see 'did not report' and let the IPMC look for that pattern. Maybe just have your template generator default to DNR in the text? +1 on defaulting to DNR. How about sending out the whole Incubator report to all podling dev lists, every month? That way the DNR shows up without an IPMC member having to notice and take action. But in addition, it increases podling exposure to other projects and to the ASF at large. An alternative is to send it out to only the podlings that are reporting for a cycle, but that's more work and doesn't serve the purpose of connecting the podling to being in the Incubator quite so cleanly. I feel all that we are all volunteers, that podlings are volunteers who don't necessarily have their organizational act together, and that calling them out for DNR is not a very effective technique to providing the supervision that we, as a PMC, are on the hook for. So I'm inclined for now to nag, and to spend a few minutes making that job less labor-intensive. I'm beginning to think your mind's made up and the original question was a pleasantry, but in case not... I hold a different view of things. While I think that we, ok you, are on the hook for a board report, we've (PMC) delegated[1] the reporting of each podling to the mentors that we approved for that podling. We aren't calling out the podling as DNR - we're calling out their mentor as DNR. If there's additional nags to go out, I'd do my default to DNR and send the nag to the mentors directly. Ultimately, making that job less labor-intensive involves getting mentors and would-be-mentors to realize they can't simply go around spewing their seeds as absentee fathers - it's a real commitment; to the podling and to the foundation. Shucks, keeping a record of deadbeat mentors would prolly help... In the end though, you've a thankless and tough job, so consider these as constructive thoughts to be readily ignored in favor of whatever it takes to get your job done:) Thanks, --tim [1] - http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Mentor Things should be in their hands as much as possible. In my opinion each podling group of developers should be ensuring that their board report is ready, with the mentors just mentoring and making sure that actual status does get reported. I wonder if we could utilise the podling metadata system at content/podlings.xml to get a podling PPMC member or a mentor to set an attribute to mark that the report is received. Put the PPMC in the loop. This gets them used to overseeing their own project, being self-reliant, and maintaining their own records. Another benefit of editing that file is that they see when their next report is due and whether their metadata needs to be updated. Any nag to them could encourage them to visit that file. -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Graduate Apache Etch podling from Apache Incubator
This is a call for vote to graduate the Apache Etch podling from Apache Incubator. The Apache Etch project entered the Incubator in September 2008. Since then it has had ups and downs but we feel ready for graduation now. Our community, though small, is active and healthy. In the past four years we have grown the community in committers and users (e.g. in the automotive domain). We made significant improvements to the project codebase and completed several releases according to the ASF guidelines. The community (including our mentors and shepherds) has voted to proceed with graduation [1], the result can be found at [2]. Discussion and voting for the proposed resolution is also available at [3] and [4]. Please find the proposed board resolution below. Please cast your votes: [ ] +1 Graduate Apache Etch podling from Apache Incubator [ ] +0 Indifferent to the graduation status of Apache Etch podling [ ] -1 Reject graduation of Apache Etch podling from Apache Incubator because ... Thanks, Martin [1] http://s.apache.org/etch-graduation-vote [2] http://s.apache.org/etch-graduation-vote-result [3] http://s.apache.org/etch-resolution-proposal [4] http://s.apache.org/etch-proposal-vote-result - Resolution: X. Establish the Apache Etch Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to a cross-platform, language- and transport-independent RPC-like messaging framework for building and consuming network services. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Etch Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Etch Project be and hereby is responsible for the creation and maintenance of software related to a cross-platform, language- and transport-independent RPC-like messaging framework for building and consuming network services; and be it further RESOLVED, that the office of Vice President, Apache Etch be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Etch Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Etch Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Etch Project: * Scott Comerscco...@apache.org * Martijn Dashorst dasho...@apache.org * Michael Fitzner fitz...@apache.org * Youngjin Park yp...@apache.org * Martin Veith vei...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Martin Veith be appointed to the office of Vice President, Apache Etch, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Etch PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Etch Project; and be it further RESOLVED, that the Apache Etch Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Etch podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Etch podling encumbered upon the Apache Incubator Project are hereafter discharged. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: More and better report nagging
Personally, I'm not against nagging. Actually, when I'm on the receiving end, I usually appreciate it, as timeliness is not a quality I am widely praised for. Some podlings are in a position that is different from TLPs - they are new to the whole thing, and may therefore require a little more help than we would expect a TLP to need in remembering their responsibilities. However, if I were needing to nag a podling that is otherwise near graduation, I'd perhaps be worried. The DNR marker is still important though, and we should be sure that we don't 'over-nag'. We encourage (more earlier in the process of incubation, less later) and if after a few nags they don't do it, then DNR is just fine. Upayavira On Tue, Dec 18, 2012, at 09:04 AM, David Crossley wrote: Tim Williams wrote: On Mon, Dec 17, 2012 at 7:48 PM, Benson Margulies bimargul...@gmail.com wrote: On Mon, Dec 17, 2012 at 7:35 PM, Marvin Humphrey mar...@rectangular.com wrote: On Mon, Dec 17, 2012 at 4:04 PM, Tim Williams william...@gmail.com wrote: FWIW, I feel the same. I'd rather see 'did not report' and let the IPMC look for that pattern. Maybe just have your template generator default to DNR in the text? +1 on defaulting to DNR. How about sending out the whole Incubator report to all podling dev lists, every month? That way the DNR shows up without an IPMC member having to notice and take action. But in addition, it increases podling exposure to other projects and to the ASF at large. An alternative is to send it out to only the podlings that are reporting for a cycle, but that's more work and doesn't serve the purpose of connecting the podling to being in the Incubator quite so cleanly. I feel all that we are all volunteers, that podlings are volunteers who don't necessarily have their organizational act together, and that calling them out for DNR is not a very effective technique to providing the supervision that we, as a PMC, are on the hook for. So I'm inclined for now to nag, and to spend a few minutes making that job less labor-intensive. I'm beginning to think your mind's made up and the original question was a pleasantry, but in case not... I hold a different view of things. While I think that we, ok you, are on the hook for a board report, we've (PMC) delegated[1] the reporting of each podling to the mentors that we approved for that podling. We aren't calling out the podling as DNR - we're calling out their mentor as DNR. If there's additional nags to go out, I'd do my default to DNR and send the nag to the mentors directly. Ultimately, making that job less labor-intensive involves getting mentors and would-be-mentors to realize they can't simply go around spewing their seeds as absentee fathers - it's a real commitment; to the podling and to the foundation. Shucks, keeping a record of deadbeat mentors would prolly help... In the end though, you've a thankless and tough job, so consider these as constructive thoughts to be readily ignored in favor of whatever it takes to get your job done:) Thanks, --tim [1] - http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Mentor Things should be in their hands as much as possible. In my opinion each podling group of developers should be ensuring that their board report is ready, with the mentors just mentoring and making sure that actual status does get reported. I wonder if we could utilise the podling metadata system at content/podlings.xml to get a podling PPMC member or a mentor to set an attribute to mark that the report is received. Put the PPMC in the loop. This gets them used to overseeing their own project, being self-reliant, and maintaining their own records. Another benefit of editing that file is that they see when their next report is due and whether their metadata needs to be updated. Any nag to them could encourage them to visit that file. -David - 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: More and better report nagging
On Tue, Dec 18, 2012 at 5:21 AM, Upayavira u...@odoko.co.uk wrote: Personally, I'm not against nagging. Actually, when I'm on the receiving end, I usually appreciate it, as timeliness is not a quality I am widely praised for. Some podlings are in a position that is different from TLPs - they are new to the whole thing, and may therefore require a little more help than we would expect a TLP to need in remembering their responsibilities. However, if I were needing to nag a podling that is otherwise near graduation, I'd perhaps be worried. The DNR marker is still important though, and we should be sure that we don't 'over-nag'. We encourage (more earlier in the process of incubation, less later) and if after a few nags they don't do it, then DNR is just fine. I want, at least, a *quick* way to find out how many DNR's are pending, and be able to make informed decisions about nagging. So I plan to go ahead with the template that allows a tool to tell who is missing. Upayavira On Tue, Dec 18, 2012, at 09:04 AM, David Crossley wrote: Tim Williams wrote: On Mon, Dec 17, 2012 at 7:48 PM, Benson Margulies bimargul...@gmail.com wrote: On Mon, Dec 17, 2012 at 7:35 PM, Marvin Humphrey mar...@rectangular.com wrote: On Mon, Dec 17, 2012 at 4:04 PM, Tim Williams william...@gmail.com wrote: FWIW, I feel the same. I'd rather see 'did not report' and let the IPMC look for that pattern. Maybe just have your template generator default to DNR in the text? +1 on defaulting to DNR. How about sending out the whole Incubator report to all podling dev lists, every month? That way the DNR shows up without an IPMC member having to notice and take action. But in addition, it increases podling exposure to other projects and to the ASF at large. An alternative is to send it out to only the podlings that are reporting for a cycle, but that's more work and doesn't serve the purpose of connecting the podling to being in the Incubator quite so cleanly. I feel all that we are all volunteers, that podlings are volunteers who don't necessarily have their organizational act together, and that calling them out for DNR is not a very effective technique to providing the supervision that we, as a PMC, are on the hook for. So I'm inclined for now to nag, and to spend a few minutes making that job less labor-intensive. I'm beginning to think your mind's made up and the original question was a pleasantry, but in case not... I hold a different view of things. While I think that we, ok you, are on the hook for a board report, we've (PMC) delegated[1] the reporting of each podling to the mentors that we approved for that podling. We aren't calling out the podling as DNR - we're calling out their mentor as DNR. If there's additional nags to go out, I'd do my default to DNR and send the nag to the mentors directly. Ultimately, making that job less labor-intensive involves getting mentors and would-be-mentors to realize they can't simply go around spewing their seeds as absentee fathers - it's a real commitment; to the podling and to the foundation. Shucks, keeping a record of deadbeat mentors would prolly help... In the end though, you've a thankless and tough job, so consider these as constructive thoughts to be readily ignored in favor of whatever it takes to get your job done:) Thanks, --tim [1] - http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Mentor Things should be in their hands as much as possible. In my opinion each podling group of developers should be ensuring that their board report is ready, with the mentors just mentoring and making sure that actual status does get reported. I wonder if we could utilise the podling metadata system at content/podlings.xml to get a podling PPMC member or a mentor to set an attribute to mark that the report is received. Put the PPMC in the loop. This gets them used to overseeing their own project, being self-reliant, and maintaining their own records. Another benefit of editing that file is that they see when their next report is due and whether their metadata needs to be updated. Any nag to them could encourage them to visit that file. -David - 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: More and better report nagging
On Tue, Dec 18, 2012, at 11:39 AM, Benson Margulies wrote: On Tue, Dec 18, 2012 at 5:21 AM, Upayavira u...@odoko.co.uk wrote: Personally, I'm not against nagging. Actually, when I'm on the receiving end, I usually appreciate it, as timeliness is not a quality I am widely praised for. Some podlings are in a position that is different from TLPs - they are new to the whole thing, and may therefore require a little more help than we would expect a TLP to need in remembering their responsibilities. However, if I were needing to nag a podling that is otherwise near graduation, I'd perhaps be worried. The DNR marker is still important though, and we should be sure that we don't 'over-nag'. We encourage (more earlier in the process of incubation, less later) and if after a few nags they don't do it, then DNR is just fine. I want, at least, a *quick* way to find out how many DNR's are pending, and be able to make informed decisions about nagging. So I plan to go ahead with the template that allows a tool to tell who is missing. Seems reasonable to me. Upayavira - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduate Apache Etch podling from Apache Incubator
Hi Martin! Looks good in general, but a few things need to be updated before you are finished: http://incubator.apache.org/projects/etch.html contains still quite a lot TBD. I guess most are resolved and only needs updating in SVN [1] LieGrue, strub [1] https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/ - Original Message - From: Martin Veith martin.ve...@bmw-carit.de To: general@incubator.apache.org general@incubator.apache.org Cc: etch-...@incubator.apache.org etch-...@incubator.apache.org Sent: Tuesday, December 18, 2012 10:10 AM Subject: [VOTE] Graduate Apache Etch podling from Apache Incubator T his is a call for vote to graduate the Apache Etch podling from Apache Incubator. The Apache Etch project entered the Incubator in September 2008. Since then it has had ups and downs but we feel ready for graduation now. Our community, though small, is active and healthy. In the past four years we have grown the community in committers and users (e.g. in the automotive domain). We made significant improvements to the project codebase and completed several releases according to the ASF guidelines. The community (including our mentors and shepherds) has voted to proceed with graduation [1], the result can be found at [2]. Discussion and voting for the proposed resolution is also available at [3] and [4]. Please find the proposed board resolution below. Please cast your votes: [ ] +1 Graduate Apache Etch podling from Apache Incubator [ ] +0 Indifferent to the graduation status of Apache Etch podling [ ] -1 Reject graduation of Apache Etch podling from Apache Incubator because ... Thanks, Martin [1] http://s.apache.org/etch-graduation-vote [2] http://s.apache.org/etch-graduation-vote-result [3] http://s.apache.org/etch-resolution-proposal [4] http://s.apache.org/etch-proposal-vote-result - Resolution: X. Establish the Apache Etch Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to a cross-platform, language- and transport-independent RPC-like messaging framework for building and consuming network services. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Etch Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Etch Project be and hereby is responsible for the creation and maintenance of software related to a cross-platform, language- and transport-independent RPC-like messaging framework for building and consuming network services; and be it further RESOLVED, that the office of Vice President, Apache Etch be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Etch Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Etch Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Etch Project: * Scott Comer scco...@apache.org * Martijn Dashorst dasho...@apache.org * Michael Fitzner fitz...@apache.org * Youngjin Park yp...@apache.org * Martin Veith vei...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Martin Veith be appointed to the office of Vice President, Apache Etch, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Etch PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Etch Project; and be it further RESOLVED, that the Apache Etch Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Etch podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Etch podling encumbered upon the Apache Incubator Project are hereafter discharged.
RE: [VOTE] Graduate Apache Etch podling from Apache Incubator
Hello Mark, thank you for your feedback! Mark Struberg wrote on 2012-12-18: Looks good in general, but a few things need to be updated before you are finished: http://incubator.apache.org/projects/etch.html contains still quite a lot TBD. I guess most are resolved and only needs updating in SVN [1] I updated the status page already this morning, but I forgot to publish the site. Now it's live. Best Regards, Martin - Original Message - From: Martin Veith martin.ve...@bmw-carit.de To: general@incubator.apache.org general@incubator.apache.org Cc: etch-...@incubator.apache.org etch-...@incubator.apache.org Sent: Tuesday, December 18, 2012 10:10 AM Subject: [VOTE] Graduate Apache Etch podling from Apache Incubator T his is a call for vote to graduate the Apache Etch podling from Apache Incubator. The Apache Etch project entered the Incubator in September 2008. Since then it has had ups and downs but we feel ready for graduation now. Our community, though small, is active and healthy. In the past four years we have grown the community in committers and users (e.g. in the automotive domain). We made significant improvements to the project codebase and completed several releases according to the ASF guidelines. The community (including our mentors and shepherds) has voted to proceed with graduation [1], the result can be found at [2]. Discussion and voting for the proposed resolution is also available at [3] and [4]. Please find the proposed board resolution below. Please cast your votes: [ ] +1 Graduate Apache Etch podling from Apache Incubator [ ] +0 Indifferent to the graduation status of Apache Etch podling [ ] -1 Reject graduation of Apache Etch podling from Apache Incubator because ... Thanks, Martin [1] http://s.apache.org/etch-graduation-vote [2] http://s.apache.org/etch-graduation-vote-result [3] http://s.apache.org/etch-resolution-proposal [4] http://s.apache.org/etch-proposal-vote-result -- --- Resolution: X. Establish the Apache Etch Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to a cross-platform, language- and transport-independent RPC-like messaging framework for building and consuming network services. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Etch Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Etch Project be and hereby is responsible for the creation and maintenance of software related to a cross-platform, language- and transport-independent RPC-like messaging framework for building and consuming network services; and be it further RESOLVED, that the office of Vice President, Apache Etch be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Etch Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Etch Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Etch Project: * Scott Comer scco...@apache.org * Martijn Dashorst dasho...@apache.org * Michael Fitzner fitz...@apache.org * Youngjin Park yp...@apache.org * Martin Veith vei...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Martin Veith be appointed to the office of Vice President, Apache Etch, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Etch PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Etch Project; and be it further RESOLVED, that the Apache Etch Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Etch podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Etch podling encumbered upon the Apache
Re: [VOTE] Graduate Apache Etch podling from Apache Incubator
[X] +1 Graduate Apache Etch podling from Apache Incubator (binding) Martijn - 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 (RC2)
+1 On Tue, Dec 18, 2012 at 2:39 AM, Matei Zaharia ma...@apache.org wrote: +1 Tested it on Mac OS X. Matei On Dec 11, 2012, at 12:56 PM, Benjamin Hindman 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. The candidate for Mesos 0.10.0-incubating release is available at: http://people.apache.org/~benh/mesos-0.10.0-incubating-RC2/mesos-0.10.0-incubating.tar.gz The tag to be voted on: https://svn.apache.org/repos/asf/incubator/mesos/tags/release-0.10.0-incubating-RC2 The MD5 checksum of the tarball can be found at: http://people.apache.org/~benh/mesos-0.10.0-incubating-RC2/mesos-0.10.0-incubating.tar.gz.md5 The signature of the tarball can be found at: http://people.apache.org/~benh/mesos-0.10.0-incubating-RC2/mesos-0.10.0-incubating.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 Friday, December 14th 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 -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduate Apache Etch podling from Apache Incubator
+1. Let's go etch! On Dec 18, 2012, at 1:10 AM, Martin Veith wrote: This is a call for vote to graduate the Apache Etch podling from Apache Incubator. The Apache Etch project entered the Incubator in September 2008. Since then it has had ups and downs but we feel ready for graduation now. Our community, though small, is active and healthy. In the past four years we have grown the community in committers and users (e.g. in the automotive domain). We made significant improvements to the project codebase and completed several releases according to the ASF guidelines. The community (including our mentors and shepherds) has voted to proceed with graduation [1], the result can be found at [2]. Discussion and voting for the proposed resolution is also available at [3] and [4]. Please find the proposed board resolution below. Please cast your votes: [ ] +1 Graduate Apache Etch podling from Apache Incubator [ ] +0 Indifferent to the graduation status of Apache Etch podling [ ] -1 Reject graduation of Apache Etch podling from Apache Incubator because ... Thanks, Martin [1] http://s.apache.org/etch-graduation-vote [2] http://s.apache.org/etch-graduation-vote-result [3] http://s.apache.org/etch-resolution-proposal [4] http://s.apache.org/etch-proposal-vote-result - Resolution: X. Establish the Apache Etch Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to a cross-platform, language- and transport-independent RPC-like messaging framework for building and consuming network services. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Etch Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Etch Project be and hereby is responsible for the creation and maintenance of software related to a cross-platform, language- and transport-independent RPC-like messaging framework for building and consuming network services; and be it further RESOLVED, that the office of Vice President, Apache Etch be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Etch Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Etch Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Etch Project: * Scott Comerscco...@apache.org * Martijn Dashorst dasho...@apache.org * Michael Fitzner fitz...@apache.org * Youngjin Park yp...@apache.org * Martin Veith vei...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Martin Veith be appointed to the office of Vice President, Apache Etch, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Etch PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Etch Project; and be it further RESOLVED, that the Apache Etch Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Etch podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Etch podling encumbered upon the Apache Incubator Project are hereafter discharged. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduate Apache Etch podling from Apache Incubator
+1 Doug On Tue, Dec 18, 2012 at 1:10 AM, Martin Veith martin.ve...@bmw-carit.de wrote: This is a call for vote to graduate the Apache Etch podling from Apache Incubator. The Apache Etch project entered the Incubator in September 2008. Since then it has had ups and downs but we feel ready for graduation now. Our community, though small, is active and healthy. In the past four years we have grown the community in committers and users (e.g. in the automotive domain). We made significant improvements to the project codebase and completed several releases according to the ASF guidelines. The community (including our mentors and shepherds) has voted to proceed with graduation [1], the result can be found at [2]. Discussion and voting for the proposed resolution is also available at [3] and [4]. Please find the proposed board resolution below. Please cast your votes: [ ] +1 Graduate Apache Etch podling from Apache Incubator [ ] +0 Indifferent to the graduation status of Apache Etch podling [ ] -1 Reject graduation of Apache Etch podling from Apache Incubator because ... Thanks, Martin [1] http://s.apache.org/etch-graduation-vote [2] http://s.apache.org/etch-graduation-vote-result [3] http://s.apache.org/etch-resolution-proposal [4] http://s.apache.org/etch-proposal-vote-result - Resolution: X. Establish the Apache Etch Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to a cross-platform, language- and transport-independent RPC-like messaging framework for building and consuming network services. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Etch Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Etch Project be and hereby is responsible for the creation and maintenance of software related to a cross-platform, language- and transport-independent RPC-like messaging framework for building and consuming network services; and be it further RESOLVED, that the office of Vice President, Apache Etch be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Etch Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Etch Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Etch Project: * Scott Comerscco...@apache.org * Martijn Dashorst dasho...@apache.org * Michael Fitzner fitz...@apache.org * Youngjin Park yp...@apache.org * Martin Veith vei...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Martin Veith be appointed to the office of Vice President, Apache Etch, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Etch PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Etch Project; and be it further RESOLVED, that the Apache Etch Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Etch podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Etch podling encumbered upon the Apache Incubator Project are hereafter discharged. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Request for Mentors on Mesos
Hey all, the Mesos project is looking for some additional mentors to help with incubation: http://incubator.apache.org/mesos/ We're close to cutting our 0.10 release and are still a bit new to the ASF. We would appreciate another mentor for the project to ensure we're living up to ASF principles. We'd love to get in a state that we could eventually graduate after building a community and pushing more releases out. Let me know if you can help out. -- Cheers, Chris Aniszczyk | Open Source Manager | Twitter, Inc. @cra | +1 512 961 6719
Re: [VOTE] Graduate Apache Etch podling from Apache Incubator
+1 On Tue, Dec 18, 2012 at 12:31 PM, Doug Cutting cutt...@apache.org wrote: +1 Doug On Tue, Dec 18, 2012 at 1:10 AM, Martin Veith martin.ve...@bmw-carit.de wrote: This is a call for vote to graduate the Apache Etch podling from Apache Incubator. The Apache Etch project entered the Incubator in September 2008. Since then it has had ups and downs but we feel ready for graduation now. Our community, though small, is active and healthy. In the past four years we have grown the community in committers and users (e.g. in the automotive domain). We made significant improvements to the project codebase and completed several releases according to the ASF guidelines. The community (including our mentors and shepherds) has voted to proceed with graduation [1], the result can be found at [2]. Discussion and voting for the proposed resolution is also available at [3] and [4]. Please find the proposed board resolution below. Please cast your votes: [ ] +1 Graduate Apache Etch podling from Apache Incubator [ ] +0 Indifferent to the graduation status of Apache Etch podling [ ] -1 Reject graduation of Apache Etch podling from Apache Incubator because ... Thanks, Martin [1] http://s.apache.org/etch-graduation-vote [2] http://s.apache.org/etch-graduation-vote-result [3] http://s.apache.org/etch-resolution-proposal [4] http://s.apache.org/etch-proposal-vote-result - Resolution: X. Establish the Apache Etch Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to a cross-platform, language- and transport-independent RPC-like messaging framework for building and consuming network services. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Etch Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Etch Project be and hereby is responsible for the creation and maintenance of software related to a cross-platform, language- and transport-independent RPC-like messaging framework for building and consuming network services; and be it further RESOLVED, that the office of Vice President, Apache Etch be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Etch Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Etch Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Etch Project: * Scott Comerscco...@apache.org * Martijn Dashorst dasho...@apache.org * Michael Fitzner fitz...@apache.org * Youngjin Park yp...@apache.org * Martin Veith vei...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Martin Veith be appointed to the office of Vice President, Apache Etch, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Etch PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Etch Project; and be it further RESOLVED, that the Apache Etch Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Etch podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Etch podling encumbered upon the Apache Incubator Project are hereafter discharged. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
Re: Request for Mentors on Mesos
I can do it. On Tue, Dec 18, 2012 at 9:36 AM, Chris Aniszczyk z...@twitter.com wrote: Hey all, the Mesos project is looking for some additional mentors to help with incubation: http://incubator.apache.org/mesos/ We're close to cutting our 0.10 release and are still a bit new to the ASF. We would appreciate another mentor for the project to ensure we're living up to ASF principles. We'd love to get in a state that we could eventually graduate after building a community and pushing more releases out. Let me know if you can help out. -- Cheers, Chris Aniszczyk | Open Source Manager | Twitter, Inc. @cra | +1 512 961 6719
Re: [VOTE] Release Apache Mesos 0.10.0-incubating (RC2)
+1 Tested it on Mac OS X. Matei On Dec 11, 2012, at 12:56 PM, Benjamin Hindman 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. The candidate for Mesos 0.10.0-incubating release is available at: http://people.apache.org/~benh/mesos-0.10.0-incubating-RC2/mesos-0.10.0-incubating.tar.gz The tag to be voted on: https://svn.apache.org/repos/asf/incubator/mesos/tags/release-0.10.0-incubating-RC2 The MD5 checksum of the tarball can be found at: http://people.apache.org/~benh/mesos-0.10.0-incubating-RC2/mesos-0.10.0-incubating.tar.gz.md5 The signature of the tarball can be found at: http://people.apache.org/~benh/mesos-0.10.0-incubating-RC2/mesos-0.10.0-incubating.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 Friday, December 14th 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
Re: Graduation
Hi, it's hard to tell at this point. We have some very neat contributions and integrations coming in that should be quite interesting, so in my opinion we should have a clearer view for answering your question after the forthcoming release - on which we are currently working. One sure thing is that we have not yet reached critical mass for graduation. Matthieu On Dec 13, 2012, at 22:17 , Benson Margulies wrote: Hello S4, How far off do you think that you are from having enough people on board to graduate? --benson - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduate Apache Etch podling from Apache Incubator
all necessary TBD in the status file got filled. proposal looks fine. +1 and good luck! LieGrue, strub - Original Message - From: Mark Struberg strub...@yahoo.de To: general@incubator.apache.org general@incubator.apache.org Cc: etch-...@incubator.apache.org etch-...@incubator.apache.org Sent: Tuesday, December 18, 2012 1:31 PM Subject: Re: [VOTE] Graduate Apache Etch podling from Apache Incubator Hi Martin! Looks good in general, but a few things need to be updated before you are finished: http://incubator.apache.org/projects/etch.html contains still quite a lot TBD. I guess most are resolved and only needs updating in SVN [1] LieGrue, strub [1] https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/ - Original Message - From: Martin Veith martin.ve...@bmw-carit.de To: general@incubator.apache.org general@incubator.apache.org Cc: etch-...@incubator.apache.org etch-...@incubator.apache.org Sent: Tuesday, December 18, 2012 10:10 AM Subject: [VOTE] Graduate Apache Etch podling from Apache Incubator T his is a call for vote to graduate the Apache Etch podling from Apache Incubator. The Apache Etch project entered the Incubator in September 2008. Since then it has had ups and downs but we feel ready for graduation now. Our community, though small, is active and healthy. In the past four years we have grown the community in committers and users (e.g. in the automotive domain). We made significant improvements to the project codebase and completed several releases according to the ASF guidelines. The community (including our mentors and shepherds) has voted to proceed with graduation [1], the result can be found at [2]. Discussion and voting for the proposed resolution is also available at [3] and [4]. Please find the proposed board resolution below. Please cast your votes: [ ] +1 Graduate Apache Etch podling from Apache Incubator [ ] +0 Indifferent to the graduation status of Apache Etch podling [ ] -1 Reject graduation of Apache Etch podling from Apache Incubator because ... Thanks, Martin [1] http://s.apache.org/etch-graduation-vote [2] http://s.apache.org/etch-graduation-vote-result [3] http://s.apache.org/etch-resolution-proposal [4] http://s.apache.org/etch-proposal-vote-result - Resolution: X. Establish the Apache Etch Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to a cross-platform, language- and transport-independent RPC-like messaging framework for building and consuming network services. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Etch Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Etch Project be and hereby is responsible for the creation and maintenance of software related to a cross-platform, language- and transport-independent RPC-like messaging framework for building and consuming network services; and be it further RESOLVED, that the office of Vice President, Apache Etch be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Etch Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Etch Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Etch Project: * Scott Comer scco...@apache.org * Martijn Dashorst dasho...@apache.org * Michael Fitzner fitz...@apache.org * Youngjin Park yp...@apache.org * Martin Veith vei...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Martin Veith be appointed to the office of Vice President, Apache Etch, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Etch PMC be and hereby is tasked with the creation of a set of bylaws intended
wiki privs
I don't seem to have the privs to add a page to the Incubator wiki; I wanted to write up the new proposed change to the retirement procedures. Should I just usurp http://wiki.apache.org/incubator/RetiringPodlings? Regards, Alan
Re: wiki privs
Alan, whats your Wiki-Name? One needs to put your name into the Contributors Page On Wed, Dec 19, 2012 at 5:02 AM, Alan Cabrera l...@toolazydogs.com wrote: I don't seem to have the privs to add a page to the Incubator wiki; I wanted to write up the new proposed change to the retirement procedures. Should I just usurp http://wiki.apache.org/incubator/RetiringPodlings? Regards, Alan -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: wiki privs
AlanCabrera Do I do that or does someone need to do this for me? If the former, where do I do that? Regards, Alan On Dec 18, 2012, at 8:15 PM, Christian Grobmeier wrote: Alan, whats your Wiki-Name? One needs to put your name into the Contributors Page On Wed, Dec 19, 2012 at 5:02 AM, Alan Cabrera l...@toolazydogs.com wrote: I don't seem to have the privs to add a page to the Incubator wiki; I wanted to write up the new proposed change to the retirement procedures. Should I just usurp http://wiki.apache.org/incubator/RetiringPodlings? Regards, Alan -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: wiki privs
On Tue, Dec 18, 2012 at 8:25 PM, Alan Cabrera l...@toolazydogs.com wrote: AlanCabrera Do I do that or does someone need to do this for me? If the former, where do I do that? You're already there on the ContributorsGroup page -- so whatever is thwarting you, it's not that. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: wiki privs
On Dec 18, 2012, at 9:27 PM, Marvin Humphrey wrote: On Tue, Dec 18, 2012 at 8:25 PM, Alan Cabrera l...@toolazydogs.com wrote: AlanCabrera Do I do that or does someone need to do this for me? If the former, where do I do that? You're already there on the ContributorsGroup page -- so whatever is thwarting you, it's not that. NM, EBKAC. I just figured out that I have to enter the new page name in the URL. Regards, Alan - 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 (RC2)
Most things look good. MD5, sig, etc. However, I see boto-2.0b2.zip in thirdparty/ but no note in NOTICE. Has this already been brought up? On Mon, Dec 17, 2012 at 2:01 PM, Matei Zaharia ma...@eecs.berkeley.eduwrote: +1 Tested it on Mac OS X. Matei On Dec 11, 2012, at 12:56 PM, Benjamin Hindman 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. The candidate for Mesos 0.10.0-incubating release is available at: http://people.apache.org/~benh/mesos-0.10.0-incubating-RC2/mesos-0.10.0-incubating.tar.gz The tag to be voted on: https://svn.apache.org/repos/asf/incubator/mesos/tags/release-0.10.0-incubating-RC2 The MD5 checksum of the tarball can be found at: http://people.apache.org/~benh/mesos-0.10.0-incubating-RC2/mesos-0.10.0-incubating.tar.gz.md5 The signature of the tarball can be found at: http://people.apache.org/~benh/mesos-0.10.0-incubating-RC2/mesos-0.10.0-incubating.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 Friday, December 14th 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
Re: [VOTE] Release Apache Mesos 0.10.0-incubating (RC2)
+1 On Tue, Dec 11, 2012 at 12:56 PM, Benjamin Hindman b...@berkeley.eduwrote: 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. The candidate for Mesos 0.10.0-incubating release is available at: http://people.apache.org/~benh/mesos-0.10.0-incubating-RC2/mesos-0.10.0-incubating.tar.gz The tag to be voted on: https://svn.apache.org/repos/asf/incubator/mesos/tags/release-0.10.0-incubating-RC2 The MD5 checksum of the tarball can be found at: http://people.apache.org/~benh/mesos-0.10.0-incubating-RC2/mesos-0.10.0-incubating.tar.gz.md5 The signature of the tarball can be found at: http://people.apache.org/~benh/mesos-0.10.0-incubating-RC2/mesos-0.10.0-incubating.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 Friday, December 14th 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.
