Re: [DISCUSS] Communicating intent around non-release, downstream integration binary artifacts

2015-06-25 Thread Jochen Theodorou
Am 24.06.2015 23:32, schrieb Ross Gardler (MS OPEN TECH): For HTTPd I was referring to the assertion from Justin earlier in this thread FWIW, httpd always had nightly tarballs available for consumption and testing. (though reading that now I wonder if he meant source tarballs - which is an

Re: [DISCUSS] Communicating intent around non-release, downstream integration binary artifacts

2015-06-25 Thread Jochen Theodorou
Am 24.06.2015 22:32, schrieb Emmanuel Lécharny: Le 24/06/15 22:28, David Nalley a écrit : [...] More generally to the underlying issue that prompted this discussion: With the concrete example of Geode's DockerHub presence, I don't think it's acceptable:

Re: [DISCUSS] Communicating intent around non-release, downstream integration binary artifacts

2015-06-25 Thread Emmanuel Lécharny
Le 25/06/15 09:21, Jochen Theodorou a écrit : Am 24.06.2015 22:32, schrieb Emmanuel Lécharny: Le 24/06/15 22:28, David Nalley a écrit : [...] More generally to the underlying issue that prompted this discussion: With the concrete example of Geode's DockerHub presence, I don't think it's

Re: [VOTE] Release Apache Atlas version 0.5-incubating

2015-06-25 Thread Harish Butani
+1 On Thu, Jun 25, 2015 at 12:28 PM, Arpit Gupta ar...@hortonworks.com wrote: +1 (non binding) We have been running regressions tests on this release and dont see any blockers. -- Arpit Gupta Hortonworks Inc. http://hortonworks.com/ On Jun 25, 2015, at 12:25 PM, Jakob Homan

[RESULT][VOTE] Accept Freemarker into Apache Incubator

2015-06-25 Thread Jacopo Cappellato
With 20 positive votes (13 binding and 7 non-binding) and no negative vote, the vote to accept Freemarker into the Incubator is successful. We will proceed with the project initial setup. Thank you, Jacopo +1 Pierre Smits Sergio Fernández (*) Jean-Baptiste Onofré (*) Bertrand Delacretaz (*)

Re: [VOTE] Accept Freemarker into Apache Incubator

2015-06-25 Thread Pierre Smits
Congratulations Jacopo, Best regards, Pierre Op vrijdag 26 juni 2015 heeft Jacopo Cappellato jaco...@apache.org het volgende geschreven: With 20 positive votes (13 binding and 7 non-binding) and no negative vote, the vote to accept Freemarker into the Incubator is successful. We will

Re: [DISCUSS] Communicating intent around non-release, downstream integration binary artifacts

2015-06-25 Thread Sean Busbey
On Jun 25, 2015 3:01 AM, Emmanuel Lécharny elecha...@gmail.com wrote: Le 25/06/15 09:21, Jochen Theodorou a écrit : Am 24.06.2015 22:32, schrieb Emmanuel Lécharny: Le 24/06/15 22:28, David Nalley a écrit : [...] More generally to the underlying issue that prompted this discussion: With

Re: [VOTE] Apache Ignite 1.2.0 release (RC2)

2015-06-25 Thread Branko Čibej
On 24.06.2015 08:34, Dmitriy Setrakyan wrote: On Tue, Jun 23, 2015 at 8:26 AM, Justin Mclean jus...@classsoftware.com wrote: Hi, Moreover, modules under extdata are test only and are not used anywhere in the project. They are used to test code deployment functionality. Perhaps it would be

Re: [VOTE] Release Apache Atlas version 0.5-incubating

2015-06-25 Thread Justin Mclean
HI, +1 binding I checked: - incubating in name - Signatures and check sums good - DISCLAIMER exists - LICENSE and NOTICE correct - No unexpected binaries in source - All source has apache headers - Can compile from source Thanks, Justin

Re: Licensing Issue

2015-06-25 Thread Niclas Hedhman
Ralph, yes, you might have a good point there. But that should then raise another angle. Say that I have 2 plugins for a project, both with the same set of features, and one is recommended and has ALv2, whereas the optional one is LGPL. However, a majority (say everyone) chooses the LGPL plugin,

Re: [DISCUSS] Communicating intent around non-release, downstream integration binary artifacts

2015-06-25 Thread Jochen Theodorou
Am 25.06.2015 15:13, schrieb Sean Busbey: [...] If the Docker Hub page wasn't under the control of the Geode PMC, then I'd say it was a marks violation and they'd have to seek out control of it or removal. can you explain me how that is a marks violation? bye blackdrag -- Jochen blackdrag

Re: [VOTE] Release Apache Atlas version 0.5-incubating

2015-06-25 Thread Jon Maron
+1 On Jun 24, 2015, at 9:46 PM, Venkatesh Seetharam venkat...@apache.org wrote: Hello folks, This is a call for a vote on the Apache Atlas 0.5 incubating release. A vote was held on developer mailing list and it passed with 9 +1's. Vote thread: http://s.apache.org/RyM Results

Re: Licensing Issue

2015-06-25 Thread Stefan Reich
Please - can we all stop using licenses and just open source everything? Progress is waiting for us. BTW, I am now adding all (!) programming languages to the realm of AI. (Meaning they can then be programmed automatically.) tinybrain.blog.de Cheers Stefan Am 21.06.2015 00:51 schrieb Lewis John

Re: [PROPOSAL]Pistachio

2015-06-25 Thread Gavin Li
We need more mentors. Please let me know if you are interested. THanks, Gavin Li On Mon, Jun 22, 2015 at 8:25 PM, Gavin Li lyo.ga...@gmail.com wrote: Roman, I think Pistachio is similar to Ignite in the sense that they both try to distribute the computation to storage to co-locate the data

Re: [DISCUSS] Communicating intent around non-release, downstream integration binary artifacts

2015-06-25 Thread Bertrand Delacretaz
On Thu, Jun 25, 2015 at 3:13 PM, Sean Busbey bus...@cloudera.com wrote: ...My understanding is that the Docker Hub page is under the control of the Geode PMC There's no Geode PMC, as it's a podling the Incubator PMC is in charge of their releases. Even if you ignore the fact that projects

Re: [VOTE] Release Apache Atlas version 0.5-incubating

2015-06-25 Thread Arun C Murthy
+1 (binding) Arun On Jun 24, 2015, at 6:46 PM, Venkatesh Seetharam venkat...@apache.org wrote: Hello folks, This is a call for a vote on the Apache Atlas 0.5 incubating release. A vote was held on developer mailing list and it passed with 9 +1's. Vote thread: http://s.apache.org/RyM

Re: [VOTE] Release Apache Atlas version 0.5-incubating

2015-06-25 Thread Jakob Homan
+1 (binding, forwarded from podling vote) On 25 June 2015 at 10:05, Jon Maron jma...@hortonworks.com wrote: +1 On Jun 24, 2015, at 9:46 PM, Venkatesh Seetharam venkat...@apache.org wrote: Hello folks, This is a call for a vote on the Apache Atlas 0.5 incubating release. A vote was held

Re: [VOTE] Release Apache Atlas version 0.5-incubating

2015-06-25 Thread Seetharam Venkatesh
Sorry Chris, one of the repo, codehaus is shutdown - we have already addressed this and will spin a new patch release post this. Thanks! On Thu, Jun 25, 2015 at 3:42 PM Chris Douglas cdoug...@apache.org wrote: +1 (binding) Checksum, signature OK, DISCLAIMER/LICENSE/NOTICE look OK, compile

Re: [VOTE] Release Apache Atlas version 0.5-incubating

2015-06-25 Thread Chris Douglas
+1 (binding) Checksum, signature OK, DISCLAIMER/LICENSE/NOTICE look OK, compile from source works but the package target broke for me. -C On Wed, Jun 24, 2015 at 6:46 PM, Venkatesh Seetharam venkat...@apache.org wrote: Hello folks, This is a call for a vote on the Apache Atlas 0.5 incubating

Re: [DISCUSS] Communicating intent around non-release, downstream integration binary artifacts

2015-06-25 Thread Sean Busbey
On Thu, Jun 25, 2015 at 11:06 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Thu, Jun 25, 2015 at 3:13 PM, Sean Busbey bus...@cloudera.com wrote: ...My understanding is that the Docker Hub page is under the control of the Geode PMC There's no Geode PMC, as it's a podling

Re: [VOTE] Release Apache Atlas version 0.5-incubating

2015-06-25 Thread Amareshwari Sriramdasu
+1 (binding) Verified the following : - Checksums match. - Signature looks good. - Artifacts contain incubating word. - DISCLAIMER exists. - Top level LICENSE and NOTICE files look good. - Built from source successfully. Thanks Amareshwari On Thu, Jun 25, 2015 at 7:16

Re: [DISCUSS] Communicating intent around non-release, downstream integration binary artifacts

2015-06-25 Thread Rob Vesse
On 24/06/2015 18:02, Markus Weimer mar...@weimo.de wrote: Personally I think the policy should be clarified such that nightly builds MUST only live on ASF infrastructure (whether that be the Nexus SNAPSHOTs repo, committer web space etc). As soon as you start putting them on external