You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openaz.apache.org by jo...@apache.org on 2016/05/26 02:34:34 UTC
Podling Report Reminder - June 2016
Dear podling,
This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.
The board meeting is scheduled for Wed, 15 June 2016, 10:30 am PDT.
The report for your podling will form a part of the Incubator PMC
report. The Incubator PMC requires your report to be submitted 2 weeks
before the board meeting, to allow sufficient time for review and
submission (Wed, June 1st).
Please submit your report with sufficient time to allow the Incubator
PMC, and subsequently board members to review and digest. Again, the
very latest you should submit your report is 2 weeks prior to the board
meeting.
Thanks,
The Apache Incubator PMC
Submitting your Report
----------------------
Your report should contain the following:
* Your project name
* A brief description of your project, which assumes no knowledge of
the project or necessarily of its field
* A list of the three most important issues to address in the move
towards graduation.
* Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of
* How has the community developed since the last report
* How has the project developed since the last report.
This should be appended to the Incubator Wiki page at:
http://wiki.apache.org/incubator/May2016
Note: This is manually populated. You may need to wait a little before
this page is created from a template.
Mentors
-------
Mentors should review reports for their project(s) and sign them off on
the Incubator wiki page. Signing off reports shows that you are
following the project - projects that are not signed may raise alarms
for the Incubator PMC.
Incubator PMC
Re: Podling Report Reminder - June 2016
Posted by David Ash <gr...@gmail.com>.
Great job Ajith and Emmanuel! Thanks for getting this taken care of.
On May 31, 2016 12:11 AM, "Emmanuel Lécharny" <el...@gmail.com> wrote:
> Le 30/05/16 à 16:11, Ajith Nair a écrit :
> > Emmanuel,
> >
> > Thank you for the comments. I’ve updated it, please see below.
> >
> > Couple of questions:
> >
> > IP clearance - I’m not quite sure what is involved. Are we talking
> about ICLAs ? The last I know we were waiting for Oracle ICLAs. What else
> needs to be done to move forward ?
>
> You mentionned that the code from 'AT&T, JP Morgan and Oracle' have been
> merged. We just need to be sure that this code is free to use (ie,
> license is compatible, or that those companies have agreed to donate
> this code to The ASF. We don't need another Google vs Oracle battle)
>
> That also mean that all the controbutors to this code must grant the
> donation, too.
>
> >
> > I guess the report needs to uploaded to Apache Wiki before it can be
> signed ?
> Yep.
>
> Thanks !
>
Re: Podling Report Reminder - June 2016
Posted by Emmanuel Lécharny <el...@gmail.com>.
Le 31/05/16 � 16:00, DRAGOSH, PAMELA L (PAM) a �crit :
> Folks (I�m back from 2 weeks of vacation),
>
> The Code from AT&T agreed to donate the code, we filed the correct ICLA�s.
>
> Ajith can confirm for JP Morgan.
>
> I don�t believe Oracle has filed any ICLA�s nor contributed any code. They
> have disappeared from contributing to this effort. If not, I hope they
> speak up.
>
> If this report hasn�t been filed onto the website I will go ahead and do
> so later today.
Thanks Pam !
Re: Podling Report Reminder - June 2016
Posted by David Ash <gr...@gmail.com>.
I just got back from Japan. Am I all set for committing / project
management in Jira yet?
On Wed, Jun 1, 2016 at 2:28 AM, Emmanuel Lécharny <el...@gmail.com>
wrote:
> Le 31/05/16 à 18:55, DRAGOSH, PAMELA L (PAM) a écrit :
> > Yeah the link was incorrect in the last email sent to us. No big deal.
> >
> > I will put it in the June2016 right now.
>
> Many thanks, Pamela !
>
> I just signed off the report. Keep going !
>
>
Re: Podling Report Reminder - June 2016
Posted by Emmanuel Lécharny <el...@gmail.com>.
Le 31/05/16 � 18:55, DRAGOSH, PAMELA L (PAM) a �crit :
> Yeah the link was incorrect in the last email sent to us. No big deal.
>
> I will put it in the June2016 right now.
Many thanks, Pamela !
I just signed off the report. Keep going !
Re: Podling Report Reminder - June 2016
Posted by "DRAGOSH, PAMELA L (PAM)" <pd...@research.att.com>.
Yeah the link was incorrect in the last email sent to us. No big deal.
I will put it in the June2016 right now.
Pam
On 5/31/16, 12:52 PM, "John D. Ament" <jo...@apache.org> wrote:
>On Tue, May 31, 2016 at 12:47 PM Emmanuel Lécharny <el...@gmail.com>
>wrote:
>
>> Le 31/05/16 à 16:13, DRAGOSH, PAMELA L (PAM) a écrit :
>> > Done.
>>
>> Hmmmm. I think you pushed it in the May 2016 page. The correct page is
>> https://wiki.apache.org/incubator/June2016
>>
>>
>My fault - still working the kinks out of Marvin Jr.
Re: Podling Report Reminder - June 2016
Posted by "John D. Ament" <jo...@apache.org>.
On Tue, May 31, 2016 at 12:47 PM Emmanuel Lécharny <el...@gmail.com>
wrote:
> Le 31/05/16 à 16:13, DRAGOSH, PAMELA L (PAM) a écrit :
> > Done.
>
> Hmmmm. I think you pushed it in the May 2016 page. The correct page is
> https://wiki.apache.org/incubator/June2016
>
>
My fault - still working the kinks out of Marvin Jr.
Re: Podling Report Reminder - June 2016
Posted by Emmanuel Lécharny <el...@gmail.com>.
Le 31/05/16 � 16:13, DRAGOSH, PAMELA L (PAM) a �crit :
> Done.
Hmmmm. I think you pushed it in the May 2016 page. The correct page is
https://wiki.apache.org/incubator/June2016
Re: Podling Report Reminder - June 2016
Posted by "DRAGOSH, PAMELA L (PAM)" <pd...@research.att.com>.
Done.
Thanks,
Pam
On 5/31/16, 10:05 AM, "Ajith Nair" <aj...@gmail.com> wrote:
>Pam, please go ahead. I haven't been able to get it to the wiki yet.
>
>Thanks,
>Ajith
>
>Sent from iPhone....
>
>
>> On May 31, 2016, at 10:00 AM, DRAGOSH, PAMELA L (PAM)
>><pd...@research.att.com> wrote:
>>
>> Folks (I¹m back from 2 weeks of vacation),
>>
>> The Code from AT&T agreed to donate the code, we filed the correct
>>ICLA¹s.
>>
>> Ajith can confirm for JP Morgan.
>>
>> I don¹t believe Oracle has filed any ICLA¹s nor contributed any code.
>>They
>> have disappeared from contributing to this effort. If not, I hope they
>> speak up.
>>
>> If this report hasn¹t been filed onto the website I will go ahead and do
>> so later today.
>>
>> Thanks,
>>
>> Pam
>>
>>> On 5/30/16, 11:11 AM, "Emmanuel Lécharny" <el...@gmail.com> wrote:
>>>
>>>> Le 30/05/16 à 16:11, Ajith Nair a écrit :
>>>> Emmanuel,
>>>>
>>>> Thank you for the comments. I¹ve updated it, please see below.
>>>>
>>>> Couple of questions:
>>>>
>>>> IP clearance - I¹m not quite sure what is involved. Are we talking
>>>> about ICLAs ? The last I know we were waiting for Oracle ICLAs. What
>>>> else needs to be done to move forward ?
>>>
>>> You mentionned that the code from 'AT&T, JP Morgan and Oracle' have
>>>been
>>> merged. We just need to be sure that this code is free to use (ie,
>>> license is compatible, or that those companies have agreed to donate
>>> this code to The ASF. We don't need another Google vs Oracle battle)
>>>
>>> That also mean that all the controbutors to this code must grant the
>>> donation, too.
>>>
>>>>
>>>> I guess the report needs to uploaded to Apache Wiki before it can be
>>>> signed ?
>>> Yep.
>>>
>>> Thanks !
>>
Re: Podling Report Reminder - June 2016
Posted by Ajith Nair <aj...@gmail.com>.
Pam, please go ahead. I haven't been able to get it to the wiki yet.
Thanks,
Ajith
Sent from iPhone....
> On May 31, 2016, at 10:00 AM, DRAGOSH, PAMELA L (PAM) <pd...@research.att.com> wrote:
>
> Folks (I¹m back from 2 weeks of vacation),
>
> The Code from AT&T agreed to donate the code, we filed the correct ICLA¹s.
>
> Ajith can confirm for JP Morgan.
>
> I don¹t believe Oracle has filed any ICLA¹s nor contributed any code. They
> have disappeared from contributing to this effort. If not, I hope they
> speak up.
>
> If this report hasn¹t been filed onto the website I will go ahead and do
> so later today.
>
> Thanks,
>
> Pam
>
>> On 5/30/16, 11:11 AM, "Emmanuel Lécharny" <el...@gmail.com> wrote:
>>
>>> Le 30/05/16 à 16:11, Ajith Nair a écrit :
>>> Emmanuel,
>>>
>>> Thank you for the comments. I¹ve updated it, please see below.
>>>
>>> Couple of questions:
>>>
>>> IP clearance - I¹m not quite sure what is involved. Are we talking
>>> about ICLAs ? The last I know we were waiting for Oracle ICLAs. What
>>> else needs to be done to move forward ?
>>
>> You mentionned that the code from 'AT&T, JP Morgan and Oracle' have been
>> merged. We just need to be sure that this code is free to use (ie,
>> license is compatible, or that those companies have agreed to donate
>> this code to The ASF. We don't need another Google vs Oracle battle)
>>
>> That also mean that all the controbutors to this code must grant the
>> donation, too.
>>
>>>
>>> I guess the report needs to uploaded to Apache Wiki before it can be
>>> signed ?
>> Yep.
>>
>> Thanks !
>
Re: Podling Report Reminder - June 2016
Posted by "DRAGOSH, PAMELA L (PAM)" <pd...@research.att.com>.
Folks (I¹m back from 2 weeks of vacation),
The Code from AT&T agreed to donate the code, we filed the correct ICLA¹s.
Ajith can confirm for JP Morgan.
I don¹t believe Oracle has filed any ICLA¹s nor contributed any code. They
have disappeared from contributing to this effort. If not, I hope they
speak up.
If this report hasn¹t been filed onto the website I will go ahead and do
so later today.
Thanks,
Pam
On 5/30/16, 11:11 AM, "Emmanuel Lécharny" <el...@gmail.com> wrote:
>Le 30/05/16 à 16:11, Ajith Nair a écrit :
>> Emmanuel,
>>
>> Thank you for the comments. I¹ve updated it, please see below.
>>
>> Couple of questions:
>>
>> IP clearance - I¹m not quite sure what is involved. Are we talking
>>about ICLAs ? The last I know we were waiting for Oracle ICLAs. What
>>else needs to be done to move forward ?
>
>You mentionned that the code from 'AT&T, JP Morgan and Oracle' have been
>merged. We just need to be sure that this code is free to use (ie,
>license is compatible, or that those companies have agreed to donate
>this code to The ASF. We don't need another Google vs Oracle battle)
>
>That also mean that all the controbutors to this code must grant the
>donation, too.
>
>>
>> I guess the report needs to uploaded to Apache Wiki before it can be
>>signed ?
>Yep.
>
>Thanks !
Re: Podling Report Reminder - June 2016
Posted by Emmanuel Lécharny <el...@gmail.com>.
Le 30/05/16 � 16:11, Ajith Nair a �crit :
> Emmanuel,
>
> Thank you for the comments. I\u2019ve updated it, please see below.
>
> Couple of questions:
>
> IP clearance - I\u2019m not quite sure what is involved. Are we talking about ICLAs ? The last I know we were waiting for Oracle ICLAs. What else needs to be done to move forward ?
You mentionned that the code from 'AT&T, JP Morgan and Oracle' have been
merged. We just need to be sure that this code is free to use (ie,
license is compatible, or that those companies have agreed to donate
this code to The ASF. We don't need another Google vs Oracle battle)
That also mean that all the controbutors to this code must grant the
donation, too.
>
> I guess the report needs to uploaded to Apache Wiki before it can be signed ?
Yep.
Thanks !
Re: Podling Report Reminder - June 2016
Posted by Ajith Nair <aj...@gmail.com>.
Emmanuel,
Thank you for the comments. I’ve updated it, please see below.
Couple of questions:
IP clearance - I’m not quite sure what is involved. Are we talking about ICLAs ? The last I know we were waiting for Oracle ICLAs. What else needs to be done to move forward ?
I guess the report needs to uploaded to Apache Wiki before it can be signed ?
===============================================================
OpenAz
OpenAz is a project to create tools and libraries to enable the
development of Attribute-based Access Control (ABAC) Systems in a
variety of languages. In general the work is at least consistent with
or actually conforming to the OASIS XACML Standard.
OpenAZ has been incubating since 01-2015.
Three most important issues to address in the move towards graduation:
1. Increasing community involvement: We are focusing on getting
information
published on the website to aid the acquisition and orientation of new
contributors,
as well increasing the number of committers, in order to reduce
individual member
workload, reduce reliance on any particular member, and to increase
project velocity. David Ash was voted in as a committer last month.
There are several other committers that may be added in the near future.
2. Merging the source code from AT&T, JP Morgan and Oracle and creating
POMs. AT&T and JP Morgan source code has been merged and POMs created,
it needs uploading into the Apache repository. AT&T and JP Morgan ICLAs were received, but Oracle is taking more time. The IP clearance is on it's way.
3. Get our first release done.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None. The efforts to revive the project seem to be paying off and discussions are gaining traction.
How has the community developed since the last report?
Pam Dragosh, David Ash and Ajith Nair are the active committers at this point. The project intends to reboot the PPMC which may include removing
some of the initial commiters who are no longer active. There are, however, several contributors who could be potentially added as committers in the future.
How has the project developed since the last report?
1. Ongoing collective effort to improve project documentation, marketing material for better visbility and adoption.
2. A pending contribution towards PEP implementation is being reviewed and we plan to merge in these changes soon.
3. We are looking into design feedback/comments from Nextlabs - a XACML service provider. We hope to incorporate many of these in the coming weeks.
Date of last release:
N/A
When were the last committers or PMC members elected?
One new committer was elected Tuesday, May 3rd.
=================================================================
Thanks,
Ajith
> On May 28, 2016, at 2:01 AM, Emmanuel Lécharny <el...@gmail.com> wrote:
>
> Le 28/05/16 à 07:04, Ajith Nair a écrit :
>> How about this ?
>>
>> ==========================================================
>>
>> OpenAz
>>
>> OpenAz is a project to create tools and libraries to enable the
>> development of Attribute-based Access Control (ABAC) Systems in a
>> variety of languages. In general the work is at least consistent with
>> or actually conforming to the OASIS XACML Standard.
>>
>> OpenAZ has been incubating since 01-2015.
>>
>>
>> Three most important issues to address in the move towards graduation:
>>
>> 1. Increasing community involvement: We are focusing on getting
>> information
>> published on the website to aid the acquisition and orientation of new
>> contributors,
>> as well increasing the number of committers, in order to reduce
>> individual member
>> workload, reduce reliance on any particular member, and to increase
>> project velocity. No new committers were added in the previous month.
>
> Actually, David was added...
>
>> There are several other committers that may be added in the near future.
>>
>> 2. Merging the source code from AT&T, JP Morgan and Oracle and creating
>> POM¹s. AT&T and JP Morgan source code has been merged and POM¹s created,
>> it needs uploading into the Apache repository.
> I think there are som non ascii chars (POM¹s instead of POM's)
>
> Regardless, inform the board that IP clearance is on its way : we
> absolutely need to be sure that the code coming from such big companies
> are allowed to be injected into The ASF code base (Oracle is proven to
> be picky when it comes to IP and Copyright - even if it's only an API ;-) )
>>
>> 3. Get our first release done.
>>
>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
>> aware of?
>>
>> None. The efforts to revive the project seem to be paying off and discussions are gaining traction.
>>
>> How has the community developed since the last report?
>>
>> No new committers were added. There are several contributors who could be potentially added as committers in the future
> See upper.
>
> At this point, it would be good to establish who are the active
> committers, telling the board that the project intend to 'reboot' the
> PPMC (that may implies some of the initial committers will be removed
> from teh list of PPMC members)
>
>>
>> How has the project developed since the last report?
>>
>> 1. Ongoing collective effort to improve project documentation, marketing material for better visbility and adoption.
>> 2. A pending contribution towards PEP implementation is being reviewed and we plan to merge in these changes soon.
>> 3. We are looking into design feedback/comments from Nextlabs - a XACML service provider. We hope to incorporate many of these in the coming weeks.
>>
>> Date of last release:
>>
>> N/A
>>
>> When were the last committers or PMC members elected?
>>
>> One new committer was elected Tuesday, May 3rd.
>> ==========================================================
>
> Thanks a lot, Ajith !
Re: Podling Report Reminder - June 2016
Posted by Emmanuel Lécharny <el...@gmail.com>.
Le 28/05/16 � 07:04, Ajith Nair a �crit :
> How about this ?
>
> ==========================================================
>
> OpenAz
>
> OpenAz is a project to create tools and libraries to enable the
> development of Attribute-based Access Control (ABAC) Systems in a
> variety of languages. In general the work is at least consistent with
> or actually conforming to the OASIS XACML Standard.
>
> OpenAZ has been incubating since 01-2015.
>
>
> Three most important issues to address in the move towards graduation:
>
> 1. Increasing community involvement: We are focusing on getting
> information
> published on the website to aid the acquisition and orientation of new
> contributors,
> as well increasing the number of committers, in order to reduce
> individual member
> workload, reduce reliance on any particular member, and to increase
> project velocity. No new committers were added in the previous month.
Actually, David was added...
> There are several other committers that may be added in the near future.
>
> 2. Merging the source code from AT&T, JP Morgan and Oracle and creating
> POM�s. AT&T and JP Morgan source code has been merged and POM�s created,
> it needs uploading into the Apache repository.
I think there are som non ascii chars (POM�s instead of POM's)
Regardless, inform the board that IP clearance is on its way : we
absolutely need to be sure that the code coming from such big companies
are allowed to be injected into The ASF code base (Oracle is proven to
be picky when it comes to IP and Copyright - even if it's only an API ;-) )
>
> 3. Get our first release done.
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
> None. The efforts to revive the project seem to be paying off and discussions are gaining traction.
>
> How has the community developed since the last report?
>
> No new committers were added. There are several contributors who could be potentially added as committers in the future
See upper.
At this point, it would be good to establish who are the active
committers, telling the board that the project intend to 'reboot' the
PPMC (that may implies some of the initial committers will be removed
from teh list of PPMC members)
>
> How has the project developed since the last report?
>
> 1. Ongoing collective effort to improve project documentation, marketing material for better visbility and adoption.
> 2. A pending contribution towards PEP implementation is being reviewed and we plan to merge in these changes soon.
> 3. We are looking into design feedback/comments from Nextlabs - a XACML service provider. We hope to incorporate many of these in the coming weeks.
>
> Date of last release:
>
> N/A
>
> When were the last committers or PMC members elected?
>
> One new committer was elected Tuesday, May 3rd.
> ==========================================================
Thanks a lot, Ajith !
Re: Podling Report Reminder - June 2016
Posted by Ajith Nair <aj...@gmail.com>.
How about this ?
==========================================================
OpenAz
OpenAz is a project to create tools and libraries to enable the
development of Attribute-based Access Control (ABAC) Systems in a
variety of languages. In general the work is at least consistent with
or actually conforming to the OASIS XACML Standard.
OpenAZ has been incubating since 01-2015.
Three most important issues to address in the move towards graduation:
1. Increasing community involvement: We are focusing on getting
information
published on the website to aid the acquisition and orientation of new
contributors,
as well increasing the number of committers, in order to reduce
individual member
workload, reduce reliance on any particular member, and to increase
project velocity. No new committers were added in the previous month.
There are several other committers that may be added in the near future.
2. Merging the source code from AT&T, JP Morgan and Oracle and creating
POM¹s. AT&T and JP Morgan source code has been merged and POM¹s created,
it needs uploading into the Apache repository.
3. Get our first release done.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None. The efforts to revive the project seem to be paying off and discussions are gaining traction.
How has the community developed since the last report?
No new committers were added. There are several contributors who could be potentially added as committers in the future.
How has the project developed since the last report?
1. Ongoing collective effort to improve project documentation, marketing material for better visbility and adoption.
2. A pending contribution towards PEP implementation is being reviewed and we plan to merge in these changes soon.
3. We are looking into design feedback/comments from Nextlabs - a XACML service provider. We hope to incorporate many of these in the coming weeks.
Date of last release:
N/A
When were the last committers or PMC members elected?
One new committer was elected Tuesday, May 3rd.
==========================================================
> On May 27, 2016, at 8:42 AM, David Ash <gr...@gmail.com> wrote:
>
> Awesome. Thanks! :-)
>
> On Fri, May 27, 2016 at 6:26 AM, Ajith Nair <aj...@gmail.com> wrote:
>
>> I'll take a shot at it.
>>
>> Thanks,
>> Ajith
>>
>>
>>> On May 26, 2016, at 9:21 PM, David Ash <gr...@gmail.com> wrote:
>>>
>>> Okay... so what's our story? Anyone else want to take a crack at it? If
>>> not, I'll probably be able to come up with something before Jun 1.
>>>
>>> On Thu, May 26, 2016 at 2:38 AM, Emmanuel Lécharny <el...@gmail.com>
>>> wrote:
>>>
>>>>> Le 26/05/16 à 07:02, David Ash a écrit :
>>>>> As an FYI to others, I am currently in Japan (on vacation) and will not
>>>> be
>>>>> back until after June 1st. I am mildly available to help if necessary,
>>>> but
>>>>> I am hopeful others will be able to do this.
>>>>>
>>>>> If not, please let me know.
>>>>>
>>>>> Also, didn't we just do one of these (within the past month)?
>>>>
>>>> Yes, this is every month.
>>>>
>>>> This one is critical because the last one was discussing about the
>>>> potential shutdown of the project, so we need to provide some feedback
>>>> about the current reboot (which seems to be in good way)
>>>>
>>>>
>>
Re: Podling Report Reminder - June 2016
Posted by David Ash <gr...@gmail.com>.
Awesome. Thanks! :-)
On Fri, May 27, 2016 at 6:26 AM, Ajith Nair <aj...@gmail.com> wrote:
> I'll take a shot at it.
>
> Thanks,
> Ajith
>
>
> > On May 26, 2016, at 9:21 PM, David Ash <gr...@gmail.com> wrote:
> >
> > Okay... so what's our story? Anyone else want to take a crack at it? If
> > not, I'll probably be able to come up with something before Jun 1.
> >
> > On Thu, May 26, 2016 at 2:38 AM, Emmanuel Lécharny <el...@gmail.com>
> > wrote:
> >
> >>> Le 26/05/16 à 07:02, David Ash a écrit :
> >>> As an FYI to others, I am currently in Japan (on vacation) and will not
> >> be
> >>> back until after June 1st. I am mildly available to help if necessary,
> >> but
> >>> I am hopeful others will be able to do this.
> >>>
> >>> If not, please let me know.
> >>>
> >>> Also, didn't we just do one of these (within the past month)?
> >>
> >> Yes, this is every month.
> >>
> >> This one is critical because the last one was discussing about the
> >> potential shutdown of the project, so we need to provide some feedback
> >> about the current reboot (which seems to be in good way)
> >>
> >>
>
Re: Podling Report Reminder - June 2016
Posted by Ajith Nair <aj...@gmail.com>.
I'll take a shot at it.
Thanks,
Ajith
> On May 26, 2016, at 9:21 PM, David Ash <gr...@gmail.com> wrote:
>
> Okay... so what's our story? Anyone else want to take a crack at it? If
> not, I'll probably be able to come up with something before Jun 1.
>
> On Thu, May 26, 2016 at 2:38 AM, Emmanuel Lécharny <el...@gmail.com>
> wrote:
>
>>> Le 26/05/16 à 07:02, David Ash a écrit :
>>> As an FYI to others, I am currently in Japan (on vacation) and will not
>> be
>>> back until after June 1st. I am mildly available to help if necessary,
>> but
>>> I am hopeful others will be able to do this.
>>>
>>> If not, please let me know.
>>>
>>> Also, didn't we just do one of these (within the past month)?
>>
>> Yes, this is every month.
>>
>> This one is critical because the last one was discussing about the
>> potential shutdown of the project, so we need to provide some feedback
>> about the current reboot (which seems to be in good way)
>>
>>
Re: Podling Report Reminder - June 2016
Posted by David Ash <gr...@gmail.com>.
Okay... so what's our story? Anyone else want to take a crack at it? If
not, I'll probably be able to come up with something before Jun 1.
On Thu, May 26, 2016 at 2:38 AM, Emmanuel Lécharny <el...@gmail.com>
wrote:
> Le 26/05/16 à 07:02, David Ash a écrit :
> > As an FYI to others, I am currently in Japan (on vacation) and will not
> be
> > back until after June 1st. I am mildly available to help if necessary,
> but
> > I am hopeful others will be able to do this.
> >
> > If not, please let me know.
> >
> > Also, didn't we just do one of these (within the past month)?
>
> Yes, this is every month.
>
> This one is critical because the last one was discussing about the
> potential shutdown of the project, so we need to provide some feedback
> about the current reboot (which seems to be in good way)
>
>
Re: Podling Report Reminder - June 2016
Posted by Emmanuel Lécharny <el...@gmail.com>.
Le 26/05/16 � 07:02, David Ash a �crit :
> As an FYI to others, I am currently in Japan (on vacation) and will not be
> back until after June 1st. I am mildly available to help if necessary, but
> I am hopeful others will be able to do this.
>
> If not, please let me know.
>
> Also, didn't we just do one of these (within the past month)?
Yes, this is every month.
This one is critical because the last one was discussing about the
potential shutdown of the project, so we need to provide some feedback
about the current reboot (which seems to be in good way)
Re: Podling Report Reminder - June 2016
Posted by David Ash <gr...@gmail.com>.
As an FYI to others, I am currently in Japan (on vacation) and will not be
back until after June 1st. I am mildly available to help if necessary, but
I am hopeful others will be able to do this.
If not, please let me know.
Also, didn't we just do one of these (within the past month)?
On Wed, May 25, 2016 at 8:34 PM, <jo...@apache.org> wrote:
> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
>
> The board meeting is scheduled for Wed, 15 June 2016, 10:30 am PDT.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, June 1st).
>
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
>
> Thanks,
>
> The Apache Incubator PMC
>
> Submitting your Report
>
> ----------------------
>
> Your report should contain the following:
>
> * Your project name
> * A brief description of your project, which assumes no knowledge of
> the project or necessarily of its field
> * A list of the three most important issues to address in the move
> towards graduation.
> * Any issues that the Incubator PMC or ASF Board might wish/need to be
> aware of
> * How has the community developed since the last report
> * How has the project developed since the last report.
>
> This should be appended to the Incubator Wiki page at:
>
> http://wiki.apache.org/incubator/May2016
>
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
>
> Mentors
> -------
>
> Mentors should review reports for their project(s) and sign them off on
> the Incubator wiki page. Signing off reports shows that you are
> following the project - projects that are not signed may raise alarms
> for the Incubator PMC.
>
> Incubator PMC
>