Re: [RESULT] MXNet to enter the Incubator

Thanks John. For those following along - http://incubator.apache.org/projects/mxnet.html created. Mailing lists requested. On Mon, Jan 23, 2017 at 3:34 PM, John D. Ament wrote: > Nope, its not an issue. As a reminder, don't forget to create a >

Re: Binary file inclusion (was [VOTE] Apache Toree (incubating) 0.1.0-rc4 as 0.1.0)

Just FYI, Groovy had numerous such "test" jars and wrapper files and such initially. It turned out to only be a couple of hours work to remove them and build them on the fly within the build files. While I certainly see both sides of the argument about whether some "binary-like" artifacts might be

Re: [RESULT] MXNet to enter the Incubator

Nope, its not an issue. As a reminder, don't forget to create a content/projects/mxnet.xml for the project (infra requires both to get started). John On Mon, Jan 23, 2017 at 1:16 PM Henri Yandell wrote: > Heh - I was assuming Champion automatically became Mentor. Any issue

Re: [VOTE] Apache Toree (incubating) 0.1.0-rc4 as 0.1.0

Hi, > - The following test jars have been replaced with code to compile source > and build jars at runtime Great! > With regard to sbt, Apache Spark includes a build > script for sbt here: https://github.com/apache/spark/blob/master/build/sbt Can > we grab that script and use it? Sure. > -

Re: [VOTE] Release Apache Atlas 0.7.1 (incubating) RC3

Hi, +1 (binding) I checked: - incubating in name - DISCLAIMER exists - LICENSE is good - NOTICE Is good (but year needs updating) - No unexpected binary files in source release - All ASF files have apache headers - Can compile from source You may not need jQuery-placeholer or platform.js in

[VOTE] Release Apache Atlas 0.7.1 (incubating) RC3

Incubator PMC, Apache Atlas community has voted on and approved the proposal to release Apache Atlas 0.7.1 (incubating). - vote result thread: https://lists.apache.org/thread.html/3615a9f16a49a1960e7a694b6693c8b27e4600b3003e973b755e0078@%3Cdev.atlas.apache.org%3E - vote thread:

Re: Binary file inclusion (was [VOTE] Apache Toree (incubating) 0.1.0-rc4 as 0.1.0)

On 1/23/17, 9:51 AM, "John D. Ament" wrote: >> >> The gradle wrapper and similar are also not permitted. Build processes >> need to bootstrap it. >> >> >I would like to understand why, from a legal standpoint, these are not >allowed. I don't think it is a legal issue.

Re: [RESULT] MXNet to enter the Incubator

Heh - I was assuming Champion automatically became Mentor. Any issue if I do that, or have I just created red-tape hell? I think pulling the content out would be better - that way you have startup Mentor cost and recurring Mentor cost described separately. Hen On Mon, Jan 23, 2017 at 10:11 AM,

Re: [RESULT] MXNet to enter the Incubator

Henri, That's because technically speaking you're off the hook. You're only the champion of the podling, its up to the mentors now to get them bootstrapped. Since you weren't on the mentor list, you have nothing more to worry about for MXNet. I've contemplated (and still do) pulling out

Re: [RESULT] MXNet to enter the Incubator

Yeah; it was a bit tricky to find the page but I got there after working backwards from RocketMQ's JIRA issues :) Mental note that a "Vote successful; what next?" Guide might be a good idea. It didn't occur to me to go look at the Mentor doc. Hen On Mon, Jan 23, 2017 at 9:43 AM, John D. Ament

Re: Binary file inclusion (was [VOTE] Apache Toree (incubating) 0.1.0-rc4 as 0.1.0)

On Mon, Jan 23, 2017 at 8:04 AM Marvin Humphrey wrote: > On Mon, Jan 23, 2017 at 4:35 AM, John D. Ament > wrote: > > > What I'm trying to make sure we're agreeing to is > > that the problem isn't that there is a JAR to .tar.gz file in the > >

Re: [VOTE] Apache Toree (incubating) 0.1.0-rc4 as 0.1.0

Hi everyone, Based on feedback we've received regarding issues with this release candidate, we are preparing a new candidate to address those issues. - The following test jars have been replaced with code to compile source and build jars at runtime to provide the same test functionality: -

Re: [RESULT] MXNet to enter the Incubator

Henri, Compare the list of steps you're planning to take vs http://www.apache.org/dev/infra-contact#requesting-podling John On Mon, Jan 23, 2017 at 12:20 PM Henri Yandell wrote: > Vote is closed and successful. > > 7 binding +1 votes. > > Henry Saputra (hsaputra) >

[RESULT] MXNet to enter the Incubator

Vote is closed and successful. 7 binding +1 votes. Henry Saputra (hsaputra) Sebastian Schelter (ssc) Markus Weimer (weimer) Stian Soiland-Reyes(stain) Suneel Marthi (smarthi) Jean-Baptiste Onofré (jbonofre) Henri Yandell (bayard) 7 community +1 votes. Charith Elvitigala

Re: [VOTE] MXNet to enter the Incubator

Thank you everyone for your votes. I'm calling the vote closed and will send out a RESULT mail momentarily. On Mon, Jan 16, 2017 at 8:20 PM, Henri Yandell wrote: > Hi Incubator folk, > >I would like to call a vote for accepting "MXNet" for incubation in > the Apache

Re: Binary file inclusion (was [VOTE] Apache Toree (incubating) 0.1.0-rc4 as 0.1.0)

On Mon, Jan 23, 2017 at 4:35 AM, John D. Ament wrote: > What I'm trying to make sure we're agreeing to is > that the problem isn't that there is a JAR to .tar.gz file in the > distribution. Its that the original source is missing. No. Bundling jar files is not OK in

Re: Binary file inclusion (was [VOTE] Apache Toree (incubating) 0.1.0-rc4 as 0.1.0)

On Mon, Jan 23, 2017 at 3:19 AM Justin Mclean wrote: > Hi, > > > My interpretation of the term "compiled code" means compiled versions of > the source code within the package. > > So how is including a jar in a source release to which there is no source > code included

Re: [VOTE] Release Apache Ranger 0.6.3 (incubating) - rc1

I've raised a JIRA so that these concerns will get fixed: https://issues.apache.org/jira/browse/RANGER-1326 Colm. On Sat, Jan 21, 2017 at 4:37 AM, Justin Mclean wrote: > Hi, > > > I'll point out that Ranger has graduated to a TLP, so the IPMC's votes > are > >

Re: Binary file inclusion (was [VOTE] Apache Toree (incubating) 0.1.0-rc4 as 0.1.0)

Hi, > My interpretation of the term "compiled code" means compiled versions of the > source code within the package. So how is including a jar in a source release to which there is no source code included (or even a pointer to that code that I can see) actually open source software? Given