You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openaz.apache.org by Marvin <no...@apache.org> on 2015/06/29 16:15:04 UTC

Incubator PMC/Board report for Jul 2015 ([ppmc])


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 July 2015, 10:30 am PST. 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, Jul 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/July2015

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: Incubator PMC/Board report for Jul 2015 ([ppmc])

Posted by Ajith Nair <aj...@gmail.com>.
Pam, Emmanuel, Colm,

I would definitely want to see OpenAz successful and be adopted widely. I haven’t been able to stay engaged as much as I would like to, in the last couple of months or so. I do intent to contribute to this effort going forward.

As Pam mentioned, we have a potential release candidate. Ideally, it would be nice to add a couple of tests that demonstrate the use/configuration of PIPs, with the PepAPI in action. I can take this up and add it in the next few days.

Ajith



> On Jul 2, 2015, at 3:28 PM, DRAGOSH, PAMELA L (PAM) <pd...@research.att.com> wrote:
> 
> Emmanuel,
> 
> I can¹t answer for other folks, I know that myself and my company are
> committed to seeing OpenAZ be successful. I would ask those folks to
> please indicate if they are still committed. I know that my management
> team will get involved and pull in help from our vendors/partners who will
> be utilizing this software in their platforms. I will raise this issue
> with them.
> 
> Pam
> 
> On 6/30/15, 7:05 PM, "Emmanuel Lécharny" <el...@gmail.com> wrote:
> 
>> Le 30/06/15 17:13, DRAGOSH, PAMELA L (PAM) a écrit :
>>> Colm,
>>> 
>>> This code when it was first put into Github was already fully
>>> functioning. In fact, its in production at AT&T.
>>> 
>>> There was a list of items that were done to get it ³Apache-ready², that
>>> included all the package renaming, and all the formatting that you did.
>>> I believe there might be a few more items that folks want done before
>>> the release, we¹ll flesh that out soon enough.
>> 
>> Pamela,
>> 
>> I think you don't get it.
>> 
>> What Colm point out, and I would have done the same thing, would have I
>> posted a response faster, is that this podling has little to no
>> activity, beside what you and Colm has done in the last few weeks. This
>> is not good.
>> 
>> We do expect that projects accepted into the incubator start getting
>> some traction, some new commers to see what's going on, using the
>> existing code, pointing to errors or proposing patches. So far, none of
>> that happened, yet. All what we have seen since january is some code
>> being injected into an Apache repository, some package renaming, and
>> that's pretty much it.
>> 
>> What we need is not -only- a release, but a full status :
>> - who is *really* working on the project ?
>> - what's the roadmap, where is it being discussed ?
>> - do we have potential new committers, or at least some potential ?
>> - what is the effort done to expose the project to the world ? (website,
>> etc) ?
>> 
>> Everything that would make OpenAZ a candidate for a promotion to a TLP,
>> in other words.
>> 
>> I do understand that OpenAZ is used in production, but this is
>> irrelevant : what is is how do we build a community around the project,
>> to maintain it if you have to quite the project. Atm, you are the only
>> one with Colm who have shawn some involvement into it, and we need at
>> least 3 person to vote a release. This is not going to fly...
>> 
>> I do think this project is important and deserves a better exposition,
>> and more effort to make it a vibrant community, beside the original
>> committers. I don't see that happening, as of today, and I'd like to
>> know what is going to be done to fix this issue.
>> 
>> Many thanks !
>> Emmanuel
>> 
> 


Re: Incubator PMC/Board report for Jul 2015 ([ppmc])

Posted by "DRAGOSH, PAMELA L (PAM)" <pd...@research.att.com>.
Emmanuel,

I can¹t answer for other folks, I know that myself and my company are
committed to seeing OpenAZ be successful. I would ask those folks to
please indicate if they are still committed. I know that my management
team will get involved and pull in help from our vendors/partners who will
be utilizing this software in their platforms. I will raise this issue
with them.

Pam

On 6/30/15, 7:05 PM, "Emmanuel Lécharny" <el...@gmail.com> wrote:

>Le 30/06/15 17:13, DRAGOSH, PAMELA L (PAM) a écrit :
>> Colm,
>>
>> This code when it was first put into Github was already fully
>>functioning. In fact, its in production at AT&T.
>>
>> There was a list of items that were done to get it ³Apache-ready², that
>>included all the package renaming, and all the formatting that you did.
>>I believe there might be a few more items that folks want done before
>>the release, we¹ll flesh that out soon enough.
>
>Pamela,
>
>I think you don't get it.
>
>What Colm point out, and I would have done the same thing, would have I
>posted a response faster, is that this podling has little to no
>activity, beside what you and Colm has done in the last few weeks. This
>is not good.
>
>We do expect that projects accepted into the incubator start getting
>some traction, some new commers to see what's going on, using the
>existing code, pointing to errors or proposing patches. So far, none of
>that happened, yet. All what we have seen since january is some code
>being injected into an Apache repository, some package renaming, and
>that's pretty much it.
>
>What we need is not -only- a release, but a full status :
>- who is *really* working on the project ?
>- what's the roadmap, where is it being discussed ?
>- do we have potential new committers, or at least some potential ?
>- what is the effort done to expose the project to the world ? (website,
>etc) ?
>
>Everything that would make OpenAZ a candidate for a promotion to a TLP,
>in other words.
>
>I do understand that OpenAZ is used in production, but this is
>irrelevant : what is is how do we build a community around the project,
>to maintain it if you have to quite the project. Atm, you are the only
>one with Colm who have shawn some involvement into it, and we need at
>least 3 person to vote a release. This is not going to fly...
>
>I do think this project is important and deserves a better exposition,
>and more effort to make it a vibrant community, beside the original
>committers. I don't see that happening, as of today, and I'd like to
>know what is going to be done to fix this issue.
>
>Many thanks !
>Emmanuel
>


Re: Incubator PMC/Board report for Jul 2015 ([ppmc])

Posted by Emmanuel Lécharny <el...@gmail.com>.
Le 30/06/15 17:13, DRAGOSH, PAMELA L (PAM) a écrit :
> Colm,
>
> This code when it was first put into Github was already fully functioning. In fact, its in production at AT&T.
>
> There was a list of items that were done to get it “Apache-ready”, that included all the package renaming, and all the formatting that you did. I believe there might be a few more items that folks want done before the release, we’ll flesh that out soon enough.

Pamela,

I think you don't get it.

What Colm point out, and I would have done the same thing, would have I
posted a response faster, is that this podling has little to no
activity, beside what you and Colm has done in the last few weeks. This
is not good.

We do expect that projects accepted into the incubator start getting
some traction, some new commers to see what's going on, using the
existing code, pointing to errors or proposing patches. So far, none of
that happened, yet. All what we have seen since january is some code
being injected into an Apache repository, some package renaming, and
that's pretty much it.

What we need is not -only- a release, but a full status :
- who is *really* working on the project ?
- what's the roadmap, where is it being discussed ?
- do we have potential new committers, or at least some potential ?
- what is the effort done to expose the project to the world ? (website,
etc) ?

Everything that would make OpenAZ a candidate for a promotion to a TLP,
in other words.

I do understand that OpenAZ is used in production, but this is
irrelevant : what is is how do we build a community around the project,
to maintain it if you have to quite the project. Atm, you are the only
one with Colm who have shawn some involvement into it, and we need at
least 3 person to vote a release. This is not going to fly...

I do think this project is important and deserves a better exposition,
and more effort to make it a vibrant community, beside the original
committers. I don't see that happening, as of today, and I'd like to
know what is going to be done to fix this issue.

Many thanks !
Emmanuel


Re: Incubator PMC/Board report for Jul 2015 ([ppmc])

Posted by "DRAGOSH, PAMELA L (PAM)" <pd...@research.att.com>.
Colm,

This code when it was first put into Github was already fully functioning. In fact, its in production at AT&T.

There was a list of items that were done to get it “Apache-ready”, that included all the package renaming, and all the formatting that you did. I believe there might be a few more items that folks want done before the release, we’ll flesh that out soon enough.

Pam

From: Colm O hEigeartaigh <co...@apache.org>>
Reply-To: "coheigea@apache.org<ma...@apache.org>" <co...@apache.org>>
Date: Tuesday, June 30, 2015 at 10:31 AM
To: Pamela Dragosh <pd...@research.att.com>>
Cc: "dev@openaz.incubator.apache.org<ma...@openaz.incubator.apache.org>" <de...@openaz.incubator.apache.org>>
Subject: Re: Incubator PMC/Board report for Jul 2015 ([ppmc])


The last commit was by me on "Tue May 26"...that is not really indicative that the project is near a release. Or am I missing something?

Colm.

On Tue, Jun 30, 2015 at 2:50 PM, DRAGOSH, PAMELA L (PAM) <pd...@research.att.com>> wrote:
Yes I will be happy to do an update.

I think we are pretty close to doing a release for the software, I¹ll see
if I can kick that off this week. Call a vote?

In addition, I¹ll get that website up and running.

Thanks,

Pam

On 6/30/15, 5:05 AM, "Colm O hEigeartaigh" <co...@apache.org>> wrote:

>Could one of the core OpenAZ team please provide an update on the project?
>There is no work going on here. I believe the problem was a hold-up on the
>Oracle end in terms of the ICLAs, is there any progress on this? This
>podling cannot be maintained indefinitely without any work being done.
>
>Colm.
>
>On Mon, Jun 29, 2015 at 3:15 PM, Marvin <no...@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 July 2015, 10:30 am PST. 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, Jul 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/July2015
>>
>> 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
>>
>>
>
>
>--
>Colm O hEigeartaigh
>
>Talend Community Coder
>http://coders.talend.com




--
Colm O hEigeartaigh

Talend Community Coder
http://coders.talend.com

Re: Incubator PMC/Board report for Jul 2015 ([ppmc])

Posted by Colm O hEigeartaigh <co...@apache.org>.
The last commit was by me on "Tue May 26"...that is not really indicative
that the project is near a release. Or am I missing something?

Colm.

On Tue, Jun 30, 2015 at 2:50 PM, DRAGOSH, PAMELA L (PAM) <
pdragosh@research.att.com> wrote:

> Yes I will be happy to do an update.
>
> I think we are pretty close to doing a release for the software, I¹ll see
> if I can kick that off this week. Call a vote?
>
> In addition, I¹ll get that website up and running.
>
> Thanks,
>
> Pam
>
> On 6/30/15, 5:05 AM, "Colm O hEigeartaigh" <co...@apache.org> wrote:
>
> >Could one of the core OpenAZ team please provide an update on the project?
> >There is no work going on here. I believe the problem was a hold-up on the
> >Oracle end in terms of the ICLAs, is there any progress on this? This
> >podling cannot be maintained indefinitely without any work being done.
> >
> >Colm.
> >
> >On Mon, Jun 29, 2015 at 3:15 PM, Marvin <no...@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 July 2015, 10:30 am PST. 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, Jul 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/July2015
> >>
> >> 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
> >>
> >>
> >
> >
> >--
> >Colm O hEigeartaigh
> >
> >Talend Community Coder
> >http://coders.talend.com
>
>


-- 
Colm O hEigeartaigh

Talend Community Coder
http://coders.talend.com

Re: Incubator PMC/Board report for Jul 2015 ([ppmc])

Posted by "DRAGOSH, PAMELA L (PAM)" <pd...@research.att.com>.
Yes I will be happy to do an update.

I think we are pretty close to doing a release for the software, I¹ll see
if I can kick that off this week. Call a vote?

In addition, I¹ll get that website up and running.

Thanks,

Pam

On 6/30/15, 5:05 AM, "Colm O hEigeartaigh" <co...@apache.org> wrote:

>Could one of the core OpenAZ team please provide an update on the project?
>There is no work going on here. I believe the problem was a hold-up on the
>Oracle end in terms of the ICLAs, is there any progress on this? This
>podling cannot be maintained indefinitely without any work being done.
>
>Colm.
>
>On Mon, Jun 29, 2015 at 3:15 PM, Marvin <no...@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 July 2015, 10:30 am PST. 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, Jul 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/July2015
>>
>> 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
>>
>>
>
>
>-- 
>Colm O hEigeartaigh
>
>Talend Community Coder
>http://coders.talend.com


Re: Incubator PMC/Board report for Jul 2015 ([ppmc])

Posted by Colm O hEigeartaigh <co...@apache.org>.
Could one of the core OpenAZ team please provide an update on the project?
There is no work going on here. I believe the problem was a hold-up on the
Oracle end in terms of the ICLAs, is there any progress on this? This
podling cannot be maintained indefinitely without any work being done.

Colm.

On Mon, Jun 29, 2015 at 3:15 PM, Marvin <no...@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 July 2015, 10:30 am PST. 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, Jul 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/July2015
>
> 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
>
>


-- 
Colm O hEigeartaigh

Talend Community Coder
http://coders.talend.com