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  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  >
> 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  >
> > 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
> > > >   

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 
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 
> 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  >
> > 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
> > 

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 
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 
> 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
> > 

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  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 
> 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 

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 
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 

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: Wiki Access - Podling Mentor

[John D. Ament]

To clarify...

It seems that a step was missed to confirm that all mentors for Freemarker
were on the IPMC.  Jacopo wasn't actually an IPMC when the project started,
but joined us when it did.  David, we need all mentors to be on the IPMC
for a podling.  You're a member, so you're free to join the IPMC whenever.
Please just send a request to private.

John

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

> On Mon, Apr 11, 2016 at 6:45 PM, David E. Jones  wrote:
>
> > Thanks John, worked just fine.
>
> David, can you please request to join the IPMC on private@incubator?
>
> Marvin Humphrey
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

[VOTE] TinkerPop 3.2.0-incubating Release

[Stephen Mallette]

Hello,

We are happy to announce that TinkerPop 3.2.0-incubating ready for release.

NOTE that this is a tandem release in that 3.1.2-incubating is also
available and up for VOTE separately on a different thread.

The release artifacts can be found at this location:
https://dist.apache.org/repos/dist/dev/incubator/tinkerpop/3.2.0-incubating/

The source distribution is provided by:
apache-tinkerpop-3.2.0-incubating-src.zip

Two binary distributions are provided for user convenience:
apache-gremlin-console-3.2.0-incubating-bin.zip
apache-gremlin-server-3.2.0-incubating-bin.zip

The GPG key used to sign the release artifacts is available at:
https://dist.apache.org/repos/dist/dev/incubator/tinkerpop/KEYS

The online docs can be found here:
http://tinkerpop.apache.org/docs/3.2.0-incubating/reference/ (user docs)
http://tinkerpop.apache.org/docs/3.2.0-incubating/upgrade/ (upgrade docs)
http://tinkerpop.apache.org/javadocs/3.2.0-incubating/core/ (core javadoc)
http://tinkerpop.apache.org/javadocs/3.2.0-incubating/full/ (full javadoc)

The tag in Apache Git can be found here:

https://git-wip-us.apache.org/repos/asf?p=incubator-tinkerpop.git;a=tag;h=eaa4a3735af6caf2ec22bf069aa52c58fc8ebe80

The release notes are available here:
https://github.com/apache/incubator-tinkerpop/blob/3.2.0-incubating/CHANGELOG.asciidoc#tinkerpop-320-release-date-april-8-2016

Finally, the dev@tinkerpop [VOTE] thread can be found at this location:

https://pony-poc.apache.org/thread.html/Z37px8p8po7ekry
https://pony-poc.apache.org/thread.html/Z-manw7pq82nlrf

Result summary: +8 (4 binding, 4 non-binding), 0 (0), -1 (0)

The [VOTE] will be open for at least the next 72 hours.

Thank you very much,
Stephen

[VOTE] TinkerPop 3.1.2-incubating Release

[Stephen Mallette]

Hello,

We are happy to announce that TinkerPop 3.1.2-incubating ready for release.

NOTE that this is a tandem release in that 3.2.0-incubating is also
available and up for VOTE separately on a different thread.

The release artifacts can be found at this location:
https://dist.apache.org/repos/dist/dev/incubator/tinkerpop/3.1.2-incubating/

The source distribution is provided by:
apache-tinkerpop-3.1.2-incubating-src.zip

Two binary distributions are provided for user convenience:
apache-gremlin-console-3.1.2-incubating-bin.zip
apache-gremlin-server-3.1.2-incubating-bin.zip

The GPG key used to sign the release artifacts is available at:
https://dist.apache.org/repos/dist/dev/incubator/tinkerpop/KEYS

The online docs can be found here:
http://tinkerpop.apache.org/docs/3.1.2-incubating/reference/ (user docs)
http://tinkerpop.apache.org/docs/3.1.2-incubating/upgrade/ (upgrade docs)
http://tinkerpop.apache.org/javadocs/3.1.2-incubating/core/ (core javadoc)
http://tinkerpop.apache.org/javadocs/3.1.2-incubating/full/ (full javadoc)

The tag in Apache Git can be found here:
https://git-wip-us.apache.org/repos/asf?p=incubator-tinkerpop.git;a=tag;h=031dfe308b8a318581288c720a8bfc0aa254d7ce

The release notes are available here:
https://github.com/apache/incubator-tinkerpop/blob/3.1.2-incubating/CHANGELOG.asciidoc#tinkerpop-312-release-date-april-8-2016

Finally, the dev@tinkerpop [VOTE] thread can be found at this location:

https://pony-poc.apache.org/thread.html/Z21yvtt9hebv15s
https://pony-poc.apache.org/thread.html/Zdt01jof9azg0yy

Result summary: +6 (4 binding, 2 non-binding), 0 (0), -1 (0)

The [VOTE] will be open for at least the next 72 hours.

Thank you very much,
Stephen

[NOTICE] new committer for Apache Johnzon podling: Reinhard Sandtner

[Hendrik Dev]

FYI

-- Forwarded message --
From: Hendrik Dev 
Date: Tue, Apr 12, 2016 at 1:47 PM
Subject: new committer: Reinhard Sandtner
To: "d...@johnzon.incubator.apache.org" 


The Podling Project Management Committee (PPMC) for Apache Johnzon
(incubating) has asked Reinhard Sandtner to become a committer and we
are pleased
to announce that they have accepted.

Welcome Reinhard, great to have you on board.

Being a committer enables easier contribution to the
project since there is no need to go via the patch
submission process. This should enable better productivity.

On behalf of the Apache Johnzon PPMC
Hendrik Saly

-- 
Hendrik Saly (salyh, hendrikdev22)
@hendrikdev22
PGP: 0x22D7F6EC

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

RE: [VOTE] [FINERACT] 0.1.0.incubating for release

[Adi Raju]

Adding general@incubator.apache.org into mailing list

-Original Message-
From: Adi Raju [mailto:adi.r...@confluxtechnologies.com] 
Sent: 12 April 2016 10:35
To: d...@fineract.incubator.apache.org
Subject: RE: [VOTE] [FINERACT] 0.1.0.incubating for release

Release files correspond to the following fineract source branch
https://github.com/apache/incubator-fineract/tree/0.1.0-incubating

Regards,
Adi


-Original Message-
From: Markus Geiß [mailto:markus.ge...@live.de]
Sent: 12 April 2016 10:08
To: d...@fineract.incubator.apache.org
Subject: RE: [VOTE] [FINERACT] 0.1.0.incubating for release

+1

Maybe we can add a link to the GitHub tag, so it is easier to validate the
content.

> Date: Mon, 11 Apr 2016 16:15:16 +0530
> Subject: [VOTE] [FINERACT] 0.1.0.incubating for release
> From: raj...@apache.org
> To: d...@fineract.incubator.apache.org
> 
> Hello All,
> 
> I have prepared the files for first release of FINERACT.
> The files are hosted at
> https://dist.apache.org/repos/dist/dev/incubator/fineract/
> This is a source only release with no binaries, with instructions on 
> how to build/test the application.
> 
> Being the first release, I request the mentors to review the content, 
> especially of LICENSE, NOTICE, DISCLAIMER files.
> 
> We have multi-tenancy architecture. Main DB contains list of tenants 
> and their corresponding DB names and access details.
> These tenant specific DB can even have variations in schema. Access to 
> these tenant databases are created at runtime.
> Enhancement of entity objects corresponding to tenant databases fails 
> with OpenJPA. This is because access to DB metadata of tenant 
> databases is not available at boot time.
> We couldn't migrate to OpenJPA and avoid dependency on
Hibernate(LGPLv2.1).
> Since we are making source only distribution, can we get waiver on 
> this dependency?
> 
> With this background, I call for formal VOTING for the first release.
> 
> Regards,
> Adi Raju
  



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

[VOTE] Release apache-singa-incubating-0.3.0 (RC1)

[Wang Wei]

Hi all,

The SINGA community has voted on and approved a proposal to release Apache
SINGA 0.3.0 (incubating).

The vote thread is at:
http://mail-archives.apache.org/mod_mbox/singa-dev/201604.mbox/%3CCAJz0iLsVNaLN_TmuBPJ93n21tWSj=s6fmpbffsNt8Aumm=n...@mail.gmail.com%3E

and the result is at:
http://mail-archives.apache.org/mod_mbox/singa-dev/201604.mbox/%3CCAJz0iLt=ALvT012V5fgxiGX=5cxewphavv3dh5o27ydvbks...@mail.gmail.com%3E

We ask the IPMC to vote on this release.

The artifacts to be voted on are located here:
https://dist.apache.org/repos/dist/dev/incubator/singa/0.3.0/

The hashes of the artifacts are as follows:
MD5:  F8 F9 81 D7 60 B9 3E F9  29 80 33 B1 18 8B D7 05

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

and the signature file is:
https://dist.apache.org/repos/dist/dev/incubator/singa/0.3.0/apache-singa-incubating-0.3.0-RC1.tar.gz.asc

The github tag is at
https://github.com/apache/incubator-singa/releases/tag/v0.3.0-rc1. The
commit ID is fb5b2184160f3c2d3b422e5ed58657b6f460d090


To check the license, you can use the Apache Rat tool following
```
./configure
make rat
```
The result is in rat_check file. 

The vote is open for at least 72 hours, or until the necessary number of
 votes (3 +1) is reached.

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

Best,
Wei Wang