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

2017-01-07 Thread Joe Witt 
+1 binding

On Jan 7, 2017 2:20 PM, "Edward Zhang"  wrote:

> +1
> Glad to see Range will graduate!
>
> Thanks
> Edward
>
> On Sat, Jan 7, 2017 at 9:26 AM, Drew Farris  wrote:
>
> > +1 (binding)
> >
> > On Sat, Jan 7, 2017 at 12:56 AM Niclas Hedhman 
> wrote:
> >
> > > +1 (binding)
> > >
> > > On Sat, Jan 7, 2017 at 6:29 AM, Owen O'Malley 
> > wrote:
> > >
> > > > +1 (binding)
> > > >
> > > > On Wed, Jan 4, 2017 at 5:15 PM, Balaji Ganesan <
> > > balaji.ganesa...@gmail.com
> > > > >
> > > > wrote:
> > > >
> > > > > +1 Great to see the progress from the Ranger community.
> > > > >
> > > > > On Wed, Jan 4, 2017 at 4:54 PM, Suneel Marthi 
> > > > wrote:
> > > > >
> > > > > > +1 binding
> > > > > >
> > > > > > On Wed, Jan 4, 2017 at 5:48 PM, Ramesh Mani <
> rm...@hortonworks.com
> > >
> > > > > 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 > > > 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
> > >

Re: Request to join IPMC

2017-01-07 Thread Henry Saputra 
Markus,

Please send the request to private@incubator mailing list.

- Henry

On Fri, Jan 6, 2017 at 9:20 AM, Markus Weimer  wrote:

> Hi,
>
> I'm an Apache member and am already helping the Hivemall project as a
> mentor. It is about time I join the IPMC :)
>
> Thanks,
>
> Markus
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

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

2017-01-07 Thread Edward Zhang 
+1
Glad to see Range will graduate!

Thanks
Edward

On Sat, Jan 7, 2017 at 9:26 AM, Drew Farris  wrote:

> +1 (binding)
>
> On Sat, Jan 7, 2017 at 12:56 AM Niclas Hedhman  wrote:
>
> > +1 (binding)
> >
> > On Sat, Jan 7, 2017 at 6:29 AM, Owen O'Malley 
> wrote:
> >
> > > +1 (binding)
> > >
> > > On Wed, Jan 4, 2017 at 5:15 PM, Balaji Ganesan <
> > balaji.ganesa...@gmail.com
> > > >
> > > wrote:
> > >
> > > > +1 Great to see the progress from the Ranger community.
> > > >
> > > > On Wed, Jan 4, 2017 at 4:54 PM, Suneel Marthi 
> > > wrote:
> > > >
> > > > > +1 binding
> > > > >
> > > > > On Wed, Jan 4, 2017 at 5: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 > > 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
> > > > > >
> > > >

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

2017-01-07 Thread Drew Farris 
+1 (binding)

On Sat, Jan 7, 2017 at 12:56 AM Niclas Hedhman  wrote:

> +1 (binding)
>
> On Sat, Jan 7, 2017 at 6:29 AM, Owen O'Malley  wrote:
>
> > +1 (binding)
> >
> > On Wed, Jan 4, 2017 at 5:15 PM, Balaji Ganesan <
> balaji.ganesa...@gmail.com
> > >
> > wrote:
> >
> > > +1 Great to see the progress from the Ranger community.
> > >
> > > On Wed, Jan 4, 2017 at 4:54 PM, Suneel Marthi 
> > wrote:
> > >
> > > > +1 binding
> > > >
> > > > On Wed, Jan 4, 2017 at 5: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 > 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
> >

Re: Request to join IPMC

2017-01-07 Thread Tsuyoshi Ozawa 
+1 (non-binding)

Markus helps us when making Hivemall the Apache Incubator podling. He
is also PPMC of Apache REEF project. His record is enough to become
IPMC.

Thanks,
- Tsuyoshi

On Sat, Jan 7, 2017 at 2:20 AM, Markus Weimer  wrote:
> Hi,
>
> I'm an Apache member and am already helping the Hivemall project as a
> mentor. It is about time I join the IPMC :)
>
> Thanks,
>
> Markus
>
> -
> 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: [VOTE] Drop incubating requirement of Maven artifacts

2017-01-07 Thread John D. Ament 
On Sat, Jan 7, 2017 at 9:23 AM Niclas Hedhman  wrote:

> On Sat, Jan 7, 2017 at 9:36 PM, John D. Ament 
> 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
>

Re: [VOTE] Drop incubating requirement of Maven artifacts

2017-01-07 Thread Niclas Hedhman 
On Sat, Jan 7, 2017 at 9:36 PM, John D. Ament  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.


Cheers
--
Niclas Hedhman, Software Developer
http://polygene.apache.org - New Energy for Java

Re: [VOTE] Drop incubating requirement of Maven artifacts

2017-01-07 Thread John D. Ament 
Niclas,

I wanted to read through your notes pretty in depth before responding.

On Thu, Jan 5, 2017 at 7:37 PM Niclas Hedhman  wrote:

> Coming late to the party...
>
> This has been discussed, and contentious, since "forever". A long time ago,
> there was a notion that a podling release was not an ASF release (which was
> the main reason for the "incubating" marker in all release and support
> artifacts. But that pendulum has swung in the opposite direction, and
> podling releases are now expected to be at ASF TLP levels.
>
>
Thank you for acknowledging this.


> Pierre pointed out that "incubating" refers to community and not code, but
> we don't release a community, we release code. I think this is an important
> fact.
>
> 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.


>
> So, I am +1 with John's "something is broken" observation, although I also
> agree with the many "-1"s that think there is value to the public here.
>
>
> Cheers
>
> On Wed, Jan 4, 2017 at 7:47 PM, John D. Ament 
> wrote:
>
> > I'll point out that this is a cancel thread..., I'm fine if people want
> to
> > continue chatting in here, but I started a new discussion on
> > https://lists.apache.org/thread.html/15550f5bf622ae3070b558505c8a0f
> > d0ce3b23df3012d57de8b6d9f3@%3Cgeneral.incubator.apache.org%3E
> >
> > I'll try to answer questions I saw pop up
> >
> > Mark Struberg: No, ignoring commons/log4j for a minute, other projects
> > continue to work under legacy maven coordinates.  Includes one i already
> > linked to - groovy, also freemarker, zest/polygene (a project that went
> > straight to TLP).  There's neither foundation policy nor legal impact by
> > using other very similar marks, especially when the project's name hasn't
> > changed.  Publishing under "com.oracle.someProduct" would probably be bad
> > from a marks standpoint since it shows as property of some other company,
> > whereas former foundations or completely independent projects.  Plus, the
> > way maven central works you own the entire tld, except for cases where
> its
> > a known third party publisher.  For instance, I own (personally) the
> domain
> > name ament.ws and have access to publish under maven coordinates
> > ws.ament.*.  Github users have to request io.github.themselves
> manually.  I
> > assume that something similar exists between the ASF and Sonatype to
> enable
> > publishing under org.apache, and ensure that no one else can use
> > org.apache.
> >
> > Pierre Smits: This is something I expected to be a hot topic.  So while
> > 100% consensus isn't expected, a clear path forward is something to
> expect,
> > even if not everyone is happy about the outcome.  FWIW, there seem to be
> 3
> > different POVs (that I could identify) on those who were against the
> idea:
> >
> > - Those who thought this was dropping -incubating from the Apache release
> > archive.
> > - Those who acknowledged that this was maven specific and felt it should
> > continue as is.
> > - Those who acknowledged that this was currently maven specific and
> should
> > be made broader.
> >
> > John
> >
> >
> > On Wed, Jan 4, 2017 at 4:49 AM Martijn Dashorst <
> > martijn.dasho...@gmail.com>
> > wrote:
> >
> > > Late to the party, but having a long think about this is sometimes
> > > beneficial.
> > >
> > > +1 to drop the -incubator/-incubating version attachment for any
> > > artifacts (not just Maven).
> > >
> > > My reasoning is the following:
> > >
> > > Source code lives longer than any community. Long after a podling has
> > > gone through the incubator, the code remains. The releases remain. How
> > > a community conducts itself doesn't reflect on the released code. Code
> > > just exists.
> > >
> > > While it is important for current users coming to a project to know
> > > the status of the community, does it really matter if the code is in
> > > incubation or has graduated? Does that matter in 5 years whether the
> > > code of foo-1.2 was incubating while the community has graduated and
> > > now resides in the

Re: [DISCUSS] Proposing MXNet for the Apache Incubator

2017-01-07 Thread Sebastian 

Great to see you join our efforts!

On 06.01.2017 18:20, Markus Weimer wrote:

On 2017-01-05 9:12 PM, Henri Yandell wrote:

I'd like to propose a new incubator Apache MXNet podling.


Awesome! If you still need a mentor, feel free to sign me up!

Markus

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



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

Re: [VOTE] Drop incubating requirement of Maven artifacts

2017-01-07 Thread Pierre Smits 
Hi Niclas,

You Saïd it correctly

It is an education program.

Best regards,

Pierre

On Saturday, January 7, 2017, Niclas Hedhman  wrote:

> Pierre,
> Where can I download or "consume" a project community? I would like to have
> a local copy of it, right here. ;-)
>
> Communities are living things, people, and not an immutable release
> artifact. Incubation is not a release process, it is effectively an
> education program for inexperienced people by experienced people, passing
> the baton of collective knowledge. Sorry, but I simply fail to equate this
> with the release process of "open source software for the public good", I
> think the analogy is too thin.
>
> Cheers
>
> On Sat, Jan 7, 2017 at 4:42 AM, Pierre Smits  > wrote:
>
> > Nicolas, all,
> >
> > Despite your believes, you do release communities. Because the community
> is
> > the incubating project. Only after the community meets the criteria of
> > graduation a proposal is submitted, seconded by the IPMC and reviewed by
> > the board. The community works the code during incubation until it
> > consistently meets just one (small set) of the graduation criteria
> > (compliance to ASF rules). But all the other aspects (community size,
> > diversity and interaction) are far more important for the success, given
> > the principle Community over Code.
> >
> > Otherwise, your suggestion to use the same standards for releasing as tlp
> > (released communities) and the examples brought forward look very sound
> and
> > acceptable.
> >
> > Best regards,
> >
> > Pierre Smits
> >
> > ORRTIZ.COM 
> > OFBiz based solutions & services
> >
> > OFBiz Extensions Marketplace
> > http://oem.ofbizci.net/oci-2/
> >
> > On Fri, Jan 6, 2017 at 1:37 AM, Niclas Hedhman  > wrote:
> >
> > > Coming late to the party...
> > >
> > > This has been discussed, and contentious, since "forever". A long time
> > ago,
> > > there was a notion that a podling release was not an ASF release (which
> > was
> > > the main reason for the "incubating" marker in all release and support
> > > artifacts. But that pendulum has swung in the opposite direction, and
> > > podling releases are now expected to be at ASF TLP levels.
> > >
> > > Pierre pointed out that "incubating" refers to community and not code,
> > but
> > > we don't release a community, we release code. I think this is an
> > important
> > > fact.
> > >
> > > 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.
> > >
> > > So, I am +1 with John's "something is broken" observation, although I
> > also
> > > agree with the many "-1"s that think there is value to the public here.
> > >
> > >
> > > Cheers
> > >
> > > On Wed, Jan 4, 2017 at 7:47 PM, John D. Ament  >
> > > wrote:
> > >
> > > > I'll point out that this is a cancel thread..., I'm fine if people
> want
> > > to
> > > > continue chatting in here, but I started a new discussion on
> > > > https://lists.apache.org/thread.html/15550f5bf622ae3070b558505c8a0f
> > > > d0ce3b23df3012d57de8b6d9f3@%3Cgeneral.incubator.apache.org%3E
> > > >
> > > > I'll try to answer questions I saw pop up
> > > >
> > > > Mark Struberg: No, ignoring commons/log4j for a minute, other
> projects
> > > > continue to work under legacy maven coordinates.  Includes one i
> > already
> > > > linked to - groovy, also freemarker, zest/polygene (a project that
> went
> > > > straight to TLP).  There's neither foundation policy nor legal impact
> > by
> > > > using other very similar marks, especially when the project's name
> > hasn't
> > > > changed.  Publishing under "com.oracle.someProduct" would probably be
> > bad
> > > > from a marks standpoint since it shows as property of some other
> > company,
> > > > whereas former foundations or completely independent projects.  Plus,
> > the
> > > > way maven central works you own the entire tld, except for cases
> where
> > > its
> > > > a known third party publisher.  For instance, I own (personally) the
> > > domain
> > > > name ament.ws and have access to publish under maven coordinates
> > > > ws.ament.*.  Github users have to request io.github.themselves
> > > manually.  I
> > > > assume that something similar exists between the ASF and Sonatype to
> > > enable
> > > > publishing under org.apache, and ensure that no one else can use
> > > > org.apache.
> > > >
> > > > Pierre Smits: This is something I expected to be a hot topic.  So
> while
> > > > 100%