Re: [ANNOUNCE] Six new Incubator PMC members

[Luke Han]

Welcome


Best Regards!
-

Luke Han

On Sat, Nov 7, 2015 at 2:17 PM, Jean-Baptiste Onofré 
wrote:

> Welcome aboard guys !
>
> Regards
> JB
>
>
> On 11/07/2015 05:43 AM, Marvin Humphrey wrote:
>
>> Greetings,
>>
>> I'm delighted to welcome six new members of the Incubator PMC!
>>
>> *   Tom Barber (magicaltrout), PMC Chair of OODT.
>> *   Patrick Wendell (pwendell), PMC member of Spark and committer
>>  on Avro and Flume.
>> *   Reynold Xin (rxin), PMC member of Spark.
>> *   Phil Sorber (sorber), PMC member for TrafficServer.
>> *   Julien Le Dem (julien), PMC Chair of Parquet, PMC member of Pig and
>> Tez.
>> *   Jacques Nadeau (jacques), PMC Chair of Drill, PMC member of Calcite.
>>
>> Welcome aboard -- we can't wait to see how you will help our podling
>> communities succeed!
>>
>> Marvin Humphrey
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

RE: Concerning Sentry: A disagreement over the Apache Way and graduation

[Dennis E. Hamilton]

> -Original Message-
> From: Branko Čibej [mailto:br...@apache.org]
> Sent: Saturday, November 7, 2015 09:29
> To: general@incubator.apache.org
> Subject: Re: Concerning Sentry: A disagreement over the Apache Way and
> graduation
> 
> On 03.11.2015 09:48, Bertrand Delacretaz wrote:
[ ... ]
> > Based on the information provided in this thread It looks to me like
> > Sentry isn't operating according to items CO20, CO40, CS20 and CS50 of
> > our maturity model [1].
> 

[ ... ]
> Can we please stop calling someone's pet paperwork "our maturity model?"
> I'm fed up to the gills with the assumption that it has any relevance
> for anything or anyone in the foundation, including the Incubator and
> Podlings.
> 
> -- Brane

[orcmid] 

Huh?  The development of this document, 



was carried out on the dev community list over a significant period of time.  
It even provides an account for that development and where related materials 
can be found.  It is a work in progress, as is the ASF itself.  As far as I can 
tell, being a tender-foot in these parts, this is a distillation of a great 
deal of thinking and consideration based on serious consideration by 
contributors with substantial experience.  

I find the dismissing of that effort to be very peculiar as part of a 
discussion about The Apache Way.

It is easy to find evidence that this is relevant to several someones in the 
foundation, including in the Incubator and Podlings.  Apparently, some other 
someones have not been paying attention or simply haven't taken it seriously.  
That happens.

I do agree that a list of codes without any context is probably not a very 
gentle application of it as part of an assessment of a podling's readiness to 
graduate.  

> 
> 
> -
> 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: Concerning Sentry: A disagreement over the Apache Way and graduation

[Dennis E. Hamilton]

If the mentor brought the considerations to a podling for them to reconcile
and record, that would be great.  If that were guidance to mentors, that
would be great also.

What concerns me is that podlings of newly-arrived initial committers may
tend to see whatever the practice that is suggested to them as being gospel
and this is carried from one PPMC to another.

I have seen too much customization too early and there is then not even some
sort of common practice that can be used even as training wheels.  It is
like trying to improvise jazz when you take your first instrument out of the
box.  

Bothers me.  YMMV [;<).

> -Original Message-
> From: Ross Gardler [mailto:ross.gard...@microsoft.com]
> Sent: Saturday, November 7, 2015 12:58
> To: general@incubator.apache.org; dennis.hamil...@acm.org
> Subject: RE: Concerning Sentry: A disagreement over the Apache Way and
> graduation
> 
> There should be no recommendation for podlings. Mentors should guide the
> podling to making the right decision for their community by discussing
> the pros and cons of each model.
> 
> The idea of a mentor bringing their preference, or worse the IPMC having
> a "default" is problematic.
> 
> Sent from my Windows Phone
> 
> From: Dennis E. Hamilton
> Sent: ‎11/‎6/‎2015 9:35 AM
> To: general@incubator.apache.org
> Subject: RE: Concerning Sentry: A disagreement over the Apache Way and
> graduation
> 
> I think there is a difference between what TLPs do and what the
> recommended approach for Podlings is.
> 
> My impression, based on limited podling experience, is that the default
> tends to be PPMC == committer.
> 
> Thanks for raising the notion of looking at why committers are *not*
> moved to the PMC of a TLP after some period of time, though.  My
> question, as a PMC member, would be whether or not we are holding the
> reins too tight at the expense of both community and sustainability.  An
> useful danger sign, that.
> 
>  - Dennis
> 
> > -Original Message-
> > From: Greg Reddin [mailto:gred...@gmail.com]
> > Sent: Friday, November 6, 2015 06:22
> > To: general@incubator.apache.org
> > Subject: Re: Concerning Sentry: A disagreement over the Apache Way and
> > graduation
> >
> > On Fri, Nov 6, 2015 at 7:58 AM, Rich Bowen  wrote:
> > > On 11/05/2015 12:02 AM, Joe Schaefer wrote:
> > >> Committership is the right to do work on the project. PMC
> membership
> > is the
> > >> right to participate in governance.  People left in the nebulous
> > state
> > >> between
> > >> committership and PMC membership for long periods of time more than
> > likely
> > >> will give up in frustration for not being trusted enough to govern
> > their
> > >> own work.
> > >
> > >
> > > Most of the older projects at the Foundation do not have PMC ==
> > > Committer. Notably, httpd. The notion that committers are
> > automatically
> > > PMC is a fairly new innovation. As it happens, it's an innovation
> that
> > I
> > > wholeheartedly support and recommend, but it's a minority of
> projects
> > > that have this policy. If you follow board reports, you'll notice
> that
> > > PMC additions and Committer additions are seldom coincident.
> >
> > In further support of Joe's point, for most of the projects I've been
> > involved with, the PMC promotion was almost automatic and occurred
> > within about 6 months of committership. The committer-only period was
> > just a probationary period to make sure a person was not going to
> > abuse his/her privileges. An invite to committership comes with an
> > unspoken assumption that we want you to help govern the project, but
> > let's start with giving you access. I don't know that I ever saw
> > anyone stay as committer-only for an extended period of time.
> >
> > Greg
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org



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

Re: Project Website Template

[Ted Dunning]

Easy is good


The Jekyll work flow has worked well in the project I have mentored.  

Sent from my iPhone

> On Nov 7, 2015, at 10:04, Luciano Resende  wrote:
> 
> I have just spent a day or so building a new podling website based on
> Jekyll and I tried to model it as a template, where a new project/podling
> can easily modify _data/project.yml and configure it's name, dev list, user
> list, jira, source repository, etc.
> 
> I was wondering if this would be good as a "template" where new projects
> that come on board could easily fork to start their website and just change
> the styles and contents of main page, and voila, the site would be ready,
> with all the required trademarks and other apache requirements, etc
> 
> Thoughts ?
> 
> -- 
> Luciano Resende
> http://people.apache.org/~lresende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/

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

RE: Concerning Sentry: A disagreement over the Apache Way and graduation

[Ross Gardler]

There should be no recommendation for podlings. Mentors should guide the 
podling to making the right decision for their community by discussing the pros 
and cons of each model.

The idea of a mentor bringing their preference, or worse the IPMC having a 
"default" is problematic.

Sent from my Windows Phone

From: Dennis E. Hamilton
Sent: ‎11/‎6/‎2015 9:35 AM
To: general@incubator.apache.org
Subject: RE: Concerning Sentry: A disagreement over the Apache Way and 
graduation

I think there is a difference between what TLPs do and what the recommended 
approach for Podlings is.

My impression, based on limited podling experience, is that the default tends 
to be PPMC == committer.

Thanks for raising the notion of looking at why committers are *not* moved to 
the PMC of a TLP after some period of time, though.  My question, as a PMC 
member, would be whether or not we are holding the reins too tight at the 
expense of both community and sustainability.  An useful danger sign, that.

 - Dennis

> -Original Message-
> From: Greg Reddin [mailto:gred...@gmail.com]
> Sent: Friday, November 6, 2015 06:22
> To: general@incubator.apache.org
> Subject: Re: Concerning Sentry: A disagreement over the Apache Way and
> graduation
>
> On Fri, Nov 6, 2015 at 7:58 AM, Rich Bowen  wrote:
> > On 11/05/2015 12:02 AM, Joe Schaefer wrote:
> >> Committership is the right to do work on the project. PMC membership
> is the
> >> right to participate in governance.  People left in the nebulous
> state
> >> between
> >> committership and PMC membership for long periods of time more than
> likely
> >> will give up in frustration for not being trusted enough to govern
> their
> >> own work.
> >
> >
> > Most of the older projects at the Foundation do not have PMC ==
> > Committer. Notably, httpd. The notion that committers are
> automatically
> > PMC is a fairly new innovation. As it happens, it's an innovation that
> I
> > wholeheartedly support and recommend, but it's a minority of projects
> > that have this policy. If you follow board reports, you'll notice that
> > PMC additions and Committer additions are seldom coincident.
>
> In further support of Joe's point, for most of the projects I've been
> involved with, the PMC promotion was almost automatic and occurred
> within about 6 months of committership. The committer-only period was
> just a probationary period to make sure a person was not going to
> abuse his/her privileges. An invite to committership comes with an
> unspoken assumption that we want you to help govern the project, but
> let's start with giving you access. I don't know that I ever saw
> anyone stay as committer-only for an extended period of time.
>
> Greg
>
> -
> 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: Concerning Sentry: A disagreement over the Apache Way and graduation

[Greg Stein]

On Sat, Nov 7, 2015 at 1:07 PM, Dennis E. Hamilton 
wrote:
>...

> Huh?  The development of this document,
>
>  >
>
> was carried out on the dev community list over a significant period of
> time.  It even provides an account for


And that is the key part: written by the ComDev community. Not the
Foundation. I believe Brane shares my fear that the document will become a
de facto standard/requirement across the ASF.

Should mentors and podlines want to use it as a guide for things to
consider... great.

But some of us will push back, if it appears it is being used as a
yardstick, rather than a guide.

Cheers,
-g

Project Website Template

[Luciano Resende]

I have just spent a day or so building a new podling website based on
Jekyll and I tried to model it as a template, where a new project/podling
can easily modify _data/project.yml and configure it's name, dev list, user
list, jira, source repository, etc.

I was wondering if this would be good as a "template" where new projects
that come on board could easily fork to start their website and just change
the styles and contents of main page, and voila, the site would be ready,
with all the required trademarks and other apache requirements, etc

Thoughts ?

-- 
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Concerning Sentry: A disagreement over the Apache Way and graduation

[Branko Čibej]

On 03.11.2015 09:48, Bertrand Delacretaz wrote:
> On Mon, Nov 2, 2015 at 11:11 PM, Joe Brockmeier  wrote:
>> ...Sentry started with 24 committers/PPMC. It hasn't added any PPMC members
>> since its inception...
> If that's correct I'm -1 on graduating Sentry.
>
> and earlier he wrote:
>> ..The model that Sentry is pursing may work very well *for the existing
>> members of the podling.* In my opinion, its process is entirely too
>> opaque to allow for interested parties outside of the existing podling
>> and companies interested in Sentry development to become involved...
> Not having added any PPMC members seems to confirm that.
>
> Based on the information provided in this thread It looks to me like
> Sentry isn't operating according to items CO20, CO40, CS20 and CS50 of
> our maturity model [1].

Can we please stop calling someone's pet paperwork "our maturity model?"
I'm fed up to the gills with the assumption that it has any relevance
for anything or anyone in the foundation, including the Incubator and
Podlings.

-- Brane


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

Re: Project Website Template

[larry mccay]

+1 - this would be a great resource for bootstrapping a new project!

On Sat, Nov 7, 2015 at 5:35 PM, Julian Hyde  wrote:

> +1
>
> I had the same thought when I built Calcite’s site based on jekyll
> (actually cloned from Orc’s site). Thanks for making this template — I’m
> sure it will be helpful to new projects.
>
> We should make it clear that it is optional, of course. But when Calcite
> entered the incubator there were entirely too many choices (and
> opportunities to make mistakes). The whole svnpubsub vs cms question, for
> instance, delayed our web site by about 6 months because we weren’t sure
> whether we could backtrack once we had made a decision. So I think it would
> be useful if there were some default choices to get incubator projects off
> and running quickly.
>
> I also think it would be useful to provide a template for maven/java based
> projects. There would be a pom.xml, module/pom.xml and
> module/org/apache/foo/Foo.java, and just enough content in the pom.xml to
> be able to make a release by typing “mvn release:prepare … mvn
> release:perform”. If anyone is interested I’ll do it.
>
> Luciano, Did you have a place in mind to put your template site? I think
> it would need to be in an apache project, not in github, so that any
> podling can import it without worrying about IP contamination.
>
> Julian
>
>
>
> > On Nov 7, 2015, at 1:21 PM, Ted Dunning  wrote:
> >
> >
> > Easy is good
> >
> >
> > The Jekyll work flow has worked well in the project I have mentored.
> >
> > Sent from my iPhone
> >
> >> On Nov 7, 2015, at 10:04, Luciano Resende  wrote:
> >>
> >> I have just spent a day or so building a new podling website based on
> >> Jekyll and I tried to model it as a template, where a new
> project/podling
> >> can easily modify _data/project.yml and configure it's name, dev list,
> user
> >> list, jira, source repository, etc.
> >>
> >> I was wondering if this would be good as a "template" where new projects
> >> that come on board could easily fork to start their website and just
> change
> >> the styles and contents of main page, and voila, the site would be
> ready,
> >> with all the required trademarks and other apache requirements, etc
> >>
> >> Thoughts ?
> >>
> >> --
> >> Luciano Resende
> >> http://people.apache.org/~lresende
> >> http://twitter.com/lresende1975
> >> http://lresende.blogspot.com/
> >
> > -
> > 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
>
>

[VOTE] Release Apache Kylin 1.1.1 (incubating)

[ShaoFeng Shi]

Hi all,

The Apache Kylin community has voted on and approved a proposal to release
Apache Kylin 1.1.1-incubating. This release only includes license cleanup,
no Java code change; For more information please check KYLIN-999.

Proposal:
http://s.apache.org/kylin-1.1.1-vote_rc1

Vote result:
7 binding +1 votes
9 non-binding +1 votes
No -1 votes
http://s.apache.org/kylin-1.1.1-result_rc1


The commit to be voted upon:
https://github.com/apache/incubator-kylin/commit/708ea38d7f764048e67e8e1ee8a13955983d12ba

Its hash is 708ea38d7f764048e67e8e1ee8a13955983d12ba.

The artifacts to be voted on are located here:
https://dist.apache.org/repos/dist/dev/incubator/kylin/apache-kylin-1.1.1-incubating-rc1/

The hashes of the artifacts are as follows:
apache-kylin-1.1.1-incubating-src.tar.gz.md5
ff942b2eba870b04552bc8c8dace5517
apache-kylin-1.1.1-incubating-src.tar.gz.sha1
cc8990ba7821b02f4bf6da5f870b30a915881535

A staged Maven repository is available for review at:
https://repository.apache.org/content/repositories/orgapachekylin-1013/

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

Pursuant to the Releases section of the Incubation Policy and with
the endorsement of our mentors we would now like to request
the permission of the Incubator PMC to publish the release. The vote
is open for 72 hours, or until the necessary number of votes (3 +1)
is reached.

[ ] +1 Release this package
[ ]  0 I don't feel strongly about it, but I'm okay with the release
[ ] -1 Do not release this package because...


Shaofeng Shi, on behalf of Apache Kylin PPMC
shaofeng...@apache.org

Re: Project Website Template

[Julian Hyde]

+1 

I had the same thought when I built Calcite’s site based on jekyll (actually 
cloned from Orc’s site). Thanks for making this template — I’m sure it will be 
helpful to new projects.

We should make it clear that it is optional, of course. But when Calcite 
entered the incubator there were entirely too many choices (and opportunities 
to make mistakes). The whole svnpubsub vs cms question, for instance, delayed 
our web site by about 6 months because we weren’t sure whether we could 
backtrack once we had made a decision. So I think it would be useful if there 
were some default choices to get incubator projects off and running quickly.

I also think it would be useful to provide a template for maven/java based 
projects. There would be a pom.xml, module/pom.xml and 
module/org/apache/foo/Foo.java, and just enough content in the pom.xml to be 
able to make a release by typing “mvn release:prepare … mvn release:perform”. 
If anyone is interested I’ll do it.

Luciano, Did you have a place in mind to put your template site? I think it 
would need to be in an apache project, not in github, so that any podling can 
import it without worrying about IP contamination.

Julian



> On Nov 7, 2015, at 1:21 PM, Ted Dunning  wrote:
> 
> 
> Easy is good
> 
> 
> The Jekyll work flow has worked well in the project I have mentored.  
> 
> Sent from my iPhone
> 
>> On Nov 7, 2015, at 10:04, Luciano Resende  wrote:
>> 
>> I have just spent a day or so building a new podling website based on
>> Jekyll and I tried to model it as a template, where a new project/podling
>> can easily modify _data/project.yml and configure it's name, dev list, user
>> list, jira, source repository, etc.
>> 
>> I was wondering if this would be good as a "template" where new projects
>> that come on board could easily fork to start their website and just change
>> the styles and contents of main page, and voila, the site would be ready,
>> with all the required trademarks and other apache requirements, etc
>> 
>> Thoughts ?
>> 
>> -- 
>> Luciano Resende
>> http://people.apache.org/~lresende
>> http://twitter.com/lresende1975
>> http://lresende.blogspot.com/
> 
> -
> 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: [DISCUSS] Graduate REEF

[Markus Weimer]

On 2015-11-06 09:22, Marvin Humphrey wrote:

I checked over the resolution and it looks good except for one thing
I'm not certain about -- the two scope statements don't agree
precisely.  One speaks of "a software framework" and the other, "ease
of development":


Excellent find. We'll harmonize that before calling a [VOTE].

Markus

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

Re: Project Website Template

[Luciano Resende]

On Sat, Nov 7, 2015 at 7:35 PM, Julian Hyde  wrote:

> +1
>
> I had the same thought when I built Calcite’s site based on jekyll
> (actually cloned from Orc’s site). Thanks for making this template — I’m
> sure it will be helpful to new projects.
>
> We should make it clear that it is optional, of course. But when Calcite
> entered the incubator there were entirely too many choices (and
> opportunities to make mistakes). The whole svnpubsub vs cms question, for
> instance, delayed our web site by about 6 months because we weren’t sure
> whether we could backtrack once we had made a decision. So I think it would
> be useful if there were some default choices to get incubator projects off
> and running quickly.
>

Exactly, it will be optional, and the goal is to document exactly what a
new project (and sometimes a completely new community) needs to do to get
the website up and running, including the whole workflow, and what to
request from infra.


>
> I also think it would be useful to provide a template for maven/java based
> projects. There would be a pom.xml, module/pom.xml and
> module/org/apache/foo/Foo.java, and just enough content in the pom.xml to
> be able to make a release by typing “mvn release:prepare … mvn
> release:perform”. If anyone is interested I’ll do it.
>

I believe this is already available if your "parent pom" inherit from
"apache pom".
See: http://svn.apache.org/repos/asf/maven/pom/tags/apache-17/


>
> Luciano, Did you have a place in mind to put your template site? I think
> it would need to be in an apache project, not in github, so that any
> podling can import it without worrying about IP contamination.
>
>
I was thinking on a git repository owned by incubator. It would be mirrored
in github mostly for the simplification of collaboration via PR.

When a new projects comes in, it would request a new website git as a fork
from the template, so that in the future it would be able to cherry-pick
enhancements or fixes from upstream.


> Julian
>
>
>
Thoughts ?



-- 
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/