Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
On Tue, Jul 21, 2015 at 4:08 AM, amareshwarisr . amareshw...@gmail.com wrote: Seems the DESCRIPTION_AND_SCOPE of the project is set to the automated and managed flow of information between systems. I dont see any such on project website - http://ignite.incubator.apache.org/ Looks like a copy from NIFI's graduation discussion - http://mail-archives.apache.org/mod_mbox/incubator-general/201506.mbox/%3CCALJK9a4PD%2B3qGGQbbHHyLfY8Ut9BP9VyEDwtnZDSWjpMKiwk9w%40mail.gmail.com%3E . You might want to correct it. Yup, copy-n-paste never works :) Corrected below. Correct me if description is fine and I'm wrong in understanding the description Thanks Amareshwari On Tue, Jul 21, 2015 at 5:06 AM, Dmitriy Setrakyan dsetrak...@apache.org wrote: Hello Apache Incubator, At the suggestion of our mentors the Ignite community established consensus and held a successful vote with 14 +1 votes in favor of proposing graduation to TLP. Vote thread: http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Graduate-Apache-Ignite-from-Incubation-td1539.html Summary of the vote results: +1 (non-binding) = 14 1. Yakov Zhdanov (PMC) 2. Gianfranco Murador (PMC) 3. Ira Vasilinets (PMC) 4. Nikolai Tichinov (PMC) 5. Semyon Boikov (PMC) 6. Sergi Vladykin (PMC) 7. Alexey Goncharuk (PMC) 8. Ognen Duzlevski (PMC) 9. Valentin Kulichenko (PMC) 10. Nikita Ivanov (PMC) 11. Dmitriy Setrakyan (PMC) 12. Andrey Novikov (Committer) 13. Alexey Kuznetsov (Committer) 14. Milap Wadwa We’d like to initiate this discussion/proposal to establish a consensus within the incubator and if appropriate will initiate a vote. Below is our proposed resolution: Thank you Dmitriy Setrakyan(on behalf of the Apache Ignite PPMC) SUBJECT: Establish the Apache Ignite TLP 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 the automated and managed flow of information between systems. Should be: - related to delivering an In-Memory Data Fabric - a high-performance, integrated and distributed in-memory platform for computing and transacting on large-scale data sets in real-time NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Ignite Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Ignite Project be and hereby is responsible for the creation and maintenance of software related to the automated and managed flow of information between systems and be it further RESOLVED, that the office of Vice President, Apache Ignite 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 Ignite Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Ignite 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 Ignite Project: Semyon Boikov (sboi...@apache.org) Konstantin Boudnik (c...@apache.org) Branko Čibej (br...@apache.org) Ognen Duzlevski (mak...@apache.org) Sergey Evdokimov (sevdoki...@apache.org) Alexey Goncharuk (agoncha...@apache.org) Nikita Ivanov (nivano...@apache.org) Sergey Khisamov (s...@apache.org) Valentin Kulichenko (vkuliche...@apache.org) Alexey Kuznetsov (akuznet...@apache.org) Gianfranco Murador (mura...@apache.org) Andrey Novikov (anovi...@apache.org) Vladimir Ozerov (voze...@apache.org) Dmitriy Setrakyan (dsetrak...@apache.org) Roman Shaposhnik (r...@apache.org) Ilya Sterin (iste...@apache.org) Nikolai Tikhonov (ntikho...@apache.org) Irina Vasilinets (ivasilin...@apache.org) Anton Vinogradov (a...@apache.org) Sergey Vladykin (svlady...@apache.org) Evans Ye (evan...@apache.org) Yakov Zhdanov (yzhda...@apache.org) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Dmitriy Setrakyan be appointed to the office of Vice President, Apache Ignite, 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 Ignite PMC be and hereby is tasked with the creation of a set of
[RESULT] [VOTE] Apache Ignite 1.3.0 release (RC2)
Hello! Apache Ignite 1.3.0 release (RC2) has been accepted. Here are the votes received: - Justin Mclean (binding) - Konstantin Boudnik (binding) - Branko Cibej (binding) - Sergey Khisamov - Nick Tikhonov - Ira Vasilinets - Semyon Boikov - Alex Kuznetsov - Yakov Zhdanov Thanks! --Yakov
Re: Kylin mentor
Hi Luke, I’d be willing to act as a mentor to Kylin. If that’s okay with the Kylin community, let me know and I’ll update appropriate files. -Taylor On Jul 21, 2015, at 3:13 AM, Luke Han luke...@apache.org wrote: Thanks Julian to step up, as previous advisor, you already give us a lot of help and guide. Really appreciated to be Apache Kylin's official mentor. If anyone else would like to help us, please also leave message here. Thank you very much. Luke On Tue, Jul 21, 2015 at 10:30 AM, Julian Hyde jh...@apache.org wrote: Done. Thanks. On Jul 20, 2015, at 2:02 PM, Marvin Humphrey mar...@rectangular.com wrote: On Mon, Jul 20, 2015 at 1:45 PM, Julian Hyde jh...@apache.org wrote: The Kylin project has said that they would like more mentors. I have been mentoring unofficially for a while, and am happy to become an official mentor. I am already an IPMC member. Sounds great! There's no formal process for adding Mentors beyond gauging the consent of the podling community. Please add yourself as a Kylin Mentor to... * content/podlings.xml * content/projects/kylin.xml 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 signature.asc Description: Message signed with OpenPGP using GPGMail
Re: [VOTE] Release Apache Twill-0.6.0-incubating
Signature file looks good Hash files look good LICENSE file looks good NOTICE file looks good DISCLAIMER file exist Source compiled and passed tests +1 (binding) Good job guys - Henry On Tue, Jul 21, 2015 at 3:36 AM, Terence Yim cht...@apache.org wrote: Hi all, This is to call for a vote on releasing Apache Twill 0.6.0-incubating. This is the seventh release for Twill. Apache Twill is an abstraction over Apache Hadoop YARN that reduces the complexity of developing distributed applications. Vote on twill-dev: http://s.apache.org/ABI Result on vote on twill-dev: http://s.apache.org/Hk4 The source tarball, including signatures, digests, etc. can be found at: https://dist.apache.org/repos/dist/dev/incubator/twill/0.6.0-incubating-rc2/src The tag to be voted upon is v0.6.0-incubating: https://git-wip-us.apache.org/repos/asf?p=incubator-twill.git;a=shortlog;h=refs/tags/v0.6.0-incubating The release hash is 518cc1a24c1ae29e46b58debe0f1a177d1589321: https://git-wip-us.apache.org/repos/asf?p=incubator-twill.git;a=commit;h=518cc1a24c1ae29e46b58debe0f1a177d1589321 The Nexus Staging URL: https://repository.apache.org/content/repositories/orgapachetwill-1017 Release artifacts are signed with the following key: https://people.apache.org/keys/committer/chtyim.asc KEYS file available: https://dist.apache.org/repos/dist/dev/incubator/twill/KEYS For information about the contents of this release, see: https://dist.apache.org/repos/dist/dev/incubator/twill/0.6.0-incubating-rc1/CHANGES.txt Please vote on releasing this package as Apache Twill 0.6.0-incubating The vote will be open for 72 hours. [ ] +1 Release this package as Apache Twill 0.6.0-incubating [ ] +0 no opinion [ ] -1 Do not release this package because ... Thanks, The Apache Twill Team - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
It seems that 63% of the podling's PMC is affiliated to 1 organisation (Gridgrain). Have sufficient grounds been covered to ensure diversity and independece? Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Tue, Jul 21, 2015 at 5:13 PM, Dmitriy Setrakyan dsetrak...@apache.org wrote: On Tue, Jul 21, 2015 at 4:08 AM, amareshwarisr . amareshw...@gmail.com wrote: Seems the DESCRIPTION_AND_SCOPE of the project is set to the automated and managed flow of information between systems. I dont see any such on project website - http://ignite.incubator.apache.org/ Looks like a copy from NIFI's graduation discussion - http://mail-archives.apache.org/mod_mbox/incubator-general/201506.mbox/%3CCALJK9a4PD%2B3qGGQbbHHyLfY8Ut9BP9VyEDwtnZDSWjpMKiwk9w%40mail.gmail.com%3E . You might want to correct it. Yup, copy-n-paste never works :) Corrected below. Correct me if description is fine and I'm wrong in understanding the description Thanks Amareshwari On Tue, Jul 21, 2015 at 5:06 AM, Dmitriy Setrakyan dsetrak...@apache.org wrote: Hello Apache Incubator, At the suggestion of our mentors the Ignite community established consensus and held a successful vote with 14 +1 votes in favor of proposing graduation to TLP. Vote thread: http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Graduate-Apache-Ignite-from-Incubation-td1539.html Summary of the vote results: +1 (non-binding) = 14 1. Yakov Zhdanov (PMC) 2. Gianfranco Murador (PMC) 3. Ira Vasilinets (PMC) 4. Nikolai Tichinov (PMC) 5. Semyon Boikov (PMC) 6. Sergi Vladykin (PMC) 7. Alexey Goncharuk (PMC) 8. Ognen Duzlevski (PMC) 9. Valentin Kulichenko (PMC) 10. Nikita Ivanov (PMC) 11. Dmitriy Setrakyan (PMC) 12. Andrey Novikov (Committer) 13. Alexey Kuznetsov (Committer) 14. Milap Wadwa We’d like to initiate this discussion/proposal to establish a consensus within the incubator and if appropriate will initiate a vote. Below is our proposed resolution: Thank you Dmitriy Setrakyan(on behalf of the Apache Ignite PPMC) SUBJECT: Establish the Apache Ignite TLP 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 the automated and managed flow of information between systems. Should be: - related to delivering an In-Memory Data Fabric - a high-performance, integrated and distributed in-memory platform for computing and transacting on large-scale data sets in real-time NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Ignite Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Ignite Project be and hereby is responsible for the creation and maintenance of software related to the automated and managed flow of information between systems and be it further RESOLVED, that the office of Vice President, Apache Ignite 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 Ignite Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Ignite 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 Ignite Project: Semyon Boikov (sboi...@apache.org) Konstantin Boudnik (c...@apache.org) Branko Čibej (br...@apache.org) Ognen Duzlevski (mak...@apache.org) Sergey Evdokimov (sevdoki...@apache.org) Alexey Goncharuk (agoncha...@apache.org) Nikita Ivanov (nivano...@apache.org) Sergey Khisamov (s...@apache.org) Valentin Kulichenko (vkuliche...@apache.org) Alexey Kuznetsov (akuznet...@apache.org) Gianfranco Murador (mura...@apache.org) Andrey Novikov (anovi...@apache.org) Vladimir Ozerov (voze...@apache.org) Dmitriy Setrakyan (dsetrak...@apache.org) Roman Shaposhnik (r...@apache.org) Ilya Sterin (iste...@apache.org) Nikolai Tikhonov (ntikho...@apache.org) Irina Vasilinets (ivasilin...@apache.org) Anton Vinogradov (a...@apache.org) Sergey Vladykin (svlady...@apache.org) Evans Ye (evan...@apache.org) Yakov
Re: [VOTE] Release Apache Zeppelin (incubating) 0.5.0-incubating
Got it, thank you very much, Justin, for the explanation! On behalf of the Apache Zeppelin (incubating) PPMC I have contacted the original author and he agreed to contribute this code, with the proper Apache 2.0 licence header, directly to the Apache Zeppelin (incubating) codebase as a separate patch. So it is going to be resolved completely, together with 2 other issues raised here, over the next release. Edward J. Yoon, does this explanation and actions taken make you more comfortable with changing your opinion\vote? Please let us know. Thanks in advance. -- Kind regards, Alexander On Wed, Jul 22, 2015 at 1:20 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, Regarding the issue raised by Edward - we were under impression that this particular contribution is covered by https://github.com/apache/incubator-zeppelin/blob/master/NOTICE#L53 (as we use the code from https://code.google.com/p/selenium/issues/detail?id=1361 that was not merged to the selenium, keeping the attribution) It depends on how that original code is licensed and if you have permission to use the code from the author. I don't know the exact particulars, and it may be fine, but it seem unclear to me. This probably doesn’t have to be sorted in the this release but would need to be sorted before graduation, but other IPMC member may hold different opinions. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- -- Kind regards, Alexander. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [NOTICE] Yetus TLP proposal
Added. Thanks for the suggestion David. On Sun, Jul 19, 2015 at 11:57 AM, David Nalley da...@gnsa.us wrote: Please consider using commits@ - that's a well known design pattern that is used pervasively. If you need notifications@ in addition, that's okay too, but there are lots of things that assume commits@ --David On Fri, Jul 17, 2015 at 1:34 PM, Sean Busbey bus...@cloudera.com wrote: On Thu, Jul 16, 2015 at 4:50 PM, Henry Saputra henry.sapu...@gmail.com wrote: What is the notificati...@yetus.apache.org list for? - Henry internal build notifications, commits to git. basically all the automated message stuff. -- Sean - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Sean
Re: [RESULT] [VOTE] Apache Ignite 1.3.0 release (RC2)
Apache Ignite 1.3.0 released. Maven artifacts released, sources and convenience binaries moved to svn/~/release, site updated. On Tue, Jul 21, 2015 at 7:34 PM, Yakov Zhdanov yzhda...@apache.org wrote: Hello! Apache Ignite 1.3.0 release (RC2) has been accepted. Here are the votes received: - Justin Mclean (binding) - Konstantin Boudnik (binding) - Branko Cibej (binding) - Sergey Khisamov - Nick Tikhonov - Ira Vasilinets - Semyon Boikov - Alex Kuznetsov - Yakov Zhdanov Thanks! --Yakov
Re: [VOTE] Release Apache Zeppelin (incubating) 0.5.0-incubating
Thanks to Justin for his thorough review, as always. I have pinged back the Apache Zeppelin community to see if we could quickly address the issue. - Henry On Mon, Jul 20, 2015 at 9:58 PM, Edward J. Yoon edwardy...@apache.org wrote: Has the author of zeppelin-server/src/test/java/com/webautomation/ScreenCaptureHtmlUnitDriver.java signed a ICLA? It looks like came from Selenium community - https://groups.google.com/forum/#!searchin/selenium-developers/Ivan$20Vasiliev$20%7Csort:relevance/selenium-developers/PTR_j4xLVRM/k2yVq01Fa7oJ If license header can't be attached discretionally by a third party, I don't think this can be included. -1 (binding) I think it'd be nice to fix every LICENSE and NOTICE issues. On Sun, Jul 19, 2015 at 9:33 AM, Justin Mclean jus...@classsoftware.com wrote: Hi, +1 binding Please fix the LICENSE/NOTICE issues are fixed for next release. Given everything involved is Apache comparable it's more a documentation issue but still important to get right. If you need a hand or need it reviewed before your next release just ask. The LICENSE/NOTICE issues and missing DISCLAIMER from the binary files is more serious and IMO they shouldn’t be released but I’ll leave that up to the PMC/IPMC. I checked: - signatures and hashes good - incubating in source file - DISCLAIMER exists - LICENSE isn’t correct (see below) - NOTICE also has issues (see below) - All source has apache headers (except one) - No unexpected binary files - Can compile from source LICENSE and NOTICE issues - LICENSE states Copyright 2014, NFLabs inc.” when it should be ASF and specified in the NOTICE file. - NOTICE contains Font Awesome (SIL + MIT), Ace (BSD), Simple line icons (MIT) but there is no need for these to be in NOTICE [1] - LICENSE should contain things mentioned in NOTICE [1] - Has the author of zeppelin-server/src/test/java/com/webautomation/ScreenCaptureHtmlUnitDriver.java signed a ICLA? I notice it’s missing a header and it’s not 100% clear to me what it’s licensing is. For the binary release: - Missing NOTICE and DISCLAIMER from top level directory - Unadorned LICENSE and NOTICE in META_INF or jar and war so not correct, please see [2]. There's several NOTICE files in the libs jars that would have an impact on the binary NOTICE file [3] Thanks, Justin 1. http://www.apache.org/dev/licensing-howto.html#permissive-deps 2. http://www.apache.org/dev/licensing-howto.html#binary 3. http://www.apache.org/dev/licensing-howto.html#alv2-dep - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Best Regards, Edward J. Yoon - 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: [DISCUSS] Diversity policy (WAS: Re: [DISCUSSION] Graduate Ignite from the Apache Incubator)
On Tue, Jul 21, 2015 at 4:56 PM, Daniel Gruno humbed...@apache.org wrote: If by this you mean the Incubator has taught the podling what it needs to know, and the podling is following the best practices of the Apache Way, then we are in full agreement. I don't see the need to single me out here, I am not disagreeing with that. Please don't feel singled out. The response was addressed to you because you had raised the question. There was a discussion 3 years ago about this, but it did not result in a change in our published policy. The policy is still there. Since the policy doesn't document the current consensus, could you draft an update? A discussion of specific text is more likely to converge. -C If we are interested in changing that policy, we should agree on a change in a discussion with that as the main topic, and then _write it down_. We should not have to refer to discussions where this _may have come up off-topic or as a side note_, that is not fair to people trying to find out what our practices are. With regards, Daniel. They've completed a curriculum that clears their IP and introduces them to the ASF's infrastructure, procedures, and culture. The project must be open, and not threatened by the challenges that open development poses. We encourage transparency by creating a climate for projects to report honestly about diversity, rather than incentivizing corruption of that metric. As this thread demonstrates, the IPMC cannot do more. -C P.S. Please fix your quoting, or delete the tail of the message as you reply. [1] http://s.apache.org/uT4 [2] http://s.apache.org/m2u - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Zeppelin (incubating) 0.5.0-incubating
Hi, Regarding the issue raised by Edward - we were under impression that this particular contribution is covered by https://github.com/apache/incubator-zeppelin/blob/master/NOTICE#L53 (as we use the code from https://code.google.com/p/selenium/issues/detail?id=1361 that was not merged to the selenium, keeping the attribution) It depends on how that original code is licensed and if you have permission to use the code from the author. I don't know the exact particulars, and it may be fine, but it seem unclear to me. This probably doesn’t have to be sorted in the this release but would need to be sorted before graduation, but other IPMC member may hold different opinions. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
Chris, Thanks for bringing up the Tez discussion. I think that it was a great example of a community responding to questions and criticisms in a very open and evidence based manner. I was strongly -1 on that proposal originally based on similar grounds to what has been raised in this thread. The community responded and showed me how I was in error. The discussion was civil, but there were strong disagreements that were worked out over time. On my side, I was working enormously hard at the time and subject to jet-lag which made it very hard to respond well. My vote in the ensuing VOTE thread was +1 because of how the community responded. I was convinced that the community was open and welcoming and trying to build. The raw numbers about affiliation weren't the whole story by any stretch. On Tue, Jul 21, 2015 at 4:36 PM, Chris Douglas cdoug...@apache.org wrote: Daniel- This has been discussed recently in graduations for Tez [1], Drill [2], and other projects whose continued incubation serves no purpose. They've completed a curriculum that clears their IP and introduces them to the ASF's infrastructure, procedures, and culture. The project must be open, and not threatened by the challenges that open development poses. We encourage transparency by creating a climate for projects to report honestly about diversity, rather than incentivizing corruption of that metric. As this thread demonstrates, the IPMC cannot do more. -C P.S. Please fix your quoting, or delete the tail of the message as you reply. [1] http://s.apache.org/uT4 [2] http://s.apache.org/m2u - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Zeppelin (incubating) 0.5.0-incubating
Apologies for not timely response. Thank you Konstantin and Justin for your reviews - we have filed the issues to track that your feedback is going to be addressed https://issues.apache.org/jira/browse/ZEPPELIN-174 https://issues.apache.org/jira/browse/ZEPPELIN-175 Regarding the issue raised by Edward - we were under impression that this particular contribution is covered by https://github.com/apache/incubator-zeppelin/blob/master/NOTICE#L53 (as we use the code from https://code.google.com/p/selenium/issues/detail?id=1361 that was not merged to the selenium, keeping the attribution) Please let me know in case if that is not enough and we will be glad to address it asap to reconcile the -1. Thanks in advance! On Wed, Jul 22, 2015 at 2:46 AM, Henry Saputra henry.sapu...@gmail.com wrote: Thanks to Justin for his thorough review, as always. I have pinged back the Apache Zeppelin community to see if we could quickly address the issue. - Henry On Mon, Jul 20, 2015 at 9:58 PM, Edward J. Yoon edwardy...@apache.org wrote: Has the author of zeppelin-server/src/test/java/com/webautomation/ScreenCaptureHtmlUnitDriver.java signed a ICLA? It looks like came from Selenium community - https://groups.google.com/forum/#!searchin/selenium-developers/Ivan$20Vasiliev$20%7Csort:relevance/selenium-developers/PTR_j4xLVRM/k2yVq01Fa7oJ If license header can't be attached discretionally by a third party, I don't think this can be included. -1 (binding) I think it'd be nice to fix every LICENSE and NOTICE issues. On Sun, Jul 19, 2015 at 9:33 AM, Justin Mclean jus...@classsoftware.com wrote: Hi, +1 binding Please fix the LICENSE/NOTICE issues are fixed for next release. Given everything involved is Apache comparable it's more a documentation issue but still important to get right. If you need a hand or need it reviewed before your next release just ask. The LICENSE/NOTICE issues and missing DISCLAIMER from the binary files is more serious and IMO they shouldn’t be released but I’ll leave that up to the PMC/IPMC. I checked: - signatures and hashes good - incubating in source file - DISCLAIMER exists - LICENSE isn’t correct (see below) - NOTICE also has issues (see below) - All source has apache headers (except one) - No unexpected binary files - Can compile from source LICENSE and NOTICE issues - LICENSE states Copyright 2014, NFLabs inc.” when it should be ASF and specified in the NOTICE file. - NOTICE contains Font Awesome (SIL + MIT), Ace (BSD), Simple line icons (MIT) but there is no need for these to be in NOTICE [1] - LICENSE should contain things mentioned in NOTICE [1] - Has the author of zeppelin-server/src/test/java/com/webautomation/ScreenCaptureHtmlUnitDriver.java signed a ICLA? I notice it’s missing a header and it’s not 100% clear to me what it’s licensing is. For the binary release: - Missing NOTICE and DISCLAIMER from top level directory - Unadorned LICENSE and NOTICE in META_INF or jar and war so not correct, please see [2]. There's several NOTICE files in the libs jars that would have an impact on the binary NOTICE file [3] Thanks, Justin 1. http://www.apache.org/dev/licensing-howto.html#permissive-deps 2. http://www.apache.org/dev/licensing-howto.html#binary 3. http://www.apache.org/dev/licensing-howto.html#alv2-dep - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Best Regards, Edward J. Yoon - 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 -- -- Kind regards, Alexander. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
The so-called diversity requirement has been discussed on this list for a number of times. Most recent is the graduation of Flume project (back in 2012). Here's a quote from that thread (kudos to Roy; for those who want to look it up in the archives MessageId is 73db2e64-87d5-4dd5-91fb-403464895...@gbiv.com): [quote] There is no diversity requirement at the ASF. There is a behavior requirement for graduation and a behavior requirement for TLPs. We must not confuse the two. If the Incubator says that there is a diversity requirement for graduation, ignore it (or at least figure out what the docs were supposed to say and then do that). I'd urge folks to fix the docs, but I know where that leads ... and I have no cycles to spare. A diversity requirement would mean that a person's employment status impacts their ability to participate here. IOW, it would create a perverse incentive for them not to be employed. [/quote] Regards, Cos On Tue, Jul 21, 2015 at 05:55PM, Pierre Smits wrote: It seems that 63% of the podling's PMC is affiliated to 1 organisation (Gridgrain). Have sufficient grounds been covered to ensure diversity and independece? Best regards, Pierre Smits On Tue, Jul 21, 2015 at 5:13 PM, Dmitriy Setrakyan dsetrak...@apache.org wrote: On Tue, Jul 21, 2015 at 4:08 AM, amareshwarisr . amareshw...@gmail.com wrote: Seems the DESCRIPTION_AND_SCOPE of the project is set to the automated and managed flow of information between systems. I dont see any such on project website - http://ignite.incubator.apache.org/ Looks like a copy from NIFI's graduation discussion - http://mail-archives.apache.org/mod_mbox/incubator-general/201506.mbox/%3CCALJK9a4PD%2B3qGGQbbHHyLfY8Ut9BP9VyEDwtnZDSWjpMKiwk9w%40mail.gmail.com%3E . You might want to correct it. Yup, copy-n-paste never works :) Corrected below. Correct me if description is fine and I'm wrong in understanding the description Thanks Amareshwari On Tue, Jul 21, 2015 at 5:06 AM, Dmitriy Setrakyan dsetrak...@apache.org wrote: Hello Apache Incubator, At the suggestion of our mentors the Ignite community established consensus and held a successful vote with 14 +1 votes in favor of proposing graduation to TLP. Vote thread: http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Graduate-Apache-Ignite-from-Incubation-td1539.html Summary of the vote results: +1 (non-binding) = 14 1. Yakov Zhdanov (PMC) 2. Gianfranco Murador (PMC) 3. Ira Vasilinets (PMC) 4. Nikolai Tichinov (PMC) 5. Semyon Boikov (PMC) 6. Sergi Vladykin (PMC) 7. Alexey Goncharuk (PMC) 8. Ognen Duzlevski (PMC) 9. Valentin Kulichenko (PMC) 10. Nikita Ivanov (PMC) 11. Dmitriy Setrakyan (PMC) 12. Andrey Novikov (Committer) 13. Alexey Kuznetsov (Committer) 14. Milap Wadwa We’d like to initiate this discussion/proposal to establish a consensus within the incubator and if appropriate will initiate a vote. Below is our proposed resolution: Thank you Dmitriy Setrakyan(on behalf of the Apache Ignite PPMC) SUBJECT: Establish the Apache Ignite TLP 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 the automated and managed flow of information between systems. Should be: - related to delivering an In-Memory Data Fabric - a high-performance, integrated and distributed in-memory platform for computing and transacting on large-scale data sets in real-time NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Ignite Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Ignite Project be and hereby is responsible for the creation and maintenance of software related to the automated and managed flow of information between systems and be it further RESOLVED, that the office of Vice President, Apache Ignite 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 Ignite Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Ignite 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
Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
Actually, given that this project was a spin-out of an internal project, this is a stunningly low number to have achieved so quickly (assuming that the 37% are actually active, that is). Kudos. +1 On Tue, Jul 21, 2015 at 4:08 AM, amareshwarisr . amareshw...@gmail.com wrote: Seems the DESCRIPTION_AND_SCOPE of the project is set to the automated and managed flow of information between systems. I dont see any such on project website - http://ignite.incubator.apache.org/ Looks like a copy from NIFI's graduation discussion - http://mail-archives.apache.org/mod_mbox/incubator-general/201506.mbox/%3CCALJK9a4PD%2B3qGGQbbHHyLfY8Ut9BP9VyEDwtnZDSWjpMKiwk9w%40mail.gmail.com%3E . You might want to correct it. Correct me if description is fine and I'm wrong in understanding the description Thanks Amareshwari On Tue, Jul 21, 2015 at 5:06 AM, Dmitriy Setrakyan dsetrak...@apache.org wrote: Hello Apache Incubator, At the suggestion of our mentors the Ignite community established consensus and held a successful vote with 14 +1 votes in favor of proposing graduation to TLP. Vote thread: http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Graduate-Apache-Ignite-from-Incubation-td1539.html Summary of the vote results: +1 (non-binding) = 14 1. Yakov Zhdanov (PMC) 2. Gianfranco Murador (PMC) 3. Ira Vasilinets (PMC) 4. Nikolai Tichinov (PMC) 5. Semyon Boikov (PMC) 6. Sergi Vladykin (PMC) 7. Alexey Goncharuk (PMC) 8. Ognen Duzlevski (PMC) 9. Valentin Kulichenko (PMC) 10. Nikita Ivanov (PMC) 11. Dmitriy Setrakyan (PMC) 12. Andrey Novikov (Committer) 13. Alexey Kuznetsov (Committer) 14. Milap Wadwa We’d like to initiate this discussion/proposal to establish a consensus within the incubator and if appropriate will initiate a vote. Below is our proposed resolution: Thank you Dmitriy Setrakyan(on behalf of the Apache Ignite PPMC) SUBJECT: Establish the Apache Ignite TLP 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 the automated and managed flow of information between systems. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Ignite Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Ignite Project be and hereby is responsible for the creation and maintenance of software related to the automated and managed flow of information between systems and be it further RESOLVED, that the office of Vice President, Apache Ignite 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 Ignite Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Ignite 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 Ignite Project: Semyon Boikov (sboi...@apache.org) Konstantin Boudnik (c...@apache.org) Branko Čibej (br...@apache.org) Ognen Duzlevski (mak...@apache.org) Sergey Evdokimov (sevdoki...@apache.org) Alexey Goncharuk (agoncha...@apache.org) Nikita Ivanov (nivano...@apache.org) Sergey Khisamov (s...@apache.org) Valentin Kulichenko (vkuliche...@apache.org) Alexey Kuznetsov (akuznet...@apache.org) Gianfranco Murador (mura...@apache.org) Andrey Novikov (anovi...@apache.org) Vladimir Ozerov (voze...@apache.org) Dmitriy Setrakyan (dsetrak...@apache.org) Roman Shaposhnik (r...@apache.org) Ilya Sterin (iste...@apache.org) Nikolai Tikhonov (ntikho...@apache.org) Irina Vasilinets (ivasilin...@apache.org) Anton Vinogradov (a...@apache.org) Sergey Vladykin (svlady...@apache.org) Evans Ye (evan...@apache.org) Yakov Zhdanov (yzhda...@apache.org) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Dmitriy Setrakyan be appointed to the office of Vice President, Apache Ignite, 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 Ignite PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased
Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
I have seen top level projects, with majority of PMCs come from paid employees of a single company, suffer of growth and development when the employees of such company stop contributing to the project. Going back to Apache Ignite, since it is the main core of GridGain I doubt the project will be abandoned, unless the whole company shift gear or go bankrupt. The proposed PMCs also includes the mentors, which I could bring some check and balance to the project, and I know they have done great job bringing the Ignite initial committers to the Apache way. - Henry On Tue, Jul 21, 2015 at 2:29 PM, Daniel Gruno humbed...@apache.org wrote: While Roy is indeed a smart man, there is no BDFL in the ASF. Quoting Roy out of context is not a Hail Mary you can just throw out there when someone disagrees with you. Several people, including several IPMC members have expressed concerns. Address them properly instead of insisting on your way or the high way. The question of diversity in this case is not are we enough men/women/whatever, the question here is is there a single corporate entity with a deciding vote in the project?. What I am concerned with here is the responses to this. Instead of saying We don't believe that to be the case, the PPMC is saying there's no rule against that! as if there _is_ an issue but it's being swept under the rug. With regards, Daniel. On 2015-07-21 23:19, Roman Shaposhnik wrote: Please re-read the quote from Roy: There is no diversity requirement at the ASF. There is a behavior requirement for graduation and a behavior requirement for TLPs. We must not confuse the two. and later I'd urge folks to fix the docs, but I know where that leads ... and I have no cycles to spare. Thanks, Roman. On Tue, Jul 21, 2015 at 1:55 PM, jan i j...@apache.org wrote: On 21 July 2015 at 22:48, Daniel Gruno humbed...@apache.org wrote: On 07/21/2015 10:39 PM, Ted Dunning wrote: Present time diversity or lack of same is not a bar to graduation. So we should just scrap the bit in the Incubator policy that says A major criterion for graduation is to have developed an open and diverse meritocratic community.? I think not. If diversity does not matter, then please explain these references: http://www.apache.org/foundation/how-it-works.html Diversity of committership is important for two main reasons: - it gives long term stability to the project development: in fact, with all the developers affiliated to the same entity, the chance of seeing all of them moving away from the project at the same time is much greater than with a community of individuals affiliated to unrelated entities. - it gives a greater variety of technical visions: something that guarantees a better adherence to environment and user's needs, thus a higher change of finding real-life use of the software. http://www.apache.org/foundation/board/reporting - PMC and committer diversity A healthy project should survive the departure of any single contributor or employer of contributors. Healthy projects also serve needs of many parties. Thus the ASF prefers that projects have diverse PMCs and committerships. *IF* the PMC has any concerns or perceives a problem with the diversity, then the report should include information on the number of unique organizations currently represented in its PMC and committership. If diversity did not matter for TLPs, the above explanation and guidelines are false I think not. rgds jan I. What is important is that the committers and PMC of the new project understand how to make releases and are building community. On Tue, Jul 21, 2015 at 1:30 PM, Pierre Smits pierre.sm...@gmail.com wrote: Thanks, Konstantin, for the enlighting quote. And the link leading to nowhere. If we take away the names of the mentors from the list (Branko, Roman and yours) as well as those in other projects (Evans) from the list of intended project members, the situation even grows worse. Then the number grows to 77%. That doesn't look promising regarding independence, and neither regarding healthiness. Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Tue, Jul 21, 2015 at 8:53 PM, Konstantin Boudnik c...@apache.org wrote: The so-called diversity requirement has been discussed on this list for a number of times. Most recent is the graduation of Flume project (back in 2012). Here's a quote from that thread (kudos to Roy; for those who want to look it up in the archives MessageId is 73db2e64-87d5-4dd5-91fb-403464895...@gbiv.com): [quote] There is no diversity requirement at the ASF. There is a behavior requirement for graduation and a behavior requirement for TLPs. We must not confuse the two. If
Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
Accusation of what exactly? To the best of my knowledge, Roy has not been a part of the Ignite discussion, nor is he quoting policy in that particular sentence, but stating his opinion that the published Incubator policy should be overlooked (to which I disagree). Yes, he explains in rigorous detail why he thinks the way he thinks, but that is still an _opinion_, and quoting it as if it is policy (our published policy still begs to differ) is something I will consider as being out of context, as it does not convey the exact sentiment but rather, in my view, warps it into a truth of sorts. Yes, I value your hard work and I think you have immense amounts of merit, but I really dislike people always throwing Roy into every single discussion, and I tend to point it out. With regards, Daniel. On 2015-07-21 23:48, Roman Shaposhnik wrote: On Tue, Jul 21, 2015 at 2:29 PM, Daniel Gruno humbed...@apache.org wrote: Quoting Roy out of context Daniel, unless you can substantiate the above claim I suggest you retract your statement. In open communities an accusation that you just threw at me carries a lot of weight and I will absolutely NOT tolerate baseless accusations of that kind. I really hope I've done enough around IPMC over the years to earn at least a modicum of respect. Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
On Tue, Jul 21, 2015 at 3:05 PM, Daniel Gruno humbed...@apache.org wrote: Accusation of what exactly? Quoting Roy out of context. Here's what you said: Quoting Roy out of context is not a Hail Mary you can just throw out there when someone disagrees with you. To the best of my knowledge, Roy has not been a part of the Ignite discussion, nor is he quoting policy in that particular sentence, but stating his opinion that the published Incubator policy should be overlooked (to which I disagree). Yes, he explains in rigorous detail why he thinks the way he thinks, but that is still an _opinion_, and quoting it as if it is policy (our published policy still begs to differ) is something I will consider as being out of context, Then you should've said quoting it as if it is policy. Because you see: quoting it as if it is policy != Quoting Roy out of context Precision of language in contentious online discussions is of paramount importance. This time I'll chalk up our misunderstanding to your sloppy use of language in that particular sentence. Which brings us back to what you actually wanted to say, which is: quoting it as if it is policy. That was NOT my intent. My intent was to *highlight* what I took as a very insightful statement made in discussion extremely similar to the one we're having here 3 years after the original discussion. Roy's statement changed the way I think about ASF and IPMC. That was all I was trying to communicate. Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
Thanks, Konstantin, for the enlighting quote. And the link leading to nowhere. If we take away the names of the mentors from the list (Branko, Roman and yours) as well as those in other projects (Evans) from the list of intended project members, the situation even grows worse. Then the number grows to 77%. That doesn't look promising regarding independence, and neither regarding healthiness. Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Tue, Jul 21, 2015 at 8:53 PM, Konstantin Boudnik c...@apache.org wrote: The so-called diversity requirement has been discussed on this list for a number of times. Most recent is the graduation of Flume project (back in 2012). Here's a quote from that thread (kudos to Roy; for those who want to look it up in the archives MessageId is 73db2e64-87d5-4dd5-91fb-403464895...@gbiv.com): [quote] There is no diversity requirement at the ASF. There is a behavior requirement for graduation and a behavior requirement for TLPs. We must not confuse the two. If the Incubator says that there is a diversity requirement for graduation, ignore it (or at least figure out what the docs were supposed to say and then do that). I'd urge folks to fix the docs, but I know where that leads ... and I have no cycles to spare. A diversity requirement would mean that a person's employment status impacts their ability to participate here. IOW, it would create a perverse incentive for them not to be employed. [/quote] Regards, Cos On Tue, Jul 21, 2015 at 05:55PM, Pierre Smits wrote: It seems that 63% of the podling's PMC is affiliated to 1 organisation (Gridgrain). Have sufficient grounds been covered to ensure diversity and independece? Best regards, Pierre Smits On Tue, Jul 21, 2015 at 5:13 PM, Dmitriy Setrakyan dsetrak...@apache.org wrote: On Tue, Jul 21, 2015 at 4:08 AM, amareshwarisr . amareshw...@gmail.com wrote: Seems the DESCRIPTION_AND_SCOPE of the project is set to the automated and managed flow of information between systems. I dont see any such on project website - http://ignite.incubator.apache.org/ Looks like a copy from NIFI's graduation discussion - http://mail-archives.apache.org/mod_mbox/incubator-general/201506.mbox/%3CCALJK9a4PD%2B3qGGQbbHHyLfY8Ut9BP9VyEDwtnZDSWjpMKiwk9w%40mail.gmail.com%3E . You might want to correct it. Yup, copy-n-paste never works :) Corrected below. Correct me if description is fine and I'm wrong in understanding the description Thanks Amareshwari On Tue, Jul 21, 2015 at 5:06 AM, Dmitriy Setrakyan dsetrak...@apache.org wrote: Hello Apache Incubator, At the suggestion of our mentors the Ignite community established consensus and held a successful vote with 14 +1 votes in favor of proposing graduation to TLP. Vote thread: http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Graduate-Apache-Ignite-from-Incubation-td1539.html Summary of the vote results: +1 (non-binding) = 14 1. Yakov Zhdanov (PMC) 2. Gianfranco Murador (PMC) 3. Ira Vasilinets (PMC) 4. Nikolai Tichinov (PMC) 5. Semyon Boikov (PMC) 6. Sergi Vladykin (PMC) 7. Alexey Goncharuk (PMC) 8. Ognen Duzlevski (PMC) 9. Valentin Kulichenko (PMC) 10. Nikita Ivanov (PMC) 11. Dmitriy Setrakyan (PMC) 12. Andrey Novikov (Committer) 13. Alexey Kuznetsov (Committer) 14. Milap Wadwa We’d like to initiate this discussion/proposal to establish a consensus within the incubator and if appropriate will initiate a vote. Below is our proposed resolution: Thank you Dmitriy Setrakyan(on behalf of the Apache Ignite PPMC) SUBJECT: Establish the Apache Ignite TLP 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 the automated and managed flow of information between systems. Should be: - related to delivering an In-Memory Data Fabric - a high-performance, integrated and distributed in-memory platform for computing and transacting on large-scale data sets in real-time NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Ignite Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED,
[NOTICE] Lens VOTEing for graduation
FYI, Lens is currently VOTEing on a graduation resolution following successful discussions thereof. -Jakob -- Forwarded message -- From: Jakob Homan jgho...@gmail.com Date: 21 July 2015 at 13:27 Subject: [VOTE] Graduate Lens from Incubator To: d...@lens.incubator.apache.org Following two positive discussions[1][2] regarding Lens' current status, I'm calling a VOTE to graduate the project from the Incubator to TLP status. After this VOTE succeeds, its resolution will be forwarded to the Incubator list for another VOTE, after which the resolution will be sent to the Board for consideration at its next meeting. I've removed myself and Chris Douglas (checked with him offline), now that our roles as mentors have finished and we've not been involved otherwise with the community. The vote will run for 72 hours, ending 2pm PST July 24th. Everyone in the Lens community is invited and encouraged to vote, although only PPMC votes are binding [ ] +1 Graduate Apache Lens from the Incubator. [ ] +0 Don't care. [ ] -1 Don't graduate Apache Lens from the Incubator because ... Here's my binding vote: +1. -Jakob [1] http://s.apache.org/LensGradDiscuss1 [2] http://s.apache.org/LensGradDiscuss2 Apache Lens graduation resolution draft 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 unified analytics across multiple tiered data stores. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Lens Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Lens Project be and hereby is responsible for the creation and maintenance of software related to unified analytics across multiple tiered data stores; and be it further RESOLVED, that the office of Vice President, Apache Lens 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 Lens Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Lens 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 Lens Project: * Amareshwari Sriramadasu amareshwari at apache dot org * Arshad Matin arshadmatin at apache dot org * Gunther Hagleitner gunther at apache dot org * Himanshu Gahlaut himanshugahlaut at apache dot org * Jaideep Dhok jdhok at apache dot org * Jean Baptiste Onofre jbonofre at apache dot org * Raghavendra Singh raghavsingh at apache dot org * Rajat Khandelwal prongs at apache dot org * Raju Bairishetti raju at apache dot org * Sharad Agarwal sharad at apache dot org * Sreekanth Ramakrishnan sreekanth at apache dot org * Srikanth Sundarrajan sriksun at apache dot org * Suma Shivaprasad sumasai at apache dot org * Vikram Dixit vikram at apache dot org * Vinod Kumar Vavilapalli vinodkv at apache dot org * Yash Sharma yash at apache dot org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Amareshwari Sriramadasu be appointed to the office of Vice President, Apache Lens, 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 Lens Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Lens podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Lens 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: [DISCUSSION] Graduate Ignite from the Apache Incubator
Present time diversity or lack of same is not a bar to graduation. What is important is that the committers and PMC of the new project understand how to make releases and are building community. On Tue, Jul 21, 2015 at 1:30 PM, Pierre Smits pierre.sm...@gmail.com wrote: Thanks, Konstantin, for the enlighting quote. And the link leading to nowhere. If we take away the names of the mentors from the list (Branko, Roman and yours) as well as those in other projects (Evans) from the list of intended project members, the situation even grows worse. Then the number grows to 77%. That doesn't look promising regarding independence, and neither regarding healthiness. Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Tue, Jul 21, 2015 at 8:53 PM, Konstantin Boudnik c...@apache.org wrote: The so-called diversity requirement has been discussed on this list for a number of times. Most recent is the graduation of Flume project (back in 2012). Here's a quote from that thread (kudos to Roy; for those who want to look it up in the archives MessageId is 73db2e64-87d5-4dd5-91fb-403464895...@gbiv.com): [quote] There is no diversity requirement at the ASF. There is a behavior requirement for graduation and a behavior requirement for TLPs. We must not confuse the two. If the Incubator says that there is a diversity requirement for graduation, ignore it (or at least figure out what the docs were supposed to say and then do that). I'd urge folks to fix the docs, but I know where that leads ... and I have no cycles to spare. A diversity requirement would mean that a person's employment status impacts their ability to participate here. IOW, it would create a perverse incentive for them not to be employed. [/quote] Regards, Cos On Tue, Jul 21, 2015 at 05:55PM, Pierre Smits wrote: It seems that 63% of the podling's PMC is affiliated to 1 organisation (Gridgrain). Have sufficient grounds been covered to ensure diversity and independece? Best regards, Pierre Smits On Tue, Jul 21, 2015 at 5:13 PM, Dmitriy Setrakyan dsetrak...@apache.org wrote: On Tue, Jul 21, 2015 at 4:08 AM, amareshwarisr . amareshw...@gmail.com wrote: Seems the DESCRIPTION_AND_SCOPE of the project is set to the automated and managed flow of information between systems. I dont see any such on project website - http://ignite.incubator.apache.org/ Looks like a copy from NIFI's graduation discussion - http://mail-archives.apache.org/mod_mbox/incubator-general/201506.mbox/%3CCALJK9a4PD%2B3qGGQbbHHyLfY8Ut9BP9VyEDwtnZDSWjpMKiwk9w%40mail.gmail.com%3E . You might want to correct it. Yup, copy-n-paste never works :) Corrected below. Correct me if description is fine and I'm wrong in understanding the description Thanks Amareshwari On Tue, Jul 21, 2015 at 5:06 AM, Dmitriy Setrakyan dsetrak...@apache.org wrote: Hello Apache Incubator, At the suggestion of our mentors the Ignite community established consensus and held a successful vote with 14 +1 votes in favor of proposing graduation to TLP. Vote thread: http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Graduate-Apache-Ignite-from-Incubation-td1539.html Summary of the vote results: +1 (non-binding) = 14 1. Yakov Zhdanov (PMC) 2. Gianfranco Murador (PMC) 3. Ira Vasilinets (PMC) 4. Nikolai Tichinov (PMC) 5. Semyon Boikov (PMC) 6. Sergi Vladykin (PMC) 7. Alexey Goncharuk (PMC) 8. Ognen Duzlevski (PMC) 9. Valentin Kulichenko (PMC) 10. Nikita Ivanov (PMC) 11. Dmitriy Setrakyan (PMC) 12. Andrey Novikov (Committer) 13. Alexey Kuznetsov (Committer) 14. Milap Wadwa We’d like to initiate this discussion/proposal to establish a consensus within the incubator and if appropriate will initiate a vote. Below is our proposed resolution: Thank you Dmitriy Setrakyan(on behalf of the Apache Ignite PPMC) SUBJECT: Establish the Apache Ignite TLP 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 the automated and managed flow of information between systems. Should be: - related to delivering an In-Memory Data Fabric -
Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
While Roy is indeed a smart man, there is no BDFL in the ASF. Quoting Roy out of context is not a Hail Mary you can just throw out there when someone disagrees with you. Several people, including several IPMC members have expressed concerns. Address them properly instead of insisting on your way or the high way. The question of diversity in this case is not are we enough men/women/whatever, the question here is is there a single corporate entity with a deciding vote in the project?. What I am concerned with here is the responses to this. Instead of saying We don't believe that to be the case, the PPMC is saying there's no rule against that! as if there _is_ an issue but it's being swept under the rug. With regards, Daniel. On 2015-07-21 23:19, Roman Shaposhnik wrote: Please re-read the quote from Roy: There is no diversity requirement at the ASF. There is a behavior requirement for graduation and a behavior requirement for TLPs. We must not confuse the two. and later I'd urge folks to fix the docs, but I know where that leads ... and I have no cycles to spare. Thanks, Roman. On Tue, Jul 21, 2015 at 1:55 PM, jan i j...@apache.org wrote: On 21 July 2015 at 22:48, Daniel Gruno humbed...@apache.org wrote: On 07/21/2015 10:39 PM, Ted Dunning wrote: Present time diversity or lack of same is not a bar to graduation. So we should just scrap the bit in the Incubator policy that says A major criterion for graduation is to have developed an open and diverse meritocratic community.? I think not. If diversity does not matter, then please explain these references: http://www.apache.org/foundation/how-it-works.html Diversity of committership is important for two main reasons: - it gives long term stability to the project development: in fact, with all the developers affiliated to the same entity, the chance of seeing all of them moving away from the project at the same time is much greater than with a community of individuals affiliated to unrelated entities. - it gives a greater variety of technical visions: something that guarantees a better adherence to environment and user's needs, thus a higher change of finding real-life use of the software. http://www.apache.org/foundation/board/reporting - PMC and committer diversity A healthy project should survive the departure of any single contributor or employer of contributors. Healthy projects also serve needs of many parties. Thus the ASF prefers that projects have diverse PMCs and committerships. *IF* the PMC has any concerns or perceives a problem with the diversity, then the report should include information on the number of unique organizations currently represented in its PMC and committership. If diversity did not matter for TLPs, the above explanation and guidelines are false I think not. rgds jan I. What is important is that the committers and PMC of the new project understand how to make releases and are building community. On Tue, Jul 21, 2015 at 1:30 PM, Pierre Smits pierre.sm...@gmail.com wrote: Thanks, Konstantin, for the enlighting quote. And the link leading to nowhere. If we take away the names of the mentors from the list (Branko, Roman and yours) as well as those in other projects (Evans) from the list of intended project members, the situation even grows worse. Then the number grows to 77%. That doesn't look promising regarding independence, and neither regarding healthiness. Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Tue, Jul 21, 2015 at 8:53 PM, Konstantin Boudnik c...@apache.org wrote: The so-called diversity requirement has been discussed on this list for a number of times. Most recent is the graduation of Flume project (back in 2012). Here's a quote from that thread (kudos to Roy; for those who want to look it up in the archives MessageId is 73db2e64-87d5-4dd5-91fb-403464895...@gbiv.com): [quote] There is no diversity requirement at the ASF. There is a behavior requirement for graduation and a behavior requirement for TLPs. We must not confuse the two. If the Incubator says that there is a diversity requirement for graduation, ignore it (or at least figure out what the docs were supposed to say and then do that). I'd urge folks to fix the docs, but I know where that leads ... and I have no cycles to spare. A diversity requirement would mean that a person's employment status impacts their ability to participate here. IOW, it would create a perverse incentive for them not to be employed. [/quote] Regards, Cos On Tue, Jul 21, 2015 at 05:55PM, Pierre Smits wrote: It seems that 63% of the podling's PMC is affiliated to 1 organisation (Gridgrain). Have sufficient grounds been covered to ensure diversity and independece? Best regards, Pierre Smits On Tue, Jul
Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
On Tue, Jul 21, 2015 at 2:29 PM, Daniel Gruno humbed...@apache.org wrote: Quoting Roy out of context Daniel, unless you can substantiate the above claim I suggest you retract your statement. In open communities an accusation that you just threw at me carries a lot of weight and I will absolutely NOT tolerate baseless accusations of that kind. I really hope I've done enough around IPMC over the years to earn at least a modicum of respect. Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
On Tue, Jul 21, 2015 at 11:44PM, Pierre Smits wrote: A lot has changed in the period after the posting of Roy. Back then there seemed to have been less concern regarding independence and diversity. We now have a code of conduct (even though some are convinced that these are mere guidelines when it comes to a project's independence). I fail to see how CoC has to do with the numbers you just quoted, so let's not sway the conversation that way. That said - can you quote any empirical evidences (or any evidences at all) on why %63 seems low? I have asked you this very question in a different message and would appreciate if the person who started this discussion can add some factual information to support the claim. Thank you. Cos Diversity is not the same as having 3 independent (p)PMC members. The diversity aspect is also intended to ensure that there is some kind of balance, before a project goes bust. If such happens, it might be to late. Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Tue, Jul 21, 2015 at 11:19 PM, Roman Shaposhnik ro...@shaposhnik.org wrote: Please re-read the quote from Roy: There is no diversity requirement at the ASF. There is a behavior requirement for graduation and a behavior requirement for TLPs. We must not confuse the two. and later I'd urge folks to fix the docs, but I know where that leads ... and I have no cycles to spare. Thanks, Roman. On Tue, Jul 21, 2015 at 1:55 PM, jan i j...@apache.org wrote: On 21 July 2015 at 22:48, Daniel Gruno humbed...@apache.org wrote: On 07/21/2015 10:39 PM, Ted Dunning wrote: Present time diversity or lack of same is not a bar to graduation. So we should just scrap the bit in the Incubator policy that says A major criterion for graduation is to have developed an open and diverse meritocratic community.? I think not. If diversity does not matter, then please explain these references: http://www.apache.org/foundation/how-it-works.html Diversity of committership is important for two main reasons: - it gives long term stability to the project development: in fact, with all the developers affiliated to the same entity, the chance of seeing all of them moving away from the project at the same time is much greater than with a community of individuals affiliated to unrelated entities. - it gives a greater variety of technical visions: something that guarantees a better adherence to environment and user's needs, thus a higher change of finding real-life use of the software. http://www.apache.org/foundation/board/reporting - PMC and committer diversity A healthy project should survive the departure of any single contributor or employer of contributors. Healthy projects also serve needs of many parties. Thus the ASF prefers that projects have diverse PMCs and committerships. *IF* the PMC has any concerns or perceives a problem with the diversity, then the report should include information on the number of unique organizations currently represented in its PMC and committership. If diversity did not matter for TLPs, the above explanation and guidelines are false I think not. rgds jan I. What is important is that the committers and PMC of the new project understand how to make releases and are building community. On Tue, Jul 21, 2015 at 1:30 PM, Pierre Smits pierre.sm...@gmail.com wrote: Thanks, Konstantin, for the enlighting quote. And the link leading to nowhere. If we take away the names of the mentors from the list (Branko, Roman and yours) as well as those in other projects (Evans) from the list of intended project members, the situation even grows worse. Then the number grows to 77%. That doesn't look promising regarding independence, and neither regarding healthiness. Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Tue, Jul 21, 2015 at 8:53 PM, Konstantin Boudnik c...@apache.org wrote: The so-called diversity requirement has been discussed on this list for a number of times. Most recent is the graduation of Flume project (back in 2012). Here's a quote from that thread (kudos to Roy; for those who want to look it up in the archives MessageId is 73db2e64-87d5-4dd5-91fb-403464895...@gbiv.com): [quote] There is no diversity requirement at the ASF. There is a behavior requirement for graduation and a behavior
Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
Another minor nitpick: On the people page of the ignite website, some are tagged as PMC and there is a tag for PMC Chair. Until official graduation, that should probably change to PPMC and the PMC Chair tag be removed, since AFAIK podlings don't have VPs. -Taylor On Jul 21, 2015, at 5:08 PM, Daniel Gruno humbed...@apache.org wrote: Nitpicking time. Your supposedly vendor-neutral web site says: GridGain Community Edition is a binary build of Apache Ignite created by GridGain, which includes optional LGPL dependencies, such as Hibernate L2 cache integration and Geospatial Indexing. It benefits from continued testing by GridGain engineers and may contain latest bug fixes and features that will be included into the future official Apache Ignite releases. - I consider this very biased towards a single company (especially considering it is the _only_ 3rd party listed, and you do _not_ specify how other 3rd parties may get listed on the page). You start off by saying you don't endorse it, and then you praise it - it's either or. Your web site also lists the organizational affiliation of PMC members. While this may be useful internally in the ASF, I fail to see why this is mentioned on the web site. This should have no relevance to the project whatsoever. You point to gridgain.org for several of your documentation segments, this is also not acceptable. I would very much like to see this rectified before we get to an actual vote, or I will possibly be casting a -1. With regards, Daniel. On 07/21/2015 10:48 PM, Daniel Gruno wrote: On 07/21/2015 10:39 PM, Ted Dunning wrote: Present time diversity or lack of same is not a bar to graduation. So we should just scrap the bit in the Incubator policy that says A major criterion for graduation is to have developed an open and diverse meritocratic community.? I think not. What is important is that the committers and PMC of the new project understand how to make releases and are building community. On Tue, Jul 21, 2015 at 1:30 PM, Pierre Smits pierre.sm...@gmail.com wrote: Thanks, Konstantin, for the enlighting quote. And the link leading to nowhere. If we take away the names of the mentors from the list (Branko, Roman and yours) as well as those in other projects (Evans) from the list of intended project members, the situation even grows worse. Then the number grows to 77%. That doesn't look promising regarding independence, and neither regarding healthiness. Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Tue, Jul 21, 2015 at 8:53 PM, Konstantin Boudnik c...@apache.org wrote: The so-called diversity requirement has been discussed on this list for a number of times. Most recent is the graduation of Flume project (back in 2012). Here's a quote from that thread (kudos to Roy; for those who want to look it up in the archives MessageId is 73db2e64-87d5-4dd5-91fb-403464895...@gbiv.com): [quote] There is no diversity requirement at the ASF. There is a behavior requirement for graduation and a behavior requirement for TLPs. We must not confuse the two. If the Incubator says that there is a diversity requirement for graduation, ignore it (or at least figure out what the docs were supposed to say and then do that). I'd urge folks to fix the docs, but I know where that leads ... and I have no cycles to spare. A diversity requirement would mean that a person's employment status impacts their ability to participate here. IOW, it would create a perverse incentive for them not to be employed. [/quote] Regards, Cos On Tue, Jul 21, 2015 at 05:55PM, Pierre Smits wrote: It seems that 63% of the podling's PMC is affiliated to 1 organisation (Gridgrain). Have sufficient grounds been covered to ensure diversity and independece? Best regards, Pierre Smits On Tue, Jul 21, 2015 at 5:13 PM, Dmitriy Setrakyan dsetrak...@apache.org wrote: On Tue, Jul 21, 2015 at 4:08 AM, amareshwarisr . amareshw...@gmail.com wrote: Seems the DESCRIPTION_AND_SCOPE of the project is set to the automated and managed flow of information between systems. I dont see any such on project website - http://ignite.incubator.apache.org/ Looks like a copy from NIFI's graduation discussion - http://mail-archives.apache.org/mod_mbox/incubator-general/201506.mbox/%3CCALJK9a4PD%2B3qGGQbbHHyLfY8Ut9BP9VyEDwtnZDSWjpMKiwk9w%40mail.gmail.com%3E . You might want to correct it. Yup, copy-n-paste never works :) Corrected below. Correct me if description is fine and I'm wrong in understanding the description Thanks Amareshwari On Tue, Jul 21, 2015 at 5:06 AM, Dmitriy Setrakyan dsetrak...@apache.org wrote: Hello Apache Incubator, At the suggestion of our mentors the Ignite community established consensus and
Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
Sorry, which part of the quoted policy the 63% is allegedly scraping out? For easy reference, here's the link https://incubator.apache.org/guides/graduation.html to the document containing the section of Creating an Open and Diverse community. So far I haven't heard a single matter of fact evidence supporting your claim. Thanks Cos On Tue, Jul 21, 2015 at 10:48PM, Daniel Gruno wrote: On 07/21/2015 10:39 PM, Ted Dunning wrote: Present time diversity or lack of same is not a bar to graduation. So we should just scrap the bit in the Incubator policy that says A major criterion for graduation is to have developed an open and diverse meritocratic community.? I think not. What is important is that the committers and PMC of the new project understand how to make releases and are building community. On Tue, Jul 21, 2015 at 1:30 PM, Pierre Smits pierre.sm...@gmail.com wrote: Thanks, Konstantin, for the enlighting quote. And the link leading to nowhere. If we take away the names of the mentors from the list (Branko, Roman and yours) as well as those in other projects (Evans) from the list of intended project members, the situation even grows worse. Then the number grows to 77%. That doesn't look promising regarding independence, and neither regarding healthiness. Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Tue, Jul 21, 2015 at 8:53 PM, Konstantin Boudnik c...@apache.org wrote: The so-called diversity requirement has been discussed on this list for a number of times. Most recent is the graduation of Flume project (back in 2012). Here's a quote from that thread (kudos to Roy; for those who want to look it up in the archives MessageId is 73db2e64-87d5-4dd5-91fb-403464895...@gbiv.com): [quote] There is no diversity requirement at the ASF. There is a behavior requirement for graduation and a behavior requirement for TLPs. We must not confuse the two. If the Incubator says that there is a diversity requirement for graduation, ignore it (or at least figure out what the docs were supposed to say and then do that). I'd urge folks to fix the docs, but I know where that leads ... and I have no cycles to spare. A diversity requirement would mean that a person's employment status impacts their ability to participate here. IOW, it would create a perverse incentive for them not to be employed. [/quote] Regards, Cos On Tue, Jul 21, 2015 at 05:55PM, Pierre Smits wrote: It seems that 63% of the podling's PMC is affiliated to 1 organisation (Gridgrain). Have sufficient grounds been covered to ensure diversity and independece? Best regards, Pierre Smits On Tue, Jul 21, 2015 at 5:13 PM, Dmitriy Setrakyan dsetrak...@apache.org wrote: On Tue, Jul 21, 2015 at 4:08 AM, amareshwarisr . amareshw...@gmail.com wrote: Seems the DESCRIPTION_AND_SCOPE of the project is set to the automated and managed flow of information between systems. I dont see any such on project website - http://ignite.incubator.apache.org/ Looks like a copy from NIFI's graduation discussion - http://mail-archives.apache.org/mod_mbox/incubator-general/201506.mbox/%3CCALJK9a4PD%2B3qGGQbbHHyLfY8Ut9BP9VyEDwtnZDSWjpMKiwk9w%40mail.gmail.com%3E . You might want to correct it. Yup, copy-n-paste never works :) Corrected below. Correct me if description is fine and I'm wrong in understanding the description Thanks Amareshwari On Tue, Jul 21, 2015 at 5:06 AM, Dmitriy Setrakyan dsetrak...@apache.org wrote: Hello Apache Incubator, At the suggestion of our mentors the Ignite community established consensus and held a successful vote with 14 +1 votes in favor of proposing graduation to TLP. Vote thread: http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Graduate-Apache-Ignite-from-Incubation-td1539.html Summary of the vote results: +1 (non-binding) = 14 1. Yakov Zhdanov (PMC) 2. Gianfranco Murador (PMC) 3. Ira Vasilinets (PMC) 4. Nikolai Tichinov (PMC) 5. Semyon Boikov (PMC) 6. Sergi Vladykin (PMC) 7. Alexey Goncharuk (PMC) 8. Ognen Duzlevski (PMC) 9. Valentin Kulichenko (PMC) 10. Nikita Ivanov (PMC) 11. Dmitriy Setrakyan (PMC) 12. Andrey Novikov (Committer) 13. Alexey Kuznetsov (Committer) 14. Milap Wadwa We’d like to initiate this discussion/proposal to establish a consensus within the incubator and if appropriate will initiate a vote. Below is our proposed resolution: Thank you Dmitriy Setrakyan(on behalf of the Apache Ignite PPMC) SUBJECT: Establish the Apache Ignite TLP WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation
Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
Is this a reply to me or to Pierre? I have not mentioned 63% anywhere. I have stated that we have a policy that states that a podling must have an open and diverse meritocratic community. The link you put in your reply says exactly that. With regards, Daniel. On 2015-07-22 00:16, Konstantin Boudnik wrote: Sorry, which part of the quoted policy the 63% is allegedly scraping out? For easy reference, here's the link https://incubator.apache.org/guides/graduation.html to the document containing the section of Creating an Open and Diverse community. So far I haven't heard a single matter of fact evidence supporting your claim. Thanks Cos On Tue, Jul 21, 2015 at 10:48PM, Daniel Gruno wrote: On 07/21/2015 10:39 PM, Ted Dunning wrote: Present time diversity or lack of same is not a bar to graduation. So we should just scrap the bit in the Incubator policy that says A major criterion for graduation is to have developed an open and diverse meritocratic community.? I think not. What is important is that the committers and PMC of the new project understand how to make releases and are building community. On Tue, Jul 21, 2015 at 1:30 PM, Pierre Smits pierre.sm...@gmail.com wrote: Thanks, Konstantin, for the enlighting quote. And the link leading to nowhere. If we take away the names of the mentors from the list (Branko, Roman and yours) as well as those in other projects (Evans) from the list of intended project members, the situation even grows worse. Then the number grows to 77%. That doesn't look promising regarding independence, and neither regarding healthiness. Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Tue, Jul 21, 2015 at 8:53 PM, Konstantin Boudnik c...@apache.org wrote: The so-called diversity requirement has been discussed on this list for a number of times. Most recent is the graduation of Flume project (back in 2012). Here's a quote from that thread (kudos to Roy; for those who want to look it up in the archives MessageId is 73db2e64-87d5-4dd5-91fb-403464895...@gbiv.com): [quote] There is no diversity requirement at the ASF. There is a behavior requirement for graduation and a behavior requirement for TLPs. We must not confuse the two. If the Incubator says that there is a diversity requirement for graduation, ignore it (or at least figure out what the docs were supposed to say and then do that). I'd urge folks to fix the docs, but I know where that leads ... and I have no cycles to spare. A diversity requirement would mean that a person's employment status impacts their ability to participate here. IOW, it would create a perverse incentive for them not to be employed. [/quote] Regards, Cos On Tue, Jul 21, 2015 at 05:55PM, Pierre Smits wrote: It seems that 63% of the podling's PMC is affiliated to 1 organisation (Gridgrain). Have sufficient grounds been covered to ensure diversity and independece? Best regards, Pierre Smits On Tue, Jul 21, 2015 at 5:13 PM, Dmitriy Setrakyan dsetrak...@apache.org wrote: On Tue, Jul 21, 2015 at 4:08 AM, amareshwarisr . amareshw...@gmail.com wrote: Seems the DESCRIPTION_AND_SCOPE of the project is set to the automated and managed flow of information between systems. I dont see any such on project website - http://ignite.incubator.apache.org/ Looks like a copy from NIFI's graduation discussion - http://mail-archives.apache.org/mod_mbox/incubator-general/201506.mbox/%3CCALJK9a4PD%2B3qGGQbbHHyLfY8Ut9BP9VyEDwtnZDSWjpMKiwk9w%40mail.gmail.com%3E . You might want to correct it. Yup, copy-n-paste never works :) Corrected below. Correct me if description is fine and I'm wrong in understanding the description Thanks Amareshwari On Tue, Jul 21, 2015 at 5:06 AM, Dmitriy Setrakyan dsetrak...@apache.org wrote: Hello Apache Incubator, At the suggestion of our mentors the Ignite community established consensus and held a successful vote with 14 +1 votes in favor of proposing graduation to TLP. Vote thread: http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Graduate-Apache-Ignite-from-Incubation-td1539.html Summary of the vote results: +1 (non-binding) = 14 1. Yakov Zhdanov (PMC) 2. Gianfranco Murador (PMC) 3. Ira Vasilinets (PMC) 4. Nikolai Tichinov (PMC) 5. Semyon Boikov (PMC) 6. Sergi Vladykin (PMC) 7. Alexey Goncharuk (PMC) 8. Ognen Duzlevski (PMC) 9. Valentin Kulichenko (PMC) 10. Nikita Ivanov (PMC) 11. Dmitriy Setrakyan (PMC) 12. Andrey Novikov (Committer) 13. Alexey Kuznetsov (Committer) 14. Milap Wadwa We’d like to initiate this discussion/proposal to establish a consensus within the incubator and if appropriate will initiate a vote. Below is our proposed resolution: Thank you Dmitriy Setrakyan(on behalf of the Apache Ignite PPMC) SUBJECT: Establish the Apache Ignite TLP WHEREAS,
Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
On 21 July 2015 at 22:48, Daniel Gruno humbed...@apache.org wrote: On 07/21/2015 10:39 PM, Ted Dunning wrote: Present time diversity or lack of same is not a bar to graduation. So we should just scrap the bit in the Incubator policy that says A major criterion for graduation is to have developed an open and diverse meritocratic community.? I think not. If diversity does not matter, then please explain these references: http://www.apache.org/foundation/how-it-works.html Diversity of committership is important for two main reasons: - it gives long term stability to the project development: in fact, with all the developers affiliated to the same entity, the chance of seeing all of them moving away from the project at the same time is much greater than with a community of individuals affiliated to unrelated entities. - it gives a greater variety of technical visions: something that guarantees a better adherence to environment and user's needs, thus a higher change of finding real-life use of the software. http://www.apache.org/foundation/board/reporting - PMC and committer diversity A healthy project should survive the departure of any single contributor or employer of contributors. Healthy projects also serve needs of many parties. Thus the ASF prefers that projects have diverse PMCs and committerships. *IF* the PMC has any concerns or perceives a problem with the diversity, then the report should include information on the number of unique organizations currently represented in its PMC and committership. If diversity did not matter for TLPs, the above explanation and guidelines are false I think not. rgds jan I. What is important is that the committers and PMC of the new project understand how to make releases and are building community. On Tue, Jul 21, 2015 at 1:30 PM, Pierre Smits pierre.sm...@gmail.com wrote: Thanks, Konstantin, for the enlighting quote. And the link leading to nowhere. If we take away the names of the mentors from the list (Branko, Roman and yours) as well as those in other projects (Evans) from the list of intended project members, the situation even grows worse. Then the number grows to 77%. That doesn't look promising regarding independence, and neither regarding healthiness. Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Tue, Jul 21, 2015 at 8:53 PM, Konstantin Boudnik c...@apache.org wrote: The so-called diversity requirement has been discussed on this list for a number of times. Most recent is the graduation of Flume project (back in 2012). Here's a quote from that thread (kudos to Roy; for those who want to look it up in the archives MessageId is 73db2e64-87d5-4dd5-91fb-403464895...@gbiv.com): [quote] There is no diversity requirement at the ASF. There is a behavior requirement for graduation and a behavior requirement for TLPs. We must not confuse the two. If the Incubator says that there is a diversity requirement for graduation, ignore it (or at least figure out what the docs were supposed to say and then do that). I'd urge folks to fix the docs, but I know where that leads ... and I have no cycles to spare. A diversity requirement would mean that a person's employment status impacts their ability to participate here. IOW, it would create a perverse incentive for them not to be employed. [/quote] Regards, Cos On Tue, Jul 21, 2015 at 05:55PM, Pierre Smits wrote: It seems that 63% of the podling's PMC is affiliated to 1 organisation (Gridgrain). Have sufficient grounds been covered to ensure diversity and independece? Best regards, Pierre Smits On Tue, Jul 21, 2015 at 5:13 PM, Dmitriy Setrakyan dsetrak...@apache.org wrote: On Tue, Jul 21, 2015 at 4:08 AM, amareshwarisr . amareshw...@gmail.com wrote: Seems the DESCRIPTION_AND_SCOPE of the project is set to the automated and managed flow of information between systems. I dont see any such on project website - http://ignite.incubator.apache.org/ Looks like a copy from NIFI's graduation discussion - http://mail-archives.apache.org/mod_mbox/incubator-general/201506.mbox/%3CCALJK9a4PD%2B3qGGQbbHHyLfY8Ut9BP9VyEDwtnZDSWjpMKiwk9w%40mail.gmail.com%3E . You might want to correct it. Yup, copy-n-paste never works :) Corrected below. Correct me if description is fine and I'm wrong in understanding the description Thanks Amareshwari On Tue, Jul 21, 2015 at 5:06 AM, Dmitriy Setrakyan dsetrak...@apache.org wrote: Hello Apache Incubator, At the suggestion of our mentors the Ignite community established consensus and held a successful vote with 14 +1 votes in favor of proposing graduation to TLP.
Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
Yet, the graduation of the projects like Apache Tez had happened with close to 100% PPMC employed by the same company. Shall IPMC first workout what diversity means in numbers and then apply it to all podlings, instead of doing this arbitrary? And what that number should be? Would it need to be 47%? Why not 26% perhaps? May be Pierre can share his thoughts on why 63% seems to be low. Perhaps he would care to produce some statistical evidences that anything above 62% doesn't work? A project isn't controlled by a company but by its PMC. If PMC doesn't do its job then the board@ has ways of interfere, and so far was doing just that very effectively. Cos On Tue, Jul 21, 2015 at 10:44PM, jan i wrote: On 21 July 2015 at 22:39, Ted Dunning ted.dunn...@gmail.com wrote: Present time diversity or lack of same is not a bar to graduation. Reading other lists, it seems to me that board is very concerned about TLPs that are dominated by one company. We (ASF) want to ensure that a project is not controlled by a company, and also that the project can survive if the company decides to do something else. That is diversity to me, and I hope to many others. It might not be a bar for leaving the incubator, but I sure hope it is a bar for getting a board approval. (and actually I thought it was a concern for incubator too). rgds jan i. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
It seems to me the spirit of the diversity statement is about project survival: A healthy project should survive the departure of any single contributor or employer of contributors. So I would think satisfying that requirement wouldn’t necessarily involve a percentage, but rather a simple number: At least 3 PMC members who are not affiliated with the employer of the majority. That way if the employer of the majority departed, there would be enough remaining members for form consensus. -Taylor On Jul 21, 2015, at 4:55 PM, jan i j...@apache.org wrote: On 21 July 2015 at 22:48, Daniel Gruno humbed...@apache.org wrote: On 07/21/2015 10:39 PM, Ted Dunning wrote: Present time diversity or lack of same is not a bar to graduation. So we should just scrap the bit in the Incubator policy that says A major criterion for graduation is to have developed an open and diverse meritocratic community.? I think not. If diversity does not matter, then please explain these references: http://www.apache.org/foundation/how-it-works.html Diversity of committership is important for two main reasons: - it gives long term stability to the project development: in fact, with all the developers affiliated to the same entity, the chance of seeing all of them moving away from the project at the same time is much greater than with a community of individuals affiliated to unrelated entities. - it gives a greater variety of technical visions: something that guarantees a better adherence to environment and user's needs, thus a higher change of finding real-life use of the software. http://www.apache.org/foundation/board/reporting - PMC and committer diversity A healthy project should survive the departure of any single contributor or employer of contributors. Healthy projects also serve needs of many parties. Thus the ASF prefers that projects have diverse PMCs and committerships. *IF* the PMC has any concerns or perceives a problem with the diversity, then the report should include information on the number of unique organizations currently represented in its PMC and committership. If diversity did not matter for TLPs, the above explanation and guidelines are false I think not. rgds jan I. What is important is that the committers and PMC of the new project understand how to make releases and are building community. On Tue, Jul 21, 2015 at 1:30 PM, Pierre Smits pierre.sm...@gmail.com wrote: Thanks, Konstantin, for the enlighting quote. And the link leading to nowhere. If we take away the names of the mentors from the list (Branko, Roman and yours) as well as those in other projects (Evans) from the list of intended project members, the situation even grows worse. Then the number grows to 77%. That doesn't look promising regarding independence, and neither regarding healthiness. Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Tue, Jul 21, 2015 at 8:53 PM, Konstantin Boudnik c...@apache.org wrote: The so-called diversity requirement has been discussed on this list for a number of times. Most recent is the graduation of Flume project (back in 2012). Here's a quote from that thread (kudos to Roy; for those who want to look it up in the archives MessageId is 73db2e64-87d5-4dd5-91fb-403464895...@gbiv.com): [quote] There is no diversity requirement at the ASF. There is a behavior requirement for graduation and a behavior requirement for TLPs. We must not confuse the two. If the Incubator says that there is a diversity requirement for graduation, ignore it (or at least figure out what the docs were supposed to say and then do that). I'd urge folks to fix the docs, but I know where that leads ... and I have no cycles to spare. A diversity requirement would mean that a person's employment status impacts their ability to participate here. IOW, it would create a perverse incentive for them not to be employed. [/quote] Regards, Cos On Tue, Jul 21, 2015 at 05:55PM, Pierre Smits wrote: It seems that 63% of the podling's PMC is affiliated to 1 organisation (Gridgrain). Have sufficient grounds been covered to ensure diversity and independece? Best regards, Pierre Smits On Tue, Jul 21, 2015 at 5:13 PM, Dmitriy Setrakyan dsetrak...@apache.org wrote: On Tue, Jul 21, 2015 at 4:08 AM, amareshwarisr . amareshw...@gmail.com wrote: Seems the DESCRIPTION_AND_SCOPE of the project is set to the automated and managed flow of information between systems. I dont see any such on project website - http://ignite.incubator.apache.org/ Looks like a copy from NIFI's graduation discussion -
Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
On Tue, Jul 21, 2015 at 11:08PM, Daniel Gruno wrote: Nitpicking time. Your supposedly vendor-neutral web site says: GridGain Community Edition is a binary build of Apache Ignite created by GridGain, which includes optional LGPL dependencies, such as Hibernate L2 cache integration and Geospatial Indexing. It benefits from continued testing by GridGain engineers and may contain latest bug fixes and features that will be included into the future official Apache Ignite releases. - I consider this very biased towards a single company (especially considering it is the _only_ 3rd party listed, and you do _not_ specify how other 3rd parties may get listed on the page). You start off by saying you don't endorse it, and then you praise it - it's either or. Your web site also lists the organizational affiliation of PMC members. While this may be useful internally in the ASF, I fail to see why this is mentioned on the web site. This should have no relevance to the project whatsoever. You point to gridgain.org for several of your documentation segments, this is also not acceptable. I would very much like to see this rectified before we get to an actual vote, or I will possibly be casting a -1. Fair points! Thanks Daniel, I was sure these very fixed a while ago. As for the affiliation of the members: pretty much every other ASF project does the same. Shall we make sure that established TLPs aren't doing this either? Regards, Cos With regards, Daniel. On 07/21/2015 10:48 PM, Daniel Gruno wrote: On 07/21/2015 10:39 PM, Ted Dunning wrote: Present time diversity or lack of same is not a bar to graduation. So we should just scrap the bit in the Incubator policy that says A major criterion for graduation is to have developed an open and diverse meritocratic community.? I think not. What is important is that the committers and PMC of the new project understand how to make releases and are building community. On Tue, Jul 21, 2015 at 1:30 PM, Pierre Smits pierre.sm...@gmail.com wrote: Thanks, Konstantin, for the enlighting quote. And the link leading to nowhere. If we take away the names of the mentors from the list (Branko, Roman and yours) as well as those in other projects (Evans) from the list of intended project members, the situation even grows worse. Then the number grows to 77%. That doesn't look promising regarding independence, and neither regarding healthiness. Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Tue, Jul 21, 2015 at 8:53 PM, Konstantin Boudnik c...@apache.org wrote: The so-called diversity requirement has been discussed on this list for a number of times. Most recent is the graduation of Flume project (back in 2012). Here's a quote from that thread (kudos to Roy; for those who want to look it up in the archives MessageId is 73db2e64-87d5-4dd5-91fb-403464895...@gbiv.com): [quote] There is no diversity requirement at the ASF. There is a behavior requirement for graduation and a behavior requirement for TLPs. We must not confuse the two. If the Incubator says that there is a diversity requirement for graduation, ignore it (or at least figure out what the docs were supposed to say and then do that). I'd urge folks to fix the docs, but I know where that leads ... and I have no cycles to spare. A diversity requirement would mean that a person's employment status impacts their ability to participate here. IOW, it would create a perverse incentive for them not to be employed. [/quote] Regards, Cos On Tue, Jul 21, 2015 at 05:55PM, Pierre Smits wrote: It seems that 63% of the podling's PMC is affiliated to 1 organisation (Gridgrain). Have sufficient grounds been covered to ensure diversity and independece? Best regards, Pierre Smits On Tue, Jul 21, 2015 at 5:13 PM, Dmitriy Setrakyan dsetrak...@apache.org wrote: On Tue, Jul 21, 2015 at 4:08 AM, amareshwarisr . amareshw...@gmail.com wrote: Seems the DESCRIPTION_AND_SCOPE of the project is set to the automated and managed flow of information between systems. I dont see any such on project website - http://ignite.incubator.apache.org/ Looks like a copy from NIFI's graduation discussion - http://mail-archives.apache.org/mod_mbox/incubator-general/201506.mbox/%3CCALJK9a4PD%2B3qGGQbbHHyLfY8Ut9BP9VyEDwtnZDSWjpMKiwk9w%40mail.gmail.com%3E . You might want to correct it. Yup, copy-n-paste never works :) Corrected below. Correct me if description is fine and I'm wrong in understanding the description Thanks Amareshwari On Tue, Jul 21, 2015 at 5:06 AM, Dmitriy Setrakyan dsetrak...@apache.org wrote: Hello Apache Incubator, At the suggestion of our
Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
Please re-read the quote from Roy: There is no diversity requirement at the ASF. There is a behavior requirement for graduation and a behavior requirement for TLPs. We must not confuse the two. and later I'd urge folks to fix the docs, but I know where that leads ... and I have no cycles to spare. Thanks, Roman. On Tue, Jul 21, 2015 at 1:55 PM, jan i j...@apache.org wrote: On 21 July 2015 at 22:48, Daniel Gruno humbed...@apache.org wrote: On 07/21/2015 10:39 PM, Ted Dunning wrote: Present time diversity or lack of same is not a bar to graduation. So we should just scrap the bit in the Incubator policy that says A major criterion for graduation is to have developed an open and diverse meritocratic community.? I think not. If diversity does not matter, then please explain these references: http://www.apache.org/foundation/how-it-works.html Diversity of committership is important for two main reasons: - it gives long term stability to the project development: in fact, with all the developers affiliated to the same entity, the chance of seeing all of them moving away from the project at the same time is much greater than with a community of individuals affiliated to unrelated entities. - it gives a greater variety of technical visions: something that guarantees a better adherence to environment and user's needs, thus a higher change of finding real-life use of the software. http://www.apache.org/foundation/board/reporting - PMC and committer diversity A healthy project should survive the departure of any single contributor or employer of contributors. Healthy projects also serve needs of many parties. Thus the ASF prefers that projects have diverse PMCs and committerships. *IF* the PMC has any concerns or perceives a problem with the diversity, then the report should include information on the number of unique organizations currently represented in its PMC and committership. If diversity did not matter for TLPs, the above explanation and guidelines are false I think not. rgds jan I. What is important is that the committers and PMC of the new project understand how to make releases and are building community. On Tue, Jul 21, 2015 at 1:30 PM, Pierre Smits pierre.sm...@gmail.com wrote: Thanks, Konstantin, for the enlighting quote. And the link leading to nowhere. If we take away the names of the mentors from the list (Branko, Roman and yours) as well as those in other projects (Evans) from the list of intended project members, the situation even grows worse. Then the number grows to 77%. That doesn't look promising regarding independence, and neither regarding healthiness. Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Tue, Jul 21, 2015 at 8:53 PM, Konstantin Boudnik c...@apache.org wrote: The so-called diversity requirement has been discussed on this list for a number of times. Most recent is the graduation of Flume project (back in 2012). Here's a quote from that thread (kudos to Roy; for those who want to look it up in the archives MessageId is 73db2e64-87d5-4dd5-91fb-403464895...@gbiv.com): [quote] There is no diversity requirement at the ASF. There is a behavior requirement for graduation and a behavior requirement for TLPs. We must not confuse the two. If the Incubator says that there is a diversity requirement for graduation, ignore it (or at least figure out what the docs were supposed to say and then do that). I'd urge folks to fix the docs, but I know where that leads ... and I have no cycles to spare. A diversity requirement would mean that a person's employment status impacts their ability to participate here. IOW, it would create a perverse incentive for them not to be employed. [/quote] Regards, Cos On Tue, Jul 21, 2015 at 05:55PM, Pierre Smits wrote: It seems that 63% of the podling's PMC is affiliated to 1 organisation (Gridgrain). Have sufficient grounds been covered to ensure diversity and independece? Best regards, Pierre Smits On Tue, Jul 21, 2015 at 5:13 PM, Dmitriy Setrakyan dsetrak...@apache.org wrote: On Tue, Jul 21, 2015 at 4:08 AM, amareshwarisr . amareshw...@gmail.com wrote: Seems the DESCRIPTION_AND_SCOPE of the project is set to the automated and managed flow of information between systems. I dont see any such on project website - http://ignite.incubator.apache.org/ Looks like a copy from NIFI's graduation discussion - http://mail-archives.apache.org/mod_mbox/incubator-general/201506.mbox/%3CCALJK9a4PD%2B3qGGQbbHHyLfY8Ut9BP9VyEDwtnZDSWjpMKiwk9w%40mail.gmail.com%3E . You might want to correct it. Yup, copy-n-paste never works :) Corrected below.
Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
On Tue, Jul 21, 2015 at 10:30PM, Pierre Smits wrote: Thanks, Konstantin, for the enlighting quote. And the link leading to nowhere. Or, I didn't know that unique message Id isn't enough nowadays. Here's the easier link for your convenience ;) http://markmail.org/message/5l5hsygvntcx5fqb with the link to the overarching thread http://apache.markmail.org/message/5l5hsygvntcx5fqb?q=flume+diversity+list:org%2Eapache%2Eincubator%2Egeneral+from:+%22Roy%22 Cos If we take away the names of the mentors from the list (Branko, Roman and yours) as well as those in other projects (Evans) from the list of intended project members, the situation even grows worse. Then the number grows to 77%. That doesn't look promising regarding independence, and neither regarding healthiness. Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Tue, Jul 21, 2015 at 8:53 PM, Konstantin Boudnik c...@apache.org wrote: The so-called diversity requirement has been discussed on this list for a number of times. Most recent is the graduation of Flume project (back in 2012). Here's a quote from that thread (kudos to Roy; for those who want to look it up in the archives MessageId is 73db2e64-87d5-4dd5-91fb-403464895...@gbiv.com): [quote] There is no diversity requirement at the ASF. There is a behavior requirement for graduation and a behavior requirement for TLPs. We must not confuse the two. If the Incubator says that there is a diversity requirement for graduation, ignore it (or at least figure out what the docs were supposed to say and then do that). I'd urge folks to fix the docs, but I know where that leads ... and I have no cycles to spare. A diversity requirement would mean that a person's employment status impacts their ability to participate here. IOW, it would create a perverse incentive for them not to be employed. [/quote] Regards, Cos On Tue, Jul 21, 2015 at 05:55PM, Pierre Smits wrote: It seems that 63% of the podling's PMC is affiliated to 1 organisation (Gridgrain). Have sufficient grounds been covered to ensure diversity and independece? Best regards, Pierre Smits On Tue, Jul 21, 2015 at 5:13 PM, Dmitriy Setrakyan dsetrak...@apache.org wrote: On Tue, Jul 21, 2015 at 4:08 AM, amareshwarisr . amareshw...@gmail.com wrote: Seems the DESCRIPTION_AND_SCOPE of the project is set to the automated and managed flow of information between systems. I dont see any such on project website - http://ignite.incubator.apache.org/ Looks like a copy from NIFI's graduation discussion - http://mail-archives.apache.org/mod_mbox/incubator-general/201506.mbox/%3CCALJK9a4PD%2B3qGGQbbHHyLfY8Ut9BP9VyEDwtnZDSWjpMKiwk9w%40mail.gmail.com%3E . You might want to correct it. Yup, copy-n-paste never works :) Corrected below. Correct me if description is fine and I'm wrong in understanding the description Thanks Amareshwari On Tue, Jul 21, 2015 at 5:06 AM, Dmitriy Setrakyan dsetrak...@apache.org wrote: Hello Apache Incubator, At the suggestion of our mentors the Ignite community established consensus and held a successful vote with 14 +1 votes in favor of proposing graduation to TLP. Vote thread: http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Graduate-Apache-Ignite-from-Incubation-td1539.html Summary of the vote results: +1 (non-binding) = 14 1. Yakov Zhdanov (PMC) 2. Gianfranco Murador (PMC) 3. Ira Vasilinets (PMC) 4. Nikolai Tichinov (PMC) 5. Semyon Boikov (PMC) 6. Sergi Vladykin (PMC) 7. Alexey Goncharuk (PMC) 8. Ognen Duzlevski (PMC) 9. Valentin Kulichenko (PMC) 10. Nikita Ivanov (PMC) 11. Dmitriy Setrakyan (PMC) 12. Andrey Novikov (Committer) 13. Alexey Kuznetsov (Committer) 14. Milap Wadwa We’d like to initiate this discussion/proposal to establish a consensus within the incubator and if appropriate will initiate a vote. Below is our proposed resolution: Thank you Dmitriy Setrakyan(on behalf of the Apache Ignite PPMC) SUBJECT: Establish the Apache Ignite TLP 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 the automated and managed flow of
Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
On 21 July 2015 at 22:39, Ted Dunning ted.dunn...@gmail.com wrote: Present time diversity or lack of same is not a bar to graduation. Reading other lists, it seems to me that board is very concerned about TLPs that are dominated by one company. We (ASF) want to ensure that a project is not controlled by a company, and also that the project can survive if the company decides to do something else. That is diversity to me, and I hope to many others. It might not be a bar for leaving the incubator, but I sure hope it is a bar for getting a board approval. (and actually I thought it was a concern for incubator too). rgds jan i.
Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
Nitpicking time. Your supposedly vendor-neutral web site says: GridGain Community Edition is a binary build of Apache Ignite created by GridGain, which includes optional LGPL dependencies, such as Hibernate L2 cache integration and Geospatial Indexing. It benefits from continued testing by GridGain engineers and may contain latest bug fixes and features that will be included into the future official Apache Ignite releases. - I consider this very biased towards a single company (especially considering it is the _only_ 3rd party listed, and you do _not_ specify how other 3rd parties may get listed on the page). You start off by saying you don't endorse it, and then you praise it - it's either or. Your web site also lists the organizational affiliation of PMC members. While this may be useful internally in the ASF, I fail to see why this is mentioned on the web site. This should have no relevance to the project whatsoever. You point to gridgain.org for several of your documentation segments, this is also not acceptable. I would very much like to see this rectified before we get to an actual vote, or I will possibly be casting a -1. With regards, Daniel. On 07/21/2015 10:48 PM, Daniel Gruno wrote: On 07/21/2015 10:39 PM, Ted Dunning wrote: Present time diversity or lack of same is not a bar to graduation. So we should just scrap the bit in the Incubator policy that says A major criterion for graduation is to have developed an open and diverse meritocratic community.? I think not. What is important is that the committers and PMC of the new project understand how to make releases and are building community. On Tue, Jul 21, 2015 at 1:30 PM, Pierre Smits pierre.sm...@gmail.com wrote: Thanks, Konstantin, for the enlighting quote. And the link leading to nowhere. If we take away the names of the mentors from the list (Branko, Roman and yours) as well as those in other projects (Evans) from the list of intended project members, the situation even grows worse. Then the number grows to 77%. That doesn't look promising regarding independence, and neither regarding healthiness. Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Tue, Jul 21, 2015 at 8:53 PM, Konstantin Boudnik c...@apache.org wrote: The so-called diversity requirement has been discussed on this list for a number of times. Most recent is the graduation of Flume project (back in 2012). Here's a quote from that thread (kudos to Roy; for those who want to look it up in the archives MessageId is 73db2e64-87d5-4dd5-91fb-403464895...@gbiv.com): [quote] There is no diversity requirement at the ASF. There is a behavior requirement for graduation and a behavior requirement for TLPs. We must not confuse the two. If the Incubator says that there is a diversity requirement for graduation, ignore it (or at least figure out what the docs were supposed to say and then do that). I'd urge folks to fix the docs, but I know where that leads ... and I have no cycles to spare. A diversity requirement would mean that a person's employment status impacts their ability to participate here. IOW, it would create a perverse incentive for them not to be employed. [/quote] Regards, Cos On Tue, Jul 21, 2015 at 05:55PM, Pierre Smits wrote: It seems that 63% of the podling's PMC is affiliated to 1 organisation (Gridgrain). Have sufficient grounds been covered to ensure diversity and independece? Best regards, Pierre Smits On Tue, Jul 21, 2015 at 5:13 PM, Dmitriy Setrakyan dsetrak...@apache.org wrote: On Tue, Jul 21, 2015 at 4:08 AM, amareshwarisr . amareshw...@gmail.com wrote: Seems the DESCRIPTION_AND_SCOPE of the project is set to the automated and managed flow of information between systems. I dont see any such on project website - http://ignite.incubator.apache.org/ Looks like a copy from NIFI's graduation discussion - http://mail-archives.apache.org/mod_mbox/incubator-general/201506.mbox/%3CCALJK9a4PD%2B3qGGQbbHHyLfY8Ut9BP9VyEDwtnZDSWjpMKiwk9w%40mail.gmail.com%3E . You might want to correct it. Yup, copy-n-paste never works :) Corrected below. Correct me if description is fine and I'm wrong in understanding the description Thanks Amareshwari On Tue, Jul 21, 2015 at 5:06 AM, Dmitriy Setrakyan dsetrak...@apache.org wrote: Hello Apache Incubator, At the suggestion of our mentors the Ignite community established consensus and held a successful vote with 14 +1 votes in favor of proposing graduation to TLP. Vote thread: http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Graduate-Apache-Ignite-from-Incubation-td1539.html Summary of the vote results: +1 (non-binding) = 14 1. Yakov Zhdanov (PMC) 2. Gianfranco Murador (PMC) 3. Ira Vasilinets (PMC) 4. Nikolai Tichinov (PMC) 5. Semyon
Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
On Tue, Jul 21, 2015 at 05:13PM, P. Taylor Goetz wrote: It seems to me the spirit of the diversity statement is about project survival: A healthy project should survive the departure of any single contributor or employer of contributors. So I would think satisfying that requirement wouldn’t necessarily involve a percentage, but rather a simple number: At least 3 PMC members who are not affiliated with the employer of the majority. I think it sounds reasonable! And looks like it's all right here: there's more than 3 PMC members not affiliated with the majority's employer. Cos That way if the employer of the majority departed, there would be enough remaining members for form consensus. -Taylor On Jul 21, 2015, at 4:55 PM, jan i j...@apache.org wrote: On 21 July 2015 at 22:48, Daniel Gruno humbed...@apache.org wrote: On 07/21/2015 10:39 PM, Ted Dunning wrote: Present time diversity or lack of same is not a bar to graduation. So we should just scrap the bit in the Incubator policy that says A major criterion for graduation is to have developed an open and diverse meritocratic community.? I think not. If diversity does not matter, then please explain these references: http://www.apache.org/foundation/how-it-works.html Diversity of committership is important for two main reasons: - it gives long term stability to the project development: in fact, with all the developers affiliated to the same entity, the chance of seeing all of them moving away from the project at the same time is much greater than with a community of individuals affiliated to unrelated entities. - it gives a greater variety of technical visions: something that guarantees a better adherence to environment and user's needs, thus a higher change of finding real-life use of the software. http://www.apache.org/foundation/board/reporting - PMC and committer diversity A healthy project should survive the departure of any single contributor or employer of contributors. Healthy projects also serve needs of many parties. Thus the ASF prefers that projects have diverse PMCs and committerships. *IF* the PMC has any concerns or perceives a problem with the diversity, then the report should include information on the number of unique organizations currently represented in its PMC and committership. If diversity did not matter for TLPs, the above explanation and guidelines are false I think not. rgds jan I. What is important is that the committers and PMC of the new project understand how to make releases and are building community. On Tue, Jul 21, 2015 at 1:30 PM, Pierre Smits pierre.sm...@gmail.com wrote: Thanks, Konstantin, for the enlighting quote. And the link leading to nowhere. If we take away the names of the mentors from the list (Branko, Roman and yours) as well as those in other projects (Evans) from the list of intended project members, the situation even grows worse. Then the number grows to 77%. That doesn't look promising regarding independence, and neither regarding healthiness. Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Tue, Jul 21, 2015 at 8:53 PM, Konstantin Boudnik c...@apache.org wrote: The so-called diversity requirement has been discussed on this list for a number of times. Most recent is the graduation of Flume project (back in 2012). Here's a quote from that thread (kudos to Roy; for those who want to look it up in the archives MessageId is 73db2e64-87d5-4dd5-91fb-403464895...@gbiv.com): [quote] There is no diversity requirement at the ASF. There is a behavior requirement for graduation and a behavior requirement for TLPs. We must not confuse the two. If the Incubator says that there is a diversity requirement for graduation, ignore it (or at least figure out what the docs were supposed to say and then do that). I'd urge folks to fix the docs, but I know where that leads ... and I have no cycles to spare. A diversity requirement would mean that a person's employment status impacts their ability to participate here. IOW, it would create a perverse incentive for them not to be employed. [/quote] Regards, Cos On Tue, Jul 21, 2015 at 05:55PM, Pierre Smits wrote: It seems that 63% of the podling's PMC is affiliated to 1 organisation (Gridgrain). Have sufficient grounds been covered to ensure diversity and independece? Best regards, Pierre Smits On Tue, Jul 21, 2015 at 5:13 PM, Dmitriy Setrakyan dsetrak...@apache.org wrote: On Tue, Jul 21, 2015 at 4:08 AM, amareshwarisr . amareshw...@gmail.com wrote: Seems the
Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
On 07/21/2015 10:39 PM, Ted Dunning wrote: Present time diversity or lack of same is not a bar to graduation. So we should just scrap the bit in the Incubator policy that says A major criterion for graduation is to have developed an open and diverse meritocratic community.? I think not. What is important is that the committers and PMC of the new project understand how to make releases and are building community. On Tue, Jul 21, 2015 at 1:30 PM, Pierre Smits pierre.sm...@gmail.com wrote: Thanks, Konstantin, for the enlighting quote. And the link leading to nowhere. If we take away the names of the mentors from the list (Branko, Roman and yours) as well as those in other projects (Evans) from the list of intended project members, the situation even grows worse. Then the number grows to 77%. That doesn't look promising regarding independence, and neither regarding healthiness. Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Tue, Jul 21, 2015 at 8:53 PM, Konstantin Boudnik c...@apache.org wrote: The so-called diversity requirement has been discussed on this list for a number of times. Most recent is the graduation of Flume project (back in 2012). Here's a quote from that thread (kudos to Roy; for those who want to look it up in the archives MessageId is 73db2e64-87d5-4dd5-91fb-403464895...@gbiv.com): [quote] There is no diversity requirement at the ASF. There is a behavior requirement for graduation and a behavior requirement for TLPs. We must not confuse the two. If the Incubator says that there is a diversity requirement for graduation, ignore it (or at least figure out what the docs were supposed to say and then do that). I'd urge folks to fix the docs, but I know where that leads ... and I have no cycles to spare. A diversity requirement would mean that a person's employment status impacts their ability to participate here. IOW, it would create a perverse incentive for them not to be employed. [/quote] Regards, Cos On Tue, Jul 21, 2015 at 05:55PM, Pierre Smits wrote: It seems that 63% of the podling's PMC is affiliated to 1 organisation (Gridgrain). Have sufficient grounds been covered to ensure diversity and independece? Best regards, Pierre Smits On Tue, Jul 21, 2015 at 5:13 PM, Dmitriy Setrakyan dsetrak...@apache.org wrote: On Tue, Jul 21, 2015 at 4:08 AM, amareshwarisr . amareshw...@gmail.com wrote: Seems the DESCRIPTION_AND_SCOPE of the project is set to the automated and managed flow of information between systems. I dont see any such on project website - http://ignite.incubator.apache.org/ Looks like a copy from NIFI's graduation discussion - http://mail-archives.apache.org/mod_mbox/incubator-general/201506.mbox/%3CCALJK9a4PD%2B3qGGQbbHHyLfY8Ut9BP9VyEDwtnZDSWjpMKiwk9w%40mail.gmail.com%3E . You might want to correct it. Yup, copy-n-paste never works :) Corrected below. Correct me if description is fine and I'm wrong in understanding the description Thanks Amareshwari On Tue, Jul 21, 2015 at 5:06 AM, Dmitriy Setrakyan dsetrak...@apache.org wrote: Hello Apache Incubator, At the suggestion of our mentors the Ignite community established consensus and held a successful vote with 14 +1 votes in favor of proposing graduation to TLP. Vote thread: http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Graduate-Apache-Ignite-from-Incubation-td1539.html Summary of the vote results: +1 (non-binding) = 14 1. Yakov Zhdanov (PMC) 2. Gianfranco Murador (PMC) 3. Ira Vasilinets (PMC) 4. Nikolai Tichinov (PMC) 5. Semyon Boikov (PMC) 6. Sergi Vladykin (PMC) 7. Alexey Goncharuk (PMC) 8. Ognen Duzlevski (PMC) 9. Valentin Kulichenko (PMC) 10. Nikita Ivanov (PMC) 11. Dmitriy Setrakyan (PMC) 12. Andrey Novikov (Committer) 13. Alexey Kuznetsov (Committer) 14. Milap Wadwa We’d like to initiate this discussion/proposal to establish a consensus within the incubator and if appropriate will initiate a vote. Below is our proposed resolution: Thank you Dmitriy Setrakyan(on behalf of the Apache Ignite PPMC) SUBJECT: Establish the Apache Ignite TLP 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 the automated and managed flow of information between systems. Should be: - related to delivering an In-Memory Data Fabric - a high-performance, integrated and distributed in-memory platform for computing and transacting on large-scale data sets in real-time NOW, THEREFORE, BE IT
Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
On Wed, Jul 22, 2015 at 12:17AM, Daniel Gruno wrote: Is this a reply to me or to Pierre? I have not mentioned 63% anywhere. I have stated that we have a policy that states that a podling must have an open and diverse meritocratic community. The link you put in your reply says exactly that. it was question to Daniel because I don't see where proposed podling fails to have an open and diverse meritocratic community; alas I don't see where the alleged policy scraping is happening. The only quantitative data point I have seen so far is these 63% - hence my reference. If this conversation has any attempt to be actionable - let's at least try to be fact-of-matter. So far it was just a vague pointing to the out-of-context quotes from the Incubator's guidelines. Regards, Cos With regards, Daniel. On 2015-07-22 00:16, Konstantin Boudnik wrote: Sorry, which part of the quoted policy the 63% is allegedly scraping out? For easy reference, here's the link https://incubator.apache.org/guides/graduation.html to the document containing the section of Creating an Open and Diverse community. So far I haven't heard a single matter of fact evidence supporting your claim. Thanks Cos On Tue, Jul 21, 2015 at 10:48PM, Daniel Gruno wrote: On 07/21/2015 10:39 PM, Ted Dunning wrote: Present time diversity or lack of same is not a bar to graduation. So we should just scrap the bit in the Incubator policy that says A major criterion for graduation is to have developed an open and diverse meritocratic community.? I think not. What is important is that the committers and PMC of the new project understand how to make releases and are building community. On Tue, Jul 21, 2015 at 1:30 PM, Pierre Smits pierre.sm...@gmail.com wrote: Thanks, Konstantin, for the enlighting quote. And the link leading to nowhere. If we take away the names of the mentors from the list (Branko, Roman and yours) as well as those in other projects (Evans) from the list of intended project members, the situation even grows worse. Then the number grows to 77%. That doesn't look promising regarding independence, and neither regarding healthiness. Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Tue, Jul 21, 2015 at 8:53 PM, Konstantin Boudnik c...@apache.org wrote: The so-called diversity requirement has been discussed on this list for a number of times. Most recent is the graduation of Flume project (back in 2012). Here's a quote from that thread (kudos to Roy; for those who want to look it up in the archives MessageId is 73db2e64-87d5-4dd5-91fb-403464895...@gbiv.com): [quote] There is no diversity requirement at the ASF. There is a behavior requirement for graduation and a behavior requirement for TLPs. We must not confuse the two. If the Incubator says that there is a diversity requirement for graduation, ignore it (or at least figure out what the docs were supposed to say and then do that). I'd urge folks to fix the docs, but I know where that leads ... and I have no cycles to spare. A diversity requirement would mean that a person's employment status impacts their ability to participate here. IOW, it would create a perverse incentive for them not to be employed. [/quote] Regards, Cos On Tue, Jul 21, 2015 at 05:55PM, Pierre Smits wrote: It seems that 63% of the podling's PMC is affiliated to 1 organisation (Gridgrain). Have sufficient grounds been covered to ensure diversity and independece? Best regards, Pierre Smits On Tue, Jul 21, 2015 at 5:13 PM, Dmitriy Setrakyan dsetrak...@apache.org wrote: On Tue, Jul 21, 2015 at 4:08 AM, amareshwarisr . amareshw...@gmail.com wrote: Seems the DESCRIPTION_AND_SCOPE of the project is set to the automated and managed flow of information between systems. I dont see any such on project website - http://ignite.incubator.apache.org/ Looks like a copy from NIFI's graduation discussion - http://mail-archives.apache.org/mod_mbox/incubator-general/201506.mbox/%3CCALJK9a4PD%2B3qGGQbbHHyLfY8Ut9BP9VyEDwtnZDSWjpMKiwk9w%40mail.gmail.com%3E . You might want to correct it. Yup, copy-n-paste never works :) Corrected below. Correct me if description is fine and I'm wrong in understanding the description Thanks Amareshwari On Tue, Jul 21, 2015 at 5:06 AM, Dmitriy Setrakyan dsetrak...@apache.org wrote: Hello Apache Incubator, At the suggestion of our mentors the Ignite community established consensus and held a successful vote with 14 +1 votes in favor of proposing graduation to TLP. Vote thread: http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Graduate-Apache-Ignite-from-Incubation-td1539.html Summary of the vote results: +1 (non-binding) = 14 1. Yakov Zhdanov (PMC) 2. Gianfranco
Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
On Tue, Jul 21, 2015 at 3:04 PM, P. Taylor Goetz ptgo...@gmail.com wrote: Another minor nitpick: On the people page of the ignite website, some are tagged as PMC and there is a tag for PMC Chair. Until official graduation, that should probably change to PPMC and the PMC Chair tag be removed, since AFAIK podlings don't have VPs. Done.
Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
On Tue, Jul 21, 2015 at 2:29 PM, Daniel Gruno humbed...@apache.org wrote: The question of diversity in this case is not are we enough men/women/whatever, the question here is is there a single corporate entity with a deciding vote in the project?. Actually, I would hope that the criterion is whether there is a single corporate entity, the distraction of which would effectively kill the project. And we do need to look at Ambari as a precedent. Even now the PMC has 30 members from one company and 7 from other companies. No other company has more than two PMC members and all of the top 24 contributors are from the majority company. I would be very surprised if this project could survive a withdrawal of support from that one company. Yet we graduated Ambari without a peep. Not surprisingly, most of the votes were cast by employees of that one company. But nobody complained at all. So it behooves us as some critique Ignite for lack of diversity to ask whether precedent matters at all here. Does it?
Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
On Tue, Jul 21, 2015 at 2:08 PM, Daniel Gruno humbed...@apache.org wrote: Nitpicking time. Your supposedly vendor-neutral web site says: GridGain Community Edition is a binary build of Apache Ignite created by GridGain, which includes optional LGPL dependencies, such as Hibernate L2 cache integration and Geospatial Indexing. It benefits from continued testing by GridGain engineers and may contain latest bug fixes and features that will be included into the future official Apache Ignite releases. - I consider this very biased towards a single company (especially considering it is the _only_ 3rd party listed, and you do _not_ specify how other 3rd parties may get listed on the page). Good point. I have added text specifying how other companies can provide their community editions for Apache Ignite. You start off by saying you don't endorse it, and then you praise it - it's either or. We started out by providing just a blank link, but it became very confusing to our users, and we allowed GridGain to add a brief description. I have just updated the text of the description to strip it out of anything other than facts. I don't think it conflicts with Ignite not officially endorsing this edition. Your web site also lists the organizational affiliation of PMC members. While this may be useful internally in the ASF, I fail to see why this is mentioned on the web site. This should have no relevance to the project whatsoever. Although I see your point, I don't think it's harmful one way or another. All the community members voluntarily and willingly provided their company affiliation. You point to gridgain.org for several of your documentation segments, this is also not acceptable. This is not on purpose. The documentation was initially migrated from GridGain and some old links might have sneaked in. I cannot find any places with gridgain.org links you are referencing. Can you please point those out, so I can quickly fix them? I would very much like to see this rectified before we get to an actual vote, or I will possibly be casting a -1. With regards, Daniel. On 07/21/2015 10:48 PM, Daniel Gruno wrote: On 07/21/2015 10:39 PM, Ted Dunning wrote: Present time diversity or lack of same is not a bar to graduation. So we should just scrap the bit in the Incubator policy that says A major criterion for graduation is to have developed an open and diverse meritocratic community.? I think not. What is important is that the committers and PMC of the new project understand how to make releases and are building community. On Tue, Jul 21, 2015 at 1:30 PM, Pierre Smits pierre.sm...@gmail.com wrote: Thanks, Konstantin, for the enlighting quote. And the link leading to nowhere. If we take away the names of the mentors from the list (Branko, Roman and yours) as well as those in other projects (Evans) from the list of intended project members, the situation even grows worse. Then the number grows to 77%. That doesn't look promising regarding independence, and neither regarding healthiness. Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Tue, Jul 21, 2015 at 8:53 PM, Konstantin Boudnik c...@apache.org wrote: The so-called diversity requirement has been discussed on this list for a number of times. Most recent is the graduation of Flume project (back in 2012). Here's a quote from that thread (kudos to Roy; for those who want to look it up in the archives MessageId is 73db2e64-87d5-4dd5-91fb-403464895...@gbiv.com): [quote] There is no diversity requirement at the ASF. There is a behavior requirement for graduation and a behavior requirement for TLPs. We must not confuse the two. If the Incubator says that there is a diversity requirement for graduation, ignore it (or at least figure out what the docs were supposed to say and then do that). I'd urge folks to fix the docs, but I know where that leads ... and I have no cycles to spare. A diversity requirement would mean that a person's employment status impacts their ability to participate here. IOW, it would create a perverse incentive for them not to be employed. [/quote] Regards, Cos On Tue, Jul 21, 2015 at 05:55PM, Pierre Smits wrote: It seems that 63% of the podling's PMC is affiliated to 1 organisation (Gridgrain). Have sufficient grounds been covered to ensure diversity and independece? Best regards, Pierre Smits On Tue, Jul 21, 2015 at 5:13 PM, Dmitriy Setrakyan dsetrak...@apache.org wrote: On Tue, Jul 21, 2015 at 4:08 AM, amareshwarisr . amareshw...@gmail.com wrote: Seems the DESCRIPTION_AND_SCOPE of the project is set to the automated and managed flow of information between systems. I dont see any such on
Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
On 2015-07-22 00:15, Roman Shaposhnik wrote: On Tue, Jul 21, 2015 at 3:05 PM, Daniel Gruno humbed...@apache.org wrote: Accusation of what exactly? Quoting Roy out of context. Here's what you said: Quoting Roy out of context is not a Hail Mary you can just throw out there when someone disagrees with you. To the best of my knowledge, Roy has not been a part of the Ignite discussion, nor is he quoting policy in that particular sentence, but stating his opinion that the published Incubator policy should be overlooked (to which I disagree). Yes, he explains in rigorous detail why he thinks the way he thinks, but that is still an _opinion_, and quoting it as if it is policy (our published policy still begs to differ) is something I will consider as being out of context, Then you should've said quoting it as if it is policy. Because you see: quoting it as if it is policy != Quoting Roy out of context Precision of language in contentious online discussions is of paramount importance. This time I'll chalk up our misunderstanding to your sloppy use of language in that particular sentence. I don't believe I was being sloppy in my use of language, but I don't want to turn this into a battle over which dictionary is the best, despite your counter-accusation of my sloppy verbal skills. Which brings us back to what you actually wanted to say, which is: quoting it as if it is policy. That was NOT my intent. My intent was to *highlight* what I took as a very insightful statement made in discussion extremely similar to the one we're having here 3 years after the original discussion. Roy's statement changed the way I think about ASF and IPMC. That was all I was trying to communicate. Be that as it may, if people have concerns about it, and it's still in the policy docs, you either acknowledge and try your best to deal with these concerns, or you work to change the policy, preferably in a _separate channel_, you don't just dismiss it. I am neither agreeing nor disagreeing with whether it is the _right_ policy, I am merely stating that it IS in our published policy and that concerns have been raised relating to this. This particular bit has nothing to do with Ignite, but graduation in general. With regards, Daniel. Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
On 2015-07-22 00:41, Konstantin Boudnik wrote: On Wed, Jul 22, 2015 at 12:17AM, Daniel Gruno wrote: Is this a reply to me or to Pierre? I have not mentioned 63% anywhere. I have stated that we have a policy that states that a podling must have an open and diverse meritocratic community. The link you put in your reply says exactly that. it was question to Daniel because I don't see where proposed podling fails to have an open and diverse meritocratic community; alas I don't see where the alleged policy scraping is happening. The only quantitative data point I have seen so far is these 63% - hence my reference. I wrote scrap, not scrape. They are two different words with different meanings. I was referring to Ted's argument that diversity was not a bar to graduation, which seems to contradict our policy. Either that published policy needs to be changed (and that should be done outside this podling discussion), or the graduation needs to adhere to that policy. But simply ignoring it is not something I am willing to do. WIth regards, Daniel. If this conversation has any attempt to be actionable - let's at least try to be fact-of-matter. So far it was just a vague pointing to the out-of-context quotes from the Incubator's guidelines. Regards, Cos With regards, Daniel. On 2015-07-22 00:16, Konstantin Boudnik wrote: Sorry, which part of the quoted policy the 63% is allegedly scraping out? For easy reference, here's the link https://incubator.apache.org/guides/graduation.html to the document containing the section of Creating an Open and Diverse community. So far I haven't heard a single matter of fact evidence supporting your claim. Thanks Cos On Tue, Jul 21, 2015 at 10:48PM, Daniel Gruno wrote: On 07/21/2015 10:39 PM, Ted Dunning wrote: Present time diversity or lack of same is not a bar to graduation. So we should just scrap the bit in the Incubator policy that says A major criterion for graduation is to have developed an open and diverse meritocratic community.? I think not. What is important is that the committers and PMC of the new project understand how to make releases and are building community. On Tue, Jul 21, 2015 at 1:30 PM, Pierre Smits pierre.sm...@gmail.com wrote: Thanks, Konstantin, for the enlighting quote. And the link leading to nowhere. If we take away the names of the mentors from the list (Branko, Roman and yours) as well as those in other projects (Evans) from the list of intended project members, the situation even grows worse. Then the number grows to 77%. That doesn't look promising regarding independence, and neither regarding healthiness. Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Tue, Jul 21, 2015 at 8:53 PM, Konstantin Boudnik c...@apache.org wrote: The so-called diversity requirement has been discussed on this list for a number of times. Most recent is the graduation of Flume project (back in 2012). Here's a quote from that thread (kudos to Roy; for those who want to look it up in the archives MessageId is 73db2e64-87d5-4dd5-91fb-403464895...@gbiv.com): [quote] There is no diversity requirement at the ASF. There is a behavior requirement for graduation and a behavior requirement for TLPs. We must not confuse the two. If the Incubator says that there is a diversity requirement for graduation, ignore it (or at least figure out what the docs were supposed to say and then do that). I'd urge folks to fix the docs, but I know where that leads ... and I have no cycles to spare. A diversity requirement would mean that a person's employment status impacts their ability to participate here. IOW, it would create a perverse incentive for them not to be employed. [/quote] Regards, Cos On Tue, Jul 21, 2015 at 05:55PM, Pierre Smits wrote: It seems that 63% of the podling's PMC is affiliated to 1 organisation (Gridgrain). Have sufficient grounds been covered to ensure diversity and independece? Best regards, Pierre Smits On Tue, Jul 21, 2015 at 5:13 PM, Dmitriy Setrakyan dsetrak...@apache.org wrote: On Tue, Jul 21, 2015 at 4:08 AM, amareshwarisr . amareshw...@gmail.com wrote: Seems the DESCRIPTION_AND_SCOPE of the project is set to the automated and managed flow of information between systems. I dont see any such on project website - http://ignite.incubator.apache.org/ Looks like a copy from NIFI's graduation discussion - http://mail-archives.apache.org/mod_mbox/incubator-general/201506.mbox/%3CCALJK9a4PD%2B3qGGQbbHHyLfY8Ut9BP9VyEDwtnZDSWjpMKiwk9w%40mail.gmail.com%3E . You might want to correct it. Yup, copy-n-paste never works :) Corrected below. Correct me if description is fine and I'm wrong in understanding the description Thanks Amareshwari On Tue, Jul 21, 2015 at 5:06 AM, Dmitriy Setrakyan dsetrak...@apache.org wrote: Hello Apache Incubator, At the
Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
On Wed, Jul 22, 2015 at 12:33AM, Daniel Gruno wrote: On 2015-07-22 00:15, Roman Shaposhnik wrote: On Tue, Jul 21, 2015 at 3:05 PM, Daniel Gruno humbed...@apache.org wrote: Accusation of what exactly? Quoting Roy out of context. Here's what you said: Quoting Roy out of context is not a Hail Mary you can just throw out there when someone disagrees with you. To the best of my knowledge, Roy has not been a part of the Ignite discussion, nor is he quoting policy in that particular sentence, but stating his opinion that the published Incubator policy should be overlooked (to which I disagree). Yes, he explains in rigorous detail why he thinks the way he thinks, but that is still an _opinion_, and quoting it as if it is policy (our published policy still begs to differ) is something I will consider as being out of context, Then you should've said quoting it as if it is policy. Because you see: quoting it as if it is policy != Quoting Roy out of context Precision of language in contentious online discussions is of paramount importance. This time I'll chalk up our misunderstanding to your sloppy use of language in that particular sentence. I don't believe I was being sloppy in my use of language, but I don't want to turn this into a battle over which dictionary is the best, despite your counter-accusation of my sloppy verbal skills. Which brings us back to what you actually wanted to say, which is: quoting it as if it is policy. That was NOT my intent. My intent was to *highlight* what I took as a very insightful statement made in discussion extremely similar to the one we're having here 3 years after the original discussion. Roy's statement changed the way I think about ASF and IPMC. That was all I was trying to communicate. Be that as it may, if people have concerns about it, and it's still in the policy docs, you either acknowledge and try your best to deal with these concerns, or you work to change the policy, preferably in a _separate channel_, you don't just dismiss it. The guidelines - not the _policy_ mind you - says exactly this: A major criterion for graduation is to have developed an open and diverse meritocratic community. So far there wasn't a single fact showing that the proposed podling has failed to do this. If such facts aren't brought to the attention of the IPMC I'd suggest we just drop the matter and/or move the further policy discussions to a separate thread to establish the semantics of that statements, if so desired. Cos I am neither agreeing nor disagreeing with whether it is the _right_ policy, I am merely stating that it IS in our published policy and that concerns have been raised relating to this. This particular bit has nothing to do with Ignite, but graduation in general. With regards, Daniel. Thanks, Roman. - 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: [DISCUSSION] Graduate Ignite from the Apache Incubator
On 2015-07-22 00:47, Konstantin Boudnik wrote: On Wed, Jul 22, 2015 at 12:33AM, Daniel Gruno wrote: On 2015-07-22 00:15, Roman Shaposhnik wrote: On Tue, Jul 21, 2015 at 3:05 PM, Daniel Gruno humbed...@apache.org wrote: Accusation of what exactly? Quoting Roy out of context. Here's what you said: Quoting Roy out of context is not a Hail Mary you can just throw out there when someone disagrees with you. To the best of my knowledge, Roy has not been a part of the Ignite discussion, nor is he quoting policy in that particular sentence, but stating his opinion that the published Incubator policy should be overlooked (to which I disagree). Yes, he explains in rigorous detail why he thinks the way he thinks, but that is still an _opinion_, and quoting it as if it is policy (our published policy still begs to differ) is something I will consider as being out of context, Then you should've said quoting it as if it is policy. Because you see: quoting it as if it is policy != Quoting Roy out of context Precision of language in contentious online discussions is of paramount importance. This time I'll chalk up our misunderstanding to your sloppy use of language in that particular sentence. I don't believe I was being sloppy in my use of language, but I don't want to turn this into a battle over which dictionary is the best, despite your counter-accusation of my sloppy verbal skills. Which brings us back to what you actually wanted to say, which is: quoting it as if it is policy. That was NOT my intent. My intent was to *highlight* what I took as a very insightful statement made in discussion extremely similar to the one we're having here 3 years after the original discussion. Roy's statement changed the way I think about ASF and IPMC. That was all I was trying to communicate. Be that as it may, if people have concerns about it, and it's still in the policy docs, you either acknowledge and try your best to deal with these concerns, or you work to change the policy, preferably in a _separate channel_, you don't just dismiss it. The guidelines - not the _policy_ mind you - says exactly this: A major criterion for graduation is to have developed an open and diverse meritocratic community. The policy says the podling SHALL Demonstrate an active and diverse development community. One can argue that this is somewhat open to interpretation. So far there wasn't a single fact showing that the proposed podling has failed to do this. While there is a high concentration of PMC members from one company, yes, it is not axiomatic that this leads to bad things. I have not stated that this particular issue is a problem. If such facts aren't brought to the attention of the IPMC I'd suggest we just drop the matter and/or move the further policy discussions to a separate thread to establish the semantics of that statements, if so desired. I would very much like that :) Clearly there is disagreement in the Incubator on the importance and meaning of this specific element of the published policy. With regards, Daniel. Cos I am neither agreeing nor disagreeing with whether it is the _right_ policy, I am merely stating that it IS in our published policy and that concerns have been raised relating to this. This particular bit has nothing to do with Ignite, but graduation in general. With regards, Daniel. Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
The following page of the Incubator project states 'The project is not highly dependent on any single contributor (there are at least 3 legally independent committers and there is no single company or entity that is vital to the success of the project)'. https://incubator.apache.org/incubation/Incubation_Policy.html#Minimum+Graduation+Requirements The latter part of that statement ( there is no single company or entity that is vital to the success of the project) in the policy document is very clear. Proposing a group of privileged contributors of which 63% is affiliated to one organisation can not be regarded as anything else than that a single company has a disproportional influence on the project. Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com
Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
On Wed, Jul 22, 2015 at 12:38AM, Daniel Gruno wrote: On 2015-07-22 00:41, Konstantin Boudnik wrote: On Wed, Jul 22, 2015 at 12:17AM, Daniel Gruno wrote: Is this a reply to me or to Pierre? I have not mentioned 63% anywhere. I have stated that we have a policy that states that a podling must have an open and diverse meritocratic community. The link you put in your reply says exactly that. it was question to Daniel because I don't see where proposed podling fails to have an open and diverse meritocratic community; alas I don't see where the alleged policy scraping is happening. The only quantitative data point I have seen so far is these 63% - hence my reference. I wrote scrap, not scrape. They are two different words with different meanings. Sorry, of course scrap - damn phone auto-incorrect ;) I was referring to Ted's argument that diversity was not a bar to graduation, which seems to contradict our policy. I let Ted to address your comment. Either that published policy needs to be changed (and that should be done outside this podling discussion), or the graduation needs to adhere to that policy. But simply ignoring it is not something I am willing to do. Ignoring what exactly? The diverse language in the Incubator guidelines (again, not the policy) is extremely vague and is evidently a subject to all sorts of interpretations. But let's have a further discussion about the exact semantics of it elsewhere, if desired. Cos WIth regards, Daniel. If this conversation has any attempt to be actionable - let's at least try to be fact-of-matter. So far it was just a vague pointing to the out-of-context quotes from the Incubator's guidelines. Regards, Cos With regards, Daniel. On 2015-07-22 00:16, Konstantin Boudnik wrote: Sorry, which part of the quoted policy the 63% is allegedly scraping out? For easy reference, here's the link https://incubator.apache.org/guides/graduation.html to the document containing the section of Creating an Open and Diverse community. So far I haven't heard a single matter of fact evidence supporting your claim. Thanks Cos On Tue, Jul 21, 2015 at 10:48PM, Daniel Gruno wrote: On 07/21/2015 10:39 PM, Ted Dunning wrote: Present time diversity or lack of same is not a bar to graduation. So we should just scrap the bit in the Incubator policy that says A major criterion for graduation is to have developed an open and diverse meritocratic community.? I think not. What is important is that the committers and PMC of the new project understand how to make releases and are building community. On Tue, Jul 21, 2015 at 1:30 PM, Pierre Smits pierre.sm...@gmail.com wrote: Thanks, Konstantin, for the enlighting quote. And the link leading to nowhere. If we take away the names of the mentors from the list (Branko, Roman and yours) as well as those in other projects (Evans) from the list of intended project members, the situation even grows worse. Then the number grows to 77%. That doesn't look promising regarding independence, and neither regarding healthiness. Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Tue, Jul 21, 2015 at 8:53 PM, Konstantin Boudnik c...@apache.org wrote: The so-called diversity requirement has been discussed on this list for a number of times. Most recent is the graduation of Flume project (back in 2012). Here's a quote from that thread (kudos to Roy; for those who want to look it up in the archives MessageId is 73db2e64-87d5-4dd5-91fb-403464895...@gbiv.com): [quote] There is no diversity requirement at the ASF. There is a behavior requirement for graduation and a behavior requirement for TLPs. We must not confuse the two. If the Incubator says that there is a diversity requirement for graduation, ignore it (or at least figure out what the docs were supposed to say and then do that). I'd urge folks to fix the docs, but I know where that leads ... and I have no cycles to spare. A diversity requirement would mean that a person's employment status impacts their ability to participate here. IOW, it would create a perverse incentive for them not to be employed. [/quote] Regards, Cos On Tue, Jul 21, 2015 at 05:55PM, Pierre Smits wrote: It seems that 63% of the podling's PMC is affiliated to 1 organisation (Gridgrain). Have sufficient grounds been covered to ensure diversity and independece? Best regards, Pierre Smits On Tue, Jul 21, 2015 at 5:13 PM, Dmitriy Setrakyan dsetrak...@apache.org wrote: On Tue, Jul 21, 2015 at 4:08 AM, amareshwarisr . amareshw...@gmail.com wrote: Seems the DESCRIPTION_AND_SCOPE of the project is set to the automated and managed flow of information between systems. I dont see any such on project website -
Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
On Tue, Jul 21, 2015 at 7:10 PM, Ted Dunning ted.dunn...@gmail.com wrote: On Tue, Jul 21, 2015 at 2:29 PM, Daniel Gruno humbed...@apache.org wrote: The question of diversity in this case is not are we enough men/women/whatever, the question here is is there a single corporate entity with a deciding vote in the project?. Actually, I would hope that the criterion is whether there is a single corporate entity, the distraction of which would effectively kill the project. And we do need to look at Ambari as a precedent. Even now the PMC has 30 members from one company and 7 from other companies. No other company has more than two PMC members and all of the top 24 contributors are from the majority company. I would be very surprised if this project could survive a withdrawal of support from that one company. Yet we graduated Ambari without a peep. Not surprisingly, most of the votes were cast by employees of that one company. But nobody complained at all. So it behooves us as some critique Ignite for lack of diversity to ask whether precedent matters at all here. Does it? Speaking generally: I don't think so. No one noticed or complained is hardly reason to ignore problems, (if it is indeed a problem) or to say that such decisions are now binding. It might be a different matter if it was explicitly acknowledged. --David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
On 2015-07-22 01:17, Dmitriy Setrakyan wrote: On Tue, Jul 21, 2015 at 2:08 PM, Daniel Gruno humbed...@apache.org wrote: Nitpicking time. Your supposedly vendor-neutral web site says: GridGain Community Edition is a binary build of Apache Ignite created by GridGain, which includes optional LGPL dependencies, such as Hibernate L2 cache integration and Geospatial Indexing. It benefits from continued testing by GridGain engineers and may contain latest bug fixes and features that will be included into the future official Apache Ignite releases. - I consider this very biased towards a single company (especially considering it is the _only_ 3rd party listed, and you do _not_ specify how other 3rd parties may get listed on the page). Good point. I have added text specifying how other companies can provide their community editions for Apache Ignite. Excellent! You start off by saying you don't endorse it, and then you praise it - it's either or. We started out by providing just a blank link, but it became very confusing to our users, and we allowed GridGain to add a brief description. I have just updated the text of the description to strip it out of anything other than facts. I don't think it conflicts with Ignite not officially endorsing this edition. Thanks :) I still find it a bit problematic that the text infers that GridGain's 3rd party binary is somehow potentially upstream from Apache Ignite, but I will defer to Shane to decide whether that is allowed or not. Your web site also lists the organizational affiliation of PMC members. While this may be useful internally in the ASF, I fail to see why this is mentioned on the web site. This should have no relevance to the project whatsoever. Although I see your point, I don't think it's harmful one way or another. All the community members voluntarily and willingly provided their company affiliation. To be clear, I am not about to veto a graduation vote because of company affiliations, I just don't think it belongs on the page. If/when you graduate, the PMC has every right to decide this for themselves, I believe. You point to gridgain.org for several of your documentation segments, this is also not acceptable. This is not on purpose. The documentation was initially migrated from GridGain and some old links might have sneaked in. I cannot find any places with gridgain.org links you are referencing. Can you please point those out, so I can quickly fix them? http://ignite.incubator.apache.org/features/datagrid.html http://ignite.incubator.apache.org/features/igniterdd.html etc. I think you should just grep for it in your features directory, there may be more pages that refer to it. With regards, Daniel I would very much like to see this rectified before we get to an actual vote, or I will possibly be casting a -1. With regards, Daniel. On 07/21/2015 10:48 PM, Daniel Gruno wrote: On 07/21/2015 10:39 PM, Ted Dunning wrote: Present time diversity or lack of same is not a bar to graduation. So we should just scrap the bit in the Incubator policy that says A major criterion for graduation is to have developed an open and diverse meritocratic community.? I think not. What is important is that the committers and PMC of the new project understand how to make releases and are building community. On Tue, Jul 21, 2015 at 1:30 PM, Pierre Smits pierre.sm...@gmail.com wrote: Thanks, Konstantin, for the enlighting quote. And the link leading to nowhere. If we take away the names of the mentors from the list (Branko, Roman and yours) as well as those in other projects (Evans) from the list of intended project members, the situation even grows worse. Then the number grows to 77%. That doesn't look promising regarding independence, and neither regarding healthiness. Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Tue, Jul 21, 2015 at 8:53 PM, Konstantin Boudnik c...@apache.org wrote: The so-called diversity requirement has been discussed on this list for a number of times. Most recent is the graduation of Flume project (back in 2012). Here's a quote from that thread (kudos to Roy; for those who want to look it up in the archives MessageId is 73db2e64-87d5-4dd5-91fb-403464895...@gbiv.com): [quote] There is no diversity requirement at the ASF. There is a behavior requirement for graduation and a behavior requirement for TLPs. We must not confuse the two. If the Incubator says that there is a diversity requirement for graduation, ignore it (or at least figure out what the docs were supposed to say and then do that). I'd urge folks to fix the docs, but I know where that leads ... and I have no cycles to spare. A diversity requirement would mean that a person's employment status impacts their ability to participate here. IOW, it would create a perverse incentive for them
Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
Daniel- This has been discussed recently in graduations for Tez [1], Drill [2], and other projects whose continued incubation serves no purpose. They've completed a curriculum that clears their IP and introduces them to the ASF's infrastructure, procedures, and culture. The project must be open, and not threatened by the challenges that open development poses. We encourage transparency by creating a climate for projects to report honestly about diversity, rather than incentivizing corruption of that metric. As this thread demonstrates, the IPMC cannot do more. -C P.S. Please fix your quoting, or delete the tail of the message as you reply. [1] http://s.apache.org/uT4 [2] http://s.apache.org/m2u - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
(Sorry if the placement of this reply is wrong, but this thread is getting long and tarting to branch a bit...) Maybe the question we should be asking is: Has the ignite podling demonstrated sufficient dedication to diversity that it can survive as a TLP, and not be overly influenced by a single corporate entity? If the answer is yes, then I would vote +1. -Taylor On Jul 21, 2015, at 7:21 PM, David Nalley da...@gnsa.us wrote: On Tue, Jul 21, 2015 at 7:10 PM, Ted Dunning ted.dunn...@gmail.com wrote: On Tue, Jul 21, 2015 at 2:29 PM, Daniel Gruno humbed...@apache.org wrote: The question of diversity in this case is not are we enough men/women/whatever, the question here is is there a single corporate entity with a deciding vote in the project?. Actually, I would hope that the criterion is whether there is a single corporate entity, the distraction of which would effectively kill the project. And we do need to look at Ambari as a precedent. Even now the PMC has 30 members from one company and 7 from other companies. No other company has more than two PMC members and all of the top 24 contributors are from the majority company. I would be very surprised if this project could survive a withdrawal of support from that one company. Yet we graduated Ambari without a peep. Not surprisingly, most of the votes were cast by employees of that one company. But nobody complained at all. So it behooves us as some critique Ignite for lack of diversity to ask whether precedent matters at all here. Does it? Speaking generally: I don't think so. No one noticed or complained is hardly reason to ignore problems, (if it is indeed a problem) or to say that such decisions are now binding. It might be a different matter if it was explicitly acknowledged. --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
[DISCUSS] Diversity policy (WAS: Re: [DISCUSSION] Graduate Ignite from the Apache Incubator)
On 07/22/2015 01:36 AM, Chris Douglas wrote: Daniel- This has been discussed recently in graduations for Tez [1], Drill [2], and other projects whose continued incubation serves no purpose. If by this you mean the Incubator has taught the podling what it needs to know, and the podling is following the best practices of the Apache Way, then we are in full agreement. I don't see the need to single me out here, I am not disagreeing with that. I am saying that we have a published policy which states that a podling SHALL demonstrate an active and diverse development community. Some people are having concerns about this particular item, some are saying it's irrelevant. I don't think it's irrelevant when it is in our policy. If the IPMC feels this policy is too vague or outright wrong, then we should have a discussion about what we're going to do about that, and then act on it. But as it stand, the policy states that for a project to be considered for graduation, it shall demonstrate diversity, and people are in their right to raise that as a concern, as it is _in the policy_, regardless of what a segment of the IPMC have decided in other graduation discussions or votes. There was a discussion 3 years ago about this, but it did not result in a change in our published policy. The policy is still there. If we are interested in changing that policy, we should agree on a change in a discussion with that as the main topic, and then _write it down_. We should not have to refer to discussions where this _may have come up off-topic or as a side note_, that is not fair to people trying to find out what our practices are. With regards, Daniel. They've completed a curriculum that clears their IP and introduces them to the ASF's infrastructure, procedures, and culture. The project must be open, and not threatened by the challenges that open development poses. We encourage transparency by creating a climate for projects to report honestly about diversity, rather than incentivizing corruption of that metric. As this thread demonstrates, the IPMC cannot do more. -C P.S. Please fix your quoting, or delete the tail of the message as you reply. [1] http://s.apache.org/uT4 [2] http://s.apache.org/m2u - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
On Tue, Jul 21, 2015 at 4:26 PM, Daniel Gruno humbed...@apache.org wrote: On 2015-07-22 01:17, Dmitriy Setrakyan wrote: On Tue, Jul 21, 2015 at 2:08 PM, Daniel Gruno humbed...@apache.org wrote: Nitpicking time. Your supposedly vendor-neutral web site says: GridGain Community Edition is a binary build of Apache Ignite created by GridGain, which includes optional LGPL dependencies, such as Hibernate L2 cache integration and Geospatial Indexing. It benefits from continued testing by GridGain engineers and may contain latest bug fixes and features that will be included into the future official Apache Ignite releases. - I consider this very biased towards a single company (especially considering it is the _only_ 3rd party listed, and you do _not_ specify how other 3rd parties may get listed on the page). Good point. I have added text specifying how other companies can provide their community editions for Apache Ignite. Excellent! You start off by saying you don't endorse it, and then you praise it - it's either or. We started out by providing just a blank link, but it became very confusing to our users, and we allowed GridGain to add a brief description. I have just updated the text of the description to strip it out of anything other than facts. I don't think it conflicts with Ignite not officially endorsing this edition. Thanks :) I still find it a bit problematic that the text infers that GridGain's 3rd party binary is somehow potentially upstream from Apache Ignite, but I will defer to Shane to decide whether that is allowed or not. Your web site also lists the organizational affiliation of PMC members. While this may be useful internally in the ASF, I fail to see why this is mentioned on the web site. This should have no relevance to the project whatsoever. Although I see your point, I don't think it's harmful one way or another. All the community members voluntarily and willingly provided their company affiliation. To be clear, I am not about to veto a graduation vote because of company affiliations, I just don't think it belongs on the page. If/when you graduate, the PMC has every right to decide this for themselves, I believe. Looking at how this discussion is going, I think we should leave it as is for now in the interest of transparency. You point to gridgain.org for several of your documentation segments, this is also not acceptable. This is not on purpose. The documentation was initially migrated from GridGain and some old links might have sneaked in. I cannot find any places with gridgain.org links you are referencing. Can you please point those out, so I can quickly fix them? http://ignite.incubator.apache.org/features/datagrid.html http://ignite.incubator.apache.org/features/igniterdd.html etc. I think you should just grep for it in your features directory, there may be more pages that refer to it. I fixed it in a bunch of places by doing a grep. If you find anything I missed, please let me know.
Re: Kylin mentor
Thanks Julian to step up, as previous advisor, you already give us a lot of help and guide. Really appreciated to be Apache Kylin's official mentor. If anyone else would like to help us, please also leave message here. Thank you very much. Luke On Tue, Jul 21, 2015 at 10:30 AM, Julian Hyde jh...@apache.org wrote: Done. Thanks. On Jul 20, 2015, at 2:02 PM, Marvin Humphrey mar...@rectangular.com wrote: On Mon, Jul 20, 2015 at 1:45 PM, Julian Hyde jh...@apache.org wrote: The Kylin project has said that they would like more mentors. I have been mentoring unofficially for a while, and am happy to become an official mentor. I am already an IPMC member. Sounds great! There's no formal process for adding Mentors beyond gauging the consent of the podling community. Please add yourself as a Kylin Mentor to... * content/podlings.xml * content/projects/kylin.xml 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
[RESULT] [VOTE] Release Apache Kylin-0.7.2-incubating
This vote passes with 6 +1s and no 0 or -1 votes: +1 Justin Mclean (binding) +1 Henry Saputra (binding) +1 Owen O'Malley (binding) +1 Ted Dunning (binding) +1 Julian Hyde (binding) +1 Luke Han Thanks everyone. We’ll now roll the release out to the mirrors. Luke Han, on behalf of Apache Kylin PPMC - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Release Apache Twill-0.6.0-incubating
Hi all, This is to call for a vote on releasing Apache Twill 0.6.0-incubating. This is the seventh release for Twill. Apache Twill is an abstraction over Apache Hadoop YARN that reduces the complexity of developing distributed applications. Vote on twill-dev: http://s.apache.org/ABI Result on vote on twill-dev: http://s.apache.org/Hk4 The source tarball, including signatures, digests, etc. can be found at: https://dist.apache.org/repos/dist/dev/incubator/twill/0.6.0-incubating-rc2/src The tag to be voted upon is v0.6.0-incubating: https://git-wip-us.apache.org/repos/asf?p=incubator-twill.git;a=shortlog;h=refs/tags/v0.6.0-incubating The release hash is 518cc1a24c1ae29e46b58debe0f1a177d1589321: https://git-wip-us.apache.org/repos/asf?p=incubator-twill.git;a=commit;h=518cc1a24c1ae29e46b58debe0f1a177d1589321 The Nexus Staging URL: https://repository.apache.org/content/repositories/orgapachetwill-1017 Release artifacts are signed with the following key: https://people.apache.org/keys/committer/chtyim.asc KEYS file available: https://dist.apache.org/repos/dist/dev/incubator/twill/KEYS For information about the contents of this release, see: https://dist.apache.org/repos/dist/dev/incubator/twill/0.6.0-incubating-rc1/CHANGES.txt Please vote on releasing this package as Apache Twill 0.6.0-incubating The vote will be open for 72 hours. [ ] +1 Release this package as Apache Twill 0.6.0-incubating [ ] +0 no opinion [ ] -1 Do not release this package because ... Thanks, The Apache Twill Team - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
Seems the DESCRIPTION_AND_SCOPE of the project is set to the automated and managed flow of information between systems. I dont see any such on project website - http://ignite.incubator.apache.org/ Looks like a copy from NIFI's graduation discussion - http://mail-archives.apache.org/mod_mbox/incubator-general/201506.mbox/%3CCALJK9a4PD%2B3qGGQbbHHyLfY8Ut9BP9VyEDwtnZDSWjpMKiwk9w%40mail.gmail.com%3E. You might want to correct it. Correct me if description is fine and I'm wrong in understanding the description Thanks Amareshwari On Tue, Jul 21, 2015 at 5:06 AM, Dmitriy Setrakyan dsetrak...@apache.org wrote: Hello Apache Incubator, At the suggestion of our mentors the Ignite community established consensus and held a successful vote with 14 +1 votes in favor of proposing graduation to TLP. Vote thread: http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Graduate-Apache-Ignite-from-Incubation-td1539.html Summary of the vote results: +1 (non-binding) = 14 1. Yakov Zhdanov (PMC) 2. Gianfranco Murador (PMC) 3. Ira Vasilinets (PMC) 4. Nikolai Tichinov (PMC) 5. Semyon Boikov (PMC) 6. Sergi Vladykin (PMC) 7. Alexey Goncharuk (PMC) 8. Ognen Duzlevski (PMC) 9. Valentin Kulichenko (PMC) 10. Nikita Ivanov (PMC) 11. Dmitriy Setrakyan (PMC) 12. Andrey Novikov (Committer) 13. Alexey Kuznetsov (Committer) 14. Milap Wadwa We’d like to initiate this discussion/proposal to establish a consensus within the incubator and if appropriate will initiate a vote. Below is our proposed resolution: Thank you Dmitriy Setrakyan(on behalf of the Apache Ignite PPMC) SUBJECT: Establish the Apache Ignite TLP 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 the automated and managed flow of information between systems. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Ignite Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Ignite Project be and hereby is responsible for the creation and maintenance of software related to the automated and managed flow of information between systems and be it further RESOLVED, that the office of Vice President, Apache Ignite 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 Ignite Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Ignite 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 Ignite Project: Semyon Boikov (sboi...@apache.org) Konstantin Boudnik (c...@apache.org) Branko Čibej (br...@apache.org) Ognen Duzlevski (mak...@apache.org) Sergey Evdokimov (sevdoki...@apache.org) Alexey Goncharuk (agoncha...@apache.org) Nikita Ivanov (nivano...@apache.org) Sergey Khisamov (s...@apache.org) Valentin Kulichenko (vkuliche...@apache.org) Alexey Kuznetsov (akuznet...@apache.org) Gianfranco Murador (mura...@apache.org) Andrey Novikov (anovi...@apache.org) Vladimir Ozerov (voze...@apache.org) Dmitriy Setrakyan (dsetrak...@apache.org) Roman Shaposhnik (r...@apache.org) Ilya Sterin (iste...@apache.org) Nikolai Tikhonov (ntikho...@apache.org) Irina Vasilinets (ivasilin...@apache.org) Anton Vinogradov (a...@apache.org) Sergey Vladykin (svlady...@apache.org) Evans Ye (evan...@apache.org) Yakov Zhdanov (yzhda...@apache.org) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Dmitriy Setrakyan be appointed to the office of Vice President, Apache Ignite, 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 Ignite 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 Ignite Project; and be it further RESOLVED, that the Apache Ignite Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Ignite podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Ignite podling encumbered upon the Apache Incubator Project are hereafter
[ANNOUNCE] Apache Kylin v0.7.2-incubating released
Hello The Apache Kylin team would like to announce the release of Apache Kylin 0.7.2-incubating. Apache Kylin is an open source Distributed Analytics Engine, provides SQL interface and multi-dimensional analysis (OLAP) on Hadoop supporting extremely large datasets. More details on Apache Kylin can be found here: http://kylin.incubator.apache.org/ The release artifacts can be downloaded from here: http://kylin.incubator.apache.org/download/ Maven artifacts have been made available here: https://repository.apache.org/content/repositories/releases/org/apache/kylin/ Release notes available here: http://kylin.incubator.apache.org/docs/release_notes.html We thank everyone who made this release possible. Thanks. The Apache Kylin team DISCLAIMER Apache Kylin is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by Apache Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.
Re: [VOTE] Release Apache Kylin-0.7.2-incubating
On Mon, Jul 20, 2015 at 10:30 AM, Owen O'Malley omal...@apache.org wrote: * All of the java files are in org.apache.kylin package. Only exceptions were in the atopcalcite module: * net.hydromatic.optiq.runtime * org.eigenbase.sql2rel Are those classes coming from a different package? Do you intend to repackage them? These files are copied from apache-calcite and made small local changes. The original author is Julian Hyde. I'm sending patches to calcite so that these local override won't be required in future release. Thanks for your support! On Tue, Jul 21, 2015 at 6:15 AM, Julian Hyde jh...@apache.org wrote: +1 (binding) Checked signature and hashes. Built and ran unit tests (jdk 1.8, mac os x). Julian On Jul 20, 2015, at 1:36 PM, Ted Dunning ted.dunn...@gmail.com wrote: +1 (binding) What I did: Checked signatures and hashes Ran unit tests Ran RAT, inspected exclusions Searched for files with odd permissions, found many executable files What I suggest: Files that don't need to be executable should not be. There are 6 shell scripts in the source, but there are another 30 files that are marked as executable that should not be. On Mon, Jul 20, 2015 at 10:30 AM, Owen O'Malley omal...@apache.org wrote: * Checked GPG signature and hashes. * Built and ran unit tests. * Checked that all java files had Apache headers. * All of the java files are in org.apache.kylin package. Only exceptions were in the atopcalcite module: * net.hydromatic.optiq.runtime * org.eigenbase.sql2rel Are those classes coming from a different package? Do you intend to repackage them? +1 (binding) On Sat, Jul 18, 2015 at 12:43 AM, Henry Saputra henry.sapu...@gmail.com wrote: Signature file looks good Hashes are checked (NOTE next time probably use sha512) NOTICE file looks good LICENSE file looks good DISCLAIMER exists No 3rd party exes. +1 (binding) On Thu, Jul 16, 2015 at 9:22 PM, Luke Han luke...@apache.org wrote: Hi all, The Apache Kylin community has voted on and approved a proposal to release Apache Kylin 0.7.2 (incubating), the first release of Apache Kylin. We already have applied some suggestion in last vote attempt, please refer to below vote mail thread for detail. Proposal: http://s.apache.org/kylin-0.7.2-vote_rc2 Vote result: http://s.apache.org/kylin-0.7.2-vote_result 5 binding +1 votes 2 non-binding +1 votes No -1 votes The commit to be voted upon: https://github.com/apache/incubator-kylin/commit/f7a28422645bc209b2c38bb05b24a340444f9066 Its hash is f7a28422645bc209b2c38bb05b24a340444f9066. The artifacts to be voted on are located here: https://dist.apache.org/repos/dist/dev/incubator/kylin/apache-kylin-0.7.2-incubating-rc2/ The hashes of the artifacts are as follows: src.tar.gz.md5 334c0981d0a258f2d83402bdb75486dd src.tar.gz.sha1 c377bcb7be17e0ad5540ce2a3d1366cc0c451eda A staged Maven repository is available for review at: https://repository.apache.org/content/repositories/orgapachekylin-1008/ Release artifacts are signed with the following key: https://people.apache.org/keys/committer/lukehan.asc Pursuant to the Releases section of the Incubation Policy and with the endorsement of our mentors we would now like to request the permission of the Incubator PMC to publish the release. The vote is open for 72 hours, or until the necessary number of votes (3 +1) is reached. [ ] +1 Release this package [ ] 0 I don't feel strongly about it, but I'm okay with the release [ ] -1 Do not release this package because... +1 from Luke Luke Han, on behalf of Apache Kylin PPMC - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSSION] Graduate Ignite from the Apache Incubator
On 21.07.2015 03:26, Konstantin Boudnik wrote: Thanks for kicking off this discussion, Dmirtiy. As one of the mentors I think this podling is ready to get graduated. The process of indocrInating this group of people into the Apache Way was not always a walk in a park and we had our share of heated discussions. But the fact that the community converged into the ASF way of doing things and did it with open face makes me believe that the goal of the incubation has been achieved. There's nothing for me as a mentor to help this podling with. I second all of the above. No, scratch that. One last thing I want to do. Here it is: before we submit this resolution to the IPMC vote, let's remove the following paragraph: RESOLVED, that the initial Apache Ignite 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 Ignite Project; and be it further There's clearly no need to create any special bylaws unless the project needs to amend the common and minimal set of ASF bylaws. Having more laws makes a project worst off not better. Hence, I move to remove this clause completely. Agreed. The Ignite podling has its development and release processes adequately documented and/or automated and IMO does not need any further rules that depart from published ASF policy. -- Brane - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
