Re: [graduation] Maturity model-based assessment of Groovy for its graduation

If we are to use the maturity model as the guideline regarding podling graduation, then certainly the model should be voted on and approved by the membership as *the* model for the ASF, right? Basically, it looks to me that the model is proposing and creating policy, and this is something that

Re: Mentor disengagement - a suggestion

On Thu, Oct 15, 2015 at 3:24 AM, Bertrand Delacretaz wrote: > On Thu, Oct 15, 2015 at 12:24 AM, Martijn Dashorst > wrote: >> ...we should >> strive to make incubation take not longer than a year or so. Or when >> incubation takes longer, have a

Re: [graduation] Maturity model-based assessment of Groovy for its graduation

As someone who is going through incubation right now, I think I would have liked to have been looking at the maturity model from day 1 of incubation. On Thu, Oct 15, 2015 at 8:30 AM, Bertrand Delacretaz wrote: > On Thu, Oct 15, 2015 at 2:21 PM, Jim Jagielski

Re: [graduation] Maturity model-based assessment of Groovy for its graduation

Le 15/10/15 11:46, Bertrand Delacretaz a écrit : > Hi Incubator PMC, > > FYI I have started an experiment at > https://github.com/apache/incubator-groovy/blob/master/MATURITY.adoc , > using our maturity model to evaluate Groovy before its mentors suggest > its graduation (which should happen very

Re: [graduation] Maturity model-based assessment of Groovy for its graduation

On Thu, Oct 15, 2015 at 12:14 PM, Emmanuel Lécharny wrote: > ...I do think > that an audit of all the existing TLP should be done in the next month > to check if all the iterms are correctly fullfiled That would be interesting but that's 167 TLPs if my memory is

Re: [graduation] Maturity model-based assessment of Groovy for its graduation

Le 15/10/15 13:49, Bertrand Delacretaz a écrit : > On Thu, Oct 15, 2015 at 12:14 PM, Emmanuel Lécharny > wrote: >> ...I do think >> that an audit of all the existing TLP should be done in the next month >> to check if all the iterms are correctly fullfiled > That would

Re: [graduation] Maturity model-based assessment of Groovy for its graduation

On Thu, Oct 15, 2015 at 2:21 PM, Jim Jagielski wrote: > ...If we are to use the maturity model as the guideline regarding podling > graduation, then certainly the model should be voted on and approved > by the membership as *the* model for the ASF, right?... That would be good

Re: [graduation] Maturity model-based assessment of Groovy for its graduation

A huge +1, but I wonder about a few things. Who does the work? Who evaluates the results? What happens when projects "fail"? Le 15/10/15 11:46, Bertrand Delacretaz a écrit : > Hi Incubator PMC, > > FYI I have started an experiment at >

Re: structural reform- division of labor

The incubator is a very large committee with a lot of moving parts. To pick an example off the top of my head, let's look at the mentoring situation. What we generally do with new mentors is say hey so and so I trust you will do a good job of watching over this podling for us. What we don't

Re: Mentor disengagement - a suggestion

On Thu, Oct 15, 2015 at 12:24 AM, Martijn Dashorst wrote: > ...we should > strive to make incubation take not longer than a year or so. Or when > incubation takes longer, have a plan to switch mentors, perhaps a new > mentor might bring a new graduation spirit into the

Re: Mentor disengagement - a suggestion

On Wed, Oct 14, 2015 at 3:15 PM, Marko Rodriguez wrote: > ...Once we got one of our mentors engaged -- Daniel Gruno -- its been smooth > sailing. You > know how we got him engaged? HipChat. He set us up an account and now we > can "@Humbedooh" with questions and get

Re: structural reform- division of labor

On Thu, Oct 15, 2015 at 5:05 AM, Joe Schaefer wrote: > ...Formally, that's all a working group needs to be- yet another mailing > list I'm not in favor of more mailing lists, I think [tags] in subject lines can pretty much do the same thing without splitting

[graduation] Maturity model-based assessment of Groovy for its graduation

Hi Incubator PMC, FYI I have started an experiment at https://github.com/apache/incubator-groovy/blob/master/MATURITY.adoc , using our maturity model to evaluate Groovy before its mentors suggest its graduation (which should happen very soon). So far this has helped uncover a few issues that we

Re: structural reform- division of labor

That's certainly a reasonable approach, but it doesn't quite capture what I'm talking about when I mention the concept of having individual working groups to do more focused collaboration on specific areas of work activity.  Where these conversations take place isn't really all that important,

Re: [graduation] Maturity model-based assessment of Groovy for its graduation

Le 15/10/15 16:28, Filip Hanik a écrit : > On Thursday, October 15, 2015, Emmanuel Lécharny > wrote: > >> Le 15/10/15 13:17, Rich Bowen a écrit : >>> A huge +1, but I wonder about a few things. Who does the work? >> I guess that each PMC should be responsible for this work,

Re: [graduation] Maturity model-based assessment of Groovy for its graduation

> On Oct 15, 2015, at 10:03 AM, Rich Bowen wrote: > > > > On 10/15/2015 08:21 AM, Jim Jagielski wrote: >> If we are to use the maturity model as the guideline regarding podling >> graduation, then certainly the model should be voted on and approved >> by the membership as

Re: [graduation] Maturity model-based assessment of Groovy for its graduation

Hi, On Thu, Oct 15, 2015 at 3:11 PM, Stephen Mallette wrote: > ...As someone who is going through incubation right now, I think I would have > liked to have been looking at the maturity model from day 1 of incubation... Yes, that would be nice IMO. As that's quite a new

RE: structural reform- division of labor

+1 -Original Message- From: Bertrand Delacretaz [mailto:bdelacre...@apache.org] Sent: Thursday, October 15, 2015 00:39 To: Incubator General ; Joe Schaefer Subject: Re: structural reform- division of labor On Thu, Oct 15, 2015 at

Re: [graduation] Maturity model-based assessment of Groovy for its graduation

On 10/15/2015 08:21 AM, Jim Jagielski wrote: If we are to use the maturity model as the guideline regarding podling graduation, then certainly the model should be voted on and approved by the membership as *the* model for the ASF, right? Basically, it looks to me that the model is proposing

Re: [graduation] Maturity model-based assessment of Groovy for its graduation

On Thursday, October 15, 2015, Emmanuel Lécharny wrote: > Le 15/10/15 13:17, Rich Bowen a écrit : > > A huge +1, but I wonder about a few things. Who does the work? > > I guess that each PMC should be responsible for this work, with a dead > line soft enough that it allows

Re: [VOTE] Graduate Apache Kylin from the Apache Incubator

+1 2015-10-16 9:17 GMT+08:00 Andrew Purtell : > +1 (binding) > > On Thu, Oct 15, 2015 at 4:59 PM, Luke Han wrote: > > > The Apache Kylin community and project made significant advances during > the > > incubating (from Nov 2014) and > > believes it is

[Vote] Graduate Kylin from the Apache Incubator

The Kylin community and project made significant advances during the incubating (from Nov 2014) and believes it is ready to graduate as a top-level project. The Apache Kylin is very active. The PPMC doubled in size (added 6 committers and 2 mentors) and increased diversity in the past year.

Re: [DISCUSS] Graduate Kylin from the Apache Incubator

Apache Kylin's name search has been approved, will raise vote now. Thanks. Best Regards! - Luke Han On Sun, Oct 11, 2015 at 9:38 PM, Luke Han wrote: > Thank you very much for your great feedback. > > For the bylaws, personally I would like to have one

Re: [VOTE] Graduate Apache Kylin from the Apache Incubator

+1 Best Regards! - Luke Han On Fri, Oct 16, 2015 at 9:41 AM, ShaoFeng Shi wrote: > +1 > > 2015-10-16 9:17 GMT+08:00 Andrew Purtell : > > > +1 (binding) > > > > On Thu, Oct 15, 2015 at 4:59 PM, Luke Han

Re: [Vote] Graduate Kylin from the Apache Incubator

Please ignore my last reply in this thread, wrong tying in my keyboard:) Sorry for that. Luke Best Regards! - Luke Han On Fri, Oct 16, 2015 at 7:43 AM, Luke Han wrote: > The Kylin community and project made significant advances during the > incubating

Re: [VOTE] Graduate Apache Kylin from the Apache Incubator

+1 (binding) On Thursday, October 15, 2015, Luke Han wrote: > The Apache Kylin community and project made significant advances during the > incubating (from Nov 2014) and > believes it is ready to graduate as a top-level project. > > The Apache Kylin is very active. The PPMC

Re: [VOTE] Graduate Apache Kylin from the Apache Incubator

+1 (binding) On Thu, Oct 15, 2015 at 4:59 PM, Luke Han wrote: > The Apache Kylin community and project made significant advances during the > incubating (from Nov 2014) and > believes it is ready to graduate as a top-level project. > > The Apache Kylin is very active. The

Permission to edit incubator wiki

Hi, I'll be reporting for HORN, so if possible could someone grant me permissions to edit the incubator wiki? My wiki id is ZachJaffee Thanks! Zach -- Zach Jaffee B.S. Computer Science Case Western Reserve University Class of 2017 Operations Director | WRUW FM 91.1 Cleveland Secretary |

Re: Permission to edit incubator wiki

On Thu, Oct 15, 2015 at 11:10 AM, Zachary Jaffee wrote: > My wiki id is ZachJaffee Done. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail:

RE: [VOTE] Graduate Apache Kylin from the Apache Incubator

+1 -Original Message- From: Luke Han [mailto:luke...@gmail.com] Sent: 2015年10月16日 9:53 To: general@incubator.apache.org Subject: Re: [VOTE] Graduate Apache Kylin from the Apache Incubator +1 Best Regards! - Luke Han On Fri, Oct 16, 2015 at 9:41 AM, ShaoFeng Shi

Re: [VOTE] Graduate Apache Kylin from the Apache Incubator

+1 Zhong, Jason 于2015年10月16日周五 下午1:37写道： > +1 > > -Original Message- > From: Luke Han [mailto:luke...@gmail.com] > Sent: 2015年10月16日 9:53 > To: general@incubator.apache.org > Subject: Re: [VOTE] Graduate Apache Kylin from the Apache Incubator > > +1 > > > Best Regards!

When podlings don't file a report

Greets, This month, six podlings failed to file a report. Of those, one has failed to file 4 months running, and another two have failed to file for 2 months running. Filing one month late every once in a while is excusable, but two months or more ought to trigger a followup. If it turns out

RE: When podlings don't file a report

Mentors, in my opinion, are not responsible for their podlings. They are responsible for guiding the podlings but not for filing. Mentors do have a responsibility to the IPMC to make a recommendation (e.g. "I've looked into the failure to report and am happy with the status, it's just busy

Starting from the other end

We have just had a few interminable threads regarding what is wrong with incubator and jumping directly to implementation attempts for changes. That isn't the way I would code something complex so it seems to me that by analogy we might want to start from the other end and start with what we all