Re: HTTPS project sites

[Christopher]

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

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  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 contributors within both industry and academia. We would
> like to follow ASF meritocratic principles to encourage more developers to
> contribute in this project. We know that only active and committed
> developers from a diverse set of backgrounds can make MXNet a successful
> project.  We are also improving the documentation and 

Re: [DISCUSS] Proposing MXNet for the Apache Incubator

[Henri Yandell]

Added :)

On Fri, Jan 13, 2017 at 3:48 AM, Zhang Jian 
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  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 

Re: [DISCUSS] Proposing MXNet for the Apache Incubator

[Henri Yandell]

Thanks Yifeng :) Added.

On Fri, Jan 13, 2017 at 3:33 AM, yifeng.geng  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  wrote:
> > 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>
> > >>
> > >>
> >
> -
> 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

[DRAFT] Incubator PMC Board Report - January 2017

[John D. Ament]

All,

Below is the current draft.  I missed in the first report that two podlings
were missing sign offs - Spot and ODF.  Please review the report and make
changes.

Incubator PMC report for January 2017

The Apache Incubator is the entry path into the ASF for projects and
codebases wishing to become part of the Foundation's efforts.

There are presently 64 podlings incubating.  We had one new podling join.
No
changes in PMC membership.

* Community

  New IPMC members:

  - None

  People who left the IPMC:

  - None

* New Podlings

  - Griffin

* Graduations

  The board has motions for the following:

  - Ranger

* Releases

  The following releases entered distribution during the month of
  December:

  - Apache Mynewt1.0.0-b1-incubating  2016-12-12
  - Apache Edgent1.0.0-incubating 2016-12-15
  - Apache Tephra0.10.0-incubating2016-12-15
  - Apache Fineract  0.5.0-incubating 2016-12-22
  - Apache Streams   0.4.1-incubating 2016-12-26
  - Apache Guacamole 0.9.10-incubating2016-12-29


* IP Clearance

  - None

* Legal / Trademarks

  - The process for picking a new incubator logo has begun, we're expecting
to
complete it in April.  Thanks to Sally for picking up the CFP!
  - Incubator documentation updates are in progress, we are starting with
release management then will move into roles & responsibilities.

* Infrastructure

  - No issues, though its suspected some status on github as master for
OpenWhisk may be expected.

* Miscellaneous

  - N/A

* Credits

  - Report Manager: John D. Ament

 Summary of podling reports 

* Still getting started at the Incubator

  - NetBeans
  - RocketMQ
  - Traffic Control
  - Weex

* Not yet ready to graduate

  No release:

  - Annotator
  - MADlib
  - ODF Toolkit

  Community growth:

  - Gossip
  - Horn
  - Juneau
  - Mynewt

* Ready to graduate

  The Board has motions for the following:

  - Ranger

  The following appear to be close from maturity model:

  - Airflow
  - BatchEE
  - FreeMarker
  - Metron

  Still waiting on sign off

  - ODF Toolkit
  - Spot

* Did not report, expected next month

  - DataFu
  - Milagro
  - SensSoft

--
   Table of Contents
Airflow
Annotator
BatchEE
FreeMarker
Gossip
HAWQ
Hivemall
HORN
Juneau
MADlib
Metron
Mynewt
NetBeans
ODF Toolkit
OpenWhisk
RocketMQ
Rya
Spot
Traffic Control
Weex

--



Airflow

Airflow is a workflow automation and scheduling system that can be used to
author and manage data pipelines.

Airflow has been incubating since 2016-03-31.

Three most important issues to address in the move towards graduation:

  1. Getting an Apache release out
  2.
  3.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

  None

How has the community developed since the last report?

  1. We elected 1 new PPMC Member/Committer : Alex Van Boxel a.k.a.
 alexvanboxel
  2. Since our last podling report 3 months ago (i.e. between Oct 4 and Dec
 31, inclusive), we grew our contributors from 191 to 224
  3. Since our last podling report 3 months ago (i.e. between Oct 4 and Dec
 31, inclusive), we resolved 202 pull requests (currently at 1263 closed
 PRs)
  4. One meet-up, hosted at WePay, was held by the community
  5. Since being accepted into the incubator, the number of companies
 officially using Apache Airflow has risen from 30 to 74

How has the project developed since the last report?

  See above

Date of last release:

  None.  First ASF release currently being discussed.

When were the last committers or PPMC members elected?

  As mentioned on

https://cwiki.apache.org/confluence/display/AIRFLOW/Announcements#Announcements-Nov28,2016
,
  Alex Van Boxel joined the Apache Airflow PPMC/Committer group.

Signed-off-by:

  [X](airflow) Chris Nauroth
  [x](airflow) Hitesh Shah
  [ ](airflow) Jakob Homan


Annotator

Annotator provides annotation enabling code for browsers, servers, and
humans.

Annotator has been incubating since 2016-08-30.

Three most important issues to address in the move towards graduation:

  1. Publish a project roadmap to guide us towards a first release
  2. Achieve active development cadence
  3. Improve project description and clarify purpose on the web site

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

  Code contributions at Apache have not yet begun, although the community is
  coalescing.

How has the community developed since the last report?

  One (1) new contributor has expressed interest on the mailing list.

How has the project developed since the last report?

  The initial website is up and all repositories have been created.

Date of last release:

  None

When were the last committers or PPMC members elected?

  None since start 

Re: HTTPS project sites

[John D. Ament]

Christopher,

You can skip the protocol portion of the URL, and only include //

http://stackoverflow.com/questions/550038/is-it-valid-to-replace-http-with-in-a-script-src-http

John

On Fri, Jan 13, 2017 at 12:34 PM Christopher  wrote:

> 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/).
>
> This appears to be caused by Chrome being a bit aggressive about not
> loading scripts from HTTP sources when the page itself is loaded with
> HTTPS.
>
> Projects may wish to check their sites to ensure that their javascript/css
> resources are loading correctly when using HTTPS.
>
> --
> Christopher
>

Re: HTTPS project sites

[Christopher]

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
> framework for distributed tracing. It can be used with both standalone
> applications and libraries.
>
>
>
> > 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.
> >
> >
> >
> >
> > This appears to be caused by Chrome being a bit aggressive about not
> > loading scripts from HTTP sources when the page itself is loaded with
> > HTTPS.
> >
> > Projects may wish to check their sites to ensure that their
> 

Re: HTTPS project sites

[Martin Gainty]

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]

html - How to allow http content within an iframe on a 
...
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
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
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 framework 
for distributed tracing. It can be used with both standalone applications and 
libraries.



> 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.
>
>
>
>
> This appears to be caused by Chrome being a bit aggressive about not
> loading scripts from HTTP sources when the page itself is loaded with
> HTTPS.
>
> Projects may wish to check their sites to ensure that their javascript/css
> resources are loading correctly when using HTTPS.
>
> --
> Christopher
>
--
Christopher

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

[Chip Senkbeil]

Please vote on releasing the following candidate as Apache Toree
(incubating) version 0.1.0.

A vote on this release has passed within the Toree PPMC.

PPMC vote result thread:
https://lists.apache.org/thread.html/5589e9b729333b0d95ccea639fcacf03fdc3d9480aaeb8e80399ad35@


PPMC vote thread:
https://lists.apache.org/thread.html/493874de453d9ccbdbc3aecc2f527dea6af82d657104732d726e07f9@


The tag to be voted on is v0.1.0-rc4
(1d526954ecaba1d5dc0f40ec555dd598b2b11df7), located here:
https://github.com/apache/incubator-toree/commit/1d526954ecaba1d5dc0f40ec555dd598b2b11df7

All distribution packages, including signatures, digests, etc. can be found
at:
https://dist.apache.org/repos/dist/dev/incubator/toree/0.1.0/rc4/

Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/chipsenkbeil.asc

The list of keys associated with Toree is available at:
https://people.apache.org/keys/group/toree.asc

Staging artifacts can be found at:
https://repository.apache.org/content/repositories/orgapachetoree-1002/

Please vote on releasing this package as Apache Toree 0.1.0-incubating!

The vote is open for 72 hours - until Monday, January 16, at 22:43 UTC -
and passes if a majority of at least 3 +1 IPMC votes are cast.

[ ] +1 Release this package as Apache Toree 0.1.0-incubating
[ ] -1 Do not release this package because ...

To learn more about Apache Toree, please see
http://toree.incubator.apache.org/

Re: HTTPS project sites

[Christopher]

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.

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.
>
>
> ?
>
> 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.
>
>
>
>
> This appears to be caused by Chrome being a bit aggressive about not
> loading scripts from HTTP sources when the page itself is loaded with
> HTTPS.
>
> Projects may wish to check their sites to ensure that their javascript/css
> resources are loading correctly when using HTTPS.
>
> --
> Christopher
>
-- 
Christopher

Re: HTTPS project sites

[Martin Gainty]

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




This appears to be caused by Chrome being a bit aggressive about not
loading scripts from HTTP sources when the page itself is loaded with HTTPS.

Projects may wish to check their sites to ensure that their javascript/css
resources are loading correctly when using HTTPS.

--
Christopher

HTTPS project sites

[Christopher]

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/).

This appears to be caused by Chrome being a bit aggressive about not
loading scripts from HTTP sources when the page itself is loaded with HTTPS.

Projects may wish to check their sites to ensure that their javascript/css
resources are loading correctly when using HTTPS.

-- 
Christopher

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

[Velmurugan Periasamy]

Incubator PMC:

Apache Ranger community has voted on and approved a proposal to release Apache 
Ranger 0.6.3 (incubating). 

[VOTE RESULT] thread:
   
https://lists.apache.org/thread.html/20eac9a410a41eb1c78fbb8bc181d593a1d1500c5a771b50c9a0caa9@%3Cdev.ranger.apache.org%3E

Apache ranger-0.6.3-rc1 release candidate is now available with the following 
artifacts up for IPMC vote. 

I kindly request that the Incubator PMC members review and vote on this 
incubator release.

Git tag for the release:
  https://github.com/apache/incubator-ranger/tree/ranger-0.6.3-rc1  (last 
commit id :  86b606571938658101886c0473701f95da031300)
Sources for the release:
  
https://dist.apache.org/repos/dist/dev/incubator/ranger/0.6.3-incubating-rc1/apache-ranger-incubating-0.6.3.tar.gz

Source release verification:
PGP Signature:  
  
https://dist.apache.org/repos/dist/dev/incubator/ranger/0.6.3-incubating-rc1/apache-ranger-incubating-0.6.3.tar.gz.asc
 
MD5/SHA  Hash:
  
https://dist.apache.org/repos/dist/dev/incubator/ranger/0.6.3-incubating-rc1/apache-ranger-incubating-0.6.3.tar.gz.mds
 

Keys to verify the signature of the release artifact are available at:
  https://people.apache.org/keys/group/ranger.asc

Release Notes:
   
https://cwiki.apache.org/confluence/display/RANGER/Apache+Ranger+0.6.3+-+Release+Notes
Build verification steps can be found at:
   http://ranger.incubator.apache.org/quick_start_guide.html

The vote will be open for at least 72 hours or until necessary number of votes 
are reached.
[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)

Here is my +1 (non binding).

Thank you,
Vel
-
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

[Zhang Jian]

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  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 contributors within both industry and academia. We would
> like to follow ASF meritocratic principles to encourage more developers to
> contribute in this project. We know that only active and committed
> developers from a diverse set of backgrounds can make MXNet a successful
> project.  We are also 

Re: [DISCUSS] Proposing MXNet for the Apache Incubator

[yifeng . geng]

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  wrote: 
> 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> 
> >> 
> >> 
> 
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: IP Clearance terms

[John D. Ament]

On Fri, Jan 13, 2017 at 12:36 AM Henri Yandell  wrote:

> 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?
>
>
Go for it.  IP Clearance is way down on my list because:

- Its not usual for a podling to receive a subsequent donation.
- I hate that the IPMC is responsible for all TLPs IP Clearance.

John


> Thanks,
>
> Hen
>

[jira] [Updated] (INCUBATOR-147) Incubator Logo 1 "Block" by claasreimer (Nœrdisch GmbH)

[Claas Reimer (Noerdisch GmbH) (JIRA)]

 [ 
https://issues.apache.org/jira/browse/INCUBATOR-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claas Reimer (Noerdisch GmbH) updated INCUBATOR-147:

Description: The concept V1 "Block"  by Claas Reimer, 
claas.rei...@noerdisch.de represents the intention of growing and expanding for 
projects visualized by several connected squares. Several colors represent 
different influences or topics which come together for building a strong unit.  
(was: The concept V1 "Block"  by Claas Reimer, claas.rei...@noerdisch.de 
represents the intention of growing and expanding for projects visualized by 
several connected squares. Several colors represent different influences or 
topics which come together to build a strong unit.)

> Incubator Logo 1 "Block" by claasreimer (Nœrdisch GmbH)
> ---
>
> Key: INCUBATOR-147
> URL: https://issues.apache.org/jira/browse/INCUBATOR-147
> Project: Incubator
>  Issue Type: Task
>  Components: LogoSubmission
>Reporter: Claas Reimer (Noerdisch GmbH)
> Attachments: logo-1_block_apache-incubator_claasreimer-noerdisch.pdf, 
> logo-1_block_apache-incubator_claasreimer-noerdisch.png
>
>
> The concept V1 "Block"  by Claas Reimer, claas.rei...@noerdisch.de represents 
> the intention of growing and expanding for projects visualized by several 
> connected squares. Several colors represent different influences or topics 
> which come together for building a strong unit.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Updated] (INCUBATOR-147) Incubator Logo 1 "Block" by claasreimer (Nœrdisch GmbH)

[Claas Reimer (Noerdisch GmbH) (JIRA)]

 [ 
https://issues.apache.org/jira/browse/INCUBATOR-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claas Reimer (Noerdisch GmbH) updated INCUBATOR-147:

Description: The concept V1 "Block"  by Claas Reimer, 
claas.rei...@noerdisch.de represents the intention of growing and expanding for 
projects visualized by several connected squares. Several colors represent 
different influences or topics which come together to build a strong unit.  
(was: The concept V1 "Block"  by Claas Reimer, claas.rei...@noerdisch.de 
represents the intention of growing and expanding for projects visualized by 
several connected squares.)

> Incubator Logo 1 "Block" by claasreimer (Nœrdisch GmbH)
> ---
>
> Key: INCUBATOR-147
> URL: https://issues.apache.org/jira/browse/INCUBATOR-147
> Project: Incubator
>  Issue Type: Task
>  Components: LogoSubmission
>Reporter: Claas Reimer (Noerdisch GmbH)
> Attachments: logo-1_block_apache-incubator_claasreimer-noerdisch.pdf, 
> logo-1_block_apache-incubator_claasreimer-noerdisch.png
>
>
> The concept V1 "Block"  by Claas Reimer, claas.rei...@noerdisch.de represents 
> the intention of growing and expanding for projects visualized by several 
> connected squares. Several colors represent different influences or topics 
> which come together to build a strong unit.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Created] (INCUBATOR-149) Incubator Logo 3 „Sun" by claasreimer (Nœrdisch GmbH)

[Claas Reimer (Noerdisch GmbH) (JIRA)]

Claas Reimer (Noerdisch GmbH) created INCUBATOR-149:
---

 Summary: Incubator Logo 3 „Sun" by claasreimer (Nœrdisch GmbH)
 Key: INCUBATOR-149
 URL: https://issues.apache.org/jira/browse/INCUBATOR-149
 Project: Incubator
  Issue Type: Task
  Components: LogoSubmission
Reporter: Claas Reimer (Noerdisch GmbH)
 Attachments: logo-3_sun_apache-incubator_claasreimer-noerdisch.pdf, 
logo-3_sun_apache-incubator_claasreimer-noerdisch.png

The concept V3 "Sun"  by Claas Reimer, claas.rei...@noerdisch.de represents the 
intention of growing and expanding for projects visualized by a sun-like icon 
and stands for live, birth, dynamic and power. Also you can imagine science or 
LED lights.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Updated] (INCUBATOR-148) Incubator Logo 2 „Tree" by claasreimer (Nœrdisch GmbH)

[Claas Reimer (Noerdisch GmbH) (JIRA)]

 [ 
https://issues.apache.org/jira/browse/INCUBATOR-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claas Reimer (Noerdisch GmbH) updated INCUBATOR-148:

Description: The concept V2 "Tree"  by Claas Reimer, 
claas.rei...@noerdisch.de represents the intention of growing and expanding for 
projects visualized by a tree. The tree also is a symbol for power in live and 
you can also imagine a cloud or even an abstract heart.  (was: The concept V2 
"Tree"  by Claas Reimer, claas.rei...@noerdisch.de represents the intention of 
growing and expanding for projects visualized by a tree. Also a tree is a 
symbol for giving live and you can also imagine a cloud or an abstract heart.)

> Incubator Logo 2 „Tree" by claasreimer (Nœrdisch GmbH)
> --
>
> Key: INCUBATOR-148
> URL: https://issues.apache.org/jira/browse/INCUBATOR-148
> Project: Incubator
>  Issue Type: Task
>  Components: LogoSubmission
>Reporter: Claas Reimer (Noerdisch GmbH)
> Attachments: logo-2_tree_apache-incubator_claasreimer-noerdisch.pdf, 
> logo-2_tree_apache-incubator_claasreimer-noerdisch.png
>
>
> The concept V2 "Tree"  by Claas Reimer, claas.rei...@noerdisch.de represents 
> the intention of growing and expanding for projects visualized by a tree. The 
> tree also is a symbol for power in live and you can also imagine a cloud or 
> even an abstract heart.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Updated] (INCUBATOR-148) Incubator Logo 2 „Tree" by claasreimer (Nœrdisch GmbH)

[Claas Reimer (Noerdisch GmbH) (JIRA)]

 [ 
https://issues.apache.org/jira/browse/INCUBATOR-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claas Reimer (Noerdisch GmbH) updated INCUBATOR-148:

Description: The concept V2 "Tree"  by Claas Reimer, 
claas.rei...@noerdisch.de represents the intention of growing and expanding for 
projects visualized by a tree. Also a tree is a symbol for giving live and you 
can also imagine a cloud or an abstract heart.  (was: The concept V2 "Tree"  by 
Claas Reimer, claas.rei...@noerdisch.de represents the intention of growing and 
expanding for projects visualized by a tree.)

> Incubator Logo 2 „Tree" by claasreimer (Nœrdisch GmbH)
> --
>
> Key: INCUBATOR-148
> URL: https://issues.apache.org/jira/browse/INCUBATOR-148
> Project: Incubator
>  Issue Type: Task
>  Components: LogoSubmission
>Reporter: Claas Reimer (Noerdisch GmbH)
> Attachments: logo-2_tree_apache-incubator_claasreimer-noerdisch.pdf, 
> logo-2_tree_apache-incubator_claasreimer-noerdisch.png
>
>
> The concept V2 "Tree"  by Claas Reimer, claas.rei...@noerdisch.de represents 
> the intention of growing and expanding for projects visualized by a tree. 
> Also a tree is a symbol for giving live and you can also imagine a cloud or 
> an abstract heart.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Created] (INCUBATOR-148) Incubator Logo 2 „Tree" by claasreimer (Nœrdisch GmbH)

[Claas Reimer (Noerdisch GmbH) (JIRA)]

Claas Reimer (Noerdisch GmbH) created INCUBATOR-148:
---

 Summary: Incubator Logo 2 „Tree" by claasreimer (Nœrdisch GmbH)
 Key: INCUBATOR-148
 URL: https://issues.apache.org/jira/browse/INCUBATOR-148
 Project: Incubator
  Issue Type: Task
  Components: LogoSubmission
Reporter: Claas Reimer (Noerdisch GmbH)
 Attachments: logo-2_tree_apache-incubator_claasreimer-noerdisch.pdf, 
logo-2_tree_apache-incubator_claasreimer-noerdisch.png

The concept V2 "Tree"  by Claas Reimer, claas.rei...@noerdisch.de represents 
the intention of growing and expanding for projects visualized by a tree.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[jira] [Created] (INCUBATOR-147) Incubator Logo 1 "Block" by claasreimer (Nœrdisch GmbH)

[Claas Reimer (Noerdisch GmbH) (JIRA)]

Claas Reimer (Noerdisch GmbH) created INCUBATOR-147:
---

 Summary: Incubator Logo 1 "Block" by claasreimer (Nœrdisch GmbH)
 Key: INCUBATOR-147
 URL: https://issues.apache.org/jira/browse/INCUBATOR-147
 Project: Incubator
  Issue Type: Task
  Components: LogoSubmission
Reporter: Claas Reimer (Noerdisch GmbH)
 Attachments: logo-1_block_apache-incubator_claasreimer-noerdisch.pdf, 
logo-1_block_apache-incubator_claasreimer-noerdisch.png

The concept V1 "Block"  by Claas Reimer, claas.rei...@noerdisch.de represents 
the intention of growing and expanding for projects visualized by several 
connected squares.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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