Re: Committer for MXNet.

[Henri Yandell]

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

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

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

Re: Write access to January report page

[Marvin Humphrey]

On Mon, Jan 9, 2017 at 11:34 AM, Carlos Santana  wrote:
> Hi my I just created a userid CarlosSantana on the wiki
> Can I get write access?

Done.

Marvin Humphrey

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

[DISCUSS] Hammock to incubate at the ASF as Apache Hammock (incubating)

[John D. Ament]

Hi All,

I would like to submit to you a proposal to bring Hammock to the ASF.
Hammock is a lightweight microservices framework and CDI (Contexts and
Dependency Injection for Java) extension library.  It is designed for small
deployments first, high configurability and a simplified development
model.  The core microservice runtime is meant to replace legacy Java based
application servers while the remaining CDI extensions are meant to work in
any CDI runtime.  Its a small team, mostly getting started with community
contribution, however it makes sense to move into a foundation rather than
try to keep it operating alone.

I've copied the proposal text below.  The page can be found at
https://wiki.apache.org/incubator/HammockProposal .  I'm looking forward to
seeing interest and discussions around Hammock.  Some might say its my
pride and joy.

= Hammock Proposal =

== Abstract ==

Hammock is a CDI (Contexts & Dependency Injection for Java) based
Microservices framework.  It provides basic bootstrapping as well as a
number of CDI extensions focused on the tools typically used in
microservices development.

== Proposal ==

The proposal is to create the Hammock Project within the Apache Software
Foundation.

== Background ==

Hammock was conceived as an initial prototype from the Resteasy codebase
some years back to prove out CDI integration in a JAX-RS container on top
of Netty as a webserver.  Over time, it grew into a more robust
implementation supporting pluggable servlet containers, JAX-RS
implementations.  It has also started to house various CDI extensions that
focus on cloud environments and tooling useful to microservices.

A small developer and user community have formed around the tooling,
allowing it to be tried and tested in various deployment environments.

== Rationale ==

The need for frameworks based around microservices has grown over time.
The need to leverage various Java EE technologies has allowed projects to
leverage these tools without changing their development methodologies.

== Initial Goals ==

Hammock has just completed its 1.0 release.  Upon migrating to ASF
infrastructure, we anticipate various re-packaging steps - maven
coordinates, package name changes.  A website will need to be created in
addition to new features coming into the code base.

== Current Status ==

Hammock has a strong pipeline of features coming in.  It is aligned to the
CDI 1.2 API but will go to CDI 2.0 once available and stabilized.  New
users are popping up and features coming in as those users need them.

=== Meritocracy ===

The Hammock codebase has been Apache v2 licensed since the beginning.  As
we start to move to the ASF, we expect to more formalize development
strategies and build out

=== Community ===

The target community are those interested in CDI but want to slim down
their container dependencies.  The Microprofile community has focused on
that pretty heavily and we see interest coming from there frequently.

=== Core Developers ===

 * John D. Ament
 * Libor Kramoliš
 * Irimia Dragos
 * Gerald Mücke

=== Alignment ===

Hammock currently leverages the following Apache products:
 * CXF
 * Tomcat
 * DeltaSpike
 * Johnzon
 * ActiveMQ Artemis
 * OpenWebBeans

In addition, there are plans to add integration for Camel, Juneau, Kafka in
the near term.

== Known Risks ==

=== Orphaned products ===

Hammock was one of the first six implementations of Microprofile.  It was
the first implementation not backed by a software vendor but instead a true
community effort.  Based on the path forward for both the project and
Microprofile, it is not likely to be abandoned any time soon.

=== Inexperience with Open Source ===

Half of the committers are active in other areas of open source.  With
time, the remaining half will gain their footing.

=== Homogenous Developers ===

Hammock was not started within a company.  Instead it came together as a
shared vision from a number of community members.  The developer community
behind it do not hail from any single company, giving the project a leg up
in staying diverse.

=== Reliance on Salaried Developers ===

None of the current developers are paid salary to work on or maintain
Hammock.

=== Relationships with Other Apache Products ===

Hammock is built from a large number of existing Apache Products.  Full
list can be found in the alignment section.

=== A Excessive Fascination with the Apache Brand ===

The move to the ASF is focused on creating a level playing field and a true
community around the product.  Leveraging the ASF is based on core
committer competencies within the ASF (over Eclipse Foundation or Linux
Foundation).

== Documentation ==

All user documentation can be found in the wiki -
https://github.com/hammock-project/hammock/wiki

== Initial Source ==

All source code from https://github.com/hammock-project, with the exclusion
of micrprofile-samples are eligible for inclusion.
The logo of Hammock was a paid item.  A license can be requested from the

[RESULT] [VOTE] Graduate Apache Ranger Project from the Incubator - Resending with additional mail distro

[Ramesh Mani]

Resending after segregating the results with number of binding and
non-binding votes.

Dear Incubator members,

It has been more that 72 hours since I started this VOTE thread, so I
consider this voting thread as closed.
Many Thanks to incubator members and mentors for voting.

Here is the result

Eighteen [+1] Votes  ( 12 binding votes , 6 non-binding votes )

Binding Votes:
==

 Jean-Baptiste Onofré   (binding)
 Mark Struberg  (binding)
 Roman Shaposhnik   (binding)
Julian Hyde (binding)
Chris Nauroth   (binding)
Suneel Marthi   (binding)
Owen O'Malley   (binding)
Niclas Hedhman  (binding)
Drew Farris (binding)
Joe Witt(binding)
Alan Gates  (binding)
Jakob Homan (binding)

Non-Binding Votes:
==

Selvamohan Neethiraj(non-binding)
Balaji Ganesan  (non-binding)

Edward Zhang(non-binding)


Sailaja Polavarapu  (non-binding)
Ramesh Mani (non-binding)
Gautam Borad(non-binding)



Zero [+0] Votes

Zero [-1] Votes

Voting succeeded and I shall proceed to the next step discussion with
Ranger Mentors on Apache Ranger TLP.

Congratulations Rangers!

Many Thanks,
Ramesh Mani


On 1/4/17, 2:48 PM, "Ramesh Mani"  wrote:

>Dear Incubator members,
>
>Apache Ranger Project community has successfully released 0.6.2 version
>and with it there had been a lot of discussion within Apache Ranger
>community to consider graduation to TLP. Apache Ranger entered into
>incubation on 24th July 2014 and from this welcoming community had done a
>tremendous job in resolving various technical hurdles like refactoring
>the project core model to  be service based, adding more Apache Hadoop
>components like Apache YARN, Apache Storm, Apache Kafka, Apache Nifi,
>Apache Ranger KMS into Ranger Authorizing  model for security and making
>it into a core product in the Apache Hadoop security space. PPMC has
>exhibited a clear understanding of this growing apache community by
>electing  4 individuals as committers  and  inculding 22 individuals as
>contributors to the Apache Ranger project. PPMC also has done 8
>successful releases under the guidance of mentors demonstrating their
>mastery over AFS¹s IP policies.
>
>An voting was conducted within Apache Ranger Community to graduate Apache
>Ranger Project to Top Level Project. Vote passed with 16 +1 votes , no 0
>or ­1 votes.
>http://mail-archives.apache.org/mod_mbox/incubator-ranger-dev/201612.mbox/
>%3CD479D4C8.11E4E%25rmani%40hortonworks.com%3E
>
>Apache Ranger Project has shown a great perspective to become a true TLP.
>Following summary on the project reflects its accomplishment.
>
>Please vote on the Project resolution that is found in bottom to graduate
>Apache Ranger Project from Incubator to Top Level Project.
>
>[ ] +1 Graduate Apache Ranger from the Incubator.
>[ ] +0 No opinion
>[ ] -1 Don't graduate Apache Ranger from the Incubator ( please provide
>the reason)
>
>This VOTE will be opened for next 72 hours.
>
>Thanks all Mentors and Apache Ranger Project members for their support
>and contributions.
>
>Here is my vote +1 (binding)
>
>Project Summary:
>=
>
>http://incubator.apache.org/projects/ranger.html
>
>Project website:
>=
>
>http://ranger.incubator.apache.org
>
>Project Documentation:
>===
>
>http://ranger.incubator.apache.org/index.html
>http://ranger.incubator.apache.org/quick_start_guide.html
>https://cwiki.apache.org/confluence/display/RANGER/Release+Folders
>
>Project maturity Assessment:
>===
>
>https://cwiki.apache.org/confluence/display/RANGER/Apache+Ranger+Project+M
>a
>turity+Model
>
>Proposed PMC size: 17
>
>Total number of committers   : 14 members
>Total number of contributors : 22 members
>
>PMC affiliation (* indicated chair)
>
>* Hortonworks (9)
>   Privacera (2)
>   BlueTalon (1)
>   Others(1)
>
>1802 commits on develop
>22 contributors across all branches
>Dev list averaged ~50 msgs/month in 2016
>User list averaged ~40 msgs/month in 2016
>1208 issues created
>997 issues resolved
>
>Committer¹s affiliation:
>===
>Active:
>Hortonworks
>Talend
>Freestone infotech
>BlueTalon
>eBay
>Others
>
>
>Apache Ranger Top Level Project Resolution:
>
>
>Establish the Apache Ranger Project
>
>WHEREAS, the Board of Directors deems it to be in the best interests of
>the Foundation and consistent with the Foundation¹s purpose 

[RESULT] [VOTE] Graduate Apache Ranger Project from the Incubator - Resending with additional mail distro

[Ramesh Mani]

Resending after seggregatting the results with number of binding and
non-binding votes.

Dear Incubator members,

It has been more that 72 hours since I started this VOTE thread, so I
consider this voting thread as closed.
Many Thanks to incubator members and mentors for voting.

Here is the result

Eighteen [+1] Votes  ( 12 binding votes , 6 non-binding votes )

 Jean-Baptiste Onofré   (binding)
 Mark Struberg  (binding)
 Roman Shaposhnik   (binding)
Julian Hyde (binding)
Chris Nauroth   (binding)
Selvamohan Neethiraj(non-binding)
Suneel Marthi   (binding)
Balaji Ganesan  (non-binding)
Owen O'Malley   (binding)
Niclas Hedhman  (binding)
Drew Farris (binding)
Edward Zhang(non-binding)
Joe Witt(binding)
Gautam Borad(non-binding)
Alan Gates  (non-binding)
Sailaja Polavarapu  (non-binding)
Ramesh Mani (non-binding)
Jakob Homan (binding)


Zero [+0] Votes

Zero [-1] Votes

Voting succeeded and I shall proceed to the next step discussion with
Ranger Mentors on Apache Ranger TLP.

Congratulations Rangers!

Many Thanks,
Ramesh Mani


On 1/4/17, 2:48 PM, "Ramesh Mani"  wrote:

>Dear Incubator members,
>
>Apache Ranger Project community has successfully released 0.6.2 version
>and with it there had been a lot of discussion within Apache Ranger
>community to consider graduation to TLP. Apache Ranger entered into
>incubation on 24th July 2014 and from this welcoming community had done a
>tremendous job in resolving various technical hurdles like refactoring
>the project core model to  be service based, adding more Apache Hadoop
>components like Apache YARN, Apache Storm, Apache Kafka, Apache Nifi,
>Apache Ranger KMS into Ranger Authorizing  model for security and making
>it into a core product in the Apache Hadoop security space. PPMC has
>exhibited a clear understanding of this growing apache community by
>electing  4 individuals as committers  and  inculding 22 individuals as
>contributors to the Apache Ranger project. PPMC also has done 8
>successful releases under the guidance of mentors demonstrating their
>mastery over AFS¹s IP policies.
>
>An voting was conducted within Apache Ranger Community to graduate Apache
>Ranger Project to Top Level Project. Vote passed with 16 +1 votes , no 0
>or ­1 votes.
>http://mail-archives.apache.org/mod_mbox/incubator-ranger-dev/201612.mbox/
>%3CD479D4C8.11E4E%25rmani%40hortonworks.com%3E
>
>Apache Ranger Project has shown a great perspective to become a true TLP.
>Following summary on the project reflects its accomplishment.
>
>Please vote on the Project resolution that is found in bottom to graduate
>Apache Ranger Project from Incubator to Top Level Project.
>
>[ ] +1 Graduate Apache Ranger from the Incubator.
>[ ] +0 No opinion
>[ ] -1 Don't graduate Apache Ranger from the Incubator ( please provide
>the reason)
>
>This VOTE will be opened for next 72 hours.
>
>Thanks all Mentors and Apache Ranger Project members for their support
>and contributions.
>
>Here is my vote +1 (binding)
>
>Project Summary:
>=
>
>http://incubator.apache.org/projects/ranger.html
>
>Project website:
>=
>
>http://ranger.incubator.apache.org
>
>Project Documentation:
>===
>
>http://ranger.incubator.apache.org/index.html
>http://ranger.incubator.apache.org/quick_start_guide.html
>https://cwiki.apache.org/confluence/display/RANGER/Release+Folders
>
>Project maturity Assessment:
>===
>
>https://cwiki.apache.org/confluence/display/RANGER/Apache+Ranger+Project+M
>a
>turity+Model
>
>Proposed PMC size: 17
>
>Total number of committers   : 14 members
>Total number of contributors : 22 members
>
>PMC affiliation (* indicated chair)
>
>* Hortonworks (9)
>   Privacera (2)
>   BlueTalon (1)
>   Others(1)
>
>1802 commits on develop
>22 contributors across all branches
>Dev list averaged ~50 msgs/month in 2016
>User list averaged ~40 msgs/month in 2016
>1208 issues created
>997 issues resolved
>
>Committer¹s affiliation:
>===
>Active:
>Hortonworks
>Talend
>Freestone infotech
>BlueTalon
>eBay
>Others
>
>
>Apache Ranger Top Level Project Resolution:
>
>
>Establish the Apache Ranger Project
>
>WHEREAS, the Board of Directors deems it to be in the best interests of
>the Foundation and consistent with the Foundation¹s purpose to establish a
>Project Management Committee charged with the 

Re: [VOTE] Graduate Apache Ranger Project from the Incubator - Resending with additional mail distro

[Luciano Resende]

+1 (binding)

On Wed, Jan 4, 2017 at 2:48 PM, Ramesh Mani  wrote:

> Dear Incubator members,
>
> Apache Ranger Project community has successfully released 0.6.2 version
> and with it there had been a lot of discussion within Apache Ranger
> community to consider graduation to TLP. Apache Ranger entered into
> incubation on 24th July 2014 and from this welcoming community had done a
> tremendous job in resolving various technical hurdles like refactoring the
> project core model to  be service based, adding more Apache Hadoop
> components like Apache YARN, Apache Storm, Apache Kafka, Apache Nifi,
> Apache Ranger KMS into Ranger Authorizing  model for security and making it
> into a core product in the Apache Hadoop security space. PPMC has exhibited
> a clear understanding of this growing apache community by electing  4
> individuals as committers  and  inculding 22 individuals as contributors to
> the Apache Ranger project. PPMC also has done 8 successful releases under
> the guidance of mentors demonstrating their mastery over AFS’s IP policies.
>
> An voting was conducted within Apache Ranger Community to graduate Apache
> Ranger Project to Top Level Project. Vote passed with 16 +1 votes , no 0 or
> –1 votes.
> http://mail-archives.apache.org/mod_mbox/incubator-ranger-
> dev/201612.mbox/%3CD479D4C8.11E4E%25rmani%40hortonworks.com%3E
>
> Apache Ranger Project has shown a great perspective to become a true TLP.
> Following summary on the project reflects its accomplishment.
>
> Please vote on the Project resolution that is found in bottom to graduate
> Apache Ranger Project from Incubator to Top Level Project.
>
> [ ] +1 Graduate Apache Ranger from the Incubator.
> [ ] +0 No opinion
> [ ] -1 Don't graduate Apache Ranger from the Incubator ( please provide
> the reason)
>
> This VOTE will be opened for next 72 hours.
>
> Thanks all Mentors and Apache Ranger Project members for their support and
> contributions.
>
> Here is my vote +1 (binding)
>
> Project Summary:
> =
>
> http://incubator.apache.org/projects/ranger.html
>
> Project website:
> =
>
> http://ranger.incubator.apache.org
>
> Project Documentation:
> ===
>
> http://ranger.incubator.apache.org/index.html
> http://ranger.incubator.apache.org/quick_start_guide.html
> https://cwiki.apache.org/confluence/display/RANGER/Release+Folders
>
> Project maturity Assessment:
> ===
>
> https://cwiki.apache.org/confluence/display/RANGER/
> Apache+Ranger+Project+Ma
> turity+Model
>
> Proposed PMC size: 17
>
> Total number of committers   : 14 members
> Total number of contributors : 22 members
>
> PMC affiliation (* indicated chair)
>
> * Hortonworks (9)
>Privacera (2)
>BlueTalon (1)
>Others(1)
>
> 1802 commits on develop
> 22 contributors across all branches
> Dev list averaged ~50 msgs/month in 2016
> User list averaged ~40 msgs/month in 2016
> 1208 issues created
> 997 issues resolved
>
> Committer’s affiliation:
> ===
> Active:
> Hortonworks
> Talend
> Freestone infotech
> BlueTalon
> eBay
> Others
>
>
> Apache Ranger Top Level Project Resolution:
> 
>
> Establish the Apache Ranger Project
>
> WHEREAS, the Board of Directors deems it to be in the best interests of
> the Foundation and consistent with the Foundation’s purpose to establish a
> Project Management Committee charged with the creation and maintenance of
> open-source software, for distribution at no charge to the public, related
> to a data management platform That provides real-time, consistent access
> to data-intensive applications throughout widely distributed cloud
> architectures.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Ranger Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED,that the Apache Ranger Project be and hereby is responsible for
> the creation and maintenance of software related to a data management
> platform that provides real-time, consistent access to data-intensive
> applications throughout widely distributed cloud architectures.
>
> RESOLVED, that the office of "Vice President, Apache Ranger" be and
> hereby is created, the person holding such office to serve at the
> direction of the Board of Directors as the chair of the Apache Ranger
> Project, and to have primary responsibility for management of the projects
> within the scope of responsibility of the Apache Ranger Project; and be it
> Further.
>
> RESOLVED,that the persons listed immediately below be and hereby are
> appointed to serve as the initial members of the Apache Ranger Project:
>
> Alok La
> la...@apache.org
> Alan Gates
> ga...@apache.org
> Balaji Ganesan
> 

[RESULT] [VOTE] Graduate Apache Ranger Project from the Incubator - Resending with additional mail distro

[Ramesh Mani]

Resending this email with updated result count, as I noticed one more +1
(from Jakob Homan) after I sent the email.


Dear Incubator members,

It has been more that 72 hours since I started this VOTE thread, so I
consider this voting thread as closed.
Many Thanks to incubator members and mentors for voting.

Here is the result

Eighteen [+1] Votes

 Jean-Baptiste Onofré   
 Mark Struberg  
 Roman Shaposhnik   
Julian Hyde 
Chris Nauroth   
Selvamohan Neethiraj
Suneel Marthi   
Balaji Ganesan  
Owen O'Malley   
Niclas Hedhman  
Drew Farris 
Edward Zhang
Joe Witt
Gautam Borad
Alan Gates  
Sailaja Polavarapu  
Ramesh Mani  
Jakob Homan 


Zero [+0] Votes

Zero [-1] Votes

Voting succeeded and I shall proceed to the next step discussion with
Ranger Mentors on Apache Ranger TLP.

Congratulations Rangers!

Many Thanks,
Ramesh Mani


On 1/4/17, 2:48 PM, "Ramesh Mani"  wrote:

>Dear Incubator members,
>
>Apache Ranger Project community has successfully released 0.6.2 version
>and with it there had been a lot of discussion within Apache Ranger
>community to consider graduation to TLP. Apache Ranger entered into
>incubation on 24th July 2014 and from this welcoming community had done a
>tremendous job in resolving various technical hurdles like refactoring
>the project core model to  be service based, adding more Apache Hadoop
>components like Apache YARN, Apache Storm, Apache Kafka, Apache Nifi,
>Apache Ranger KMS into Ranger Authorizing  model for security and making
>it into a core product in the Apache Hadoop security space. PPMC has
>exhibited a clear understanding of this growing apache community by
>electing  4 individuals as committers  and  inculding 22 individuals as
>contributors to the Apache Ranger project. PPMC also has done 8
>successful releases under the guidance of mentors demonstrating their
>mastery over AFS¹s IP policies.
>
>An voting was conducted within Apache Ranger Community to graduate Apache
>Ranger Project to Top Level Project. Vote passed with 16 +1 votes , no 0
>or ­1 votes.
>http://mail-archives.apache.org/mod_mbox/incubator-ranger-dev/201612.mbox/
>%3CD479D4C8.11E4E%25rmani%40hortonworks.com%3E
>
>Apache Ranger Project has shown a great perspective to become a true TLP.
>Following summary on the project reflects its accomplishment.
>
>Please vote on the Project resolution that is found in bottom to graduate
>Apache Ranger Project from Incubator to Top Level Project.
>
>[ ] +1 Graduate Apache Ranger from the Incubator.
>[ ] +0 No opinion
>[ ] -1 Don't graduate Apache Ranger from the Incubator ( please provide
>the reason)
>
>This VOTE will be opened for next 72 hours.
>
>Thanks all Mentors and Apache Ranger Project members for their support
>and contributions.
>
>Here is my vote +1 (binding)
>
>Project Summary:
>=
>
>http://incubator.apache.org/projects/ranger.html
>
>Project website:
>=
>
>http://ranger.incubator.apache.org
>
>Project Documentation:
>===
>
>http://ranger.incubator.apache.org/index.html
>http://ranger.incubator.apache.org/quick_start_guide.html
>https://cwiki.apache.org/confluence/display/RANGER/Release+Folders
>
>Project maturity Assessment:
>===
>
>https://cwiki.apache.org/confluence/display/RANGER/Apache+Ranger+Project+M
>a
>turity+Model
>
>Proposed PMC size: 17
>
>Total number of committers   : 14 members
>Total number of contributors : 22 members
>
>PMC affiliation (* indicated chair)
>
>* Hortonworks (9)
>   Privacera (2)
>   BlueTalon (1)
>   Others(1)
>
>1802 commits on develop
>22 contributors across all branches
>Dev list averaged ~50 msgs/month in 2016
>User list averaged ~40 msgs/month in 2016
>1208 issues created
>997 issues resolved
>
>Committer¹s affiliation:
>===
>Active:
>Hortonworks
>Talend
>Freestone infotech
>BlueTalon
>eBay
>Others
>
>
>Apache Ranger Top Level Project Resolution:
>
>
>Establish the Apache Ranger Project
>
>WHEREAS, the Board of Directors deems it to be in the best interests of
>the Foundation and consistent with the Foundation¹s purpose to establish a
>Project Management Committee charged with the creation and maintenance of
>open-source software, for distribution at no charge to the public, related
>to a data management platform That provides real-time, consistent access
>to data-intensive 

[RESULT] [VOTE] Graduate Apache Ranger Project from the Incubator - Resending with additional mail distro

[Ramesh Mani]

Resending this email with updated result count, as I noticed one more +1
(from Jakob Homan) after I sent the email.


Dear Incubator members,

It has been more that 72 hours since I started this VOTE thread, so I
consider this voting thread as closed.
Many Thanks to incubator members and mentors for voting.

Here is the result

Seventeen [+1] Votes

 Jean-Baptiste Onofré   
 Mark Struberg  
 Roman Shaposhnik   
Julian Hyde 
Chris Nauroth   
Selvamohan Neethiraj
Suneel Marthi   
Balaji Ganesan  
Owen O'Malley   
Niclas Hedhman  
Drew Farris 
Edward Zhang
Joe Witt
Gautam Borad
Alan Gates  
Sailaja Polavarapu  
Ramesh Mani  
Jakob Homan 


Zero [+0] Votes

Zero [-1] Votes

Voting succeeded and I shall proceed to the next step discussion with
Ranger Mentors on Apache Ranger TLP.

Congratulations Rangers!

Many Thanks,
Ramesh Mani


On 1/4/17, 2:48 PM, "Ramesh Mani"  wrote:

>Dear Incubator members,
>
>Apache Ranger Project community has successfully released 0.6.2 version
>and with it there had been a lot of discussion within Apache Ranger
>community to consider graduation to TLP. Apache Ranger entered into
>incubation on 24th July 2014 and from this welcoming community had done a
>tremendous job in resolving various technical hurdles like refactoring
>the project core model to  be service based, adding more Apache Hadoop
>components like Apache YARN, Apache Storm, Apache Kafka, Apache Nifi,
>Apache Ranger KMS into Ranger Authorizing  model for security and making
>it into a core product in the Apache Hadoop security space. PPMC has
>exhibited a clear understanding of this growing apache community by
>electing  4 individuals as committers  and  inculding 22 individuals as
>contributors to the Apache Ranger project. PPMC also has done 8
>successful releases under the guidance of mentors demonstrating their
>mastery over AFS¹s IP policies.
>
>An voting was conducted within Apache Ranger Community to graduate Apache
>Ranger Project to Top Level Project. Vote passed with 16 +1 votes , no 0
>or ­1 votes.
>http://mail-archives.apache.org/mod_mbox/incubator-ranger-dev/201612.mbox/
>%3CD479D4C8.11E4E%25rmani%40hortonworks.com%3E
>
>Apache Ranger Project has shown a great perspective to become a true TLP.
>Following summary on the project reflects its accomplishment.
>
>Please vote on the Project resolution that is found in bottom to graduate
>Apache Ranger Project from Incubator to Top Level Project.
>
>[ ] +1 Graduate Apache Ranger from the Incubator.
>[ ] +0 No opinion
>[ ] -1 Don't graduate Apache Ranger from the Incubator ( please provide
>the reason)
>
>This VOTE will be opened for next 72 hours.
>
>Thanks all Mentors and Apache Ranger Project members for their support
>and contributions.
>
>Here is my vote +1 (binding)
>
>Project Summary:
>=
>
>http://incubator.apache.org/projects/ranger.html
>
>Project website:
>=
>
>http://ranger.incubator.apache.org
>
>Project Documentation:
>===
>
>http://ranger.incubator.apache.org/index.html
>http://ranger.incubator.apache.org/quick_start_guide.html
>https://cwiki.apache.org/confluence/display/RANGER/Release+Folders
>
>Project maturity Assessment:
>===
>
>https://cwiki.apache.org/confluence/display/RANGER/Apache+Ranger+Project+M
>a
>turity+Model
>
>Proposed PMC size: 17
>
>Total number of committers   : 14 members
>Total number of contributors : 22 members
>
>PMC affiliation (* indicated chair)
>
>* Hortonworks (9)
>   Privacera (2)
>   BlueTalon (1)
>   Others(1)
>
>1802 commits on develop
>22 contributors across all branches
>Dev list averaged ~50 msgs/month in 2016
>User list averaged ~40 msgs/month in 2016
>1208 issues created
>997 issues resolved
>
>Committer¹s affiliation:
>===
>Active:
>Hortonworks
>Talend
>Freestone infotech
>BlueTalon
>eBay
>Others
>
>
>Apache Ranger Top Level Project Resolution:
>
>
>Establish the Apache Ranger Project
>
>WHEREAS, the Board of Directors deems it to be in the best interests of
>the Foundation and consistent with the Foundation¹s purpose to establish a
>Project Management Committee charged with the creation and maintenance of
>open-source software, for distribution at no charge to the public, related
>to a data management platform That provides real-time, consistent access
>to data-intensive 

Re: Write access to January report page

[Carlos Santana]

Hi my I just created a userid CarlosSantana on the wiki
Can I get write access?

[RESULT] [VOTE] Graduate Apache Ranger Project from the Incubator - Resending with additional mail distro

[Ramesh Mani]

Dear Incubator members,

It has been more that 72 hours since I started this VOTE thread, so I
consider this voting thread as closed.
Many Thanks to incubator members and mentors for voting.

Here is the result

Seventeen [+1] Votes

 Jean-Baptiste Onofré   
 Mark Struberg  
 Roman Shaposhnik   
Julian Hyde 
Chris Nauroth   
Selvamohan Neethiraj

Suneel Marthi   
Balaji Ganesan  
Owen O'Malley   
Niclas Hedhman  
Drew Farris 
Edward Zhang
Joe Witt
Gautam Borad
Alan Gates  
Sailaja Polavarapu  
Ramesh Mani  

Zero [+0] Votes

Zero [-1] Votes

Voting succeeded and I shall proceed to the next step discussion with
Ranger Mentors on Apache Ranger TLP.

Congratulations Rangers!

Many Thanks,
Ramesh Mani


On 1/4/17, 2:48 PM, "Ramesh Mani"  wrote:

>Dear Incubator members,
>
>Apache Ranger Project community has successfully released 0.6.2 version
>and with it there had been a lot of discussion within Apache Ranger
>community to consider graduation to TLP. Apache Ranger entered into
>incubation on 24th July 2014 and from this welcoming community had done a
>tremendous job in resolving various technical hurdles like refactoring
>the project core model to  be service based, adding more Apache Hadoop
>components like Apache YARN, Apache Storm, Apache Kafka, Apache Nifi,
>Apache Ranger KMS into Ranger Authorizing  model for security and making
>it into a core product in the Apache Hadoop security space. PPMC has
>exhibited a clear understanding of this growing apache community by
>electing  4 individuals as committers  and  inculding 22 individuals as
>contributors to the Apache Ranger project. PPMC also has done 8
>successful releases under the guidance of mentors demonstrating their
>mastery over AFS¹s IP policies.
>
>An voting was conducted within Apache Ranger Community to graduate Apache
>Ranger Project to Top Level Project. Vote passed with 16 +1 votes , no 0
>or ­1 votes.
>http://mail-archives.apache.org/mod_mbox/incubator-ranger-dev/201612.mbox/
>%3CD479D4C8.11E4E%25rmani%40hortonworks.com%3E
>
>Apache Ranger Project has shown a great perspective to become a true TLP.
>Following summary on the project reflects its accomplishment.
>
>Please vote on the Project resolution that is found in bottom to graduate
>Apache Ranger Project from Incubator to Top Level Project.
>
>[ ] +1 Graduate Apache Ranger from the Incubator.
>[ ] +0 No opinion
>[ ] -1 Don't graduate Apache Ranger from the Incubator ( please provide
>the reason)
>
>This VOTE will be opened for next 72 hours.
>
>Thanks all Mentors and Apache Ranger Project members for their support
>and contributions.
>
>Here is my vote +1 (binding)
>
>Project Summary:
>=
>
>http://incubator.apache.org/projects/ranger.html
>
>Project website:
>=
>
>http://ranger.incubator.apache.org
>
>Project Documentation:
>===
>
>http://ranger.incubator.apache.org/index.html
>http://ranger.incubator.apache.org/quick_start_guide.html
>https://cwiki.apache.org/confluence/display/RANGER/Release+Folders
>
>Project maturity Assessment:
>===
>
>https://cwiki.apache.org/confluence/display/RANGER/Apache+Ranger+Project+M
>a
>turity+Model
>
>Proposed PMC size: 17
>
>Total number of committers   : 14 members
>Total number of contributors : 22 members
>
>PMC affiliation (* indicated chair)
>
>* Hortonworks (9)
>   Privacera (2)
>   BlueTalon (1)
>   Others(1)
>
>1802 commits on develop
>22 contributors across all branches
>Dev list averaged ~50 msgs/month in 2016
>User list averaged ~40 msgs/month in 2016
>1208 issues created
>997 issues resolved
>
>Committer¹s affiliation:
>===
>Active:
>Hortonworks
>Talend
>Freestone infotech
>BlueTalon
>eBay
>Others
>
>
>Apache Ranger Top Level Project Resolution:
>
>
>Establish the Apache Ranger Project
>
>WHEREAS, the Board of Directors deems it to be in the best interests of
>the Foundation and consistent with the Foundation¹s purpose to establish a
>Project Management Committee charged with the creation and maintenance of
>open-source software, for distribution at no charge to the public, related
>to a data management platform That provides real-time, consistent access
>to data-intensive applications throughout widely distributed cloud
>architectures.
>
>NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
>(PMC), to be known as the "Apache 

Re: [VOTE] Graduate Apache Ranger Project from the Incubator - Resending with additional mail distro

[Jakob Homan]

+1 (binding)

On 9 January 2017 at 10:52, Sailaja Polavarapu
 wrote:
> +1
>
> -Sailaja
>
>
>
>
> On 1/4/17, 2:48 PM, "Ramesh Mani"  wrote:
>
>>Dear Incubator members,
>>
>>Apache Ranger Project community has successfully released 0.6.2 version and 
>>with it there had been a lot of discussion within Apache Ranger community to 
>>consider graduation to TLP. Apache Ranger entered into incubation on 24th 
>>July 2014 and from this welcoming community had done a tremendous job in 
>>resolving various technical hurdles like refactoring the project core model 
>>to  be service based, adding more Apache Hadoop components like Apache YARN, 
>>Apache Storm, Apache Kafka, Apache Nifi,  Apache Ranger KMS into Ranger 
>>Authorizing  model for security and making it into a core product in the 
>>Apache Hadoop security space. PPMC has exhibited a clear understanding of 
>>this growing apache community by electing  4 individuals as committers  and  
>>inculding 22 individuals as contributors to the Apache Ranger project. PPMC 
>>also has done 8 successful releases under the guidance of mentors 
>>demonstrating their mastery over AFS’s IP policies.
>>
>>An voting was conducted within Apache Ranger Community to graduate Apache 
>>Ranger Project to Top Level Project. Vote passed with 16 +1 votes , no 0 or 
>>–1 votes.
>>http://mail-archives.apache.org/mod_mbox/incubator-ranger-dev/201612.mbox/%3CD479D4C8.11E4E%25rmani%40hortonworks.com%3E
>>
>>Apache Ranger Project has shown a great perspective to become a true TLP. 
>>Following summary on the project reflects its accomplishment.
>>
>>Please vote on the Project resolution that is found in bottom to graduate 
>>Apache Ranger Project from Incubator to Top Level Project.
>>
>>[ ] +1 Graduate Apache Ranger from the Incubator.
>>[ ] +0 No opinion
>>[ ] -1 Don't graduate Apache Ranger from the Incubator ( please provide the 
>>reason)
>>
>>This VOTE will be opened for next 72 hours.
>>
>>Thanks all Mentors and Apache Ranger Project members for their support and 
>>contributions.
>>
>>Here is my vote +1 (binding)
>>
>>Project Summary:
>>=
>>
>>http://incubator.apache.org/projects/ranger.html
>>
>>Project website:
>>=
>>
>>http://ranger.incubator.apache.org
>>
>>Project Documentation:
>>===
>>
>>http://ranger.incubator.apache.org/index.html
>>http://ranger.incubator.apache.org/quick_start_guide.html
>>https://cwiki.apache.org/confluence/display/RANGER/Release+Folders
>>
>>Project maturity Assessment:
>>===
>>
>>https://cwiki.apache.org/confluence/display/RANGER/Apache+Ranger+Project+Ma
>>turity+Model
>>
>>Proposed PMC size: 17
>>
>>Total number of committers   : 14 members
>>Total number of contributors : 22 members
>>
>>PMC affiliation (* indicated chair)
>>
>>* Hortonworks (9)
>>   Privacera (2)
>>   BlueTalon (1)
>>   Others(1)
>>
>>1802 commits on develop
>>22 contributors across all branches
>>Dev list averaged ~50 msgs/month in 2016
>>User list averaged ~40 msgs/month in 2016
>>1208 issues created
>>997 issues resolved
>>
>>Committer’s affiliation:
>>===
>>Active:
>>Hortonworks
>>Talend
>>Freestone infotech
>>BlueTalon
>>eBay
>>Others
>>
>>
>>Apache Ranger Top Level Project Resolution:
>>
>>
>>Establish the Apache Ranger Project
>>
>>WHEREAS, the Board of Directors deems it to be in the best interests of
>>the Foundation and consistent with the Foundation’s purpose to establish a
>>Project Management Committee charged with the creation and maintenance of
>>open-source software, for distribution at no charge to the public, related
>>to a data management platform That provides real-time, consistent access
>>to data-intensive applications throughout widely distributed cloud
>>architectures.
>>
>>NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
>>(PMC), to be known as the "Apache Ranger Project", be and hereby is
>>established pursuant to Bylaws of the Foundation; and be it further
>>
>>RESOLVED,that the Apache Ranger Project be and hereby is responsible for
>>the creation and maintenance of software related to a data management
>>platform that provides real-time, consistent access to data-intensive
>>applications throughout widely distributed cloud architectures.
>>
>>RESOLVED, that the office of "Vice President, Apache Ranger" be and
>>hereby is created, the person holding such office to serve at the
>>direction of the Board of Directors as the chair of the Apache Ranger
>>Project, and to have primary responsibility for management of the projects
>>within the scope of responsibility of the Apache Ranger Project; and be it
>>Further.
>>
>>RESOLVED,that the persons listed immediately below be and hereby are
>>appointed to serve as the initial members of the Apache Ranger Project:
>>
>>Alok La

Re: Release Process [was: [VOTE] Drop incubating requirement of Maven artifacts]

[Edward Capriolo]

On Sun, Jan 8, 2017 at 7:26 PM, John D. Ament  wrote:

> On Sun, Jan 8, 2017 at 6:55 PM Niclas Hedhman  wrote:
>
> > Yes, I think we all hear your "frustration" that the process is not as
> > streamlined as it perhaps could, nor that the documentation is as solid
> as
> > one might expect (patches are welcome)
> >
> > The underlying "issue" between the previous "GitHub/Maven releases" and
> > "Apache releases" was discussed at length long time ago. Basically,
> pushing
> > something to Maven Central is not a release. It is a "convenience
> service"
> > by the project, and is not at all required from Apache's point of view.
> > This fact may have some repercussions in how you approach the release.
> >
> > Perhaps it is possible to automate a bunch of this, for future podlings
> to
> > benefit from. And perhaps with help from someone who has experienced this
> > recently and have notes, infra could create a self-service portal for
> > setting it up.
> >
> > In Apache Polygene, we have gotten very far in terms of release
> automation,
> > but the initial steps are of course outside our scope. Probably after our
> > next release, we will publish reusable Gradle components for the Apache
> > release process for other Gradle based projects to benefit from. We'll
> see
> > exactly how we do this.
> >
>
> Agreed with all of the above.  In addition, the ASF parent pom is at
> https://svn.apache.org/repos/asf/maven/pom/trunk/asf/pom.xml which can
> have
> a lot more added to it.
>
> It strikes me though from reading your commentary, a lot of what you ran
> into is specific to how your project is setup.  RAT for instance, I
> wouldn't have ignored headers on README.md (it should have headers).
> Standard eclipse files should probably be excluded by default, since those
> are IDE generated values.  However in your case, if the file is in the
> release it should have a valid header.
>
> Release processes are interesting.  Given a similar set of developers, its
> surprisingly high how frequently release steps will differ between
> projects.  Even when it comes to a build.  Some projects like to have an
> explicit RAT check step, others like it with every build.  Different
> projects have different preferences and I think if we standardize it we'll
> start to stifle creativity.
>
>
>
>
> >
> > Cheers
> > Niclas
> >
> >
> > On Mon, Jan 9, 2017 at 1:12 AM, Edward Capriolo 
> > wrote:
> >
> > > On Sat, Jan 7, 2017 at 9:42 AM, John D. Ament 
> > > wrote:
> > >
> > > > On Sat, Jan 7, 2017 at 9:23 AM Niclas Hedhman 
> > > wrote:
> > > >
> > > > > On Sat, Jan 7, 2017 at 9:36 PM, John D. Ament <
> johndam...@apache.org
> > >
> > > > > wrote:
> > > > >
> > > > > > > So, instead of tying the "incubating" marker to "incubating", I
> > > would
> > > > > favor
> > > > > > > a system of marker(s) indicating the code maturity (incl
> legal).
> > > So,
> > > > > for a
> > > > > > > podling release to be 1.2.3 (a la Groovy), the same release
> > > standard
> > > > as
> > > > > > > TLPs are applied, but allow "alpha", "rc" or similar markers
> for
> > > > > podlings
> > > > > > > to "practice" releases. Probably not pushing those to mirrors,
> > but
> > > > > > > otherwise identical in "process" for podling to get their grips
> > on
> > > > the
> > > > > > > release process.
> > > > > > >
> > > > >
> > > > > > I think this is a fair point, and probably close to what podling
> > > > > > communities do (when its a fairly new codebase).  We often see
> > > releases
> > > > > in
> > > > > > the 0.x line, and in the 1+ lines.  Its up to the podling to
> > > determine
> > > > > how
> > > > > > mature they are from a release numbering standpoint.  I wouldn't
> > want
> > > > the
> > > > > > IPMC to enforce a versioning scheme.
> > > > > > It does however seem like a foundation wide versioning scheme may
> > > make
> > > > > > sense, or at least references to common references, e.g. semver,
> > may
> > > > make
> > > > > > sense as a recommendation to new podlings.
> > > > >
> > > > > Yeah, this is a tricky question. On one hand I don't like to
> dictate,
> > > but
> > > > > as a user I like to have a unified view of the world. Perhaps one
> or
> > > two
> > > > > DOAP entries would be a good way, and more strongly promote the
> DOAP
> > > and
> > > > > over time our common tooling could provide the unified view. A bit
> of
> > > > "be a
> > > > > good citizen for your own sake" attitude.
> > > > >
> > > > >
> > > > I'm not sure what you mean by DOAP entries.  Do you have an example?
> > > >
> > > > John
> > > >
> > > >
> > > >
> > > > >
> > > > > Cheers
> > > > > --
> > > > > Niclas Hedhman, Software Developer
> > > > > http://polygene.apache.org - New Energy for Java
> > > > >
> > > >
> > >
> > > But that pendulum has swung in the opposite direction, and podling
> > releases
> > > are now expected to be at ASF TLP levels.
> > >
> > 

Re: Committer for MXNet.

[Henri Yandell]

Thanks :)

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

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

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

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

Re: [DISCUSS] Proposing MXNet for the Apache Incubator

[Henri Yandell]

Added :)

On Fri, Jan 6, 2017 at 1:11 PM, Indhu Bharathi 
wrote:

> Please sign me up as a committer - I've been working with Mu at work on
> MXNet (Amazon) and would love to get more involved in the project.
> GitHub ID:  indhub
>
> Thanks,
> Indu
>
> On 2017-01-05 21:12 (-0800), Henri Yandell  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 

Re: [DISCUSS] Proposing MXNet for the Apache Incubator

[Henri Yandell]

Added :)

On Fri, Jan 6, 2017 at 10:59 AM, Naveen Swamy  wrote:

> Hello
>
> Please sign me up as a committer for MXNet - I've been working with Mu at
> work on MXNet (Amazon) and would love to get more involved in the project.
>
> *GitHub ID: nswamy*
>
>
> Thanks, Naveen
>
>
>
> On 2017-01-05 21:12 (-0800), Henri Yandell  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 

Re: [DISCUSS] Proposing MXNet for the Apache Incubator

[Joe Spisak]

Please sign me up as a committer - I've been working with Mu at work on MXNet 
(Amazon) and would love to get more involved in the project.

Github ID: jspisak

On 2017-01-05 21: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 

Re: [DISCUSS] Proposing MXNet for the Apache Incubator

[Mu Li]

Thanks, Henri.

The correct github link is https://github.com/dmlc/mxnet

On 2017-01-05 21: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 improving the documentation and code to help new
> developers get started quickly.

Re: [DISCUSS] Proposing MXNet for the Apache Incubator

[Indhu Bharathi]

Please sign me up as a committer - I've been working with Mu at work on MXNet 
(Amazon) and would love to get more involved in the project.
GitHub ID:  indhub

Thanks,
Indu

On 2017-01-05 21:12 (-0800), Henri Yandell  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
> 

Re: [DISCUSS] Proposing MXNet for the Apache Incubator

[Naveen Swamy]

Hello 

Please sign me up as a committer for MXNet - I've been working with Mu at work 
on MXNet (Amazon) and would love to get more involved in the project.

GitHub ID: nswamy

Thanks, Naveen 


-
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

[Naveen Swamy]

Hello

Please sign me up as a committer for MXNet - I've been working with Mu at
work on MXNet (Amazon) and would love to get more involved in the project.

*GitHub ID: nswamy*


Thanks, Naveen



On 2017-01-05 21:12 (-0800), Henri Yandell  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 

Committer for MXNet.

[Chris Olivier]

I would like to volunteer as a committer for MXNet.

-Chris Olivier
cjolivie...@gmail.com

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

Re: [DRAFT] Incubator PMC Board Report - January 2017

[Felix Meschberger]

Hi

Hmm, I see OpenWhisk missing here. I know the community had an edit last week 
and Matt tried to update …

Will check back with the poddling.

Regards
Felix

> Am 09.01.2017 um 02:05 schrieb John D. Ament :
> 
> All,
> 
> Below is the current draft of the IPMC board report.  Please review it for
> accurancy and make changes on https://wiki.apache.org/incubator/January2017
> if needed.
> 
> One call out - many podlings have very few mentor sign offs.  Would be good
> to get more mentors looking at the reports.
> 
> John
> 
> ---
> 
> 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
> 
>  Need Signoffs:
> 
>  - HAWQ
>  - Annotator
>  - Hivemall
>  - MADlib
>  - NetBeans
> 
> * Ready to graduate
> 
>  The Board has motions for the following:
> 
>  - Ranger?
> 
>  The following appear to be close from maturity model:
> 
>  - Airflow
>  - BatchEE
>  - FreeMarker
>  - Metron
> 
> * Did not report, expected next month
> 
>  - DataFu
>  - Milagro
>  - OpenWhisk
>  - SensSoft
> 
> 
> --
>   Table of Contents
> Airflow
> Annotator
> BatchEE
> FreeMarker
> Gossip
> HAWQ
> Hivemall
> HORN
> Juneau
> MADlib
> Metron
> Mynewt
> NetBeans
> ODF Toolkit
> 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
> 
> Shepherd/Mentor notes:
> 
> 
> 
> 
> Annotator
> 
> Annotator provides annotation enabling code for browsers, servers, and
> humans.
> 
> Annotator has been incubating since 2016-08-30.
> 
> Three