[MENTORS] Incubator board report has been submitted

[Justin Mclean]

Hi,

The report has been submitted and incubator report wiki page made read only. If 
you need to make any last minute changes before the board meeting please use 
whimsey. [1]

Thanks,
Justin

1. https://whimsy.apache.org/board/agenda/2020-02-19/Incubator
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Incubator board report

[Justin Mclean]

HI,

> Could you elaborate on that a bit more?  Note that since the incubator
> report is public, discussing issues that may have come up on the private
> list could be a bit awkward.

Which is why i didn’t elaborate on it here. That info would go into a private 
section.

> There's 6 podlings who have not reported.  Some of them are repeat
> offenders.  If you don't get to it before then, in my morning I'll drop a
> note to them reminding them about their board report responsibilities.

If you could that would be a great help.

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

Re: Incubator board report

[John D. Ament]

On Fri, Jun 8, 2018 at 11:23 PM Justin Mclean 
wrote:

> Hi,
>
> I’m a little behind on sorting out my first incubator board report and I’m
> just abut to hop on several planes and trains (30+ hours travel) to get to
> a conference.
>
> I can see we have a bit to report this month, with a number of releases
> and a number of new projects coming into the incubator and a couple of
> issues with existing existing project that the board needs to know about
> (but are being dealt with).
>

Could you elaborate on that a bit more?  Note that since the incubator
report is public, discussing issues that may have come up on the private
list could be a bit awkward.


>
> I will able to get to it on Sunday / Monday so it will still be done
> before the board meeting. Before then if anyone thinks there something that
> need to be mentioned in the report just add it to this thread.
>

There's 6 podlings who have not reported.  Some of them are repeat
offenders.  If you don't get to it before then, in my morning I'll drop a
note to them reminding them about their board report responsibilities.

There's others that are still missing sign off.  That's OK because mentors
have until Tuesday next week to do that.




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

Incubator board report

[Justin Mclean]

Hi,

I’m a little behind on sorting out my first incubator board report and I’m just 
abut to hop on several planes and trains (30+ hours travel) to get to a 
conference.

I can see we have a bit to report this month, with a number of releases and a 
number of new projects coming into the incubator and a couple of issues with 
existing existing project that the board needs to know about (but are being 
dealt with).

I will able to get to it on Sunday / Monday so it will still be done before the 
board meeting. Before then if anyone thinks there something that need to be 
mentioned in the report just add it to this thread.

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

Re: Final draft of the Incubator Board Report - April 2016

[James Taylor]

Me too - my bad. So sorry. I'm embarrassed to admit I can't find an email
for it.

On Tuesday, April 12, 2016, Henry Saputra <henry.sapu...@gmail.com> wrote:

> No need to be curious too much, mea culpa from me for missing signing off
> the report :)
>
> I had the impression I did sign off the report for Mnemonic, sincerely
> apologize.
>
> - Henry
>
> On Tue, Apr 12, 2016 at 4:38 PM, Wang, Yanping <yanping.w...@intel.com
> <javascript:;>>
> wrote:
>
> > Hi, John
> >
> > I think our mentors are busy during the day.
> > Patrick was on vacation last week. I'd suggest give them a few more hours
> > to signoff the report.
> >
> > Thanks,
> > Yanping
> >
> > -Original Message-
> > From: John D. Ament [mailto:johndam...@apache.org <javascript:;>]
> > Sent: Tuesday, April 12, 2016 4:32 PM
> > To: general@incubator.apache.org <javascript:;>
> > Subject: Re: Final draft of the Incubator Board Report - April 2016
> >
> > I'm a bit curious about how we should handle Mnemonic.  I've received no
> > response thus far from the podling.  I'd rather not kick them out of the
> > monthly report.
> >
> > John
> >
> > On Mon, Apr 11, 2016 at 11:28 PM Marvin Humphrey <mar...@rectangular.com
> <javascript:;>>
> > wrote:
> >
> > > On Mon, Apr 11, 2016 at 3:56 AM, John D. Ament <johndam...@apache.org
> <javascript:;>>
> > > wrote:
> > >
> > > > Below is the final draft of the board report.
> > >
> > > The report looks good to me!  Comments inline.
> > >
> > > >   - Airflow
> > > >   - Gearpump
> > > >   - Mnemonic
> > > >   - Omid
> > > >   - Tephra
> > > >
> > > > * Graduations
> > > >
> > > >   The board has motions for the following:
> > > >
> > > >   - Apex
> > > >   - Johnzon
> > > >   - TinkerPop
> > > >   - AsterixDB
> > >
> > > What turnover!  I see that with the addition of Quickstep that's *six*
> > new
> > > podlings in one month, which has to be a record.
> > >
> > > Congrats to all the entrants and graduates!
> > >
> > > > * Credits
> > > >
> > > >   - Report Manager:
> > >
> > > I added the credit for this month's erstwhile Report Manager. :)
> > >
> > > > * Did not report, expected next month
> > > >
> > > >   - Concerted
> > > >   - OpenAz
> > > >   - Tephra
> > >
> > > The OpenAZ report was due in January and is thus 4 months late, which I
> > > have
> > > now noted on the wiki.  OpenAZ's status has been raised on
> > > private@incubator
> > > and we just have to keep raising it each month until a report gets
> filed.
> > >
> > > > 
> > > > Fineract
> > > >
> > > > Fineract is an open source system for core banking as a platform.
> > > >
> > > > Fineract has been incubating since 2015-12-15.
> > > >
> > > > Three most important issues to address in the move towards
> graduation:
> > > >
> > > >   1. Finalising the initial release
> > > >   2. Improve the communication around the differences between the
> > > previous
> > > >  MifosX project and the new Fineract project, especially in the
> > > MifosX
> > > >  community, website etc.
> > > >   3. With the first initial release, encourage the community to use
> the
> > > >  proper infastructure (mailing lists, issue tracker) for the
> > ongoing
> > > >  collaboration within the community.
> > > >   4. Change management towards less 'key-man' dependency on previous
> > > >  tech/community leaders from MifosX, more towards community
> driven
> > > >  consensus.
> > > >   5. Reduce clutter on mailinglist from JIRA updates etc.
> > > >
> > > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> > > > aware of?
> > > >
> > > >   On the mailinglist there have been discussions around the lack of
> > > traffic
> > > >   on it. This is part of the switchover from the current MifosX
> > community
> > > >   and mailinglists towards the new Fineract lists. At the same time
> the
> > > >   recent meet-

Re: Final draft of the Incubator Board Report - April 2016

[Andrew Purtell]

The deadline for signing off is today, right? Sorry to take it to the last
minute

On Tue, Apr 12, 2016 at 5:29 PM, Henry Saputra <henry.sapu...@gmail.com>
wrote:

> No need to be curious too much, mea culpa from me for missing signing off
> the report :)
>
> I had the impression I did sign off the report for Mnemonic, sincerely
> apologize.
>
> - Henry
>
> On Tue, Apr 12, 2016 at 4:38 PM, Wang, Yanping <yanping.w...@intel.com>
> wrote:
>
> > Hi, John
> >
> > I think our mentors are busy during the day.
> > Patrick was on vacation last week. I'd suggest give them a few more hours
> > to signoff the report.
> >
> > Thanks,
> > Yanping
> >
> > -Original Message-
> > From: John D. Ament [mailto:johndam...@apache.org]
> > Sent: Tuesday, April 12, 2016 4:32 PM
> > To: general@incubator.apache.org
> > Subject: Re: Final draft of the Incubator Board Report - April 2016
> >
> > I'm a bit curious about how we should handle Mnemonic.  I've received no
> > response thus far from the podling.  I'd rather not kick them out of the
> > monthly report.
> >
> > John
> >
> > On Mon, Apr 11, 2016 at 11:28 PM Marvin Humphrey <mar...@rectangular.com
> >
> > wrote:
> >
> > > On Mon, Apr 11, 2016 at 3:56 AM, John D. Ament <johndam...@apache.org>
> > > wrote:
> > >
> > > > Below is the final draft of the board report.
> > >
> > > The report looks good to me!  Comments inline.
> > >
> > > >   - Airflow
> > > >   - Gearpump
> > > >   - Mnemonic
> > > >   - Omid
> > > >   - Tephra
> > > >
> > > > * Graduations
> > > >
> > > >   The board has motions for the following:
> > > >
> > > >   - Apex
> > > >   - Johnzon
> > > >   - TinkerPop
> > > >   - AsterixDB
> > >
> > > What turnover!  I see that with the addition of Quickstep that's *six*
> > new
> > > podlings in one month, which has to be a record.
> > >
> > > Congrats to all the entrants and graduates!
> > >
> > > > * Credits
> > > >
> > > >   - Report Manager:
> > >
> > > I added the credit for this month's erstwhile Report Manager. :)
> > >
> > > > * Did not report, expected next month
> > > >
> > > >   - Concerted
> > > >   - OpenAz
> > > >   - Tephra
> > >
> > > The OpenAZ report was due in January and is thus 4 months late, which I
> > > have
> > > now noted on the wiki.  OpenAZ's status has been raised on
> > > private@incubator
> > > and we just have to keep raising it each month until a report gets
> filed.
> > >
> > > > 
> > > > Fineract
> > > >
> > > > Fineract is an open source system for core banking as a platform.
> > > >
> > > > Fineract has been incubating since 2015-12-15.
> > > >
> > > > Three most important issues to address in the move towards
> graduation:
> > > >
> > > >   1. Finalising the initial release
> > > >   2. Improve the communication around the differences between the
> > > previous
> > > >  MifosX project and the new Fineract project, especially in the
> > > MifosX
> > > >  community, website etc.
> > > >   3. With the first initial release, encourage the community to use
> the
> > > >  proper infastructure (mailing lists, issue tracker) for the
> > ongoing
> > > >  collaboration within the community.
> > > >   4. Change management towards less 'key-man' dependency on previous
> > > >  tech/community leaders from MifosX, more towards community
> driven
> > > >  consensus.
> > > >   5. Reduce clutter on mailinglist from JIRA updates etc.
> > > >
> > > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> > > > aware of?
> > > >
> > > >   On the mailinglist there have been discussions around the lack of
> > > traffic
> > > >   on it. This is part of the switchover from the current MifosX
> > community
> > > >   and mailinglists towards the new Fineract lists. At the same time
> the
> > > >   recent meet-up of Mifosx and Fineract devs and people interested in
> > it
> > > >   (see community devel

Re: Final draft of the Incubator Board Report - April 2016

[Henry Saputra]

No need to be curious too much, mea culpa from me for missing signing off
the report :)

I had the impression I did sign off the report for Mnemonic, sincerely
apologize.

- Henry

On Tue, Apr 12, 2016 at 4:38 PM, Wang, Yanping <yanping.w...@intel.com>
wrote:

> Hi, John
>
> I think our mentors are busy during the day.
> Patrick was on vacation last week. I'd suggest give them a few more hours
> to signoff the report.
>
> Thanks,
> Yanping
>
> -Original Message-
> From: John D. Ament [mailto:johndam...@apache.org]
> Sent: Tuesday, April 12, 2016 4:32 PM
> To: general@incubator.apache.org
> Subject: Re: Final draft of the Incubator Board Report - April 2016
>
> I'm a bit curious about how we should handle Mnemonic.  I've received no
> response thus far from the podling.  I'd rather not kick them out of the
> monthly report.
>
> John
>
> On Mon, Apr 11, 2016 at 11:28 PM Marvin Humphrey <mar...@rectangular.com>
> wrote:
>
> > On Mon, Apr 11, 2016 at 3:56 AM, John D. Ament <johndam...@apache.org>
> > wrote:
> >
> > > Below is the final draft of the board report.
> >
> > The report looks good to me!  Comments inline.
> >
> > >   - Airflow
> > >   - Gearpump
> > >   - Mnemonic
> > >   - Omid
> > >   - Tephra
> > >
> > > * Graduations
> > >
> > >   The board has motions for the following:
> > >
> > >   - Apex
> > >   - Johnzon
> > >   - TinkerPop
> > >   - AsterixDB
> >
> > What turnover!  I see that with the addition of Quickstep that's *six*
> new
> > podlings in one month, which has to be a record.
> >
> > Congrats to all the entrants and graduates!
> >
> > > * Credits
> > >
> > >   - Report Manager:
> >
> > I added the credit for this month's erstwhile Report Manager. :)
> >
> > > * Did not report, expected next month
> > >
> > >   - Concerted
> > >   - OpenAz
> > >   - Tephra
> >
> > The OpenAZ report was due in January and is thus 4 months late, which I
> > have
> > now noted on the wiki.  OpenAZ's status has been raised on
> > private@incubator
> > and we just have to keep raising it each month until a report gets filed.
> >
> > > 
> > > Fineract
> > >
> > > Fineract is an open source system for core banking as a platform.
> > >
> > > Fineract has been incubating since 2015-12-15.
> > >
> > > Three most important issues to address in the move towards graduation:
> > >
> > >   1. Finalising the initial release
> > >   2. Improve the communication around the differences between the
> > previous
> > >  MifosX project and the new Fineract project, especially in the
> > MifosX
> > >  community, website etc.
> > >   3. With the first initial release, encourage the community to use the
> > >  proper infastructure (mailing lists, issue tracker) for the
> ongoing
> > >  collaboration within the community.
> > >   4. Change management towards less 'key-man' dependency on previous
> > >  tech/community leaders from MifosX, more towards community driven
> > >  consensus.
> > >   5. Reduce clutter on mailinglist from JIRA updates etc.
> > >
> > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> > > aware of?
> > >
> > >   On the mailinglist there have been discussions around the lack of
> > traffic
> > >   on it. This is part of the switchover from the current MifosX
> community
> > >   and mailinglists towards the new Fineract lists. At the same time the
> > >   recent meet-up of Mifosx and Fineract devs and people interested in
> it
> > >   (see community development), has also triggered a lot of offline
> > >   interaction.
> > >
> > > How has the community developed since the last report?
> > >
> > >   While activity on the mailinglist has been pretty low, we've had a
> > great
> > >   meet-up in Amsterdam where a nice mix of existing MifosX community
> > members
> > >   and a group of new interested people was present. This has boosted
> > >   interest in Fineract.
> > >
> > >   We have a high level of interest from new contributors throughout
> > Africa -
> > >   we are working to properly engage them and guide them to the correct
> > >   collaboration channels in our Fineract community.
> 

Re: Final draft of the Incubator Board Report - April 2016

[Patrick Hunt]

Hey there, just back from vacation and getting caught up. Thanks for
the reminder!

Patrick

On Tue, Apr 12, 2016 at 4:38 PM, Wang, Yanping <yanping.w...@intel.com> wrote:
> Hi, John
>
> I think our mentors are busy during the day.
> Patrick was on vacation last week. I'd suggest give them a few more hours to 
> signoff the report.
>
> Thanks,
> Yanping
>
> -Original Message-
> From: John D. Ament [mailto:johndam...@apache.org]
> Sent: Tuesday, April 12, 2016 4:32 PM
> To: general@incubator.apache.org
> Subject: Re: Final draft of the Incubator Board Report - April 2016
>
> I'm a bit curious about how we should handle Mnemonic.  I've received no
> response thus far from the podling.  I'd rather not kick them out of the
> monthly report.
>
> John
>
> On Mon, Apr 11, 2016 at 11:28 PM Marvin Humphrey <mar...@rectangular.com>
> wrote:
>
>> On Mon, Apr 11, 2016 at 3:56 AM, John D. Ament <johndam...@apache.org>
>> wrote:
>>
>> > Below is the final draft of the board report.
>>
>> The report looks good to me!  Comments inline.
>>
>> >   - Airflow
>> >   - Gearpump
>> >   - Mnemonic
>> >   - Omid
>> >   - Tephra
>> >
>> > * Graduations
>> >
>> >   The board has motions for the following:
>> >
>> >   - Apex
>> >   - Johnzon
>> >   - TinkerPop
>> >   - AsterixDB
>>
>> What turnover!  I see that with the addition of Quickstep that's *six* new
>> podlings in one month, which has to be a record.
>>
>> Congrats to all the entrants and graduates!
>>
>> > * Credits
>> >
>> >   - Report Manager:
>>
>> I added the credit for this month's erstwhile Report Manager. :)
>>
>> > * Did not report, expected next month
>> >
>> >   - Concerted
>> >   - OpenAz
>> >   - Tephra
>>
>> The OpenAZ report was due in January and is thus 4 months late, which I
>> have
>> now noted on the wiki.  OpenAZ's status has been raised on
>> private@incubator
>> and we just have to keep raising it each month until a report gets filed.
>>
>> > 
>> > Fineract
>> >
>> > Fineract is an open source system for core banking as a platform.
>> >
>> > Fineract has been incubating since 2015-12-15.
>> >
>> > Three most important issues to address in the move towards graduation:
>> >
>> >   1. Finalising the initial release
>> >   2. Improve the communication around the differences between the
>> previous
>> >  MifosX project and the new Fineract project, especially in the
>> MifosX
>> >  community, website etc.
>> >   3. With the first initial release, encourage the community to use the
>> >  proper infastructure (mailing lists, issue tracker) for the ongoing
>> >  collaboration within the community.
>> >   4. Change management towards less 'key-man' dependency on previous
>> >  tech/community leaders from MifosX, more towards community driven
>> >  consensus.
>> >   5. Reduce clutter on mailinglist from JIRA updates etc.
>> >
>> > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
>> > aware of?
>> >
>> >   On the mailinglist there have been discussions around the lack of
>> traffic
>> >   on it. This is part of the switchover from the current MifosX community
>> >   and mailinglists towards the new Fineract lists. At the same time the
>> >   recent meet-up of Mifosx and Fineract devs and people interested in it
>> >   (see community development), has also triggered a lot of offline
>> >   interaction.
>> >
>> > How has the community developed since the last report?
>> >
>> >   While activity on the mailinglist has been pretty low, we've had a
>> great
>> >   meet-up in Amsterdam where a nice mix of existing MifosX community
>> members
>> >   and a group of new interested people was present. This has boosted
>> >   interest in Fineract.
>> >
>> >   We have a high level of interest from new contributors throughout
>> Africa -
>> >   we are working to properly engage them and guide them to the correct
>> >   collaboration channels in our Fineract community.
>> >
>> > How has the project developed since the last report?
>> >
>> >   Individual members of the leading partner organizations building
>> solutions
>> >   using t

RE: Final draft of the Incubator Board Report - April 2016

[Wang, Yanping]

Hi, John

I think our mentors are busy during the day. 
Patrick was on vacation last week. I'd suggest give them a few more hours to 
signoff the report.

Thanks,
Yanping 

-Original Message-
From: John D. Ament [mailto:johndam...@apache.org] 
Sent: Tuesday, April 12, 2016 4:32 PM
To: general@incubator.apache.org
Subject: Re: Final draft of the Incubator Board Report - April 2016

I'm a bit curious about how we should handle Mnemonic.  I've received no
response thus far from the podling.  I'd rather not kick them out of the
monthly report.

John

On Mon, Apr 11, 2016 at 11:28 PM Marvin Humphrey <mar...@rectangular.com>
wrote:

> On Mon, Apr 11, 2016 at 3:56 AM, John D. Ament <johndam...@apache.org>
> wrote:
>
> > Below is the final draft of the board report.
>
> The report looks good to me!  Comments inline.
>
> >   - Airflow
> >   - Gearpump
> >   - Mnemonic
> >   - Omid
> >   - Tephra
> >
> > * Graduations
> >
> >   The board has motions for the following:
> >
> >   - Apex
> >   - Johnzon
> >   - TinkerPop
> >   - AsterixDB
>
> What turnover!  I see that with the addition of Quickstep that's *six* new
> podlings in one month, which has to be a record.
>
> Congrats to all the entrants and graduates!
>
> > * Credits
> >
> >   - Report Manager:
>
> I added the credit for this month's erstwhile Report Manager. :)
>
> > * Did not report, expected next month
> >
> >   - Concerted
> >   - OpenAz
> >   - Tephra
>
> The OpenAZ report was due in January and is thus 4 months late, which I
> have
> now noted on the wiki.  OpenAZ's status has been raised on
> private@incubator
> and we just have to keep raising it each month until a report gets filed.
>
> > 
> > Fineract
> >
> > Fineract is an open source system for core banking as a platform.
> >
> > Fineract has been incubating since 2015-12-15.
> >
> > Three most important issues to address in the move towards graduation:
> >
> >   1. Finalising the initial release
> >   2. Improve the communication around the differences between the
> previous
> >  MifosX project and the new Fineract project, especially in the
> MifosX
> >  community, website etc.
> >   3. With the first initial release, encourage the community to use the
> >  proper infastructure (mailing lists, issue tracker) for the ongoing
> >  collaboration within the community.
> >   4. Change management towards less 'key-man' dependency on previous
> >  tech/community leaders from MifosX, more towards community driven
> >  consensus.
> >   5. Reduce clutter on mailinglist from JIRA updates etc.
> >
> > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> > aware of?
> >
> >   On the mailinglist there have been discussions around the lack of
> traffic
> >   on it. This is part of the switchover from the current MifosX community
> >   and mailinglists towards the new Fineract lists. At the same time the
> >   recent meet-up of Mifosx and Fineract devs and people interested in it
> >   (see community development), has also triggered a lot of offline
> >   interaction.
> >
> > How has the community developed since the last report?
> >
> >   While activity on the mailinglist has been pretty low, we've had a
> great
> >   meet-up in Amsterdam where a nice mix of existing MifosX community
> members
> >   and a group of new interested people was present. This has boosted
> >   interest in Fineract.
> >
> >   We have a high level of interest from new contributors throughout
> Africa -
> >   we are working to properly engage them and guide them to the correct
> >   collaboration channels in our Fineract community.
> >
> > How has the project developed since the last report?
> >
> >   Individual members of the leading partner organizations building
> solutions
> >   using the Fineract platform have begun to effectively use the Fineract
> >   issue tracker to communicate and track the requirements and
> enhancements
> >   they're building and contributing to Fineract. These individuals are
> >   setting a good example that other individuals from our partner
> community
> >   should follow.
> >
> > Date of last release:
> >
> >   N/A
> >
> > When were the last committers or PMC members elected?
> >
> >   N/A
> >
> > Signed-off-by:
> >
> >   [ ](fineract) Ross Gardler
> >   [ ](fineract) Greg Stein
> >   [X](fineract) Roman Shaposh

Re: Final draft of the Incubator Board Report - April 2016

[John D. Ament]

I'm a bit curious about how we should handle Mnemonic.  I've received no
response thus far from the podling.  I'd rather not kick them out of the
monthly report.

John

On Mon, Apr 11, 2016 at 11:28 PM Marvin Humphrey 
wrote:

> On Mon, Apr 11, 2016 at 3:56 AM, John D. Ament 
> wrote:
>
> > Below is the final draft of the board report.
>
> The report looks good to me!  Comments inline.
>
> >   - Airflow
> >   - Gearpump
> >   - Mnemonic
> >   - Omid
> >   - Tephra
> >
> > * Graduations
> >
> >   The board has motions for the following:
> >
> >   - Apex
> >   - Johnzon
> >   - TinkerPop
> >   - AsterixDB
>
> What turnover!  I see that with the addition of Quickstep that's *six* new
> podlings in one month, which has to be a record.
>
> Congrats to all the entrants and graduates!
>
> > * Credits
> >
> >   - Report Manager:
>
> I added the credit for this month's erstwhile Report Manager. :)
>
> > * Did not report, expected next month
> >
> >   - Concerted
> >   - OpenAz
> >   - Tephra
>
> The OpenAZ report was due in January and is thus 4 months late, which I
> have
> now noted on the wiki.  OpenAZ's status has been raised on
> private@incubator
> and we just have to keep raising it each month until a report gets filed.
>
> > 
> > Fineract
> >
> > Fineract is an open source system for core banking as a platform.
> >
> > Fineract has been incubating since 2015-12-15.
> >
> > Three most important issues to address in the move towards graduation:
> >
> >   1. Finalising the initial release
> >   2. Improve the communication around the differences between the
> previous
> >  MifosX project and the new Fineract project, especially in the
> MifosX
> >  community, website etc.
> >   3. With the first initial release, encourage the community to use the
> >  proper infastructure (mailing lists, issue tracker) for the ongoing
> >  collaboration within the community.
> >   4. Change management towards less 'key-man' dependency on previous
> >  tech/community leaders from MifosX, more towards community driven
> >  consensus.
> >   5. Reduce clutter on mailinglist from JIRA updates etc.
> >
> > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> > aware of?
> >
> >   On the mailinglist there have been discussions around the lack of
> traffic
> >   on it. This is part of the switchover from the current MifosX community
> >   and mailinglists towards the new Fineract lists. At the same time the
> >   recent meet-up of Mifosx and Fineract devs and people interested in it
> >   (see community development), has also triggered a lot of offline
> >   interaction.
> >
> > How has the community developed since the last report?
> >
> >   While activity on the mailinglist has been pretty low, we've had a
> great
> >   meet-up in Amsterdam where a nice mix of existing MifosX community
> members
> >   and a group of new interested people was present. This has boosted
> >   interest in Fineract.
> >
> >   We have a high level of interest from new contributors throughout
> Africa -
> >   we are working to properly engage them and guide them to the correct
> >   collaboration channels in our Fineract community.
> >
> > How has the project developed since the last report?
> >
> >   Individual members of the leading partner organizations building
> solutions
> >   using the Fineract platform have begun to effectively use the Fineract
> >   issue tracker to communicate and track the requirements and
> enhancements
> >   they're building and contributing to Fineract. These individuals are
> >   setting a good example that other individuals from our partner
> community
> >   should follow.
> >
> > Date of last release:
> >
> >   N/A
> >
> > When were the last committers or PMC members elected?
> >
> >   N/A
> >
> > Signed-off-by:
> >
> >   [ ](fineract) Ross Gardler
> >   [ ](fineract) Greg Stein
> >   [X](fineract) Roman Shaposhnik
>
> This report provides excellent insight into the challenges and
> opportunities
> before the Fineract community.  Thank you for a good read, and good luck!
>
> > 
> > FreeMarker
>
> > How has the project developed since the last report?
> >
> >   FreeMarker had two public releases: A Release Candidate (so that users
> can
> >   test it), and one final release. Apart from the new features and
> fixes, we
> >   have adjusted the source code and build process to follow Apache best
> >   practices more closely, and to be more appealing for contributors
> >   (switching to Java 5, fixing formatting where it didn't fit the modern
> >   Java conventions).
>
> Those sound like good ideas!  There really are a lot of ways to make a
> project
> easier to contribute to, but they can be hard to see when you're in the
> thick
> of it.
>
> > 
> > Gearpump
> >
> > Gearpump is a reactive real-time streaming engine based on the
> micro-service
> > Actor model.
> >
> > Gearpump 

Re: Final draft of the Incubator Board Report - April 2016

[Marvin Humphrey]

On Mon, Apr 11, 2016 at 3:56 AM, John D. Ament  wrote:

> Below is the final draft of the board report.

The report looks good to me!  Comments inline.

>   - Airflow
>   - Gearpump
>   - Mnemonic
>   - Omid
>   - Tephra
>
> * Graduations
>
>   The board has motions for the following:
>
>   - Apex
>   - Johnzon
>   - TinkerPop
>   - AsterixDB

What turnover!  I see that with the addition of Quickstep that's *six* new
podlings in one month, which has to be a record.

Congrats to all the entrants and graduates!

> * Credits
>
>   - Report Manager:

I added the credit for this month's erstwhile Report Manager. :)

> * Did not report, expected next month
>
>   - Concerted
>   - OpenAz
>   - Tephra

The OpenAZ report was due in January and is thus 4 months late, which I have
now noted on the wiki.  OpenAZ's status has been raised on private@incubator
and we just have to keep raising it each month until a report gets filed.

> 
> Fineract
>
> Fineract is an open source system for core banking as a platform.
>
> Fineract has been incubating since 2015-12-15.
>
> Three most important issues to address in the move towards graduation:
>
>   1. Finalising the initial release
>   2. Improve the communication around the differences between the previous
>  MifosX project and the new Fineract project, especially in the MifosX
>  community, website etc.
>   3. With the first initial release, encourage the community to use the
>  proper infastructure (mailing lists, issue tracker) for the ongoing
>  collaboration within the community.
>   4. Change management towards less 'key-man' dependency on previous
>  tech/community leaders from MifosX, more towards community driven
>  consensus.
>   5. Reduce clutter on mailinglist from JIRA updates etc.
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
>   On the mailinglist there have been discussions around the lack of traffic
>   on it. This is part of the switchover from the current MifosX community
>   and mailinglists towards the new Fineract lists. At the same time the
>   recent meet-up of Mifosx and Fineract devs and people interested in it
>   (see community development), has also triggered a lot of offline
>   interaction.
>
> How has the community developed since the last report?
>
>   While activity on the mailinglist has been pretty low, we've had a great
>   meet-up in Amsterdam where a nice mix of existing MifosX community members
>   and a group of new interested people was present. This has boosted
>   interest in Fineract.
>
>   We have a high level of interest from new contributors throughout Africa -
>   we are working to properly engage them and guide them to the correct
>   collaboration channels in our Fineract community.
>
> How has the project developed since the last report?
>
>   Individual members of the leading partner organizations building solutions
>   using the Fineract platform have begun to effectively use the Fineract
>   issue tracker to communicate and track the requirements and enhancements
>   they're building and contributing to Fineract. These individuals are
>   setting a good example that other individuals from our partner community
>   should follow.
>
> Date of last release:
>
>   N/A
>
> When were the last committers or PMC members elected?
>
>   N/A
>
> Signed-off-by:
>
>   [ ](fineract) Ross Gardler
>   [ ](fineract) Greg Stein
>   [X](fineract) Roman Shaposhnik

This report provides excellent insight into the challenges and opportunities
before the Fineract community.  Thank you for a good read, and good luck!

> 
> FreeMarker

> How has the project developed since the last report?
>
>   FreeMarker had two public releases: A Release Candidate (so that users can
>   test it), and one final release. Apart from the new features and fixes, we
>   have adjusted the source code and build process to follow Apache best
>   practices more closely, and to be more appealing for contributors
>   (switching to Java 5, fixing formatting where it didn't fit the modern
>   Java conventions).

Those sound like good ideas!  There really are a lot of ways to make a project
easier to contribute to, but they can be hard to see when you're in the thick
of it.

> 
> Gearpump
>
> Gearpump is a reactive real-time streaming engine based on the micro-service
> Actor model.
>
> Gearpump has been incubating since 2016-03-08.
>
> Three most important issues to address in the move towards graduation:
>
>   1. Make initial Apache branded release
>   2. Initial community process definition and practice enforcement by
>  following Apache policies
>   3. Build the first Apache branded informative website to make Gearpump
>  contributor and end-user friendly.
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
>   The rights holder of the Gearpump copyright filed a CCLA including 

Re: Final draft of the Incubator Board Report - April 2016

[Marvin Humphrey]

On Mon, Apr 11, 2016 at 6:13 AM, John D. Ament  wrote:
> Got it.  If you're having issues with the wiki, I'd be happy to tick your
> name for you (since we have email confirmation).

I edited the wiki on Upayavira's behalf.

Marvin Humphrey

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

Re: Final draft of the Incubator Board Report - April 2016

[John D. Ament]

Got it.  If you're having issues with the wiki, I'd be happy to tick your
name for you (since we have email confirmation).

John

On Mon, Apr 11, 2016 at 8:52 AM Upayavira  wrote:

> Regarding Wave, I'm happy to sign off the report, just didn't get time
> and got stuck regaining access to my wiki account given slow responses
> from Moin. And yes, if Wave continues in the incubator, it really could
> do with more mentors.
>
> Upayavira
>
> On Mon, 11 Apr 2016, at 11:56 AM, John D. Ament wrote:
> > All,
> >
> > Below is the final draft of the board report.  Remember, mentors have
> > until
> > tomorrow end of day to sign off on podlings.  We have two podlings with
> > no
> > sign offs - Mnemonic and Wave.  Wave is especially concerning since its
> > just Upyavira now.
> >
> > I've extended the months of the non-reporting podlings at this point.  I
> > would ask that if any of those podlings do create a report between now
> > and
> > end of day tomorrow, to first reach out on the general@ list to confirm.
> > I'd rather a podling miss a report than hurry a report that few people
> > can
> > review.
> >
> > - John
> > -
> >
> > Incubator PMC report for April 2016
> >
> > 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 56 podlings currently undergoing incubation.  We have four
> > podlings planning to graduate this month and added five podlings to
> > the roster.  As is typical in the months following the annual members
> > meeting, we have seen a jump in the number of IPMC members join.
> >
> > * Community
> >
> >   New IPMC members:
> >
> >   - Marvin Humphrey
> >   - Suneel Marthi
> >   - Uma Gangumalla
> >   - Henri Yandell
> >
> >   People who left the IPMC:
> >
> >   - Jukka Zitting
> >
> > * New Podlings
> >
> >   - Airflow
> >   - Gearpump
> >   - Mnemonic
> >   - Omid
> >   - Tephra
> >
> > * Graduations
> >
> >   The board has motions for the following:
> >
> >   - Apex
> >   - Johnzon
> >   - TinkerPop
> >   - AsterixDB
> >
> > * Releases
> >
> >   The following releases entered distribution during the month of
> >   March:
> >
> >   2016-03-02 Apache MRQL 0.9.6-incubating
> >   2016-03-03 Apache Apex Malhar 3.3.1-incubating
> >   2016-03-03 Apache Htrace 4.1.0-incubating
> >   2016-03-04 Apache Mynewt-0.8.0-b1-incubating
> >   2016-03-09 Apache Kudu 0.7.1-incubating
> >   2016-03-10 Apache Ranger 0.5.2-incubating
> >   2016-03-11 Apache Taverna-language 0.15.1-incubating
> >   2016-03-11 Apache Taverna-osgi 0.2.1-incubating
> >   2016-03-14 Apache MADlib v1.9alpha-rc2-incubating
> >   2016-03-21 Apache Unomi 1.0.0-incubating
> >   2016-03-25 Apache Mynewt 0.8.0-b2-incubating
> >   2016-03-27 Apache FreeMarker 2.3.24-incubating
> >
> >
> > * IP Clearance
> >
> >   - Apache Sling Dynamic Includes
> >
> > * Legal / Trademarks
> >
> >
> >
> > * Infrastructure
> >
> >   We continue to struggle with podling report reminders.
> >   A suite of manual reminders were sent, some were received
> >   by the podlings and some were not.
> >
> > * Miscellaneous
> >
> >   Based on group understanding, it appears that the Concerted podling
> >   will retire soon.
> >
> >
> >
> > * Credits
> >
> >   - Report Manager:
> >
> > --- Summary of podling reports 
> >
> > * Still getting started at the Incubator
> >
> >   - Gearpump
> >   - iota
> >   - Joshua
> >   - Metron
> >   - Milagro
> >   - Mnemonic
> >   - Quarks
> >
> > * Not yet ready to graduate
> >
> >   No release:
> >
> >   - Hawq
> >   - Horn
> >   - Impala
> >   - Rya
> >   - Toree
> >
> >   Community growth:
> >
> >   - Fineract
> >   - Geode
> >   - MADlib
> >   - Ranger
> >   - Wave
> >
> > * Ready to graduate
> >
> >   The Board has motions for the following:
> >
> >   - Apex
> >   - Johnzon
> >   - TinkerPop
> >   - AsterixDB
> >
> > * Did not report, expected next month
> >
> >   - Concerted
> >   - OpenAz
> >   - Tephra
> >
> > --
> >Table of Contents
> > Apex
> > BatchEE
> > Concerted
> > DataFu
> > Fineract
> > FreeMarker
> > Gearpump
> > Geode
> > HAWQ
> > HORN
> > HTrace
> > Impala
> > iota
> > Johnzon
> > Joshua
> > MADlib
> > Metron
> > Milagro
> > Mnemonic
> > Mynewt
> > ODF Toolkit
> > Quarks
> > Ranger
> > Rya
> > Sirona
> > Toree
> >
> > --
> >
> > 
> > Apex
> >
> > Apex is an enterprise grade native YARN big data-in-motion platform that
> > unifies stream processing and batch processing.
> >
> > Apex has been incubating since 2015-08-17.
> >
> > Three most important issues to address in the move towards graduation:
> >
> >   None. Incubator graduation VOTE passed: https://s.apache.org/qhTf
> >
> > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to 

Re: Final draft of the Incubator Board Report - April 2016

[Upayavira]

Regarding Wave, I'm happy to sign off the report, just didn't get time
and got stuck regaining access to my wiki account given slow responses
from Moin. And yes, if Wave continues in the incubator, it really could
do with more mentors.

Upayavira

On Mon, 11 Apr 2016, at 11:56 AM, John D. Ament wrote:
> All,
> 
> Below is the final draft of the board report.  Remember, mentors have
> until
> tomorrow end of day to sign off on podlings.  We have two podlings with
> no
> sign offs - Mnemonic and Wave.  Wave is especially concerning since its
> just Upyavira now.
> 
> I've extended the months of the non-reporting podlings at this point.  I
> would ask that if any of those podlings do create a report between now
> and
> end of day tomorrow, to first reach out on the general@ list to confirm.
> I'd rather a podling miss a report than hurry a report that few people
> can
> review.
> 
> - John
> -
> 
> Incubator PMC report for April 2016
> 
> 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 56 podlings currently undergoing incubation.  We have four
> podlings planning to graduate this month and added five podlings to
> the roster.  As is typical in the months following the annual members
> meeting, we have seen a jump in the number of IPMC members join.
> 
> * Community
> 
>   New IPMC members:
> 
>   - Marvin Humphrey
>   - Suneel Marthi
>   - Uma Gangumalla
>   - Henri Yandell
> 
>   People who left the IPMC:
> 
>   - Jukka Zitting
> 
> * New Podlings
> 
>   - Airflow
>   - Gearpump
>   - Mnemonic
>   - Omid
>   - Tephra
> 
> * Graduations
> 
>   The board has motions for the following:
> 
>   - Apex
>   - Johnzon
>   - TinkerPop
>   - AsterixDB
> 
> * Releases
> 
>   The following releases entered distribution during the month of
>   March:
> 
>   2016-03-02 Apache MRQL 0.9.6-incubating
>   2016-03-03 Apache Apex Malhar 3.3.1-incubating
>   2016-03-03 Apache Htrace 4.1.0-incubating
>   2016-03-04 Apache Mynewt-0.8.0-b1-incubating
>   2016-03-09 Apache Kudu 0.7.1-incubating
>   2016-03-10 Apache Ranger 0.5.2-incubating
>   2016-03-11 Apache Taverna-language 0.15.1-incubating
>   2016-03-11 Apache Taverna-osgi 0.2.1-incubating
>   2016-03-14 Apache MADlib v1.9alpha-rc2-incubating
>   2016-03-21 Apache Unomi 1.0.0-incubating
>   2016-03-25 Apache Mynewt 0.8.0-b2-incubating
>   2016-03-27 Apache FreeMarker 2.3.24-incubating
> 
> 
> * IP Clearance
> 
>   - Apache Sling Dynamic Includes
> 
> * Legal / Trademarks
> 
> 
> 
> * Infrastructure
> 
>   We continue to struggle with podling report reminders.
>   A suite of manual reminders were sent, some were received
>   by the podlings and some were not.
> 
> * Miscellaneous
> 
>   Based on group understanding, it appears that the Concerted podling
>   will retire soon.
> 
> 
> 
> * Credits
> 
>   - Report Manager:
> 
> --- Summary of podling reports 
> 
> * Still getting started at the Incubator
> 
>   - Gearpump
>   - iota
>   - Joshua
>   - Metron
>   - Milagro
>   - Mnemonic
>   - Quarks
> 
> * Not yet ready to graduate
> 
>   No release:
> 
>   - Hawq
>   - Horn
>   - Impala
>   - Rya
>   - Toree
> 
>   Community growth:
> 
>   - Fineract
>   - Geode
>   - MADlib
>   - Ranger
>   - Wave
> 
> * Ready to graduate
> 
>   The Board has motions for the following:
> 
>   - Apex
>   - Johnzon
>   - TinkerPop
>   - AsterixDB
> 
> * Did not report, expected next month
> 
>   - Concerted
>   - OpenAz
>   - Tephra
> 
> --
>Table of Contents
> Apex
> BatchEE
> Concerted
> DataFu
> Fineract
> FreeMarker
> Gearpump
> Geode
> HAWQ
> HORN
> HTrace
> Impala
> iota
> Johnzon
> Joshua
> MADlib
> Metron
> Milagro
> Mnemonic
> Mynewt
> ODF Toolkit
> Quarks
> Ranger
> Rya
> Sirona
> Toree
> 
> --
> 
> 
> Apex
> 
> Apex is an enterprise grade native YARN big data-in-motion platform that
> unifies stream processing and batch processing.
> 
> Apex has been incubating since 2015-08-17.
> 
> Three most important issues to address in the move towards graduation:
> 
>   None. Incubator graduation VOTE passed: https://s.apache.org/qhTf
> 
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware
> of?
> 
>   Resolution to establish Apache Apex as TLP submitted to board.
> 
> How has the community developed since the last report?
> 
>   The community is very engaged with the development of the project.  We
>   see
>   continious uptick in mailing list participaton (2180 messages on dev@
>   for
>   March, 122+ subscribers).
> 
>   The community discussed graduation, addressed outstanding issues and
>   completed VOTE.
> 
>   The community has been active building additional meetup groups:
>   http://s.apache.org/jKT
>   

Final draft of the Incubator Board Report - April 2016

[John D. Ament]

All,

Below is the final draft of the board report.  Remember, mentors have until
tomorrow end of day to sign off on podlings.  We have two podlings with no
sign offs - Mnemonic and Wave.  Wave is especially concerning since its
just Upyavira now.

I've extended the months of the non-reporting podlings at this point.  I
would ask that if any of those podlings do create a report between now and
end of day tomorrow, to first reach out on the general@ list to confirm.
I'd rather a podling miss a report than hurry a report that few people can
review.

- John
-

Incubator PMC report for April 2016

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 56 podlings currently undergoing incubation.  We have four
podlings planning to graduate this month and added five podlings to
the roster.  As is typical in the months following the annual members
meeting, we have seen a jump in the number of IPMC members join.

* Community

  New IPMC members:

  - Marvin Humphrey
  - Suneel Marthi
  - Uma Gangumalla
  - Henri Yandell

  People who left the IPMC:

  - Jukka Zitting

* New Podlings

  - Airflow
  - Gearpump
  - Mnemonic
  - Omid
  - Tephra

* Graduations

  The board has motions for the following:

  - Apex
  - Johnzon
  - TinkerPop
  - AsterixDB

* Releases

  The following releases entered distribution during the month of
  March:

  2016-03-02 Apache MRQL 0.9.6-incubating
  2016-03-03 Apache Apex Malhar 3.3.1-incubating
  2016-03-03 Apache Htrace 4.1.0-incubating
  2016-03-04 Apache Mynewt-0.8.0-b1-incubating
  2016-03-09 Apache Kudu 0.7.1-incubating
  2016-03-10 Apache Ranger 0.5.2-incubating
  2016-03-11 Apache Taverna-language 0.15.1-incubating
  2016-03-11 Apache Taverna-osgi 0.2.1-incubating
  2016-03-14 Apache MADlib v1.9alpha-rc2-incubating
  2016-03-21 Apache Unomi 1.0.0-incubating
  2016-03-25 Apache Mynewt 0.8.0-b2-incubating
  2016-03-27 Apache FreeMarker 2.3.24-incubating


* IP Clearance

  - Apache Sling Dynamic Includes

* Legal / Trademarks



* Infrastructure

  We continue to struggle with podling report reminders.
  A suite of manual reminders were sent, some were received
  by the podlings and some were not.

* Miscellaneous

  Based on group understanding, it appears that the Concerted podling
  will retire soon.



* Credits

  - Report Manager:

--- Summary of podling reports 

* Still getting started at the Incubator

  - Gearpump
  - iota
  - Joshua
  - Metron
  - Milagro
  - Mnemonic
  - Quarks

* Not yet ready to graduate

  No release:

  - Hawq
  - Horn
  - Impala
  - Rya
  - Toree

  Community growth:

  - Fineract
  - Geode
  - MADlib
  - Ranger
  - Wave

* Ready to graduate

  The Board has motions for the following:

  - Apex
  - Johnzon
  - TinkerPop
  - AsterixDB

* Did not report, expected next month

  - Concerted
  - OpenAz
  - Tephra

--
   Table of Contents
Apex
BatchEE
Concerted
DataFu
Fineract
FreeMarker
Gearpump
Geode
HAWQ
HORN
HTrace
Impala
iota
Johnzon
Joshua
MADlib
Metron
Milagro
Mnemonic
Mynewt
ODF Toolkit
Quarks
Ranger
Rya
Sirona
Toree

--


Apex

Apex is an enterprise grade native YARN big data-in-motion platform that
unifies stream processing and batch processing.

Apex has been incubating since 2015-08-17.

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

  None. Incubator graduation VOTE passed: https://s.apache.org/qhTf

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

  Resolution to establish Apache Apex as TLP submitted to board.

How has the community developed since the last report?

  The community is very engaged with the development of the project.  We see
  continious uptick in mailing list participaton (2180 messages on dev@ for
  March, 122+ subscribers).

  The community discussed graduation, addressed outstanding issues and
  completed VOTE.

  The community has been active building additional meetup groups:
  http://s.apache.org/jKT
  Many presentations and uptick in engagement.

How has the project developed since the last report?

  Release 3.3.1-icubating of Malhar on 2016-03-02

  Various metrics for March are as follows:
  +---+
  |   Metric | Core  | Malhar |
  +---+
  | Non Merge Commits|  52   |   22   |
  | Contributors |  10   |   11   |
  | Jira New Issues  |  40   |   31   |
  | Resolved Issues  |  43   |   20   |
  | Pull Requests merged |  33   |   12   |
  | Pull Requests proposed   |   2   |   11   |
  

Re: [DRAFT] - Incubator Board Report March 2016

[Yuri Z]

I guess the Wave project missed the report. Can you guide us on how do we
fill in the report now?

On Tue, Mar 8, 2016 at 8:24 PM John D. Ament  wrote:

> On Tue, Mar 8, 2016 at 12:14 AM Justin Mclean  wrote:
>
> > Hi John,
> >
> > > I've moved the podlings that had no report submitted to non-reporting
> and
> > > marked them as monthly.  I'm especially concerned about iota and
> Johnzon,
> > > one a brand new podling (maybe they shouldn't have reported this
> month?)
> >
> > JFYI Iota has been slow to start up I’m not sure they would have anything
> > to report.
> >
>
> And thats perfectly normal.  Most podlings in their first months report is
> basically "some of our ML's work, some of our website is there"
>
> My concern is that by making no report, we have no guage of how they're
> doing.
>
>
> >
> > Thanks,
> > Justin
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [DRAFT] - Incubator Board Report March 2016

[John D. Ament]

On Tue, Mar 8, 2016 at 12:14 AM Justin Mclean  wrote:

> Hi John,
>
> > I've moved the podlings that had no report submitted to non-reporting and
> > marked them as monthly.  I'm especially concerned about iota and Johnzon,
> > one a brand new podling (maybe they shouldn't have reported this month?)
>
> JFYI Iota has been slow to start up I’m not sure they would have anything
> to report.
>

And thats perfectly normal.  Most podlings in their first months report is
basically "some of our ML's work, some of our website is there"

My concern is that by making no report, we have no guage of how they're
doing.


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

Re: [DRAFT] - Incubator Board Report March 2016

[Justin Mclean]

Hi John,

> I've moved the podlings that had no report submitted to non-reporting and
> marked them as monthly.  I'm especially concerned about iota and Johnzon,
> one a brand new podling (maybe they shouldn't have reported this month?)

JFYI Iota has been slow to start up I’m not sure they would have anything to 
report.

Thanks,
Justin


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

Re: [DRAFT] - Incubator Board Report March 2016

[John D. Ament]

I've moved the podlings that had no report submitted to non-reporting and
marked them as monthly.  I'm especially concerned about iota and Johnzon,
one a brand new podling (maybe they shouldn't have reported this month?)
and the other a podling that was trying to graduate.  I'll reach out to
those communities separately.

I left the following reports in for now, without sign off.  They should be
removed before we submit the report to the board unless one of their
mentors can sign off on the reports:

- Kudu
- Myriad

Both are fine reports, so shouldn't be an issue to sign off on them.

Note that I signed off on the CommonsRDF report, but to be clear to
everyone, it is an acknowledgement that the podling is in danger of
retiring.

This month seems to have been a pretty big swing in mentors on projects.  I
think everyones realizing how busy they are.  For those mentors who have
resigned, if you could please update podlings.xml to indicate your
resignation that would be appreciated.

For any podling that may be suffering from a lack of mentorship, I would
suggest to please reach out to the IPMC for support, we have many trained
members who may be willing to give you a hand.

John

On Mon, Mar 7, 2016 at 2:15 PM John D. Ament  wrote:

> Hi all,
>
> I have some things I'm going to wrap up tonight.  But below is the current
> draft report.  I notice that there are still many missing podlings.
>
> - Atlas
> - Htrace
> - iota (new podling)
> - Johnzon (just raised a graduation vote)
> - OpenAz
> - Ranger
> - Sirona
> - Wave
>
> I'd like to hear from these podlings/mentors to understand where their
> reports are.
>
> John
>
>
> = Incubator PMC report for March 2016 =
> === Timeline ===
> ||Wed March 02 ||Podling reports due by end of day ||
> ||Sun March 06 ||Shepherd reviews due by end of day ||
> ||Sun March 06 ||Summary due by end of day ||
> ||Tue March 08 ||Mentor signoff due by end of day ||
> ||Wed March 09 ||Report submitted to Board ||
> ||Wed March 16 ||Board meeting ||
>
>
> === Shepherd Assignments ===
> ||Drew Farris ||Sirona ||
> ||John Ament ||Streams ||
> ||John Ament ||Wave ||
> ||Justin Mclean ||Metron ||
> ||P. Taylor Goetz ||Joshua ||
> ||P. Taylor Goetz ||Zeppelin ||
> ||P. Taylor Goetz ||log4cxx2 ||
> ||Timothy Chen ||Impala ||
> ||Timothy Chen ||Johnzon ||
> ||Timothy Chen ||MRQL ||
> ||[none] ||Atlas ||
> ||[none] ||Climate Model Diagnostic Analyzer ||
> ||[none] ||CommonsRDF ||
> ||[none] ||Fineract ||
> ||[none] ||HTrace ||
> ||[none] ||Kudu ||
> ||[none] ||Milagro ||
> ||[none] ||Myriad ||
> ||[none] ||OpenAz ||
> ||[none] ||Ranger ||
> ||[none] ||SAMOA ||
> ||[none] ||Sentry ||
> ||[none] ||Singa ||
> ||[none] ||Taverna ||
> ||[none] ||Toree ||
> ||[none] ||Trafodion ||
> ||[none] ||iota ||
>
>
> === Report content ===
> {{{
> Incubator PMC report for March 2016
>
> 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 52 podlings currently undergoing incubation.
>
> * Community
>
>   New IPMC members:
>
>   - Kathey Marsden
>   - Daniel John Debrunner
>
> * New Podlings
>
>   - Guacamole
>   - Joshua
>   - Quarks
>
> * Graduations
>
>   The board has motions for the following:
>
>   - Sentry
>
> * Releases
>
>   The following releases entered distribution during the month of
>   February:
>
>   2016-02-06 Apache Geode 1.0.0-incubating.M1
>   2016-02-07 Apache Apex v3.3.0-incubating
>   2016-02-11 Apache Wave 0.4.0-incubating
>   2016-02-11 Apache SystemML 0.9.0-incubating
>   2016-02-11 Apache TinkerPop 3.1.1-incubating
>   2016-02-20 Apache Johnzon 0.9.3-incubating
>   2016-02-25 Apache Kudu (incubating) 0.7.0
>   2016-02-26 Apache AsterixDB 0.8.8-incubating
>
> * IP Clearance
>
>
>
> * Legal / Trademarks
>
>   - There was substantial discussion on general@incubator about how
> challenging it is to produce compliant LICENSE and NOTICE files.
>
>   - A couple of podlings with runtime LGPL dependencies pledged to remove
> those dependencies before graduation but were permitted to make
> incubating releases in the meantime.  There was uncertainty as to
> whether VP Legal's approval was required; ultimately VP Legal appeared
> on general@incubator and approved the plans.
>
> * Infrastructure
>
>
>
> * Miscellaneous
>
>   - The Incubator's Retirement Guide has been substantially refreshed, and
> it should now be easier for a Mentor or other volunteer to perform the
> administrative steps to retire a podling.
>
> * Credits
>
>   - Report Manager: Marvin Humphrey
>
>  Summary of podling reports 
>
> * Still getting started at the Incubator
>
>   - Impala
>   - Joshua
>   - Milagro
>
> * Not yet ready to graduate
>
>   No release:
>
>   - CMDA
>   - Fineract
>   - log4cxx2
>   - Metron
>   - Toree
>
>   Community growth:
>
>   - Commons RDF
>   - Kudu
>   - Myriad
>   - SAMOA
>   - Singa
>   - Taverna
>   - 

[DRAFT] - Incubator Board Report March 2016

[John D. Ament]

Hi all,

I have some things I'm going to wrap up tonight.  But below is the current
draft report.  I notice that there are still many missing podlings.

- Atlas
- Htrace
- iota (new podling)
- Johnzon (just raised a graduation vote)
- OpenAz
- Ranger
- Sirona
- Wave

I'd like to hear from these podlings/mentors to understand where their
reports are.

John


= Incubator PMC report for March 2016 =
=== Timeline ===
||Wed March 02 ||Podling reports due by end of day ||
||Sun March 06 ||Shepherd reviews due by end of day ||
||Sun March 06 ||Summary due by end of day ||
||Tue March 08 ||Mentor signoff due by end of day ||
||Wed March 09 ||Report submitted to Board ||
||Wed March 16 ||Board meeting ||


=== Shepherd Assignments ===
||Drew Farris ||Sirona ||
||John Ament ||Streams ||
||John Ament ||Wave ||
||Justin Mclean ||Metron ||
||P. Taylor Goetz ||Joshua ||
||P. Taylor Goetz ||Zeppelin ||
||P. Taylor Goetz ||log4cxx2 ||
||Timothy Chen ||Impala ||
||Timothy Chen ||Johnzon ||
||Timothy Chen ||MRQL ||
||[none] ||Atlas ||
||[none] ||Climate Model Diagnostic Analyzer ||
||[none] ||CommonsRDF ||
||[none] ||Fineract ||
||[none] ||HTrace ||
||[none] ||Kudu ||
||[none] ||Milagro ||
||[none] ||Myriad ||
||[none] ||OpenAz ||
||[none] ||Ranger ||
||[none] ||SAMOA ||
||[none] ||Sentry ||
||[none] ||Singa ||
||[none] ||Taverna ||
||[none] ||Toree ||
||[none] ||Trafodion ||
||[none] ||iota ||


=== Report content ===
{{{
Incubator PMC report for March 2016

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 52 podlings currently undergoing incubation.

* Community

  New IPMC members:

  - Kathey Marsden
  - Daniel John Debrunner

* New Podlings

  - Guacamole
  - Joshua
  - Quarks

* Graduations

  The board has motions for the following:

  - Sentry

* Releases

  The following releases entered distribution during the month of
  February:

  2016-02-06 Apache Geode 1.0.0-incubating.M1
  2016-02-07 Apache Apex v3.3.0-incubating
  2016-02-11 Apache Wave 0.4.0-incubating
  2016-02-11 Apache SystemML 0.9.0-incubating
  2016-02-11 Apache TinkerPop 3.1.1-incubating
  2016-02-20 Apache Johnzon 0.9.3-incubating
  2016-02-25 Apache Kudu (incubating) 0.7.0
  2016-02-26 Apache AsterixDB 0.8.8-incubating

* IP Clearance



* Legal / Trademarks

  - There was substantial discussion on general@incubator about how
challenging it is to produce compliant LICENSE and NOTICE files.

  - A couple of podlings with runtime LGPL dependencies pledged to remove
those dependencies before graduation but were permitted to make
incubating releases in the meantime.  There was uncertainty as to
whether VP Legal's approval was required; ultimately VP Legal appeared
on general@incubator and approved the plans.

* Infrastructure



* Miscellaneous

  - The Incubator's Retirement Guide has been substantially refreshed, and
it should now be easier for a Mentor or other volunteer to perform the
administrative steps to retire a podling.

* Credits

  - Report Manager: Marvin Humphrey

 Summary of podling reports 

* Still getting started at the Incubator

  - Impala
  - Joshua
  - Milagro

* Not yet ready to graduate

  No release:

  - CMDA
  - Fineract
  - log4cxx2
  - Metron
  - Toree

  Community growth:

  - Commons RDF
  - Kudu
  - Myriad
  - SAMOA
  - Singa
  - Taverna
  - Trafodion
  - Zeppelin

* Ready to graduate

  The Board has motions for the following:

  - Sentry

* Did not report, expected next month



--
   Table of Contents
Atlas
Climate Model Diagnostic Analyzer
CommonsRDF
Fineract
HTrace
Impala
iota
Johnzon
Joshua
Kudu
log4cxx2
Metron
Milagro
MRQL
Myriad
OpenAz
Ranger
SAMOA
Sentry
Singa
Sirona
Streams
Taverna
Toree
Trafodion
Wave
Zeppelin

--


Atlas

Apache Atlas is a scalable and extensible set of core foundational
governance services that enables enterprises to effectively and efficiently
meet their compliance requirements within Hadoop and allows integration with
the complete enterprise data ecosystem

Atlas has been incubating since 2015-05-05.

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

  1.
  2.
  3.

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



How has the community developed since the last report?



How has the project developed since the last report?



Date of last release:

  -XX-XX

When were the last committers or PMC members elected?



Signed-off-by:

  [ ](atlas) Arun Murthy
  [ ](atlas) Chris Douglas
  [ ](atlas) Jakob Homan
  [ ](atlas) Vinod Kumar Vavilapalli

Shepherd/Mentor notes:




Climate Model Diagnostic Analyzer

CMDA provides web services for multi-aspect physics-based and phenomenon-

Incubator board report

[Ted Dunning]

Also committed to the June agenda and all updates committed back to the
wiki.


Incubator PMC report for June 2015

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

With 4 new podlings and no graduations, the Incubator has grown to 43
podlings this month -- up from 31 one year ago, but still well shy of the
record 57 set in 2012.

We had some issues this month with Sentry's latest release and
engagement.  See the miscellaneous section for more details.

There are several podlings that seem to be having trouble coming
together. These include log4cxx2 and kalumet.  We will keep an eye on
these for now and initiate discussions about retiring the podlings as
appropriate.

Otherwise, there are no particular issues that warrant board
attention.

* Community

  New IPMC members:

Jarek Jarcec Cecho
Bill Rowe (rejoining)

* New Podlings

Atlas
CMDA (Climate Model Diagnostic Analyzer)
MySOS
Trafodion

* Graduations

None this month.

* Releases

  The following releases were made since the last Incubator report:

  johnzon-0.8
  kylin-0.7.1
  ranger-0.5.0
  TinkerPop 3.0.0.M9


* IP Clearance

  Sebastien Goasguen, Ian Duffy, and Darren Brogan donated gstack to
  Cloudstack.  gstack is an API wrapper that maps the Google Cloud Platform
  compute engine (GCE) API to the CloudStack API.

  Sebastien Goasguen, Ian Duffy, and Darren Brogan donated ec2stack to
  Cloudstack.  ec2stack is an API wrapper that maps the AWS Elastic Compute
  Cloud (EC2) API to the CloudStack API.

  Adobe donated the Sling HApi Tools, which provide a set of Hypermedia API
  tools for Sling.

* Legal / Trademarks

  There was much debate about the name of the new MySOS podling on Incubator
  lists and elsewhere.  The Incubator voted to accept the podling, since
  project name choice does not block entry into incubation.

* Miscellaneous

  Several mentors for Sentry have expressed concerns about the
  podling's engagement with the incubating process. Mentors are in
  dissent with the podling's self-report, and are recommending that
  the podling be moved to monthly reporting until concerns are
  addressed. Since the self-report was not signed off by the mentors,
  we have not included it in this report and will include it in
  subsequent reports as the mentors synchronize with the community.

  A proposal to incubate the Freemarker template engine is under discussion.

  The question of whether or not podlings may have official blogs came up
  and was discussed with both Press and Infrastructure.  Past rulings have
  been inconsistent.  The situation was resolved by establishing that
  podling Mentors must review posts prior to publication.

 Summary of podling reports 

* Still getting started at the Incubator

asterixdb
atlas
geode
myriad
trafodion

* Not yet ready to graduate

  No release:

corinthia
groovy
log4cxx2
taverna

  Community growth:



* Ready to graduate

  The Board has motions for the following:



* Did not report, expected next month

batchee
climate model diagnostic analyzer (CMDA)
kalumet


--
   Table of Contents
AsterixDB
Atlas
BatchEE
Brooklyn
Climate Model Diagnostic Analyzer
CommonsRDF
Corinthia
Geode
Groovy
HTrace
Ignite
Johnzon
Kalumet
log4cxx2
MRQL
Myriad
Ranger
REEF
SAMOA
Sentry
Singa
Sirona
Streams
Taverna
Trafodion
Wave
Zeppelin

--


AsterixDB

Apache AsterixDB is a scalable big data management system (BDMS) that
provides
storage, management, and query capabilities for large collections of semi-
structured data.

AsterixDB has been incubating since 2015-02-28.

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

  1. Do an Apache release.
  2. Migrate issues from Google Code
  3. Grow community

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

  No, moving steadily.

How has the community developed since the last report?

  Some activity on the users list.
  First interest by developers (but site makes it hard).

How has the project developed since the last report?

  First version of the site is up.
  Development is ongoing.

Date of last release:

  No Releases yet.

When were the last committers or PMC members elected?

  No elected PMC and/or committers

Signed-off-by:

  [X](asterixdb) Ate Douma
  [ ](asterixdb) Chris Mattmann
  [ ](asterixdb) Henry Saputra
  [X](asterixdb) Jochen Wiedmann
  [x](asterixdb) Ted Dunning

Shepherd/Mentor notes:

AsterixDB has provided monthly reports for March, April, and May. So,
it should be in group 3 (quarterly reports), shouldn't it?



Atlas

Apache Atlas is a scalable and extensible set of core foundational
governance
services that enables enterprises to effectively and 

Incubator Board Report, February 2012

[Noel J. Bergman]

Over the past month, there has been a lot of discussion within the
Incubator.  We have voted in a new PMC Chair, Jukka Zitting, who will be
rotating out of the PMC Chair position of JackRabbit.

There has been a lot of discussion over the future of the Incubator.  Under
one proposal, the Board would establish new TLPs whose PMC chair is an ASF
Member and initial PMC has at least 3 ASF Members.  Such a TLP would be
under incubation, but not under an Incubator.  Under such a plan, ComDev
would be given responsibility for much of the Incubator's Policy  Procedure
documentation, and similar Community Development related content.  Other
proposals are less radical, and focus on doing something to ensure more
active and involved Mentors.

More immediately, some of Jukka's thoughts on the Board's hot topic of
pushing projects out of the Incubator are presented in the following
exchange:

Jukka Zitting wrote:
 Sam Ruby wrote:
 What I would like to see is the Incubator start identifying PPMCs that
 are stalled, and to consider what information they need (in future
 reports) to help them (us) make such a determination.  I am not
 suggesting that this be made retroactive.  Or that it be done
 immediately.  A plan would be fine: i.e., setting a date by which the
 IPMC will have decided what information needs to be in such reports,
 and a schedule by which the PPMCs need to start providing said
 information.

 My suggestion is to ask the podlings now in category 2 to report again
 in May on their progress on the identified blockers. If there's been
 no measurable progress by then, we'll dig deeper to see what we can
 do. Podlings reporting in other months can be picked up for a similar
 oversight cycle over the coming months. By July we should then have a
 pretty accurate record of progress throughout the entire Incubator,
 including a clear list of podlings that are stuck and need help.

 Before the next quarterly report I'd rely on mentors to help the
 podlings identify and implement ways to move forward. And of course,
 if a podling or its mentors feel that more help is needed, asking on
 general@ or submitting an extra report is always a good idea.

On a related topic, the Incubator PMC voted to reite the HISE podling.  BVal
has voted to seek TLP status.  Syncope, intended to be a reference
implementation for Open Source Identity Management, was voted to begin
Incubation.

The podling reports are below.  Sam suggested including podling reports as a
link to a frozen wiki page.  The Incubator PMC requests feedback from the
Board as a whole as to whether an in-line summary and URL to is satisfactory
for future reports.


 Summary of podling reports 

We reviewed all podlings reporting in this quarter and categorized them
according to their progress through the Incubator and the most pressing
issues that are currently blocking progress.

Still getting started at the Incubator (7 podlings)

  Any23, Bloodhound, Cordova, DeltaSpike, DeviceMap, Flex, Openmeetings

  These projects are still getting started, so no immediate progress
  towards graduation is yet expected.

Not yet ready to graduate (13 podlings)

  IP clearance: Amber
  Release trouble: Clerezza, Stanbol
  Low activity: Ambari, Nuvem, PhotArk, SIS, Wink, Zeta Components
  Low diversity: Airavata, Droids, VCL, Wookie

  We expect the next quarterly report of projects in this category to
  include a summary of their actions and progress in solving these issues.

Ready to graduate (4 podlings)

  Jena, Lucene.NET, NPanday, OpenNLP

  We expect these projects to graduate within the next quarter.

 Detailed Reports 

Airavata

Airavata is a software toolkit which provides features to compose, manage,
execute, and monitor large scale applications and workflows on computational
resources ranging from local clusters to national grids and computing
clouds.
Airavata is incubating since May 2011.

A list of the three most important issues to address in the move towards
graduation

  1. The barrier of entry in contributing to Airavata seems to be high.
 The code, documentation and JIRA issues have to be efficiently
 organized and managed to appeal to wider developer community.

  2. Develop a strong community with organizational diversity and well
 aligned with existing ASF projects as outlined here:
 http://wiki.apache.org/incubator/AiravataProposal#Alignment

  3. Create a regular and predictable release process and schedule

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

  Whilst our community is reasonably large and active we do not, at present,
  have significant diversity, but are working on it. Right now most of the
  contributors that are active are from Indiana University. Chris from JPL
  is involved very closely from a mentoring perspective and will try and get
  involved code wise. The 0.2 release candidate is currently VOTE'ing 

Re: Actively retiring projects (was: Incubator Board Report November 2011)

[Jukka Zitting]

Hi,

Some further followup on this.

On Thu, Jan 12, 2012 at 3:00 PM, Jukka Zitting jukka.zitt...@gmail.com wrote:
 On Sun, Jan 8, 2012 at 1:46 PM, Jukka Zitting jukka.zitt...@gmail.com wrote:
 On Wed, Nov 16, 2011 at 9:36 PM, Sam Ruby ru...@intertwingly.net wrote:
 2008-08-19 PhotArk

 S: Zero recent activity.
 R: Terminate.

 I contacted photark-dev@, asking for a status update or a decision to
 terminate. Luciano is helping the community.

Led by Luciano, the PhotArk community is discussion a new direction.
I'm looking forward to a summary in their February status report.

 2008-11-06 Kato

 S: Zero activity.
 R: Terminate.

 The status of Kato (in relation to Oracle's actions) is being
 evaluated. Ant is helping the community.

It seems like Kato now has a more or less definite statement of
non-interest from Oracle, which leaves them discussing how to continue
from here. Their next status report is due in March; looking forward
to a summary then.

 2008-11-19 Stonehenge

 S: Zero activity.
 R: Terminate.

 I contacted stonehenge-dev@, asking them to retire or come up with a
 plan to revive the project. No mentors visible (6 listed).

As discussed, Stonehenge had already been voted to retire. I completed
the process.

 2009-07-06 VXQuery

 S: Zero recent activity.
 R: Terminate.

 I contacted vxquery-dev@, asking them to retire or come up with a plan
 to revive the project. No mentors visible (4 listed).

There's some desire for further development, but apparently little
energy or interest in community-building. The option of taking the
codebase to an external hosting space came up. I suggested graduating
into an XMLBeans subproject as an alternative, assuming the XMLBeans
PMC is willing to help with the oversight.

 2009-11-05 HISE

 S: Zero recent activity.
 R: Terminate.

 I contacted hise-dev@, asking them to retire or come up with a plan to
 revive the project. No mentors visible (3 listed).

I started the hise-dev@ vote to retire the project based on feedback
from the community.

BR,

Jukka Zitting

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

Re: Actively retiring projects (was: Incubator Board Report November 2011)

[Daniel Shahaf]

Jukka Zitting wrote on Mon, Jan 30, 2012 at 17:20:41 +0100:
 Their next status report is due in March; looking forward
 to a summary then.

They're free to send an out-of-cycle report in February if they
want to...

/reminder

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

Re: Actively retiring projects (was: Incubator Board Report November 2011)

[Mohammad Nour El-Din]

Hi...

On Sun, Jan 8, 2012 at 1:46 PM, Jukka Zitting jukka.zitt...@gmail.comwrote:

 Hi,

 What's the status of this effort?

 I went through all the older-than-year podlings identified by Sam for
 a quick (i.e. incomplete) review of the project status. See below for
 my summary (S) and subjective recommendation (R) for each project.

 Please branch any followup discussion about specific podlings to
 separate threads.

 On Wed, Nov 16, 2011 at 9:36 PM, Sam Ruby ru...@intertwingly.net wrote:
  2007-09-17 JSPWiki

 S: Actively discussing leaving the Incubator
 (http://markmail.org/message/etgsawr7mtjggppt).
 R: Ask for an exit or graduation plan in next report (if not executed
 sooner).

  2008-01-06 RAT

 S: Looking to graduate but stuck with (self-inflicted?) bureacracy.
 R: Push to graduate within Q1.

  2008-05-20 Hama

 S: Active but not too diverse (?) community.
 R: Ask for a graduation plan in next report.

  2008-07-08 Empire-db

 S: Graduating in January.
 R: Congratulations!

  2008-08-19 PhotArk

 S: Zero recent activity.
 R: Terminate.

  2008-09-02 Etch

 S: Too small to graduate yet
 (http://markmail.org/message/ihkdh4rfunwzkjs7). Martijn is helping
 them.
 R: More mentors needed?

  2008-09-04 Tashi

 S: Commit activity by two committers but near-zero public discussion.
 No active mentors.
 R: Mentors needed.

  2008-09-29 Olio

 S: Retired.
 R: RIP.

  2008-10-06 VCL

 S: Fairly active but not diverse enough community.
 R: More mentor help needed for the community solve the diversity issue?

  2008-10-09 Droids

 S: Somewhat active, still not enough for a TLP. Last report mentions
 IP clearance issues?
 R: Ask for a graduation plan in next report.

  2008-11-06 Kato

 S: Zero activity.
 R: Terminate.

  2008-11-19 Stonehenge

 S: Zero activity.
 R: Terminate.

  2009-04-24 Ace

 S: Graduated.
 R: Congratulations!

  2009-05-27 Wink

 S: Pretty low but steady activity. Too small to graduate.
 R: Ask for a graduation plan in next report.

  2009-07-06 VXQuery

 S: Zero recent activity.
 R: Terminate.

  2009-07-17 Wookie

 S: Somewhat active, not enough for a TLP.
 R: Ask for a graduation plan in next report.

  2009-11-05 HISE

 S: Zero recent activity.
 R: Terminate.

  2009-11-27 Clerezza

 S: Fairly active but not diverse enough community.
 R: More mentor help needed for the community solve the diversity issue?

  2010-01-10 Manifold Connector Framework (ManifoldCF)

 S: Fairly active but not diverse enough community.
 R: More mentor help needed for the community solve the diversity issue.

  2010-02-21 SIS

 S: Last activity in November
 (
 http://mail-archives.apache.org/mod_mbox/incubator-sis-dev/20.mbox/browser
 )
 R: Retire unless activity picks up in Q1.

  2010-03-01 Bean Validation

 S: Just about to graduate.
 R: Congratulations!

  2010-05-09 Amber

 S: Somewhat active, not enough for a TLP.
 R: Ask for a graduation plan in next report.

  2010-05-19 Deltacloud

 S: Graduated.
 R: Congratulations!

  2010-05-21 Zeta Components

 S: Fairly active but not diverse enough community. Looking for a new
 mentor.
 R: More mentor help needed for the community solve the diversity issue.

  2010-06-24 Nuvem

 S: Last activity in November
 (
 http://mail-archives.apache.org/mod_mbox/incubator-nuvem-dev/20.mbox/browser
 )
 R: Retire unless activity picks up in Q1.

  2010-07-14 Chukwa

 S: Fairly active but not diverse enough community.
 R: More mentor help needed for the community solve the diversity issue?

  2010-07-22 Lucy

 S: Active and apparently pretty diverse community. Why not already
 graduated?
 R: Ask for a graduation plan in next report.

  2010-08-13 NPanday

 S: Active and apparently pretty diverse community. Why not already
 graduated?
 R: Ask for a graduation plan in next report.

  2010-09-07 Isis

 S: Active and apparently pretty diverse community. Why not already
 graduated?
 R: Ask for a graduation plan in next report.


Thats all true, the only problem we have is that we didn't get any new
committers yet.



  2010-09-26 Gora

 S: Graduating in January.
 R: Congratulations!

  2010-10-03 Kitty

 S: Last activity in November
 (
 http://mail-archives.apache.org/mod_mbox/incubator-kitty-dev/20.mbox/browser
 )
 R: Retire unless activity picks up in Q1.

  2010-11-02 Celix

 S: Somewhat active, not enough for a TLP.
 R: Ask for a graduation plan in next report.

  2010-11-15 Stanbol

 S: Fairly active and apparently diverse community. No release yet.
 R: Ask for a graduation plan in next report.

 BR,

 Jukka Zitting

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




-- 
Thanks
- Mohammad Nour

Life is like riding a bicycle. To keep your balance you must keep moving
- Albert Einstein

Re: January 2012 Incubator Board Report

[sebb]

On 12 January 2012 06:09, Noel J. Bergman n...@devtech.com wrote:
 A number of substantive issues came up during the past month.

 First, and although it was raised on the private list and therefore details
 won't be part of the public report, we advise the Board that there is
 substantial discussion regarding changing the Incubator VP, which has been
 held for almost 8 years by the current VP.

 Second, there is a dispute, both in the abstract and concretely, regarding
 whether or not the ASF, via the Incubator, may play host to a community that
 has forked a compatibly licensed codebase.  Roy suggested that, in the
 specific case:

 The VOTE was based on misleading information.  The Incubator PMC should
 declare it
 void and request a new proposal.  The existing Bloodhound podling should
 be
 placed on hold until this is sorted out.

 Greg has said, more recently, that the Bloodhound and Trac communities
 already have a new non-fork plan and are executing on that now, on the
 bloodhound-dev mailing list.  If that comes to pass, perhaps no further
 attention from the PMC and Board will be required on this issue.  If not,
 we'll have to revisit the specific case.

 However, Bill Rowe has requested that the Incubator PMC formally put the
 general matter to the Board: what policy do or should we have regarding a
 community that wishes to fork a suitably licensed codebase and come to the
 ASF?  If so, what is that policy?  Or is that decision still a matter to be
 determined situationally by the Incubator PMC?  For whatever it is worth,
 the latter is the opinion of the Incubator VP, who recalls that more than
 one successful ASF project started elsewhere and came to the ASF as a fork,
 and not without some complaint from members of the outside community (e.g.,
 Apache Felix).

 Third, there was a lot of discussion surrounding a couple of Incubator
 issues: 1) podlings being comfortably settled in the Incubator, and not
 being focused enough on graduation; 2) Mentors being insufficiently active,
 and thus not providing either proper guidance or oversight.  We definitely
 need to address these issues, promoting both Mentor involvement and
 graduation from the Incubator.  And, finally, Jukka spent time reviewing the
 status of many of the older podlings, and recommending an action.

 Perhaps not coincidentally, ACE, Gora and Bean Validation Framework are all
 in graduation mode.  But, meanwhile, Bloodhound (the podling previously
 mentioned), DeviceMap and Flex have joined.

 Below are podling reports.  Sam Ruby has already reviewed the original list
 prior to posting, and requested that specific posts not be provided to the
 Board, as he was unhappy with their status:

    Kato: has been in limbo for years due to Oracle.  The podling needs to
 decide what to do, or terminate
    Bloodhound, HISE, JSPWiki and Openmeetings: missing
    VXQuery: not signed off by a Mentor

 Although initially requested to be excluded, the Celix and Tashi reports
 were revised to provide at least some graduation guidance, and so their
 reports are included, below.

 -

 Any23

 Any23 is defined as a Java library, a Web service and a set of command line
 tools to extract and validate structured data in RDF format from a variety
 of Web documents and markup formats. Any23 is what it is informally named an
 RDF Distiller.

 A list of the three most important issues to address in the move towards
 graduation

   1. Port Any23 code to ASF infrastructure and update license headers
   2. Develop a strong community with organizational diversity and with
 strong connections to other relevant ASF communities.
   3. At least one Any23 incubating release

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

 Yes, all of the code has been ported from Google Code to the ASF. Thanks to
 Daniel Shahaf and Michele Mostarda for
 leading the charge here.

 How has the community developed since the last report?

 All ASF karma has been granted on the repository, and we've received a few
 JIRA issues, but not from outside
 the core set of PPMC members as of yet. The team needs to respond to Paolo
 Castagna's points regarding RDF
 frameworks and collaboration, and will hopefully do so this month.

 How has the project developed since the last report?

 Any23 was voted into the Incubator by the IPMC on October 1, 2011.

 We have Jenkins CI builds going thanks to Lewis John McGibbney, code up and
 running at the ASF thanks to Michele
 and to Daniel, so we're all set to really get kicking!

 
 Celix

 Celix is an implementation of the OSGi Specification in C.

 Celix entered incubation on November 2, 2010.

 Over the last few months lots of work has been put into integrating APR and
 updating the Celix code base to the proposed code style. This code style has
 partially been documented on [1]. Also some effort has been put into
 updating 

Re: January 2012 Incubator Board Report

[Jukka Zitting]

Hi,

On Thu, Jan 12, 2012 at 12:27 PM, sebb seb...@gmail.com wrote:
 On 12 January 2012 06:09, Noel J. Bergman n...@devtech.com wrote:
 Cordova

 Does not appear to mention anywhere that the previous name was
 Callback which is a strange omission.

The renaming was mentioned already in the December report.

Anyway, for clarity we'll include a short note about the previous name
in future reports.

BR,

Jukka Zitting

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

Re: Actively retiring projects (was: Incubator Board Report November 2011)

[Jukka Zitting]

Hi,

Following up on projects where my recommendation was an unconditional
Terminate.

On Sun, Jan 8, 2012 at 1:46 PM, Jukka Zitting jukka.zitt...@gmail.com wrote:
 On Wed, Nov 16, 2011 at 9:36 PM, Sam Ruby ru...@intertwingly.net wrote:
 2008-08-19 PhotArk

 S: Zero recent activity.
 R: Terminate.

I contacted photark-dev@, asking for a status update or a decision to
terminate. Luciano is helping the community.

 2008-11-06 Kato

 S: Zero activity.
 R: Terminate.

The status of Kato (in relation to Oracle's actions) is being
evaluated. Ant is helping the community.

 2008-11-19 Stonehenge

 S: Zero activity.
 R: Terminate.

I contacted stonehenge-dev@, asking them to retire or come up with a
plan to revive the project. No mentors visible (6 listed).

 2009-07-06 VXQuery

 S: Zero recent activity.
 R: Terminate.

I contacted vxquery-dev@, asking them to retire or come up with a plan
to revive the project. No mentors visible (4 listed).

 2009-11-05 HISE

 S: Zero recent activity.
 R: Terminate.

I contacted hise-dev@, asking them to retire or come up with a plan to
revive the project. No mentors visible (3 listed).

BR,

Jukka Zitting

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

Re: Actively retiring projects (was: Incubator Board Report November 2011)

[Daniel Kulp]

On Thursday, January 12, 2012 3:00:41 PM Jukka Zitting wrote:
 The status of Kato (in relation to Oracle's actions) is being
 evaluated. Ant is helping the community.
 
  2008-11-19 Stonehenge
  
  S: Zero activity.
  R: Terminate.
 
 I contacted stonehenge-dev@, asking them to retire or come up with a
 plan to revive the project. No mentors visible (6 listed).

We already had the vote to retire it:

http://mail-archives.apache.org/mod_mbox/incubator-general/201106.mbox/%3C1479384.AD1QayfXJR%40dilbert.dankulp.com%3E

I've just been to busy to finish up the steps and the other mentors have pretty 
much disappeared.   Any help would be appreciated.

 

-- 
Daniel Kulp
dk...@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com

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

Re: Actively retiring projects (was: Incubator Board Report November 2011)

[Jukka Zitting]

Hi,

On Thu, Jan 12, 2012 at 3:20 PM, Daniel Kulp dk...@apache.org wrote:
 On Thursday, January 12, 2012 3:00:41 PM Jukka Zitting wrote:
 I contacted stonehenge-dev@, asking them to retire or come up with a
 plan to revive the project. No mentors visible (6 listed).

 We already had the vote to retire it:

 http://mail-archives.apache.org/mod_mbox/incubator-general/201106.mbox/%3C1479384.AD1QayfXJR%40dilbert.dankulp.com%3E

Thanks! I missed that.

 I've just been to busy to finish up the steps and the other mentors have 
 pretty
 much disappeared. Any help would be appreciated.

No worries. I'll take care of it.

BR,

Jukka Zitting

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

January 2012 Incubator Board Report

[Noel J. Bergman]

A number of substantive issues came up during the past month.

First, and although it was raised on the private list and therefore details
won't be part of the public report, we advise the Board that there is
substantial discussion regarding changing the Incubator VP, which has been
held for almost 8 years by the current VP.

Second, there is a dispute, both in the abstract and concretely, regarding
whether or not the ASF, via the Incubator, may play host to a community that
has forked a compatibly licensed codebase.  Roy suggested that, in the
specific case:

 The VOTE was based on misleading information.  The Incubator PMC should
declare it
 void and request a new proposal.  The existing Bloodhound podling should
be
 placed on hold until this is sorted out.

Greg has said, more recently, that the Bloodhound and Trac communities
already have a new non-fork plan and are executing on that now, on the
bloodhound-dev mailing list.  If that comes to pass, perhaps no further
attention from the PMC and Board will be required on this issue.  If not,
we'll have to revisit the specific case.

However, Bill Rowe has requested that the Incubator PMC formally put the
general matter to the Board: what policy do or should we have regarding a
community that wishes to fork a suitably licensed codebase and come to the
ASF?  If so, what is that policy?  Or is that decision still a matter to be
determined situationally by the Incubator PMC?  For whatever it is worth,
the latter is the opinion of the Incubator VP, who recalls that more than
one successful ASF project started elsewhere and came to the ASF as a fork,
and not without some complaint from members of the outside community (e.g.,
Apache Felix).

Third, there was a lot of discussion surrounding a couple of Incubator
issues: 1) podlings being comfortably settled in the Incubator, and not
being focused enough on graduation; 2) Mentors being insufficiently active,
and thus not providing either proper guidance or oversight.  We definitely
need to address these issues, promoting both Mentor involvement and
graduation from the Incubator.  And, finally, Jukka spent time reviewing the
status of many of the older podlings, and recommending an action.

Perhaps not coincidentally, ACE, Gora and Bean Validation Framework are all
in graduation mode.  But, meanwhile, Bloodhound (the podling previously
mentioned), DeviceMap and Flex have joined.

Below are podling reports.  Sam Ruby has already reviewed the original list
prior to posting, and requested that specific posts not be provided to the
Board, as he was unhappy with their status:

Kato: has been in limbo for years due to Oracle.  The podling needs to
decide what to do, or terminate
Bloodhound, HISE, JSPWiki and Openmeetings: missing
VXQuery: not signed off by a Mentor

Although initially requested to be excluded, the Celix and Tashi reports
were revised to provide at least some graduation guidance, and so their
reports are included, below.

-

Any23

Any23 is defined as a Java library, a Web service and a set of command line
tools to extract and validate structured data in RDF format from a variety
of Web documents and markup formats. Any23 is what it is informally named an
RDF Distiller.

A list of the three most important issues to address in the move towards
graduation

   1. Port Any23 code to ASF infrastructure and update license headers
   2. Develop a strong community with organizational diversity and with
strong connections to other relevant ASF communities.
   3. At least one Any23 incubating release

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

Yes, all of the code has been ported from Google Code to the ASF. Thanks to
Daniel Shahaf and Michele Mostarda for
leading the charge here.

How has the community developed since the last report?

All ASF karma has been granted on the repository, and we've received a few
JIRA issues, but not from outside
the core set of PPMC members as of yet. The team needs to respond to Paolo
Castagna's points regarding RDF
frameworks and collaboration, and will hopefully do so this month.

How has the project developed since the last report?

Any23 was voted into the Incubator by the IPMC on October 1, 2011.

We have Jenkins CI builds going thanks to Lewis John McGibbney, code up and
running at the ASF thanks to Michele
and to Daniel, so we're all set to really get kicking!


Celix

Celix is an implementation of the OSGi Specification in C.

Celix entered incubation on November 2, 2010.

Over the last few months lots of work has been put into integrating APR and
updating the Celix code base to the proposed code style. This code style has
partially been documented on [1]. Also some effort has been put into
updating the source for Visual Studio, even though not yet finished some
interesting and helpful patches where submitted and applied.

In Oktober an 

Re: January 2012 Incubator Board Report

[Daniel Shahaf]

On Thu, Jan 12, 2012, at 01:09, Noel J. Bergman wrote:
 Below are podling reports.  Sam Ruby has already reviewed the original list
 prior to posting, and requested that specific posts not be provided to the
 Board, as he was unhappy with their status:
 
 Kato: has been in limbo for years due to Oracle.  The podling needs to
 decide what to do, or terminate
 Bloodhound, HISE, JSPWiki and Openmeetings: missing
 VXQuery: not signed off by a Mentor
 

Perhaps to state the obvious, but: Mentors and PPMCers of the above
projects, please relay the above to your dev lists.

 -
 
 Any23
 
...
 Yes, all of the code has been ported from Google Code to the ASF.
 Thanks to Daniel Shahaf and Michele Mostarda for leading the
 charge here.

To clarify: I'm not a member of the Any23 community; I only participated
here as a member of Infra.

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

Re: January 2012 Incubator Board Report

[Mattmann, Chris A (388J)]

On Jan 11, 2012, at 10:39 PM, Daniel Shahaf wrote:

 
 -
 
 Any23
 
 ...
 Yes, all of the code has been ported from Google Code to the ASF.
 Thanks to Daniel Shahaf and Michele Mostarda for leading the
 charge here.
 
 To clarify: I'm not a member of the Any23 community; I only participated
 here as a member of Infra.

We appreciate your help and I still am happy that I gave you credit in the 
report regardless.

Cheers,
Chris

++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattm...@nasa.gov
WWW:   http://sunset.usc.edu/~mattmann/
++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++


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

Re: Actively retiring projects (was: Incubator Board Report November 2011)

[Martijn Dashorst]

Just an FYI: I have posted a status update on Etch on general@, hoping
it doesn't fall on deaf ears with all the discussions going on:

http://mail-archives.apache.org/mod_mbox/incubator-general/201201.mbox/%3ccab63y-dsjkbkeljkhuvkbdlmsjwvfvixo0fnxexofhq1v4m...@mail.gmail.com%3e

Martijn

On Sun, Jan 8, 2012 at 1:46 PM, Jukka Zitting jukka.zitt...@gmail.com wrote:
 Hi,

 What's the status of this effort?

 I went through all the older-than-year podlings identified by Sam for
 a quick (i.e. incomplete) review of the project status. See below for
 my summary (S) and subjective recommendation (R) for each project.

 Please branch any followup discussion about specific podlings to
 separate threads.

 On Wed, Nov 16, 2011 at 9:36 PM, Sam Ruby ru...@intertwingly.net wrote:
 2007-09-17 JSPWiki

 S: Actively discussing leaving the Incubator
 (http://markmail.org/message/etgsawr7mtjggppt).
 R: Ask for an exit or graduation plan in next report (if not executed sooner).

 2008-01-06 RAT

 S: Looking to graduate but stuck with (self-inflicted?) bureacracy.
 R: Push to graduate within Q1.

 2008-05-20 Hama

 S: Active but not too diverse (?) community.
 R: Ask for a graduation plan in next report.

 2008-07-08 Empire-db

 S: Graduating in January.
 R: Congratulations!

 2008-08-19 PhotArk

 S: Zero recent activity.
 R: Terminate.

 2008-09-02 Etch

 S: Too small to graduate yet
 (http://markmail.org/message/ihkdh4rfunwzkjs7). Martijn is helping
 them.
 R: More mentors needed?

 2008-09-04 Tashi

 S: Commit activity by two committers but near-zero public discussion.
 No active mentors.
 R: Mentors needed.

 2008-09-29 Olio

 S: Retired.
 R: RIP.

 2008-10-06 VCL

 S: Fairly active but not diverse enough community.
 R: More mentor help needed for the community solve the diversity issue?

 2008-10-09 Droids

 S: Somewhat active, still not enough for a TLP. Last report mentions
 IP clearance issues?
 R: Ask for a graduation plan in next report.

 2008-11-06 Kato

 S: Zero activity.
 R: Terminate.

 2008-11-19 Stonehenge

 S: Zero activity.
 R: Terminate.

 2009-04-24 Ace

 S: Graduated.
 R: Congratulations!

 2009-05-27 Wink

 S: Pretty low but steady activity. Too small to graduate.
 R: Ask for a graduation plan in next report.

 2009-07-06 VXQuery

 S: Zero recent activity.
 R: Terminate.

 2009-07-17 Wookie

 S: Somewhat active, not enough for a TLP.
 R: Ask for a graduation plan in next report.

 2009-11-05 HISE

 S: Zero recent activity.
 R: Terminate.

 2009-11-27 Clerezza

 S: Fairly active but not diverse enough community.
 R: More mentor help needed for the community solve the diversity issue?

 2010-01-10 Manifold Connector Framework (ManifoldCF)

 S: Fairly active but not diverse enough community.
 R: More mentor help needed for the community solve the diversity issue.

 2010-02-21 SIS

 S: Last activity in November
 (http://mail-archives.apache.org/mod_mbox/incubator-sis-dev/20.mbox/browser)
 R: Retire unless activity picks up in Q1.

 2010-03-01 Bean Validation

 S: Just about to graduate.
 R: Congratulations!

 2010-05-09 Amber

 S: Somewhat active, not enough for a TLP.
 R: Ask for a graduation plan in next report.

 2010-05-19 Deltacloud

 S: Graduated.
 R: Congratulations!

 2010-05-21 Zeta Components

 S: Fairly active but not diverse enough community. Looking for a new mentor.
 R: More mentor help needed for the community solve the diversity issue.

 2010-06-24 Nuvem

 S: Last activity in November
 (http://mail-archives.apache.org/mod_mbox/incubator-nuvem-dev/20.mbox/browser)
 R: Retire unless activity picks up in Q1.

 2010-07-14 Chukwa

 S: Fairly active but not diverse enough community.
 R: More mentor help needed for the community solve the diversity issue?

 2010-07-22 Lucy

 S: Active and apparently pretty diverse community. Why not already graduated?
 R: Ask for a graduation plan in next report.

 2010-08-13 NPanday

 S: Active and apparently pretty diverse community. Why not already graduated?
 R: Ask for a graduation plan in next report.

 2010-09-07 Isis

 S: Active and apparently pretty diverse community. Why not already graduated?
 R: Ask for a graduation plan in next report.

 2010-09-26 Gora

 S: Graduating in January.
 R: Congratulations!

 2010-10-03 Kitty

 S: Last activity in November
 (http://mail-archives.apache.org/mod_mbox/incubator-kitty-dev/20.mbox/browser)
 R: Retire unless activity picks up in Q1.

 2010-11-02 Celix

 S: Somewhat active, not enough for a TLP.
 R: Ask for a graduation plan in next report.

 2010-11-15 Stanbol

 S: Fairly active and apparently diverse community. No release yet.
 R: Ask for a graduation plan in next report.

 BR,

 Jukka Zitting

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




-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com

Re: Actively retiring projects (was: Incubator Board Report November 2011)

[Greg Stein]

Since this thread has come back to life, I read through it and have
one comment to add:

On Wed, Nov 16, 2011 at 20:27, Benson Margulies bimargul...@gmail.com wrote:
...
 I can see two problems with this view to begin with. One is IP
 management. The more people participate in a project and the longer
 they do so, the messier it becomes to track provenance and get ICLAs
 from all of the contributors. One almost wishes that the ASF could
 accept ICLAs and code grants for code that is in fact living somewhere
 else. I'm sure someone will tell me why that idea is nuts.

Actually, the ASF doesn't vette *why* an ICLA is being filed. It
simply takes it and records it.

The serf project[*] requires all committers to sign an ICLA with the
ASF before receiving access. This way, should we ever want to move the
project to the ASF, we have all commits already covered under an ICLA.
While the project would still hit the Incubator, its IP clearance
would be done on Day One.

Cheers,
-g

[*] http://code.google.com/p/serf/ ... serf/ASF history at
http://s.apache.org/jz

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

Re: Actively retiring projects (was: Incubator Board Report November 2011)

[Jukka Zitting]

Hi,

What's the status of this effort?

I went through all the older-than-year podlings identified by Sam for
a quick (i.e. incomplete) review of the project status. See below for
my summary (S) and subjective recommendation (R) for each project.

Please branch any followup discussion about specific podlings to
separate threads.

On Wed, Nov 16, 2011 at 9:36 PM, Sam Ruby ru...@intertwingly.net wrote:
 2007-09-17 JSPWiki

S: Actively discussing leaving the Incubator
(http://markmail.org/message/etgsawr7mtjggppt).
R: Ask for an exit or graduation plan in next report (if not executed sooner).

 2008-01-06 RAT

S: Looking to graduate but stuck with (self-inflicted?) bureacracy.
R: Push to graduate within Q1.

 2008-05-20 Hama

S: Active but not too diverse (?) community.
R: Ask for a graduation plan in next report.

 2008-07-08 Empire-db

S: Graduating in January.
R: Congratulations!

 2008-08-19 PhotArk

S: Zero recent activity.
R: Terminate.

 2008-09-02 Etch

S: Too small to graduate yet
(http://markmail.org/message/ihkdh4rfunwzkjs7). Martijn is helping
them.
R: More mentors needed?

 2008-09-04 Tashi

S: Commit activity by two committers but near-zero public discussion.
No active mentors.
R: Mentors needed.

 2008-09-29 Olio

S: Retired.
R: RIP.

 2008-10-06 VCL

S: Fairly active but not diverse enough community.
R: More mentor help needed for the community solve the diversity issue?

 2008-10-09 Droids

S: Somewhat active, still not enough for a TLP. Last report mentions
IP clearance issues?
R: Ask for a graduation plan in next report.

 2008-11-06 Kato

S: Zero activity.
R: Terminate.

 2008-11-19 Stonehenge

S: Zero activity.
R: Terminate.

 2009-04-24 Ace

S: Graduated.
R: Congratulations!

 2009-05-27 Wink

S: Pretty low but steady activity. Too small to graduate.
R: Ask for a graduation plan in next report.

 2009-07-06 VXQuery

S: Zero recent activity.
R: Terminate.

 2009-07-17 Wookie

S: Somewhat active, not enough for a TLP.
R: Ask for a graduation plan in next report.

 2009-11-05 HISE

S: Zero recent activity.
R: Terminate.

 2009-11-27 Clerezza

S: Fairly active but not diverse enough community.
R: More mentor help needed for the community solve the diversity issue?

 2010-01-10 Manifold Connector Framework (ManifoldCF)

S: Fairly active but not diverse enough community.
R: More mentor help needed for the community solve the diversity issue.

 2010-02-21 SIS

S: Last activity in November
(http://mail-archives.apache.org/mod_mbox/incubator-sis-dev/20.mbox/browser)
R: Retire unless activity picks up in Q1.

 2010-03-01 Bean Validation

S: Just about to graduate.
R: Congratulations!

 2010-05-09 Amber

S: Somewhat active, not enough for a TLP.
R: Ask for a graduation plan in next report.

 2010-05-19 Deltacloud

S: Graduated.
R: Congratulations!

 2010-05-21 Zeta Components

S: Fairly active but not diverse enough community. Looking for a new mentor.
R: More mentor help needed for the community solve the diversity issue.

 2010-06-24 Nuvem

S: Last activity in November
(http://mail-archives.apache.org/mod_mbox/incubator-nuvem-dev/20.mbox/browser)
R: Retire unless activity picks up in Q1.

 2010-07-14 Chukwa

S: Fairly active but not diverse enough community.
R: More mentor help needed for the community solve the diversity issue?

 2010-07-22 Lucy

S: Active and apparently pretty diverse community. Why not already graduated?
R: Ask for a graduation plan in next report.

 2010-08-13 NPanday

S: Active and apparently pretty diverse community. Why not already graduated?
R: Ask for a graduation plan in next report.

 2010-09-07 Isis

S: Active and apparently pretty diverse community. Why not already graduated?
R: Ask for a graduation plan in next report.

 2010-09-26 Gora

S: Graduating in January.
R: Congratulations!

 2010-10-03 Kitty

S: Last activity in November
(http://mail-archives.apache.org/mod_mbox/incubator-kitty-dev/20.mbox/browser)
R: Retire unless activity picks up in Q1.

 2010-11-02 Celix

S: Somewhat active, not enough for a TLP.
R: Ask for a graduation plan in next report.

 2010-11-15 Stanbol

S: Fairly active and apparently diverse community. No release yet.
R: Ask for a graduation plan in next report.

BR,

Jukka Zitting

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

Re: Actively retiring projects (was: Incubator Board Report November 2011)

[Robert Burrell Donkin]

On Sun, Jan 8, 2012 at 12:46 PM, Jukka Zitting jukka.zitt...@gmail.com wrote:

snip

 2008-01-06 RAT

 S: Looking to graduate but stuck with (self-inflicted?) bureacracy.
 R: Push to graduate within Q1.

Rat is stalled on trademarks

Robert

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

Re: Actively retiring projects (was: Incubator Board Report November 2011)

[Mattmann, Chris A (388J)]

Hey Jukka,

On Jan 8, 2012, at 4:46 AM, Jukka Zitting wrote:

 2010-02-21 SIS
 
 S: Last activity in November
 (http://mail-archives.apache.org/mod_mbox/incubator-sis-dev/20.mbox/browser)
 R: Retire unless activity picks up in Q1.

As a SIS mentor I'd say this is fair, but my personal gut tells me it would be 
nice to give
SIS until end of Q2/Q3. Also I'll echo my call again for contributors (mentors, 
geospatial
enthusiasts, others) and for folks that are interested in having an ALv2 
licensed 
geospatial toolkit to come on over to sis-dev@ or sis-user@ and contribute.

Cheers,
Chris

++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattm...@nasa.gov
WWW:   http://sunset.usc.edu/~mattmann/
++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++


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

Re: Actively retiring projects (was: Incubator Board Report November 2011)

[Sam Ruby]

On Sun, Jan 8, 2012 at 7:46 AM, Jukka Zitting jukka.zitt...@gmail.com wrote:
 Hi,

 I went through all the older-than-year podlings identified by Sam for
 a quick (i.e. incomplete) review of the project status. See below for
 my summary (S) and subjective recommendation (R) for each project.

Excellent work!  This is the type of information I would love to see
in board reports from the Incubator.

For reference, here are the published incubator reports, minus the
podling reports:

https://whimsy.apache.org/board/minutes/Incubator.html

Here are the podling reports for all of the podlings that have yet to
(or never managed to) graduate:

https://whimsy.apache.org/board/minutes/#podling

Here is an up-to-the-minute update on podlings by age (complete with a graph):

https://whimsy.apache.org/incubator/podlings/by-age

- Sam Ruby

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

December 2011 Incubator Board Report

[Noel J. Bergman]

We've all been aware that the Incubator has been growing more than
graduating, over the years.  Last month, Sam started a discussion regarding
being more proactive and pushing projects out of the nest, basically one way
or another, after a year.  A real issue is pushing out those really ready to
graduate, and doing the garbage collection on those that are already dead
(and may have even voted to terminate).  In-between are those projects that
are struggling to achieve critical mass, but are active with who they do
have involved.  The response from mentors of various projects was quite
encouraging, both in specifics and in concept, and hopefully we'll start to
see a wave of TLP requests, following ACE, Bean Validation, and Empire-DB.

Meanwhile, Apache DeltaSpike -- a collection of JSR-299 (CDI) Extensions for
building applications on the Java SE and EE platforms -- was voted for
Incubation.

There has also been excellent discussion about pruning and clarifying
Incubation rules and process, to be more streamlined and minimal.

With respect to the monthly board report, since the last report (and since
the schedule change), we've changed how reminders are processed, and hope to
be well on the way to cleaning up the problem where the wrong projects were
listed and reminded.  There were still a few glitches for this month, but
hopefully they're resolved for next.  Brett Porter, Dave Crossley,
Upayavira, Jim, and others have contributed to the efforts, and are well
deserving of continued thanks.

Even so, and despite an extra day and reminder, neither HISE nor KATA
reported.  Wave did take advantage of the time to report.


Accumulo

Accumulo is a sorted, distributed key/value store based on BigTable's
design.  Accumulo entered incubation in September 2011.

In the move towards graduation, we must address:
1. Learning Apache procedures
2. Creating releases
3. Building a community

Community Development:
* active discussion on mailing lists and on JIRA tickets
* three new contributors have submitted patches this month
* logo voted upon

Project Development:
* made progress towards releasing 1.3.5 (now on candidate 10)
* incorporated lessons from failed release candidates into redesign of
release process for trunk
* fixed bugs / tested code / added documentation



Ambari

Ambari is monitoring, administration and lifecycle management project for
Apache Hadoop clusters.

 * Incubating since 30 August 2011.
 * Picked CTR instead of RTC.
 * Development proceeding actively. (129 jiras fixed so far, 15k of java)
 * Should have first end to end test working soon.

Issues that must be addressed before graduation are:
 * Making a release
 * Attracting users and developers
 * Increase diversity of developers outside of Hortonworks



Amber

Amber has been incubating since July 2010. Amber is a project to develop a
Java library which provides an API specification for, and an unconditionally
compliant implementation of the OAuth v1.0, v1.0a and v2.0 specifications.
OAuth is a mechanism that allows users to authenticate and authorise access
by another party to resources they control while avoiding the need to share
their username and password credentials.

The most important issues that must be addressed before graduation are:

 - Clarify status of code grant
 - Attract users and developers
 - Generate a release

The Incubator PMC / ASF Board should be aware that:

 - Community activity is relatively low
 - We need copyright signoff from University of Newcastle

How has the community developed since the last report

 - New users / devs show up on the mailing lists both contributing patches
and asking for guidance/release

How has the project developed since the last report

 - The old trunk has been moved to a branch amber-0.10 which reflects OAuth
0.10 spec
 - The new trunk is being updated to latest 0.22 spec version
 - Versions of artifacts have been aligned to the supported OAuth
specification supported
 - Discussion about preparing for an initial release is ongoing



Any23

Any23 is defined as a Java library, a Web service and a set of command line
tools to extract and validate structured data in RDF format from a variety
of Web documents and markup formats. Any23 is what it is informally named an
RDF Distiller.

A list of the three most important issues to address in the move towards
graduation

   1. Port Any23 code to ASF infrastructure and update license headers
   2. Develop a strong community with organizational diversity and with
strong connections to other relevant ASF communities.
   3. At least one Any23 incubating release

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

Yes, there has been ongoing work to bring the Any23 codebase to Apache SVN.
The final stages include loading the code dump to the Apache test repos,
there will then be a short time for the dev/committer team to review 

RE: October 2011 Incubator Board Report

[Noel J. Bergman]

 Our next report is due in December, not October.

Nu?  So where is it?

--- Noel


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

Re: Missing reports (was: Re: Incubator Board Report November 2011)

[Dennis Lundberg]

On 2011-11-16 21:53, Dennis Lundberg wrote:
 Hi
 
 I am one of the mentors for NPanday. We did not provide a report this
 month. We apologize for this.
 
 Like Stefan I cannot seem to find the handy reminder e-mail that usually
 comes on the first day of the reporting month. Neither in my inbox nor
 the dev-list archive.
 
 Do you want us to report next month instead?

I never got an answer to this. Anyone?


If so, I guess I'll need to update this wiki page right?

http://wiki.apache.org/incubator/ReportingSchedule


 
 
 On 2011-11-16 11:57, Christian Grobmeier wrote:
 This time were 7 reports missed (leaving out S4):

 On Wed, Nov 16, 2011 at 5:41 AM, Noel J. Bergman n...@devtech.com wrote:
 Amber
 HISE
 Kalumet
 Lucene.NET
 NPanday
 Zeta Components

 Stonehenge
 SHOULD BE RETIRED.

 I am a Mentor of Zeta. This time I have not had the time to push the
 report. A pity, nobody else felt responsible. I have asked at the
 developers list about the activity of the podling.

 Can we hear from the mentors of the other projects what is going on in
 their podlings?
 A mentors response is what we should get when report is missed by default.

 In addition I think we should notify Stonehenge about retiring them
 and afterward start a vote here finally.

 Thoughts?

 Cheers
 Christian

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


 
 


-- 
Dennis Lundberg

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

Re: Missing reports (was: Re: Incubator Board Report November 2011)

[Bertrand Delacretaz]

On Wednesday, November 30, 2011, Dennis Lundberg wrote:

On 2011-11-16 21:53, Dennis Lundberg wrote:
 ...I am one of the mentors for NPanday. We did not provide a report this
 month. We apologize for this...

 Do you want us to report next month instead?

I'd say yes, report at the next opportunity.

...If so, I guess I'll need to update this wiki page right?

http://wiki.apache.org/incubator/ReportingSchedule

I don't think so, just go back to your normal schedule after the shifted
report.

-Bertrand

Re: Missing reports (was: Re: Incubator Board Report November 2011)

[David Crossley]

Jim Jagielski wrote:

 For now on, Marvin which sends the reminder Emails to the PMCs
 will also send reminders to all the PPMCs (via their *-dev@ lists)
 as well as the summary to IPMC.
 
 It's crucial the that
   http://incubator.apache.org/report_due_[123].txt
 page be up to date and correct since Marvin still pulls the
 needs to report as well as email address from that
 location.

Thanks to Upayavira for starting it and Jim for integrating
it to big Marvin.

Those files are generated by Clutch.
It reads the ReportingSchedule [1] wiki, then verifies that their
dev list is operational. If not, then they are listed with the
default general@ address.

So another plea to podlings to keep their entry in [1]
up-to-date.

[1] http://wiki.apache.org/incubator/ReportingSchedule

-David

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

Re: Actively retiring projects (was: Incubator Board Report November 2011)

[Sam Ruby]

On Wed, Nov 16, 2011 at 3:36 PM, Sam Ruby ru...@intertwingly.net wrote:

 Looking at the current list of projects, we have many that exceed that
 number.  Far exceed that number.  In fact the median age is 416 days
 and the mean age is 536.

Thanks to Gavin installing the necessary prerequisites on
people.apache.org, a richer (and live) presentation of this data can
be found here:

  http://people.apache.org/~rubys/incubator-by-age

- Sam Ruby

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

Re: Actively retiring projects (was: Incubator Board Report November 2011)

[Christian Grobmeier]

On Sun, Nov 20, 2011 at 1:47 PM, Sam Ruby ru...@intertwingly.net wrote:
 On Wed, Nov 16, 2011 at 3:36 PM, Sam Ruby ru...@intertwingly.net wrote:

 Looking at the current list of projects, we have many that exceed that
 number.  Far exceed that number.  In fact the median age is 416 days
 and the mean age is 536.

 Thanks to Gavin installing the necessary prerequisites on
 people.apache.org, a richer (and live) presentation of this data can
 be found here:

  http://people.apache.org/~rubys/incubator-by-age

I think there are more tools like this around... i think it makes
sense to somehow link them on the incubator website if possible.
Right?


 - Sam Ruby

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




-- 
http://www.grobmeier.de
https://www.timeandbill.de

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

Re: Actively retiring projects (was: Incubator Board Report November 2011)

[Mohammad Nour El-Din]

On Fri, Nov 18, 2011 at 8:23 AM, Henri Yandell flame...@gmail.com wrote:

 On Wed, Nov 16, 2011 at 12:36 PM, Sam Ruby ru...@intertwingly.net wrote:
  On Tue, Nov 15, 2011 at 11:41 PM, Noel J. Bergman n...@devtech.com
 wrote:
 
  We are, however, recognizing that we've had growth issues of our own.
  As
  David Crossley pointed out, he made mistakes last month related to the
  Reporting Schedule, and we continue to have issues.  The Incubator is
 almost
  as big as the rest of the ASF combined.  David posted a plot chart
  reflecting our growth: http://incubator.apache.org/history/
 
  Excellent plot chart.  As with most plot charts, the end result is a
  Rorschach test.  I'll tell you what I (personally) see in this chart:
  a failure to perform garbage collection.  My personal perspective is
  that incubation shouldn't generally take more than a year.  That
  doesn't mean that there won't be exceptions, and in a few rare cases,
  some that go well beyond that arbitrary time limit, but the point is
  that those should be the exception rather than the rule.

 Now that time is freeing up a tiny bit, I need to document a thread
 from August that would put pressure on projects who haven't done their
 IP handling. I'm less worried about a podling who haven't graduated
 after 12 months and more worried about a podling who haven't managed
 to get their CLAs right within 3 months. We still have far too many
 podlings who haven't signed off on that (first) part of their
 incubation.

 So +1 in sentiment, but a different focus.


+1 on the same point



 Hen

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




-- 
Thanks
- Mohammad Nour

Life is like riding a bicycle. To keep your balance you must keep moving
- Albert Einstein

Re: Actively retiring projects (was: Incubator Board Report November 2011)

[Mohammad Nour El-Din]

On Sun, Nov 20, 2011 at 3:01 PM, Christian Grobmeier grobme...@gmail.comwrote:

 On Sun, Nov 20, 2011 at 1:47 PM, Sam Ruby ru...@intertwingly.net wrote:
  On Wed, Nov 16, 2011 at 3:36 PM, Sam Ruby ru...@intertwingly.net
 wrote:
 
  Looking at the current list of projects, we have many that exceed that
  number.  Far exceed that number.  In fact the median age is 416 days
  and the mean age is 536.
 
  Thanks to Gavin installing the necessary prerequisites on
  people.apache.org, a richer (and live) presentation of this data can
  be found here:
 
   http://people.apache.org/~rubys/incubator-by-age

 I think there are more tools like this around... i think it makes
 sense to somehow link them on the incubator website if possible.
 Right?


IDK, should such information be public to that level, or only discussed on
the level of the IPMC ?



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



 --
 http://www.grobmeier.de
 https://www.timeandbill.de

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




-- 
Thanks
- Mohammad Nour

Life is like riding a bicycle. To keep your balance you must keep moving
- Albert Einstein

Re: Actively retiring projects (was: Incubator Board Report November 2011)

[Christian Grobmeier]

On Sun, Nov 20, 2011 at 2:17 PM, Mohammad Nour El-Din
nour.moham...@gmail.com wrote:
 On Sun, Nov 20, 2011 at 3:01 PM, Christian Grobmeier 
 grobme...@gmail.comwrote:
   http://people.apache.org/~rubys/incubator-by-age

 I think there are more tools like this around... i think it makes
 sense to somehow link them on the incubator website if possible.
 Right?

 IDK, should such information be public to that level, or only discussed on
 the level of the IPMC ?

Well, Sams script is already public. In addition - what data show
there is so sensitive we can't make it public?




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



 --
 http://www.grobmeier.de
 https://www.timeandbill.de

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




 --
 Thanks
 - Mohammad Nour
 
 Life is like riding a bicycle. To keep your balance you must keep moving
 - Albert Einstein



-- 
http://www.grobmeier.de
https://www.timeandbill.de

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

Re: Missing reports (was: Re: Incubator Board Report November 2011)

[Jim Jagielski]

For now on, Marvin which sends the reminder Emails to the PMCs
will also send reminders to all the PPMCs (via their *-dev@ lists)
as well as the summary to IPMC.

It's crucial the that
http://incubator.apache.org/report_due_[123].txt
page be up to date and correct since Marvin still pulls the
needs to report as well as email address from that
location.

On Nov 16, 2011, at 3:53 PM, Dennis Lundberg wrote:

 Hi
 
 I am one of the mentors for NPanday. We did not provide a report this
 month. We apologize for this.
 
 Like Stefan I cannot seem to find the handy reminder e-mail that usually
 comes on the first day of the reporting month. Neither in my inbox nor
 the dev-list archive.
 
 Do you want us to report next month instead?
 
 
 On 2011-11-16 11:57, Christian Grobmeier wrote:
 This time were 7 reports missed (leaving out S4):
 
 On Wed, Nov 16, 2011 at 5:41 AM, Noel J. Bergman n...@devtech.com wrote:
 Amber
 HISE
 Kalumet
 Lucene.NET
 NPanday
 Zeta Components
 
 Stonehenge
 SHOULD BE RETIRED.
 
 I am a Mentor of Zeta. This time I have not had the time to push the
 report. A pity, nobody else felt responsible. I have asked at the
 developers list about the activity of the podling.
 
 Can we hear from the mentors of the other projects what is going on in
 their podlings?
 A mentors response is what we should get when report is missed by default.
 
 In addition I think we should notify Stonehenge about retiring them
 and afterward start a vote here finally.
 
 Thoughts?
 
 Cheers
 Christian
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 
 
 
 
 -- 
 Dennis Lundberg
 
 -
 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: Actively retiring projects (was: Incubator Board Report November 2011)

[Luciano Resende]

On Wed, Nov 16, 2011 at 12:36 PM, Sam Ruby ru...@intertwingly.net wrote:
 On Tue, Nov 15, 2011 at 11:41 PM, Noel J. Bergman n...@devtech.com wrote:

 We are, however, recognizing that we've had growth issues of our own.  As
 David Crossley pointed out, he made mistakes last month related to the
 Reporting Schedule, and we continue to have issues.  The Incubator is almost
 as big as the rest of the ASF combined.  David posted a plot chart
 reflecting our growth: http://incubator.apache.org/history/

 Excellent plot chart.  As with most plot charts, the end result is a
 Rorschach test.  I'll tell you what I (personally) see in this chart:
 a failure to perform garbage collection.  My personal perspective is
 that incubation shouldn't generally take more than a year.  That
 doesn't mean that there won't be exceptions, and in a few rare cases,
 some that go well beyond that arbitrary time limit, but the point is
 that those should be the exception rather than the rule.

 Looking at the current list of projects, we have many that exceed that
 number.  Far exceed that number.  In fact the median age is 416 days
 and the mean age is 536.

 People here may disagree with my arbitrary date, and that's OK.  But
 my feeling is that there needs to be an expectation that a podling
 produces AT THE VERY MINIMUM a credible plan that they are executing
 on which will lead to graduation at some point.  If they fail to
 produce such a plan, or fail to execute on that plan (within reason),
 they should be asked to explain themselves.  If they fail to do so,
 the incubation at the ASF should cease.

 At the moment, the expectation is that the mentors be the ones to take
 up this task.  For whatever reason, that isn't reliably being done.
 This causes the board to complain periodically.  I am of the belief
 that the first level of culling needs to be performed at the Incubator
 level.  If we need to appoint a set of grim reapers, lets do so, and I
 will volunteer to be a part of such an effort.

 Meanwhile, I will personally focus on JSPWiki.  If others wish to join
 me, here is a a current list of projects that have been incubating
 more than a year:

 2007-09-17 JSPWiki
 2008-01-06 RAT
 2008-05-20 Hama
 2008-07-08 Empire-db
 2008-08-19 PhotArk
 2008-09-02 Etch
 2008-09-04 Tashi
 2008-09-29 Olio
 2008-10-06 VCL
 2008-10-09 Droids
 2008-11-06 Kato
 2008-11-19 Stonehenge
 2009-04-24 Ace
 2009-05-27 Wink
 2009-07-06 VXQuery
 2009-07-17 Wookie
 2009-11-05 HISE
 2009-11-27 Clerezza
 2010-01-10 Manifold Connector Framework (ManifoldCF)
 2010-02-21 SIS
 2010-03-01 Bean Validation
 2010-05-09 Amber
 2010-05-19 Deltacloud
 2010-05-21 Zeta Components
 2010-06-24 Nuvem
 2010-07-14 Chukwa
 2010-07-22 Lucy
 2010-08-13 NPanday
 2010-09-07 Isis
 2010-09-26 Gora
 2010-10-03 Kitty
 2010-11-02 Celix
 2010-11-15 Stanbol

 - Sam Ruby


Maybe I've had been using a high bar with the podlings I
mentor/participate. I'll look into graduating couple podlings after I
come back from Thanks Giving : Apache PhotArk, Apache Wink.


-- 
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: Actively retiring projects (was: Incubator Board Report November 2011)

[Henri Yandell]

On Sun, Nov 20, 2011 at 8:11 AM, Luciano Resende luckbr1...@gmail.com wrote:

 Maybe I've had been using a high bar with the podlings I
 mentor/participate. I'll look into graduating couple podlings after I
 come back from Thanks Giving : Apache PhotArk, Apache Wink.

First things first - can you get Wink's copyright status sorted out?
It's not signed off on the status page yet to say that we have the
rights to host the code.

This had better just be a case of no one having updated the right page
given that Wink appears to have been making releases.

Hen

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

Re: Actively retiring projects (was: Incubator Board Report November 2011)

[Brett Porter]

On 16/11/2011, at 12:36 PM, Sam Ruby wrote:

 My personal perspective is
 that incubation shouldn't generally take more than a year.  That
 doesn't mean that there won't be exceptions, and in a few rare cases,
 some that go well beyond that arbitrary time limit, but the point is
 that those should be the exception rather than the rule.

I agree with that period of time, but would avoid throwing that number around 
too much as they tend to become unwritten rules. A much better criteria is the 
other you've mentioned...

 But
 my feeling is that there needs to be an expectation that a podling
 produces AT THE VERY MINIMUM a credible plan that they are executing
 on which will lead to graduation at some point.  If they fail to
 produce such a plan, or fail to execute on that plan (within reason),
 they should be asked to explain themselves.  If they fail to do so,
 the incubation at the ASF should cease.

For those interested, this was the topic of my talk at ApacheCon this year: 
http://lanyrd.com/2011/apachecon-north-america/skdqx/

We ask for these in each podling report, but the top 3 things tend to not 
have enough detail (actions to take), or list the wrong types of things without 
reasoning.

I think we should be asking podlings to have a more complete graduation plan by 
their 3rd month - even if it has gaps they know they need to fill, or places it 
may change in future.

Cheers,
Brett

--
Brett Porter
br...@apache.org
http://brettporter.wordpress.com/


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

Re: Actively retiring projects (was: Incubator Board Report November 2011)

[Kevan Miller]

On Nov 20, 2011, at 2:14 PM, Henri Yandell wrote:

 On Sun, Nov 20, 2011 at 8:11 AM, Luciano Resende luckbr1...@gmail.com wrote:
 
 Maybe I've had been using a high bar with the podlings I
 mentor/participate. I'll look into graduating couple podlings after I
 come back from Thanks Giving : Apache PhotArk, Apache Wink.
 
 First things first - can you get Wink's copyright status sorted out?
 It's not signed off on the status page yet to say that we have the
 rights to host the code.
 
 This had better just be a case of no one having updated the right page
 given that Wink appears to have been making releases.

Yes, it is… There were initial donations from both IBM and HP. The HP donation 
was chosen as the initial Wink implementation. 

I'll verify the grants (though I recall checking them during the initial 
contribution) and update the status.

--kevan


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

Re: Actively retiring projects (was: Incubator Board Report November 2011)

[ant elder]

On Fri, Nov 18, 2011 at 9:09 AM, Robert Burrell Donkin
robertburrelldon...@gmail.com wrote:
 On Fri, Nov 18, 2011 at 6:23 AM, Henri Yandell flame...@gmail.com wrote:
 On Wed, Nov 16, 2011 at 12:36 PM, Sam Ruby ru...@intertwingly.net wrote:
 On Tue, Nov 15, 2011 at 11:41 PM, Noel J. Bergman n...@devtech.com wrote:

 We are, however, recognizing that we've had growth issues of our own.  As
 David Crossley pointed out, he made mistakes last month related to the
 Reporting Schedule, and we continue to have issues.  The Incubator is 
 almost
 as big as the rest of the ASF combined.  David posted a plot chart
 reflecting our growth: http://incubator.apache.org/history/

 Excellent plot chart.  As with most plot charts, the end result is a
 Rorschach test.  I'll tell you what I (personally) see in this chart:
 a failure to perform garbage collection.  My personal perspective is
 that incubation shouldn't generally take more than a year.  That
 doesn't mean that there won't be exceptions, and in a few rare cases,
 some that go well beyond that arbitrary time limit, but the point is
 that those should be the exception rather than the rule.

 Sometimes when you turn up the heat and reduce the cooking time, the
 pies end up being half baked...


I agree with that and also with Benson's comments about size and
growth often being one of the barriers to graduation. A number of the
long term poddlings don't have a very diverse or even three active
committers, if theres a threat of expulsion because of that they'll
probably just start making any old person a committer just to make up
the numbers.

   ...ant

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

Re: Actively retiring projects (was: Incubator Board Report November 2011)

[Robert Burrell Donkin]

On Fri, Nov 18, 2011 at 6:23 AM, Henri Yandell flame...@gmail.com wrote:
 On Wed, Nov 16, 2011 at 12:36 PM, Sam Ruby ru...@intertwingly.net wrote:
 On Tue, Nov 15, 2011 at 11:41 PM, Noel J. Bergman n...@devtech.com wrote:

 We are, however, recognizing that we've had growth issues of our own.  As
 David Crossley pointed out, he made mistakes last month related to the
 Reporting Schedule, and we continue to have issues.  The Incubator is almost
 as big as the rest of the ASF combined.  David posted a plot chart
 reflecting our growth: http://incubator.apache.org/history/

 Excellent plot chart.  As with most plot charts, the end result is a
 Rorschach test.  I'll tell you what I (personally) see in this chart:
 a failure to perform garbage collection.  My personal perspective is
 that incubation shouldn't generally take more than a year.  That
 doesn't mean that there won't be exceptions, and in a few rare cases,
 some that go well beyond that arbitrary time limit, but the point is
 that those should be the exception rather than the rule.

Sometimes when you turn up the heat and reduce the cooking time, the
pies end up being half baked...

I think that it should be possible to reduce mean graduation time for
main sequence podlings by tuning the process but worry about moving
away from graduation by acclamation and consensus towards a contested
system. I think this will happen if we just reduce time and increase
the pressure.

 Now that time is freeing up a tiny bit, I need to document a thread
 from August that would put pressure on projects who haven't done their
 IP handling. I'm less worried about a podling who haven't graduated
 after 12 months and more worried about a podling who haven't managed
 to get their CLAs right within 3 months. We still have far too many
 podlings who haven't signed off on that (first) part of their
 incubation.

+1

Defining a more linear process for main sequence podlings would
probably make sense and focus efforts towards graduation priorities

Robert

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

Re: Actively retiring projects (was: Incubator Board Report November 2011)

[Donald Whytock]

On Wed, Nov 16, 2011 at 8:27 PM, Benson Margulies bimargul...@gmail.com wrote:
 I can see two problems with this view to begin with. One is IP
 management. The more people participate in a project and the longer
 they do so, the messier it becomes to track provenance and get ICLAs
 from all of the contributors. One almost wishes that the ASF could
 accept ICLAs and code grants for code that is in fact living somewhere
 else. I'm sure someone will tell me why that idea is nuts.

Well, if the code is living somewhere else, that means the code in ASF
would be taking up space for possibly no good reason, as people might
more habitually go to where the code is living.

On the other hand, the ASF could theoretically act as a last line of
defense against system failure, community dissolution,
sociopolitically-motivated bogus forking, etc., in that if all else
fails people can go to Apache to get a stable release of something.

I'm sorry...was that a rhetorical question?

Don

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

Re: Actively retiring projects (was: Incubator Board Report November 2011)

[Robert Burrell Donkin]

On Thu, Nov 17, 2011 at 1:40 AM, Sam Ruby ru...@intertwingly.net wrote:
 On Wed, Nov 16, 2011 at 8:17 PM, Mohammad Nour El-Din
 nour.moham...@gmail.com wrote:
 Hi...

   The idea sounds good in general more specifically that should be clear
 and documented on the incubator site for future incubating projects. But,
 IMHO, we should categorize projects mentioned in that list from very old to
 recent ones and each group of mentors get in touch with their mentored
 projects and get with some feedback about such plan, so we can be more fair
 and give people a chance either to do some progress, more specifically for
 recent incubated projects and even for the older projects to revive if that
 is possible.

 Thoughts ?

 Nobody is proposing immediate expulsion of any PPMC based solely on a metric.

 On the other hand, it should not be a surprise to mentors that they
 are responsible for[1] assessment of the Podling status with respect
 to continuation/exit strategy.  Reports for PPMCs that are older than
 a year should be expected to contain this information.  Repeated
 failure to include such information and/or demonstrate forward
 progress towards meeting these objectives should cause the Incubator
 (not the Board!) to take action.

I think this is more about pushing ourselves, and less about pushing podlings

The Incubator now has a process which works okay for many podlings.
The challenge now is to focus more effort on those cases where the
process isn't working. Metrics are useful in discovering and
highlighting sub-populations.

Robert

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

Re: Actively retiring projects (was: Incubator Board Report November 2011)

[Nick Burch]

On Wed, 16 Nov 2011, Sam Ruby wrote:

Meanwhile, I will personally focus on JSPWiki.  If others wish to join
me, here is a a current list of projects that have been incubating
more than a year:


I've been meaning to try to help out with JSPWiki for a while, but I've 
not yet had the time. If there's going to be more than one of us though, 
then hopefully the work involved will be something I can commit to


Currently the JSPWiki mentors are listed as:
 * snoopdave - Dave Johnson
 * clr - Craig Russell
 * henning - Henning Schmiedehausen
 * rubys - Sam Ruby

Are any of the others currently active and able to help?

(My hunch from having spoken to a few jspwiki community members is that we 
need to have another go at helping them understand the apache way, then 
give a deadline, but I've not looked in detail to be sure)


Nick

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

Re: Actively retiring projects (was: Incubator Board Report November 2011)

[Henri Yandell]

On Wed, Nov 16, 2011 at 12:36 PM, Sam Ruby ru...@intertwingly.net wrote:
 On Tue, Nov 15, 2011 at 11:41 PM, Noel J. Bergman n...@devtech.com wrote:

 We are, however, recognizing that we've had growth issues of our own.  As
 David Crossley pointed out, he made mistakes last month related to the
 Reporting Schedule, and we continue to have issues.  The Incubator is almost
 as big as the rest of the ASF combined.  David posted a plot chart
 reflecting our growth: http://incubator.apache.org/history/

 Excellent plot chart.  As with most plot charts, the end result is a
 Rorschach test.  I'll tell you what I (personally) see in this chart:
 a failure to perform garbage collection.  My personal perspective is
 that incubation shouldn't generally take more than a year.  That
 doesn't mean that there won't be exceptions, and in a few rare cases,
 some that go well beyond that arbitrary time limit, but the point is
 that those should be the exception rather than the rule.

Now that time is freeing up a tiny bit, I need to document a thread
from August that would put pressure on projects who haven't done their
IP handling. I'm less worried about a podling who haven't graduated
after 12 months and more worried about a podling who haven't managed
to get their CLAs right within 3 months. We still have far too many
podlings who haven't signed off on that (first) part of their
incubation.

So +1 in sentiment, but a different focus.

Hen

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

Missing reports (was: Re: Incubator Board Report November 2011)

[Christian Grobmeier]

This time were 7 reports missed (leaving out S4):

On Wed, Nov 16, 2011 at 5:41 AM, Noel J. Bergman n...@devtech.com wrote:
 Amber
 HISE
 Kalumet
 Lucene.NET
 NPanday
 Zeta Components

 Stonehenge
 SHOULD BE RETIRED.

I am a Mentor of Zeta. This time I have not had the time to push the
report. A pity, nobody else felt responsible. I have asked at the
developers list about the activity of the podling.

Can we hear from the mentors of the other projects what is going on in
their podlings?
A mentors response is what we should get when report is missed by default.

In addition I think we should notify Stonehenge about retiring them
and afterward start a vote here finally.

Thoughts?

Cheers
Christian

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

Actively retiring projects (was: Incubator Board Report November 2011)

[Sam Ruby]

On Tue, Nov 15, 2011 at 11:41 PM, Noel J. Bergman n...@devtech.com wrote:

 We are, however, recognizing that we've had growth issues of our own.  As
 David Crossley pointed out, he made mistakes last month related to the
 Reporting Schedule, and we continue to have issues.  The Incubator is almost
 as big as the rest of the ASF combined.  David posted a plot chart
 reflecting our growth: http://incubator.apache.org/history/

Excellent plot chart.  As with most plot charts, the end result is a
Rorschach test.  I'll tell you what I (personally) see in this chart:
a failure to perform garbage collection.  My personal perspective is
that incubation shouldn't generally take more than a year.  That
doesn't mean that there won't be exceptions, and in a few rare cases,
some that go well beyond that arbitrary time limit, but the point is
that those should be the exception rather than the rule.

Looking at the current list of projects, we have many that exceed that
number.  Far exceed that number.  In fact the median age is 416 days
and the mean age is 536.

People here may disagree with my arbitrary date, and that's OK.  But
my feeling is that there needs to be an expectation that a podling
produces AT THE VERY MINIMUM a credible plan that they are executing
on which will lead to graduation at some point.  If they fail to
produce such a plan, or fail to execute on that plan (within reason),
they should be asked to explain themselves.  If they fail to do so,
the incubation at the ASF should cease.

At the moment, the expectation is that the mentors be the ones to take
up this task.  For whatever reason, that isn't reliably being done.
This causes the board to complain periodically.  I am of the belief
that the first level of culling needs to be performed at the Incubator
level.  If we need to appoint a set of grim reapers, lets do so, and I
will volunteer to be a part of such an effort.

Meanwhile, I will personally focus on JSPWiki.  If others wish to join
me, here is a a current list of projects that have been incubating
more than a year:

2007-09-17 JSPWiki
2008-01-06 RAT
2008-05-20 Hama
2008-07-08 Empire-db
2008-08-19 PhotArk
2008-09-02 Etch
2008-09-04 Tashi
2008-09-29 Olio
2008-10-06 VCL
2008-10-09 Droids
2008-11-06 Kato
2008-11-19 Stonehenge
2009-04-24 Ace
2009-05-27 Wink
2009-07-06 VXQuery
2009-07-17 Wookie
2009-11-05 HISE
2009-11-27 Clerezza
2010-01-10 Manifold Connector Framework (ManifoldCF)
2010-02-21 SIS
2010-03-01 Bean Validation
2010-05-09 Amber
2010-05-19 Deltacloud
2010-05-21 Zeta Components
2010-06-24 Nuvem
2010-07-14 Chukwa
2010-07-22 Lucy
2010-08-13 NPanday
2010-09-07 Isis
2010-09-26 Gora
2010-10-03 Kitty
2010-11-02 Celix
2010-11-15 Stanbol

- Sam Ruby

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

Re: Actively retiring projects (was: Incubator Board Report November 2011)

[Christian Grobmeier]

On Wed, Nov 16, 2011 at 9:36 PM, Sam Ruby ru...@intertwingly.net wrote:
 On Tue, Nov 15, 2011 at 11:41 PM, Noel J. Bergman n...@devtech.com wrote:
 Excellent plot chart.  As with most plot charts, the end result is a
 Rorschach test.  I'll tell you what I (personally) see in this chart:
 a failure to perform garbage collection.  My personal perspective is
 that incubation shouldn't generally take more than a year.  That
 doesn't mean that there won't be exceptions, and in a few rare cases,
 some that go well beyond that arbitrary time limit, but the point is
 that those should be the exception rather than the rule.

 Looking at the current list of projects, we have many that exceed that
 number.  Far exceed that number.  In fact the median age is 416 days
 and the mean age is 536.

 People here may disagree with my arbitrary date, and that's OK.  But
 my feeling is that there needs to be an expectation that a podling
 produces AT THE VERY MINIMUM a credible plan that they are executing
 on which will lead to graduation at some point.  If they fail to
 produce such a plan, or fail to execute on that plan (within reason),
 they should be asked to explain themselves.  If they fail to do so,
 the incubation at the ASF should cease.

+1

 At the moment, the expectation is that the mentors be the ones to take
 up this task.  For whatever reason, that isn't reliably being done.
 This causes the board to complain periodically.  I am of the belief
 that the first level of culling needs to be performed at the Incubator
 level.  If we need to appoint a set of grim reapers, lets do so, and I
 will volunteer to be a part of such an effort.

+1

I observe several podlings and sometimes I have the feeling that
Mentors are not very active. In addition I welcome such a grim reaper
committee.

I would suggest a semi automatic process for projects who fail to
report (as suggested today). One of the mentors should explain why the
report has failed.

 Meanwhile, I will personally focus on JSPWiki.  If others wish to join
 me, here is a a current list of projects that have been incubating
 more than a year:

On the report is Stonehenge mentioned for garbage collection.
I spoke to Zeta people today, I still get responses there. Discussion
is, how things can be improved. I would leave them there and let's
hope, situation is fixed soon.

Deltacloud has graduated and can be put off from your list.
Rat is discussing graduation and should be moved from the list too.

On the other projects I can't tell much.

Therefore I am for +1 to start retiring discussion on JSPWiki and Stonehenge

Cheers


 2007-09-17 JSPWiki
 2008-01-06 RAT
 2008-05-20 Hama
 2008-07-08 Empire-db
 2008-08-19 PhotArk
 2008-09-02 Etch
 2008-09-04 Tashi
 2008-09-29 Olio
 2008-10-06 VCL
 2008-10-09 Droids
 2008-11-06 Kato
 2008-11-19 Stonehenge
 2009-04-24 Ace
 2009-05-27 Wink
 2009-07-06 VXQuery
 2009-07-17 Wookie
 2009-11-05 HISE
 2009-11-27 Clerezza
 2010-01-10 Manifold Connector Framework (ManifoldCF)
 2010-02-21 SIS
 2010-03-01 Bean Validation
 2010-05-09 Amber
 2010-05-19 Deltacloud
 2010-05-21 Zeta Components
 2010-06-24 Nuvem
 2010-07-14 Chukwa
 2010-07-22 Lucy
 2010-08-13 NPanday
 2010-09-07 Isis
 2010-09-26 Gora
 2010-10-03 Kitty
 2010-11-02 Celix
 2010-11-15 Stanbol

 - Sam Ruby

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





-- 
http://www.grobmeier.de

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

Re: Missing reports (was: Re: Incubator Board Report November 2011)

[Dennis Lundberg]

Hi

I am one of the mentors for NPanday. We did not provide a report this
month. We apologize for this.

Like Stefan I cannot seem to find the handy reminder e-mail that usually
comes on the first day of the reporting month. Neither in my inbox nor
the dev-list archive.

Do you want us to report next month instead?


On 2011-11-16 11:57, Christian Grobmeier wrote:
 This time were 7 reports missed (leaving out S4):
 
 On Wed, Nov 16, 2011 at 5:41 AM, Noel J. Bergman n...@devtech.com wrote:
 Amber
 HISE
 Kalumet
 Lucene.NET
 NPanday
 Zeta Components
 
 Stonehenge
 SHOULD BE RETIRED.
 
 I am a Mentor of Zeta. This time I have not had the time to push the
 report. A pity, nobody else felt responsible. I have asked at the
 developers list about the activity of the podling.
 
 Can we hear from the mentors of the other projects what is going on in
 their podlings?
 A mentors response is what we should get when report is missed by default.
 
 In addition I think we should notify Stonehenge about retiring them
 and afterward start a vote here finally.
 
 Thoughts?
 
 Cheers
 Christian
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 
 


-- 
Dennis Lundberg

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

Re: Actively retiring projects (was: Incubator Board Report November 2011)

[Daniel Kulp]

On Wednesday, November 16, 2011 9:48:02 PM Christian Grobmeier wrote:
 On Wed, Nov 16, 2011 at 9:36 PM, Sam Ruby ru...@intertwingly.net wrote:
  Meanwhile, I will personally focus on JSPWiki.  If others wish to join
  me, here is a a current list of projects that have been incubating
 
  more than a year:
 On the report is Stonehenge mentioned for garbage collection.
 I spoke to Zeta people today, I still get responses there. Discussion
 is, how things can be improved. I would leave them there and let's
 hope, situation is fixed soon.
 
 Deltacloud has graduated and can be put off from your list.
 Rat is discussing graduation and should be moved from the list too.
 
 On the other projects I can't tell much.
 
 Therefore I am for +1 to start retiring discussion on JSPWiki and Stonehenge 

We've already voted to retire Stonehenge.   The mentors have been too busy 
with other things to finish the final cleanup.  As one of the mentors, I'll 
take the blame for that.  :-(


-- 
Daniel Kulp
dk...@apache.org
http://dankulp.com/blog
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: Actively retiring projects (was: Incubator Board Report November 2011)

[Sam Ruby]

On Wed, Nov 16, 2011 at 3:48 PM, Christian Grobmeier
grobme...@gmail.com wrote:

 Deltacloud has graduated and can be put off from your list.
 Rat is discussing graduation and should be moved from the list too.

The master list from which I drew the data can be found here:

http://incubator.apache.org/projects/

The script I used is attached to this message

- Sam Ruby


incubator.rb
Description: application/ruby

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

Re: Missing reports (was: Re: Incubator Board Report November 2011)

[Christian Grobmeier]

Actually I checked and could not find a reminder for Zeta dev too.

On Wed, Nov 16, 2011 at 9:53 PM, Dennis Lundberg denn...@apache.org wrote:
 Hi

 I am one of the mentors for NPanday. We did not provide a report this
 month. We apologize for this.

 Like Stefan I cannot seem to find the handy reminder e-mail that usually
 comes on the first day of the reporting month. Neither in my inbox nor
 the dev-list archive.

 Do you want us to report next month instead?


 On 2011-11-16 11:57, Christian Grobmeier wrote:
 This time were 7 reports missed (leaving out S4):

 On Wed, Nov 16, 2011 at 5:41 AM, Noel J. Bergman n...@devtech.com wrote:
 Amber
 HISE
 Kalumet
 Lucene.NET
 NPanday
 Zeta Components

 Stonehenge
 SHOULD BE RETIRED.

 I am a Mentor of Zeta. This time I have not had the time to push the
 report. A pity, nobody else felt responsible. I have asked at the
 developers list about the activity of the podling.

 Can we hear from the mentors of the other projects what is going on in
 their podlings?
 A mentors response is what we should get when report is missed by default.

 In addition I think we should notify Stonehenge about retiring them
 and afterward start a vote here finally.

 Thoughts?

 Cheers
 Christian

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




 --
 Dennis Lundberg

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





-- 
http://www.grobmeier.de

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

Re: Actively retiring projects (was: Incubator Board Report November 2011)

[Christian Grobmeier]

On Wed, Nov 16, 2011 at 9:57 PM, Sam Ruby ru...@intertwingly.net wrote:
 On Wed, Nov 16, 2011 at 3:48 PM, Christian Grobmeier
 grobme...@gmail.com wrote:

 Deltacloud has graduated and can be put off from your list.
 Rat is discussing graduation and should be moved from the list too.

 The master list from which I drew the data can be found here:

 http://incubator.apache.org/projects/

 The script I used is attached to this message

The script is fine.
Deltacloud has not started graduation yet (just the vote is done).
And I follow the rat-dev list, therefore I can say there is efford in
graduation direction

Cheers


 - Sam Ruby


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




-- 
http://www.grobmeier.de

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

Re: Actively retiring projects (was: Incubator Board Report November 2011)

[sebb]

On 16 November 2011 20:57, Sam Ruby ru...@intertwingly.net wrote:
 On Wed, Nov 16, 2011 at 3:48 PM, Christian Grobmeier
 grobme...@gmail.com wrote:

 Deltacloud has graduated and can be put off from your list.
 Rat is discussing graduation and should be moved from the list too.

 The master list from which I drew the data can be found here:

 http://incubator.apache.org/projects/

By the way, that page is now generated from an XML file which may be
easier to parse:

http://incubator.apache.org/podlings.xml
with DTD
http://incubator.apache.org/podlings.dtd

The original versions are also in SVN at :

https://svn.apache.org/repos/asf/incubator/public/trunk/site-author

 The script I used is attached to this message

 - Sam Ruby


 -
 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: Actively retiring projects (was: Incubator Board Report November 2011)

[Benson Margulies]

I have been working to get Empire-DB to graduate, and I expect to have
a vote in front of general@ quite soon.

On Wed, Nov 16, 2011 at 5:17 PM, sebb seb...@gmail.com wrote:
 On 16 November 2011 20:57, Sam Ruby ru...@intertwingly.net wrote:
 On Wed, Nov 16, 2011 at 3:48 PM, Christian Grobmeier
 grobme...@gmail.com wrote:

 Deltacloud has graduated and can be put off from your list.
 Rat is discussing graduation and should be moved from the list too.

 The master list from which I drew the data can be found here:

 http://incubator.apache.org/projects/

 By the way, that page is now generated from an XML file which may be
 easier to parse:

 http://incubator.apache.org/podlings.xml
 with DTD
 http://incubator.apache.org/podlings.dtd

 The original versions are also in SVN at :

 https://svn.apache.org/repos/asf/incubator/public/trunk/site-author

 The script I used is attached to this message

 - Sam Ruby


 -
 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: Actively retiring projects (was: Incubator Board Report November 2011)

[David Crossley]

Sam Ruby wrote:
 Noel J. Bergman wrote:
 
  We are, however, recognizing that we've had growth issues of our own.  As
  David Crossley pointed out, he made mistakes last month related to the
  Reporting Schedule, and we continue to have issues.  The Incubator is almost
  as big as the rest of the ASF combined.  David posted a plot chart
  reflecting our growth: http://incubator.apache.org/history/

 Excellent plot chart.  As with most plot charts, the end result is a
 Rorschach test.  I'll tell you what I (personally) see in this chart:
 a failure to perform garbage collection.

That is one of the main reasons that i made it.
As i said in its recent announcement, this is not sustainable
to have 60 projects in the incubator at once.

Clutch has also been attempting to show where more attention
is needed: http://incubator.apache.org/clutch.html
Look for anything coloured vermilion-red (as explained there).
Especially these columns:
 B: elapsedDays
 H: statusAge

Some time ago we tried a process whereby the whole Incubator
would help to get projects who were stuck to get over their hurdles.
http://s.apache.org/graduation-appeal
[appeal] Help Us Graduate!

I still think that the idea should be useful, but we obviously
need the graduation-plan-or-retire approach too.

-David

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

Re: Missing reports (was: Re: Incubator Board Report November 2011)

[David Crossley]

Dennis Lundberg wrote:
 
 Like Stefan I cannot seem to find the handy reminder e-mail that usually
 comes on the first day of the reporting month. Neither in my inbox nor
 the dev-list archive.

As explained here early this month, the automated reminder
failed because there was an extra board meeting this month
which tricked the marvin script.

Each project needs to care for their entry in the
http://wiki.apache.org/incubator/ReportingSchedule
and be aware of their own reporting month.

-David

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

Re: Missing reports (was: Re: Incubator Board Report November 2011)

[Mohammad Nour El-Din]

Hi...

   Having automated e-mails sent as reminders is a good thing and handy
too. But, IMHO, even with having this in hand mentors *should* be following
up with their mentored projects just in case something went wrong with the
automation scripts like what happened this time, also to follow up with the
reporting schedule and see if their mentored projects should report on a
specific month or not and whether the schedule is correct or not.

On Thu, Nov 17, 2011 at 2:55 AM, David Crossley cross...@apache.org wrote:

 Dennis Lundberg wrote:
 
  Like Stefan I cannot seem to find the handy reminder e-mail that usually
  comes on the first day of the reporting month. Neither in my inbox nor
  the dev-list archive.

 As explained here early this month, the automated reminder
 failed because there was an extra board meeting this month
 which tricked the marvin script.

 Each project needs to care for their entry in the
 http://wiki.apache.org/incubator/ReportingSchedule
 and be aware of their own reporting month.

 -David

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




-- 
Thanks
- Mohammad Nour

Life is like riding a bicycle. To keep your balance you must keep moving
- Albert Einstein

Re: Actively retiring projects (was: Incubator Board Report November 2011)

[Mohammad Nour El-Din]

On Thu, Nov 17, 2011 at 12:20 AM, Benson Margulies bimargul...@gmail.comwrote:

 I have been working to get Empire-DB to graduate, and I expect to have
 a vote in front of general@ quite soon.


Same with Bean Validation the vote on the dev list is already done and next
steps will be taken soon. I take the blame for the delay.



 On Wed, Nov 16, 2011 at 5:17 PM, sebb seb...@gmail.com wrote:
  On 16 November 2011 20:57, Sam Ruby ru...@intertwingly.net wrote:
  On Wed, Nov 16, 2011 at 3:48 PM, Christian Grobmeier
  grobme...@gmail.com wrote:
 
  Deltacloud has graduated and can be put off from your list.
  Rat is discussing graduation and should be moved from the list too.
 
  The master list from which I drew the data can be found here:
 
  http://incubator.apache.org/projects/
 
  By the way, that page is now generated from an XML file which may be
  easier to parse:
 
  http://incubator.apache.org/podlings.xml
  with DTD
  http://incubator.apache.org/podlings.dtd
 
  The original versions are also in SVN at :
 
  https://svn.apache.org/repos/asf/incubator/public/trunk/site-author
 
  The script I used is attached to this message
 
  - Sam Ruby
 
 
  -
  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




-- 
Thanks
- Mohammad Nour

Life is like riding a bicycle. To keep your balance you must keep moving
- Albert Einstein

Re: Actively retiring projects (was: Incubator Board Report November 2011)

[Mohammad Nour El-Din]

Hi...

   The idea sounds good in general more specifically that should be clear
and documented on the incubator site for future incubating projects. But,
IMHO, we should categorize projects mentioned in that list from very old to
recent ones and each group of mentors get in touch with their mentored
projects and get with some feedback about such plan, so we can be more fair
and give people a chance either to do some progress, more specifically for
recent incubated projects and even for the older projects to revive if that
is possible.

Thoughts ?

On Thu, Nov 17, 2011 at 3:12 AM, Mohammad Nour El-Din 
nour.moham...@gmail.com wrote:



 On Thu, Nov 17, 2011 at 12:20 AM, Benson Margulies 
 bimargul...@gmail.comwrote:

 I have been working to get Empire-DB to graduate, and I expect to have
 a vote in front of general@ quite soon.


 Same with Bean Validation the vote on the dev list is already done and
 next steps will be taken soon. I take the blame for the delay.



 On Wed, Nov 16, 2011 at 5:17 PM, sebb seb...@gmail.com wrote:
  On 16 November 2011 20:57, Sam Ruby ru...@intertwingly.net wrote:
  On Wed, Nov 16, 2011 at 3:48 PM, Christian Grobmeier
  grobme...@gmail.com wrote:
 
  Deltacloud has graduated and can be put off from your list.
  Rat is discussing graduation and should be moved from the list too.
 
  The master list from which I drew the data can be found here:
 
  http://incubator.apache.org/projects/
 
  By the way, that page is now generated from an XML file which may be
  easier to parse:
 
  http://incubator.apache.org/podlings.xml
  with DTD
  http://incubator.apache.org/podlings.dtd
 
  The original versions are also in SVN at :
 
  https://svn.apache.org/repos/asf/incubator/public/trunk/site-author
 
  The script I used is attached to this message
 
  - Sam Ruby
 
 
  -
  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




 --
 Thanks
 - Mohammad Nour
 
 Life is like riding a bicycle. To keep your balance you must keep moving
 - Albert Einstein




-- 
Thanks
- Mohammad Nour

Life is like riding a bicycle. To keep your balance you must keep moving
- Albert Einstein

Re: Actively retiring projects (was: Incubator Board Report November 2011)

[Benson Margulies]

While I agree that it's important to confront the current inventory, I
think that the situation at hand is as much a matter of what goes into
the incubator as what comes out.

In my limited experience, size and growth are a big barrier to
graduation. If a project is chugging along exhibiting good Apache
process, but not quite achieving the necessary size, it poses a
dilemma. No one wants to exile them to the outer darkness, and no one
wants to graduate them, either.

Perhaps one implication of this is that the bar for entry with respect
to community size and diversity should be higher. In the modern world
of (ahem) github, no one needs Apache infrastructure to run an open
source project. A small group of people have any number of choices for
free and open hosting. They can come to the incubator when and if they
get are big enough to have a strong likelihood of success.

I can see two problems with this view to begin with. One is IP
management. The more people participate in a project and the longer
they do so, the messier it becomes to track provenance and get ICLAs
from all of the contributors. One almost wishes that the ASF could
accept ICLAs and code grants for code that is in fact living somewhere
else. I'm sure someone will tell me why that idea is nuts.

The second is that growth is not cured by a minimum size. We want to
see a podling do a good job of accepting new contributors. Even if a
group of 27 people shows up on a proposal and commit their brains out,
a year later there may still be 27 of them. I think that a solution
here might be for such projects to be graduated but to have a
requirement of a PMC member, or even PMC chair, who is an iPMC member
and who thus can provide an extra level of detailed supervision.

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

Re: Actively retiring projects (was: Incubator Board Report November 2011)

[Sam Ruby]

On Wed, Nov 16, 2011 at 8:17 PM, Mohammad Nour El-Din
nour.moham...@gmail.com wrote:
 Hi...

   The idea sounds good in general more specifically that should be clear
 and documented on the incubator site for future incubating projects. But,
 IMHO, we should categorize projects mentioned in that list from very old to
 recent ones and each group of mentors get in touch with their mentored
 projects and get with some feedback about such plan, so we can be more fair
 and give people a chance either to do some progress, more specifically for
 recent incubated projects and even for the older projects to revive if that
 is possible.

 Thoughts ?

Nobody is proposing immediate expulsion of any PPMC based solely on a metric.

On the other hand, it should not be a surprise to mentors that they
are responsible for[1] assessment of the Podling status with respect
to continuation/exit strategy.  Reports for PPMCs that are older than
a year should be expected to contain this information.  Repeated
failure to include such information and/or demonstrate forward
progress towards meeting these objectives should cause the Incubator
(not the Board!) to take action.

- Sam Ruby

[1] 
http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Mentor

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

Incubator Board Report November 2011

[Noel J. Bergman]

Notwithstanding the fact that members of the Board are active within the
Incubator, there are no issues requiring Board attention or intervention.

We are, however, recognizing that we've had growth issues of our own.  As
David Crossley pointed out, he made mistakes last month related to the
Reporting Schedule, and we continue to have issues.  The Incubator is almost
as big as the rest of the ASF combined.  David posted a plot chart
reflecting our growth: http://incubator.apache.org/history/

Roy proposed one change to help cut down on some commit karma logistics.
Sebb and David have been discussing some changes to help manage the
meta-data, e.g., reporting schedule.  Nothing is concrete, yet, but clearly
we need to make some changes to make things easier.

OpenMeetings -- project to provide video conferencing, instant messaging,
white board, collaborative document editing and other groupware tools using
API functions of the Red5 Streaming Server for Remoting and Streaming -- has
been accepted for Incubation.



Accumulo

Accumulo is a sorted, distributed key/value store based on BigTable's
design.  Accumulo entered incubation in September 2011.

In the move towards graduation, we must address:
1. Learning Apache procedures
2. Creating releases
3. Building a community

Community Development:
* active discussion on mailing lists and on JIRA tickets
* two new contributors have submitted patches
* web site created
* procedures and decision processes beginning to take form

Project Development:
* podling voted on release candidate for 1.3.5 (soon to be submitted to
incubator PMC)
* documented release process
* applied formatting and licenses
* fixed bugs / tested code / added documentation




Airavata

Airavata is a software toolkit which provides features to compose, manage,
execute, and monitor large scale applications and workflows on computational
resources ranging from local clusters to national grids and computing
clouds. Airavata is incubating since May 2011.

A list of the three most important issues to address in the move towards
graduation

   1. The barrier of entry in contributing to Airavata seems to be high. The
code, documentation and JIRA issues have to be efficiently organized and
managed to appeal to wider developer community.
   2. Test coverage of the code has to be increased significantly.
   3. Develop a strong community with organizational diversity and well
aligned with existing ASF projects as outlined here:
http://wiki.apache.org/incubator/AiravataProposal#Alignment

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

No, not at this time.

How has the community developed since the last report?

Patanachai Tangchaisin, Heshan Suriyarachchi and Saminda Wijeratne were
VOTEd in as committers and PPMC members on the project.
Chris, Ross, Ate, Suresh, Marlon, Raminder met at ApacheCon NA and had a
great time! Suresh's Fast Feather talk introducing Airavata went great.

How has the project developed since the last report?

* Community is efficient being engaged through maling list and JIRA.
* The code is significantly improved with proper modular organization and
packaging since entering incubation.
* Documentation and website have also been improved.
* All data base required components are integrated with Derby.
* The XRegistry component is deprecated in favor of synergizing with other
Apache repository projects like Jack Rabbit through the JCR API.
* Jenkins continuos integration and sonar code analysis dashboard are setup
and actively used by the community.
* The project is preparing its initial 0.1-incubating release, currently
VOTE'ing on the 2nd release candidate.





Amber

DID NOT REPORT




Any23

Anything To Triples (shortly Any23) defined as a Java library, a Web service
and a set of command line tools to extract and validate structured data in
RDF format from a variety of Web documents and markup formats. Any23 is what
it is informally named an RDF Distiller.

A list of the three most important issues to address in the move towards
graduation

   1. Port Any23 code to ASF infrastructure and update license headers
   2. Develop a strong community with organizational diversity and with
strong connections to other relevant ASF communities.
   3. At least one Any23 incubating release

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

No, not at this time.

How has the community developed since the last report?

Paolo Castagna came onto list and filed some issues ANY23-18, and ANY23-19
suggesting to abstract away the interfaces
in Any23 and make it easier to plug in other RDF technologies, and to
support RDF-A.

Giovanni Tumarello now has his account.

How has the project developed since the last report?

Any23 was voted into the Incubator by the IPMC on October 1, 2011.

All infrastructure has been moved over to Apache. Michele 

October 2011 Incubator Board Report revised (missed removing WAVE, too)

[Noel J. Bergman]

Most of the general discussion on the Incubator list over the past month was
how to improve the usability of the Incubator web-site.

S4 (Simple Scalable Streaming System) -- a general-purpose, distributed,
scalable, partially fault-tolerant, pluggable platform that allows
programmers to easily develop applications for processing continuous,
unbounded streams of data -- was voted to begin Incubation.

Any23 (Anything To Triples) -- a Java library, a Web service and a set of
command line tools to extract and validate structured data in RDF format
from a variety of Web documents and markup formats -- was voted to begin
Incubation.

Apache DirectMemory -- a multi-layered cache implementation featuring
off-heap memory storage (ala Terracotta BigMemory) to enable caching of Java
objects without degrading JVM performance -- was voted to begin Incubation.

Apache Callback (derived from PhonaGap) -- a platform for building native
(Apple iOS, Google Android, RIM BlackBerry, Microsoft Windows Phone 7, HP
webOS, Nokia Symbian and Samsung Bada) mobile applications using HTML, CSS
and JavaScript -- was voted to begin Incubation.

DeltaCloud is currently voting on graduation from the Incubator.  ACE is
also discussing graduation.

With respect ot an early version of the report, there was confusion as to
which podlings needed to report this month, but we appear to have it
straightened out.  The Wiki page had a few too many projects loaded onto it.

--

Accumulo

Accumulo is a sorted, distributed key/value store based on BigTable's
design.  Accumulo entered incubation in September 2011.

In the move towards graduation, we must address:
1. Learning Apache procedures
2. Creating releases
3. Building a community

Any issues that the Incubator PMC or ASF Board might wish/need to be aware
of:
Discussion is ongoing as to whether agreements other than ICLAs are needed
or desirable for people employed by the US government to make contributions
to Apache (see LEGAL-100).

Developments since entering incubation:
* mailing lists created
* JIRA created
* SVN directory and git mirror created
* accounts for initial committers created
* ICLAs and Software Grant filed
* CMS-ready site begun
* initial code uploaded
* Jenkins build created
* ReviewBoard group created


---

ACE

Apache ACE is a software distribution framework that allows you to centrally
manage and distribute software components, configuration data and other
artifacts to target systems. ACE started incubation on April 24th 2009.

There are currently no issues requiring board or Incubator PMC attention.

Community:
 * We've got a lot of great feedback and patches from the community.
 * There have been talks with the jclouds (we use them) as well as the
Amdatu (they use us) open source projects.

Software:
 * We now have a REST client API.
 * The management agent has been extended.
 * Karaf features were added.
 * We have a server side resolver based on Apache Felix.

Licensing and other issues:
 * None at the moment.

Things to resolve prior to graduation:
 * We hope this is our very last board report as we think we're ready for
graduation now!




Ambari

Ambari is monitoring, administration and lifecycle management project for
Apache Hadoop clusters.

 * Incubating since 30 August 2011.
 * Mailing lists created and mentors subscribed.
 * Confluence created.
 * Initial code committed.
 * Site created.
 * Code grant received.
 * Development proceeding actively.
 * RAT added to pom and report is clean.




Any23

Anything To Triples (shortly Any23) defined as a Java library, a Web service
and a set of command line tools to extract and validate structured data in
RDF format from a variety of Web documents and markup formats. Any23 is what
it is informally named an RDF Distiller.

A list of the three most important issues to address in the move towards
graduation

   1. Port Any23 code to ASF infrastructure and update license headers
   2. Develop a strong community with organizational diversity and with
strong connections to other relevant ASF communities.
   3. At least one Any23 incubating release

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

No, not at this time.

How has the community developed since the last report?

Everyone has their ASF account set up, except for Giovanni Tumarello (ICLA
filed and Chris working on getting
account set up). We've already moved our discussions onto the public mailing
lists now that they are set up.

How has the project developed since the last report?

Any23 was voted into the Incubator by the IPMC on October 1, 2011.

Software grants from DERI and from FBK have been filed and accepted thanks
to Michele Mostarda. There has already
been discussion of how to move over JIRA issues and Wiki issues from the
Google Code site and the full issues transition
was completed on 12/10/2011. Code 

RE: October 2011 Incubator Board Report revised (missed removing WAVE, too)

[Noel J. Bergman]

Weird ... that was posted to my output queue on Monday.  :-(  No big deal.
Just a clarification that Wave wasn't missing.

--- Noel



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

Re: October 2011 Incubator Board Report

[Brian LeRoux]

 I removed Wave from the bottom as it reported last month, but Imperius, 
 JSPWiki, and Kitty appear to be missing according to the reporting schedule. 
 Also, it seems Callback isn't scheduled to first report until December - was 
 that a mistake on the schedule page or a deliberate decision by the mentors?

I believe this was deliberate while we sorted out the infrastructure
move which, while still ongoing, I think aiming for a report in
November is very doable. (The practice couldn't hurt.)

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

Re: October 2011 Incubator Board Report

[Dan Peterson]

On Mon, Oct 24, 2011 at 5:37 PM, Brett Porter br...@apache.org wrote:


 On 25/10/2011, at 9:02 AM, Noel J. Bergman wrote:

  With respect ot an early version of the report, there was confusion as to
  which podlings needed to report this month, but we appear to have it
  straightened out.  The Wiki page had a few too many projects loaded onto
 it.

 I removed Wave from the bottom as it reported last month,


Brett, thanks for clearing that up!


 but Imperius, JSPWiki, and Kitty appear to be missing according to the
 reporting schedule. Also, it seems Callback isn't scheduled to first report
 until December - was that a mistake on the schedule page or a deliberate
 decision by the mentors?

 Thanks,
 Brett

 --
 Brett Porter
 br...@apache.org
 http://brettporter.wordpress.com/
 http://au.linkedin.com/in/brettporter





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

Re: October 2011 Incubator Board Report

[Kevan Miller]

On Oct 24, 2011, at 8:37 PM, Brett Porter wrote:

 
 On 25/10/2011, at 9:02 AM, Noel J. Bergman wrote:
 
 With respect ot an early version of the report, there was confusion as to
 which podlings needed to report this month, but we appear to have it
 straightened out.  The Wiki page had a few too many projects loaded onto it.
 
 I removed Wave from the bottom as it reported last month, but Imperius, 
 JSPWiki, and Kitty appear to be missing according to the reporting schedule. 
 Also, it seems Callback isn't scheduled to first report until December - was 
 that a mistake on the schedule page or a deliberate decision by the mentors?

Imperius is retired -- must be some additional cleanup required. I'll track it 
down, but might not be 'till ApacheCon…

There was a bit of confusion for the Kitty project because they got an email 
notice but weren't listed in the template on the Incubator wiki. Someone did 
asked about it on the kitty dev list. However, I got my podlings confused 
(another of my podlings was listed in the template, but wasn't due for a 
report). And I incorrectly assumed Kitty wasn't due to report this month...

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

Re: October 2011 Incubator Board Report

[David Crossley]

Brian LeRoux wrote:
  Brett Porter wrote:
 
  ... Also, it seems Callback isn't scheduled to first report until December 
  - was that a mistake on the schedule page or a deliberate decision by the 
  mentors?
 
 I believe this was deliberate while we sorted out the infrastructure
 move which, while still ongoing, I think aiming for a report in
 November is very doable. (The practice couldn't hurt.)

That was my mistake again. I added it to ReportingSchedule
and again got the dates wrong. I usually add new ones
to report straight away, as i reckon reporting all progress
is good.

If Callback does want to report in November then please
just edit the schedule. Clutch will pick it up later
and add to this month's reminder list.

-David

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

October 2011 Incubator Board Report

[Noel J. Bergman]

Most of the general discussion on the Incubator list over the past month was
how to improve the usability of the Incubator web-site.

S4 (Simple Scalable Streaming System) -- a general-purpose, distributed,
scalable, partially fault-tolerant, pluggable platform that allows
programmers to easily develop applications for processing continuous,
unbounded streams of data -- was voted to begin Incubation.

Any23 (Anything To Triples) -- a Java library, a Web service and a set of
command line tools to extract and validate structured data in RDF format
from a variety of Web documents and markup formats -- was voted to begin
Incubation.

Apache DirectMemory -- a multi-layered cache implementation featuring
off-heap memory storage (ala Terracotta BigMemory) to enable caching of Java
objects without degrading JVM performance -- was voted to begin Incubation.

Apache Callback (derived from PhonaGap) -- a platform for building native
(Apple iOS, Google Android, RIM BlackBerry, Microsoft Windows Phone 7, HP
webOS, Nokia Symbian and Samsung Bada) mobile applications using HTML, CSS
and JavaScript -- was voted to begin Incubation.

DeltaCloud is currently voting on graduation from the Incubator.  ACE is
also discussing graduation.

With respect ot an early version of the report, there was confusion as to
which podlings needed to report this month, but we appear to have it
straightened out.  The Wiki page had a few too many projects loaded onto it.

--

Accumulo

Accumulo is a sorted, distributed key/value store based on BigTable's
design.  Accumulo entered incubation in September 2011.

In the move towards graduation, we must address:
1. Learning Apache procedures
2. Creating releases
3. Building a community

Any issues that the Incubator PMC or ASF Board might wish/need to be aware
of:
Discussion is ongoing as to whether agreements other than ICLAs are needed
or desirable for people employed by the US government to make contributions
to Apache (see LEGAL-100).

Developments since entering incubation:
* mailing lists created
* JIRA created
* SVN directory and git mirror created
* accounts for initial committers created
* ICLAs and Software Grant filed
* CMS-ready site begun
* initial code uploaded
* Jenkins build created
* ReviewBoard group created


---

ACE

Apache ACE is a software distribution framework that allows you to centrally
manage and distribute software components, configuration data and other
artifacts to target systems. ACE started incubation on April 24th 2009.

There are currently no issues requiring board or Incubator PMC attention.

Community:
 * We've got a lot of great feedback and patches from the community.
 * There have been talks with the jclouds (we use them) as well as the
Amdatu (they use us) open source projects.

Software:
 * We now have a REST client API.
 * The management agent has been extended.
 * Karaf features were added.
 * We have a server side resolver based on Apache Felix.

Licensing and other issues:
 * None at the moment.

Things to resolve prior to graduation:
 * We hope this is our very last board report as we think we're ready for
graduation now!




Ambari

Ambari is monitoring, administration and lifecycle management project for
Apache Hadoop clusters.

 * Incubating since 30 August 2011.
 * Mailing lists created and mentors subscribed.
 * Confluence created.
 * Initial code committed.
 * Site created.
 * Code grant received.
 * Development proceeding actively.
 * RAT added to pom and report is clean.




Any23

Anything To Triples (shortly Any23) defined as a Java library, a Web service
and a set of command line tools to extract and validate structured data in
RDF format from a variety of Web documents and markup formats. Any23 is what
it is informally named an RDF Distiller.

A list of the three most important issues to address in the move towards
graduation

   1. Port Any23 code to ASF infrastructure and update license headers
   2. Develop a strong community with organizational diversity and with
strong connections to other relevant ASF communities.
   3. At least one Any23 incubating release

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

No, not at this time.

How has the community developed since the last report?

Everyone has their ASF account set up, except for Giovanni Tumarello (ICLA
filed and Chris working on getting
account set up). We've already moved our discussions onto the public mailing
lists now that they are set up.

How has the project developed since the last report?

Any23 was voted into the Incubator by the IPMC on October 1, 2011.

Software grants from DERI and from FBK have been filed and accepted thanks
to Michele Mostarda. There has already
been discussion of how to move over JIRA issues and Wiki issues from the
Google Code site and the full issues transition
was completed on 12/10/2011. Code 

Re: October 2011 Incubator Board Report

[Brett Porter]

On 25/10/2011, at 9:02 AM, Noel J. Bergman wrote:

 With respect ot an early version of the report, there was confusion as to
 which podlings needed to report this month, but we appear to have it
 straightened out.  The Wiki page had a few too many projects loaded onto it.

I removed Wave from the bottom as it reported last month, but Imperius, 
JSPWiki, and Kitty appear to be missing according to the reporting schedule. 
Also, it seems Callback isn't scheduled to first report until December - was 
that a mistake on the schedule page or a deliberate decision by the mentors?

Thanks,
Brett

--
Brett Porter
br...@apache.org
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter





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

Re: October 2011 Incubator Board Report

[Tommaso Teofili]

Correct,
Hama reported in September, also the 'usual' reminder didn't reach out the
hama-dev@ ML.
Tommaso

2011/10/18 Michael Fitzner fitzner.mich...@googlemail.com

 I think some projects are wrong scheduled for the „October 2011
 Incubator Board Report“ The current schedule plan
 http://wiki.apache.org/incubator/ReportingSchedule shows that projects
 like Etch, Hama, Hcatalog are in the months March, June, September,
 December and not in October. It would be greate if someone could
 correct this in the October report.

 The Etch project had its report in September; see
 http://wiki.apache.org/incubator/September2011 and
 http://incubator.apache.org/clutch.html

 If there was a decision to report in October too, we would like to
 apologise for missing it.

 Thanks
 Michael F. (Apache Etch)

 2011/10/18 Noel J. Bergman n...@devtech.com:
  Most of the general discussion on the Incubator list over the past month
 was
  how to improve the usability of the Incubator web-site.
 
  S4 (Simple Scalable Streaming System) -- a general-purpose, distributed,
  scalable, partially fault-tolerant, pluggable platform that allows
  programmers to easily develop applications for processing continuous,
  unbounded streams of data -- was voted to begin Incubation.
 
  Any23 (Anything To Triples) -- a Java library, a Web service and a set of
  command line tools to extract and validate structured data in RDF format
  from a variety of Web documents and markup formats -- was voted to begin
  Incubation.
 
  Apache DirectMemory -- a multi-layered cache implementation featuring
  off-heap memory storage (ala Terracotta BigMemory) to enable caching of
 Java
  objects without degrading JVM performance -- was voted to begin
 Incubation.
 
  Apache Callback (derived from PhonaGap) -- a platform for building native
  (Apple iOS, Google Android, RIM BlackBerry, Microsoft Windows Phone 7, HP
  webOS, Nokia Symbian and Samsung Bada) mobile applications using HTML,
 CSS
  and JavaScript -- was voted to begin Incubation.
 
  DeltaCloud is currently voting on graduation from the Incubator.  ACE is
  also discussing graduation.
 
  ETCH, HAMA, HCATALOG (managed to do a release, though), KATO, MANIFOLDCF
  (also managed to do a release, though), RAT and WAVE all failed to report
  this month.  The Chair is raising the issue of what to do with these
  projects.
 
  --
 
  Accumulo
 
  Accumulo is a sorted, distributed key/value store based on BigTable's
  design.  Accumulo entered incubation in September 2011.
 
  In the move towards graduation, we must address:
  1. Learning Apache procedures
  2. Creating releases
  3. Building a community
 
  Any issues that the Incubator PMC or ASF Board might wish/need to be
 aware
  of:
  Discussion is ongoing as to whether agreements other than ICLAs are
 needed
  or desirable for people employed by the US government to make
 contributions
  to Apache (see LEGAL-100).
 
  Developments since entering incubation:
  * mailing lists created
  * JIRA created
  * SVN directory and git mirror created
  * accounts for initial committers created
  * ICLAs and Software Grant filed
  * CMS-ready site begun
  * initial code uploaded
  * Jenkins build created
  * ReviewBoard group created
 
 
  ---
 
  ACE
 
  Apache ACE is a software distribution framework that allows you to
 centrally
  manage and distribute software components, configuration data and other
  artifacts to target systems. ACE started incubation on April 24th 2009.
 
  There are currently no issues requiring board or Incubator PMC attention.
 
  Community:
   * We've got a lot of great feedback and patches from the community.
   * There have been talks with the jclouds (we use them) as well as the
  Amdatu (they use us) open source projects.
 
  Software:
   * We now have a REST client API.
   * The management agent has been extended.
   * Karaf features were added.
   * We have a server side resolver based on Apache Felix.
 
  Licensing and other issues:
   * None at the moment.
 
  Things to resolve prior to graduation:
   * We hope this is our very last board report as we think we're ready for
  graduation now!
 
 
  
 
  Ambari
 
  Ambari is monitoring, administration and lifecycle management project for
  Apache Hadoop clusters.
 
   * Incubating since 30 August 2011.
   * Mailing lists created and mentors subscribed.
   * Confluence created.
   * Initial code committed.
   * Site created.
   * Code grant received.
   * Development proceeding actively.
   * RAT added to pom and report is clean.
 
 
  
 
  Any23
 
  Anything To Triples (shortly Any23) defined as a Java library, a Web
 service
  and a set of command line tools to extract and validate structured data
 in
  RDF format from a variety of Web documents and markup formats. Any23 is
 what
  it is informally named an RDF Distiller.
 
  A list of the three most important issues

Re: October 2011 Incubator Board Report

[Stuart Monteith]

Hi,
	The Kato project reported in Secptember, as per our schedule. Our next 
report is due in December, not October.


regards,
Stuart


On 18/10/11 18:05, Noel J. Bergman wrote:

-8
ETCH, HAMA, HCATALOG (managed to do a release, though), KATO, MANIFOLDCF
(also managed to do a release, though), RAT and WAVE all failed to report
this month.  The Chair is raising the issue of what to do with these
projects.
-8


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

Re: October 2011 Incubator Board Report

[Joe Schaefer]

The board@ rescheduled the meeting
at the beginning of this month.  The
second round of nags had the date right;
the first round didn't.

Nov 7 is perhaps the board's face-to-face
meeting in Vancouver.  I would expect the 16th
to be the date for Nov PMC reports to be submitted,
but just an educated guess.





From: Noel J. Bergman n...@devtech.com
To: general@incubator.apache.org; Joe Schaefer joe_schae...@yahoo.com
Sent: Wednesday, October 19, 2011 4:48 PM
Subject: RE: October 2011 Incubator Board Report

 Keep in mind the board meeting isn't until
 next week, so there's still time to address
 the missingreports.

sigh We had the meeting date wrong, too.  When did October move to the
4th week?  And I have no idea when the November meeting will be, since there
are two dates in there (7th and 16th).

    --- Noel

Re: October 2011 Incubator Board Report

[Shane Curcuru]

Joe is correct: 7-Nov is the Board F2F at an offsite location during the 
Monday of ApacheCon.


The normal November meeting, where we'd expect monthly reports, is on 
the 16th as normal.


The October meeting was indeed moved somewhat late, but I was hoping 
no-one else would mind having a couple of extra days.  8-)


- Shane

On 10/19/2011 4:57 PM, Joe Schaefer wrote:

The board@ rescheduled the meeting
at the beginning of this month.  The
second round of nags had the date right;
the first round didn't.

Nov 7 is perhaps the board's face-to-face
meeting in Vancouver.  I would expect the 16th
to be the date for Nov PMC reports to be submitted,
but just an educated guess.






From: Noel J. Bergmann...@devtech.com
To: general@incubator.apache.org; Joe Schaeferjoe_schae...@yahoo.com
Sent: Wednesday, October 19, 2011 4:48 PM
Subject: RE: October 2011 Incubator Board Report


Keep in mind the board meeting isn't until
next week, so there's still time to address
the missingreports.


sigh  We had the meeting date wrong, too.  When did October move to the
4th week?  And I have no idea when the November meeting will be, since there
are two dates in there (7th and 16th).

 --- Noel







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

October 2011 Incubator Board Report

[Noel J. Bergman]

Most of the general discussion on the Incubator list over the past month was
how to improve the usability of the Incubator web-site.

S4 (Simple Scalable Streaming System) -- a general-purpose, distributed,
scalable, partially fault-tolerant, pluggable platform that allows
programmers to easily develop applications for processing continuous,
unbounded streams of data -- was voted to begin Incubation.

Any23 (Anything To Triples) -- a Java library, a Web service and a set of
command line tools to extract and validate structured data in RDF format
from a variety of Web documents and markup formats -- was voted to begin
Incubation.

Apache DirectMemory -- a multi-layered cache implementation featuring
off-heap memory storage (ala Terracotta BigMemory) to enable caching of Java
objects without degrading JVM performance -- was voted to begin Incubation.

Apache Callback (derived from PhonaGap) -- a platform for building native
(Apple iOS, Google Android, RIM BlackBerry, Microsoft Windows Phone 7, HP
webOS, Nokia Symbian and Samsung Bada) mobile applications using HTML, CSS
and JavaScript -- was voted to begin Incubation.

DeltaCloud is currently voting on graduation from the Incubator.  ACE is
also discussing graduation.

ETCH, HAMA, HCATALOG (managed to do a release, though), KATO, MANIFOLDCF
(also managed to do a release, though), RAT and WAVE all failed to report
this month.  The Chair is raising the issue of what to do with these
projects.

--

Accumulo

Accumulo is a sorted, distributed key/value store based on BigTable's
design.  Accumulo entered incubation in September 2011.

In the move towards graduation, we must address:
1. Learning Apache procedures
2. Creating releases
3. Building a community

Any issues that the Incubator PMC or ASF Board might wish/need to be aware
of:
Discussion is ongoing as to whether agreements other than ICLAs are needed
or desirable for people employed by the US government to make contributions
to Apache (see LEGAL-100).

Developments since entering incubation:
* mailing lists created
* JIRA created
* SVN directory and git mirror created
* accounts for initial committers created
* ICLAs and Software Grant filed
* CMS-ready site begun
* initial code uploaded
* Jenkins build created
* ReviewBoard group created


---

ACE

Apache ACE is a software distribution framework that allows you to centrally
manage and distribute software components, configuration data and other
artifacts to target systems. ACE started incubation on April 24th 2009.

There are currently no issues requiring board or Incubator PMC attention.

Community:
 * We've got a lot of great feedback and patches from the community.
 * There have been talks with the jclouds (we use them) as well as the
Amdatu (they use us) open source projects.

Software:
 * We now have a REST client API.
 * The management agent has been extended.
 * Karaf features were added.
 * We have a server side resolver based on Apache Felix.

Licensing and other issues:
 * None at the moment.

Things to resolve prior to graduation:
 * We hope this is our very last board report as we think we're ready for
graduation now!




Ambari

Ambari is monitoring, administration and lifecycle management project for
Apache Hadoop clusters.

 * Incubating since 30 August 2011.
 * Mailing lists created and mentors subscribed.
 * Confluence created.
 * Initial code committed.
 * Site created.
 * Code grant received.
 * Development proceeding actively.
 * RAT added to pom and report is clean.




Any23

Anything To Triples (shortly Any23) defined as a Java library, a Web service
and a set of command line tools to extract and validate structured data in
RDF format from a variety of Web documents and markup formats. Any23 is what
it is informally named an RDF Distiller.

A list of the three most important issues to address in the move towards
graduation

   1. Port Any23 code to ASF infrastructure and update license headers
   2. Develop a strong community with organizational diversity and with
strong connections to other relevant ASF communities.
   3. At least one Any23 incubating release

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

No, not at this time.

How has the community developed since the last report?

Everyone has their ASF account set up, except for Giovanni Tumarello (ICLA
filed and Chris working on getting
account set up). We've already moved our discussions onto the public mailing
lists now that they are set up.

How has the project developed since the last report?

Any23 was voted into the Incubator by the IPMC on October 1, 2011.

Software grants from DERI and from FBK have been filed and accepted thanks
to Michele Mostarda. There has already
been discussion of how to move over JIRA issues and Wiki issues from the
Google Code site and the full issues transition
was completed on 12/10/2011. 

Re: October 2011 Incubator Board Report

[Joe Schaefer]

Keep in mind the board meeting isn't until
next week, so there's still time to address
the missingreports.





From: Noel J. Bergman n...@devtech.com
To: bo...@apache.org
Cc: general@incubator.apache.org
Sent: Tuesday, October 18, 2011 1:05 PM
Subject: October 2011 Incubator Board Report

Most of the general discussion on the Incubator list over the past month was
how to improve the usability of the Incubator web-site.

S4 (Simple Scalable Streaming System) -- a general-purpose, distributed,
scalable, partially fault-tolerant, pluggable platform that allows
programmers to easily develop applications for processing continuous,
unbounded streams of data -- was voted to begin Incubation.

Any23 (Anything To Triples) -- a Java library, a Web service and a set of
command line tools to extract and validate structured data in RDF format
from a variety of Web documents and markup formats -- was voted to begin
Incubation.

Apache DirectMemory -- a multi-layered cache implementation featuring
off-heap memory storage (ala Terracotta BigMemory) to enable caching of Java
objects without degrading JVM performance -- was voted to begin Incubation.

Apache Callback (derived from PhonaGap) -- a platform for building native
(Apple iOS, Google Android, RIM BlackBerry, Microsoft Windows Phone 7, HP
webOS, Nokia Symbian and Samsung Bada) mobile applications using HTML, CSS
and JavaScript -- was voted to begin Incubation.

DeltaCloud is currently voting on graduation from the Incubator.  ACE is
also discussing graduation.

ETCH, HAMA, HCATALOG (managed to do a release, though), KATO, MANIFOLDCF
(also managed to do a release, though), RAT and WAVE all failed to report
this month.  The Chair is raising the issue of what to do with these
projects.

--

Accumulo

Accumulo is a sorted, distributed key/value store based on BigTable's
design.  Accumulo entered incubation in September 2011.

In the move towards graduation, we must address:
1. Learning Apache procedures
2. Creating releases
3. Building a community

Any issues that the Incubator PMC or ASF Board might wish/need to be aware
of:
Discussion is ongoing as to whether agreements other than ICLAs are needed
or desirable for people employed by the US government to make contributions
to Apache (see LEGAL-100).

Developments since entering incubation:
* mailing lists created
* JIRA created
* SVN directory and git mirror created
* accounts for initial committers created
* ICLAs and Software Grant filed
* CMS-ready site begun
* initial code uploaded
* Jenkins build created
* ReviewBoard group created


---

ACE

Apache ACE is a software distribution framework that allows you to centrally
manage and distribute software components, configuration data and other
artifacts to target systems. ACE started incubation on April 24th 2009.

There are currently no issues requiring board or Incubator PMC attention.

Community:
* We've got a lot of great feedback and patches from the community.
* There have been talks with the jclouds (we use them) as well as the
Amdatu (they use us) open source projects.

Software:
* We now have a REST client API.
* The management agent has been extended.
* Karaf features were added.
* We have a server side resolver based on Apache Felix.

Licensing and other issues:
* None at the moment.

Things to resolve prior to graduation:
* We hope this is our very last board report as we think we're ready for
graduation now!




Ambari

Ambari is monitoring, administration and lifecycle management project for
Apache Hadoop clusters.

* Incubating since 30 August 2011.
* Mailing lists created and mentors subscribed.
* Confluence created.
* Initial code committed.
* Site created.
* Code grant received.
* Development proceeding actively.
* RAT added to pom and report is clean.




Any23

Anything To Triples (shortly Any23) defined as a Java library, a Web service
and a set of command line tools to extract and validate structured data in
RDF format from a variety of Web documents and markup formats. Any23 is what
it is informally named an RDF Distiller.

A list of the three most important issues to address in the move towards
graduation

   1. Port Any23 code to ASF infrastructure and update license headers
   2. Develop a strong community with organizational diversity and with
strong connections to other relevant ASF communities.
   3. At least one Any23 incubating release

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

No, not at this time.

How has the community developed since the last report?

Everyone has their ASF account set up, except for Giovanni Tumarello (ICLA
filed and Chris working on getting
account set up). We've already moved our discussions onto the public mailing
lists now that they are set up.

How has the project developed since the last report?

Any23 was voted

Re: October 2011 Incubator Board Report

[Michael Fitzner]

I think some projects are wrong scheduled for the „October 2011
Incubator Board Report“ The current schedule plan
http://wiki.apache.org/incubator/ReportingSchedule shows that projects
like Etch, Hama, Hcatalog are in the months March, June, September,
December and not in October. It would be greate if someone could
correct this in the October report.

The Etch project had its report in September; see
http://wiki.apache.org/incubator/September2011 and
http://incubator.apache.org/clutch.html

If there was a decision to report in October too, we would like to
apologise for missing it.

Thanks
Michael F. (Apache Etch)

2011/10/18 Noel J. Bergman n...@devtech.com:
 Most of the general discussion on the Incubator list over the past month was
 how to improve the usability of the Incubator web-site.

 S4 (Simple Scalable Streaming System) -- a general-purpose, distributed,
 scalable, partially fault-tolerant, pluggable platform that allows
 programmers to easily develop applications for processing continuous,
 unbounded streams of data -- was voted to begin Incubation.

 Any23 (Anything To Triples) -- a Java library, a Web service and a set of
 command line tools to extract and validate structured data in RDF format
 from a variety of Web documents and markup formats -- was voted to begin
 Incubation.

 Apache DirectMemory -- a multi-layered cache implementation featuring
 off-heap memory storage (ala Terracotta BigMemory) to enable caching of Java
 objects without degrading JVM performance -- was voted to begin Incubation.

 Apache Callback (derived from PhonaGap) -- a platform for building native
 (Apple iOS, Google Android, RIM BlackBerry, Microsoft Windows Phone 7, HP
 webOS, Nokia Symbian and Samsung Bada) mobile applications using HTML, CSS
 and JavaScript -- was voted to begin Incubation.

 DeltaCloud is currently voting on graduation from the Incubator.  ACE is
 also discussing graduation.

 ETCH, HAMA, HCATALOG (managed to do a release, though), KATO, MANIFOLDCF
 (also managed to do a release, though), RAT and WAVE all failed to report
 this month.  The Chair is raising the issue of what to do with these
 projects.

 --

 Accumulo

 Accumulo is a sorted, distributed key/value store based on BigTable's
 design.  Accumulo entered incubation in September 2011.

 In the move towards graduation, we must address:
 1. Learning Apache procedures
 2. Creating releases
 3. Building a community

 Any issues that the Incubator PMC or ASF Board might wish/need to be aware
 of:
 Discussion is ongoing as to whether agreements other than ICLAs are needed
 or desirable for people employed by the US government to make contributions
 to Apache (see LEGAL-100).

 Developments since entering incubation:
 * mailing lists created
 * JIRA created
 * SVN directory and git mirror created
 * accounts for initial committers created
 * ICLAs and Software Grant filed
 * CMS-ready site begun
 * initial code uploaded
 * Jenkins build created
 * ReviewBoard group created


 ---

 ACE

 Apache ACE is a software distribution framework that allows you to centrally
 manage and distribute software components, configuration data and other
 artifacts to target systems. ACE started incubation on April 24th 2009.

 There are currently no issues requiring board or Incubator PMC attention.

 Community:
  * We've got a lot of great feedback and patches from the community.
  * There have been talks with the jclouds (we use them) as well as the
 Amdatu (they use us) open source projects.

 Software:
  * We now have a REST client API.
  * The management agent has been extended.
  * Karaf features were added.
  * We have a server side resolver based on Apache Felix.

 Licensing and other issues:
  * None at the moment.

 Things to resolve prior to graduation:
  * We hope this is our very last board report as we think we're ready for
 graduation now!


 

 Ambari

 Ambari is monitoring, administration and lifecycle management project for
 Apache Hadoop clusters.

  * Incubating since 30 August 2011.
  * Mailing lists created and mentors subscribed.
  * Confluence created.
  * Initial code committed.
  * Site created.
  * Code grant received.
  * Development proceeding actively.
  * RAT added to pom and report is clean.


 

 Any23

 Anything To Triples (shortly Any23) defined as a Java library, a Web service
 and a set of command line tools to extract and validate structured data in
 RDF format from a variety of Web documents and markup formats. Any23 is what
 it is informally named an RDF Distiller.

 A list of the three most important issues to address in the move towards
 graduation

   1. Port Any23 code to ASF infrastructure and update license headers
   2. Develop a strong community with organizational diversity and with
 strong connections to other relevant ASF communities.
   3. At least one Any23 incubating release

 Any issues

Re: October 2011 Incubator Board Report

[Karl Wright]

ManifoldCF is also listed as March, June, September, and December on
the referenced page.

Karl

On Tue, Oct 18, 2011 at 1:54 PM, Michael Fitzner
fitzner.mich...@googlemail.com wrote:
 I think some projects are wrong scheduled for the „October 2011
 Incubator Board Report“ The current schedule plan
 http://wiki.apache.org/incubator/ReportingSchedule shows that projects
 like Etch, Hama, Hcatalog are in the months March, June, September,
 December and not in October. It would be greate if someone could
 correct this in the October report.

 The Etch project had its report in September; see
 http://wiki.apache.org/incubator/September2011 and
 http://incubator.apache.org/clutch.html

 If there was a decision to report in October too, we would like to
 apologise for missing it.

 Thanks
 Michael F. (Apache Etch)

 2011/10/18 Noel J. Bergman n...@devtech.com:
 Most of the general discussion on the Incubator list over the past month was
 how to improve the usability of the Incubator web-site.

 S4 (Simple Scalable Streaming System) -- a general-purpose, distributed,
 scalable, partially fault-tolerant, pluggable platform that allows
 programmers to easily develop applications for processing continuous,
 unbounded streams of data -- was voted to begin Incubation.

 Any23 (Anything To Triples) -- a Java library, a Web service and a set of
 command line tools to extract and validate structured data in RDF format
 from a variety of Web documents and markup formats -- was voted to begin
 Incubation.

 Apache DirectMemory -- a multi-layered cache implementation featuring
 off-heap memory storage (ala Terracotta BigMemory) to enable caching of Java
 objects without degrading JVM performance -- was voted to begin Incubation.

 Apache Callback (derived from PhonaGap) -- a platform for building native
 (Apple iOS, Google Android, RIM BlackBerry, Microsoft Windows Phone 7, HP
 webOS, Nokia Symbian and Samsung Bada) mobile applications using HTML, CSS
 and JavaScript -- was voted to begin Incubation.

 DeltaCloud is currently voting on graduation from the Incubator.  ACE is
 also discussing graduation.

 ETCH, HAMA, HCATALOG (managed to do a release, though), KATO, MANIFOLDCF
 (also managed to do a release, though), RAT and WAVE all failed to report
 this month.  The Chair is raising the issue of what to do with these
 projects.

 --

 Accumulo

 Accumulo is a sorted, distributed key/value store based on BigTable's
 design.  Accumulo entered incubation in September 2011.

 In the move towards graduation, we must address:
 1. Learning Apache procedures
 2. Creating releases
 3. Building a community

 Any issues that the Incubator PMC or ASF Board might wish/need to be aware
 of:
 Discussion is ongoing as to whether agreements other than ICLAs are needed
 or desirable for people employed by the US government to make contributions
 to Apache (see LEGAL-100).

 Developments since entering incubation:
 * mailing lists created
 * JIRA created
 * SVN directory and git mirror created
 * accounts for initial committers created
 * ICLAs and Software Grant filed
 * CMS-ready site begun
 * initial code uploaded
 * Jenkins build created
 * ReviewBoard group created


 ---

 ACE

 Apache ACE is a software distribution framework that allows you to centrally
 manage and distribute software components, configuration data and other
 artifacts to target systems. ACE started incubation on April 24th 2009.

 There are currently no issues requiring board or Incubator PMC attention.

 Community:
  * We've got a lot of great feedback and patches from the community.
  * There have been talks with the jclouds (we use them) as well as the
 Amdatu (they use us) open source projects.

 Software:
  * We now have a REST client API.
  * The management agent has been extended.
  * Karaf features were added.
  * We have a server side resolver based on Apache Felix.

 Licensing and other issues:
  * None at the moment.

 Things to resolve prior to graduation:
  * We hope this is our very last board report as we think we're ready for
 graduation now!


 

 Ambari

 Ambari is monitoring, administration and lifecycle management project for
 Apache Hadoop clusters.

  * Incubating since 30 August 2011.
  * Mailing lists created and mentors subscribed.
  * Confluence created.
  * Initial code committed.
  * Site created.
  * Code grant received.
  * Development proceeding actively.
  * RAT added to pom and report is clean.


 

 Any23

 Anything To Triples (shortly Any23) defined as a Java library, a Web service
 and a set of command line tools to extract and validate structured data in
 RDF format from a variety of Web documents and markup formats. Any23 is what
 it is informally named an RDF Distiller.

 A list of the three most important issues to address in the move towards
 graduation

   1. Port Any23 code to ASF infrastructure and update license

Incubator Board Report August 2011

[Noel J. Bergman]

Bluesky was retired by vote of the Incubator PMC.  The project just never
managed to adjust to the ASF's community-orientation.

Olio likewise seems prime for retirement.

HISE (Human Tasks for WS-BPEL) again failed to report (that was an issue in
February as well).  Activity has picked up aomewhat being mostly dead, but
the Incubator will inquire into the viability of the project.

Oozie failed to report, but is just getting started.  There are no archives
for the -dev list.

ODF Toolkit, a set of Java modules that allow programmatic creation,
scanning and manipulation of OpenDocument Format documents, was voted to
begin Incubation, and has filed its first report.

Giraph, a large-scale, fault-tolerant, Bulk Synchronous Parallel (BSP)-based
graph processing framework that runs on Hadoop, was voted to begin
Incubation.

The Incubator PMC voted to submit Whirr for TLP status to the Board.

Richard Provarp joined the Incubator PMC.


--

Airavata

Airavata is a software toolkit which provides features to compose, manage,
execute, and monitor large scale applications and workflows on computational
resources ranging from local clusters to national grids and computing
clouds. Airavata is incubating since May 2011.

A list of the three most important issues to address in the move towards
graduation

   1. Update web service implementations from XSUL to Axis2. Update security
libraries and simplify the build process and provide sample use cases.
   2. Package, document and release at least one Apache Incubator release.
   3. Develop a strong community with organizational diversity and well
aligned with existing ASF projects as outlined here:
http://wiki.apache.org/incubator/AiravataProposal#Alignment

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

No, not at this time.

How has the community developed since the last report?

Web designer Barbara Hallock was voted in a commiter and PPMC member for her
contributions to the website design, logo and CSS contributions. The website
is now live with her contributions. Lahiru Gunathilake an existing apache
commiter from Axis2  QPID projects has made significant contributions and
provided 25+ patches to Airavata. He is voted in as a commiter and PPMC
member. A new volunteer Patanachai Tangchaisin has been contributing to the
various components of the project.

How has the project developed since the last report?

* Significant progress has been made towards a release. All components are
organized within the svn adding project level and module level maven build
profiles.
* Website is updated with documentation for build and eclipse development
instructions.
* The default database in WS-Messenger and XRegistry is changed from mysql
to Apache Derby. Derby is integrated as an embedded database to build and
deploy as a maven profile. This porting has removed the incompatible license
dependency on mysql-connector jar.
* WS-Messenger module is re-factored, packaged and tested. The messaging
system clients are being worked on, this component needs to integrated with
rest of the modules.
* XBaya module is cleaned up of unused legacy code, improved dependency
management and simple test cases are tested through.




Amber

Amber has been incubating since July 2010. Amber is a project to develop a
Java library which provides an API specification for, and an unconditionally
compliant implementation of the OAuth v1.0, v1.0a and v2.0 specifications.
OAuth is a mechanism that allows users to authenticate and authorise access
by another party to resources they control while avoiding the need to share
their username and password credentials.

The most important issues that must be addressed before graduation are:

 - Clarify status of code grant
 - Attract users and developers
 - Generate a release

The Incubator PMC / ASF Board should be aware that:

 - Community activity is relatively low

How has the community developed since the last report

 - Some users have started asking for help or getting started guides on the
mailing list

How has the project developed since the last report

 - Work has begun on updating the OAuth implementation
 - Discussion about preparing for an initial release is ongoing




Bigtop

Bigtop is a project for the development of packaging and tests of the Hadoop
ecosystem.

Bigtop entered incubation on June 20 2011

A list of the three most important issues to address in the move towards
graduation:
* Create Bigtop web site. Item in progress. See ticket BIGTOP-9
* Make an incubating release.
* Grow the community size and diversity.

Any issues that the Incubator PMC or ASF Board might wish/need to be aware
of:
* No issues

How has the community developed since the last report:
* Discussions have been started about how to organize the development (RTC
vs CTR)

How has the project developed since the last report.
* 

June 2011 Incubator Board Report

[Noel J. Bergman]

The Incubator PMC now totals 143 members, with some additional requests
(joining and a resignation) pending.  Recent changes include Peter Royal and
Phil Steitz (pending) dropping off; and Shane Curcuru, Srinath Perera,
Nicolas Lalevee, Marvin Humphrey, Michael McCandless, Nigel Daley, Tommaso
Teofili, Yegor Kozlov, Leif Hedstrom and Steve Loughran joining the PMC.

Certainly the biggest thing in the Incubator this month is the arrival of
OpenOffice.org for Incubation.  OpenOffice.org is going to need significant
help and guidance, with an emphasis on liasoning with other, external,
projects such as LibreOffice.  There is very significant concern regarding
how this project will relate to the rest of the Openoffice.org ecosystem,
and those will need to be carefully addressed.  One of the first challenges
for the project will be deciding its scope.  If it is going to try to be the
old OpenOffice.org, essentially an Apache Licensed coopetitor to the
downstream forks; or if it is going to focus on common technologies, release
vanilla binaries for key platforms, and let the downstreams take the primary
role in delivering end-user binaries.  Other issues with respect to
OpenOffice.org may challenge our infrastructure.  There may also be IP
(patent and trademark) issues to address.  But the lengthy and diverse list
of Mentors should be aware of and preparing to address all of the issues.

Despite OpenOffice.org's arrival, and its well than 1000 messages swamping
the mailing list, there was more activity than just that one topic.

BigTop, a project for the development of packaging and tests of the Hadoop
ecosystem, is proposed for Incubation.

Flume -- a distributed, reliable, and available system for efficiently
collecting,
aggregating, and moving large amounts of log data to scalable data storage
systems such as Apache Hadoop's HDFS -- was voted to enter Incubation.

Sqoop -- a tool designed for efficiently transferring bulk data between
Apache Hadoop and structured datastores such as relational databases -- was
voted to enter Incubation.

There is nascent discussion regarding moving Alois and BlueSky to dormant
status.



Airavata

Airavata is a software toolkit currently used to build science gateways but
that has a much wider potential use. It provides features to compose,
manage, execute, and monitor large scale applications and workflows on
computational resources ranging from local clusters to national grids and
computing clouds.

A list of the three most important issues to address in the move towards
graduation

   1. Finish the security paper work needed to import donated code with
cryptographic dependencies.
   2. Engage the community by document existing design, drafting detailed
JIRA tasks defining smaller goals.
   3. Remove incompatible license dependencies and implement over ALV2
compatible libraries.
   4. Simplify the build process and provide simple to use cases.
   5. At least one Apache Incubator release.
   6. Develop a strong community with organizational diversity and well
aligned with existing ASF projects as outlined here:
http://wiki.apache.org/incubator/AiravataProposal#Alignment

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

No, not at this time.

How has the community developed since the last report?

The interactions to date have been focused on development, and getting the
project started.

How has the project developed since the last report?

Airavata was voted into the Incubator by the IPMC on May 7, 2011.

Suresh Marru is pushing forward on the Airavata website. There is also work
going on related to this to define a new Apache Airavata logo. In addition,
Suresh led a development roadmap discussion.




ALOIS

The ALOIS project team wrote an private e-mail to it's mentors shortly after
the last report. They have told us that due to personal reasons they cannot
keep this project alive and there will be no project activity in near
future. We have agreed to wait until the June 2011 comes up. So far there is
no change in project activity or interest, no e-mails and even no more
private messages. After this report the Incubator-PMC needs to discuss about
moving this podling to attic. (Christian Grobmeier)

In addition to Christian's report, I'd like to mention that we didn't find
any interest in the project outside of our small group, although we did
quite a lot requests off list. If there would be someone to take over the
project, we would be happy to give a helping hand at the start. (Urs Lerch)




BeanValidation

Apache Bean Validation will deliver an implementation of the JSR303 Bean
Validation 1.0 specification. BVAL entered incubation on March 1, 2010.

A list of the three most important issues to address in the move towards
graduation.
 * Perform successful Releases - Done
 * Grow the community and committer base - stale at a medium level
 * Decide on graduation target of TLP or 

Incubator Board Report May 2011

[Noel J. Bergman]

Incubator Report May 2011

The Incubator continues to accept and graduate projects a pace.  This month
we have two new projects, one retirement (with two more likely), and one
graduation.

Imperius has voted to retire.  Others are likely to follow (see below).

LibCloud is proposed for graduation to TLP status, and presenting to the
Board as such.

OGNL, a Java development framework for Object-Graph Navigation Language, was
accepted for Incubation.

Airavata, a project that provides features to compose, manage, execute, and
monitor large scale applications and workflows on computational resources
ranging from local clusters to national grids and computing clouds, has been
accepted for Incubation.

Bluesky did not report, but did report last month and may not realize it is
still on a monthly reporting schedule.  DeltaCloud did not report, and is
active so they should have reported.  HISE and Stonehenge did not report,
and both look ripe for retirement.  The latter community is actively
discussing that this month, but simply failed to report that discussion, and
the former appears mostly dead already.

---
Incubator Project reports
---

Amber

Amber has been incubating since July 2010. Amber is a project to develop a
Java library which provides an API specification for, and an unconditionally
compliant implementation of the OAuth v1.0, v1.0a and v2.0 specifications.
OAuth is a mechanism that allows users to authenticate and authorise access
by another party to resources they control while avoiding the need to share
their username and password credentials.

The most important issues that must be addressed before graduation are:

 - Attract users and developers
 - Generate a release

The Incubator PMC / ASF Board should be aware that:

 - Community activity is relatively low

How has the community developed since the last report

 - Some users have started asking for help or getting started guides on the
mailing list

How has the project developed since the last report

 - Fixed some bugs
 - Removed LGPL licensed files from website




Bluesky

Did not report (currently on monthly schedule), but did report in April.




Clerezza

(incubating since November 27th, 2009) is an OSGi-based modular application
and set of components (bundles) for building RESTFul Semantic Web
applications and services.

There are currently no issues requiring board attention.

Recent activity:

 - Added WebId test suite
 - Added Clerezza-UIMA CAS Consumer
 - Released a new website version with much more documentation

Next steps:

 - First release
 - Improve documentation and tutorial to website


Top 2/3 Issues before graduation:

 - Prepare some easy-to-run demos to get people interested in Clerezza




Deltacloud

Did not report.  Is active, and simply failed to report.




Droids

Droids is an Incubator project arrived from Apache Labs. Droids entered
incubation on October, 2008.

It's an intelligent standalone robot framework that allows one to create and
extend existing web robots.

The last three months have been very productive for the project since
mailing and issue tracking activity have been very good. Our two new
committer have driven our first release which is planed for this month. More
people appeared on the mailing list and especially one dev is driving
constantly enhancement in our issue tracker.

Issues before graduation :

 * IP clearance




HCatalog

HCatalog is a table and storage management service for data created
using Apache Hadoop.

The most important issues in moving the project to graduation are
expanding the community of developers and producing a release of the
software.

Since the last report we have:

 * got the initial code drop checked in
 * got the build working for building, testing, and the documents
 * branched in preparation for a 0.1 release
 * started development on new features for 0.2

Currently there are 29 subscribers to the user list and 27 on the dev
list.  There were 14 and 15 respectively last month.




HISE

Did not report.  Appears largely inactive, and perhaps should be retired.




Jena

Jena was accepted into the Apache Incubator November 2010. It is an existing
project migrating to ASF. It has a large codebase that provides a semantic
web framework in Java that implements the key W3C recommendations for the
core semantic web technologies of
RDF and SPARQL.

Three most important issues to address for graduation:

* Create a code base in Apache with legal clearance.
* Establish the Apache-based community for developers, contributors and
users
* Create and communicate open project processes aligned to Apache

Issues for the Incubator PMC or ASF Board:

None.

Community development:

We have started to 

Incubator Board Report April 2011

[Noel J. Bergman]

A remarkably quiet month in general, with no Board level issues.  One
project, Apache OGNL (http://wiki.apache.org/incubator/OGNLProposal) is
under consideration.

JSPWiki, Olio and VXQuery did not report.  Neither did SocialSite, but that
was previously voted into dormant status.

---

April 2011 podling reports



Apache ACE is a software distribution framework that allows you to centrally
manage and distribute software components, configuration data and other
artifacts to target systems. ACE started incubation on April 24th 2009.

There are currently no issues requiring board or Incubator PMC attention.

Community:

Angelo gave a talk about massive device deployment and Karl and Marcel did a
tutorial about ACE in the Cloud at EclipseCon / OSGi DevCon.
We're gathering EclipseCon / OSGi DevCon feedback to populate the roadmap
and raise the corresponding Jira issues.

Software:

A lot of work has been done on the build to fully support Maven 3.
We started to work on the documentation also.
Use of Apache Karaf as default runtime is in progress.
Cloud extensions based on jclouds have been added, including a new launcher.

Licensing and other issues:

None at the moment.

Things to resolve prior to graduation:

We created a SVN maven repo waiting for some Felix dependencies release.
Make a release.
Grow the community some more.




BlueSky

BlueSky has been incubating since 01-12-2008. It is an e-learning solution
designed to help solve the disparity in availability of qualified education
between well-developed cities and poorer regions of China.

The following items have been performed since the last reporting period:
* test the stability of system on a certain scale.
* add the fuanction of recording vedio in the teacher part.

The following items are planned for the next reporting period:
* go on testing the stability of system




Celix

Celix is an implementation of the OSGi Specification in C.

Celix entered incubation on November 2, 2010.

During the EclipseCon a talk was given over Celix, also spoke with several
OSGi people who are interested in the progress, especially related to
Universal OSGi (which details specification and requirements for OSGi in
other languages).
During the last few weeks work has been done to get rid of memory leaks and
null pointers.
Currently we are looking at the requirements/details for bundle deployment
and updating, possibly in combination with Apache Ace.

Most important issues are:

- Define a status overview of what is and isn't working.
- Move all sub project to the new structure.
- Use APR for all file handling, threading etc.
- Generate awareness and grow a community




Chukwa

Chukwa is a distributed log collection and processing system built on top of
Hadoop and HBase.  Chukwa is waiting for a official working release of
Hadoop 0.2x and HBase 0.9x.  There are certain API incompatibility in
metrics collection system to prevent them working together.  This is a
blocker for Chukwa 0.5 release.

Chukwa entered incubation on August 5th, 2010.




EasyAnt

EasyAnt is a tool built on top of Ant and Ivy providing a standard approach
to building java projects without locking the users in.

Incubating since January 31st 2011

issues/agenda:
- 1 ICLA missing. The person does not answer since Feb 4th 2011, when he
indicated he was working on getting the ICLA. The svn logs have been
gathered and shared between the PPMC members in preparation for a possible
cleanup of the svn tree of that person's contribution.

activity since last report:
- the web site http://incubator.apache.org/easyant/ is published via
svnpubsub
- while reviewing the licences of the software included in the svn tree of
Easyant, some dependency on external LGPL library was found. There are
somehow optional to EasyAnt core, but not for the plugin dedicated to the
integration of that third library. A consensus was found by the developer
community to not release such software under the ASF.




Empire-db

Apache Empire-db is a relational database abstraction layer that allows
developers to take a more SQL-centric approach in application development
than traditional ORM frameworks. Its focus is to allow highly efficient
database operations in combination with a maximum of compile-time-safety and
DBMS independence. Empire-db has entered Incubation in August 2008.

Activity since last report:
- We have successfully completed and published our 2.1.0 release with few
but major improvements.
- We have increased your community by taking on a new long-time contributor
as a new committer.

Important issues to address for graduation:
We still need more contributors and more attention in the Java community.
Recently we experience increased traffic on the user lists and there are
plenty of plans on the development side. The challenge will be 

Incubator Board Report - March 2011 [REVISED WITH GORA]

[Noel J. Bergman]

[REVISED TO INCLUDE GORA.  I saw that it was already picked up from the
mailing list, but wanted to get it into the archives in one place.  Thanks
to Chris for posting, and Doug for including.]

Nigel Daly, Tommaso Teofili, and Alan Gates have joined the PMC since the
last report.

Howl -- a table and storage management service for data created using Apache
Hadoop -- has been accepted for Incubation.  It will be renamed first, given
that there is an ObjectWeb project also called HOWL.

MRUnit -- a library to support unit testing of Hadoop MapReduce jobs -- has
been accepted for Incubation.

Rave -- a web And social Mashup Engine -- has been accepted for Incubation.

BeanValidation and Gora failed to report this period.



ALOIS

ALOIS stands for Advanced Log Data Insight System and is meant to be a
fully implemented open source SIEM security information and event management
system.

ALOIS is incubating since 22nd October 2010.

The following items have been performed since the last reporting period:
 * Launch of the project website
 * Code review
 * Lightning Talk at the CCC Conference in Berlin
 * Promoting the project on different plaforms
 * Preparing several talks and booths (Chemnitz, Berlin, CeBIT, ...)

Three most important issues to address in the move towards graduation:
 * Releasing Version 1
 * Enlarge the developer base
 * Creating more use cases

How has the community developed since the last report:
 * Despite the activities no real community so far

How has the project developed since the last report:
 * The code is stable and accessable
 * The website is online and managed



BeanValidation

Failed to report.  There is some degree of activity on its mailing lists,
and addition of new Committers.




Bluesky

BlueSky has been incubating since 01-12-2008. It is an e-learning solution
designed to help solve the disparity in availability of qualified education
between well-developed cities and poorer regions of China.

The following items have been performed since the last reporting period:
 * Now improving the statbility of system
 * Resolving the problems of having no Screen images
 * Resolving unstability of the 2nd focus student's data transportation.

The following items are planned for the next reporting period:
 * Improving the stability of the system
 * add the fuanction of recording vedio in the teacher part.




EasyAnt

EasyAnt is a tool built on top of Ant and Ivy providing a standard approach
to building java projects without locking the users in.

Incubating since January 31st 2011

issues/agenda
- 1 ICLA missing. The person does not answer since Feb 4th 2011, when he
indicated he was working on getting the ICLA.

- the code base has been migrated in SVN

- the issues are in JIRA with component EASYANT




Etch

Etch was accepted into Incubator on 2 September 2008.

Etch is a cross-platform, language- and transport-independent framework for
building and consuming network services. The Etch toolset includes a network
service description language, a compiler, and binding libraries for a
variety of programming languages.

For the last 3 months the main effort has been by Holger Grandy and Michael
Fitzner, who contributed some bug fixes and have been converting
documentation.

The transition of current Etch Website to the new Apache CMS is in progress.
Major parts of the sides are already available inside the CMS repository and
can be seen at the staging area.

The Spawn Labs team (Comer, Dixson) is working to integrate the c-binding
into their product. They've been very quiet lately. We miss them. Comer
wrote up something about his service cloud and is waiting for permission to
publish it.

Although progress is now visible, we still need to get more user and
development activity on our lists.

Top issues currently are:
- plan features and dates for release 1.2 / 1.1.1
- work on further language bindings
- website transition to Apache CMS
- documentation

Note by Martijn Dashorst: I met with Holger Grandy and Michael Fitzner at
FOSDEM'11 and we spoke about lots of stuff concerning Etch. I think the
future for the podling is bright, but we need to get more people involved by
publishing articles. The biggest problem is finding the right venues for
publishing the articles. I'll bring Etch under the attention of PR to see if
they have any good ideas.




Gora

Gora is an ORM framework for column stores such as Apache HBase and Apache
Cassandra with a specific focus on Hadoop.

A list of the three most important issues to address in the move towards
graduation

   1. Port Gora code and license headers into ASF license headers
   2. Develop a strong community with organizational diversity and with
infection into existing ASF projects like Nutch and Hadoop
   3. At least one Gora incubating release

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

Incubator Board Report - March 2011

[Noel J. Bergman]

Nigel Daly, Tommaso Teofili, and Alan Gates have joined the PMC since the
last report.

Howl -- a table and storage management service for data created using Apache
Hadoop -- has been accepted for Incubation.  It will be renamed first, given
that there is an ObjectWeb project also called HOWL.

MRUnit -- a library to support unit testing of Hadoop MapReduce jobs -- has
been accepted for Incubation.

Rave -- a web And social Mashup Engine -- has been accepted for Incubation.

BeanValidation and Gora failed to report this period.



ALOIS

ALOIS stands for Advanced Log Data Insight System and is meant to be a
fully implemented open source SIEM security information and event management
system.

ALOIS is incubating since 22nd October 2010.

The following items have been performed since the last reporting period:
 * Launch of the project website
 * Code review
 * Lightning Talk at the CCC Conference in Berlin
 * Promoting the project on different plaforms
 * Preparing several talks and booths (Chemnitz, Berlin, CeBIT, ...)

Three most important issues to address in the move towards graduation:
 * Releasing Version 1
 * Enlarge the developer base
 * Creating more use cases

How has the community developed since the last report:
 * Despite the activities no real community so far

How has the project developed since the last report:
 * The code is stable and accessable
 * The website is online and managed



BeanValidation

Failed to report.  There is some degree of activity on its mailing lists,
and addition of new Committers.




Bluesky

BlueSky has been incubating since 01-12-2008. It is an e-learning solution
designed to help solve the disparity in availability of qualified education
between well-developed cities and poorer regions of China.

The following items have been performed since the last reporting period:
 * Now improving the statbility of system
 * Resolving the problems of having no Screen images
 * Resolving unstability of the 2nd focus student's data transportation.

The following items are planned for the next reporting period:
 * Improving the stability of the system
 * add the fuanction of recording vedio in the teacher part.




EasyAnt

EasyAnt is a tool built on top of Ant and Ivy providing a standard approach
to building java projects without locking the users in.

Incubating since January 31st 2011

issues/agenda
- 1 ICLA missing. The person does not answer since Feb 4th 2011, when he
indicated he was working on getting the ICLA.

- the code base has been migrated in SVN

- the issues are in JIRA with component EASYANT




Etch

Etch was accepted into Incubator on 2 September 2008.

Etch is a cross-platform, language- and transport-independent framework for
building and consuming network services. The Etch toolset includes a network
service description language, a compiler, and binding libraries for a
variety of programming languages.

For the last 3 months the main effort has been by Holger Grandy and Michael
Fitzner, who contributed some bug fixes and have been converting
documentation.

The transition of current Etch Website to the new Apache CMS is in progress.
Major parts of the sides are already available inside the CMS repository and
can be seen at the staging area.

The Spawn Labs team (Comer, Dixson) is working to integrate the c-binding
into their product. They've been very quiet lately. We miss them. Comer
wrote up something about his service cloud and is waiting for permission to
publish it.

Although progress is now visible, we still need to get more user and
development activity on our lists.

Top issues currently are:
- plan features and dates for release 1.2 / 1.1.1
- work on further language bindings
- website transition to Apache CMS
- documentation

Note by Martijn Dashorst: I met with Holger Grandy and Michael Fitzner at
FOSDEM'11 and we spoke about lots of stuff concerning Etch. I think the
future for the podling is bright, but we need to get more people involved by
publishing articles. The biggest problem is finding the right venues for
publishing the articles. I'll bring Etch under the attention of PR to see if
they have any good ideas.




Gora

Gora is Gora is an ORM framework for column stores such as Apache HBase and
Apache Cassandra with a specific focus on Hadoop.

Did not report.  Has voted in new Committers.  Appears quite active.



Hama

Hama was accepted into Incubator on 20 May 2008. Hama is a distributed
computing framework based on BSP (Bulk Synchronous Parallel) computing
techniques for massive scientific computations.

== Top 2 or 3 things to resolve prior to graduation ==

 * Complete first release
 * Invite new active committers

== Issues for the Incubator PMC or ASF Board ==

None.

== Community development ==

 * Mailing list shows increased usage from previous report
 * Chia-Hung Lin has contributed a part