Re: Podling Report Reminder - November 2016
Hi guys, I just updated the wiki page with the Beam podling report. You can still review it there: https://wiki.apache.org/incubator/November2016 Regards JB On 11/02/2016 07:30 AM, James Malone wrote: 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 Apex, Apache Spark, and Google Cloud Dataflow. Beam also brings SDKs in different languages, allowing users to easily implement their data integration processes. Beam has been incubating since 2016-02-01. The most important issue to address in the move towards graduation: 1. Make it easier for the Beam community to to learn, use, and grow by expanding and improving the Beam documentation, code samples, and the 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? * 441 closed/merged pull requests * High engagement on dev and user mailing lists (742 / 179 messages) * Several public talks, articles, and videos including: - @Scale San Jose (“No shard left behind: APIs for massive parallel efficiency in Apache Beam”) - Strata + Hadoop World NYC (“Learn stream processing with Apache Beam”) - Paris Spark Meetup (“Introduction to Apache Beam”) - Hadoop Summit Melbourne (“Stream/Batch processing portable across on-prem (Spark, Flink) and Cloud with Apache Beam”) - Hadoop User Group Taipei (“Stream Processing with Beam and Google Cloud Dataflow”) - Data Science Lab London (“Apache Beam: Stream and Batch Processing; Unified and Portable!”) How has the project developed since the last report? Major developments on the project since last report include the following: * Second and third incubating release (0.2.0 and 0.3.0) and a release guide [1] * New DirectRunner support for testing streaming pipelines[2] * Continued improvements to the Flink, Spark, and Dataflow runners * Added support for new IO connectors, including MongoDB, Kinesis, and JDBC with Cassandra, MQTT support pending in pull requests * Addition of the Apache Apex runner on a feature branch, and continued work on the Apache Gearpump runner and Python SDK feature branches. [3] * Continued reorganization and refactoring of the project * Continued improvements to documentation and testing [1]: http://beam.incubator.apache.org/contribute/release-guide/ [2]: http://beam.incubator.apache.org/blog/2016/10/20/test-stream.html [3]: http://beam.incubator.apache.org/contribute/work-in- progress/#feature-branches Dates of last releases: * 2016/08/07 - 0.2.0-incubating * 2016/10/31 - 0.3.0-incubating When were the last committers or PMC members elected? The following committers were elected on 2016/10/20: * Thomas Weise * Jesse Anderson * Thomas Groh Signed-off-by: [ ](beam) Jean-Baptiste Onofre [ ](beam) Venkatesh Seetharam [ ](beam) Ted Dunning Shepherd/Mentor notes: -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
Re: Podling Report Reminder - November 2016
Thanks for the edits! Here is an amended proposal for a draft report: --- 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 Apex, Apache Spark, and Google Cloud Dataflow. Beam also brings SDKs in different languages, allowing users to easily implement their data integration processes. Beam has been incubating since 2016-02-01. The most important issue to address in the move towards graduation: 1. Make it easier for the Beam community to to learn, use, and grow by expanding and improving the Beam documentation, code samples, and the 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? * 441 closed/merged pull requests * High engagement on dev and user mailing lists (742 / 179 messages) * Several public talks, articles, and videos including: - @Scale San Jose (“No shard left behind: APIs for massive parallel efficiency in Apache Beam”) - Strata + Hadoop World NYC (“Learn stream processing with Apache Beam”) - Paris Spark Meetup (“Introduction to Apache Beam”) - Hadoop Summit Melbourne (“Stream/Batch processing portable across on-prem (Spark, Flink) and Cloud with Apache Beam”) - Hadoop User Group Taipei (“Stream Processing with Beam and Google Cloud Dataflow”) - Data Science Lab London (“Apache Beam: Stream and Batch Processing; Unified and Portable!”) How has the project developed since the last report? Major developments on the project since last report include the following: * Second and third incubating release (0.2.0 and 0.3.0) and a release guide [1] * New DirectRunner support for testing streaming pipelines[2] * Continued improvements to the Flink, Spark, and Dataflow runners * Added support for new IO connectors, including MongoDB, Kinesis, and JDBC with Cassandra, MQTT support pending in pull requests * Addition of the Apache Apex runner on a feature branch, and continued work on the Apache Gearpump runner and Python SDK feature branches. [3] * Continued reorganization and refactoring of the project * Continued improvements to documentation and testing [1]: http://beam.incubator.apache.org/contribute/release-guide/ [2]: http://beam.incubator.apache.org/blog/2016/10/20/test-stream.html [3]: http://beam.incubator.apache.org/contribute/work-in- progress/#feature-branches Dates of last releases: * 2016/08/07 - 0.2.0-incubating * 2016/10/31 - 0.3.0-incubating When were the last committers or PMC members elected? The following committers were elected on 2016/10/20: * Thomas Weise * Jesse Anderson * Thomas Groh Signed-off-by: [ ](beam) Jean-Baptiste Onofre [ ](beam) Venkatesh Seetharam [ ](beam) Ted Dunning Shepherd/Mentor notes: On Tue, Nov 1, 2016 at 10:09 PM, Jean-Baptiste Onofré wrote: > Hi James, > > it looks good to me. > > Just a minor thing regarding the releases, we just have to mention the > ones with did in the last quarter (no need to mention 0.1.0-incubating). > > Regards > JB > > > On 11/02/2016 12:12 AM, James Malone wrote: > >> Howdy, >> >> Sorry for being delayed; here is a proposal for our podling report! >> >> 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 Apex, >> 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. >> >> The most important issue to address in the move towards graduation: >> >> 1. Make it easier for the beam community to to learn, use, and grow by >> expanding and improving the Beam documentation, code samples, and the >> 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? >> * 441 closed/merged pull requests >> * High engagement on dev and user mailing lists (742 / 179 messages) >> * Several public talks, articles, and videos including: >> - @Scale San Jose (“No shard left behind: APIs for massive parallel >> efficiency”) >> - Strata + Hadoop World NYC (“Learn stream processing with Apache >> Beam”)
Re: Podling Report Reminder - November 2016
Hi James, it looks good to me. Just a minor thing regarding the releases, we just have to mention the ones with did in the last quarter (no need to mention 0.1.0-incubating). Regards JB On 11/02/2016 12:12 AM, James Malone wrote: Howdy, Sorry for being delayed; here is a proposal for our podling report! 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 Apex, 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. The most important issue to address in the move towards graduation: 1. Make it easier for the beam community to to learn, use, and grow by expanding and improving the Beam documentation, code samples, and the 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? * 441 closed/merged pull requests * High engagement on dev and user mailing lists (742 / 179 messages) * Several public talks, articles, and videos including: - @Scale San Jose (“No shard left behind: APIs for massive parallel efficiency”) - Strata + Hadoop World NYC (“Learn stream processing with Apache Beam”) - Paris Spark Meetup (“Introduction to Apache Beam”) - Hadoop Summit Melbourne (“Stream/Batch processing portable across on-prem (Spark, Flink) and Cloud with Apache Beam”) - Hadoop User Group Taipei (“Stream Processing with Beam and Google Cloud Dataflow”) - Data Science Lab London (“Apache Beam: Stream and Batch Processing; Unified and Portable!”) How has the project developed since the last report? Major developments on the project since last report include the following: * Second and third incubating release (0.2.0 and 0.3.0) and a release guide [1] * New DirectRunner support for testing streaming pipelines[2] * Continued improvements to the Flink, Spark, and Dataflow runners * Added support for new IO connectors, including MongoDB, Kinesis, and JDBC with Cassandra, MQTT support pending in pull requests * Addition of the Apache Apex runner on a feature branch, and continued work on the Apache Gearpump runner and Python SDK feature branches. [3] * Continued reorganization and refactoring of the project * Continued improvements to documentation and testing [1]: http://beam.incubator.apache.org/contribute/release-guide/ [2]: http://beam.incubator.apache.org/blog/2016/10/20/test-stream.html [3]: http://beam.incubator.apache.org/contribute/work-in-progress/#feature-branches Dates of last releases: * 2016/06/15 - 0.1.0-incubating * 2016/08/07 - 0.2.0-incubating * 2016/10/31 - 0.3.0-incubating When were the last committers or PMC members elected? The following committers were elected on 2016/10/20: * Thomas Weise * Jesse Anderson * Thomas Groh Signed-off-by: [ ](beam) Jean-Baptiste Onofre [ ](beam) Venkatesh Seetharam [ ](beam) Ted Dunning Shepherd/Mentor notes: On Mon, Oct 31, 2016 at 10:55 PM, Jean-Baptiste Onofré wrote: Hi James, Sorry to bother you again: do you have any update about the podling report (I checked on the incubator wiki and it's still empty) ? We would need a little time to review and sign. Please, let me know if I can help you on this. Thanks ! Regards JB On 10/27/2016 01:05 AM, James Malone wrote: Hello everyone! Unless anyone disagrees or wants to do it, I am happy to volunteer to draft this podling report for review before we submit it. I can get it done for a review this Friday (US-Pacific) if that works. Cheers! James On Wed, Oct 26, 2016 at 4:01 PM, 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, 16 November 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, November 02). 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
Podling Report Reminder - November 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, 16 November 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, November 02). 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/November2016 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 - November 2016
Minor suggestions inline: On Tue, Nov 1, 2016 at 4:12 PM, James Malone wrote: > Howdy, > > Sorry for being delayed; here is a proposal for our podling report! > > 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 Apex, > Apache Spark, and Google Cloud Dataflow (a cloud service). Beam also brings > alphabetize runners? strike "(a cloud service)"? > SDKs in different languages, allowing users to easily implement their data > integration processes. > > Beam has been incubating since 2016-02-01. > > The most important issue to address in the move towards graduation: > > 1. Make it easier for the beam community to to learn, use, and grow by > Beam > expanding and improving the Beam documentation, code samples, and the > 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? > * 441 closed/merged pull requests > * High engagement on dev and user mailing lists (742 / 179 messages) > * Several public talks, articles, and videos including: > - @Scale San Jose (“No shard left behind: APIs for massive parallel > efficiency”) > Title was actually: "No shard left behind: APIs for massive parallel efficiency in Apache Beam" > - Strata + Hadoop World NYC (“Learn stream processing with Apache > Beam”) > - Paris Spark Meetup (“Introduction to Apache Beam”) > - Hadoop Summit Melbourne (“Stream/Batch processing portable across > on-prem (Spark, Flink) and Cloud with Apache Beam”) > - Hadoop User Group Taipei (“Stream Processing with Beam and Google > Cloud Dataflow”) > - Data Science Lab London (“Apache Beam: Stream and Batch Processing; > Unified and Portable!”) > > How has the project developed since the last report? > Major developments on the project since last report include the following: > * Second and third incubating release (0.2.0 and 0.3.0) and a release guide > [1] > * New DirectRunner support for testing streaming pipelines[2] > * Continued improvements to the Flink, Spark, and Dataflow runners > * Added support for new IO connectors, including MongoDB, Kinesis, and JDBC > with Cassandra, MQTT support pending in pull requests > * Addition of the Apache Apex runner on a feature branch, and continued > work on the Apache Gearpump runner and Python SDK feature branches. [3] > * Continued reorganization and refactoring of the project > * Continued improvements to documentation and testing > > [1]: http://beam.incubator.apache.org/contribute/release-guide/ > [2]: http://beam.incubator.apache.org/blog/2016/10/20/test-stream.html > [3]: > http://beam.incubator.apache.org/contribute/work-in-progress > /#feature-branches > > > Dates of last releases: > * 2016/06/15 - 0.1.0-incubating > * 2016/08/07 - 0.2.0-incubating > * 2016/10/31 - 0.3.0-incubating > > When were the last committers or PMC members elected? > The following committers were elected on 2016/10/20: > * Thomas Weise > * Jesse Anderson > * Thomas Groh > alpha? > > Signed-off-by: > [ ](beam) Jean-Baptiste Onofre > [ ](beam) Venkatesh Seetharam > [ ](beam) Ted Dunning > > Shepherd/Mentor notes: > > On Mon, Oct 31, 2016 at 10:55 PM, Jean-Baptiste Onofré > wrote: > > > > Hi James, > > > > Sorry to bother you again: do you have any update about the podling > report (I checked on the incubator wiki and it's still empty) ? > > > > We would need a little time to review and sign. > > > > Please, let me know if I can help you on this. > > > > Thanks ! > > Regards > > JB > > > > On 10/27/2016 01:05 AM, James Malone wrote: > >> > >> Hello everyone! > >> > >> Unless anyone disagrees or wants to do it, I am happy to volunteer to > draft > >> this podling report for review before we submit it. I can get it done > for a > >> review this Friday (US-Pacific) if that works. > >> > >> Cheers! > >> > >> James > >> > >> On Wed, Oct 26, 2016 at 4:01 PM, 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, 16 November 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, November 02). > >>> > >>> Please submit your report with sufficient time to allow the Incubator > >>> PMC
Re: Podling Report Reminder - November 2016
Howdy, Sorry for being delayed; here is a proposal for our podling report! 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 Apex, 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. The most important issue to address in the move towards graduation: 1. Make it easier for the beam community to to learn, use, and grow by expanding and improving the Beam documentation, code samples, and the 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? * 441 closed/merged pull requests * High engagement on dev and user mailing lists (742 / 179 messages) * Several public talks, articles, and videos including: - @Scale San Jose (“No shard left behind: APIs for massive parallel efficiency”) - Strata + Hadoop World NYC (“Learn stream processing with Apache Beam”) - Paris Spark Meetup (“Introduction to Apache Beam”) - Hadoop Summit Melbourne (“Stream/Batch processing portable across on-prem (Spark, Flink) and Cloud with Apache Beam”) - Hadoop User Group Taipei (“Stream Processing with Beam and Google Cloud Dataflow”) - Data Science Lab London (“Apache Beam: Stream and Batch Processing; Unified and Portable!”) How has the project developed since the last report? Major developments on the project since last report include the following: * Second and third incubating release (0.2.0 and 0.3.0) and a release guide [1] * New DirectRunner support for testing streaming pipelines[2] * Continued improvements to the Flink, Spark, and Dataflow runners * Added support for new IO connectors, including MongoDB, Kinesis, and JDBC with Cassandra, MQTT support pending in pull requests * Addition of the Apache Apex runner on a feature branch, and continued work on the Apache Gearpump runner and Python SDK feature branches. [3] * Continued reorganization and refactoring of the project * Continued improvements to documentation and testing [1]: http://beam.incubator.apache.org/contribute/release-guide/ [2]: http://beam.incubator.apache.org/blog/2016/10/20/test-stream.html [3]: http://beam.incubator.apache.org/contribute/work-in-progress/#feature-branches Dates of last releases: * 2016/06/15 - 0.1.0-incubating * 2016/08/07 - 0.2.0-incubating * 2016/10/31 - 0.3.0-incubating When were the last committers or PMC members elected? The following committers were elected on 2016/10/20: * Thomas Weise * Jesse Anderson * Thomas Groh Signed-off-by: [ ](beam) Jean-Baptiste Onofre [ ](beam) Venkatesh Seetharam [ ](beam) Ted Dunning Shepherd/Mentor notes: On Mon, Oct 31, 2016 at 10:55 PM, Jean-Baptiste Onofré wrote: > > Hi James, > > Sorry to bother you again: do you have any update about the podling report (I checked on the incubator wiki and it's still empty) ? > > We would need a little time to review and sign. > > Please, let me know if I can help you on this. > > Thanks ! > Regards > JB > > On 10/27/2016 01:05 AM, James Malone wrote: >> >> Hello everyone! >> >> Unless anyone disagrees or wants to do it, I am happy to volunteer to draft >> this podling report for review before we submit it. I can get it done for a >> review this Friday (US-Pacific) if that works. >> >> Cheers! >> >> James >> >> On Wed, Oct 26, 2016 at 4:01 PM, 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, 16 November 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, November 02). >>> >>> 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 import
Re: Podling Report Reminder - November 2016
Hi James, Sorry to bother you again: do you have any update about the podling report (I checked on the incubator wiki and it's still empty) ? We would need a little time to review and sign. Please, let me know if I can help you on this. Thanks ! Regards JB On 10/27/2016 01:05 AM, James Malone wrote: Hello everyone! Unless anyone disagrees or wants to do it, I am happy to volunteer to draft this podling report for review before we submit it. I can get it done for a review this Friday (US-Pacific) if that works. Cheers! James On Wed, Oct 26, 2016 at 4:01 PM, 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, 16 November 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, November 02). 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/November2016 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
Podling Report Reminder - November 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, 16 November 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, November 02). 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/November2016 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 - November 2016
Hi James, any update about the podling report ? Can I help you on this ? Thanks ! Regards JB On 10/27/2016 01:05 AM, James Malone wrote: Hello everyone! Unless anyone disagrees or wants to do it, I am happy to volunteer to draft this podling report for review before we submit it. I can get it done for a review this Friday (US-Pacific) if that works. Cheers! James On Wed, Oct 26, 2016 at 4:01 PM, 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, 16 November 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, November 02). 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/November2016 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
Podling Report Reminder - November 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, 16 November 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, November 02). 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/November2016 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 - November 2016
Perfect. Thanks James ! Regards JB On Oct 27, 2016, 01:05, at 01:05, James Malone wrote: >Hello everyone! > >Unless anyone disagrees or wants to do it, I am happy to volunteer to >draft >this podling report for review before we submit it. I can get it done >for a >review this Friday (US-Pacific) if that works. > >Cheers! > >James > >On Wed, Oct 26, 2016 at 4:01 PM, 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, 16 November 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, November 02). >> >> 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/November2016 >> >> 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 - November 2016
Hello everyone! Unless anyone disagrees or wants to do it, I am happy to volunteer to draft this podling report for review before we submit it. I can get it done for a review this Friday (US-Pacific) if that works. Cheers! James On Wed, Oct 26, 2016 at 4:01 PM, 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, 16 November 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, November 02). > > 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/November2016 > > 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 - November 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, 16 November 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, November 02). 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/November2016 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 - November 2016
Hi guys @James do you want to prepare this podling report ? I will review. Let me know if you need any help. Thanks Regards JB On Oct 25, 2016, 02:02, at 02:02, johndam...@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, 16 November 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, November 02). > >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/November2016 > >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 - November 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, 16 November 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, November 02). 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/November2016 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
