Podling Report Reminder - August 2016

2016-08-03 Thread johndament 
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, 17 August 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, August 03).

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

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

Podling Report Reminder - August 2016

2016-08-02 Thread johndament 
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, 17 August 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, August 03).

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

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

2016-07-31 Thread Jean-Baptiste Onofré 

Hi James,

It's time to paste the board report on the incubator wiki:

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

It will allow mentors to have time to review and sign off the report.

Can you please do it ?
If you need any assist (permission on the wiki, ...), please let me know.

Thanks,
Regards
JB

On 07/29/2016 05:42 PM, James Malone wrote:

Hey JB,

Good catch; my sincere apologies that wasn't on the list! At this point I
propose we put the draft report with your addition on the wiki. Unless
anyone disagrees can you please do that JB? I don;t have wiki edit access.

Cheers!

James

On Thu, Jul 28, 2016 at 1:15 PM Jean-Baptiste Onofré 
wrote:


Hi James,

About the talks, we can add JBCN Barcelona ("Introduction to Apache
Beam") that I did in June.

Even than that, it looks good to me.

Regards
JB

On 07/28/2016 09:57 PM, James Malone wrote:

Hello everyone!

Here is a draft podling report for the August 2016 cycle. As you will

see,

I have mentioned 0.2.0-incubating; we will want to update this report

with

any developments on that release, so the report we submit has the most
up-to-date information. Please comment on any changes you'd like to see.

Best,

James

---

Beam

Apache Beam is an open source, unified model and set of language-specific
SDKs for defining and executing data processing workflows, and also data
ingestion and integration flows, supporting Enterprise Integration

Patterns

(EIPs) and Domain Specific Languages (DSLs). Beam pipelines simplify the
mechanics of large-scale batch and streaming data processing and can run

on

a number of runtimes such as Apache Flink, Apache Gearpump, Apache Spark,
and Google Cloud Dataflow (a cloud service). Beam also brings SDKs in
different languages, allowing users to easily implement their data
integration processes.

Beam has been incubating since 2016-02-01.

Three most important issues to address in the move towards graduation:
1. Additional and continued Beam releases
2. Grow the community of Beam users and contributors
3. Add to and improve upon documentation, code samples, and project

website


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

How has the community developed since the last report?
   * 425 closed/merged pull requests
   * High engagement on dev and user mailing lists (590 / 455 messages)
   * Several public talks, articles, and videos including:
 * Hadoop Summit San Jose (“Apache Beam: A Unified Model for Batch

and

Streaming Data Processing” & “The Next Generation of Data Processing &

OSS”

)
 * O’Reilly & The New Stack (“Future-proof and scale-proof your

code”)

 * QCon NY (“Apache Beam: The Case for Unifying Streaming API's”)

How has the project developed since the last report?
Major developments on the project since last report include the

following:

   * First incubating release (0.1.0-incubating)
   * Addition of Apache Beam Python SDK
   * Addition of the Apache Gearpump runner
   * Added support for writing to Apache Kafka clusters
   * Added support for reading from and writing to Java Message Services,
including Apache ActiveMQ, GeronimoJMS, and RabbitMQ
   * Ratified new Beam model APIs to improve efficiency and failure
handling: DoFn setup, teardown, and reuse
   * Optimized key components such as data serialization and shuffle
   * Continued improvements to the Flink, Spark, and Dataflow runners
   * Continued reorganization and refactoring of the project
   * Continued improvements to documentation and testing

Date of last release:
   * 2016/06/15 - 0.1.0-incubating
   * 2016/07/28 - 0.2.0-incubating (RC proposed)

When were the last committers or PMC members elected?
N/A - no changes since last report.

Signed-off-by:

[ ](beam) Jean-Baptiste Onofre
[ ](beam) Venkatesh Seetharam
[ ](beam) Bertrand Delacretaz
[ ](beam) Ted Dunning

Shepherd/Mentor notes:


On Wed, Jul 27, 2016 at 2:01 PM Aljoscha Krettek 
wrote:


+1

On Wed, Jul 27, 2016, 21:14 Amit Sela  wrote:


+1

On Wed, Jul 27, 2016, 22:12 Dan Halperin 
wrote:


+1 on all the above.

On Wed, Jul 27, 2016 at 12:07 PM, Jean-Baptiste Onofré <

j...@nanthrax.net>

wrote:


Hi James,

Sure, please go ahead.

I propose to send the draft on the mailing list for review. When

reviewed,

we will add on the incubator wiki (I will help you if you don't have

the

permission to do so).

Regards
JB


On 07/27/2016 07:22 PM, James Malone wrote:


Hi all,

Unless anyone disagrees, I will volunteer to write this podling

report.

My

goal is to get a draft out this week so we can review it as a

project

before we submit it to the Incubator PMC.

Cheers!

James

On Wed, Jul 27, 2016 at 4:47 AM  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.

Re: Podling Report Reminder - August 2016

2016-07-29 Thread James Malone 
Hey JB,

Good catch; my sincere apologies that wasn't on the list! At this point I
propose we put the draft report with your addition on the wiki. Unless
anyone disagrees can you please do that JB? I don;t have wiki edit access.

Cheers!

James

On Thu, Jul 28, 2016 at 1:15 PM Jean-Baptiste Onofré 
wrote:

> Hi James,
>
> About the talks, we can add JBCN Barcelona ("Introduction to Apache
> Beam") that I did in June.
>
> Even than that, it looks good to me.
>
> Regards
> JB
>
> On 07/28/2016 09:57 PM, James Malone wrote:
> > Hello everyone!
> >
> > Here is a draft podling report for the August 2016 cycle. As you will
> see,
> > I have mentioned 0.2.0-incubating; we will want to update this report
> with
> > any developments on that release, so the report we submit has the most
> > up-to-date information. Please comment on any changes you'd like to see.
> >
> > Best,
> >
> > James
> >
> > ---
> >
> > Beam
> >
> > Apache Beam is an open source, unified model and set of language-specific
> > SDKs for defining and executing data processing workflows, and also data
> > ingestion and integration flows, supporting Enterprise Integration
> Patterns
> > (EIPs) and Domain Specific Languages (DSLs). Beam pipelines simplify the
> > mechanics of large-scale batch and streaming data processing and can run
> on
> > a number of runtimes such as Apache Flink, Apache Gearpump, Apache Spark,
> > and Google Cloud Dataflow (a cloud service). Beam also brings SDKs in
> > different languages, allowing users to easily implement their data
> > integration processes.
> >
> > Beam has been incubating since 2016-02-01.
> >
> > Three most important issues to address in the move towards graduation:
> > 1. Additional and continued Beam releases
> > 2. Grow the community of Beam users and contributors
> > 3. Add to and improve upon documentation, code samples, and project
> website
> >
> > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> > aware of?
> > None.
> >
> > How has the community developed since the last report?
> >* 425 closed/merged pull requests
> >* High engagement on dev and user mailing lists (590 / 455 messages)
> >* Several public talks, articles, and videos including:
> >  * Hadoop Summit San Jose (“Apache Beam: A Unified Model for Batch
> and
> > Streaming Data Processing” & “The Next Generation of Data Processing &
> OSS”
> > )
> >  * O’Reilly & The New Stack (“Future-proof and scale-proof your
> code”)
> >  * QCon NY (“Apache Beam: The Case for Unifying Streaming API's”)
> >
> > How has the project developed since the last report?
> > Major developments on the project since last report include the
> following:
> >* First incubating release (0.1.0-incubating)
> >* Addition of Apache Beam Python SDK
> >* Addition of the Apache Gearpump runner
> >* Added support for writing to Apache Kafka clusters
> >* Added support for reading from and writing to Java Message Services,
> > including Apache ActiveMQ, GeronimoJMS, and RabbitMQ
> >* Ratified new Beam model APIs to improve efficiency and failure
> > handling: DoFn setup, teardown, and reuse
> >* Optimized key components such as data serialization and shuffle
> >* Continued improvements to the Flink, Spark, and Dataflow runners
> >* Continued reorganization and refactoring of the project
> >* Continued improvements to documentation and testing
> >
> > Date of last release:
> >* 2016/06/15 - 0.1.0-incubating
> >* 2016/07/28 - 0.2.0-incubating (RC proposed)
> >
> > When were the last committers or PMC members elected?
> > N/A - no changes since last report.
> >
> > Signed-off-by:
> >
> > [ ](beam) Jean-Baptiste Onofre
> > [ ](beam) Venkatesh Seetharam
> > [ ](beam) Bertrand Delacretaz
> > [ ](beam) Ted Dunning
> >
> > Shepherd/Mentor notes:
> >
> >
> > On Wed, Jul 27, 2016 at 2:01 PM Aljoscha Krettek 
> > wrote:
> >
> >> +1
> >>
> >> On Wed, Jul 27, 2016, 21:14 Amit Sela  wrote:
> >>
> >>> +1
> >>>
> >>> On Wed, Jul 27, 2016, 22:12 Dan Halperin 
> >>> wrote:
> >>>
>  +1 on all the above.
> 
>  On Wed, Jul 27, 2016 at 12:07 PM, Jean-Baptiste Onofré <
> >> j...@nanthrax.net>
>  wrote:
> 
> > Hi James,
> >
> > Sure, please go ahead.
> >
> > I propose to send the draft on the mailing list for review. When
>  reviewed,
> > we will add on the incubator wiki (I will help you if you don't have
> >>> the
> > permission to do so).
> >
> > Regards
> > JB
> >
> >
> > On 07/27/2016 07:22 PM, James Malone wrote:
> >
> >> Hi all,
> >>
> >> Unless anyone disagrees, I will volunteer to write this podling
> >>> report.
>  My
> >> goal is to get a draft out this week so we can review it as a
> >> project
> >> before we submit it to the Incubator PMC.
> >>
> >> Cheers!
> >>
> >> James
> >>

Re: Podling Report Reminder - August 2016

2016-07-28 Thread Jean-Baptiste Onofré 

Hi James,

About the talks, we can add JBCN Barcelona ("Introduction to Apache 
Beam") that I did in June.


Even than that, it looks good to me.

Regards
JB

On 07/28/2016 09:57 PM, James Malone wrote:

Hello everyone!

Here is a draft podling report for the August 2016 cycle. As you will see,
I have mentioned 0.2.0-incubating; we will want to update this report with
any developments on that release, so the report we submit has the most
up-to-date information. Please comment on any changes you'd like to see.

Best,

James

---

Beam

Apache Beam is an open source, unified model and set of language-specific
SDKs for defining and executing data processing workflows, and also data
ingestion and integration flows, supporting Enterprise Integration Patterns
(EIPs) and Domain Specific Languages (DSLs). Beam pipelines simplify the
mechanics of large-scale batch and streaming data processing and can run on
a number of runtimes such as Apache Flink, Apache Gearpump, Apache Spark,
and Google Cloud Dataflow (a cloud service). Beam also brings SDKs in
different languages, allowing users to easily implement their data
integration processes.

Beam has been incubating since 2016-02-01.

Three most important issues to address in the move towards graduation:
1. Additional and continued Beam releases
2. Grow the community of Beam users and contributors
3. Add to and improve upon documentation, code samples, and project website

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

How has the community developed since the last report?
   * 425 closed/merged pull requests
   * High engagement on dev and user mailing lists (590 / 455 messages)
   * Several public talks, articles, and videos including:
 * Hadoop Summit San Jose (“Apache Beam: A Unified Model for Batch and
Streaming Data Processing” & “The Next Generation of Data Processing & OSS”
)
 * O’Reilly & The New Stack (“Future-proof and scale-proof your code”)
 * QCon NY (“Apache Beam: The Case for Unifying Streaming API's”)

How has the project developed since the last report?
Major developments on the project since last report include the following:
   * First incubating release (0.1.0-incubating)
   * Addition of Apache Beam Python SDK
   * Addition of the Apache Gearpump runner
   * Added support for writing to Apache Kafka clusters
   * Added support for reading from and writing to Java Message Services,
including Apache ActiveMQ, GeronimoJMS, and RabbitMQ
   * Ratified new Beam model APIs to improve efficiency and failure
handling: DoFn setup, teardown, and reuse
   * Optimized key components such as data serialization and shuffle
   * Continued improvements to the Flink, Spark, and Dataflow runners
   * Continued reorganization and refactoring of the project
   * Continued improvements to documentation and testing

Date of last release:
   * 2016/06/15 - 0.1.0-incubating
   * 2016/07/28 - 0.2.0-incubating (RC proposed)

When were the last committers or PMC members elected?
N/A - no changes since last report.

Signed-off-by:

[ ](beam) Jean-Baptiste Onofre
[ ](beam) Venkatesh Seetharam
[ ](beam) Bertrand Delacretaz
[ ](beam) Ted Dunning

Shepherd/Mentor notes:


On Wed, Jul 27, 2016 at 2:01 PM Aljoscha Krettek 
wrote:


+1

On Wed, Jul 27, 2016, 21:14 Amit Sela  wrote:


+1

On Wed, Jul 27, 2016, 22:12 Dan Halperin 
wrote:


+1 on all the above.

On Wed, Jul 27, 2016 at 12:07 PM, Jean-Baptiste Onofré <

j...@nanthrax.net>

wrote:


Hi James,

Sure, please go ahead.

I propose to send the draft on the mailing list for review. When

reviewed,

we will add on the incubator wiki (I will help you if you don't have

the

permission to do so).

Regards
JB


On 07/27/2016 07:22 PM, James Malone wrote:


Hi all,

Unless anyone disagrees, I will volunteer to write this podling

report.

My

goal is to get a draft out this week so we can review it as a

project

before we submit it to the Incubator PMC.

Cheers!

James

On Wed, Jul 27, 2016 at 4:47 AM  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, 17 August 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, August 03).

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

Re: Podling Report Reminder - August 2016

2016-07-28 Thread James Malone 
Hello everyone!

Here is a draft podling report for the August 2016 cycle. As you will see,
I have mentioned 0.2.0-incubating; we will want to update this report with
any developments on that release, so the report we submit has the most
up-to-date information. Please comment on any changes you'd like to see.

Best,

James

---

Beam

Apache Beam is an open source, unified model and set of language-specific
SDKs for defining and executing data processing workflows, and also data
ingestion and integration flows, supporting Enterprise Integration Patterns
(EIPs) and Domain Specific Languages (DSLs). Beam pipelines simplify the
mechanics of large-scale batch and streaming data processing and can run on
a number of runtimes such as Apache Flink, Apache Gearpump, Apache Spark,
and Google Cloud Dataflow (a cloud service). Beam also brings SDKs in
different languages, allowing users to easily implement their data
integration processes.

Beam has been incubating since 2016-02-01.

Three most important issues to address in the move towards graduation:
1. Additional and continued Beam releases
2. Grow the community of Beam users and contributors
3. Add to and improve upon documentation, code samples, and project website

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

How has the community developed since the last report?
  * 425 closed/merged pull requests
  * High engagement on dev and user mailing lists (590 / 455 messages)
  * Several public talks, articles, and videos including:
* Hadoop Summit San Jose (“Apache Beam: A Unified Model for Batch and
Streaming Data Processing” & “The Next Generation of Data Processing & OSS”
)
* O’Reilly & The New Stack (“Future-proof and scale-proof your code”)
* QCon NY (“Apache Beam: The Case for Unifying Streaming API's”)

How has the project developed since the last report?
Major developments on the project since last report include the following:
  * First incubating release (0.1.0-incubating)
  * Addition of Apache Beam Python SDK
  * Addition of the Apache Gearpump runner
  * Added support for writing to Apache Kafka clusters
  * Added support for reading from and writing to Java Message Services,
including Apache ActiveMQ, GeronimoJMS, and RabbitMQ
  * Ratified new Beam model APIs to improve efficiency and failure
handling: DoFn setup, teardown, and reuse
  * Optimized key components such as data serialization and shuffle
  * Continued improvements to the Flink, Spark, and Dataflow runners
  * Continued reorganization and refactoring of the project
  * Continued improvements to documentation and testing

Date of last release:
  * 2016/06/15 - 0.1.0-incubating
  * 2016/07/28 - 0.2.0-incubating (RC proposed)

When were the last committers or PMC members elected?
N/A - no changes since last report.

Signed-off-by:

[ ](beam) Jean-Baptiste Onofre
[ ](beam) Venkatesh Seetharam
[ ](beam) Bertrand Delacretaz
[ ](beam) Ted Dunning

Shepherd/Mentor notes:


On Wed, Jul 27, 2016 at 2:01 PM Aljoscha Krettek 
wrote:

> +1
>
> On Wed, Jul 27, 2016, 21:14 Amit Sela  wrote:
>
> > +1
> >
> > On Wed, Jul 27, 2016, 22:12 Dan Halperin 
> > wrote:
> >
> > > +1 on all the above.
> > >
> > > On Wed, Jul 27, 2016 at 12:07 PM, Jean-Baptiste Onofré <
> j...@nanthrax.net>
> > > wrote:
> > >
> > > > Hi James,
> > > >
> > > > Sure, please go ahead.
> > > >
> > > > I propose to send the draft on the mailing list for review. When
> > > reviewed,
> > > > we will add on the incubator wiki (I will help you if you don't have
> > the
> > > > permission to do so).
> > > >
> > > > Regards
> > > > JB
> > > >
> > > >
> > > > On 07/27/2016 07:22 PM, James Malone wrote:
> > > >
> > > >> Hi all,
> > > >>
> > > >> Unless anyone disagrees, I will volunteer to write this podling
> > report.
> > > My
> > > >> goal is to get a draft out this week so we can review it as a
> project
> > > >> before we submit it to the Incubator PMC.
> > > >>
> > > >> Cheers!
> > > >>
> > > >> James
> > > >>
> > > >> On Wed, Jul 27, 2016 at 4:47 AM  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, 17 August 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, August 03).
> > > >>>
> > > >>> 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

Re: Podling Report Reminder - August 2016

2016-07-27 Thread Jean-Baptiste Onofré 

Hi James,

Sure, please go ahead.

I propose to send the draft on the mailing list for review. When 
reviewed, we will add on the incubator wiki (I will help you if you 
don't have the permission to do so).


Regards
JB

On 07/27/2016 07:22 PM, James Malone wrote:

Hi all,

Unless anyone disagrees, I will volunteer to write this podling report. My
goal is to get a draft out this week so we can review it as a project
before we submit it to the Incubator PMC.

Cheers!

James

On Wed, Jul 27, 2016 at 4:47 AM  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, 17 August 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, August 03).

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

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





--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Podling Report Reminder - August 2016

2016-07-27 Thread Amit Sela 
+1

On Wed, Jul 27, 2016, 22:12 Dan Halperin 
wrote:

> +1 on all the above.
>
> On Wed, Jul 27, 2016 at 12:07 PM, Jean-Baptiste Onofré 
> wrote:
>
> > Hi James,
> >
> > Sure, please go ahead.
> >
> > I propose to send the draft on the mailing list for review. When
> reviewed,
> > we will add on the incubator wiki (I will help you if you don't have the
> > permission to do so).
> >
> > Regards
> > JB
> >
> >
> > On 07/27/2016 07:22 PM, James Malone wrote:
> >
> >> Hi all,
> >>
> >> Unless anyone disagrees, I will volunteer to write this podling report.
> My
> >> goal is to get a draft out this week so we can review it as a project
> >> before we submit it to the Incubator PMC.
> >>
> >> Cheers!
> >>
> >> James
> >>
> >> On Wed, Jul 27, 2016 at 4:47 AM  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, 17 August 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, August 03).
> >>>
> >>> 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/August2016
> >>>
> >>> 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
> >>>
> >>>
> >>
> > --
> > Jean-Baptiste Onofré
> > jbono...@apache.org
> > http://blog.nanthrax.net
> > Talend - http://www.talend.com
> >
>

Re: Podling Report Reminder - August 2016

2016-07-27 Thread Dan Halperin 
+1 on all the above.

On Wed, Jul 27, 2016 at 12:07 PM, Jean-Baptiste Onofré 
wrote:

> Hi James,
>
> Sure, please go ahead.
>
> I propose to send the draft on the mailing list for review. When reviewed,
> we will add on the incubator wiki (I will help you if you don't have the
> permission to do so).
>
> Regards
> JB
>
>
> On 07/27/2016 07:22 PM, James Malone wrote:
>
>> Hi all,
>>
>> Unless anyone disagrees, I will volunteer to write this podling report. My
>> goal is to get a draft out this week so we can review it as a project
>> before we submit it to the Incubator PMC.
>>
>> Cheers!
>>
>> James
>>
>> On Wed, Jul 27, 2016 at 4:47 AM  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, 17 August 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, August 03).
>>>
>>> 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/August2016
>>>
>>> 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
>>>
>>>
>>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: Podling Report Reminder - August 2016

2016-07-27 Thread James Malone 
Hi all,

Unless anyone disagrees, I will volunteer to write this podling report. My
goal is to get a draft out this week so we can review it as a project
before we submit it to the Incubator PMC.

Cheers!

James

On Wed, Jul 27, 2016 at 4:47 AM  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, 17 August 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, August 03).
>
> 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/August2016
>
> 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
>

Podling Report Reminder - August 2016

2016-07-27 Thread johndament 
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, 17 August 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, August 03).

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

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