[jira] [Commented] (INCUBATOR-253) Issues with MXNet releases and their distribution

[Henri Yandell (Jira)]

[ 
https://issues.apache.org/jira/browse/INCUBATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17172716#comment-17172716
 ] 

Henri Yandell commented on INCUBATOR-253:
-

Noting that the DJL project have updated their language with regards to Apache 
MXNet, covering point 19.

The DJL package naming in point 17 is referential, it's their (ai.djl)'s 
implementation of a provider for mxnet.

> Issues with MXNet releases and their distribution
> -
>
> Key: INCUBATOR-253
> URL: https://issues.apache.org/jira/browse/INCUBATOR-253
> Project: Incubator
>  Issue Type: Improvement
>Reporter: Justin Mclean
>Assignee: Justin Mclean
>Priority: Major
>
> The main issues are:
> 1. Source and convenance binary releases containing Category X licensed code.
> 2. Website giving access to downloads of non released/unapproved code.
> 3. Website giving access to releases containing Category X licensed code.
> 4. Web site doesn't given enough warning to users of the issues with non 
> (P)PMC releases or making it clear that these are not ASF releases.
> 5. Maven releases containing Category X licensed code.
> 6. PiPy releases containing Category X licensed code.
> 7. Docker releases containing Category X licensed code.
> 8 Docker releases containing unreleased/unapproved code.
> 9. Trademark and branding issues with PiPy and Docker releases. 
> 10. Trademark and brand issues with naming of releases. 
> 11. Developer releases available to users and public searchable 
> https://repo.mxnet.io / https://dist.mxnet.io
> 12. Releases and other nightly builds on https://repo.mxnet.io / 
> https://dist.mxnet.io containing category X licensed code.
> 13. Lack of clarity on all platforms for what is an ASF release and what is 
> not.
> 14. Branding and release of 3rd parties containing unreleased code. (e.g. 
> https://docs.nvidia.com/deeplearning/frameworks/mxnet-release-notes/rel_20-03.html)
> For PiPy see:
> https://pypi.org/project/mxnet/
> For Docker see:
> https://hub.docker.com/u/mxnet
> For web site pages see:
> https://mxnet.apache.org/get_started?
> https://mxnet.apache.org/get_started/download
> I may of missed something, if so please add it.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[LAZY] Letting anyone invite on Slack

[Henri Yandell]

Currently only 'admins' can invite people to the ASF Slack:

  https://the-asf.slack.com/

If we view it as an IRC equivalent, having to invite people at all is
weird. We can, via a checkbox, change it so anyone on the ASF Slack (except
'guests') can invite someone to the Slack workspace:



Invitations

Choose whether to allow non-admins to invite new people to *ASF*.

 Allow everyone (except guests) to invite new members.


I can't see why we'd have an issue there, so I'm planning to turn that
checkbox on at the end of next week (Thursday or whenever I remember to
after that :) ).

If this is a bad idea, please object and let me know why :)

Hen

Re: Planning to remove rosters from active podlings

[Henri Yandell]

Cool - I was asked why the info was in the podling pages the other day and
all I had was "history/legacy" as an answer.


On Mon, Sep 25, 2017 at 13:33 John D. Ament  wrote:

> All,
>
> This coming weekend (9/29) I plan to remove the roster sections from all
> podling status pages.
>
> Podling rosters are meant to be managed in Whimsy.  The roster in the
> status page is redundant and end up out of sync.  In place of the roster, I
> will be adding a link automatically to all podling rosters.
>
> John
>

Discussion Forums?

[Henri Yandell]

The MXNet community have been discussing the possibilities of a discussion
forum. I suspect I'm out of date on the topic. Has there been Incubator
discussion on forums in the past few years? Are there projects running
forums? Discourse seems to be the current fashion.

My dated assumption is that Apache tends to be -1 to forums, but then we
had Nabble eking an existence on top of our lists as a semi-forum, then
StackExchange creating de facto Q forums; so perhaps user forums are a
thing now; or perhaps folk have their user@ mailing lists integrated with
discourse/stackoverflow etc?

Thanks,

Hen

Re: [VOTE] Apache MXNet (incubating) 0.11.0 release RC3

[Henri Yandell]

+1 (binding) to the release.

Minor items (fix next release):

* R-package/ directory is empty (needs removing as confusing, or a README
could be added explaining the code is not present and can be found outside
of Apache).
* Agreed with Justin that there needs to be a Getting Started text file of
some kind. This could be a link from the README.md to the docs/get_started
directory perhaps; though .md format isn't the easiest to read (ie: link to
website and over time we should consider whether a local version is needed).
* CONTRIBUTORS.md calls the project DMLC/MXNet.
* The NEWS.md refers to 0.11.0-rc3 as the latest version. This should refer
to the version being released rather than the rc3.
* The README.md also refers to rc3. It shouldn't refer to rc3 as a release,
and ideally it would refer to 0.11.0 as a release (though tricky to be
forward looking given that GitHub treats that as a homepage). Randomly
noting that the What's New should be dated.
* The README.md refers to the copyright being owned by Contributors. Needs
updating to a license statement (with NOTICE handling the copyright side of
things).

There's a lot of continual cleanup to do here; but given that this is a
project that has previously been released (pre-apache), and many of these
items are an issue in the old version (ie: existing users have already
dealt with things like no direct link from download to how to get
started/build etc), I don't see anything blocking.

Hen


On Fri, Aug 25, 2017 at 1:04 PM, Meghna Baijal 
wrote:

> Hi all
>
> This is a call for a releasing Apache MXNet (incubating) 0.11.0, release
> candidate 3.
>
> Apache MXNet community has voted and approved the release.
>
> Vote thread:
> https://lists.apache.org/thread.html/2695a598ae0622484d4c886dc5b2ea
> 823c306ca4ebef66accec6ee76@%3Cdev.mxnet.apache.org%3E <
> https://lists.apache.org/thread.html/2695a598ae0622484d4c886dc5b2ea
> 823c306ca4ebef66accec6ee76@%3Cdev.mxnet.apache.org%3E>
>
>
> Result thread:
> https://lists.apache.org/thread.html/d860c49194ec71c5c83ac0fa68df13
> 050dbfada4ff7052be3401fc1b@%3Cdev.mxnet.apache.org%3E <
> https://lists.apache.org/thread.html/d860c49194ec71c5c83ac0fa68df13
> 050dbfada4ff7052be3401fc1b@%3Cdev.mxnet.apache.org%3E>
>
>
> The source tarball, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/mxnet/0.11.0.rc3/ <
> https://dist.apache.org/repos/dist/dev/incubator/mxnet/0.11.0.rc3/>
>
>
> The release tag can be found here:
> https://github.com/apache/incubator-mxnet/tree/0.11.0.rc3 <
> https://github.com/apache/incubator-mxnet/tree/0.11.0.rc3>
>
>
> The release hash is ba6413d29769075dd883ec5fe6eb24afc98fb3fd and can be
> found here:
> https://github.com/apache/incubator-mxnet/commit/
> ba6413d29769075dd883ec5fe6eb24afc98fb3fd  incubator-mxnet/commit/ba6413d29769075dd883ec5fe6eb24afc98fb3fd>
>
>
> Release artifacts are signed with the following key:
> AA3EBCC3E65A768AE3D2A64B8EF47B8720E8C549
>
>
> KEY files are available here:
> https://dist.apache.org/repos/dist/dev/incubator/mxnet/0.11.0.rc3/ <
> https://dist.apache.org/repos/dist/dev/incubator/mxnet/0.11.0.rc3/>
>
>
> For information about the contents of this release, see:
> https://cwiki.apache.org/confluence/display/MXNET/v0.
> 11.0+Release+Notes+-+MXNet+v0.11+Release+Candidate <
> https://cwiki.apache.org/confluence/display/MXNET/v0.
> 11.0+Release+Notes+-+MXNet+v0.11+Release+Candidate>
>
>
> The vote will be open for at least 72 hours.
>
> [ ] +1 Release this package as 0.1.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>
> Thanks.
>

Re: Source Headers [Was: [VOTE] Apache MXNet (incubating) 0.11.0 release RC3]

[Henri Yandell]

On Tue, Aug 29, 2017 at 8:37 PM, John D. Ament 
wrote:

> On Tue, Aug 29, 2017 at 11:10 PM Justin Mclean 
> wrote:
>
> > Hi,
> >
> > > Just to be clear.  The issue in this case (not to confuse this
> situation
> > > with MADlib's) isn't what license applies but what copyrights apply.
> >
> > With a large number of files not having license headers and a mix of
> > Apache, BSD and MIT licenses it’s fairly similar IMO.
> >
>
> I'm looking at it a second time now.  I just realized that half of their
> source release is actually coming from repos not hosted at the ASF.  Hen,
> do you know if they have plans to move the rest over?
>
> https://github.com/dmlc/dmlc-core/tree/a527100d7d5001efc4954848a2fc60
> 27e48c05f4/include/dmlc
>
> The files in that directory carry no license headers on them, are hosted in
> an external repo.  But there is an Apache license at the root.
>

An excellent question. I think this came up in discussions on migrating
source; but I don't recall there being any decisions on list. It seems that
either a) It's a second repository that needs to be created for
apache-mxnet or b) it's an external dependency. There are 6 dependency
repositories being pulled from dmlc.

I'll raise this on dev@.

Hen

Source Headers [Was: [VOTE] Apache MXNet (incubating) 0.11.0 release RC3]

[Henri Yandell]

On Tue, Aug 29, 2017 at 6:38 PM, John D. Ament <johndam...@apache.org>
wrote:

> On Tue, Aug 29, 2017 at 9:30 PM John D. Ament <johndam...@apache.org>
> wrote:
>
> > On Tue, Aug 29, 2017 at 9:27 PM Henri Yandell <bay...@apache.org> wrote:
> >
> >> Reverted to "Copyright Contributors"?
> >>
> >>
> > Yes, for any file that we don't have full agreement (ICLA on file) we
> > can't remove the copyright claim that already exists.  Us receiving an
> ICLA
> > is what allows us to say "Licensed to the ASF" (it's in the ICLA).
> >
> > It's not a big deal, since its Apache licensed, we just have to be
> careful
> > we're removing someone's pre-existing claim.
> >
>
> I'll give a more concrete example.
>
> Let's say I imported this file into an ASF repo
> https://github.com/spring-projects/spring-framework/
> blob/v5.0.0.RC3/spring-core/src/main/java/org/springframework/util/
> StringUtils.java
>
> I wouldn't change the header to say licensed to the ASF.  None of the
> contributors have signed ICLAs.  The file header would remain in tact.  I
> would also have to carry their notice file around
> https://github.com/spring-projects/spring-framework/
> blob/v5.0.0.RC3/src/docs/dist/notice.txt
> (at
> least I'm assuming this is their NOTICE file, I can't find any others
> around)
>
>
For a concrete example with copyright Pivotal; sure - nice and easy.

In this case we have 'Copyright Contributors'. It's an empty phrase that
would just cause confusion. Because Contributor isn't defined, it looks
like a repeat of our source header:

"Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with this
work for additional information regarding copyright ownership. ... "

Perhaps the solution is to, in the NOTICE, state:

Copyright 2015-2016 by Contributors
Copyright 2017 The Apache Software Foundation

Where we could change 'by Contributors' to be more descriptive, but I seem
to recall lots of pushback at changing 3rd party source headers to make
them more understandable.

---

Note also that clause 5 of Apache 2.0 means that many of those 'contributor
license agreements' are Apache 2.0 Licenses and not SGA/ICLA/CCLA. Its
language should also cover something else published under Apache 2.0; ie)
no need for a different Apache source header.

Hen

Re: [VOTE] Apache MXNet (incubating) 0.11.0 release RC3

[Henri Yandell]

Reverted to "Copyright Contributors"?

On Tue, Aug 29, 2017 at 18:15 John D. Ament <johndam...@apache.org> wrote:

> Ok, so here's my +1 to release, with the following notes:
>
> - The NOTICE file is wrong.  Unless the dependencies listed have explicit
> notice requirements (they don't seem to) nothing needs to be added to the
> NOTICE file.
> - The source headers should be reverted in any areas where not all
> contributors to that file have signed ICLAs, otherwise we need some kind of
> agreement they are OK with moving to NOTICE file (which is how this has
> been handled in the past).
>
> Please create JIRAs to track these.
>
> John
>
> On Tue, Aug 29, 2017 at 9:09 PM Henri Yandell <bay...@apache.org> wrote:
>
> > I believe all the major contributors were ICLA'd, and I disagree that all
> > contributors need to SGA/ICLA; we don't do that for an existing project.
> >
> > We need to do the check to see how the footprint of contributions for the
> > largest contributor without an ICLA is (apologies for the horrible
> wording
> > there). There are over 400 contributors, but (quickly eyeballing) most
> are
> > covered by ICLA or small contributions. Note that we also have clause 5
> of
> > Apache 2.0 at play for historical contributions here.
> >
> > To John's point on source headers; the previous source headers said
> > "Copyright  by Contributors".
> >
> > Hen
> >
> > On Tue, Aug 29, 2017 at 11:01 Craig Russell <apache@gmail.com>
> wrote:
> >
> > > Hi Henri,
> > >
> > > If a project was developed outside Apache then everyone who contributed
> > to
> > > the project has to have an ICLA on file or file a Software Grant as
> part
> > of
> > > IP Clearance.
> > >
> > > It's not sufficient that the code has always been under the ASL 2.0.
> > >
> > > Are there any contributors to the project before it came to the
> incubator
> > > who are not now committers?
> > >
> > > Regards,
> > >
> > > Craig
> > >
> > > > On Aug 29, 2017, at 9:43 AM, Henri Yandell <bay...@apache.org>
> wrote:
> > > >
> > > > Apologies - I missed that mentors hadn't voted on the podling
> release.
> > > Will
> > > > review tonight; hopefully their mentors can do similar.
> > > >
> > > > There's no reason for an SGA here (and who would even sign it?). Code
> > has
> > > > been apache 2.0 since the initial commit on GitHub.
> > > >
> > > > On Tue, Aug 29, 2017 at 06:45 John D. Ament <johndam...@apache.org>
> > > wrote:
> > > >
> > > >> Dominic,
> > > >>
> > > >> One question, from looking a second time.  Was MXNet always Apache
> > > Licensed
> > > >> (prior to coming to the ASF)?
> > > >>
> > > >> John
> > > >>
> > > >> On Tue, Aug 29, 2017 at 8:39 AM Dominic Divakaruni <
> > > >> dominic.divakar...@gmail.com> wrote:
> > > >>
> > > >>> Thanks for the reply, John. None of the mentors have voted so far.
> > > >>> Henri, Suneel, Marcus, Sebastian, can you gents please review and
> > vote?
> > > >>>
> > > >>> Also, Henri, didn't you mention that there was an SGA for this
> > project?
> > > >>> Sorry if I don't recollect the exact details on the SGA bit.
> > > >>>
> > > >>> Dom
> > > >>>
> > > >>>
> > > >>> On Tue, Aug 29, 2017 at 5:27 AM, John D. Ament <
> > johndam...@apache.org>
> > > >>> wrote:
> > > >>>
> > > >>>> Non pmc members can vote non-binding.  Usually mentors review
> > > releases.
> > > >>>> Have any of your mentors reviewed and voted on it?  Due to there
> > being
> > > >> no
> > > >>>> SGA its a harder release to review.  I also need to cross check
> > ICLAs
> > > >> and
> > > >>>> files that have changed license.
> > > >>>>
> > > >>>> On Aug 29, 2017 8:13 AM, "Dominic Divakaruni" <
> > > >>>> dominic.divakar...@gmail.com>
> > > >>>> wrote:
> > > >>>>
> > > >>>>> Can this vote pass without the three +1's from the PMC? Can the
&

Re: [VOTE] Apache MXNet (incubating) 0.11.0 release RC3

[Henri Yandell]

I believe all the major contributors were ICLA'd, and I disagree that all
contributors need to SGA/ICLA; we don't do that for an existing project.

We need to do the check to see how the footprint of contributions for the
largest contributor without an ICLA is (apologies for the horrible wording
there). There are over 400 contributors, but (quickly eyeballing) most are
covered by ICLA or small contributions. Note that we also have clause 5 of
Apache 2.0 at play for historical contributions here.

To John's point on source headers; the previous source headers said
"Copyright  by Contributors".

Hen

On Tue, Aug 29, 2017 at 11:01 Craig Russell <apache@gmail.com> wrote:

> Hi Henri,
>
> If a project was developed outside Apache then everyone who contributed to
> the project has to have an ICLA on file or file a Software Grant as part of
> IP Clearance.
>
> It's not sufficient that the code has always been under the ASL 2.0.
>
> Are there any contributors to the project before it came to the incubator
> who are not now committers?
>
> Regards,
>
> Craig
>
> > On Aug 29, 2017, at 9:43 AM, Henri Yandell <bay...@apache.org> wrote:
> >
> > Apologies - I missed that mentors hadn't voted on the podling release.
> Will
> > review tonight; hopefully their mentors can do similar.
> >
> > There's no reason for an SGA here (and who would even sign it?). Code has
> > been apache 2.0 since the initial commit on GitHub.
> >
> > On Tue, Aug 29, 2017 at 06:45 John D. Ament <johndam...@apache.org>
> wrote:
> >
> >> Dominic,
> >>
> >> One question, from looking a second time.  Was MXNet always Apache
> Licensed
> >> (prior to coming to the ASF)?
> >>
> >> John
> >>
> >> On Tue, Aug 29, 2017 at 8:39 AM Dominic Divakaruni <
> >> dominic.divakar...@gmail.com> wrote:
> >>
> >>> Thanks for the reply, John. None of the mentors have voted so far.
> >>> Henri, Suneel, Marcus, Sebastian, can you gents please review and vote?
> >>>
> >>> Also, Henri, didn't you mention that there was an SGA for this project?
> >>> Sorry if I don't recollect the exact details on the SGA bit.
> >>>
> >>> Dom
> >>>
> >>>
> >>> On Tue, Aug 29, 2017 at 5:27 AM, John D. Ament <johndam...@apache.org>
> >>> wrote:
> >>>
> >>>> Non pmc members can vote non-binding.  Usually mentors review
> releases.
> >>>> Have any of your mentors reviewed and voted on it?  Due to there being
> >> no
> >>>> SGA its a harder release to review.  I also need to cross check ICLAs
> >> and
> >>>> files that have changed license.
> >>>>
> >>>> On Aug 29, 2017 8:13 AM, "Dominic Divakaruni" <
> >>>> dominic.divakar...@gmail.com>
> >>>> wrote:
> >>>>
> >>>>> Can this vote pass without the three +1's from the PMC? Can the
> >>>> committers
> >>>>> for this project provide binding votes on general@ to weigh in on
> >> this
> >>>>> release?
> >>>>>
> >>>>> On Mon, Aug 28, 2017 at 5:47 PM, Meghna Baijal <
> >>>> meghnabaijal2...@gmail.com
> >>>>>>
> >>>>> wrote:
> >>>>>
> >>>>>> Hi All,
> >>>>>> This is a reminder that the vote to release MXNet (incubating)
> >> 0.11.0
> >>>> is
> >>>>>> still open.
> >>>>>> The vote will close on Tuesday, August 29, 2017 8.04 PM UTC.
> >>>>>>
> >>>>>> [ ] +1 Release this package as 0.1.0
> >>>>>> [ ] +0 no opinion
> >>>>>> [ ] -1 Do not release this package because…
> >>>>>>
> >>>>>> Thanks,
> >>>>>> Meghna
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>> On Aug 25, 2017, at 1:04 PM, Meghna Baijal <
> >>>> meghnabaijal2...@gmail.com
> >>>>>>
> >>>>>> wrote:
> >>>>>>>
> >>>>>>> Hi all
> >>>>>>>
> >>>>>>> This is a call for a releasing Apache MXNet (incubating) 0.11.0,
> >>>>> release
> >>>>>>> candidate 3.
> >>>>>>>
> >>>>>>> Apache MXNet comm

Re: [VOTE] Apache MXNet (incubating) 0.11.0 release RC3

[Henri Yandell]

Apologies - I missed that mentors hadn't voted on the podling release. Will
review tonight; hopefully their mentors can do similar.

There's no reason for an SGA here (and who would even sign it?). Code has
been apache 2.0 since the initial commit on GitHub.

On Tue, Aug 29, 2017 at 06:45 John D. Ament  wrote:

> Dominic,
>
> One question, from looking a second time.  Was MXNet always Apache Licensed
> (prior to coming to the ASF)?
>
> John
>
> On Tue, Aug 29, 2017 at 8:39 AM Dominic Divakaruni <
> dominic.divakar...@gmail.com> wrote:
>
> > Thanks for the reply, John. None of the mentors have voted so far.
> > Henri, Suneel, Marcus, Sebastian, can you gents please review and vote?
> >
> > Also, Henri, didn't you mention that there was an SGA for this project?
> > Sorry if I don't recollect the exact details on the SGA bit.
> >
> > Dom
> >
> >
> > On Tue, Aug 29, 2017 at 5:27 AM, John D. Ament 
> > wrote:
> >
> > > Non pmc members can vote non-binding.  Usually mentors review releases.
> > > Have any of your mentors reviewed and voted on it?  Due to there being
> no
> > > SGA its a harder release to review.  I also need to cross check ICLAs
> and
> > > files that have changed license.
> > >
> > > On Aug 29, 2017 8:13 AM, "Dominic Divakaruni" <
> > > dominic.divakar...@gmail.com>
> > > wrote:
> > >
> > > > Can this vote pass without the three +1's from the PMC? Can the
> > > committers
> > > > for this project provide binding votes on general@ to weigh in on
> this
> > > > release?
> > > >
> > > > On Mon, Aug 28, 2017 at 5:47 PM, Meghna Baijal <
> > > meghnabaijal2...@gmail.com
> > > > >
> > > > wrote:
> > > >
> > > > > Hi All,
> > > > > This is a reminder that the vote to release MXNet (incubating)
> 0.11.0
> > > is
> > > > > still open.
> > > > > The vote will close on Tuesday, August 29, 2017 8.04 PM UTC.
> > > > >
> > > > > [ ] +1 Release this package as 0.1.0
> > > > > [ ] +0 no opinion
> > > > > [ ] -1 Do not release this package because…
> > > > >
> > > > > Thanks,
> > > > > Meghna
> > > > >
> > > > >
> > > > >
> > > > > > On Aug 25, 2017, at 1:04 PM, Meghna Baijal <
> > > meghnabaijal2...@gmail.com
> > > > >
> > > > > wrote:
> > > > > >
> > > > > > Hi all
> > > > > >
> > > > > > This is a call for a releasing Apache MXNet (incubating) 0.11.0,
> > > > release
> > > > > > candidate 3.
> > > > > >
> > > > > > Apache MXNet community has voted and approved the release.
> > > > > >
> > > > > > Vote thread:
> > > > > >
> > https://lists.apache.org/thread.html/2695a598ae0622484d4c886dc5b2ea
> > > > > 823c306ca4ebef66accec6ee76@%3Cdev.mxnet.apache.org%3E <
> > > > >
> https://lists.apache.org/thread.html/2695a598ae0622484d4c886dc5b2ea
> > > > > 823c306ca4ebef66accec6ee76@%3Cdev.mxnet.apache.org%3E>
> > > > > >
> > > > > >
> > > > > > Result thread:
> > > > > >
> > https://lists.apache.org/thread.html/d860c49194ec71c5c83ac0fa68df13
> > > > > 050dbfada4ff7052be3401fc1b@%3Cdev.mxnet.apache.org%3E <
> > > > >
> https://lists.apache.org/thread.html/d860c49194ec71c5c83ac0fa68df13
> > > > > 050dbfada4ff7052be3401fc1b@%3Cdev.mxnet.apache.org%3E>
> > > > > >
> > > > > >
> > > > > > The source tarball, including signatures, digests, etc. can be
> > found
> > > > at:
> > > > > >
> https://dist.apache.org/repos/dist/dev/incubator/mxnet/0.11.0.rc3/
> > <
> > > > > https://dist.apache.org/repos/dist/dev/incubator/mxnet/0.11.0.rc3/
> >
> > > > > >
> > > > > >
> > > > > > The release tag can be found here:
> > > > > > https://github.com/apache/incubator-mxnet/tree/0.11.0.rc3 <
> > > > > https://github.com/apache/incubator-mxnet/tree/0.11.0.rc3>
> > > > > >
> > > > > >
> > > > > > The release hash is ba6413d29769075dd883ec5fe6eb24afc98fb3fd and
> > can
> > > > be
> > > > > found here:
> > > > > > https://github.com/apache/incubator-mxnet/commit/
> > > > > ba6413d29769075dd883ec5fe6eb24afc98fb3fd <
> https://github.com/apache/
> > > > > incubator-mxnet/commit/ba6413d29769075dd883ec5fe6eb24afc98fb3fd>
> > > > > >
> > > > > >
> > > > > > Release artifacts are signed with the following key:
> > > > > > AA3EBCC3E65A768AE3D2A64B8EF47B8720E8C549
> > > > > >
> > > > > >
> > > > > > KEY files are available here:
> > > > > >
> https://dist.apache.org/repos/dist/dev/incubator/mxnet/0.11.0.rc3/
> > <
> > > > > https://dist.apache.org/repos/dist/dev/incubator/mxnet/0.11.0.rc3/
> >
> > > > > >
> > > > > >
> > > > > > For information about the contents of this release, see:
> > > > > > https://cwiki.apache.org/confluence/display/MXNET/v0.
> > > > > 11.0+Release+Notes+-+MXNet+v0.11+Release+Candidate <
> > > > > https://cwiki.apache.org/confluence/display/MXNET/v0.
> > > > > 11.0+Release+Notes+-+MXNet+v0.11+Release+Candidate>
> > > > > >
> > > > > >
> > > > > > The vote will be open for at least 72 hours.
> > > > > >
> > > > > > [ ] +1 Release this package as 0.1.0
> > > > > > [ ] +0 no opinion
> > > > > > [ ] -1 Do not release this package because...
> > > > > >
> > > > > > Thanks.
> > > > >
> > 

Two more additions to Jenkins

[Henri Yandell]

Hi Incubator folk with Chair permissions,

Could someone add cjolivier01 (Chris) and skm (Sandeep) to Jenkins for
MXNet please?

Thanks,

Hen

Re: Two additions to Jenkins

[Henri Yandell]

Thank you John :)

On Tue, Jul 18, 2017 at 4:54 AM, John D. Ament <johndam...@apache.org>
wrote:

> Both have been added.
>
> On Tue, Jul 18, 2017 at 5:44 AM Henri Yandell <bay...@apache.org> wrote:
>
> > Hi PMC-Chair type folk on general@incubator.
> >
> > Could someone add Naveen Swamy (nswamy@) and Mu Li (muli@) to the
> Jenkins
> > ldap group please.
> >
> > Thank you,
> >
> > Hen
> >
>

Two additions to Jenkins

[Henri Yandell]

Hi PMC-Chair type folk on general@incubator.

Could someone add Naveen Swamy (nswamy@) and Mu Li (muli@) to the Jenkins
ldap group please.

Thank you,

Hen

ZeroMQ licensing in Apache MXNet

[Henri Yandell]

One of the items that is on the list to do before releasing Apache MXNet is
removing ZeroMQ from the codebase/dependencies.

ZeroMQ is licensed under the LGPL 3.0 with an exception for static
compiling.

They have long been interested in relicensing to MPL 2.0, but haven't made
much progress, though they did relicense JeroMQ (Java
wrapper/implementaiton) last year.

In the last few months they've made a lot of progress towards relicensing:
https://github.com/zeromq/libzmq/tree/master/RELICENSE

I'd like to ask on legal-discuss@ for an exception (one year?) to continue
using ZeroMQ, with prominent documentation, in MXNet given the trend
towards MPL 2.0.

Any concerns before I do so?

Thanks,

Hen

Re: Granting access to Jenkins

[Henri Yandell]

Thank you :)

On Wed, Jun 28, 2017 at 03:10 John D. Ament <johndam...@apache.org> wrote:

> Thanks Andy.  I was just about to see if my karma now kicked in.
>
> John
>
> On Wed, Jun 28, 2017 at 6:04 AM Andy Seaborne <a...@apache.org> wrote:
>
> > Done
> >
> > On 28/06/17 10:26, Henri Yandell wrote:
> > > Could a PMC Chair type person grant access to Jenkins for Ly please
> > (login
> > > lxn2)?
> > >
> > >
> > >
> >
> https://cwiki.apache.org/confluence/display/INFRA/Jenkins#Jenkins-HowdoIgetanaccount
> > >
> > > I gave it a shot, but I don't believe I have the correct permissions.
> > >
> > > Thank you,
> > >
> > > Hen
> > >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Granting access to Jenkins

[Henri Yandell]

Could a PMC Chair type person grant access to Jenkins for Ly please (login
lxn2)?


https://cwiki.apache.org/confluence/display/INFRA/Jenkins#Jenkins-HowdoIgetanaccount

I gave it a shot, but I don't believe I have the correct permissions.

Thank you,

Hen

private list subscriptions

[Henri Yandell]

Dumb question time.

Should we encourage that @apache.org addresses are used when subscribing to
a private PMC list; and if not all PMC members have subscribed on a
podling, can one subscribe their @apache.org addresses for them?

Or should we mandate that @apache are used?

Does anything automatic happen that ensures that only committers'
addresses, or one of their preferred alternative addresses, are being used?
I'm suspecting not.

Thanks,

Hen

Re: [DISCUSSION] Apache SystemML podling graduation

[Henri Yandell]

+1. Sounds like it's passed time to discuss graduation.

There's no such thing as a perfect release, and the measure of a community
is not its ability to make a perfect release, but its ability to deal with,
and learn from, a release issue.

Hen

On Sat, May 6, 2017 at 11:04 Luciano Resende  wrote:

> John,
>
> Although the latest release had one small license issue due to recent
> changes, I don't consider that a blocking for graduation, particularly when
> we look at the past couple releases that passed without any issues trough
> IPMC.
>
> SystemML 0.12 release candidate vote at General
> https://www.mail-archive.com/general@incubator.apache.org/msg58449.html
>
> SystemML 0.13 release candidate vote at General
> https://www.mail-archive.com/general@incubator.apache.org/msg58803.html
>
> Also, we have been doing some rotation on the RM for SystemML to make sure
> others on the PPMC are comfortable building releases.
>
>
> On Sat, May 6, 2017 at 10:53 AM, John D. Ament 
> wrote:
>
> > Luciano,
> >
> > I suspect from a community standpoint SystemML is ready to go.
> >
> > I'm concerned about their ability to create ASF compliant releases.
> Their
> > current release under vote is problematic, specifically the contents of
> the
> > LICENSE file.  I would like to see the podling leave the incubator with a
> > perfect release.
> >
> > John
> >
> > On Fri, May 5, 2017 at 8:48 PM Luciano Resende 
> > wrote:
> >
> > > Apache SystemML has been under incubation since November 2015 and so
> far
> > > the project has accomplished 5 official Apache Releases, voted 4 new
> > > committers/PPMC members and has welcomed a new mentor. The community
> also
> > > continues to evangelize the project at universities, blog posts, public
> > > webcasts as well as in multiple conferences.
> > >
> > > It's time to discuss the graduation of SystemML
> > >
> > > The SystemML PPMC graduation discussion can be found here:
> > >
> > > https://www.mail-archive.com/dev@systemml.incubator.apache.
> > org/msg01457.html
> > >
> > > If SyatemML were to graduate, the proposed board resolution is being
> > > discussed/drafted at:
> > >
> > > https://www.mail-archive.com/dev@systemml.incubator.apache.
> > org/msg01728.html
> > >
> > > The optional maturity model is available at:
> > > http://systemml.apache.org/maturit <
> http://systemml.apache.org/maturity>
> > >
> > >
> > > Any thoughts, comments, questions?
> > >
> > > Thanks !
> > >
> > > Regards
> > >
> > >
> > > --
> > > Luciano Resende
> > > http://twitter.com/lresende1975
> > > http://lresende.blogspot.com/
> > >
> >
>
>
>
> --
> Luciano Resende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
>

Re: Adding committers to a PPMC

[Henri Yandell]

Doh - the UI meant I assumed I didn't have permissions as all I got on
clicking + was a Search field. I will give that feedback to the whimsical
project. I was also assuming that Whimsy gets the data from somewhere
rather than being the original source.

Thanks Craig,

Hen

On Tue, Feb 21, 2017 at 4:14 AM, Craig Russell <craig.russ...@oracle.com>
wrote:

> Hi Hen,
>
> At the bottom of the PPMC list is a big bold “+”. If you click on that,
> you can add apache ids to the PPMC.
>
> HTH,
>
> Craig
>
> > On Feb 20, 2017, at 11:36 PM, Henri Yandell <bay...@apache.org> wrote:
> >
> > When I look at https://whimsy.apache.org/roster/ppmc/mxnet - I only see
> the
> > mentors for the project listed on the PPMC. Any idea what I need to
> modify
> > to add the  original committers from the proposal to the PPMC?
> >
> > Or do the mentors have to bootstrap and vote them all on?
> >
> > Thanks,
> >
> > Hen
>
> Craig L Russell
> c...@apache.org
>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Adding committers to a PPMC

[Henri Yandell]

When I look at https://whimsy.apache.org/roster/ppmc/mxnet - I only see the
mentors for the project listed on the PPMC. Any idea what I need to modify
to add the  original committers from the proposal to the PPMC?

Or do the mentors have to bootstrap and vote them all on?

Thanks,

Hen

Adding ozawa to incubator karma

[Henri Yandell]

Hi Ted,

Could you add ozawa@ to the Incubator LDAP? He is on the MXNet project but
as he already had an Apache account he's not been granted karma as a part
of setup.

Thanks,

Hen

Re: Mentor docs: Incubator Access Authorization

[Henri Yandell]

Previously I've branched the git repo, modified and then emailed Infra
about the branch. Maybe that's an older process or because I had some Infra
or Chair privs.

Hen

On Wed, Jan 25, 2017 at 10:59 AM, John D. Ament <johndam...@apache.org>
wrote:

> TBH, I can't comprehend the first line.  Raising a PR is the only option.
> Let me see what infra guys say.
>
> On Wed, Jan 25, 2017 at 1:25 PM Henri Yandell <bay...@apache.org> wrote:
>
> > Even with that, I've found the process to edit the git file to be pain.
> >
> > I sent a pull request instead, much simpler :) Any thoughts on making
> that
> > the default instruction? It works for everyone rather than relying on PMC
> > Chair access.
> >
> > On Wed, Jan 25, 2017 at 3:37 AM, John D. Ament <johndam...@apache.org>
> > wrote:
> >
> > > Heh.  Last time I chased this one, I got as far as getting infra to
> > update
> > > the first couple of lines to note that the file was in git instead of
> in
> > > SVN (long story, before the SVN blow up the file was maintained in SVN
> > and
> > > mirrored in git, its now maintained in git and mirrored to SVN)
> > >
> > > I'll commit this.
> > >
> > > John
> > >
> > > On Wed, Jan 25, 2017 at 1:35 AM Henri Yandell <bay...@apache.org>
> wrote:
> > >
> > > > Answering myself, it went to git.
> > > >
> > > >
> > > > https://git-wip-us.apache.org/repos/asf?p=infrastructure-
> > > puppet.git;a=blob;f=modules/subversion_server/files/authorization/asf-
> > > authorization-template
> > > >
> > > > Hen
> > > >
> > > > On Tue, Jan 24, 2017 at 10:33 PM, Henri Yandell <bay...@apache.org>
> > > wrote:
> > > >
> > > > > This looks out of date:
> > > > >
> > > > >   http://incubator.apache.org/guides/mentor.html#who-auth-karma
> > > > >
> > > > > It says:
> > > > >
> > > > > 
> > > > > Incubator Access Authorization
> > > > >
> > > > > Special karma is required to authorize incubator access for
> > committers.
> > > > > This karma is limited to:
> > > > >
> > > > >- PMC Chairs (past and present)
> > > > >- Selected people in the Infrastructure team
> > > > >
> > > > > If any mentor has karma then they should authorize the committer.
> To
> > > > grant
> > > > > authorization, update:
> > > > > infrastructure/trunk/subversion/authorization/asf-
> > > authorization-template
> > > > > =
> > > > >
> > > > > That seems to have moved (been a year since I've touched this).
> > Anyone
> > > > > know where the new location is?  Or is it there and I've just lost
> > > perms
> > > > > for some reason? :)
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Hen
> > > > >
> > > > >
> > > >
> > >
> >
>

Re: Mentor docs: Incubator Access Authorization

[Henri Yandell]

Even with that, I've found the process to edit the git file to be pain.

I sent a pull request instead, much simpler :) Any thoughts on making that
the default instruction? It works for everyone rather than relying on PMC
Chair access.

On Wed, Jan 25, 2017 at 3:37 AM, John D. Ament <johndam...@apache.org>
wrote:

> Heh.  Last time I chased this one, I got as far as getting infra to update
> the first couple of lines to note that the file was in git instead of in
> SVN (long story, before the SVN blow up the file was maintained in SVN and
> mirrored in git, its now maintained in git and mirrored to SVN)
>
> I'll commit this.
>
> John
>
> On Wed, Jan 25, 2017 at 1:35 AM Henri Yandell <bay...@apache.org> wrote:
>
> > Answering myself, it went to git.
> >
> >
> > https://git-wip-us.apache.org/repos/asf?p=infrastructure-
> puppet.git;a=blob;f=modules/subversion_server/files/authorization/asf-
> authorization-template
> >
> > Hen
> >
> > On Tue, Jan 24, 2017 at 10:33 PM, Henri Yandell <bay...@apache.org>
> wrote:
> >
> > > This looks out of date:
> > >
> > >   http://incubator.apache.org/guides/mentor.html#who-auth-karma
> > >
> > > It says:
> > >
> > > 
> > > Incubator Access Authorization
> > >
> > > Special karma is required to authorize incubator access for committers.
> > > This karma is limited to:
> > >
> > >- PMC Chairs (past and present)
> > >- Selected people in the Infrastructure team
> > >
> > > If any mentor has karma then they should authorize the committer. To
> > grant
> > > authorization, update:
> > > infrastructure/trunk/subversion/authorization/asf-
> authorization-template
> > > =
> > >
> > > That seems to have moved (been a year since I've touched this). Anyone
> > > know where the new location is?  Or is it there and I've just lost
> perms
> > > for some reason? :)
> > >
> > > Thanks,
> > >
> > > Hen
> > >
> > >
> >
>

Re: Mentor docs: Incubator Access Authorization

[Henri Yandell]

Answering myself, it went to git.

https://git-wip-us.apache.org/repos/asf?p=infrastructure-puppet.git;a=blob;f=modules/subversion_server/files/authorization/asf-authorization-template

Hen

On Tue, Jan 24, 2017 at 10:33 PM, Henri Yandell <bay...@apache.org> wrote:

> This looks out of date:
>
>   http://incubator.apache.org/guides/mentor.html#who-auth-karma
>
> It says:
>
> 
> Incubator Access Authorization
>
> Special karma is required to authorize incubator access for committers.
> This karma is limited to:
>
>- PMC Chairs (past and present)
>- Selected people in the Infrastructure team
>
> If any mentor has karma then they should authorize the committer. To grant
> authorization, update:
> infrastructure/trunk/subversion/authorization/asf-authorization-template
> =
>
> That seems to have moved (been a year since I've touched this). Anyone
> know where the new location is?  Or is it there and I've just lost perms
> for some reason? :)
>
> Thanks,
>
> Hen
>
>

Mentor docs: Incubator Access Authorization

[Henri Yandell]

This looks out of date:

  http://incubator.apache.org/guides/mentor.html#who-auth-karma

It says:


Incubator Access Authorization

Special karma is required to authorize incubator access for committers.
This karma is limited to:

   - PMC Chairs (past and present)
   - Selected people in the Infrastructure team

If any mentor has karma then they should authorize the committer. To grant
authorization, update:
infrastructure/trunk/subversion/authorization/asf-authorization-template
=

That seems to have moved (been a year since I've touched this). Anyone know
where the new location is?  Or is it there and I've just lost perms for
some reason? :)

Thanks,

Hen

Re: [RESULT] MXNet to enter the Incubator

[Henri Yandell]

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 <johndam...@apache.org>
wrote:

> 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 <bay...@apache.org> wrote:
>
> > 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, John D. Ament <johndam...@apache.org>
> > wrote:
> >
> > > 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 podling bootstrap from the
> > > mentor guide.  Right now it makes sense since mentors are responsible
> for
> > > coordinating w/ INFRA and doing self-serve stuff.
> > >
> > > John
> > >
> > > On Mon, Jan 23, 2017 at 1:06 PM Henri Yandell <bay...@apache.org>
> wrote:
> > >
> > > > 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 <
> johndam...@apache.org>
> > > > wrote:
> > > >
> > > > > 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 <bay...@apache.org>
> > > > wrote:
> > > > >
> > > > > > 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(charithcc)
> > > > > > Lieven Govaerts   (lgo)
> > > > > > Byung-Gon Chun   (bgchun)
> > > > > > Xingjian SHI
> > > > > > Liang Chen
> > > > > > 梁德澎
> > > > > > YiZhi Liu
> > > > > >
> > > > > > I'll go ahead and start things off tonight. My intention is:
> > > > > >
> > > > > > 1) Ask Infra for the mailing lists. Once setup, I'll mail all
> > listed
> > > > > > committers with a heads up.
> > > > > > 2) Set up a project page (
> > > > > > 3) Open a Name Search JIRA item.
> > > > > > 4) Ask gstein@ (or the suitable forum) for approval to use
> GitHub
> > > for
> > > > > > issues.
> > > > > > 5) Email Infra to ask for their advice/assistance on transferring
> > > code
> > > > > (new
> > > > > > repo vs transferring existing repo etc).
> > > > > >
> > > > > > Thanks,
> > > > > >
> > > > > > Hen
> > > > > >
> > > > > > On Mon, Jan 16, 2017 at 8:20 PM, Henri Yandell <
> bay...@apache.org>
> > > > > wrote:
> > > > > >
> > > > > > > Hi Incubator folk,
> > > > > > >
> > > > > > >I would like to call a vote for accepting "MXNet" for
> > incubation
> > > > in
> > > > > > > the Apache Incubator.
> > > > > > >
> > > > > > > The full proposal is available at this wiki link:
> > > > > > >
> > > > > > > https://wiki.apache.org/incubator/MXNetProposal?
> > > > > action=recall=19
> > > > > > >
> > > > > > > I will reply to this email with a copy of the proposal.
> > > > > > >
> > > > > > > MXNet already has a broad community, which I think is clear
> from
> > > the
> > > > > > > interest from many contributors in being a part of the project
> at
> > > > > Apache.
> > > > > > > There are four mentors signed up, along with 2 or 3 other
> Apache
> > > > > > committers
> > > > > > > looking to be involved in the project.
> > > > > > >
> > > > > > > Please cast your vote:
> > > > > > >
> > > > > > >   [ ] +1, bring MXNet into the Incubator
> > > > > > >   [ ] -1, MXNet should not enter the Incubator, because...
> > > > > > >
> > > > > > >  The vote will be open for at least 72 hours, and only votes
> from
> > > the
> > > > > > > Incubator PMC are binding.
> > > > > > >
> > > > > > > As the proposer, I consider my vote already cast in favour (and
> > > > binding
> > > > > > as
> > > > > > > I'm a PMC member).
> > > > > > >
> > > > > > > Thanks all,
> > > > > > >
> > > > > > > Hen
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: [RESULT] MXNet to enter the Incubator

[Henri Yandell]

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, John D. Ament <johndam...@apache.org>
wrote:

> 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 podling bootstrap from the
> mentor guide.  Right now it makes sense since mentors are responsible for
> coordinating w/ INFRA and doing self-serve stuff.
>
> John
>
> On Mon, Jan 23, 2017 at 1:06 PM Henri Yandell <bay...@apache.org> wrote:
>
> > 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 <johndam...@apache.org>
> > wrote:
> >
> > > 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 <bay...@apache.org>
> > wrote:
> > >
> > > > 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(charithcc)
> > > > Lieven Govaerts   (lgo)
> > > > Byung-Gon Chun   (bgchun)
> > > > Xingjian SHI
> > > > Liang Chen
> > > > 梁德澎
> > > > YiZhi Liu
> > > >
> > > > I'll go ahead and start things off tonight. My intention is:
> > > >
> > > > 1) Ask Infra for the mailing lists. Once setup, I'll mail all listed
> > > > committers with a heads up.
> > > > 2) Set up a project page (
> > > > 3) Open a Name Search JIRA item.
> > > > 4) Ask gstein@ (or the suitable forum) for approval to use GitHub
> for
> > > > issues.
> > > > 5) Email Infra to ask for their advice/assistance on transferring
> code
> > > (new
> > > > repo vs transferring existing repo etc).
> > > >
> > > > Thanks,
> > > >
> > > > Hen
> > > >
> > > > On Mon, Jan 16, 2017 at 8:20 PM, Henri Yandell <bay...@apache.org>
> > > wrote:
> > > >
> > > > > Hi Incubator folk,
> > > > >
> > > > >I would like to call a vote for accepting "MXNet" for incubation
> > in
> > > > > the Apache Incubator.
> > > > >
> > > > > The full proposal is available at this wiki link:
> > > > >
> > > > > https://wiki.apache.org/incubator/MXNetProposal?
> > > action=recall=19
> > > > >
> > > > > I will reply to this email with a copy of the proposal.
> > > > >
> > > > > MXNet already has a broad community, which I think is clear from
> the
> > > > > interest from many contributors in being a part of the project at
> > > Apache.
> > > > > There are four mentors signed up, along with 2 or 3 other Apache
> > > > committers
> > > > > looking to be involved in the project.
> > > > >
> > > > > Please cast your vote:
> > > > >
> > > > >   [ ] +1, bring MXNet into the Incubator
> > > > >   [ ] -1, MXNet should not enter the Incubator, because...
> > > > >
> > > > >  The vote will be open for at least 72 hours, and only votes from
> the
> > > > > Incubator PMC are binding.
> > > > >
> > > > > As the proposer, I consider my vote already cast in favour (and
> > binding
> > > > as
> > > > > I'm a PMC member).
> > > > >
> > > > > Thanks all,
> > > > >
> > > > > Hen
> > > > >
> > > >
> > >
> >
>

Re: [RESULT] MXNet to enter the Incubator

[Henri Yandell]

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 <johndam...@apache.org>
wrote:

> 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 <bay...@apache.org> wrote:
>
> > 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(charithcc)
> > Lieven Govaerts   (lgo)
> > Byung-Gon Chun   (bgchun)
> > Xingjian SHI
> > Liang Chen
> > 梁德澎
> > YiZhi Liu
> >
> > I'll go ahead and start things off tonight. My intention is:
> >
> > 1) Ask Infra for the mailing lists. Once setup, I'll mail all listed
> > committers with a heads up.
> > 2) Set up a project page (
> > 3) Open a Name Search JIRA item.
> > 4) Ask gstein@ (or the suitable forum) for approval to use GitHub for
> > issues.
> > 5) Email Infra to ask for their advice/assistance on transferring code
> (new
> > repo vs transferring existing repo etc).
> >
> > Thanks,
> >
> > Hen
> >
> > On Mon, Jan 16, 2017 at 8:20 PM, Henri Yandell <bay...@apache.org>
> wrote:
> >
> > > Hi Incubator folk,
> > >
> > >I would like to call a vote for accepting "MXNet" for incubation in
> > > the Apache Incubator.
> > >
> > > The full proposal is available at this wiki link:
> > >
> > > https://wiki.apache.org/incubator/MXNetProposal?
> action=recall=19
> > >
> > > I will reply to this email with a copy of the proposal.
> > >
> > > MXNet already has a broad community, which I think is clear from the
> > > interest from many contributors in being a part of the project at
> Apache.
> > > There are four mentors signed up, along with 2 or 3 other Apache
> > committers
> > > looking to be involved in the project.
> > >
> > > Please cast your vote:
> > >
> > >   [ ] +1, bring MXNet into the Incubator
> > >   [ ] -1, MXNet should not enter the Incubator, because...
> > >
> > >  The vote will be open for at least 72 hours, and only votes from the
> > > Incubator PMC are binding.
> > >
> > > As the proposer, I consider my vote already cast in favour (and binding
> > as
> > > I'm a PMC member).
> > >
> > > Thanks all,
> > >
> > > Hen
> > >
> >
>

[RESULT] MXNet to enter the Incubator

[Henri Yandell]

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(charithcc)
Lieven Govaerts   (lgo)
Byung-Gon Chun   (bgchun)
Xingjian SHI
Liang Chen
梁德澎
YiZhi Liu

I'll go ahead and start things off tonight. My intention is:

1) Ask Infra for the mailing lists. Once setup, I'll mail all listed
committers with a heads up.
2) Set up a project page (
3) Open a Name Search JIRA item.
4) Ask gstein@ (or the suitable forum) for approval to use GitHub for
issues.
5) Email Infra to ask for their advice/assistance on transferring code (new
repo vs transferring existing repo etc).

Thanks,

Hen

On Mon, Jan 16, 2017 at 8:20 PM, Henri Yandell <bay...@apache.org> wrote:

> Hi Incubator folk,
>
>I would like to call a vote for accepting "MXNet" for incubation in
> the Apache Incubator.
>
> The full proposal is available at this wiki link:
>
> https://wiki.apache.org/incubator/MXNetProposal?action=recall=19
>
> I will reply to this email with a copy of the proposal.
>
> MXNet already has a broad community, which I think is clear from the
> interest from many contributors in being a part of the project at Apache.
> There are four mentors signed up, along with 2 or 3 other Apache committers
> looking to be involved in the project.
>
> Please cast your vote:
>
>   [ ] +1, bring MXNet into the Incubator
>   [ ] -1, MXNet should not enter the Incubator, because...
>
>  The vote will be open for at least 72 hours, and only votes from the
> Incubator PMC are binding.
>
> As the proposer, I consider my vote already cast in favour (and binding as
> I'm a PMC member).
>
> Thanks all,
>
> Hen
>

Re: [VOTE] MXNet to enter the Incubator

[Henri Yandell]

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 <bay...@apache.org> wrote:

> Hi Incubator folk,
>
>I would like to call a vote for accepting "MXNet" for incubation in
> the Apache Incubator.
>
> The full proposal is available at this wiki link:
>
> https://wiki.apache.org/incubator/MXNetProposal?action=recall=19
>
> I will reply to this email with a copy of the proposal.
>
> MXNet already has a broad community, which I think is clear from the
> interest from many contributors in being a part of the project at Apache.
> There are four mentors signed up, along with 2 or 3 other Apache committers
> looking to be involved in the project.
>
> Please cast your vote:
>
>   [ ] +1, bring MXNet into the Incubator
>   [ ] -1, MXNet should not enter the Incubator, because...
>
>  The vote will be open for at least 72 hours, and only votes from the
> Incubator PMC are binding.
>
> As the proposer, I consider my vote already cast in favour (and binding as
> I'm a PMC member).
>
> Thanks all,
>
> Hen
>

Re: [DISCUSS] Proposing MXNet for the Apache Incubator

[Henri Yandell]

The vote has started, so the proposal text is frozen. Assuming the vote is
successful, adding more folk can be an early order of business for the
newly created PPMC :)

Thanks,

Hen




On Mon, Jan 16, 2017 at 7:27 PM, tornadomeet wuwei 
wrote:

> hello,
>
>  Please sign me up as a committer for MXNet. i've been contributed some
> `operators` and examples to MXNet, and i'll continue contribute to MXNet in
> the furture.
>
>  GitHub ID: tornadomeet
>
> Thanks,
>
> Wei Wu
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Proposing MXNet for the Apache Incubator

[Henri Yandell]

The vote has started, so the proposal text is frozen. Assuming the vote is
successful, adding more folk can be an early order of business for the
newly created PPMC :)

Thanks,

Hen

On Tue, Jan 17, 2017 at 2:47 PM, Yihe Tang <tangy...@gmail.com> wrote:

> Hi Henri,
>
> I am Larry Tang, working with Minjie Wang (@jermainewang) on imperative
> programming part of MXNet. Please add me to the list of committers for
> MXNet project. I will work intensively on merging a NumPy interface into
> MXNet as its imperative subsystem in the next few months.
>
> My GitHub ID is: lryta
> Affiliation: University of Michigan.
>
> Best,
> Larry
>
> On 2017-01-06 00:12 (-0500), Henri Yandell <b...@apache.org> wrote:
> > Hello Incubator,>
> >
> > I'd like to propose a new incubator Apache MXNet podling.>
> >
> > The existing MXNet project (http://mxnet.io - 1.5 years old, 15
> committers,>
> > 200 contributors) is very interested in joining Apache. MXNet is an>
> > open-source deep learning framework that allows you to define, train,
> and>
> > deploy deep neural networks on a wide array of devices, from cloud>
> > infrastructure to mobile devices.>
> >
> > The wiki proposal page is located here:>
> >
> >   https://wiki.apache.org/incubator/MXNetProposal>
> >
> > I've included the text below in case anyone wants to focus on parts of
> it>
> > in a reply.>
> >
> > Looking forward to your thoughts, and for lots of interested Apache
> members>
> > to volunteer to mentor the project in addition to Sebastian and myself.>
> >
> > Currently the list of committers is based on the current active coders,
> so>
> > we're also very interested in hearing from anyone else who is interested
> in>
> > working on the project, be they current or future contributor!>
> >
> > Thanks,>
> >
> > Hen>
> > On behalf of the MXNet project>
> >
> > ->
> >
> > = MXNet: Apache Incubator Proposal =>
> >
> > == Abstract ==>
> >
> > MXNet is a Flexible and Efficient Library for Deep Learning>
> >
> > == Proposal ==>
> >
> > MXNet is an open-source deep learning framework that allows you to
> define,>
> > train, and deploy deep neural networks on a wide array of devices, from>
> > cloud infrastructure to mobile devices. It is highly scalable, allowing
> for>
> > fast model training, and supports a flexible programming model and
> multiple>
> > languages. MXNet allows you to mix symbolic and imperative programming>
> > flavors to maximize both efficiency and productivity. MXNet is built on
> a>
> > dynamic dependency scheduler that automatically parallelizes both
> symbolic>
> > and imperative operations on the fly. A graph optimization layer on top
> of>
> > that makes symbolic execution fast and memory efficient. The MXNet
> library>
> > is portable and lightweight, and it scales to multiple GPUs and multiple>
> > machines.>
> >
> > == Background ==>
> >
> > Deep learning is a subset of Machine learning and refers to a class of>
> > algorithms that use a hierarchical approach with non-linearities to>
> > discover and learn representations within data. Deep Learning has
> recently>
> > become very popular due to its applicability and advancement of domains>
> > such as Computer Vision, Speech Recognition, Natural Language
> Understanding>
> > and Recommender Systems. With pervasive and cost effective cloud
> computing,>
> > large labeled datasets and continued algorithmic innovation, Deep
> Learning>
> > has become the one of the most popular classes of algorithms for machine>
> > learning practitioners in recent years.>
> >
> > == Rational ==>
> >
> > The adoption of deep learning is quickly expanding from initial deep
> domain>
> > experts rooted in academia to data scientists and developers working to>
> > deploy intelligent services and products. Deep learning however has many>
> > challenges.  These include model training time (which can take days to>
> > weeks), programmability (not everyone writes Python or C++ and like>
> > symbolic programming) and balancing production readiness (support for>
> > things like failover) with development flexibility (ability to program>
> > different ways, support for new operators and model types) and speed of>
> > execution (fast and scalable model training).  Other frameworks excel on>
> > some but 

Re: [VOTE] MXNet to enter the Incubator

[Henri Yandell]

m/dmlc/mxnet (Core code)

Will need to discuss code migration with Infra.

Source and Intellectual Property Submission Plan

MXNet Code is available under Apache License, Version 2.0. We will work
with the committers to get CLAs signed and review previous contributions.

External Dependencies

   - required by the core code base: GCC or CLOM, Clang, any BLAS library
   (ATLAS, OpenBLAS, MKL), dmlc-core, mshadow, ps-lite (which requires
   lib-zeromq), TBB
   - required for GPU usage: cudnn, cuda
   - required for python usage: Python 2/3
   - required for R module: R, Rcpp (GPLv2+ licensing)
   - optional for image preparation and preprocessing: opencv
   - optional dependencies for additional features: torch7, numba, cython
   (in NNVM branch)

Rcpp and lib-zeromq are expected to be licensing discussions.

Cryptography

Not Applicable

Required Resources

Mailing Lists

There are currently no mailing lists.

The usual mailing lists are expected to be setup when entering incubation:

   - dev@mxnet for general development discussion and user interaction
   - private@mxnet for internal PPMC (and later PMC) discussions
   - commits@mxnet for all source repository commits

It's imagined that the discussion on Issue Tracking below has potential to
lead to an issues@mxnet list.

Issue Tracking

Currently uses GitHub <https://wiki.apache.org/incubator/GitHub> to track
issues. Would like to continue to do so. Will need to discuss migration
possibilities with Infra.

Committers and Affiliations

   - Tianqi Chen (UW)
   - Mu Li (AWS)
   - Junyuan Xie (AWS)
   - Bing Xu (Apple)
   - Chiyuan Zhang (MIT)
   - Minjie Wang (UYU)
   - Naiyan Wang (Tusimple)
   - Yizhi Liu (Qihoo 360)
   - Tong He (Simon Fraser University)
   - Qiang Kou (Indiana U)
   - Xingjian Shi (HKUST)
   - Joe Spisak (AWS)
   - Naveen Swamy (AWS)
   - Indhu Bharathi (AWS)
   - Chris Olivier (AWS)
   - Yutian Li (Stanford)
   - Yu Zhang (MIT)
   - Ziheng Jiang (AWS/Fudan University)
   - Hongliang Liu (Nominum)
   - Shiwen Hu (tbd)
   - Zihao Zheng (Alibaba Group)
   - Liang Xiang (Toutiao Lab)
   - Tsuyoshi Ozawa (NTT)
   - Terry Chen (Novumind)
   - Yifeng Geng (Horizon Robotics)
   - Jian Zhang (Horizon Robotics)
   -

   Liang DePeng <https://wiki.apache.org/incubator/DePeng> (Sun Yat-sen
   University)
   - Yuan Tang (Uptake)
   - Nan Zhu (Microsoft/Apache)
   - Felix Cheung (Microsoft/Apache)
   - Sandeep Krishnamurthy (AWS)

Sponsors

Champion

Henri Yandell (bayard at apache.org)

Nominated Mentors

   - Sebastian Schelter (ssc at apache.org)
   - Suneel Marthi (smarthi at apache.org)
   - Markus Weimer (weimer at apache.org)

Sponsoring Entity We are requesting the Incubator to sponsor this project.

[VOTE] MXNet to enter the Incubator

[Henri Yandell]

Hi Incubator folk,

   I would like to call a vote for accepting "MXNet" for incubation in the
Apache Incubator.

The full proposal is available at this wiki link:

https://wiki.apache.org/incubator/MXNetProposal?action=recall=19

I will reply to this email with a copy of the proposal.

MXNet already has a broad community, which I think is clear from the
interest from many contributors in being a part of the project at Apache.
There are four mentors signed up, along with 2 or 3 other Apache committers
looking to be involved in the project.

Please cast your vote:

  [ ] +1, bring MXNet into the Incubator
  [ ] -1, MXNet should not enter the Incubator, because...

 The vote will be open for at least 72 hours, and only votes from the
Incubator PMC are binding.

As the proposer, I consider my vote already cast in favour (and binding as
I'm a PMC member).

Thanks all,

Hen

Re: [DISCUSS] Proposing MXNet for the Apache Incubator

[Henri Yandell]

Added. Apologies if Liang DePeng is the incorrect anglicization of your
name.

Hen

On Sat, Jan 14, 2017 at 12:08 AM, 梁德澎 <liangdep...@gmail.com> wrote:

> Hi,
>
> I’ve been working on the MXNet-ScalaPkg for a while with Yizhi Liu
> (@javelinjs).
> Please sign me up as a committer of MxNet.
>
> GitHub ID: Ldpe2G
> Email: liangdep...@gmail.com
> Affiliations: Sun Yat-sen University
>
> 2017-01-14 13:49 GMT+08:00 Henri Yandell <bay...@apache.org>:
>
> > Thanks for all the feedback and interested parties :)
> >
> > My aim is to propose a vote on Monday, unless someone raises an issue
> > before then.
> >
> > Hen
> >
> > On Thu, Jan 5, 2017 at 9:12 PM, Henri Yandell <bay...@apache.org> wrote:
> >
> > > Hello Incubator,
> > >
> > > I'd like to propose a new incubator Apache MXNet podling.
> > >
> > > The existing MXNet project (http://mxnet.io - 1.5 years old, 15
> > > committers, 200 contributors) is very interested in joining Apache.
> MXNet
> > > is an open-source deep learning framework that allows you to define,
> > train,
> > > and deploy deep neural networks on a wide array of devices, from cloud
> > > infrastructure to mobile devices.
> > >
> > > The wiki proposal page is located here:
> > >
> > >   https://wiki.apache.org/incubator/MXNetProposal
> > >
> > > I've included the text below in case anyone wants to focus on parts of
> it
> > > in a reply.
> > >
> > > Looking forward to your thoughts, and for lots of interested Apache
> > > members to volunteer to mentor the project in addition to Sebastian and
> > > myself.
> > >
> > > Currently the list of committers is based on the current active coders,
> > so
> > > we're also very interested in hearing from anyone else who is
> interested
> > in
> > > working on the project, be they current or future contributor!
> > >
> > > Thanks,
> > >
> > > Hen
> > > On behalf of the MXNet project
> > >
> > > -
> > >
> > > = MXNet: Apache Incubator Proposal =
> > >
> > > == Abstract ==
> > >
> > > MXNet is a Flexible and Efficient Library for Deep Learning
> > >
> > > == Proposal ==
> > >
> > > MXNet is an open-source deep learning framework that allows you to
> > define,
> > > train, and deploy deep neural networks on a wide array of devices, from
> > > cloud infrastructure to mobile devices. It is highly scalable, allowing
> > for
> > > fast model training, and supports a flexible programming model and
> > multiple
> > > languages. MXNet allows you to mix symbolic and imperative programming
> > > flavors to maximize both efficiency and productivity. MXNet is built
> on a
> > > dynamic dependency scheduler that automatically parallelizes both
> > symbolic
> > > and imperative operations on the fly. A graph optimization layer on top
> > of
> > > that makes symbolic execution fast and memory efficient. The MXNet
> > library
> > > is portable and lightweight, and it scales to multiple GPUs and
> multiple
> > > machines.
> > >
> > > == Background ==
> > >
> > > Deep learning is a subset of Machine learning and refers to a class of
> > > algorithms that use a hierarchical approach with non-linearities to
> > > discover and learn representations within data. Deep Learning has
> > recently
> > > become very popular due to its applicability and advancement of domains
> > > such as Computer Vision, Speech Recognition, Natural Language
> > Understanding
> > > and Recommender Systems. With pervasive and cost effective cloud
> > computing,
> > > large labeled datasets and continued algorithmic innovation, Deep
> > Learning
> > > has become the one of the most popular classes of algorithms for
> machine
> > > learning practitioners in recent years.
> > >
> > > == Rational ==
> > >
> > > The adoption of deep learning is quickly expanding from initial deep
> > > domain experts rooted in academia to data scientists and developers
> > working
> > > to deploy intelligent services and products. Deep learning however has
> > many
> > > challenges.  These include model training time (which can take days to
> > > weeks), programmability (not everyone writes Python or C++ and like
> > > symbolic programming) and balancing 

Re: [DISCUSS] Proposing MXNet for the Apache Incubator

[Henri Yandell]

Added :)

On Fri, Jan 13, 2017 at 4:37 PM, sandeep krishnamurthy <
sandeep.krishn...@gmail.com> wrote:

> Hi,
> Please sign me up as a committer of MxNet
>
> Github ID: sandeep-krishnamurthy
> Email: sandeep.krishn...@gmail.com
> Affiliations: AWS
>
> Best,
> Sandeep Krishnamurthy
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: IP Clearance terms

[Henri Yandell]

On Fri, Jan 13, 2017 at 4:46 AM, John D. Ament 
wrote:

>
>
> - Its not usual for a podling to receive a subsequent donation.
>

Doesn't the IP Clearance also cover the initial codebase review? Or is
there a very similar page that's covering that?


> - I hate that the IPMC is responsible for all TLPs IP Clearance.
>

Agreed. The Incubator shouldn't be the general source for instructions on
bringing in a piece of code.

Hen

Re: [DISCUSS] Proposing MXNet for the Apache Incubator

[Henri Yandell]

Thanks for all the feedback and interested parties :)

My aim is to propose a vote on Monday, unless someone raises an issue
before then.

Hen

On Thu, Jan 5, 2017 at 9:12 PM, Henri Yandell <bay...@apache.org> wrote:

> Hello Incubator,
>
> I'd like to propose a new incubator Apache MXNet podling.
>
> The existing MXNet project (http://mxnet.io - 1.5 years old, 15
> committers, 200 contributors) is very interested in joining Apache. MXNet
> is an open-source deep learning framework that allows you to define, train,
> and deploy deep neural networks on a wide array of devices, from cloud
> infrastructure to mobile devices.
>
> The wiki proposal page is located here:
>
>   https://wiki.apache.org/incubator/MXNetProposal
>
> I've included the text below in case anyone wants to focus on parts of it
> in a reply.
>
> Looking forward to your thoughts, and for lots of interested Apache
> members to volunteer to mentor the project in addition to Sebastian and
> myself.
>
> Currently the list of committers is based on the current active coders, so
> we're also very interested in hearing from anyone else who is interested in
> working on the project, be they current or future contributor!
>
> Thanks,
>
> Hen
> On behalf of the MXNet project
>
> -
>
> = MXNet: Apache Incubator Proposal =
>
> == Abstract ==
>
> MXNet is a Flexible and Efficient Library for Deep Learning
>
> == Proposal ==
>
> MXNet is an open-source deep learning framework that allows you to define,
> train, and deploy deep neural networks on a wide array of devices, from
> cloud infrastructure to mobile devices. It is highly scalable, allowing for
> fast model training, and supports a flexible programming model and multiple
> languages. MXNet allows you to mix symbolic and imperative programming
> flavors to maximize both efficiency and productivity. MXNet is built on a
> dynamic dependency scheduler that automatically parallelizes both symbolic
> and imperative operations on the fly. A graph optimization layer on top of
> that makes symbolic execution fast and memory efficient. The MXNet library
> is portable and lightweight, and it scales to multiple GPUs and multiple
> machines.
>
> == Background ==
>
> Deep learning is a subset of Machine learning and refers to a class of
> algorithms that use a hierarchical approach with non-linearities to
> discover and learn representations within data. Deep Learning has recently
> become very popular due to its applicability and advancement of domains
> such as Computer Vision, Speech Recognition, Natural Language Understanding
> and Recommender Systems. With pervasive and cost effective cloud computing,
> large labeled datasets and continued algorithmic innovation, Deep Learning
> has become the one of the most popular classes of algorithms for machine
> learning practitioners in recent years.
>
> == Rational ==
>
> The adoption of deep learning is quickly expanding from initial deep
> domain experts rooted in academia to data scientists and developers working
> to deploy intelligent services and products. Deep learning however has many
> challenges.  These include model training time (which can take days to
> weeks), programmability (not everyone writes Python or C++ and like
> symbolic programming) and balancing production readiness (support for
> things like failover) with development flexibility (ability to program
> different ways, support for new operators and model types) and speed of
> execution (fast and scalable model training).  Other frameworks excel on
> some but not all of these aspects.
>
>
> == Initial Goals ==
>
> MXNet is a fairly established project on GitHub with its first code
> contribution in April 2015 and roughly 200 contributors. It is used by
> several large companies and some of the top research institutions on the
> planet. Initial goals would be the following:
>
>  1. Move the existing codebase(s) to Apache
>  1. Integrate with the Apache development process/sign CLAs
>  1. Ensure all dependencies are compliant with Apache License version 2.0
>  1. Incremental development and releases per Apache guidelines
>  1. Establish engineering discipline and a predictable release cadence of
> high quality releases
>  1. Expand the community beyond the current base of expert level users
>  1. Improve usability and the overall developer/user experience
>  1. Add additional functionality to address newer problem types and
> algorithms
>
>
> == Current Status ==
>
> === Meritocracy ===
>
> The MXNet project already operates on meritocratic principles. Today,
> MXNet has developers worldwide and has accepted multiple major patches from
> a diverse set of contributor

Re: [DISCUSS] Proposing MXNet for the Apache Incubator

[Henri Yandell]

Added :)

On Fri, Jan 13, 2017 at 3:48 AM, Zhang Jian <zhang.jian@gmail.com>
wrote:

> Hi,
> Please sign me up as a committer of MxNet
>
> Github ID: jzhang-zju
> Email: zhang.jian@gmail.com
> Affiliations: Horizon Robotics
>
> Best,
> Jian
>
> On 2017-01-06 13:12 (+0800), Henri Yandell <bay...@apache.org> wrote:
> > Hello Incubator,
> >
> > I'd like to propose a new incubator Apache MXNet podling.
> >
> > The existing MXNet project (http://mxnet.io - 1.5 years old, 15
> committers,
> > 200 contributors) is very interested in joining Apache. MXNet is an
> > open-source deep learning framework that allows you to define, train, and
> > deploy deep neural networks on a wide array of devices, from cloud
> > infrastructure to mobile devices.
> >
> > The wiki proposal page is located here:
> >
> >   https://wiki.apache.org/incubator/MXNetProposal
> >
> > I've included the text below in case anyone wants to focus on parts of it
> > in a reply.
> >
> > Looking forward to your thoughts, and for lots of interested Apache
> members
> > to volunteer to mentor the project in addition to Sebastian and myself.
> >
> > Currently the list of committers is based on the current active coders,
> so
> > we're also very interested in hearing from anyone else who is interested
> in
> > working on the project, be they current or future contributor!
> >
> > Thanks,
> >
> > Hen
> > On behalf of the MXNet project
> >
> > -
> >
> > = MXNet: Apache Incubator Proposal =
> >
> > == Abstract ==
> >
> > MXNet is a Flexible and Efficient Library for Deep Learning
> >
> > == Proposal ==
> >
> > MXNet is an open-source deep learning framework that allows you to
> define,
> > train, and deploy deep neural networks on a wide array of devices, from
> > cloud infrastructure to mobile devices. It is highly scalable, allowing
> for
> > fast model training, and supports a flexible programming model and
> multiple
> > languages. MXNet allows you to mix symbolic and imperative programming
> > flavors to maximize both efficiency and productivity. MXNet is built on a
> > dynamic dependency scheduler that automatically parallelizes both
> symbolic
> > and imperative operations on the fly. A graph optimization layer on top
> of
> > that makes symbolic execution fast and memory efficient. The MXNet
> library
> > is portable and lightweight, and it scales to multiple GPUs and multiple
> > machines.
> >
> > == Background ==
> >
> > Deep learning is a subset of Machine learning and refers to a class of
> > algorithms that use a hierarchical approach with non-linearities to
> > discover and learn representations within data. Deep Learning has
> recently
> > become very popular due to its applicability and advancement of domains
> > such as Computer Vision, Speech Recognition, Natural Language
> Understanding
> > and Recommender Systems. With pervasive and cost effective cloud
> computing,
> > large labeled datasets and continued algorithmic innovation, Deep
> Learning
> > has become the one of the most popular classes of algorithms for machine
> > learning practitioners in recent years.
> >
> > == Rational ==
> >
> > The adoption of deep learning is quickly expanding from initial deep
> domain
> > experts rooted in academia to data scientists and developers working to
> > deploy intelligent services and products. Deep learning however has many
> > challenges.  These include model training time (which can take days to
> > weeks), programmability (not everyone writes Python or C++ and like
> > symbolic programming) and balancing production readiness (support for
> > things like failover) with development flexibility (ability to program
> > different ways, support for new operators and model types) and speed of
> > execution (fast and scalable model training).  Other frameworks excel on
> > some but not all of these aspects.
> >
> >
> > == Initial Goals ==
> >
> > MXNet is a fairly established project on GitHub with its first code
> > contribution in April 2015 and roughly 200 contributors. It is used by
> > several large companies and some of the top research institutions on the
> > planet. Initial goals would be the following:
> >
> >  1. Move the existing codebase(s) to Apache
> >  1. Integrate with the Apache development process/sign CLAs
> >  1. Ensure all dependencies are compliant with Apache License version 2.0
> >  1. Increment

Re: [DISCUSS] Proposing MXNet for the Apache Incubator

[Henri Yandell]

Thanks Yifeng :) Added.

On Fri, Jan 13, 2017 at 3:33 AM, yifeng.geng <yifeng.g...@hobot.cc> wrote:

> Hello,
>
> I committed some code to MXNet and would like to get more involved in the
> project.
> Please sign me up as a committer.
>
> Github ID: gengyifeng
> Email: yifeng.g...@hobot.cc
> Affiliations: horizon robotics
>
> Best,
> Yifeng
>
> On 2017-01-13 00:54 (+0800), Henri Yandell <b...@apache.org> wrote:
> > Added :)>
> >
> > On Thu, Jan 12, 2017 at 1:37 AM, Terry Chen <ja...@gmail.com> wrote:>
> >
> > >>
> > > Hello,>
> > >>
> > > I would like to be committer of MxNet>
> > >>
> > > Github ID:   terrychenism>
> > > Email:  terrychen2...@live.com>
> > > Affiliations:  Novumind>
> > >>
> > >>
> > > Best,>
> > > Terry>
> > >>
> > > ->
> > > 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: HTTPS project sites

[Henri Yandell]

We're not doing SSL-everywhere afaict; so seems that we would want to keep
the HTTP option when in HTTP.

Would love to see Infra providing a 'how many hardcoded http/https' report
for each subdomain :)

Hen

On Fri, Jan 13, 2017 at 5:18 PM, Christopher  wrote:

> In most cases, the project developers should just make sure their
> JavaScript and CSS resources in their page point to an HTTPS version. They
> don't actually need to point to the HTTP location.
>
> On Fri, Jan 13, 2017, 20:06 Martin Gainty  wrote:
>
> >
> >
> > 
> > From: Christopher 
> > Sent: Friday, January 13, 2017 1:17 PM
> > To: general@incubator.apache.org
> > Subject: Re: HTTPS project sites
> >
> > No, I did not. This issue has nothing to do with same origin policy
> (which
> > most users should never try to disable). It's about mixed content.
> > Accessing a site via https can give a false sense of security if the site
> > itself depends on non-https content.
> >
> > In the past, many browsers would just show a mixed-content warning, which
> > most users would probably ignore. Chrome's latest behavior (and I expect
> > other browsers will follow eventually) tries to give a better indicator
> of
> > the degree of security a site has by not loading mixed-content by
> default,
> > and when the mixed-content is loaded, the page is explicitly marked "Not
> > Secure".
> >
> > The end result is that project websites may not be presented to their
> users
> > in the way the developers intended.
> >
> > MG>
> > http://stackoverflow.com/questions/18327314/how-to-
> allow-http-content-within-an-iframe-on-a-https-site
> >
> > MG>he mentions various strategies..twiddling http headers to https,
> > screen-scraping mixed-content to aggregate on secure site and proxies
> > MG> as far as proxies he mentions ngrok and
> > mitmproxy..my personal preference is Squid
> > [
> > https://cdn.sstatic.net/Sites/stackoverflow/img/apple-touch-
> i...@2.png?v=73d79a89bded
> > ]<
> > http://stackoverflow.com/questions/18327314/how-to-
> allow-http-content-within-an-iframe-on-a-https-site
> > >
> >
> > html - How to allow http content within an iframe on a ...<
> > http://stackoverflow.com/questions/18327314/how-to-
> allow-http-content-within-an-iframe-on-a-https-site
> > >
> > stackoverflow.com
> > I load some HTML into an iframe but when a file referenced is using http,
> > not https, I get the following error: [blocked] The page at
> > {current_pagename} ran insecure ...
> >
> >
> >
> > MG>HTH
> > MG>Martin-
> > On Fri, Jan 13, 2017 at 12:54 PM Martin Gainty 
> > wrote:
> >
> > > Hi Christopher
> > >
> > >
> > > did you try disabling default x-domain block for XHR request
> originating
> > > from Chrome?
> > >
> > >
> > >
> > https://joshuamcginnis.com/2011/02/28/how-to-disable-
> same-origin-policy-in-chrome/
> > How to: Disable Same-Origin Policy in Chrome | Josh McGinnis<
> > https://joshuamcginnis.com/2011/02/28/how-to-disable-
> same-origin-policy-in-chrome/
> > >
> > joshuamcginnis.com
> > How to enable cross-domain ajax requests in Chrome for development by
> > disabling the same-origin policy.
> >
> >
> >
> > >
> > >
> > > How to: Disable Same-Origin Policy in Chrome | Josh McGinnis<
> > >
> > https://joshuamcginnis.com/2011/02/28/how-to-disable-
> same-origin-policy-in-chrome/
> > How to: Disable Same-Origin Policy in Chrome | Josh McGinnis<
> > https://joshuamcginnis.com/2011/02/28/how-to-disable-
> same-origin-policy-in-chrome/
> > >
> > joshuamcginnis.com
> > How to enable cross-domain ajax requests in Chrome for development by
> > disabling the same-origin policy.
> >
> >
> >
> > > >
> > > joshuamcginnis.com
> > > How to enable cross-domain ajax requests in Chrome for development by
> > > disabling the same-origin policy.
> > >
> > >
> > > ?
> > >
> > > Martin
> > > __
> > >
> > >
> > >
> > > 
> > > From: Christopher 
> > > Sent: Friday, January 13, 2017 12:34 PM
> > > To: general@incubator.apache.org
> > > Subject: HTTPS project sites
> > >
> > > Hi incubating projects,
> > >
> > > I noticed today that at least one incubating web site won't load
> properly
> > > in the latest version of Chrome with the default settings using HTTPS (
> > > https://htrace.incubator.apache.org/).
> > Apache HTrace – About
> > htrace.incubator.apache.org
> > Apache HTrace is an Apache Incubator project providing an open source
> > framework for distributed tracing. It can be used with both standalone
> > applications and libraries.
> >
> >
> >
> > > Apache HTrace - About
> > Apache HTrace – About
> > htrace.incubator.apache.org
> > Apache HTrace is an Apache Incubator project providing an open source

Re: IP Clearance terms

[Henri Yandell]

On Thu, Jan 12, 2017 at 7:52 AM, William A Rowe Jr 
wrote:

> On Thu, Jan 12, 2017 at 6:06 AM, John D. Ament 
> wrote:
> > IMHO, IP Clearance in of itself is confusing.  For software being
> > relicensed (under an SGA) it shouldn't be needed.
>
> Well, it is needed, even where that devolves to "has all SGA paperwork
> for this incoming contribution and corresponding ICLAs been received
> and acknowledged?"
>
> > In addition, like any other podling coming in, work may be needed
> > to generate a valid release from the donation.  It may not just work.
>
> That is independent of the IP Clearance. It's the same issue as any
> brand new work created here by committers with ICLAs. Nowhere
> does the ASF enforce 'code quality' or similar metrics. If it doesn't
> build, it's open source, so just reassemble all the pieces.
>
>
This may be showing some of the issues with the template; the terms are
confusing and/or incorrect.

For example, looking at it more deeply, the template contains three
sections:

1) Identify the codebase.  Looking at that term, I would think it's a
natural first step that involves identifying which code is going to be
imported into the ASF repository. Instead it's talking about trademarks.
2) Copyright.  As a term that's simple, but too simple given we have no
copyright-only paperwork.
2i). The section then goes on to suggest that rights are transferred to the
ASF (very misleading), and says "It is only necessary to transfer rights
for the package, the core code, and any new code produced by the project.",
which is gobbledegook. The words package, core and new code produced by the
project are all undefined and vague.
2ii) A second section checks that the files have been updated to reflect
the 'new ASF copyright'; which is also inaccurate and misleading.
3) Verify distribution rights.  Sounds interesting.
3i) The first section is to check all active committers have a signed CLA
on record. Fair enough. Perhaps a better fit for section 2; if I had a
belief that section 2 should stay :)
3ii) A reminder about the possibility of CCLAs with average wording (for
example, it doesn't say who may require this). This probably speaks to
inadequate documentation elsewhere (on the CLA page?) and is not something
we should have as an explicit check.
3iii) On to one of the ones that started the thread; a compatibility check
for any non-Apache licensed content within the project.
3iv) And the other; basically the same compatibility check with a
limited/similar but not the same approach.

The paragraph that comes after does a fair, though hand-wavy job, or
summarizing the above:

"Generally, the result of checking off these items will be a Software
Grant, CLA, and Corporate CLA for ASF licensed code, which must have no
dependencies upon items whose licenses that are incompatible with the
Apache License."

Also noting that item 3 in the process says that a software grant is
required (bad name imo to use the word 'grant', we really need to fix
that). Which then talks about 'the traditional License Agreement', which is
very vague, or a CCLA Schedule B, which given we don't require that
committers have CCLAs signed is probably not something we should propose as
an equal.

Basically this line, and therefore the entire page, assumes that an
incubator project is a code donation from a corporation.

---

I was surprised to see nothing here on the process for who to get ICLAs
signed by. Only those becoming committers, or any previous contributors
(and how to determine which contributors). It also should, as a page,
consider whether having the code previously under Apache 2.0, or a category
A license, implies a different process.

I saw you were working on policy cleanup John - could I take a stab at a
rewrite of this, or is it a) got a lot of historical debate I've missed
that I should learn about or b) something you're already working on?

Thanks,

Hen

Re: [DISCUSS] Proposing MXNet for the Apache Incubator

[Henri Yandell]

Thanks :) Updated.

On Thu, Jan 12, 2017 at 10:49 AM, Henry Saputra <henry.sapu...@gmail.com>
wrote:

> Hi Henri,
>
> Could you update the proposal for === Mailing Lists === section to list
> existing and required mailing lists from Incubator?
>
> Thanks,
>
> Henry
>
> On Thu, Jan 5, 2017 at 9:12 PM, Henri Yandell <bay...@apache.org> wrote:
>
> > Hello Incubator,
> >
> > I'd like to propose a new incubator Apache MXNet podling.
> >
> > The existing MXNet project (http://mxnet.io - 1.5 years old, 15
> > committers,
> > 200 contributors) is very interested in joining Apache. MXNet is an
> > open-source deep learning framework that allows you to define, train, and
> > deploy deep neural networks on a wide array of devices, from cloud
> > infrastructure to mobile devices.
> >
> > The wiki proposal page is located here:
> >
> >   https://wiki.apache.org/incubator/MXNetProposal
> >
> > I've included the text below in case anyone wants to focus on parts of it
> > in a reply.
> >
> > Looking forward to your thoughts, and for lots of interested Apache
> members
> > to volunteer to mentor the project in addition to Sebastian and myself.
> >
> > Currently the list of committers is based on the current active coders,
> so
> > we're also very interested in hearing from anyone else who is interested
> in
> > working on the project, be they current or future contributor!
> >
> > Thanks,
> >
> > Hen
> > On behalf of the MXNet project
> >
> > -
> >
> > = MXNet: Apache Incubator Proposal =
> >
> > == Abstract ==
> >
> > MXNet is a Flexible and Efficient Library for Deep Learning
> >
> > == Proposal ==
> >
> > MXNet is an open-source deep learning framework that allows you to
> define,
> > train, and deploy deep neural networks on a wide array of devices, from
> > cloud infrastructure to mobile devices. It is highly scalable, allowing
> for
> > fast model training, and supports a flexible programming model and
> multiple
> > languages. MXNet allows you to mix symbolic and imperative programming
> > flavors to maximize both efficiency and productivity. MXNet is built on a
> > dynamic dependency scheduler that automatically parallelizes both
> symbolic
> > and imperative operations on the fly. A graph optimization layer on top
> of
> > that makes symbolic execution fast and memory efficient. The MXNet
> library
> > is portable and lightweight, and it scales to multiple GPUs and multiple
> > machines.
> >
> > == Background ==
> >
> > Deep learning is a subset of Machine learning and refers to a class of
> > algorithms that use a hierarchical approach with non-linearities to
> > discover and learn representations within data. Deep Learning has
> recently
> > become very popular due to its applicability and advancement of domains
> > such as Computer Vision, Speech Recognition, Natural Language
> Understanding
> > and Recommender Systems. With pervasive and cost effective cloud
> computing,
> > large labeled datasets and continued algorithmic innovation, Deep
> Learning
> > has become the one of the most popular classes of algorithms for machine
> > learning practitioners in recent years.
> >
> > == Rational ==
> >
> > The adoption of deep learning is quickly expanding from initial deep
> domain
> > experts rooted in academia to data scientists and developers working to
> > deploy intelligent services and products. Deep learning however has many
> > challenges.  These include model training time (which can take days to
> > weeks), programmability (not everyone writes Python or C++ and like
> > symbolic programming) and balancing production readiness (support for
> > things like failover) with development flexibility (ability to program
> > different ways, support for new operators and model types) and speed of
> > execution (fast and scalable model training).  Other frameworks excel on
> > some but not all of these aspects.
> >
> >
> > == Initial Goals ==
> >
> > MXNet is a fairly established project on GitHub with its first code
> > contribution in April 2015 and roughly 200 contributors. It is used by
> > several large companies and some of the top research institutions on the
> > planet. Initial goals would be the following:
> >
> >  1. Move the existing codebase(s) to Apache
> >  1. Integrate with the Apache development process/sign CLAs
> >  1. Ensure all dependencies are compliant with Apache License versi

Re: [DISCUSS] Proposing MXNet for the Apache Incubator

[Henri Yandell]

Added :)

On Thu, Jan 12, 2017 at 1:37 AM, Terry Chen  wrote:

>
> Hello,
>
> I would like to be committer of MxNet
>
> Github ID:   terrychenism
> Email:  terrychen2...@live.com
> Affiliations:  Novumind
>
>
> Best,
> Terry
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Proposing MXNet for the Apache Incubator

[Henri Yandell]

Added :)

On Thu, Jan 12, 2017 at 1:43 AM, Tsuyoshi Ozawa <oz...@apache.org> wrote:

> Hi Henri,
>
> My previous comment was just a review comment against the proposal,
> but I forgot to mentioning importance thing.
>
> > Currently the list of committers is based on the current active coders,
> so
> > we're also very interested in hearing from anyone else who is interested
> in
> > working on the project, be they current or future contributor!
>
> I'm also interested in working on MXNet :-)
>
> Thanks,
> - Tsuyoshi
>
> On Thu, Jan 12, 2017 at 3:43 PM, 项亮 <xlvec...@gmail.com> wrote:
> > I would like to volunteer as a committer for MXNet
> >
> > github id: xlvector
> > email: xlvec...@gmail.com
> >
> > Liang Xiang from Toutiao Lab
> >
> > On 2017-01-06 13:12 (+0800), Henri Yandell <bay...@apache.org> wrote:
> >> Hello Incubator,
> >>
> >> I'd like to propose a new incubator Apache MXNet podling.
> >>
> >> The existing MXNet project (http://mxnet.io - 1.5 years old, 15
> committers,
> >> 200 contributors) is very interested in joining Apache. MXNet is an
> >> open-source deep learning framework that allows you to define, train,
> and
> >> deploy deep neural networks on a wide array of devices, from cloud
> >> infrastructure to mobile devices.
> >>
> >> The wiki proposal page is located here:
> >>
> >>   https://wiki.apache.org/incubator/MXNetProposal
> >>
> >> I've included the text below in case anyone wants to focus on parts of
> it
> >> in a reply.
> >>
> >> Looking forward to your thoughts, and for lots of interested Apache
> members
> >> to volunteer to mentor the project in addition to Sebastian and myself.
> >>
> >> Currently the list of committers is based on the current active coders,
> so
> >> we're also very interested in hearing from anyone else who is
> interested in
> >> working on the project, be they current or future contributor!
> >>
> >> Thanks,
> >>
> >> Hen
> >> On behalf of the MXNet project
> >>
> >> -
> >>
> >> = MXNet: Apache Incubator Proposal =
> >>
> >> == Abstract ==
> >>
> >> MXNet is a Flexible and Efficient Library for Deep Learning
> >>
> >> == Proposal ==
> >>
> >> MXNet is an open-source deep learning framework that allows you to
> define,
> >> train, and deploy deep neural networks on a wide array of devices, from
> >> cloud infrastructure to mobile devices. It is highly scalable, allowing
> for
> >> fast model training, and supports a flexible programming model and
> multiple
> >> languages. MXNet allows you to mix symbolic and imperative programming
> >> flavors to maximize both efficiency and productivity. MXNet is built on
> a
> >> dynamic dependency scheduler that automatically parallelizes both
> symbolic
> >> and imperative operations on the fly. A graph optimization layer on top
> of
> >> that makes symbolic execution fast and memory efficient. The MXNet
> library
> >> is portable and lightweight, and it scales to multiple GPUs and multiple
> >> machines.
> >>
> >> == Background ==
> >>
> >> Deep learning is a subset of Machine learning and refers to a class of
> >> algorithms that use a hierarchical approach with non-linearities to
> >> discover and learn representations within data. Deep Learning has
> recently
> >> become very popular due to its applicability and advancement of domains
> >> such as Computer Vision, Speech Recognition, Natural Language
> Understanding
> >> and Recommender Systems. With pervasive and cost effective cloud
> computing,
> >> large labeled datasets and continued algorithmic innovation, Deep
> Learning
> >> has become the one of the most popular classes of algorithms for machine
> >> learning practitioners in recent years.
> >>
> >> == Rational ==
> >>
> >> The adoption of deep learning is quickly expanding from initial deep
> domain
> >> experts rooted in academia to data scientists and developers working to
> >> deploy intelligent services and products. Deep learning however has many
> >> challenges.  These include model training time (which can take days to
> >> weeks), programmability (not everyone writes Python or C++ and like
> >> symbolic programming) and balancing production readiness (support for
> >> thing

Re: [DISCUSS] Proposing MXNet for the Apache Incubator

[Henri Yandell]

Added :)

On Wed, Jan 11, 2017 at 10:43 PM, 项亮 <xlvec...@gmail.com> wrote:

> I would like to volunteer as a committer for MXNet
>
> github id: xlvector
> email: xlvec...@gmail.com
>
> Liang Xiang from Toutiao Lab
>
> On 2017-01-06 13:12 (+0800), Henri Yandell <bay...@apache.org> wrote:
> > Hello Incubator,
> >
> > I'd like to propose a new incubator Apache MXNet podling.
> >
> > The existing MXNet project (http://mxnet.io - 1.5 years old, 15
> committers,
> > 200 contributors) is very interested in joining Apache. MXNet is an
> > open-source deep learning framework that allows you to define, train, and
> > deploy deep neural networks on a wide array of devices, from cloud
> > infrastructure to mobile devices.
> >
> > The wiki proposal page is located here:
> >
> >   https://wiki.apache.org/incubator/MXNetProposal
> >
> > I've included the text below in case anyone wants to focus on parts of it
> > in a reply.
> >
> > Looking forward to your thoughts, and for lots of interested Apache
> members
> > to volunteer to mentor the project in addition to Sebastian and myself.
> >
> > Currently the list of committers is based on the current active coders,
> so
> > we're also very interested in hearing from anyone else who is interested
> in
> > working on the project, be they current or future contributor!
> >
> > Thanks,
> >
> > Hen
> > On behalf of the MXNet project
> >
> > -
> >
> > = MXNet: Apache Incubator Proposal =
> >
> > == Abstract ==
> >
> > MXNet is a Flexible and Efficient Library for Deep Learning
> >
> > == Proposal ==
> >
> > MXNet is an open-source deep learning framework that allows you to
> define,
> > train, and deploy deep neural networks on a wide array of devices, from
> > cloud infrastructure to mobile devices. It is highly scalable, allowing
> for
> > fast model training, and supports a flexible programming model and
> multiple
> > languages. MXNet allows you to mix symbolic and imperative programming
> > flavors to maximize both efficiency and productivity. MXNet is built on a
> > dynamic dependency scheduler that automatically parallelizes both
> symbolic
> > and imperative operations on the fly. A graph optimization layer on top
> of
> > that makes symbolic execution fast and memory efficient. The MXNet
> library
> > is portable and lightweight, and it scales to multiple GPUs and multiple
> > machines.
> >
> > == Background ==
> >
> > Deep learning is a subset of Machine learning and refers to a class of
> > algorithms that use a hierarchical approach with non-linearities to
> > discover and learn representations within data. Deep Learning has
> recently
> > become very popular due to its applicability and advancement of domains
> > such as Computer Vision, Speech Recognition, Natural Language
> Understanding
> > and Recommender Systems. With pervasive and cost effective cloud
> computing,
> > large labeled datasets and continued algorithmic innovation, Deep
> Learning
> > has become the one of the most popular classes of algorithms for machine
> > learning practitioners in recent years.
> >
> > == Rational ==
> >
> > The adoption of deep learning is quickly expanding from initial deep
> domain
> > experts rooted in academia to data scientists and developers working to
> > deploy intelligent services and products. Deep learning however has many
> > challenges.  These include model training time (which can take days to
> > weeks), programmability (not everyone writes Python or C++ and like
> > symbolic programming) and balancing production readiness (support for
> > things like failover) with development flexibility (ability to program
> > different ways, support for new operators and model types) and speed of
> > execution (fast and scalable model training).  Other frameworks excel on
> > some but not all of these aspects.
> >
> >
> > == Initial Goals ==
> >
> > MXNet is a fairly established project on GitHub with its first code
> > contribution in April 2015 and roughly 200 contributors. It is used by
> > several large companies and some of the top research institutions on the
> > planet. Initial goals would be the following:
> >
> >  1. Move the existing codebase(s) to Apache
> >  1. Integrate with the Apache development process/sign CLAs
> >  1. Ensure all dependencies are compliant with Apache License version 2.0
> >  1. Incremental development and releases per Apache gu

Re: [DISCUSS] Proposing MXNet for the Apache Incubator

[Henri Yandell]

Added :)

On Wed, Jan 11, 2017 at 10:57 PM, Zihao Zheng <zihaolu...@gmail.com> wrote:

> Hi, could you please add me to this group? I’ve been working on a
> visualization component(tensorboard <https://github.com/dmlc/tensorboard>)
> for MXNet for a while with Eric Junyuan Xie, and would like to contribute
> more on this direction.
>
> GitHub ID: zihaolucky
> Email: zihaolu...@gmail.com <mailto:zihaolu...@gmail.com>
> Company: Alibaba Group
>
> Thank you!
>
>
> On 2017-01-06 13:12 (+0800), Henri Yandell <bay...@apache.org> wrote:
> > Hello Incubator,
> >
> > I'd like to propose a new incubator Apache MXNet podling.
> >
> > The existing MXNet project (http://mxnet.io - 1.5 years old, 15
> committers,
> > 200 contributors) is very interested in joining Apache. MXNet is an
> > open-source deep learning framework that allows you to define, train, and
> > deploy deep neural networks on a wide array of devices, from cloud
> > infrastructure to mobile devices.
> >
> > The wiki proposal page is located here:
> >
> >   https://wiki.apache.org/incubator/MXNetProposal
> >
> > I've included the text below in case anyone wants to focus on parts of it
> > in a reply.
> >
> > Looking forward to your thoughts, and for lots of interested Apache
> members
> > to volunteer to mentor the project in addition to Sebastian and myself.
> >
> > Currently the list of committers is based on the current active coders,
> so
> > we're also very interested in hearing from anyone else who is interested
> in
> > working on the project, be they current or future contributor!
> >
> > Thanks,
> >
> > Hen
> > On behalf of the MXNet project
> >
> > -
> >
> > = MXNet: Apache Incubator Proposal =
> >
> > == Abstract ==
> >
> > MXNet is a Flexible and Efficient Library for Deep Learning
> >
> > == Proposal ==
> >
> > MXNet is an open-source deep learning framework that allows you to
> define,
> > train, and deploy deep neural networks on a wide array of devices, from
> > cloud infrastructure to mobile devices. It is highly scalable, allowing
> for
> > fast model training, and supports a flexible programming model and
> multiple
> > languages. MXNet allows you to mix symbolic and imperative programming
> > flavors to maximize both efficiency and productivity. MXNet is built on a
> > dynamic dependency scheduler that automatically parallelizes both
> symbolic
> > and imperative operations on the fly. A graph optimization layer on top
> of
> > that makes symbolic execution fast and memory efficient. The MXNet
> library
> > is portable and lightweight, and it scales to multiple GPUs and multiple
> > machines.
> >
> > == Background ==
> >
> > Deep learning is a subset of Machine learning and refers to a class of
> > algorithms that use a hierarchical approach with non-linearities to
> > discover and learn representations within data. Deep Learning has
> recently
> > become very popular due to its applicability and advancement of domains
> > such as Computer Vision, Speech Recognition, Natural Language
> Understanding
> > and Recommender Systems. With pervasive and cost effective cloud
> computing,
> > large labeled datasets and continued algorithmic innovation, Deep
> Learning
> > has become the one of the most popular classes of algorithms for machine
> > learning practitioners in recent years.
> >
> > == Rational ==
> >
> > The adoption of deep learning is quickly expanding from initial deep
> domain
> > experts rooted in academia to data scientists and developers working to
> > deploy intelligent services and products. Deep learning however has many
> > challenges.  These include model training time (which can take days to
> > weeks), programmability (not everyone writes Python or C++ and like
> > symbolic programming) and balancing production readiness (support for
> > things like failover) with development flexibility (ability to program
> > different ways, support for new operators and model types) and speed of
> > execution (fast and scalable model training).  Other frameworks excel on
> > some but not all of these aspects.
> >
> >
> > == Initial Goals ==
> >
> > MXNet is a fairly established project on GitHub with its first code
> > contribution in April 2015 and roughly 200 contributors. It is used by
> > several large companies and some of the top research institutions on the
> > planet. Initial goals would be the following:
> >
&

Re: [DISCUSS] Proposing MXNet for the Apache Incubator

[Henri Yandell]

Thanks Ziheng :)

I've added you to the page.

Hen

On Wed, Jan 11, 2017 at 9:35 PM, ziheng  wrote:

> Hello
>
> Please sign me up as a committer for MXNet - I've been working on MXNet
> Profiler and NNVM-Fusion, also will work with Mu as an intern at Amazon AWS
> team in the next months, and I would love to get more involved in the
> project.
>
> GitHub ID:ZihengJiang
> Affiliations: AWS
>
>
> Thanks
>
>
>
> --
> View this message in context: http://apache-incubator-
> general.996316.n3.nabble.com/DISCUSS-Proposing-MXNet-for-
> the-Apache-Incubator-tp53250p53335.html
> Sent from the Apache Incubator - General mailing list archive at
> Nabble.com.
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

IP Clearance terms

[Henri Yandell]

It was pointed out on legal-discuss@ that the IP Clearance terms in
http://incubator.apache.org/ip-clearance/ip-clearance-template.html are
odd. Namely the two items:

---
* Check and make sure that for all items included with the distribution
that is not under the Apache license, we have the right to combine with
Apache-licensed code and redistribute.

* Check and make sure that all items depended upon by the project is
covered by one or more of the following approved licenses: Apache, BSD,
Artistic, MIT/X, MIT/W3C, MPL 1.1, or something with essentially the same
terms.


It's odd to call out the licenses specifically (with MPL 1.1 seeming a
little odd-one-out), and the two lines are (in spirit) saying the same
thing.

What do folk think to replacing both with:

 * Check and make sure that all items depended upon by the project are
compatible with the license guidance given here:
http://www.apache.org/legal/resolved.html

Thanks,

Hen

Re: Committer for MXNet.

[Henri Yandell]

Added (after confirming offline with Chris that his affiliation is AWS).

On Fri, Jan 6, 2017 at 10:59 AM, Chris Olivier 
wrote:

> I would like to volunteer as a committer for MXNet.
>
> -Chris Olivier
> cjolivie...@gmail.com
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Committer for MXNet.

[Henri Yandell]

Thanks :)

https://www.linkedin.com/in/chris-olivier-81953223 I presume?

Part of the proposal is to identify folks' affiliations so any dependence
on a single paying employer is clear.

On Fri, Jan 6, 2017 at 10:59 AM, Chris Olivier 
wrote:

> I would like to volunteer as a committer for MXNet.
>
> -Chris Olivier
> cjolivie...@gmail.com
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Proposing MXNet for the Apache Incubator

[Henri Yandell]

Added :)

On Fri, Jan 6, 2017 at 1:11 PM, Indhu Bharathi <indhubhara...@gmail.com>
wrote:

> Please sign me up as a committer - I've been working with Mu at work on
> MXNet (Amazon) and would love to get more involved in the project.
> GitHub ID:  indhub
>
> Thanks,
> Indu
>
> On 2017-01-05 21:12 (-0800), Henri Yandell <bay...@apache.org> wrote:
> > Hello Incubator,
> >
> > I'd like to propose a new incubator Apache MXNet podling.
> >
> > The existing MXNet project (http://mxnet.io - 1.5 years old, 15
> committers,
> > 200 contributors) is very interested in joining Apache. MXNet is an
> > open-source deep learning framework that allows you to define, train, and
> > deploy deep neural networks on a wide array of devices, from cloud
> > infrastructure to mobile devices.
> >
> > The wiki proposal page is located here:
> >
> >   https://wiki.apache.org/incubator/MXNetProposal
> >
> > I've included the text below in case anyone wants to focus on parts of it
> > in a reply.
> >
> > Looking forward to your thoughts, and for lots of interested Apache
> members
> > to volunteer to mentor the project in addition to Sebastian and myself.
> >
> > Currently the list of committers is based on the current active coders,
> so
> > we're also very interested in hearing from anyone else who is interested
> in
> > working on the project, be they current or future contributor!
> >
> > Thanks,
> >
> > Hen
> > On behalf of the MXNet project
> >
> > -
> >
> > = MXNet: Apache Incubator Proposal =
> >
> > == Abstract ==
> >
> > MXNet is a Flexible and Efficient Library for Deep Learning
> >
> > == Proposal ==
> >
> > MXNet is an open-source deep learning framework that allows you to
> define,
> > train, and deploy deep neural networks on a wide array of devices, from
> > cloud infrastructure to mobile devices. It is highly scalable, allowing
> for
> > fast model training, and supports a flexible programming model and
> multiple
> > languages. MXNet allows you to mix symbolic and imperative programming
> > flavors to maximize both efficiency and productivity. MXNet is built on a
> > dynamic dependency scheduler that automatically parallelizes both
> symbolic
> > and imperative operations on the fly. A graph optimization layer on top
> of
> > that makes symbolic execution fast and memory efficient. The MXNet
> library
> > is portable and lightweight, and it scales to multiple GPUs and multiple
> > machines.
> >
> > == Background ==
> >
> > Deep learning is a subset of Machine learning and refers to a class of
> > algorithms that use a hierarchical approach with non-linearities to
> > discover and learn representations within data. Deep Learning has
> recently
> > become very popular due to its applicability and advancement of domains
> > such as Computer Vision, Speech Recognition, Natural Language
> Understanding
> > and Recommender Systems. With pervasive and cost effective cloud
> computing,
> > large labeled datasets and continued algorithmic innovation, Deep
> Learning
> > has become the one of the most popular classes of algorithms for machine
> > learning practitioners in recent years.
> >
> > == Rational ==
> >
> > The adoption of deep learning is quickly expanding from initial deep
> domain
> > experts rooted in academia to data scientists and developers working to
> > deploy intelligent services and products. Deep learning however has many
> > challenges.  These include model training time (which can take days to
> > weeks), programmability (not everyone writes Python or C++ and like
> > symbolic programming) and balancing production readiness (support for
> > things like failover) with development flexibility (ability to program
> > different ways, support for new operators and model types) and speed of
> > execution (fast and scalable model training).  Other frameworks excel on
> > some but not all of these aspects.
> >
> >
> > == Initial Goals ==
> >
> > MXNet is a fairly established project on GitHub with its first code
> > contribution in April 2015 and roughly 200 contributors. It is used by
> > several large companies and some of the top research institutions on the
> > planet. Initial goals would be the following:
> >
> >  1. Move the existing codebase(s) to Apache
> >  1. Integrate with the Apache development process/sign CLAs
> >  1. Ensure all dependencies are compliant with Apache License version 2.0
> 

Re: [DISCUSS] Proposing MXNet for the Apache Incubator

[Henri Yandell]

Added :)

On Fri, Jan 6, 2017 at 10:59 AM, Naveen Swamy <mnnav...@gmail.com> wrote:

> Hello
>
> Please sign me up as a committer for MXNet - I've been working with Mu at
> work on MXNet (Amazon) and would love to get more involved in the project.
>
> *GitHub ID: nswamy*
>
>
> Thanks, Naveen
>
>
>
> On 2017-01-05 21:12 (-0800), Henri Yandell <b...@apache.org> wrote:
>
> > Hello Incubator,>
>
> >
>
> > I'd like to propose a new incubator Apache MXNet podling.>
>
> >
>
> > The existing MXNet project (http://mxnet.io - 1.5 years old, 15
> committers,>
>
> > 200 contributors) is very interested in joining Apache. MXNet is an>
>
> > open-source deep learning framework that allows you to define, train,
> and>
>
> > deploy deep neural networks on a wide array of devices, from cloud>
>
> > infrastructure to mobile devices.>
>
> >
>
> > The wiki proposal page is located here:>
>
> >
>
> >   https://wiki.apache.org/incubator/MXNetProposal>
>
> >
>
> > I've included the text below in case anyone wants to focus on parts of
> it>
>
> > in a reply.>
>
> >
>
> > Looking forward to your thoughts, and for lots of interested Apache
> members>
>
> > to volunteer to mentor the project in addition to Sebastian and myself.>
>
> >
>
> > Currently the list of committers is based on the current active coders,
> so>
>
> > we're also very interested in hearing from anyone else who is interested
> in>
>
> > working on the project, be they current or future contributor!>
>
> >
>
> > Thanks,>
>
> >
>
> > Hen>
>
> > On behalf of the MXNet project>
>
> >
>
> > ->
>
> >
>
> > = MXNet: Apache Incubator Proposal =>
>
> >
>
> > == Abstract ==>
>
> >
>
> > MXNet is a Flexible and Efficient Library for Deep Learning>
>
> >
>
> > == Proposal ==>
>
> >
>
> > MXNet is an open-source deep learning framework that allows you to
> define,>
>
> > train, and deploy deep neural networks on a wide array of devices, from>
>
> > cloud infrastructure to mobile devices. It is highly scalable, allowing
> for>
>
> > fast model training, and supports a flexible programming model and
> multiple>
>
> > languages. MXNet allows you to mix symbolic and imperative programming>
>
> > flavors to maximize both efficiency and productivity. MXNet is built on
> a>
>
> > dynamic dependency scheduler that automatically parallelizes both
> symbolic>
>
> > and imperative operations on the fly. A graph optimization layer on top
> of>
>
> > that makes symbolic execution fast and memory efficient. The MXNet
> library>
>
> > is portable and lightweight, and it scales to multiple GPUs and multiple>
>
> > machines.>
>
> >
>
> > == Background ==>
>
> >
>
> > Deep learning is a subset of Machine learning and refers to a class of>
>
> > algorithms that use a hierarchical approach with non-linearities to>
>
> > discover and learn representations within data. Deep Learning has
> recently>
>
> > become very popular due to its applicability and advancement of domains>
>
> > such as Computer Vision, Speech Recognition, Natural Language
> Understanding>
>
> > and Recommender Systems. With pervasive and cost effective cloud
> computing,>
>
> > large labeled datasets and continued algorithmic innovation, Deep
> Learning>
>
> > has become the one of the most popular classes of algorithms for machine>
>
> > learning practitioners in recent years.>
>
> >
>
> > == Rational ==>
>
> >
>
> > The adoption of deep learning is quickly expanding from initial deep
> domain>
>
> > experts rooted in academia to data scientists and developers working to>
>
> > deploy intelligent services and products. Deep learning however has many>
>
> > challenges.  These include model training time (which can take days to>
>
> > weeks), programmability (not everyone writes Python or C++ and like>
>
> > symbolic programming) and balancing production readiness (support for>
>
> > things like failover) with development flexibility (ability to program>
>
> > different ways, support for new operators and model types) and speed of>
>
> > execution (fast and scalable model training).  Other frameworks e

Re: [DISCUSS] Proposing MXNet for the Apache Incubator

[Henri Yandell]

Thanks Joe - I've added you to the commiter list :)

On Fri, Jan 6, 2017 at 12:31 PM, Joe Spisak  wrote:

> Awesome!  Please sign me up as a committer - I've been working with Mu on
> MXNet (Amazon) and would love to get more involved with project!
>
> GitHub ID: jspisak
>
>
>
> Sent from Joe's iPhone
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Proposing MXNet for the Apache Incubator

[Henri Yandell]

Thanks Markus - I've added you to the proposal :)

On Fri, Jan 6, 2017 at 9:20 AM, Markus Weimer <mar...@weimo.de> wrote:

> On 2017-01-05 9:12 PM, Henri Yandell wrote:
>
>> I'd like to propose a new incubator Apache MXNet podling.
>>
>
> Awesome! If you still need a mentor, feel free to sign me up!
>
> Markus
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Proposing MXNet for the Apache Incubator

[Henri Yandell]

Understood. I saw that Greg had recently approved another podling to do
this. Though, assuming approved, there will still need to be some infra
headscratching on the 3,000 issues currently on the main dmlc/mxnet repo
and how imports are best done :) The simplest would be to transfer the
current repo as is over at GitHub - not sure if that's been done before.

On Thu, Jan 5, 2017 at 11:32 PM, Henry Saputra <henry.sapu...@gmail.com>
wrote:

> This is great news and I am looking forward to it =)
>
> According to proposal, the community want to stick with Github issues for
> tracking issues and bugs?
> I suppose this needs a nod by Greg Stein as rep from Apache Infra to
> confirm that this is ok for incubation and how would it impact during
> graduation.
>
> - Henry
>
> On Thu, Jan 5, 2017 at 9:12 PM, Henri Yandell <bay...@apache.org> wrote:
>
> > Hello Incubator,
> >
> > I'd like to propose a new incubator Apache MXNet podling.
> >
> > The existing MXNet project (http://mxnet.io - 1.5 years old, 15
> > committers,
> > 200 contributors) is very interested in joining Apache. MXNet is an
> > open-source deep learning framework that allows you to define, train, and
> > deploy deep neural networks on a wide array of devices, from cloud
> > infrastructure to mobile devices.
> >
> > The wiki proposal page is located here:
> >
> >   https://wiki.apache.org/incubator/MXNetProposal
> >
> > I've included the text below in case anyone wants to focus on parts of it
> > in a reply.
> >
> > Looking forward to your thoughts, and for lots of interested Apache
> members
> > to volunteer to mentor the project in addition to Sebastian and myself.
> >
> > Currently the list of committers is based on the current active coders,
> so
> > we're also very interested in hearing from anyone else who is interested
> in
> > working on the project, be they current or future contributor!
> >
> > Thanks,
> >
> > Hen
> > On behalf of the MXNet project
> >
> > -
> >
> > = MXNet: Apache Incubator Proposal =
> >
> > == Abstract ==
> >
> > MXNet is a Flexible and Efficient Library for Deep Learning
> >
> > == Proposal ==
> >
> > MXNet is an open-source deep learning framework that allows you to
> define,
> > train, and deploy deep neural networks on a wide array of devices, from
> > cloud infrastructure to mobile devices. It is highly scalable, allowing
> for
> > fast model training, and supports a flexible programming model and
> multiple
> > languages. MXNet allows you to mix symbolic and imperative programming
> > flavors to maximize both efficiency and productivity. MXNet is built on a
> > dynamic dependency scheduler that automatically parallelizes both
> symbolic
> > and imperative operations on the fly. A graph optimization layer on top
> of
> > that makes symbolic execution fast and memory efficient. The MXNet
> library
> > is portable and lightweight, and it scales to multiple GPUs and multiple
> > machines.
> >
> > == Background ==
> >
> > Deep learning is a subset of Machine learning and refers to a class of
> > algorithms that use a hierarchical approach with non-linearities to
> > discover and learn representations within data. Deep Learning has
> recently
> > become very popular due to its applicability and advancement of domains
> > such as Computer Vision, Speech Recognition, Natural Language
> Understanding
> > and Recommender Systems. With pervasive and cost effective cloud
> computing,
> > large labeled datasets and continued algorithmic innovation, Deep
> Learning
> > has become the one of the most popular classes of algorithms for machine
> > learning practitioners in recent years.
> >
> > == Rational ==
> >
> > The adoption of deep learning is quickly expanding from initial deep
> domain
> > experts rooted in academia to data scientists and developers working to
> > deploy intelligent services and products. Deep learning however has many
> > challenges.  These include model training time (which can take days to
> > weeks), programmability (not everyone writes Python or C++ and like
> > symbolic programming) and balancing production readiness (support for
> > things like failover) with development flexibility (ability to program
> > different ways, support for new operators and model types) and speed of
> > execution (fast and scalable model training).  Other frameworks excel on
> > some but not all of these aspects.
> >
> >
> > == Initial Goals ==
> >
> 

Re: [DISCUSS] Proposing MXNet for the Apache Incubator

[Henri Yandell]

On Fri, Jan 6, 2017 at 3:52 AM, John D. Ament <johndam...@apache.org> wrote:

> There seem to be some discrepancies in the proposal vs what they currently
> have.  That and some comments in line.
>
> On Fri, Jan 6, 2017 at 12:12 AM Henri Yandell <bay...@apache.org> wrote:
>
> > Hello Incubator,
> >
> > I'd like to propose a new incubator Apache MXNet podling.
> >
> > The existing MXNet project (http://mxnet.io - 1.5 years old, 15
> > committers,
> > 200 contributors) is very interested in joining Apache. MXNet is an
> > open-source deep learning framework that allows you to define, train, and
> > deploy deep neural networks on a wide array of devices, from cloud
> > infrastructure to mobile devices.
> >
>
> This seems to be a broad gap between committers and contributors.  Of the
> remaining 220 not included as committer, are they being considered?
>

Mu's contacting (and has been contacting) contributors to invite them; for
the proposal I went with the notion of the current active folk with write
access and having others introduce themselves. I suspect some are already
awaiting general@ moderators to pass their email through :)

>
> > The wiki proposal page is located here:
> >
> >   https://wiki.apache.org/incubator/MXNetProposal
> >
> >
> I've added it to the project proposals page.
>
>
*doh* Thank you :)


>
> > I've included the text below in case anyone wants to focus on parts of it
> > in a reply.
> >
> > Looking forward to your thoughts, and for lots of interested Apache
> members
> > to volunteer to mentor the project in addition to Sebastian and myself.
> >
> > Currently the list of committers is based on the current active coders,
> so
> > we're also very interested in hearing from anyone else who is interested
> in
> > working on the project, be they current or future contributor!
> >
> > Thanks,
> >
> > Hen
> > On behalf of the MXNet project
> >
> > -
> >
> > = MXNet: Apache Incubator Proposal =
> >
>
>



> >
> > === Core Developers ===
> >
> > (with GitHub logins)
> >
> >  * Tianqi Chen (@tqchen)
> >  * Mu Li (@mli)
> >  * Junyuan Xie (@piiswrong)
> >  * Bing Xu (@antinucleon)
> >  * Chiyuan Zhang (@pluskid)
> >  * Minjie Wang (@jermainewang)
> >  * Naiyan Wang (@winstywang)
> >  * Yizhi Liu (@javelinjs)
> >  * Tong He (@hetong007)
> >  * Qiang Kou (@thirdwing)
> >  * Xingjian Shi (@sxjscience)
> >
> >
> AFAIK, we still expect email addresses, not github accounts.
>
>
The GitHubs were just as an FYI :)


>
> >
> > == Initial Source ==
> >
> > We currently use Github to maintain our source code,
> > https://github.com/MXNet
>
>
> This doesn't look right.  This github organization has a single repo that
> contains a mobile app that appears to been 4 years old.  The website points
> to https://github.com/dmlc/mxnet which looks more correct.  Which is it?
> I'll also note that if it is the latter, there are git submodules in the
> codebase.  Please include references to those modules as well.  Please also
> include the website source code, if available.
>

*DOH* thank you :)

There will be more than dmlc/mxnet as some of the other dmlc repos relate
to mxnet too.


>
> I'll point out that since the github name is taken, it may be cause to say
> that MXNet isn't a viable name.  But that can be worked out later.
>

Yup. I did a preliminary name search of the various TESSA type places and
didn't see any blocking concerns.


>
> >
> > == External Dependencies ==
> >
> >  * required by the core code base: GCC or CLOM, Clang, any BLAS library
> > (ATLAS, OpenBLAS, MKL), dmlc-core, mshadow, ps-lite (which requires
> > lib-zeromq), TBB
> >  * required for GPU usage: cudnn, cuda
> >  * required for python usage: Python 2/3
> >  * required for R module: R, Rcpp (GPLv2 licensing)
> >  * optional for image preparation and preprocessing: opencv
> >  * optional dependencies for additional features: torch7, numba, cython
> (in
> > NNVM branch)
> >
>
> Before we go any further, I think we need to address the incompatible
> licenses.  Knowing that R is a core component of MXNet, how will you
> replace it?
>

I don't expect R itself to be an issue. Rcpp I expect to be an issue and
there are options here - either hosting the R module separately or
switching to using Rcpp11 (MIT license).

ZeroMQ is perhaps a larger issue given it's a transitive dependency of the
core codebase. That community has a licensing exception in addition to its
LGPL whi

Re: [DISCUSS] Proposing MXNet for the Apache Incubator

[Henri Yandell]

Brilliant - thank you Suneel :)

I see you're on the Incubator PMC and have added you to the wiki page.

On Thu, Jan 5, 2017 at 9:25 PM, Suneel Marthi <smar...@apache.org> wrote:

> I would like to sign up as mentor for MxNet.
>
> On Fri, Jan 6, 2017 at 12:12 AM, Henri Yandell <bay...@apache.org> wrote:
>
> > Hello Incubator,
> >
> > I'd like to propose a new incubator Apache MXNet podling.
> >
> > The existing MXNet project (http://mxnet.io - 1.5 years old, 15
> > committers,
> > 200 contributors) is very interested in joining Apache. MXNet is an
> > open-source deep learning framework that allows you to define, train, and
> > deploy deep neural networks on a wide array of devices, from cloud
> > infrastructure to mobile devices.
> >
> > The wiki proposal page is located here:
> >
> >   https://wiki.apache.org/incubator/MXNetProposal
> >
> > I've included the text below in case anyone wants to focus on parts of it
> > in a reply.
> >
> > Looking forward to your thoughts, and for lots of interested Apache
> members
> > to volunteer to mentor the project in addition to Sebastian and myself.
> >
> > Currently the list of committers is based on the current active coders,
> so
> > we're also very interested in hearing from anyone else who is interested
> in
> > working on the project, be they current or future contributor!
> >
> > Thanks,
> >
> > Hen
> > On behalf of the MXNet project
> >
> > -
> >
> > = MXNet: Apache Incubator Proposal =
> >
> > == Abstract ==
> >
> > MXNet is a Flexible and Efficient Library for Deep Learning
> >
> > == Proposal ==
> >
> > MXNet is an open-source deep learning framework that allows you to
> define,
> > train, and deploy deep neural networks on a wide array of devices, from
> > cloud infrastructure to mobile devices. It is highly scalable, allowing
> for
> > fast model training, and supports a flexible programming model and
> multiple
> > languages. MXNet allows you to mix symbolic and imperative programming
> > flavors to maximize both efficiency and productivity. MXNet is built on a
> > dynamic dependency scheduler that automatically parallelizes both
> symbolic
> > and imperative operations on the fly. A graph optimization layer on top
> of
> > that makes symbolic execution fast and memory efficient. The MXNet
> library
> > is portable and lightweight, and it scales to multiple GPUs and multiple
> > machines.
> >
> > == Background ==
> >
> > Deep learning is a subset of Machine learning and refers to a class of
> > algorithms that use a hierarchical approach with non-linearities to
> > discover and learn representations within data. Deep Learning has
> recently
> > become very popular due to its applicability and advancement of domains
> > such as Computer Vision, Speech Recognition, Natural Language
> Understanding
> > and Recommender Systems. With pervasive and cost effective cloud
> computing,
> > large labeled datasets and continued algorithmic innovation, Deep
> Learning
> > has become the one of the most popular classes of algorithms for machine
> > learning practitioners in recent years.
> >
> > == Rational ==
> >
> > The adoption of deep learning is quickly expanding from initial deep
> domain
> > experts rooted in academia to data scientists and developers working to
> > deploy intelligent services and products. Deep learning however has many
> > challenges.  These include model training time (which can take days to
> > weeks), programmability (not everyone writes Python or C++ and like
> > symbolic programming) and balancing production readiness (support for
> > things like failover) with development flexibility (ability to program
> > different ways, support for new operators and model types) and speed of
> > execution (fast and scalable model training).  Other frameworks excel on
> > some but not all of these aspects.
> >
> >
> > == Initial Goals ==
> >
> > MXNet is a fairly established project on GitHub with its first code
> > contribution in April 2015 and roughly 200 contributors. It is used by
> > several large companies and some of the top research institutions on the
> > planet. Initial goals would be the following:
> >
> >  1. Move the existing codebase(s) to Apache
> >  1. Integrate with the Apache development process/sign CLAs
> >  1. Ensure all dependencies are compliant with Apache License version 2.0
> >  1. Incremental development and rel

[DISCUSS] Proposing MXNet for the Apache Incubator

[Henri Yandell]

 parallelism and
data parallelism) which makes MXNet much more efficient (near-linear
speedup on state of the art models). MXNet also supports both imperative
and symbolic approaches providing ease of programming for deep learning
algorithms.

Other Apache projects that are potentially complimentary:

Apache Arrow - read data in Apache Arrow‘s internal format from MXNet, that
would allow users to run ETL/preprocessing in Spark, save the results in
Arrow’s format and then run DL algorithms on it.

Apache Singa - MXNet and Singa are both deep learning projects, and can
benefit from a larger deep learning community at Apache.

== Documentation ==

Documentation has recently migrated to http://mxnet.io.  We continue to
refine and improve the documentation.

== Initial Source ==

We currently use Github to maintain our source code,
https://github.com/MXNet

== Source and Intellectual Property Submission Plan ==

MXNet Code is available under Apache License, Version 2.0. We will work
with the committers to get CLAs signed and review previous contributions.

== External Dependencies ==

 * required by the core code base: GCC or CLOM, Clang, any BLAS library
(ATLAS, OpenBLAS, MKL), dmlc-core, mshadow, ps-lite (which requires
lib-zeromq), TBB
 * required for GPU usage: cudnn, cuda
 * required for python usage: Python 2/3
 * required for R module: R, Rcpp (GPLv2 licensing)
 * optional for image preparation and preprocessing: opencv
 * optional dependencies for additional features: torch7, numba, cython (in
NNVM branch)

Rcpt and lib-zeromq are expected to be licensing discussions.

== Cryptography ==

Not Applicable

== Required Resources ==

=== Mailing Lists ===

There is currently no mailing list.

=== Issue Tracking ===

Currently uses GitHub to track issues. Would like to continue to do so.

== Committers and Affiliations ==

 * Tianqi Chen (UW)
 * Mu Li (AWS)
 * Junyuan Xie (AWS)
 * Bing Xu (Apple)
 * Chiyuan Zhang (MIT)
 * Minjie Wang (UYU)
 * Naiyan Wang (Tusimple)
 * Yizhi Liu (Mediav)
 * Tong He (Simon Fraser University)
 * Qiang Kou (Indiana U)
 * Xingjian Shi (HKUST)

== Sponsors ==

=== Champion ===

Henri Yandell (bayard at apache.org)

=== Nominated Mentors ===

Sebastian Schelter (s...@apache.org)


=== Sponsoring Entity ===

We are requesting the Incubator to sponsor this project.

Re: Policy should be simple (was "Allowed Champions on podlings")

[Henri Yandell]

On Tue, Mar 22, 2016 at 9:19 AM, Marvin Humphrey 
wrote:

>
> Right now, Apache's rules are so complex that we are all in perpetual
> violation.  You can't even know what all the rules are!
>


First, your podling was not part of our charter nor our licensing agreement
so I must do nothing. And secondly, you must be a committer for the
committer's code to apply and you're not. And thirdly, the code is more
what you'd call "guidelines" than actual rules. Welcome aboard the
Foundation, Mr Humphrey.

I might have got the quote a little wrong :)

Hen

Re: Advice on binary NOTICE

[Henri Yandell]

On Sun, Mar 20, 2016 at 12:28 PM, Marvin Humphrey <mar...@rectangular.com>
wrote:

> On Sun, Mar 20, 2016 at 11:24 AM, Henri Yandell <bay...@apache.org> wrote:
> > I suspect 'relevant' means those parts of a NOTICE relating to the parts
> of
> > the product you use.
>
> Yes, that was the intent.  That sentence references section 4d of the ALv2,
> specifically this phrase:
>
>excluding those notices that do not pertain to any part of the
>Derivative Works,
>
> > I suspect 'relevant' needs clarification in the docs.
>
> Over time, I have come to think our approach to NOTICE should be more
> formulaic.  The expectation that our PMCs will edit dependency NOTICE
> content
> is too burdensome.
>
> It is quite challenging to analyze which parts of a NOTICE file may be
> omitted
> -- especially when you take into account the vagaries of subsuming the
> notice
> requirements of licenses besides the ALv2.  Only a handful of our PMCs
> possess
> sufficient collective expertise in open source licensing to perform such
> license analysis accurately.
>
> Yet, our goal should be for *every* Apache release to conform to both legal
> requirements and policy.  We can't change our legal obligations -- but we
> can
> and should craft policy and best-practice recommendations so that the
> process
> of assembling LICENSE and NOTICE is not so taxing and yields consistently
> correct results.
>
> The proposal from last month to cease NOTICE aggregation entirely[1]
> failed to
> achieve consensus.  The next-best alternative, it seems to me, is a
> completely
> mechanical approach to aggregation: verbatim copying of NOTICE comment from
> dependency NOTICE files to the top-level NOTICE file.  This has two
> significant advantages:
>
> *   The PMC is spared from performing analysis of dependency NOTICE
> content.
> *   Verbatim aggregation can be achieved programmatically, allowing for
> automated solutions.
>
> In the case of a NOTICE file from a non-ASF ALv2 product, verbatim
> propagation
> is a completely defensible choice.  But I think we should consider
> recommending it for all ALv2 dependencies, including ASF products.
>

+1. License compliance is best when it's simple, and errs on being
over-informative.

I think defining the structure of the files would be valuable. A standard
delimiter ( etc) between different sections and a 'header' to a
section; ie) "Contents of Jackson 1.3 NOTICE file".

Hen

Re: Update on Apache Toree and LGPL dependency

[Henri Yandell]

Brilliant :)

On Thursday, March 17, 2016, Chip Senkbeil <chip.senkb...@gmail.com> wrote:

> Just wanted to give a status update with this one. JeroMQ is down to just
> four contributors that have not responded. The current, active committers
> for JeroMQ have reverted the commits for one of the contributors here:
>
> https://github.com/zeromq/jeromq/pull/333
>
> So, progress is still being made on this one!
>
> > +1
> >
> > > On Mar 6, 2016, at 6:58 PM, Gino Bustelo <lbust...@gmail.com
> <javascript:;>> wrote:
> > >
> > > @john The 0mq ecosystem is made up of many projects of different sizes
> and maturity.
> > In the case of JeroMQ, the committers are showing an overwhelming
> momentum to transition to
> > MPL. I don't see any reason for us to consider any other alternative at
> this juncture.
> > >
> > > Gino B.
> > >
> > >> On Mar 5, 2016, at 11:42 PM, Henri Yandell <bay...@apache.org
> <javascript:;>> wrote:
> > >>
> > >> Having chatted around the 0mq community in the past; I've confidence
> in
> > >> their desire to move to MPL; and 26/32 committers is a great step
> forward.
> > >> You raise a good reservation though John - if you remove the blocker
> on the
> > >> usage side, it's easy for the licensing to remain as is.
> > >>
> > >>
> > >> I'm +1 for releasing, with a prominent note of the LGPL dependency
> (along
> > >> with a note of the resolution plan). It might be that the Toree
> committers
> > >> may be motivated to rewrite code over at 0mq if there ends up being
> any
> > >> committers who are unavailable or unwilling to relicense.
> > >>
> > >> Hen
> > >>
> > >>> On Sat, Mar 5, 2016 at 3:45 PM, John D. Ament <johndam...@apache.org
> <javascript:;>>
> wrote:
> > >>>
> > >>> Sorry, misread the revision I was looking at.  The intent to move to
> MPL
> > >>> was done on March 22 2014, 2 years ago this month, not December 2013.
> > >>>
> > >>> John
> > >>>
> > >>> On Sat, Mar 5, 2016 at 6:41 PM John D. Ament <johndam...@apache.org
> <javascript:;>>
> > >>> wrote:
> > >>>
> > >>>> I have some reservations with what you're proposing, and would like
> you
> > >>> to
> > >>>> consult w/ legal-discuss on this first.
> > >>>>
> > >>>> There's a difference between what Mynewt did and what you're
> proposing.
> > >>>> Specifically, this was a transitive dependency that they relied upon
> > >>>> indirectly, so its more of a call out for the library that was
> leveraging
> > >>>> it.  They also intended to replace the library.
> > >>>>
> > >>>> In your case, you're directly tied to a presently LGPL'd library.
> You
> > >>>> have no intentions (from what I can see) of moving off of the
> library.
> > >>>>
> > >>>> I'm also doubting their long term goals of moving to MPL.  If you
> look at
> > >>>> [1], you'll see that the page hasn't been updated since October
> 2014.  In
> > >>>> addition, looking at the pages revision history (the beauty of
> wikis),
> > >>> the
> > >>>> intent to move to MPL was published in December 2013, making the
> > >>> statement
> > >>>> over 2 years old.
> > >>>>
> > >>>> I think while this might be OK for an initial incubator release, the
> > >>>> project needs to weigh very heavily if it wants to continue to
> leverage
> > >>>> ZeroMQ or not going forward.
> > >>>>
> > >>>> [1]: http://zeromq.org/area:licensing
> > >>>>
> > >>>>
> > >>>>> On Sat, Mar 5, 2016 at 5:06 PM Gino Bustelo <g...@bustelos.com
> <javascript:;>>
> > wrote:
> > >>>>>
> > >>>>> Wanted to give folks an update on our progress with dealing with
> JeroMQ,
> > >>>>> an
> > >>>>> LGPL package that enables us to communicate via 0MQ. The 0MQ
> community
> > >>> is
> > >>>>> very aware of the issues with LGPL (LGPLv3 + static link exception)
> and
> > >>> it
> > >>>>> is their inte

Re: Advice on binary NOTICE

[Henri Yandell]

I suspect 'relevant' means those parts of a NOTICE relating to the parts of
the product you use.

In this case you'd include the whole file (ie +1 to Marvin).

I suspect 'relevant' needs clarification in the docs.

Hen



On Friday, March 18, 2016, Stephen Mallette  wrote:

> The Jackson JSON processing lib which is Apache 2.0 licensed carries this
> NOTICE file:
>
> --
> # Jackson JSON processor
>
> Jackson is a high-performance, Free/Open Source JSON processing library.
> It was originally written by Tatu Saloranta (tatu.salora...@iki.fi
> ), and has
> been in development since 2007.
> It is currently developed by a community of developers, as well as
> supported
> commercially by FasterXML.com.
>
> ## Licensing
>
> Jackson core and extension components may be licensed under different
> licenses.
> To find the details that apply to this artifact see the accompanying
> LICENSE file.
> For more information, including possible other licensing options, contact
> FasterXML.com (http://fasterxml.com).
>
> ## Credits
>
> A list of contributors may be found from CREDITS file, which is included
> in some artifacts (usually source distributions); but is always available
> from the source code management (SCM) system project uses.
> --
>
> Does anyone have any advice on what portion of this is relevant for
> inclusion in a binary NOTICE file? Should it all be included perhaps?
>
> Perhaps more generally, given
>
> http://www.apache.org/dev/licensing-howto.html#alv2-dep
>
> where it says,
>
> "If the dependency supplies a NOTICE file, its contents must be analyzed
> and the relevant portions bubbled up into the top-level NOTICE file."
>
> is there any more detailed information on how "relevant portions" get
> determined?
>
> Thanks,
>
> Stephen
>

Re: Possible ASF Incubator Project transfer..

[Henri Yandell]

So you include it in conversations - there would also need to be
discussions on the Glassfish trademark/any domains.  Nothing as
standardized as the software license grant others have referred to, but I
would expect it to be 'if a registered trademark/domain, transferring to
ASF; if not a registered trademark, possibly some form of understanding of
future use'.

Hen

On Thu, Mar 3, 2016 at 3:39 PM, Reza Rahman  wrote:

> Yep, understood. We will give it an honest effort.
>
> Sent from my iPhone
>
> > On Mar 3, 2016, at 6:30 PM, John D. Ament  wrote:
> >
> > You need to start with convincing oracle to provide an SGA for the
> entire glassfish codebase.  Your best bet is to start that before you leave
> oracle.
> >
> > John
> >
> >> On Thu, Mar 3, 2016 at 4:08 PM Reza Rahman 
> wrote:
> >> Obviously I need to take this up in earnest after Friday. In the
> meanwhile let me know what I need to do in order to get myself setup for
> this.
> >>
> >> Anything that is worth it is never easy. This matters enough to try and
> there are many that will be with us, even inside Oracle.
> >>
> >>> On Mar 3, 2016, at 3:57 PM, John D. Ament 
> wrote:
> >>>
> >>> Hi Martin, Reza,
> >>>
> >>> The biggest hurdle would likely be Oracle signing an SGA for the
> glassfish codebase.  Not to mention that all dependencies are currently
> GPL/CDDL dual licensed.
> >>>
> >>> John
> >>>
>  On Thu, Mar 3, 2016 at 3:17 PM Martin Gainty 
> wrote:
>  Looking for procedures for transferring control of currently
> un-maintained glassfish J2EE Server from Oracle to ASF incubator project
> 
>  Thanks and Regards
>  Martin Gainty
> 
> 
>  Subject: Re: [gf-users] Re: Farewell to Oracle
>  To: mgai...@hotmail.com
>  From: reza_rah...@lycos.com
>  Date: Thu, 3 Mar 2016 13:56:02 -0500
> 
> 
> 
> 
> 
> 
>  That sounds just about right. How can I
>    get involved?
> 
> 
> 
>    On 3/3/2016 1:53 PM, Martin Gainty wrote:
> 
> 
> 
> 
>    Feel free to join Marcus and myself to transfer
>  Glassfish to ASF  ..
> 
> 
> 
> 
> 
> 
>    > To: us...@glassfish.java.net
> 
>  > From: reza_rah...@lycos.com
> 
>  > Date: Thu, 3 Mar 2016 12:51:49 -0500
> 
>  > Subject: [gf-users] Farewell to Oracle
> 
>  >
> 
>  > Folks,
> 
>  >
> 
>  > I am leaving Oracle behind on Friday. I have no doubt
>  whatsoever that
> 
>  > this was one of the top five hardest decisions of my
>  life. I am also at
> 
>  > this stage equally certain that this is the way I
>  personally can best
> 
>  > help continue to advance the Java and Java EE
>  communities. I will be
> 
>  > resuming the community work I have been part of for the
>  better part of a
> 
>  > decade in earnest as soon as possible post-Oracle.
> 
>  >
> 
>  > At Oracle folks like my colleagues David Delabassee and
>  Bruno Borges
> 
>  > will continue their roles in the Java EE ecosystem. I
>  certainly wish the
> 
>  > many good folks at Oracle nothing but the best of luck.
>  They have a very
> 
>  > hard job to do and they will continue to need our
>  support, perhaps now
> 
>  > more than ever.
> 
>  >
> 
>  > As always anyone is absolutely welcome to reach out to
>  me on just about
> 
>  > anything. Below are all my contact points.
> 
>  >
> 
>  > Cheers,
> 
>  > Reza
> 
>  >
> 
>  > Email: reza_rah...@lycos.com
> 
>  > Cell: 717-329-8149
> 
>  > Home Office: 215-736-1208
> 
>  > Google/Skype: m.reza.rahman
> 
>  > Twitter: @reza_rahman
> 
>  > https://www.linkedin.com/in/javareza
> 
>  > http://blog.rahmannet.net/
> 
>  > http://cargotracker.java.net
> 
> 
> 
> 
> 
> 
> 
>

Re: Update on Apache Toree and LGPL dependency

[Henri Yandell]

Having chatted around the 0mq community in the past; I've confidence in
their desire to move to MPL; and 26/32 committers is a great step forward.
You raise a good reservation though John - if you remove the blocker on the
usage side, it's easy for the licensing to remain as is.


I'm +1 for releasing, with a prominent note of the LGPL dependency (along
with a note of the resolution plan). It might be that the Toree committers
may be motivated to rewrite code over at 0mq if there ends up being any
committers who are unavailable or unwilling to relicense.

Hen

On Sat, Mar 5, 2016 at 3:45 PM, John D. Ament  wrote:

> Sorry, misread the revision I was looking at.  The intent to move to MPL
> was done on March 22 2014, 2 years ago this month, not December 2013.
>
> John
>
> On Sat, Mar 5, 2016 at 6:41 PM John D. Ament 
> wrote:
>
> > I have some reservations with what you're proposing, and would like you
> to
> > consult w/ legal-discuss on this first.
> >
> > There's a difference between what Mynewt did and what you're proposing.
> > Specifically, this was a transitive dependency that they relied upon
> > indirectly, so its more of a call out for the library that was leveraging
> > it.  They also intended to replace the library.
> >
> > In your case, you're directly tied to a presently LGPL'd library.  You
> > have no intentions (from what I can see) of moving off of the library.
> >
> > I'm also doubting their long term goals of moving to MPL.  If you look at
> > [1], you'll see that the page hasn't been updated since October 2014.  In
> > addition, looking at the pages revision history (the beauty of wikis),
> the
> > intent to move to MPL was published in December 2013, making the
> statement
> > over 2 years old.
> >
> > I think while this might be OK for an initial incubator release, the
> > project needs to weigh very heavily if it wants to continue to leverage
> > ZeroMQ or not going forward.
> >
> > [1]: http://zeromq.org/area:licensing
> >
> >
> > On Sat, Mar 5, 2016 at 5:06 PM Gino Bustelo  wrote:
> >
> >> Wanted to give folks an update on our progress with dealing with JeroMQ,
> >> an
> >> LGPL package that enables us to communicate via 0MQ. The 0MQ community
> is
> >> very aware of the issues with LGPL (LGPLv3 + static link exception) and
> it
> >> is their intention to try to move projects to MPL v2. This is not an
> easy
> >> task depending on the age and size of the projects.
> >>
> >> Apache Toree's API access point is through the 0MQ transport layer
> (using
> >> JeroMQ) and that is how Apache Toree connects out-of-the-box with
> Jupyter,
> >> a very common way of consuming Apache Toree that is already in
> production.
> >>
> >> At this point, the JeroMQ project is still released under LGPL, but our
> >> team initiated communications in mid-February with members of the JeroMQ
> >> community to begin their transition to MPL v2 (
> >> https://github.com/zeromq/jeromq/issues/326). The JeroMQ community
> >> reacted
> >> very positively and quickly began the process of collecting votes from
> >> their committers (https://github.com/zeromq/jeromq/issues/327). After
> 15
> >> days, the current tally stands at 26 out of 32 committers have agreed to
> >> switch license.
> >>
> >> Apache Toree has a JIRA (
> https://issues.apache.org/jira/browse/TOREE-262)
> >> where we keep all the relevant links and update with the latest
> >> information. As that process is underway, we will move forward with
> plans
> >> to release a 0.1.0 version of Apache Toree based on the precedence set
> by
> >> Apache Mynewt (
> >>
> >>
> http://mail-archives.apache.org/mod_mbox/incubator-general/201602.mbox/%3C5F118AA0-4ADA-403B-A6EB-4A85F0B30651%40me.com%3E
> >> ).
> >>
> >> Thanks,
> >> Gino
> >>
> >
>

Re: [VOTE] Accept Gearpump into the Apache Incubator

[Henri Yandell]

+1 (should be binding by vote end :) ).

On Tue, Mar 1, 2016 at 4:53 PM, Andrew Purtell  wrote:

> Greetings,
>
> The discussion of the Gearpump proposal has concluded. Please vote to
> accept Gearpump into the Apache Incubator. I will leave this vote open for
> at least the next 72 hours and will aim to close it Monday the 7th of
> March, 2016 at midnight PT. Gearpump is a flexible, efficient, and scalable
> micro-service based real-time big data streaming engine. The text of the
> proposal is included below and is also available at
> https://wiki.apache.org/incubator/GearpumpProposal
>
> [ ] +1 Accept Gearpump as an Apache Incubator podling.
> [ ] +0 Abstain.
> [ ] -1 Don’t accept Gearpump as an Apache Incubator podling because ...
>
> Note that while votes from Incubator PMC members are binding, all are most
> definitely welcome to vote!
>
> I am +1 (binding).
>
> Best regards,
>
>- Andy
>
>

Re: Trouble building the incbuator website [ERR 0194]

[Henri Yandell]

On Mon, Feb 29, 2016 at 6:26 PM, Marvin Humphrey 
wrote:

> On Mon, Feb 29, 2016 at 5:44 PM, Katherine Marsden 
> wrote:
> > On 2/29/2016 5:10 PM, Katherine Marsden wrote:
> >>
> >> Hi,
> >>
> >> I am having trouble building the incubator website.   I am working on
> >> Windows 7 using Cygwin, but see the same error with git-bash.
> >> I am using IBM java 8
> >>
> > I guess IBM java was the issue. I can build using Oracle java for my
> > JAVA_HOME
>
> Glad you were able to make it work, and thank you for following up
> with the workaround!
>

As a guess, by comparing to the Attic site; maybe you need to drop a
xerces/xalan jar pair into lib.

http://svn.apache.org/repos/asf/attic/site/

Just in case anyone else hits this and finds this email.

Hen

Re: Copyright sign offs

[Henri Yandell]

Is 'it was already under Apache 2.0' typically taken to cover:

  "Check and make sure that the papers that transfer rights to the ASF been
received. It is only necessary to transfer rights for the package, the core
code, and any new code produced by the project."

?

Hen



On Mon, Feb 29, 2016 at 4:17 PM, John D. Ament <johndam...@apache.org>
wrote:

> Dennis,
>
> For some reason, Oliver Rau added you in this commit
>
> https://svn.apache.org/viewvc/incubator/public/trunk/content/projects/odftoolkit.xml?r1=1296007=1531246
> If you don't belong, you should be able to remove yourself.
>
> John
>
> On Mon, Feb 29, 2016 at 6:30 PM Dennis E. Hamilton <
> dennis.hamil...@acm.org>
> wrote:
>
> > Henri,
> >
> > I did a quick look at the odftoolkit repository and the podling page.
> >
> > The odftoolkit project was originally under ALv2.  The code still carries
> > Copyright notices on the individual files and the ALv2 license statement
> > has not been updated/replaced by the current one mentioning contribution
> to
> > the ASF, etc.
> >
> > In passing, I notice a peculiarity of the incubator page,
> > <http://incubator.apache.org/projects/odftoolkit.html>.  I'm certain I
> > was never on the PPMC and I don't think I was a committer either, unless
> it
> > is transitive via incubator (a change since 2012?).  My impression was
> that
> > the PPMC was rather small.  I have no idea what its current membership
> is.
> >
> > There has been recent maintenance on the source code, some working
> against
> > JIRA issues, as reported in the February 2016 Incubator Report.
> >
> >  - Dennis
> >
> >
> > > -Original Message-
> > > From: Henri Yandell [mailto:bay...@apache.org]
> > > Sent: Friday, February 26, 2016 17:28
> > > To: general@incubator.apache.org
> > > Subject: Copyright sign offs
> > >
> > > Haven't done this in a while :)
> > >
> > > Thought I'd share that the following podlings have not yet signed off
> on
> > > their Copyright sections in their status reports. I mention this
> because
> > > I
> > > believe it's one of the first elements that should be signed off on the
> > > status report and it's a worry if projects have not done so:
> > >
> > >   cmda
> > >   datafu
> > >   horn
> > >   johnzon
> > >   odftoolkit
> > [ ... ]
> > >
> > > I'd be interested to hear about any reasons why the above aren't able
> to
> > > sign that element of their status file off.
> > [ ... ]
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Copyright sign offs

[Henri Yandell]

Haven't done this in a while :)

Thought I'd share that the following podlings have not yet signed off on
their Copyright sections in their status reports. I mention this because I
believe it's one of the first elements that should be signed off on the
status report and it's a worry if projects have not done so:

  cmda
  datafu
  horn
  johnzon
  odftoolkit
  openaz
  samoa
  slider
  streams
  taverna

I'd be interested to hear about any reasons why the above aren't able to
sign that element of their status file off.

(same, but for those who are < 6 months in the incubator, ie) still working
on it)

  beam
  concerted
  eagle
  fineract
  guacamole
  iota
  impala
  joshua
  metron
  milagro
  rya
  systemml
  toree
  unomi

Hen

Re: [DISCUSS] Gearpump incubation proposal

[Henri Yandell]

Thought I'd share a report I generated from some code of mine on the
gearpump GitHub org (attached - though mail server may block).

The highlights are:

* 9 repos.
* High number of pull requests resolved (1026/1030).
* Fairly high number of issues resolved (853/951).
* Pull requests are resolved very quickly, over half in an hour.
* Issues a more classic 'nessie' curve. This is what I usually see for
issue/pull-request response time.
* Good balance of community and project for opening of
issues/pull-requests, but my report is limited here as I go by the public
members of the organization and I'm not analyzing where the reporters are
coming from.

Anyway - thought I'd share as I was impressed by the pull request activity.

Hen


On Thu, Feb 25, 2016 at 3:59 PM, Andrew Purtell  wrote:

> Greetings,
>
> It is my pleasure to present the proposal to incubate the Gearpump project
> at the Apache Software Foundation. Gearpump is a flexible, efficient, and
> scalable micro-service based real-time big data streaming engine developed
> up to this point by Intel Corporation as a GitHub project licensed under
> the Apache License 2.0.
>
> The text of the proposal is included below and is also available at
> https://wiki.apache.org/incubator/GearpumpProposal
>
> Best regards,
>
>- Andy​​
>
> -
>
> = Gearpump Proposal =
>
> === Abstract ===
> Gearpump is a flexible, efficient and scalable micro-service based
> real-time big data streaming engine developed by Intel Corporation which
> has been licensed by Intel under the Apache License 2.0.
>
> === Proposal ===
> Gearpump is a reactive real-time streaming engine; completely based on the
> micro-service Actor model. Gearpump provides extremely high performance
> stream processing while maintaining millisecond latency message delivery.
> It enables reusable, composable flows or partial graphs that can be
> remotely deployed and executed in a diverse set of environments, including
> IoT edge devices. These flows may be deployed and modified at runtime -- a
> capability few real time streaming frameworks provide today.
>
> The goal of this proposal is to incubate Gearpump as an Apache project in
> order to build a diverse, healthy, and self-governed open source community
> around this project.
>
> === Background ===
> In past decade, there have been many advances within real-time streaming
> frameworks. Despite many advances, users of streaming frameworks often
> complain about flexibility, efficiency, and scalability. Gearpump endeavors
> to solve these challenges by adopting the micro-service Actor model. The
> Actor model was proposed by Carl Hewitt in 1973. In the Actor model, each
> actor is a message driven micro-service; actors are the basic building
> blocks of concurrent computation. By leveraging Actor Model’s location
> transparency feature, Gearpump allows a graph to be composed of several
> partial graphs, where, for example, some parts may be deployed to remote
> IoT edge devices, and other parts to a data center. This division and
> deployment model can be changed at runtime to adapt to a changing physical
> environment, providing extreme flexibility and elasticity in solving
> various ingestion and analytics problems. We’ve found Actors to be a much
> smaller computation unit compared with threads, where smaller usually means
> better concurrency, and potentially better CPU utilization.
>
> === Rationale ===
> Gearpump tightly integrates and enhances the big data community of Apache
> projects. Intel believes Gearpump can bring benefits to the Apache
> community in a number of ways:
>
> 1. Gearpump complements many existing Apache projects, in particular, those
> commonly found within the big data space. Users of this project are also
> users of other Apache projects, such as Hadoop ecosystem projects. It is
> beneficial to align these projects under the ASF umbrella. In real-time
> streaming, Gearpump offers some special features that are useful for Apache
> users, such as exactly-once processing with millisecond message level
> latency and dynamic DAGs that allow online topology modifications.
>
> 2. Gearpump tightly integrates with Apache big data projects. It supports
> for Apache HDFS, YARN, Kafka, and HBase. It uses Apache YARN for resource
> scheduling and Apache HDFS as the essential distributed storage system.
>
> 3. The micro-service model of reusable flows that Gearpump has adopted is
> very unique, and it may become common in the future. Gearpump sets a good
> example about how distributed software can be implemented within a
> micro-service model.  An open project is of best interest to our users. By
> joining Apache, it will be a neutral infrastructure platform that will
> benefit everyone.
>
> 4. The process and development philosophy of Apache will help Gearpump
> grow, and build a diverse, healthy, and self-governed open source
> community.
>
> === Initial Goals ===
> 1. Migrate the existing codebase to Apache.

Re: Single person developed project

[Henri Yandell]

Note that http://labs.apache.org/ may be what you're looking for if this is
your own project.

On Mon, Feb 15, 2016 at 12:47 AM, Amareshwari Sriramdasu <
amareshw...@apache.org> wrote:

> Hi all,
>
> Wanted to know if a single person developed project can get incubated in
> Apache. Any doc links would be helpful as well.
>
> Thanks
> Amareshwari
>

Re: [VOTE] Accept Joshua as an Apache Incubator Podling

[Henri Yandell]

I'm more likely to guide contributions from my employer. There's been some
contributions thus far, and there is interest to put more dayjob time into
contributing, but currently there's no coder who personally is committed to
the project.

Hen

On Mon, Feb 1, 2016 at 7:20 AM, Mattmann, Chris A (3980) <
chris.a.mattm...@jpl.nasa.gov> wrote:

> Hey Jim,
>
> This is a valid concern, one that I hope is mediated by taking
> however long it takes in Incubation to attract some new committers
> to work on the project. Hopefully too you saw how long I took to
> allow the discussion to occur and so forth.
>
> Lewis has actively contributed to Joshua already - you can see -
> via the HomeBrew package he created, see:
>
> https://github.com/Homebrew/homebrew/pull/45746
>
>
> You can see too it wasn’t something just recent or something
> super quick it’s something he had to work at.
>
> As for me, my involvement is going to be limited, but I am
> actively pursuing Tika’s integration with Joshua as part of
> TIKA-1343: http://issues.apache.org/jira/browse/TIKA-1343.
>
> Finally my suspicion is that Tom, Henry and Tommaso will
> contribute a lot as well.
>
> Thanks for listening.
>
> Cheers,
> Chris
>
> ++
> Chris Mattmann, Ph.D.
> Chief Architect
> Instrument Software and Science Data Systems Section (398)
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 168-519, Mailstop: 168-527
> Email: chris.a.mattm...@nasa.gov
> WWW:  http://sunset.usc.edu/~mattmann/
> ++
> Adjunct Associate Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++
>
>
>
>
>
> -Original Message-
> From: Jim Jagielski 
> Reply-To: "general@incubator.apache.org" 
> Date: Monday, February 1, 2016 at 4:20 AM
> To: "general@incubator.apache.org" 
> Cc: "p...@cs.jhu.edu" 
> Subject: Re: [VOTE] Accept Joshua as an Apache Incubator Podling
>
> >I know this is specifically called-out in the proposal, but it
> >does seem worthy of further discussion.
> >
> >This has a pretty small list of initial committers, esp when one considers
> >how over-booked 2 of them appear to be.
> >
> >So, realistically, how active do both Chris and Lewis expect
> >to be?
> >
> >> On Jan 30, 2016, at 3:00 PM, Mattmann, Chris A (3980)
> >> wrote:
> >>
> >> Hi Everyone,
> >>
> >> OK the discussion is now completed. Please VOTE to accept Joshua
> >> into the Apache Incubator. I’ll leave the VOTE open for at least
> >> the next 72 hours, with hopes to close it next Friday the 5th of
> >> February, 2016.
> >>
> >> [ ] +1 Accept Joshua as an Apache Incubator podling.
> >> [ ] +0 Abstain.
> >> [ ] -1 Don’t accept Joshua as an Apache Incubator podling because..
> >>
> >> Of course, I am +1 on this. Please note VOTEs from Incubator PMC
> >> members are binding but all are welcome to VOTE!
> >>
> >> Cheers,
> >> Chris
> >>
> >> ++
> >> Chris Mattmann, Ph.D.
> >> Chief Architect
> >> Instrument Software and Science Data Systems Section (398)
> >> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> >> Office: 168-519, Mailstop: 168-527
> >> Email: chris.a.mattm...@nasa.gov
> >> WWW:  http://sunset.usc.edu/~mattmann/
> >> ++
> >> Adjunct Associate Professor, Computer Science Department
> >> University of Southern California, Los Angeles, CA 90089 USA
> >> ++
> >>
> >>
> >>
> >>
> >>
> >> -Original Message-
> >> From: jpluser 
> >> Date: Tuesday, January 12, 2016 at 10:56 PM
> >> To: "general@incubator.apache.org" 
> >> Cc: "p...@cs.jhu.edu" 
> >> Subject: [DISCUSS] Apache Joshua Incubator Proposal - Machine
> >>Translation
> >> Toolkit
> >>
> >>> Hi Everyone,
> >>>
> >>> Please find attached for your viewing pleasure a proposed new project,
> >>> Apache Joshua, a statistical machine translation toolkit. The proposal
> >>> is in wiki draft form at:
> >>>https://wiki.apache.org/incubator/JoshuaProposal
> >>>
> >>> Proposal text is copied below. I’ll leave the discussion open for a
> >>>week
> >>> and we are interested in folks who would like to be initial committers
> >>> and mentors. Please discuss here on the thread.
> >>>
> >>> Thanks!
> >>>
> >>> Cheers,
> >>> Chris (Champion)
> >>>
> >>> ———
> >>>
> >>> = Joshua Proposal =
> >>>
> >>> == Abstract ==
> >>> [[joshua-decoder.org|Joshua]] is an open-source statistical machine
> >>> translation toolkit. It includes a Java-based decoder for translating
> >>>with
> >>> phrase-based, 

Re: [VOTE] Accept Joshua as an Apache Incubator Podling

[Henri Yandell]

+1 (non-binding).

On Sat, Jan 30, 2016 at 5:45 PM, Luke Han  wrote:

> +1 non-binding
>
>
> Best Regards!
> -
>
> Luke Han
>
> On Sun, Jan 31, 2016 at 5:27 AM, Tom Barber 
> wrote:
>
> > +1 binding
> >
> > Should be a very interesting project!
> >
> > On Sat, Jan 30, 2016 at 8:05 PM, Ashish  wrote:
> >
> > > + (non-binding)
> > >
> > > On Sat, Jan 30, 2016 at 12:00 PM, Mattmann, Chris A (3980)
> > >  wrote:
> > > > Hi Everyone,
> > > >
> > > > OK the discussion is now completed. Please VOTE to accept Joshua
> > > > into the Apache Incubator. I’ll leave the VOTE open for at least
> > > > the next 72 hours, with hopes to close it next Friday the 5th of
> > > > February, 2016.
> > > >
> > > > [ ] +1 Accept Joshua as an Apache Incubator podling.
> > > > [ ] +0 Abstain.
> > > > [ ] -1 Don’t accept Joshua as an Apache Incubator podling because..
> > > >
> > > > Of course, I am +1 on this. Please note VOTEs from Incubator PMC
> > > > members are binding but all are welcome to VOTE!
> > > >
> > > > Cheers,
> > > > Chris
> > > >
> > > > ++
> > > > Chris Mattmann, Ph.D.
> > > > Chief Architect
> > > > Instrument Software and Science Data Systems Section (398)
> > > > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> > > > Office: 168-519, Mailstop: 168-527
> > > > Email: chris.a.mattm...@nasa.gov
> > > > WWW:  http://sunset.usc.edu/~mattmann/
> > > > ++
> > > > Adjunct Associate Professor, Computer Science Department
> > > > University of Southern California, Los Angeles, CA 90089 USA
> > > > ++
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > -Original Message-
> > > > From: jpluser 
> > > > Date: Tuesday, January 12, 2016 at 10:56 PM
> > > > To: "general@incubator.apache.org" 
> > > > Cc: "p...@cs.jhu.edu" 
> > > > Subject: [DISCUSS] Apache Joshua Incubator Proposal - Machine
> > Translation
> > > > Toolkit
> > > >
> > > >>Hi Everyone,
> > > >>
> > > >>Please find attached for your viewing pleasure a proposed new
> project,
> > > >>Apache Joshua, a statistical machine translation toolkit. The
> proposal
> > > >>is in wiki draft form at:
> > > https://wiki.apache.org/incubator/JoshuaProposal
> > > >>
> > > >>Proposal text is copied below. I’ll leave the discussion open for a
> > week
> > > >>and we are interested in folks who would like to be initial
> committers
> > > >>and mentors. Please discuss here on the thread.
> > > >>
> > > >>Thanks!
> > > >>
> > > >>Cheers,
> > > >>Chris (Champion)
> > > >>
> > > >>———
> > > >>
> > > >>= Joshua Proposal =
> > > >>
> > > >>== Abstract ==
> > > >>[[joshua-decoder.org|Joshua]] is an open-source statistical machine
> > > >>translation toolkit. It includes a Java-based decoder for translating
> > > with
> > > >>phrase-based, hierarchical, and syntax-based translation models, a
> > > >>Hadoop-based grammar extractor (Thrax), and an extensive set of tools
> > and
> > > >>scripts for training and evaluating new models from parallel text.
> > > >>
> > > >>== Proposal ==
> > > >>Joshua is a state of the art statistical machine translation system
> > that
> > > >>provides a number of features:
> > > >>
> > > >> * Support for the two main paradigms in statistical machine
> > translation:
> > > >>phrase-based and hierarchical / syntactic.
> > > >> * A sparse feature API that makes it easy to add new feature
> templates
> > > >>supporting millions of features
> > > >> * Native implementations of many tuners (MERT, MIRA, PRO, and
> AdaGrad)
> > > >> * Support for lattice decoding, allowing upstream NLP tools to
> expose
> > > >>their hypothesis space to the MT system
> > > >> * An efficient representation for models, allowing for quick loading
> > of
> > > >>multi-gigabyte model files
> > > >> * Fast decoding speed (on par with Moses and mtplz)
> > > >> * Language packs — precompiled models that allow the decoder to be
> run
> > > as
> > > >>a black box
> > > >> * Thrax, a Hadoop-based tool for learning translation models from
> > > >>parallel text
> > > >> * A suite of tools for constructing new models for any language pair
> > for
> > > >>which sufficient training data exists
> > > >>
> > > >>== Background and Rationale ==
> > > >>A number of factors make this a good time for an Apache project
> focused
> > > on
> > > >>machine translation (MT): the quality of MT output (for many language
> > > >>pairs); the average computing resources available on computers,
> > relative
> > > >>to the needs of MT systems; and the availability of a number of
> > > >>high-quality toolkits, together with a large base of researchers
> > working
> > > >>on them.
> > > >>
> > > >>Over the past decade, 

Re: [DISCUSS] Apache Joshua Incubator Proposal - Machine Translation Toolkit

[Henri Yandell]

On Wed, Jan 20, 2016 at 10:37 AM, Mattmann, Chris A (3980) <
chris.a.mattm...@jpl.nasa.gov> wrote:

> All of this can be worked during Incubation and I think we have
> the right folks here who can help to get it set up.
>

Yup - my question was well answered; thanks all :)

Hen

Re: [DISCUSS] Apache Joshua Incubator Proposal - Machine Translation Toolkit

[Henri Yandell]

'TM'?

On Tue, Jan 19, 2016 at 9:42 PM, toki <toki.kant...@gmail.com> wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 20/01/2016 03:38, Henri Yandell wrote:
>
> > License-wise, any expectation of problems from the GPL and LGPL depend
> encies?
>
> I'd also recommend closely examining the license for any TM libraries
> that ship with the program, with a focus on the providence of the  libra
> ry.
>
> Whilst it has been several years since I've used a TM library, when I
> did, the licenses were, under Debian Guidelines, non-free. Back then, I
> didn't look at licenses, to see if they complied with Apache Guidelines.
>
> About fifteen years ago, I was on the fringes of a lawsuit involving a
> TM library. All intellectual property rights of the TM Library belonged
> to the developers of the software program, even though the words in the
> TM Library were either deliberately selected by the licensed user of the
> software program, or came from parsing content that was created, and to
> whom all intellectual property rights apparently were owned, by the user
> of the software program.
>
> jonathon
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2.0.22 (GNU/Linux)
>
> iQIcBAEBAgAGBQJWnx5QAAoJEKG7hs8nSMR7YM8QAIVT3FdUncmBryIsd4fFUwDV
> nUwinxGfFON6PGdyfOPmZsl2CRz8c+sJxrCVxJePj0PbwCLTfIy+HHNro3lpAefC
> iHLBHdWyFOBtlkxac+QigRG7tuKw9xRd5lo7Y5A3cNx/C1nL0c4GULDZCaZtDnQi
> yf5bUdmyU57KYeMbg4hTePeYkiOYt1Bez37V00hj57AAuo3JZWCzGv/rFcgFZ0r5
> nGaQrSll7N8UJ68HurBPReRdxhnVYv5jTTgI0sCoJfBaIH7DZga6Mur87LGbvjUW
> 3xomBzpHuMGpZBnuNBMyyMOFpZlu41zmLHeAWL/L27fOkKcfuVcDeZsXlg/jOULg
> P/iqxuVQqpmMThpSUVDBcsBF/VjgHTGCFz7buv/4GKhNtbTohldMX6oTBaIfgPOg
> QIEM9k4LYLbl4jLBP/I3fESAte+pW1bFglMEj+YfoUTBMYQsvclMqSwi/oYA5xS2
> IbmQtqxXG26Dm/a8fb5eRJ3fp4lGkXWHmq/vdrkNLtYgQ5kwGTilQpiWjowJnLVm
> ODlTvgS44JMFeMw2cAzVUjdpH9IZT89Glo6iL3J7ncfnaIZSwozQRCbLStf1jY/u
> CznX492Lywdw2dm+QcpEpq7dm5ewm0AORFumodvn+P+cYqLigsjNOz0yO/RCaBOg
> pkYvV6RHni2vFqn44uRq
> =88z1
> -END PGP SIGNATURE-
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Apache Joshua Incubator Proposal - Machine Translation Toolkit

[Henri Yandell]

License-wise, any expectation of problems from the GPL and LGPL
dependencies?

On Mon, Jan 18, 2016 at 9:58 PM, Mattmann, Chris A (3980) <
chris.a.mattm...@jpl.nasa.gov> wrote:

> Great Hen, we’d love to have you on board as a mentor! Please
> add yourself to the proposal on the wiki.
>
> Anyone else have interest in Machine Translation? Any OpenNLP folks,
> Hadoop folks, Tika, or Lucene folks? CC’ing the dev lists for visibility
> please feel free to reply to general@i.a.o.
>
> I’ll leave the DISCUSS thread open for a few more days.
>
> Cheers,
> Chris
>
> ++
> Chris Mattmann, Ph.D.
> Chief Architect
> Instrument Software and Science Data Systems Section (398)
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 168-519, Mailstop: 168-527
> Email: chris.a.mattm...@nasa.gov
> WWW:  http://sunset.usc.edu/~mattmann/
> ++
> Adjunct Associate Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++
>
>
>
>
>
> -Original Message-
> From: Henri Yandell <bay...@apache.org>
> Reply-To: "general@incubator.apache.org" <general@incubator.apache.org>
> Date: Monday, January 18, 2016 at 7:57 PM
> To: jpluser <chris.a.mattm...@jpl.nasa.gov>,
> "general@incubator.apache.org" <general@incubator.apache.org>
> Subject: Re: [DISCUSS] Apache Joshua Incubator Proposal - Machine
> Translation Toolkit
>
> >Non-binding +1 to Joshua joining the Incubator. I'd be interested in
> >mentoring.
> >
> >
> >> -Original Message-
> >> From: jpluser <chris.a.mattm...@jpl.nasa.gov>
> >> Reply-To: "general@incubator.apache.org" <general@incubator.apache.org>
> >> Date: Tuesday, January 12, 2016 at 10:56 PM
> >> To: "general@incubator.apache.org" <general@incubator.apache.org>
> >> Cc: "p...@cs.jhu.edu" <p...@cs.jhu.edu>
> >> Subject: [DISCUSS] Apache Joshua Incubator Proposal - Machine
> >>Translation
> >> Toolkit
> >>
> >> >Hi Everyone,
> >> >
> >> >Please find attached for your viewing pleasure a proposed new project,
> >> >Apache Joshua, a statistical machine translation toolkit. The proposal
> >> >is in wiki draft form at:
> >> https://wiki.apache.org/incubator/JoshuaProposal
> >> >
> >> >Proposal text is copied below. I’ll leave the discussion open for a
> >>week
> >> >and we are interested in folks who would like to be initial committers
> >> >and mentors. Please discuss here on the thread.
> >> >
> >> >Thanks!
> >> >
> >> >Cheers,
> >> >Chris (Champion)
> >> >
> >> >———
> >> >
> >> >= Joshua Proposal =
> >> >
> >> >== Abstract ==
> >> >[[joshua-decoder.org|Joshua]] is an open-source statistical machine
> >> >translation toolkit. It includes a Java-based decoder for translating
> >>with
> >> >phrase-based, hierarchical, and syntax-based translation models, a
> >> >Hadoop-based grammar extractor (Thrax), and an extensive set of tools
> >>and
> >> >scripts for training and evaluating new models from parallel text.
> >> >
> >> >== Proposal ==
> >> >Joshua is a state of the art statistical machine translation system
> >>that
> >> >provides a number of features:
> >> >
> >> > * Support for the two main paradigms in statistical machine
> >>translation:
> >> >phrase-based and hierarchical / syntactic.
> >> > * A sparse feature API that makes it easy to add new feature templates
> >> >supporting millions of features
> >> > * Native implementations of many tuners (MERT, MIRA, PRO, and AdaGrad)
> >> > * Support for lattice decoding, allowing upstream NLP tools to expose
> >> >their hypothesis space to the MT system
> >> > * An efficient representation for models, allowing for quick loading
> >>of
> >> >multi-gigabyte model files
> >> > * Fast decoding speed (on par with Moses and mtplz)
> >> > * Language packs — precompiled models that allow the decoder to be
> >>run as
> >> >a black box
> >> > * Thrax, a Hadoop-based tool for learning translation models from
> &

Re: [DISCUSS] Apache Joshua Incubator Proposal - Machine Translation Toolkit

[Henri Yandell]

Non-binding +1 to Joshua joining the Incubator. I'd be interested in
mentoring.


> -Original Message-
> From: jpluser 
> Reply-To: "general@incubator.apache.org" 
> Date: Tuesday, January 12, 2016 at 10:56 PM
> To: "general@incubator.apache.org" 
> Cc: "p...@cs.jhu.edu" 
> Subject: [DISCUSS] Apache Joshua Incubator Proposal - Machine Translation
> Toolkit
>
> >Hi Everyone,
> >
> >Please find attached for your viewing pleasure a proposed new project,
> >Apache Joshua, a statistical machine translation toolkit. The proposal
> >is in wiki draft form at:
> https://wiki.apache.org/incubator/JoshuaProposal
> >
> >Proposal text is copied below. I’ll leave the discussion open for a week
> >and we are interested in folks who would like to be initial committers
> >and mentors. Please discuss here on the thread.
> >
> >Thanks!
> >
> >Cheers,
> >Chris (Champion)
> >
> >———
> >
> >= Joshua Proposal =
> >
> >== Abstract ==
> >[[joshua-decoder.org|Joshua]] is an open-source statistical machine
> >translation toolkit. It includes a Java-based decoder for translating with
> >phrase-based, hierarchical, and syntax-based translation models, a
> >Hadoop-based grammar extractor (Thrax), and an extensive set of tools and
> >scripts for training and evaluating new models from parallel text.
> >
> >== Proposal ==
> >Joshua is a state of the art statistical machine translation system that
> >provides a number of features:
> >
> > * Support for the two main paradigms in statistical machine translation:
> >phrase-based and hierarchical / syntactic.
> > * A sparse feature API that makes it easy to add new feature templates
> >supporting millions of features
> > * Native implementations of many tuners (MERT, MIRA, PRO, and AdaGrad)
> > * Support for lattice decoding, allowing upstream NLP tools to expose
> >their hypothesis space to the MT system
> > * An efficient representation for models, allowing for quick loading of
> >multi-gigabyte model files
> > * Fast decoding speed (on par with Moses and mtplz)
> > * Language packs — precompiled models that allow the decoder to be run as
> >a black box
> > * Thrax, a Hadoop-based tool for learning translation models from
> >parallel text
> > * A suite of tools for constructing new models for any language pair for
> >which sufficient training data exists
> >
> >== Background and Rationale ==
> >A number of factors make this a good time for an Apache project focused on
> >machine translation (MT): the quality of MT output (for many language
> >pairs); the average computing resources available on computers, relative
> >to the needs of MT systems; and the availability of a number of
> >high-quality toolkits, together with a large base of researchers working
> >on them.
> >
> >Over the past decade, machine translation (MT; the automatic translation
> >of one human language to another) has become a reality. The research into
> >statistical approaches to translation that began in the early nineties,
> >together with the availability of large amounts of training data, and
> >better computing infrastructure, have all come together to produce
> >translations results that are “good enough” for a large set of language
> >pairs and use cases. Free services like
> >[[https://www.bing.com/translator|Bing Translator]] and
> >[[https://translate.google.com|Google Translate]] have made these
> services
> >available to the average person through direct interfaces and through
> >tools like browser plugins, and sites across the world with higher
> >translation needs use them to translate their pages through automatically.
> >
> >MT does not require the infrastructure of large corporations in order to
> >produce feasible output. Machine translation can be resource-intensive,
> >but need not be prohibitively so. Disk and memory usage are mostly a
> >matter of model size, which for most language pairs is a few gigabytes at
> >most, at which size models can provide coverage on the order of tens or
> >even hundreds of thousands of words in the input and output languages. The
> >computational complexity of the algorithms used to search for translations
> >of new sentences are typically linear in the number of words in the input
> >sentence, making it possible to run a translation engine on a personal
> >computer.
> >
> >The research community has produced many different open source translation
> >projects for a range of programming languages and under a variety of
> >licenses. These projects include the core “decoder”, which takes a model
> >and uses it to translate new sentences between the language pair the model
> >was defined for. They also typically include a large set of tools that
> >enable new models to be built from large sets of example translations
> >(“parallel data”) and monolingual texts. These toolkits are usually built
> >to support the agendas of the (largely) academic researchers 

Re: ODF Toolkit may need help

[Henri Yandell]

I don't see any project within the Attic that came there from the
Incubator.

If one did, it should have passed its IP items already.

My opinion on domain names for a project not graduating is that we give it
back to who gave it to us, or if they don't want it back, let them decide
who we should give it to.

Hen

On Sat, Sep 5, 2015 at 2:28 AM, Greg Stein  wrote:

> If the podling *has* cleared all IP, then I could see allowing it. But we
> certainly don't want improper IP residing in the Attic. These aren't Apache
> projects until graduation, so don't really belong. I can see releases
> strengthening the argument for archival.
>
> Henri should be able to clarify.
>
> Cheers,
> -g
> On Sep 5, 2015 3:35 AM, "Dave Fisher"  wrote:
>
>> I recollect seeing a retiring podling with releases go to the attic. If
>> that is not correct or it was an exceptional case then thanks for the
>> correction.
>>
>> What would be done with domain names? The podling came in with the domain
>> name offtoolkit.org. What happens to that?
>>
>> Regards,
>> Dave
>>
>> Sent from my iPhone
>>
>> > On Sep 3, 2015, at 10:00 PM, Greg Stein  wrote:
>> >
>> > The Attic is for Apache projects. Podlings are simply retired/removed.
>> >> On Sep 4, 2015 9:23 AM, "Dave Fisher"  wrote:
>> >>
>> >>
>> >>
>> >> Sent from my iPhone
>> >>
>> >>> On Sep 3, 2015, at 5:12 AM, John D. Ament 
>> wrote:
>> >>>
>> >>> Hi Rob,
>>  On Thu, Sep 3, 2015 at 7:56 AM Rob Weir  wrote:
>> 
>>  On Wed, Sep 2, 2015 at 6:25 AM, John D. Ament > >
>>  wrote:
>> > All,
>> >
>> > I'd like to bring to your attention the ODF Toolkit podling.
>> >
>> > This podling has been incubating for over 4 years now.  Last month
>> they
>> > filed a report without mentor sign off, without any feedback on the
>>  mailing
>> > list.  They have remained partially active throughout the 4 years,
>> but
>>  from
>> > what I can tell suffering a bit in community growth.  I'd like to
>> seek
>> > input from the incubator on how to potentially resolve this and
>> maybe
>> >> get
>> > help for this podling.
>> >
>> > John
>> 
>> 
>>  I am the mentor who did not sign off last month.  You may have
>> noticed
>>  that the podling has been filing nearly identical reports for some
>>  time now.   I'd sum up accomplishments to date as:
>> 
>>  1) We've done a few podling releases.
>> 
>>  2) IP review is in good shape
>> 
>>  3) Community gets along well, no significant frictions
>> 
>>  4) Community has added new committers outside the original PPMC, but
>>  has also lost its original corporate-sponsored developers.
>> 
>>  5) The code is being used, as seen by incoming traffic on users list
>>  and occasional patch submissions
>> >>>
>> >>> I have noticed that.  Has the podling been made aware that the report
>> >>> shouldn't be a copy and paste, and that stagnating growth is probably
>> >> not a
>> >>> good sign?  It would help to explain why their report wasn't signed
>> off
>> >> on.
>> >>>
>> >>>
>> >>>
>> >>>
>> 
>>  These are all good steps towards graduation.  However, the community
>>  thinks, and I tend to agree, that the activity level is too low to
>>  sustain a TLP.   If we were able to attract another 2 or 3 active
>>  developers we would be in great shape.  As mentor I've given advice
>>  when asked, and when I thought needed.  But I'm not standing there
>>  with a whip and a megaphone telling them what to do.   I don't think
>>  that makes a sustainable community.
>> 
>>  I don't think shuffling the code around within Apache, to another
>>  project (or Podling) really solves anything.  The Attic is one
>> option,
>>  but my guess is that would end the podling but not the (albeit small)
>>  community.  They would probably just set up on github and continue
>>  with the same pace of activity, with a lighterweight process, outside
>>  of Apache.  So, personally, I don't think the Attic would be the
>> death
>>  of the ODF Toolkit.
>> >>>
>> >>> The attic should be considered only as a last stitch effort, all other
>> >>> attempts at resolving the podling have been tried and failed.
>> >>
>> >> Nothing stops anyone from forking the podling to another location. The
>> >> incubator would need to do something with the code. That would be to
>> put it
>> >> in the attic as an archive, as not maintained any longer.
>> >>
>> >> This is decision for the community such as it is to make.
>> >>
>> >> Regards,
>> >> Dave
>> >>
>> >>
>> >>>
>> >>>
>> 
>>  Regards,
>> 
>>  -Rob
>> 
>>  -
>>  To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> 

Re: A request/suggestion for shepherds: be firm about IP clearance

[Henri Yandell]

I'm hoping we can reach a point where every project older than 6
months has done IP clearance; then as each project reaches 6 months it
either signs off on IP or is terminated.

Hen

On Thu, Aug 23, 2012 at 7:14 AM, Benson Margulies bimargul...@gmail.com wrote:
 After my recent adventure sorting out Kato's IP clearance, I have an
 intention as a shepherd, and I'd like to suggest that others pick it
 up, as well.

 If a podling has not filled in the IP clearance field on their status
 page, ask them what's going on, and ask them to report the status in
 their report. If IP clearance is done but the status field is not
 checked, insist that they go edit that page, *right now*, and insert
 the necessary data.

 -
 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: Amber CLA status [Was: Old projects with incomplete copyright diligence]

[Henri Yandell]

Sounds like you should sign off on the first item in the Copyright
section of http://incubator.apache.org/projects/amber.html as n/a.
No code was relicensed to the ASF when Amber was created. Instead it
was a fork of Uni of Newcastle code and that copyright remains on the
code.

Hen

On Mon, Aug 20, 2012 at 1:00 AM, Antonio Sanso asa...@adobe.com wrote:
 Hi Henri,

 thanks for taking care of this.

 IANAL but technically yes I think that the OAuth 2.0 part of Amber can be 
 considered as a fork.

 Before to perform the first release we followed what has been suggested in 
 LEGAL-134.
 Did we miss something? Should we do something more or we can assume this 
 legal issue is over?

 Thanks and regards

 Antonio


 On Aug 12, 2012, at 8:28 PM, Henri Yandell wrote:

 Hi Antonio,

 This is about making sure that all software being contributed to
 Apache is covered by CLAs (continuous contribution) or the software
 license grant (single contribution). Legally it would also be fine to
 fork software under a Category A license, though it's frowned upon
 (ie: the status checkbox doesn't offer it as an option).

 By the look of LEGAL-134, it sounds like Amber started as a fork of
 University of Newcastle code?

 Hen

 On Fri, Jul 13, 2012 at 7:39 AM, Antonio Sanso asa...@adobe.com wrote:
 Hi Henri,

 Amber wise we tracked this in [0].
 Now I am not sure if we can also tick the box.

 Regards

 Antonio

 [0] https://issues.apache.org/jira/browse/LEGAL-134

 On Jul 8, 2012, at 4:22 AM, Henri Yandell wrote:

 The following projects haven't signed off on the copyright checklist item:

 2009-02-09  kato
 2009-02-13  stonehenge
 2009-05-13  socialsite
 2010-05-19  amber
 2010-09-05  nuvem
 2010-11-12  kitty
 2010-11-24  stanbol
 2011-06-13  openofficeorg

 Said checklist item is:

 Check and make sure that the papers that transfer rights to the ASF
 been received. It is only necessary to transfer rights for the
 package, the core code, and any new code produced by the project. 

 How long do we host software without explicitly stating we have these 
 rights?

 Personally I think 1 year is more than enough, even for OpenOffice.

 Note that this list comes from
 https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects

 Hen

 -
 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


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Amber CLA status [Was: Old projects with incomplete copyright diligence]

[Henri Yandell]

There are other legal items on that page that you should review and
decide if you can check off. If you're releasing, then I would expect
that page to have no unfinished tasks.

Hen

On Thu, Aug 23, 2012 at 12:32 AM, Antonio Sanso asa...@adobe.com wrote:
 Thanks a lot for your effort Henri,

  we will do as you suggested.

 Do you thing we are missing anything else legally wise?

 Regards

 Antonio

 On Aug 23, 2012, at 9:18 AM, Henri Yandell wrote:

 Sounds like you should sign off on the first item in the Copyright
 section of http://incubator.apache.org/projects/amber.html as n/a.
 No code was relicensed to the ASF when Amber was created. Instead it
 was a fork of Uni of Newcastle code and that copyright remains on the
 code.

 Hen

 On Mon, Aug 20, 2012 at 1:00 AM, Antonio Sanso asa...@adobe.com wrote:
 Hi Henri,

 thanks for taking care of this.

 IANAL but technically yes I think that the OAuth 2.0 part of Amber can be 
 considered as a fork.

 Before to perform the first release we followed what has been suggested in 
 LEGAL-134.
 Did we miss something? Should we do something more or we can assume this 
 legal issue is over?

 Thanks and regards

 Antonio


 On Aug 12, 2012, at 8:28 PM, Henri Yandell wrote:

 Hi Antonio,

 This is about making sure that all software being contributed to
 Apache is covered by CLAs (continuous contribution) or the software
 license grant (single contribution). Legally it would also be fine to
 fork software under a Category A license, though it's frowned upon
 (ie: the status checkbox doesn't offer it as an option).

 By the look of LEGAL-134, it sounds like Amber started as a fork of
 University of Newcastle code?

 Hen

 On Fri, Jul 13, 2012 at 7:39 AM, Antonio Sanso asa...@adobe.com wrote:
 Hi Henri,

 Amber wise we tracked this in [0].
 Now I am not sure if we can also tick the box.

 Regards

 Antonio

 [0] https://issues.apache.org/jira/browse/LEGAL-134

 On Jul 8, 2012, at 4:22 AM, Henri Yandell wrote:

 The following projects haven't signed off on the copyright checklist 
 item:

 2009-02-09  kato
 2009-02-13  stonehenge
 2009-05-13  socialsite
 2010-05-19  amber
 2010-09-05  nuvem
 2010-11-12  kitty
 2010-11-24  stanbol
 2011-06-13  openofficeorg

 Said checklist item is:

 Check and make sure that the papers that transfer rights to the ASF
 been received. It is only necessary to transfer rights for the
 package, the core code, and any new code produced by the project. 

 How long do we host software without explicitly stating we have these 
 rights?

 Personally I think 1 year is more than enough, even for OpenOffice.

 Note that this list comes from
 https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects

 Hen

 -
 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


 -
 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: Old projects with incomplete copyright diligence

[Henri Yandell]

http://incubator.apache.org/projects/kato.html should have a check mark for:

Check and make sure that the papers that transfer rights to the ASF
been received. It is only necessary to transfer rights for the
package, the core code, and any new code produced by the project. 

Just because it was released doesn't mean that it correctly did that.

Need to confirm that all copyright owners of any pre-Apache code
either signed ICLA/grants with us, or that the source was already
licensed under a category A license.

Hen

On Sun, Aug 12, 2012 at 12:30 PM, Benson Margulies
bimargul...@gmail.com wrote:
 Henri,

 Ant pointed out that Kato released. Where is the signoff you are looking at?

 --benson


 On Sun, Aug 12, 2012 at 2:29 PM, Henri Yandell flame...@gmail.com wrote:
 On Fri, Jul 13, 2012 at 7:17 AM, Kevan Miller kevan.mil...@gmail.com wrote:

 On Jul 7, 2012, at 10:22 PM, Henri Yandell wrote:

 The following projects haven't signed off on the copyright checklist item:

 2009-02-09  kato
 2009-02-13  stonehenge
 2009-05-13  socialsite
 2010-05-19  amber
 2010-09-05  nuvem
 2010-11-12  kitty
 2010-11-24  stanbol
 2011-06-13  openofficeorg

 Said checklist item is:

  Check and make sure that the papers that transfer rights to the ASF
 been received. It is only necessary to transfer rights for the
 package, the core code, and any new code produced by the project. 

 IIRC, there was no code grant/donation for Kitty. So, there was no code 
 grant. If that means I should indicate the 'papers have been received', I 
 can do that.

 Thanks Kevan :)

 I've updated kitty.xml to say n/a rather than a date as that's the
 method that's been used in the past to identify no need for
 grant/donation.

 Hen

 -
 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: Old projects with incomplete copyright diligence

[Henri Yandell]

On Tue, Aug 14, 2012 at 1:48 PM, Jukka Zitting jukka.zitt...@gmail.com wrote:
 Hi,

 On Tuesday, August 14, 2012, Benson Margulies wrote:

 On Tue, Aug 14, 2012 at 3:54 PM, Henri Yandell 
 flame...@gmail.comjavascript:;
 wrote:
  Just because it was released doesn't mean that it correctly did that.
 
  Need to confirm that all copyright owners of any pre-Apache code
  either signed ICLA/grants with us, or that the source was already
  licensed under a category A license.

 I volunteered to deal with all this as an expansion of a Shepherd
 assignment. I confess that I'm feeling a bit whelmed.


 FWIW, here's how I'd approach this:

 * Look at the original Kato proposal (
 http://wiki.apache.org/incubator/KatoProposal) for insight on what
 pre-Apache IP was supposed to be transferred to us.
 * Check the early Kato svn history for commits containing that IP (see
 especially revision 754956,
 http://svn.apache.org/viewvc?view=revisionrevision=754956).
 * Follow the pointers to the relevant records under
 /repos/private/documents to verify that the mentioned paperwork is in place.
 * If it indeed is, mark the IP as cleared on the Kato status page.
 * If it isn't, consider whether the ICLA on file for the committer who
 submitted the IP is sufficient to grant as the rights to keep the code.
 * Based on all the above, make an informed judgement call on whether we can
 keep the code in svn or not.

 I hope this helps! If still needed, I'd be happy to help out in a few weeks
 when I'm back from vacation.

Oops - sorry Benson. I hadn't realized you had as much historical
knowledge as I have :) Let me know if I can help.

Jukka's advice is great :)

Hen

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Amber CLA status [Was: Old projects with incomplete copyright diligence]

[Henri Yandell]

Hi Antonio,

This is about making sure that all software being contributed to
Apache is covered by CLAs (continuous contribution) or the software
license grant (single contribution). Legally it would also be fine to
fork software under a Category A license, though it's frowned upon
(ie: the status checkbox doesn't offer it as an option).

By the look of LEGAL-134, it sounds like Amber started as a fork of
University of Newcastle code?

Hen

On Fri, Jul 13, 2012 at 7:39 AM, Antonio Sanso asa...@adobe.com wrote:
 Hi Henri,

 Amber wise we tracked this in [0].
 Now I am not sure if we can also tick the box.

 Regards

 Antonio

 [0] https://issues.apache.org/jira/browse/LEGAL-134

 On Jul 8, 2012, at 4:22 AM, Henri Yandell wrote:

 The following projects haven't signed off on the copyright checklist item:

 2009-02-09  kato
 2009-02-13  stonehenge
 2009-05-13  socialsite
 2010-05-19  amber
 2010-09-05  nuvem
 2010-11-12  kitty
 2010-11-24  stanbol
 2011-06-13  openofficeorg

 Said checklist item is:

  Check and make sure that the papers that transfer rights to the ASF
 been received. It is only necessary to transfer rights for the
 package, the core code, and any new code produced by the project. 

 How long do we host software without explicitly stating we have these rights?

 Personally I think 1 year is more than enough, even for OpenOffice.

 Note that this list comes from
 https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects

 Hen

 -
 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: Old projects with incomplete copyright diligence

[Henri Yandell]

On Fri, Jul 13, 2012 at 7:17 AM, Kevan Miller kevan.mil...@gmail.com wrote:

 On Jul 7, 2012, at 10:22 PM, Henri Yandell wrote:

 The following projects haven't signed off on the copyright checklist item:

 2009-02-09  kato
 2009-02-13  stonehenge
 2009-05-13  socialsite
 2010-05-19  amber
 2010-09-05  nuvem
 2010-11-12  kitty
 2010-11-24  stanbol
 2011-06-13  openofficeorg

 Said checklist item is:

  Check and make sure that the papers that transfer rights to the ASF
 been received. It is only necessary to transfer rights for the
 package, the core code, and any new code produced by the project. 

 IIRC, there was no code grant/donation for Kitty. So, there was no code 
 grant. If that means I should indicate the 'papers have been received', I can 
 do that.

Thanks Kevan :)

I've updated kitty.xml to say n/a rather than a date as that's the
method that's been used in the past to identify no need for
grant/donation.

Hen

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Old projects with incomplete copyright diligence

[Henri Yandell]

The following projects haven't signed off on the copyright checklist item:

2009-02-09  kato
2009-02-13  stonehenge
2009-05-13  socialsite
2010-05-19  amber
2010-09-05  nuvem
2010-11-12  kitty
2010-11-24  stanbol
2011-06-13  openofficeorg

Said checklist item is:

  Check and make sure that the papers that transfer rights to the ASF
been received. It is only necessary to transfer rights for the
package, the core code, and any new code produced by the project. 

How long do we host software without explicitly stating we have these rights?

Personally I think 1 year is more than enough, even for OpenOffice.

Note that this list comes from
https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects

Hen

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Old projects with incomplete copyright diligence

[Henri Yandell]

Updating status.

On Sat, Jul 7, 2012 at 7:22 PM, Henri Yandell flame...@gmail.com wrote:
 The following projects haven't signed off on the copyright checklist item:

 2009-02-09  kato

Retiring. Source needs deleting(?).

 2009-02-13  stonehenge

Retired. Source needs deleting(?).

 2009-05-13  socialsite

Marked as Dormant (not sure how that differs from Retired). No source
to delete. I'll drop this from my pester list :)

 2010-05-19  amber

Active development.

 2010-09-05  nuvem

Activish (2 months ago).

 2010-11-12  kitty

Activish (3 months ago).

 2010-11-24  stanbol

Active development.

 2011-06-13  openofficeorg

Ross has pinged the list.

---

Hen

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [SITE] Link to board meeting minutes for podling acceptance/graduation

[Henri Yandell]

Useful, but a difficult workflow (assuming the minutes still lag the
meetings by a long way - seems true as the last 3 meetings aren't on
the site yet).

Conjecture, but I would guess that the project finish graduation
before the minutes are published. This means that the Podling members
are no longer interested in the Incubator by the time the link is
available. The Incubator PMC could do it, but I suspect no one is
interested in the ex-podling by that point.

Hen

On Wed, Nov 23, 2011 at 12:19 PM, sebb seb...@gmail.com wrote:
 Just wondering whether it would be useful to add a link to the board
 minutes that establish podlings and create TLPs?

 So for example, Libcloud was established in [1]; this could be added
 to podlings.xml and added as a link in Start Date column in the list
 of podlings [2].

 Similarly for graduated TLP podlings, the End Date could be a link
 to the minutes that established the TLP.

 These be optional fields (probably tags, as the attribute list is
 getting rather long).

 The acceptance link could eventually be mandatory if required, but not
 all podlings graduate or graduate to a TLP.

 [1] 
 http://www.apache.org/foundation/records/minutes/2011/board_minutes_2011_05_19.txt
 [2] http://incubator.apache.org/projects/index.html

 -
 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: Actively retiring projects (was: Incubator Board Report November 2011)

[Henri Yandell]

On Sun, Nov 20, 2011 at 8:11 AM, Luciano Resende luckbr1...@gmail.com wrote:

 Maybe I've had been using a high bar with the podlings I
 mentor/participate. I'll look into graduating couple podlings after I
 come back from Thanks Giving : Apache PhotArk, Apache Wink.

First things first - can you get Wink's copyright status sorted out?
It's not signed off on the status page yet to say that we have the
rights to host the code.

This had better just be a case of no one having updated the right page
given that Wink appears to have been making releases.

Hen

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Actively retiring projects (was: Incubator Board Report November 2011)

[Henri Yandell]

On Wed, Nov 16, 2011 at 12:36 PM, Sam Ruby ru...@intertwingly.net wrote:
 On Tue, Nov 15, 2011 at 11:41 PM, Noel J. Bergman n...@devtech.com wrote:

 We are, however, recognizing that we've had growth issues of our own.  As
 David Crossley pointed out, he made mistakes last month related to the
 Reporting Schedule, and we continue to have issues.  The Incubator is almost
 as big as the rest of the ASF combined.  David posted a plot chart
 reflecting our growth: http://incubator.apache.org/history/

 Excellent plot chart.  As with most plot charts, the end result is a
 Rorschach test.  I'll tell you what I (personally) see in this chart:
 a failure to perform garbage collection.  My personal perspective is
 that incubation shouldn't generally take more than a year.  That
 doesn't mean that there won't be exceptions, and in a few rare cases,
 some that go well beyond that arbitrary time limit, but the point is
 that those should be the exception rather than the rule.

Now that time is freeing up a tiny bit, I need to document a thread
from August that would put pressure on projects who haven't done their
IP handling. I'm less worried about a podling who haven't graduated
after 12 months and more worried about a podling who haven't managed
to get their CLAs right within 3 months. We still have far too many
podlings who haven't signed off on that (first) part of their
incubation.

So +1 in sentiment, but a different focus.

Hen

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Latest copyright sign-off status [Was: Podlings needing copyright sign-off]

[Henri Yandell]

On Wed, Nov 16, 2011 at 12:16 AM, Robert Burrell Donkin
robertburrelldon...@gmail.com wrote:
 On Wed, Nov 16, 2011 at 8:14 AM, Robert Burrell Donkin
 robertburrelldon...@gmail.com wrote:
 On Fri, Nov 11, 2011 at 12:14 AM, Henri Yandell flame...@gmail.com wrote:

 snip

 2009-02-09  kato

 I'm comfortable that this is safe enough copyright-wise. I would
 prefer the podling community to do the checking themselves but it's
 stalled until the JCR is sorted out.

 There is occasional interest in the codebase but work by the original
 team seems to be halted until standards issues are sorted out.

 Maybe we need a stalled status, perhaps allowing new contributors to
 boot-strap

You're a mentor, so if you're comfortable that the copyright rights
have been licensed (or there's nothing to license) then go ahead and
update the status page :)

Hen

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Latest copyright sign-off status [Was: Podlings needing copyright sign-off]

[Henri Yandell]

You should define 'very small' for Joao and work with legal-discuss
and the Incubator PMC to decide if the item can be signed off or not.

[me=bean counter who points to a field not being signed off :) ]

Hen

On Wed, Nov 16, 2011 at 4:53 AM, Jörn Kottmann kottm...@gmail.com wrote:
 Hello,

 can OpenNLP be signed-off?

 OpenNLP was hosted for some years over at SourceForge before
 we moved to the Apache Incubator.
 Over at SourceForge a couple of people worked on it.

 Most SourceForge committers are also committers here, they
 all signed an ICLA, these are:

 - Thilo Goetz
 - Jörn Kottmann
 - Jason Baldridge
 - James Kosin
 - William Silvia
 - Tom Morton

 The following people didn't maintain their commit rights:

 - Gann Bierner
 - Eric Friedman
 - Joao Cavalcanti

 Of these three people Gann Bierner and Eric Friedman signed
 the software grant. Joao Cavalcanti didn't because the amount of his
 contribution
 was very small.

 Is there anything else what we need to do to get the copyright item signed
 off?

 Thanks,
 Jörn

 On 11/11/11 1:14 AM, Henri Yandell wrote:

 Updating this, half of the items without sign-off in July are now
 signed off. I've updated the list below (though I've not yet added new
 PMCs since June).

 Here's the previous email:

 On Thu, Jul 7, 2011 at 7:20 PM, Henri Yandellflame...@gmail.com  wrote:

 Here's a list of the projects in the Incubator who need to sign off
 their copyright item; namely:

 Check and make sure that the papers that transfer rights to the ASF
 been received.
  It is only necessary to transfer rights for the package, the core
 code, and any
  new code produced by the project.  

 Here's the latest list:

 2008-09-29  olio
 2009-02-09  kato
 2009-02-13  stonehenge
 2009-05-08  ace
 2009-05-13  socialsite
 2009-06-25  wink
 2009-11-08  hise
 2010-01-27  manifoldcf
 2010-05-19  amber
 2010-05-24  zetacomponents
 2010-09-05  nuvem
 2010-11-02  celix
 2010-11-12  kitty
 2010-11-24  stanbol
 2010-12-02  jena
 2010-12-02  opennlp
 2011-06-13  openofficeorg

 Hen

 -
 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: Adobe revises Flex's future ... at the Apache Software Foundation - The H Open Source: News and Features

[Henri Yandell]

Looking forward to hearing how this isn't a code dump :)

Hen

On Wed, Nov 16, 2011 at 7:26 PM, Greg Stein gst...@gmail.com wrote:
 Heads up on some incoming proposals.

 http://www.h-online.com/open/news/item/Adobe-revises-Flex-s-future-at-the-Apache-Software-Foundation-1380242.html


 NOTE: and yes, Adobe is doing this right: they say they are crafting
 *proposals*. All is good here; I'm just giving some heads-up since I
 hadn't seen it on this list. See some more in the update section
 here:
  http://blogs.adobe.com/flex/2011/11/your-questions-about-flex.html


 Cheers,
 -g

 -
 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] Retire Olio [Was: Retire Olio?]

[Henri Yandell]

5 +1s to retire Olio.

Happily the IP did get signed off on, so no need to remove the source
code from SVN.

I'll go ahead and update the Incubator site to indicate that the
project is now retired.

Hen

On Thu, Nov 10, 2011 at 4:17 PM, Henri Yandell flame...@gmail.com wrote:
 Coming back to this.

 It unfortunately seems that there's no (even optimistic) expectation
 that Olio will graduate.

 So, voting:

 [ ] +1
 [ ] -1, no because...

 Hen

 On Tue, Aug 16, 2011 at 11:27 PM, William A. Rowe Jr.
 wr...@rowe-clan.net wrote:
 On 8/17/2011 12:47 AM, Henri Yandell wrote:
 On Tue, Aug 16, 2011 at 10:40 PM, William A. Rowe Jr.
 wr...@rowe-clan.net wrote:
 On 8/17/2011 12:37 AM, Henri Yandell wrote:
 The copyright item isn't signed off at
 https://incubator.apache.org/projects/olio.html.

 So would need to delete the code (assuming a successful retirement vote).

 Where are the mentors?

 Wondering how conflicted-providence IP would hit svn in the first place.

 Digging a bit:

 Initial Olio code dump from Sun by clr. r700550
 Added rails webapp by wsobel. r705828
 Adding Web20Emulator by sheetal. r706388

 There were other large adds, but those were the three initial big ones.

 I don't see any software grants relating to Olio. I see lots in the
 board reports about struggling to get committer diversity because the
 committers were at 3 corporations.

 I don't believe that conflicted-providence IP would have hit svn, yet
 if it's not signed off and (assuming no one steps up to say otherwise)
 I think delete is the only option we have.

 Agreed.  Unless the mentors can check off that checkbox prior to the
 project's dormancy, svn will need to be rm'ed.


 -
 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: Latest copyright sign-off status [Was: Podlings needing copyright sign-off]

[Henri Yandell]

On Sun, Nov 13, 2011 at 9:06 AM, Tommaso Teofili
tommaso.teof...@gmail.com wrote:
 2011/11/11 Henri Yandell flame...@gmail.com

 Updating this, half of the items without sign-off in July are now
 signed off. I've updated the list below (though I've not yet added new
 PMCs since June).

 Here's the previous email:

 On Thu, Jul 7, 2011 at 7:20 PM, Henri Yandell flame...@gmail.com wrote:
  Here's a list of the projects in the Incubator who need to sign off
  their copyright item; namely:
 
  Check and make sure that the papers that transfer rights to the ASF
  been received.
   It is only necessary to transfer rights for the package, the core
  code, and any
   new code produced by the project.  

 Here's the latest list:

 2008-09-29  olio
 2009-02-09  kato
 2009-02-13  stonehenge
 2009-05-08  ace
 2009-05-13  socialsite
 2009-06-25  wink
 2009-11-08  hise
 2010-01-27  manifoldcf


 in the recorded grants file I can see:

 Software grant from Metacarta, Inc.
  ...

 and, as far as I know, this is the required paperwork for ManifoldCF
 (previously knwon as Lucene Connectors Framework).

 Please let me know if I'm missing something.

Need to update your status page to indicate that:

  http://incubator.apache.org/projects/manifoldcf.html

Hen

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Retire Olio [Was: Retire Olio?]

[Henri Yandell]

Thanks Craig - nice to not have to delete the code :)

I've updated the site.

Hen

On Thu, Nov 10, 2011 at 5:58 PM, Craig L Russell
craig.russ...@oracle.com wrote:
 +1 to retire Olio.

 The code grant for olio was signed and recorded
 (https://svn.apache.org/repos/private/documents/cclas/sun-microsystems-olio.pdf
 ) but the checkbox wasn't checked in the podling status.

 Making it read only would be the proper course of action.

 Craig

 On Nov 10, 2011, at 4:17 PM, Henri Yandell wrote:

 Coming back to this.

 It unfortunately seems that there's no (even optimistic) expectation
 that Olio will graduate.

 So, voting:

 [ ] +1
 [ ] -1, no because...

 Hen

 On Tue, Aug 16, 2011 at 11:27 PM, William A. Rowe Jr.
 wr...@rowe-clan.net wrote:

 On 8/17/2011 12:47 AM, Henri Yandell wrote:

 On Tue, Aug 16, 2011 at 10:40 PM, William A. Rowe Jr.
 wr...@rowe-clan.net wrote:

 On 8/17/2011 12:37 AM, Henri Yandell wrote:

 The copyright item isn't signed off at
 https://incubator.apache.org/projects/olio.html.

 So would need to delete the code (assuming a successful retirement
 vote).

 Where are the mentors?

 Wondering how conflicted-providence IP would hit svn in the first
 place.

 Digging a bit:

 Initial Olio code dump from Sun by clr. r700550
 Added rails webapp by wsobel. r705828
 Adding Web20Emulator by sheetal. r706388

 There were other large adds, but those were the three initial big ones.

 I don't see any software grants relating to Olio. I see lots in the
 board reports about struggling to get committer diversity because the
 committers were at 3 corporations.

 I don't believe that conflicted-providence IP would have hit svn, yet
 if it's not signed off and (assuming no one steps up to say otherwise)
 I think delete is the only option we have.

 Agreed.  Unless the mentors can check off that checkbox prior to the
 project's dormancy, svn will need to be rm'ed.


 -
 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


 Craig L Russell
 Architect, Oracle
 http://db.apache.org/jdo
 408 276-5638 mailto:craig.russ...@oracle.com
 P.S. A good JDO? O, Gasp!


 -
 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

Latest copyright sign-off status [Was: Podlings needing copyright sign-off]

[Henri Yandell]

Updating this, half of the items without sign-off in July are now
signed off. I've updated the list below (though I've not yet added new
PMCs since June).

Here's the previous email:

On Thu, Jul 7, 2011 at 7:20 PM, Henri Yandell flame...@gmail.com wrote:
 Here's a list of the projects in the Incubator who need to sign off
 their copyright item; namely:

 Check and make sure that the papers that transfer rights to the ASF
 been received.
  It is only necessary to transfer rights for the package, the core
 code, and any
  new code produced by the project.  

Here's the latest list:

2008-09-29  olio
2009-02-09  kato
2009-02-13  stonehenge
2009-05-08  ace
2009-05-13  socialsite
2009-06-25  wink
2009-11-08  hise
2010-01-27  manifoldcf
2010-05-19  amber
2010-05-24  zetacomponents
2010-09-05  nuvem
2010-11-02  celix
2010-11-12  kitty
2010-11-24  stanbol
2010-12-02  jena
2010-12-02  opennlp
2011-06-13  openofficeorg

Hen

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[VOTE] Retire Olio [Was: Retire Olio?]

[Henri Yandell]

Coming back to this.

It unfortunately seems that there's no (even optimistic) expectation
that Olio will graduate.

So, voting:

[ ] +1
[ ] -1, no because...

Hen

On Tue, Aug 16, 2011 at 11:27 PM, William A. Rowe Jr.
wr...@rowe-clan.net wrote:
 On 8/17/2011 12:47 AM, Henri Yandell wrote:
 On Tue, Aug 16, 2011 at 10:40 PM, William A. Rowe Jr.
 wr...@rowe-clan.net wrote:
 On 8/17/2011 12:37 AM, Henri Yandell wrote:
 The copyright item isn't signed off at
 https://incubator.apache.org/projects/olio.html.

 So would need to delete the code (assuming a successful retirement vote).

 Where are the mentors?

 Wondering how conflicted-providence IP would hit svn in the first place.

 Digging a bit:

 Initial Olio code dump from Sun by clr. r700550
 Added rails webapp by wsobel. r705828
 Adding Web20Emulator by sheetal. r706388

 There were other large adds, but those were the three initial big ones.

 I don't see any software grants relating to Olio. I see lots in the
 board reports about struggling to get committer diversity because the
 committers were at 3 corporations.

 I don't believe that conflicted-providence IP would have hit svn, yet
 if it's not signed off and (assuming no one steps up to say otherwise)
 I think delete is the only option we have.

 Agreed.  Unless the mentors can check off that checkbox prior to the
 project's dormancy, svn will need to be rm'ed.


 -
 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: svn commit: r1163489 - in /incubator/public/trunk: clutch.pkl site-author/clutch.txt site-author/clutch.xml site-author/report_due_1.txt site-publish/clutch.html site-publish/clutch.txt site-publi

[Henri Yandell]

Thanks. I was assuming it was related to the removing it from the navbar.

Hen

On Wed, Aug 31, 2011 at 4:59 PM, sebb seb...@gmail.com wrote:
 On 31 August 2011 15:33, sebb seb...@gmail.com wrote:
 On 31 August 2011 06:39,  bay...@apache.org wrote:
 Author: bayard
 Date: Wed Aug 31 05:39:59 2011
 New Revision: 1163489

 URL: http://svn.apache.org/viewvc?rev=1163489view=rev
 Log:
 Reran clutch. Updated OGNL.

 Modified:
    incubator/public/trunk/clutch.pkl
    incubator/public/trunk/site-author/clutch.txt
    incubator/public/trunk/site-author/clutch.xml
    incubator/public/trunk/site-author/report_due_1.txt
    incubator/public/trunk/site-publish/clutch.html
    incubator/public/trunk/site-publish/clutch.txt
    incubator/public/trunk/site-publish/report_due_1.txt

 Modified: incubator/public/trunk/clutch.pkl
 URL: 
 http://svn.apache.org/viewvc/incubator/public/trunk/clutch.pkl?rev=1163489r1=1163488r2=1163489view=diff
 ==
 Binary files - no diff available.

 Modified: incubator/public/trunk/site-author/clutch.txt
 URL: 
 http://svn.apache.org/viewvc/incubator/public/trunk/site-author/clutch.txt?rev=1163489r1=1163488r2=1163489view=diff
 ==
 --- incubator/public/trunk/site-author/clutch.txt (original)
 +++ incubator/public/trunk/site-author/clutch.txt Wed Aug 31 05:39:59 2011
 @@ -36,7 +36,7 @@ mrunit,MRUnit,Incubator
  npanday,NPanday,Incubator
  nuvem,Nuvem,Incubator
  odftoolkit,ODFToolkit,Incubator
 -ognl,OGNL,Incubator
 +ognl,OGNL,? not known
  olio,Olio,Incubator
  oozie,Oozie,Incubator
  opennlp,OpenNLP,Incubator

 OGNL looks wrong - possibly because

 http://wiki.apache.org/incubator/ReportingSchedule

 has not been updated to remove OGNL?


 I've now removed OGNL from the schedule.

 -
 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: Websites of retired podlings (was Re: Retired podlings with RW SVN access)

[Henri Yandell]

On Sat, Aug 20, 2011 at 7:06 PM, Marvin Humphrey mar...@rectangular.com wrote:
 On Sat, Aug 20, 2011 at 05:25:00PM -0400, Benson Margulies wrote:
  On Sat, Aug 20, 2011 at 02:59:33PM +0300, Daniel Shahaf wrote:
   Gavin McDonald wrote on Sat, Aug 20, 2011 at 16:35:47 +1000:
The retirement guide [1] makes no mention of removing podling
websites but I think they should all be removed at retirement,
thoughts?
  
   This doesn't need to be on private@...
 
  Good catch, Daniel.  My preference would be to avoid erasing podling web
  presences on retirement,

 If an RO svn is retained, some sort of web presence explaining it
 makes sense to me. But I agree that a pseudo-active-project web site
 is not the right sort of web presence.

 Yes, I also agree that a site which misleads visitors into thinking that a
 retired podling is active is not desirable.

 When a top-level project enters the Attic, its website gets updated to reflect
 the fact that it has been retired.  For instance, all of Hivemind's web pages
 have a big red banner alerting visitors to the project's status:

    http://hivemind.apache.org/
    http://hivemind.apache.org/download.html

 Provided that someone is willing to do that work, that there is zero ongoing
 maintenance burden, and that there are no practical or legal difficulties, I
 think something similar would also be OK for a retired podling -- however,
 that's not necessarily my preferred approach.

Btw, the work is a search and replace on the body...  tag. I
generally find one that works on the site content but fails on javadoc
(as inserting a header into a frame system is painful).

Hen

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org