Re: HTTPS project sites

[John D. Ament]

Christopher,

No need to worry - thanks for clarifying!

Just to close the loop on this, did you contact the HTrace team?  Each
podling has their own means for contact.  HTrace's can be found on
http://htrace.incubator.apache.org/mail-lists.html and I would recommend
their "Developer List" to let them know.

John

On Sat, Jan 14, 2017 at 2:31 PM Christopher  wrote:

> Sorry if I caused confusion. I'm not requesting assistance... I'm just
> trying to make the community aware of the issue, and suggesting fixes. The
> HTrace page was just one example that didn't work on https.
>
> On Sat, Jan 14, 2017 at 7:59 AM John D. Ament 
> wrote:
>
> > I guess this is my confusion as well (hence my prior response).  it
> sounded
> > like from a technical standpoint he wasn't sure how to make it protocol
> > agnostic.
> >
> > RE HTTPS everywhere.  The only place that doesn't support HTTPS are the
> > staging URLs via CMS.  Other than that, all other resources support
> HTTPS.
> >
> > John
> >
> > On Sat, Jan 14, 2017 at 4:02 AM Evan Hughes 
> > wrote:
> >
> > > I see no technical reason why these external libraries cant be included
> > > with https instead of http. I would rather see https:// instead of //
> as
> > > //
> > > can cause conflict when serving from a local file system as it'll
> assume
> > > file://.
> > >
> > > Though I'm not sure what your proposing Christopher other than a issue
> > that
> > > needs to be added to htrace's jira page.
> > >
> > > ~ Evan
> > >
> > > On Sat, 14 Jan 2017 at 16:14 Christopher  wrote:
> > >
> > > > While I personally would prefer ASF switch everything over to HTTPS
> > only,
> > > > the main concern here is that projects may only be testing their
> sites
> > > with
> > > > HTTP, and they may not realize that their site breaks for visitors
> > using
> > > > HTTPS. Using "https://;, or simply "//", instead of "http://; for
> > > > javascript/css/other resources is a quick fix for most project sites.
> > > That
> > > > should get things working, regardless of whether their visitors are
> > > > visiting the project site with HTTP or HTTPS.
> > > >
> > > > On Sat, Jan 14, 2017 at 12:42 AM Henri Yandell 
> > > wrote:
> > > >
> > > > > 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<
> https://ngrok.com/usage>
> > > and
> > > > > > > mitmproxy..my personal preference is
> > Squid
> > > > > > > [
> > > > > > > 

Re: HTTPS project sites

[Christopher]

Sorry if I caused confusion. I'm not requesting assistance... I'm just
trying to make the community aware of the issue, and suggesting fixes. The
HTrace page was just one example that didn't work on https.

On Sat, Jan 14, 2017 at 7:59 AM John D. Ament  wrote:

> I guess this is my confusion as well (hence my prior response).  it sounded
> like from a technical standpoint he wasn't sure how to make it protocol
> agnostic.
>
> RE HTTPS everywhere.  The only place that doesn't support HTTPS are the
> staging URLs via CMS.  Other than that, all other resources support HTTPS.
>
> John
>
> On Sat, Jan 14, 2017 at 4:02 AM Evan Hughes 
> wrote:
>
> > I see no technical reason why these external libraries cant be included
> > with https instead of http. I would rather see https:// instead of // as
> > //
> > can cause conflict when serving from a local file system as it'll assume
> > file://.
> >
> > Though I'm not sure what your proposing Christopher other than a issue
> that
> > needs to be added to htrace's jira page.
> >
> > ~ Evan
> >
> > On Sat, 14 Jan 2017 at 16:14 Christopher  wrote:
> >
> > > While I personally would prefer ASF switch everything over to HTTPS
> only,
> > > the main concern here is that projects may only be testing their sites
> > with
> > > HTTP, and they may not realize that their site breaks for visitors
> using
> > > HTTPS. Using "https://;, or simply "//", instead of "http://; for
> > > javascript/css/other resources is a quick fix for most project sites.
> > That
> > > should get things working, regardless of whether their visitors are
> > > visiting the project site with HTTP or HTTPS.
> > >
> > > On Sat, Jan 14, 2017 at 12:42 AM Henri Yandell 
> > wrote:
> > >
> > > > 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
> > 

Re: IP Clearance terms

[John D. Ament]

On Sat, Jan 14, 2017 at 12:51 AM Henri Yandell  wrote:

> 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?
>

No.  There's a box on the page "This form is not for new projects."  We
rely on the SGA to identify the initial source and mentors to review what
gets pushed into the repo.  I'll point out two projects where this process
has been problematic:

- Groovy
- MADLib

John


>
>
> > - 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: HTTPS project sites

[John D. Ament]

I guess this is my confusion as well (hence my prior response).  it sounded
like from a technical standpoint he wasn't sure how to make it protocol
agnostic.

RE HTTPS everywhere.  The only place that doesn't support HTTPS are the
staging URLs via CMS.  Other than that, all other resources support HTTPS.

John

On Sat, Jan 14, 2017 at 4:02 AM Evan Hughes  wrote:

> I see no technical reason why these external libraries cant be included
> with https instead of http. I would rather see https:// instead of // as
> //
> can cause conflict when serving from a local file system as it'll assume
> file://.
>
> Though I'm not sure what your proposing Christopher other than a issue that
> needs to be added to htrace's jira page.
>
> ~ Evan
>
> On Sat, 14 Jan 2017 at 16:14 Christopher  wrote:
>
> > While I personally would prefer ASF switch everything over to HTTPS only,
> > the main concern here is that projects may only be testing their sites
> with
> > HTTP, and they may not realize that their site breaks for visitors using
> > HTTPS. Using "https://;, or simply "//", instead of "http://; for
> > javascript/css/other resources is a quick fix for most project sites.
> That
> > should get things working, regardless of whether their visitors are
> > visiting the project site with HTTP or HTTPS.
> >
> > On Sat, Jan 14, 2017 at 12:42 AM Henri Yandell 
> wrote:
> >
> > > 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 <
> mgai...@hotmail.com>
> > > > > 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 

Re: HTTPS project sites

[Evan Hughes]

I see no technical reason why these external libraries cant be included
with https instead of http. I would rather see https:// instead of // as //
can cause conflict when serving from a local file system as it'll assume
file://.

Though I'm not sure what your proposing Christopher other than a issue that
needs to be added to htrace's jira page.

~ Evan

On Sat, 14 Jan 2017 at 16:14 Christopher  wrote:

> While I personally would prefer ASF switch everything over to HTTPS only,
> the main concern here is that projects may only be testing their sites with
> HTTP, and they may not realize that their site breaks for visitors using
> HTTPS. Using "https://;, or simply "//", instead of "http://; for
> javascript/css/other resources is a quick fix for most project sites. That
> should get things working, regardless of whether their visitors are
> visiting the project site with HTTP or HTTPS.
>
> On Sat, Jan 14, 2017 at 12:42 AM Henri Yandell  wrote:
>
> > 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<
> > > > 

Re: [DISCUSS] Proposing MXNet for the Apache Incubator

[YiZhi Liu]

Confirmed, and please update my affiliation to 'Qihoo 360'. Thanks.

2017-01-14 16:08 GMT+08:00 梁德澎 :
> 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 :
>
>> 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  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 

Re: [DISCUSS] Proposing MXNet for the Apache Incubator

[梁德澎]

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 :

> 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  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 ==
> >
> > ===