Re: [DISCUSS] PodlingBillOfRights
On Sun, Jun 16, 2013 at 10:48 PM, Joseph Schaefer joe_schae...@yahoo.com wrote: The typical escalation path is either board@ or board-private@ assuming private messages to the chair are ineffective. Most of the time, for most of our projects, this has worked well enough. So isn't learning this bit of information a crucial part of graduation? After all, once the project leaves the incubator its commiters and PMC won't have an access to the Ombudsman, isn't it in all of our best interest to teach them from the get-go what you've just described above? What's the danger of hooking up poddlings to the very channels they should be using once they graduate? The real issue for the IPMC boils down to the judgement call of whether the standard escalation procedures are working to everyone's satisfaction, Do we have real indication they are not? Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Stratos proposal as an incubating project
Good on you. Keep it up. -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Stratos proposal as an incubating project
+1 ...ant On Fri, Jun 14, 2013 at 10:49 PM, Ross Gardler rgard...@opendirective.comwrote: I would like to invite the IPMC vote to accept the Stratos proposal [1]. I want to clarify that this vote is for the Stratos project to enter the incubator as a standard podling under the existing incubation policy. The acceptance or otherwise of the probationary TLP idea is a separate issue that will be explored during the first month of incubation, potentially resulting in a further IPMC vote. This vote is *only* for accepting the Stratos project as a podling. [ ] +1 Accept the Stratos project as an incubating project [ ] +0 [ ] -1 Do not accept the Stratos project as an incubating project because... (provide reason) It's late on Friday evening here in the UK. I'll let this vote run well into next week to allow for the weekend. Thank you for your votes. Ross - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Permission to add a page to the Incubator wiki
Hello, May I have permission to add and edit OData proposal on the Incubator wiki? My username is StephanKlevenz. Thanks! Stephan
Re: Permission to add a page to the Incubator wiki
Done. On Mon, Jun 17, 2013, at 12:36 PM, Klevenz, Stephan wrote: Hello, May I have permission to add and edit OData proposal on the Incubator wiki? My username is StephanKlevenz. Thanks! Stephan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache ODF Toolkit 0.6-incubating(RC6)
On Mon, Jun 17, 2013, at 12:12 AM, Florian Hopf wrote: the voting period has passed but we had another IPMC +1 from our mentor Nick Burch on odf-dev. Our other mentor Yegor seems to be pretty busy currently so it would be great if somebody else could have a look at the release candidate. Took a second look at this today, thanks for addressing the concerns I raised the first time around. +1 (binding) Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache jclouds 1.6.1-incubating, RC3
Hi, I would love to vote on this, it would be nice to have a test procedure like this one: https://cwiki.apache.org/CLOUDSTACK/release-test-procedure.html Cheers, -sebastien On Jun 16, 2013, at 10:04 PM, Andrew Bayer andrew.ba...@gmail.com wrote: Hello, This is the third release candidate for Apache jclouds 1.6.1-incubating, the first jclouds release at Apache. This is the IPMC vote. The PPMC vote passed, with three +1s from mentors (David Nalley, Olivier Lamy, and Suresh Marru). It fixes the following issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12324412styleName=HtmlprojectId=12314430 *** Please download, test and vote by Wednesday, June 19th, 7pm PDT. Note that we are voting upon the source (tag). In addition, a discussion of why certain files are excluded from RAT checks can be found at https://wiki.apache.org/jclouds/1.6.1%20Incubating%20Release%20Issues. Source files: http://people.apache.org/~abayer/jclouds-1.6.1-incubating-candidate-3 Maven staging repo: https://repository.apache.org/content/repositories/orgapachejclouds-016 The tags to be voted upon: - jclouds - https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds.git;a=tag;h=8ed5571b0ecf7d79c64bc16642264684882f0311 - jclouds-labs - https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-labs.git;a=tag;h=54b084e474e0c22b539ed7cce0b0ebbc82b310cb - jclouds-chef - https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-chef.git;a=tag;h=4adced11f4e74513c06023d6b3cde0642fd4017f - jclouds-karaf - https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-karaf.git;a=tag;h=9e1f0d14285c8edeb35499f313aa7dbfab4a86f6 - jclouds-cli - https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-cli.git;a=tag;h=2e3575f56de2bf67469782d94d72ce8e621ddda5 jclouds KEYS file containing PGP keys we use to sign the release: http://www.apache.org/dist/incubator/jclouds/KEYS [ ] +1 [ ] 0 [ ] -1 (explain why) Thanks! A. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache jclouds 1.6.1-incubating, RC3
Yes - we'll have a detailed one up for the next release. For now, building from the tarballs (with a standard mvn clean install, in the order the repos are listed below) should suffice - that'll cover compilation, unit tests, and RAT check. Going forward, we'll have a guide for running the live tests as well. A. On Jun 17, 2013, at 8:21 AM, Sebastien Goasguen run...@gmail.com wrote: Hi, I would love to vote on this, it would be nice to have a test procedure like this one: https://cwiki.apache.org/CLOUDSTACK/release-test-procedure.html Cheers, -sebastien On Jun 16, 2013, at 10:04 PM, Andrew Bayer andrew.ba...@gmail.com wrote: Hello, This is the third release candidate for Apache jclouds 1.6.1-incubating, the first jclouds release at Apache. This is the IPMC vote. The PPMC vote passed, with three +1s from mentors (David Nalley, Olivier Lamy, and Suresh Marru). It fixes the following issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12324412styleName=HtmlprojectId=12314430 *** Please download, test and vote by Wednesday, June 19th, 7pm PDT. Note that we are voting upon the source (tag). In addition, a discussion of why certain files are excluded from RAT checks can be found at https://wiki.apache.org/jclouds/1.6.1%20Incubating%20Release%20Issues. Source files: http://people.apache.org/~abayer/jclouds-1.6.1-incubating-candidate-3 Maven staging repo: https://repository.apache.org/content/repositories/orgapachejclouds-016 The tags to be voted upon: - jclouds - https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds.git;a=tag;h=8ed5571b0ecf7d79c64bc16642264684882f0311 - jclouds-labs - https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-labs.git;a=tag;h=54b084e474e0c22b539ed7cce0b0ebbc82b310cb - jclouds-chef - https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-chef.git;a=tag;h=4adced11f4e74513c06023d6b3cde0642fd4017f - jclouds-karaf - https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-karaf.git;a=tag;h=9e1f0d14285c8edeb35499f313aa7dbfab4a86f6 - jclouds-cli - https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-cli.git;a=tag;h=2e3575f56de2bf67469782d94d72ce8e621ddda5 jclouds KEYS file containing PGP keys we use to sign the release: http://www.apache.org/dist/incubator/jclouds/KEYS [ ] +1 [ ] 0 [ ] -1 (explain why) Thanks! A. - 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 Stratos proposal as an incubating project
+1 Dan On Jun 14, 2013, at 5:49 PM, Ross Gardler rgard...@opendirective.com wrote: I would like to invite the IPMC vote to accept the Stratos proposal [1]. I want to clarify that this vote is for the Stratos project to enter the incubator as a standard podling under the existing incubation policy. The acceptance or otherwise of the probationary TLP idea is a separate issue that will be explored during the first month of incubation, potentially resulting in a further IPMC vote. This vote is *only* for accepting the Stratos project as a podling. [ ] +1 Accept the Stratos project as an incubating project [ ] +0 [ ] -1 Do not accept the Stratos project as an incubating project because... (provide reason) It's late on Friday evening here in the UK. I'll let this vote run well into next week to allow for the weekend. Thank you for your votes. Ross - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Creation of the Incubator Ombudsman
On Sat, Jun 15, 2013 at 08:52:38AM -0700, Alan Cabrera wrote: Problem: podlings are confused on where to go when there's a problem. Cause: we seem to collect/handle/organize problems in an ad hoc manner and sometimes mentors are the problem. Solution: we create an elected Incubator Ombudsman. Regards, Alan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org IMO, a PMC chair should both behave and be seen to the community as acting in this capacity. However, others have commented on at least the perception not being that this is the case. Given that, I'd be comfortable with this as an experiment... so +0. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] OData Proposal for Incubator
Stephan What overlap (if any) do you see with the existing Marmotta podling? They are building out an implementation of the Linked Data Platform which is a ongoing W3C standardization effort (http://www.w3.org/2012/ldp/wiki/Main_Page) and can be thought of as a more RDF/Semantic Web centric alternative to the MS/Oasis OData standard. Rob On 6/17/13 8:35 AM, Klevenz, Stephan stephan.klev...@sap.com wrote: Dear ASF members, We would like to propose the OData project to the Incubator. The OData Proposal is available at: https://wiki.apache.org/incubator/ODataProposal We welcome your feedback and suggestions. Thanks! Stephan Klevenz = Apache OData = === Abstract === Apache OData is a generic Java language implementation of the OData 2.0 specification which will serve as a code base for the upcoming OASIS OData specification. === Proposal === The Open Data Protocol (OData) [1] is a Web protocol for querying and updating data that provides a way to unlock your data and free it from silos that exist in applications today. OData does this by applying and building upon Web technologies such as HTTP, Atom Publishing Protocol (AtomPub) and JSON to provide access to information from a variety of applications, services, and stores. The Apache OData is a library which enables developers to implement OData producers and OData consumers. Basic principles of the library are to provide an OData 2.0 specification compliant OData Library, enhancements shall be possible in a compatible manner, have a clear separation between Core and API, to provide an option to build extensions on top. This library should be base for implementing future releases of the specification. === Background === OData was originally developed by Microsoft and is released in a version 2.0 under an Open Specification Promise [2]. A lot of companies did show interests in this protocol, used it in products and gave feedback back to Microsoft. This joined effort resulted in a new release OData 3.0 in 2012, this version became the basis for the OASIS technical committee [3] which is currently working on a new version of the specification. This OASIS standard release is expected this year. The initial Java code of this project was developed by a development team that had already experience with other OData 2.0 and 3.0 implementations at SAP AG. The current code base implements OData 2.0 and because of this version is widely used it is a good starting point to build an open source community for the OData standard. The current code also comes up with an implementation of an OData sample service. On the one side this is an example for users which want to use the library to expose their own data and on the other side it illustrates how implemented features work. Additionally, the code base includes an extension which is called JPA processor. With this extension it is easy to expose any JPA persistence model via OData protocol without a lot of coding. === Rationale === More software vendors moving to OData means more choice for customers who will be able to use different implementations. For the standard to succeed, however, ensuring interoperability is paramount: in order to manage an ever growing context and leverage the enormous portability and interoperability issues that a globally adopted standard brings, it is necessary to think about how to make the related ecosystem healthy and sustainable. Successful modern standards are driven by: * Clear documentation, built iteratively with continuous feedback from stakeholders * A clearly defined compatibility process, enforced by tools that allow to gauge how implementations can be compatible and interoperable * Accurate compliance criteria, documented in writing as well as in actual testing code that measure how tools and libraries are able to interoperate * A sample implementation to clear up potential doubts and ensure that the standard can actually be implemented in real life scenarios The above mentioned pieces are able to make the development activity, towards an OData implementation, easier and more successful. Having an healthy ecosystem will ensure a smoother implementation process, more compliant products, and ultimately, a wider adoption of the standard. The OData ecosystem has been successful in creating and documenting early versions of the standard, yet it might potentially lack two very important aspects, that is a exhaustive implementation of the complete protocol that can be used productively and to ensure interoperability. As much as such artifacts can be developed independently by any OData proponent, the value of having a neutral party as a steward of actual code is to be considered. The Apache Software Foundation has been playing this kind of role for many years, and can provide the perfect environment to foster contributions on the OData theme with a great amount of expertise. === Initial Goals === * Implement OData 2.0, make it final and mature * Start
Re: [PROPOSAL] OData Proposal for Incubator
On 6/17/13, Klevenz, Stephan stephan.klev...@sap.com wrote: Dear ASF members, We would like to propose the OData project to the Incubator. The OData Proposal is available at: https://wiki.apache.org/incubator/ODataProposal We welcome your feedback and suggestions. JFTR , at present there is an ongoing effort to start working on an integration of the oData standards with Apache™ Bloodhound (similar to TracGVizPlugin [1]_ for Google Charts API ; I'll follow up with further details in a few days if this turns out to be useful / required ;) . This might also be added to the list of potential integrations in section «Relationships with Other Apache Products» . Therefore I'm curious and would like to know if some effort will be spent in building official Python bindings for oData . FWIW , the way I see it this project will be a very beneficial addition to the Apache ecosystem .. [1] trachacks:TracGvizPlugin (http://trac-hacks.org/wiki/TracGvizPlugin) -- Regards, Olemis. Apache™ Bloodhound contributor http://issues.apache.org/bloodhound Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/ Featured article: - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Creation of the Incubator Ombudsman
A paradox: The VP is not supposed to exercise authority in normal circumstances. Projects are supposed to have mentors that advocate for them. If a project comes 'to the ombudsman', whether that's the VP or not, what can this person do? All they can do is bring the matter to the community. If it's sensitive enough, to private@. The mentors can and should be doing this. So, if you ask me, this is just another way to avoid the problem of mentor-shortage. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Stratos proposal: is it possible to add another initial committer?
I have not closed the vote yet because it ran over the weekend. I did state I would leave it running into this week. As champion I have no objection to you adding Debo. Ultimately it reduces unnecessary traffic on this list since we won't have to formally vote him in. Ross On 17 June 2013 18:37, Sanjiva Weerawarana sanj...@wso2.com wrote: Debo Dutta, cc'ed, from Cisco, will be joining the project and it took a bit of time to get it sorted. I realize this is a late request as the VOTE is already running .. is it ok to add him now? ;-) If not we will bring him after the project starts. Cheers, Sanjiva. -- Sanjiva Weerawarana, Ph.D. Founder, Chairman CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Stratos proposal: is it possible to add another initial committer?
On Mon, Jun 17, 2013 at 10:37 AM, Sanjiva Weerawarana sanj...@wso2.com wrote: Debo Dutta, cc'ed, from Cisco, will be joining the project and it took a bit of time to get it sorted. I realize this is a late request as the VOTE is already running .. is it ok to add him now? ;-) If not we will bring him after the project starts. Voting in a new committer is a useful exercise for a fledgling PPMC. Think of this as an opportunity. :) Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Stratos proposal: is it possible to add another initial committer?
C'mon Marvin. The project has enough ASF committers on the initial commiter list (ignoring mentors) to be able to conduct a committer vote. Lets not add unnecessary bureaucracy during the initial set-up phase. Ross On 17 June 2013 19:01, Marvin Humphrey mar...@rectangular.com wrote: On Mon, Jun 17, 2013 at 10:37 AM, Sanjiva Weerawarana sanj...@wso2.com wrote: Debo Dutta, cc'ed, from Cisco, will be joining the project and it took a bit of time to get it sorted. I realize this is a late request as the VOTE is already running .. is it ok to add him now? ;-) If not we will bring him after the project starts. Voting in a new committer is a useful exercise for a fledgling PPMC. Think of this as an opportunity. :) Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Stratos proposal: is it possible to add another initial committer?
Added Debo to the initial committer list. Azeez On Mon, Jun 17, 2013 at 11:30 PM, Ross Gardler rgard...@opendirective.comwrote: I have not closed the vote yet because it ran over the weekend. I did state I would leave it running into this week. As champion I have no objection to you adding Debo. Ultimately it reduces unnecessary traffic on this list since we won't have to formally vote him in. Ross On 17 June 2013 18:37, Sanjiva Weerawarana sanj...@wso2.com wrote: Debo Dutta, cc'ed, from Cisco, will be joining the project and it took a bit of time to get it sorted. I realize this is a late request as the VOTE is already running .. is it ok to add him now? ;-) If not we will bring him after the project starts. Cheers, Sanjiva. -- Sanjiva Weerawarana, Ph.D. Founder, Chairman CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com, *Member; Apache Software Foundation; **http://www.apache.org/*http://www.apache.org/ * * *email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* * *
Re: Stratos proposal: is it possible to add another initial committer?
I'm also not worried about figuring out how to do stuff .. :-). Sanjiva. On Mon, Jun 17, 2013 at 11:34 PM, Ross Gardler rgard...@opendirective.comwrote: C'mon Marvin. The project has enough ASF committers on the initial commiter list (ignoring mentors) to be able to conduct a committer vote. Lets not add unnecessary bureaucracy during the initial set-up phase. Ross On 17 June 2013 19:01, Marvin Humphrey mar...@rectangular.com wrote: On Mon, Jun 17, 2013 at 10:37 AM, Sanjiva Weerawarana sanj...@wso2.com wrote: Debo Dutta, cc'ed, from Cisco, will be joining the project and it took a bit of time to get it sorted. I realize this is a late request as the VOTE is already running .. is it ok to add him now? ;-) If not we will bring him after the project starts. Voting in a new committer is a useful exercise for a fledgling PPMC. Think of this as an opportunity. :) Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Sanjiva Weerawarana, Ph.D. Founder, Chairman CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware
Re: [DISCUSS] PodlingBillOfRights
- Original Message - From: Roman Shaposhnik r...@apache.org To: Joseph Schaefer joe_schae...@yahoo.com Cc: general@incubator.apache.org Sent: Monday, June 17, 2013 2:02 AM Subject: Re: [DISCUSS] PodlingBillOfRights On Sun, Jun 16, 2013 at 10:48 PM, Joseph Schaefer joe_schae...@yahoo.com wrote: The typical escalation path is either board@ or board-private@ assuming private messages to the chair are ineffective. Most of the time, for most of our projects, this has worked well enough. So isn't learning this bit of information a crucial part of graduation? After all, once the project leaves the incubator its commiters and PMC won't have an access to the Ombudsman, isn't it in all of our best interest to teach them from the get-go what you've just described above? Not really, because the type of information we're looking for is about the IPMC, not the podling. What's the danger of hooking up poddlings to the very channels they should be using once they graduate? The real issue for the IPMC boils down to the judgement call of whether the standard escalation procedures are working to everyone's satisfaction, Do we have real indication they are not? Isn't this an academic question? Those of us that have been here a while have seen any number of cases where podling committers feel frustrated about the process and powerless to do anything about it. This isn't a new problem. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Stratos proposal: is it possible to add another initial committer?
Thanks a lot Sanjiva, Ross, Afkham! debo From: Afkham Azeez afk...@gmail.commailto:afk...@gmail.com Date: Tue, 18 Jun 2013 00:05:14 +0530 To: general@incubator.apache.orgmailto:general@incubator.apache.org Cc: Debo~ Dutta dedu...@cisco.commailto:dedu...@cisco.com Subject: Re: Stratos proposal: is it possible to add another initial committer? Added Debo to the initial committer list. Azeez On Mon, Jun 17, 2013 at 11:30 PM, Ross Gardler rgard...@opendirective.commailto:rgard...@opendirective.com wrote: I have not closed the vote yet because it ran over the weekend. I did state I would leave it running into this week. As champion I have no objection to you adding Debo. Ultimately it reduces unnecessary traffic on this list since we won't have to formally vote him in. Ross On 17 June 2013 18:37, Sanjiva Weerawarana sanj...@wso2.commailto:sanj...@wso2.com wrote: Debo Dutta, cc'ed, from Cisco, will be joining the project and it took a bit of time to get it sorted. I realize this is a late request as the VOTE is already running .. is it ok to add him now? ;-) If not we will bring him after the project starts. Cheers, Sanjiva. -- Sanjiva Weerawarana, Ph.D. Founder, Chairman CEO; WSO2, Inc.; http://wso2.com/ email: sanj...@wso2.commailto:sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311 blog: http://sanjiva.weerawarana.org/ Lean . Enterprise . Middleware - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.orgmailto:general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.orgmailto:general-h...@incubator.apache.org -- Afkham Azeez Director of Architecture; WSO2, Inc.; http://wso2.com, Member; Apache Software Foundation; http://www.apache.org/ email: az...@wso2.commailto:az...@wso2.com cell: +94 77 3320919 blog: http://blog.afkham.org twitter: http://twitter.com/afkham_azeez linked-in: http://lk.linkedin.com/in/afkhamazeez Lean . Enterprise . Middleware
Re: [DISCUSS] PodlingBillOfRights
On Mon, Jun 17, 2013 at 11:48 AM, Joe Schaefer joe_schae...@yahoo.com wrote: So isn't learning this bit of information a crucial part of graduation? After all, once the project leaves the incubator its commiters and PMC won't have an access to the Ombudsman, isn't it in all of our best interest to teach them from the get-go what you've just described above? Not really, because the type of information we're looking for is about the IPMC, not the podling. Perhaps I misunderstood your idea with this new Ombudsman, but to me it sounded like you wanted, above all, a *safe* way for podling to complain. IOW, a kind of a way where their complaints will be heard yet their identity protected. If that's not your primary concern -- then I really feel like an Ombudsman represented yet another layer of bureaucracy and as such I'd be -0 on it. Isn't this an academic question? Those of us that have been here a while have seen any number of cases where podling committers feel frustrated about the process and powerless to do anything about it. This isn't a new problem. As you probably noticed, I've only started this discussion in the context of a PodlingBillOfRights. You did a great job of *reminding* podlings of their rights. Note, that just like in criminal law -- not reading somebody their Miranda rights doesn't mean they don't have them -- but reading them does make a huge difference. I think we can all agree that podlings already have those rights -- we are just making it really explicit. In that line of thought, what's not clear to me is what would be the difference if we changed your right #5 to: == 5. Podlings have the right to express private concerns about anything related to their incubation to their mentors and in private to the IPMC chair (email goes here). If they feel their concerns are still not being addressed they have a right to escalate to priv...@incubator.apache.org or all the way to the ASF board at board-priv...@apache.org This is the same right as given to all ASF project members. == Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Change of Chair
On Thu, Jun 13, 2013 at 11:03 PM, Benson Margulies bimargul...@gmail.com wrote: ...I have tendered my resignation as VP, Incubator. The PMC has recommend Marvin Humphrey as my successor in a motion submitted to the Foundation board for consideration at the meeting next week Many thanks Benson for your service at a time when the Incubator PMC has been a bit...difficult. Welcome Marvin, happy to see you taking this role! -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Creation of the Incubator Ombudsman
On Jun 17, 2013, at 10:58 AM, Benson Margulies bimargul...@gmail.com wrote: A paradox: The VP is not supposed to exercise authority in normal circumstances. Projects are supposed to have mentors that advocate for them. If a project comes 'to the ombudsman', whether that's the VP or not, what can this person do? All they can do is bring the matter to the community. If it's sensitive enough, to private@. The mentors can and should be doing this. So, if you ask me, this is just another way to avoid the problem of mentor-shortage. Unless the problem is with an over active mentor or absentee/problem VP. An ombudsman frees the Incubator from having to enumerate and codify every single circumstance where things go wrong and what would the official remedy be. The ombudsman would be the go to person when podlings are having problems w/ the management that everyone on this thread seems to think should be the point people to begin with. 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.12.0-incubating (RC1)
+1 (verified checksum and signature, checked LICENSE, NOTICE, DISCLAIMER). Tom On Tue, Jun 11, 2013 at 1:05 AM, Benjamin Mahler benjamin.mah...@gmail.com wrote: Please vote on releasing the following candidate as Apache Mesos (incubating) version 0.12.0. This will be the fourth incubator release for Mesos in Apache. The candidate for Mesos 0.12.0-incubating release is available at: http://people.apache.org/~bmahler/mesos-0.12.0-incubating-RC1/mesos-0.12.0-incubating.tar.gz The tag to be voted on is 0.12.0-rc1: https://git-wip-us.apache.org/repos/asf?p=incubator-mesos.git;a=tag;h=57d7b9719dce662881b162eba10b5765a807d53c The MD5 checksum of the tarball can be found at: http://people.apache.org/~bmahler/mesos-0.12.0-incubating-RC1/mesos-0.12.0-incubating.tar.gz.md5 The signature of the tarball can be found at: http://people.apache.org/~bmahler/mesos-0.12.0-incubating-RC1/mesos-0.12.0-incubating.tar.gz.asc PGP key used to sign the release: http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xD0BEBB95D141A5B6 Please vote on releasing this package as Apache Mesos 0.12.0-incubating! The vote is open until Thursday, June 13th at 00:00 UTC and passes if a majority of at least 3 +1 IPMC votes are cast. [ ] +1 Release this package as Apache Mesos 0.12.0-incubating [ ] -1 Do not release this package because ... To learn more about Apache Mesos, please see http://incubator.apache.org/mesos. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache ODF Toolkit 0.6-incubating(RC6)
Hi all, thank you all for finally getting our long anticipated release out. These are the results of the vote: From IPMC members: +1 Dave Fisher +1 Nick Burch +1 Joe Brockmeier From PPMC members: +1 Rob Weir +1 Oliver Rau +1 Florian Hopf Other: +1 Ian C Regards Florian On 06.06.2013 07:43, Florian Hopf wrote: Hi all, RC 6 of the ODF Toolkit 0.6-incubating is ready for release. We restructured the distribution so that only the source zips are in the top level directory. Also we updated the distributed KEYS file so the release can be verified. We had a successful vote in the PPMC and already one IPMC +1 from Dave Fisher. The vote result is here: http://markmail.org/message/6l4nmnhpf4rw6zol We need two more IPMC votes to pass. Please vote on releasing the following candidate as Apache ODF Toolkit (incubating) version 0.6. http://people.apache.org/~fhopf/odftoolkit-release/0.6-incubating-rc6/ The release artifacts are build from this tag in SVN: https://svn.apache.org/repos/asf/incubator/odf/tags/0.6-incubating-rc6/ The keys that are used for signing our releases can be found here: http://www.apache.org/dist/incubator/odftoolkit/KEYS The change notes for 0.6-incubating can be found at here: https://svn.apache.org/repos/asf/incubator/odf/tags/0.6-incubating-rc6/CHANGES.txt The vote is open for 72 hours, or until we get the needed number of votes (3 +1). [ ] +1 Release this package as Apache ODF Toolkit 0.6-incubating [ ] -1 Do not release this package because... To learn more about Apache ODF Toolkit, please visit http://incubator.apache.org/odftoolkit/. Regards Florian -- Florian Hopf Freelance Software Developer http://blog.florian-hopf.de - 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.12.0-incubating (RC1)
Hey Ben, Looks like we got a 3rd +1 from Tom W -- woot -- so we can proceed :) Way to put a cherry on top since we're pushing on graduating now too! Great work guys. Cheers, Chris ++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++ -Original Message- From: Benjamin Mahler benjamin.mah...@gmail.com Date: Monday, June 17, 2013 12:12 PM To: mesos-...@incubator.apache.org mesos-...@incubator.apache.org, general@incubator.apache.org general@incubator.apache.org, jpluser chris.a.mattm...@jpl.nasa.gov Subject: Re: [VOTE] Release Apache Mesos 0.12.0-incubating (RC1) +chris Hey Chris, looks like we're stalled on releasing again. What are the rules for a lack of IPMC participation in the 72 hour window? Can we proceed? On Fri, Jun 14, 2013 at 11:09 AM, Benjamin Mahler bmah...@twitter.com wrote: Unfortunately 0.12.0 was at a point where we had flaky tests, we're in much better shape these days! (0.13.0 and later) Alright, just one additional binding vote needed!! Hopefully we can get that quickly and start preparing to release 0.13.0. On Thu, Jun 13, 2013 at 11:27 PM, Andy Konwinski andykonwin...@gmail.com wrote: Yeah, after running the tests a few more times I saw a couple different tests fail and eventually in one run of `make check` they all passed. Here's the play-by-play: I ran the tests again and they hung here for at least 10 min: MacbookAir:build andyk$ make check Making check in . make[1]: Nothing to be done for `check-am'. Making check in third_party make check-recursive Making check in libprocess Making check in third_party make check-am make libgmock.la http://libgmock.la make[6]: `libgmock.la http://libgmock.la' is up to date. Making check in . make tests make[5]: `tests' is up to date. make check-TESTS Then again, and a different test failed in libprocess after a few seconds: MacbookAir:build andyk$ cat third_party/libprocess/test-suite.log ... [ RUN ] Statistics.truncate ../../../third_party/libprocess/src/tests/statistics_tests.cpp:58: Failure Expected: (Clock::now()) = (values.get().begin()-first.secs()), actual: 1.37119e+09 vs 1.37119e+09 ../../../third_party/libprocess/src/tests/statistics_tests.cpp:71: Failure Expected: (Clock::now()) = (values.get().begin()-first.secs()), actual: 1.37128e+09 vs 1.37128e+09 [ FAILED ] Statistics.truncate (1 ms) Then they all passed! Glad to know the flakey tests are known issues and being worked on in a future release. +1 (non-binding) from me on this release. Andy On Thu, Jun 13, 2013 at 10:38 PM, Vinod Kone vinodk...@gmail.com wrote: is this test always failing or just flaky? we've fixed a bunch of our flaky tests in 0.13.0. On Thu, Jun 13, 2013 at 10:13 PM, Andy Konwinski andykonwin...@gmail.com wrote: I downloaded the tarball and it builds fine for me but `make check` doesn't succeed on OS X 10.8.3. Is this a known issue? I'll attach the test suite output and paste the output from the failing test below. Andy -- [ RUN ] ZooKeeperTest.MasterDetectorExpireSlaveZKSessionNewMaster 2013-06-13 22:07:44,372:5033(0x11747b000):ZOO_ERROR@handle_socket_error_msg@1603: Socket [127.0.0.1:51504 http://127.0.0.1:51504] zk retcode=-4, errno=64(Host is down): failed while receiving a server response 2013-06-13 22:07:44,375:5033(0x11726f000):ZOO_ERROR@handle_socket_error_msg@1603: Socket [127.0.0.1:51504 http://127.0.0.1:51504] zk retcode=-4, errno=64(Host is down): failed while receiving a server response 2013-06-13 22:07:44,377:5033(0x11726f000):ZOO_ERROR@handle_socket_error_msg@1621: Socket [127.0.0.1:51504 http://127.0.0.1:51504] zk retcode=-112, errno=70(Stale NFS file handle): sessionId=0x13f41150633 has expired. E0613 22:07:44.377506 220274688 detector.cpp:477] Master detector ((755)@ 192.168.1.104:51358 http://192.168.1.104:51358) failed to get masters: session expired ../../src/tests/zookeeper_tests.cpp:441: Failure Mock function called more times than expected - returning directly. Function call: newMasterDetected(@0x10d211c00 (758)@ 192.168.1.104:51358 http://192.168.1.104:51358) Expected: to be called once Actual: called twice - over-saturated and active 2013-06-13 22:07:47,707:5033(0x11747b000):ZOO_ERROR@handle_socket_error_msg@1621: Socket [127.0.0.1:51504 http://127.0.0.1:51504] zk retcode=-112, errno=70(Stale NFS file handle): sessionId=0x13f411506330002 has expired. [ FAILED ]
RE: [PROPOSAL] OData Proposal for Incubator
I think one concern here is appropriation of a generic, specified-tied name to an implementation, even a reference implementation. Apache OData seems over-reaching in that respect, especially since there are other projects, at ASF and elsewhere, that may employ OData bindings and services of one sort or another. -Original Message- From: Klevenz, Stephan [mailto:stephan.klev...@sap.com] Sent: Monday, June 17, 2013 08:36 AM To: general@incubator.apache.org Subject: [PROPOSAL] OData Proposal for Incubator Dear ASF members, We would like to propose the OData project to the Incubator. The OData Proposal is available at: https://wiki.apache.org/incubator/ODataProposal We welcome your feedback and suggestions. Thanks! Stephan Klevenz [ ... ] - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Creation of the Incubator Ombudsman
On Sun, Jun 16, 2013 at 8:55 PM, Alex Harui aha...@adobe.com wrote: Just curious, is the ombudsman not allowed to be a mentor for a podling? Otherwise, that podling doesn't have a safe third-party? Good point. Podlings are heavily dependent on their Mentors, especially for providing IPMC votes on releases. If you offend a Mentor and they leave, will you be able to find someone else from the limited pool of IPMC members? A reluctance to speak out is very understandable. Put another way, when the ombud is also a Mentor, the military-justice analogy seems valid. I suppose that if the IPMC Chair is not the same as the ombud, they could serve as a backup ombud. That would satisfy your concern so long as the ombud and the Chair aren't both Mentors for the same podling. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[RESULT] [VOTE] Graduation of Apache Mesos
Hi Folks, OK, this VOTE has passed with the following tallies: +1 Chris Mattmann* Vinod Kone Benjamin Hindman Benjamin Mahler Yan Xiu Deepal Jayasinghe Brenden Matthews Matei Zaharia Ant Elder* Konstantin Boudnik Christian Grobmeier* Henry Saputra* Alex Karasulu* Roman Shaposhnik* Alan Cabrera* * - indicates IPMC I'll go ahead and add the resolution to the board agenda for consideration at our June 2013 meeting. Cheers, Chris ++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++ -Original Message- From: Mattmann, jpluser chris.a.mattm...@jpl.nasa.gov Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Wednesday, June 12, 2013 1:03 PM To: general@incubator.apache.org general@incubator.apache.org Cc: mesos-...@incubator.apache.org mesos-...@incubator.apache.org Subject: [VOTE] Graduation of Apache Mesos Hi All, The Apache Mesos community is ready to graduate. They have added committers and PPMC members while in the Incubator; have made a few releases; are discussing their issues on list and in the Apache way, and are inclusive and representative of Apache's goals as a Foundation. I'm extremely happy to put them up for Incubator graduation. We've VOTEd as a community to move forward with this: DISCUSS thread here: http://s.apache.org/XAu VOTE thread here: http://s.apache.org/K8C VOTE RESULT: Message-ID: cdde1f13.d6ea1%chris.a.mattm...@jpl.nasa.gov Project Incubator status page here: http://incubator.apache.org/projects/mesos.html Board resolution pasted at bottom of email. Existing tallies from the community VOTE: +1 Chris Mattmann* Vinod Kone Benjamin Hindman Benjamin Mahler Yan Xiu Deepal Jayasinghe Brenden Matthews Matei Zaharia Ant Elder* Konstantin Boudnik * - indicates IPMC Please VOTE to graduate Apache Mesos from the Incubator. Though only Incubator PMC member VOTEs are binding, all are welcome to voice your opinion. I'll leave the VOTE open for at least 72 hours, and hopefully can get enough VOTEs in time to close it by Saturday or Sunday in time for the board meeting on 6/19. [ ] +1 Graduate Apache Mesos from the Incubator. [ ] +0 Don't care. [ ] -1 Don't graduate Apache Mesos from the Incubator because.. Thanks everyone! Cheers, Chris ---board resolution 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 efficient cluster management, resource isolation and sharing across distributed applications. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Mesos Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Mesos Project be and hereby is responsible for the creation and maintenance of software related to efficient cluster management, resource isolation and sharing across distributed applications; and be it further RESOLVED, that the office of Vice President, Apache Mesos 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 Mesos Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Mesos 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 Mesos Project: * Ali Ghodsi a...@apache.org * Andy Konwinski and...@apache.org * Benjamin Hindhman b...@apache.org * Benjamin Mahler bmah...@apache.org * Brian McCalister bri...@apache.org * Ian Holsman i...@apache.org * Matei Alexandru Zahari ma...@apache.org * Chris Mattmann mattm...@apache.org * Tom White tomwh...@apache.org * Vinod Kone vinodk...@apache.org * Brenden Matthews bren...@apache.org * Thomas Marshall tmarsh...@apache.org * Charles Reiss wog...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Benjamin Hindman be appointed to the office of Vice President, Apache Mesos, 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 Apache Mesos Project be and hereby is tasked with the migration and rationalization
Re: [PROPOSAL] Creation of the Incubator Ombudsman
I'm not in favor of an Ombudsman. Seems like an extra layer of overhead beyond what the Chair already provides. Seriously does someone need a title in order to be the clearinghouse for folks' honest assessments of the Incubator, its personnel, or other sensitive issues? My 2c. Cheers, Chris ++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++ -Original Message- From: Marvin Humphrey mar...@rectangular.com Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Monday, June 17, 2013 7:11 PM To: general@incubator.apache.org general@incubator.apache.org Subject: Re: [PROPOSAL] Creation of the Incubator Ombudsman On Sun, Jun 16, 2013 at 8:55 PM, Alex Harui aha...@adobe.com wrote: Just curious, is the ombudsman not allowed to be a mentor for a podling? Otherwise, that podling doesn't have a safe third-party? Good point. Podlings are heavily dependent on their Mentors, especially for providing IPMC votes on releases. If you offend a Mentor and they leave, will you be able to find someone else from the limited pool of IPMC members? A reluctance to speak out is very understandable. Put another way, when the ombud is also a Mentor, the military-justice analogy seems valid. I suppose that if the IPMC Chair is not the same as the ombud, they could serve as a backup ombud. That would satisfy your concern so long as the ombud and the Chair aren't both Mentors for the same podling. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
