You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@streampipes.apache.org by Patrick Wiener <wi...@apache.org> on 2020/06/01 21:06:05 UTC

Re: Podling Streampipes Report Reminder - June 2020

Hi all,

I prepared a first draft for the upcoming report (due on Wed, June 03).

It would be good if you could check the report and provide me with some feedback:

## StreamPipes

  StreamPipes is a self-service (Industrial) IoT toolbox to enable non-
  technical users to connect, analyze and explore (Industrial) IoT data
  streams.

  StreamPipes has been incubating since 2019-11-11.

### Three most important unfinished issues to address before graduating:

  1. Multiple Apache Releases
  2. Grow the developer community
  3. Attract more users

### Are there any issues that the IPMC or ASF Board need to be aware of?

  There are no issues right now.

### How has the community developed since the last report?

  In the past three months, the community developed rather well: New users
  appeared on the mailing lists, and we were able to elect the first
  external committers. The mailing list activity has increased and many 
  discussions on development-related tasks were done on the developer 
  mailing list. Overall, we feel that the community is more and more 
  following the Apache way.

  Some specific community development activities include:
  - We updated the wiki with developer information, getting started guides
    and step-by-step manuals for release management (see
    https://s.apache.org/ocz7t)
  - Updated website to include better overview of existing pipeline elements
  - Intensified work with manufacturing company to use StreamPipes for IIoT
    analytics
  - We published a blog post on how to run StreamPipes on Kubernetes, we now
    plan to publish blog posts at regular intervals
  - Added "communication channels & strategy" page in the wiki and gathered
    potential communication channels in close exchange with our mentors
    planning to intensify community growth
  - Number of Twitter followers increased (last report: 103, currently: 128)
  - Number of Github stars increased (last report: 109, currently: 143)

### How has the project developed since the last report?

  - We successfully released our first official Apache release (version
    0.66.0) including several improvements (see release notes
    https://s.apache.org/2grsk), to name the most prominent changes:
    completely new dashboard and notification design in UI, more pipeline 
    elements and improved connectors  
  - Many new pipeline elements have been added by newly elected committers
  - Both documentation and website were improved in order to increase the
    adoption of Apache StreamPipes and grow the user base

  In the next month, we plan to add better support for edge computing and
  improve the UI.

### How would you assess the podling's maturity?
Please feel free to add your own commentary.

  - [ ] Initial setup
  - [ ] Working towards first release
  - [x] Community building
  - [ ] Nearing graduation
  - [ ] Other:

### Date of last release:

  2020-05-19 (Version 0.66.0)

### When were the last committers or PPMC members elected?

  Four new committers were elected and joined the team since the last report
  aiding in contributing/maturing the project.

  - Florian Micklich (2020-03-26)
  - Daniel Ebi (2020-05-12)
  - Felix John (2020-05-12)
  - Grainier Perera (2020-05-22)

### Have your mentors been helpful and responsive?
Are things falling through the cracks? If so, please list any
open issues that need to be addressed.

  Our mentors provided very good support in preparing and performing our
  first Apache release. We would like to thank them for very helpful advice,
  also for some licensing questions we had on the list.

### Is the PPMC managing the podling's brand / trademarks?
Are 3rd parties respecting and correctly using the podlings
name and brand? If not what actions has the PPMC taken to
correct this? Has the VP, Brand approved the project name?

  Yes, we started to prepare a wiki page to develop a communication
  strategy, which also includes brand management. The next step is to 
  create a new logo that will be voted on by the community. We are 
  constantly monitoring the usage of the Apache StreamPipes name in 
  external websites and posts.

### Signed-off-by:

  - [ ] (streampipes) Christofer Dutz
     Comments:
  - [ ] (streampipes) Jean-Baptiste Onofré
     Comments:
  - [ ] (streampipes) Julian Feinauer
     Comments:
  - [ ] (streampipes) Justin Mclean
     Comments:
  - [ ] (streampipes) Kenneth Knowles
     Comments:

### IPMC/Shepherd notes:


> Am 28.05.2020 um 00:30 schrieb jmclean@apache.org:
> 
> 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 June 2020.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, June 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.
> 
> Candidate names should not be made public before people are actually
> elected, so please do not include the names of potential committers or
> PPMC members in your report.
> 
> 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.
> *   How does the podling rate their own maturity.
> 
> This should be appended to the Incubator Wiki page at:
> 
> https://cwiki.apache.org/confluence/display/INCUBATOR/June2020
> 
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
> 
> Note: The format of the report has changed to use markdown.
> 
> 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 Streampipes Report Reminder - June 2020

Posted by Patrick Wiener <wi...@apache.org>.
Hi Philipp,

good point. I'll add it.

Patrick

On 2020/06/02 06:57:56, Philipp Zehnder <ze...@fzi.de> wrote: 
> Hi Patrick,
> 
> thanks a lot, the report looks good.
> We can also mention the webinar which is now on YouTube.
> 
> Philipp
> 
> 
> > On 1. Jun 2020, at 23:06, Patrick Wiener <wi...@apache.org> wrote:
> > 
> > Hi all,
> > 
> > I prepared a first draft for the upcoming report (due on Wed, June 03).
> > 
> > It would be good if you could check the report and provide me with some feedback:
> > 
> > ## StreamPipes
> > 
> >  StreamPipes is a self-service (Industrial) IoT toolbox to enable non-
> >  technical users to connect, analyze and explore (Industrial) IoT data
> >  streams.
> > 
> >  StreamPipes has been incubating since 2019-11-11.
> > 
> > ### Three most important unfinished issues to address before graduating:
> > 
> >  1. Multiple Apache Releases
> >  2. Grow the developer community
> >  3. Attract more users
> > 
> > ### Are there any issues that the IPMC or ASF Board need to be aware of?
> > 
> >  There are no issues right now.
> > 
> > ### How has the community developed since the last report?
> > 
> >  In the past three months, the community developed rather well: New users
> >  appeared on the mailing lists, and we were able to elect the first
> >  external committers. The mailing list activity has increased and many 
> >  discussions on development-related tasks were done on the developer 
> >  mailing list. Overall, we feel that the community is more and more 
> >  following the Apache way.
> > 
> >  Some specific community development activities include:
> >  - We updated the wiki with developer information, getting started guides
> >    and step-by-step manuals for release management (see
> >    https://s.apache.org/ocz7t)
> >  - Updated website to include better overview of existing pipeline elements
> >  - Intensified work with manufacturing company to use StreamPipes for IIoT
> >    analytics
> >  - We published a blog post on how to run StreamPipes on Kubernetes, we now
> >    plan to publish blog posts at regular intervals
> >  - Added "communication channels & strategy" page in the wiki and gathered
> >    potential communication channels in close exchange with our mentors
> >    planning to intensify community growth
> >  - Number of Twitter followers increased (last report: 103, currently: 128)
> >  - Number of Github stars increased (last report: 109, currently: 143)
> > 
> > ### How has the project developed since the last report?
> > 
> >  - We successfully released our first official Apache release (version
> >    0.66.0) including several improvements (see release notes
> >    https://s.apache.org/2grsk), to name the most prominent changes:
> >    completely new dashboard and notification design in UI, more pipeline 
> >    elements and improved connectors  
> >  - Many new pipeline elements have been added by newly elected committers
> >  - Both documentation and website were improved in order to increase the
> >    adoption of Apache StreamPipes and grow the user base
> > 
> >  In the next month, we plan to add better support for edge computing and
> >  improve the UI.
> > 
> > ### How would you assess the podling's maturity?
> > Please feel free to add your own commentary.
> > 
> >  - [ ] Initial setup
> >  - [ ] Working towards first release
> >  - [x] Community building
> >  - [ ] Nearing graduation
> >  - [ ] Other:
> > 
> > ### Date of last release:
> > 
> >  2020-05-19 (Version 0.66.0)
> > 
> > ### When were the last committers or PPMC members elected?
> > 
> >  Four new committers were elected and joined the team since the last report
> >  aiding in contributing/maturing the project.
> > 
> >  - Florian Micklich (2020-03-26)
> >  - Daniel Ebi (2020-05-12)
> >  - Felix John (2020-05-12)
> >  - Grainier Perera (2020-05-22)
> > 
> > ### Have your mentors been helpful and responsive?
> > Are things falling through the cracks? If so, please list any
> > open issues that need to be addressed.
> > 
> >  Our mentors provided very good support in preparing and performing our
> >  first Apache release. We would like to thank them for very helpful advice,
> >  also for some licensing questions we had on the list.
> > 
> > ### Is the PPMC managing the podling's brand / trademarks?
> > Are 3rd parties respecting and correctly using the podlings
> > name and brand? If not what actions has the PPMC taken to
> > correct this? Has the VP, Brand approved the project name?
> > 
> >  Yes, we started to prepare a wiki page to develop a communication
> >  strategy, which also includes brand management. The next step is to 
> >  create a new logo that will be voted on by the community. We are 
> >  constantly monitoring the usage of the Apache StreamPipes name in 
> >  external websites and posts.
> > 
> > ### Signed-off-by:
> > 
> >  - [ ] (streampipes) Christofer Dutz
> >     Comments:
> >  - [ ] (streampipes) Jean-Baptiste Onofré
> >     Comments:
> >  - [ ] (streampipes) Julian Feinauer
> >     Comments:
> >  - [ ] (streampipes) Justin Mclean
> >     Comments:
> >  - [ ] (streampipes) Kenneth Knowles
> >     Comments:
> > 
> > ### IPMC/Shepherd notes:
> > 
> > 
> >> Am 28.05.2020 um 00:30 schrieb jmclean@apache.org:
> >> 
> >> 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 June 2020.
> >> The report for your podling will form a part of the Incubator PMC
> >> report. The Incubator PMC requires your report to be submitted 2 weeks
> >> before the board meeting, to allow sufficient time for review and
> >> submission (Wed, June 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.
> >> 
> >> Candidate names should not be made public before people are actually
> >> elected, so please do not include the names of potential committers or
> >> PPMC members in your report.
> >> 
> >> 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.
> >> *   How does the podling rate their own maturity.
> >> 
> >> This should be appended to the Incubator Wiki page at:
> >> 
> >> https://cwiki.apache.org/confluence/display/INCUBATOR/June2020
> >> 
> >> Note: This is manually populated. You may need to wait a little before
> >> this page is created from a template.
> >> 
> >> Note: The format of the report has changed to use markdown.
> >> 
> >> 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
> > 
> 
> .........................................................
> M. Sc. Philipp Zehnder
> Wissenschaftlicher Mitarbeiter | Research Scientist
> Information Process Engineering (IPE)
>  
> FZI Forschungszentrum Informatik
> Haid-und-Neu-Str. 10–14 
> 76131 Karlsruhe, Germany
> Tel.: +49 721 9654-805
> Fax: +49 721 9654-806
> 
> zehnder@fzi.de <ma...@fzi.de>
> https://www.fzi.de/mitarbeiter/philipp-zehnder
>  
> .........................................................
> FZI Forschungszentrum Informatik
> Stiftung des bürgerlichen Rechts
> Stiftung Az: 14-0563.1 Regierungspräsidium Karlsruhe
> Vorstand: Prof. Dr. Andreas Oberweis, Jan Wiesenberger, Prof. Dr.-Ing. J. Marius Zöllner
> Vorsitzender des Kuratoriums: Ministerialdirigent Günther Leßnerkraus
> .........................................................
> 
> 

Re: Podling Streampipes Report Reminder - June 2020

Posted by Philipp Zehnder <ze...@fzi.de>.
Hi Patrick,

thanks a lot, the report looks good.
We can also mention the webinar which is now on YouTube.

Philipp


> On 1. Jun 2020, at 23:06, Patrick Wiener <wi...@apache.org> wrote:
> 
> Hi all,
> 
> I prepared a first draft for the upcoming report (due on Wed, June 03).
> 
> It would be good if you could check the report and provide me with some feedback:
> 
> ## StreamPipes
> 
>  StreamPipes is a self-service (Industrial) IoT toolbox to enable non-
>  technical users to connect, analyze and explore (Industrial) IoT data
>  streams.
> 
>  StreamPipes has been incubating since 2019-11-11.
> 
> ### Three most important unfinished issues to address before graduating:
> 
>  1. Multiple Apache Releases
>  2. Grow the developer community
>  3. Attract more users
> 
> ### Are there any issues that the IPMC or ASF Board need to be aware of?
> 
>  There are no issues right now.
> 
> ### How has the community developed since the last report?
> 
>  In the past three months, the community developed rather well: New users
>  appeared on the mailing lists, and we were able to elect the first
>  external committers. The mailing list activity has increased and many 
>  discussions on development-related tasks were done on the developer 
>  mailing list. Overall, we feel that the community is more and more 
>  following the Apache way.
> 
>  Some specific community development activities include:
>  - We updated the wiki with developer information, getting started guides
>    and step-by-step manuals for release management (see
>    https://s.apache.org/ocz7t)
>  - Updated website to include better overview of existing pipeline elements
>  - Intensified work with manufacturing company to use StreamPipes for IIoT
>    analytics
>  - We published a blog post on how to run StreamPipes on Kubernetes, we now
>    plan to publish blog posts at regular intervals
>  - Added "communication channels & strategy" page in the wiki and gathered
>    potential communication channels in close exchange with our mentors
>    planning to intensify community growth
>  - Number of Twitter followers increased (last report: 103, currently: 128)
>  - Number of Github stars increased (last report: 109, currently: 143)
> 
> ### How has the project developed since the last report?
> 
>  - We successfully released our first official Apache release (version
>    0.66.0) including several improvements (see release notes
>    https://s.apache.org/2grsk), to name the most prominent changes:
>    completely new dashboard and notification design in UI, more pipeline 
>    elements and improved connectors  
>  - Many new pipeline elements have been added by newly elected committers
>  - Both documentation and website were improved in order to increase the
>    adoption of Apache StreamPipes and grow the user base
> 
>  In the next month, we plan to add better support for edge computing and
>  improve the UI.
> 
> ### How would you assess the podling's maturity?
> Please feel free to add your own commentary.
> 
>  - [ ] Initial setup
>  - [ ] Working towards first release
>  - [x] Community building
>  - [ ] Nearing graduation
>  - [ ] Other:
> 
> ### Date of last release:
> 
>  2020-05-19 (Version 0.66.0)
> 
> ### When were the last committers or PPMC members elected?
> 
>  Four new committers were elected and joined the team since the last report
>  aiding in contributing/maturing the project.
> 
>  - Florian Micklich (2020-03-26)
>  - Daniel Ebi (2020-05-12)
>  - Felix John (2020-05-12)
>  - Grainier Perera (2020-05-22)
> 
> ### Have your mentors been helpful and responsive?
> Are things falling through the cracks? If so, please list any
> open issues that need to be addressed.
> 
>  Our mentors provided very good support in preparing and performing our
>  first Apache release. We would like to thank them for very helpful advice,
>  also for some licensing questions we had on the list.
> 
> ### Is the PPMC managing the podling's brand / trademarks?
> Are 3rd parties respecting and correctly using the podlings
> name and brand? If not what actions has the PPMC taken to
> correct this? Has the VP, Brand approved the project name?
> 
>  Yes, we started to prepare a wiki page to develop a communication
>  strategy, which also includes brand management. The next step is to 
>  create a new logo that will be voted on by the community. We are 
>  constantly monitoring the usage of the Apache StreamPipes name in 
>  external websites and posts.
> 
> ### Signed-off-by:
> 
>  - [ ] (streampipes) Christofer Dutz
>     Comments:
>  - [ ] (streampipes) Jean-Baptiste Onofré
>     Comments:
>  - [ ] (streampipes) Julian Feinauer
>     Comments:
>  - [ ] (streampipes) Justin Mclean
>     Comments:
>  - [ ] (streampipes) Kenneth Knowles
>     Comments:
> 
> ### IPMC/Shepherd notes:
> 
> 
>> Am 28.05.2020 um 00:30 schrieb jmclean@apache.org:
>> 
>> 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 June 2020.
>> The report for your podling will form a part of the Incubator PMC
>> report. The Incubator PMC requires your report to be submitted 2 weeks
>> before the board meeting, to allow sufficient time for review and
>> submission (Wed, June 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.
>> 
>> Candidate names should not be made public before people are actually
>> elected, so please do not include the names of potential committers or
>> PPMC members in your report.
>> 
>> 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.
>> *   How does the podling rate their own maturity.
>> 
>> This should be appended to the Incubator Wiki page at:
>> 
>> https://cwiki.apache.org/confluence/display/INCUBATOR/June2020
>> 
>> Note: This is manually populated. You may need to wait a little before
>> this page is created from a template.
>> 
>> Note: The format of the report has changed to use markdown.
>> 
>> 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
> 

.........................................................
M. Sc. Philipp Zehnder
Wissenschaftlicher Mitarbeiter | Research Scientist
Information Process Engineering (IPE)
 
FZI Forschungszentrum Informatik
Haid-und-Neu-Str. 10–14 
76131 Karlsruhe, Germany
Tel.: +49 721 9654-805
Fax: +49 721 9654-806

zehnder@fzi.de <ma...@fzi.de>
https://www.fzi.de/mitarbeiter/philipp-zehnder
 
.........................................................
FZI Forschungszentrum Informatik
Stiftung des bürgerlichen Rechts
Stiftung Az: 14-0563.1 Regierungspräsidium Karlsruhe
Vorstand: Prof. Dr. Andreas Oberweis, Jan Wiesenberger, Prof. Dr.-Ing. J. Marius Zöllner
Vorsitzender des Kuratoriums: Ministerialdirigent Günther Leßnerkraus
.........................................................


Re: Podling Streampipes Report Reminder - June 2020

Posted by Patrick Wiener <wi...@apache.org>.
alright - then I add it to the Incubator Wiki.

Patrick

> Am 02.06.2020 um 19:36 schrieb Dominik Riemer <ri...@apache.org>:
> 
> Hi Patrick,
> 
> sounds good, I don't have anything to add!
> 
> Dominik
> 
> -----Original Message-----
> From: Patrick Wiener <wi...@apache.org> 
> Sent: Monday, June 1, 2020 11:06 PM
> To: dev@streampipes.apache.org
> Subject: Re: Podling Streampipes Report Reminder - June 2020
> 
> Hi all,
> 
> I prepared a first draft for the upcoming report (due on Wed, June 03).
> 
> It would be good if you could check the report and provide me with some feedback:
> 
> ## StreamPipes
> 
>  StreamPipes is a self-service (Industrial) IoT toolbox to enable non-
>  technical users to connect, analyze and explore (Industrial) IoT data
>  streams.
> 
>  StreamPipes has been incubating since 2019-11-11.
> 
> ### Three most important unfinished issues to address before graduating:
> 
>  1. Multiple Apache Releases
>  2. Grow the developer community
>  3. Attract more users
> 
> ### Are there any issues that the IPMC or ASF Board need to be aware of?
> 
>  There are no issues right now.
> 
> ### How has the community developed since the last report?
> 
>  In the past three months, the community developed rather well: New users
>  appeared on the mailing lists, and we were able to elect the first
>  external committers. The mailing list activity has increased and many
>  discussions on development-related tasks were done on the developer
>  mailing list. Overall, we feel that the community is more and more
>  following the Apache way.
> 
>  Some specific community development activities include:
>  - We updated the wiki with developer information, getting started guides
>    and step-by-step manuals for release management (see
>    https://s.apache.org/ocz7t)
>  - Updated website to include better overview of existing pipeline elements
>  - Intensified work with manufacturing company to use StreamPipes for IIoT
>    analytics
>  - We published a blog post on how to run StreamPipes on Kubernetes, we now
>    plan to publish blog posts at regular intervals
>  - Added "communication channels & strategy" page in the wiki and gathered
>    potential communication channels in close exchange with our mentors
>    planning to intensify community growth
>  - Number of Twitter followers increased (last report: 103, currently: 128)
>  - Number of Github stars increased (last report: 109, currently: 143)
> 
> ### How has the project developed since the last report?
> 
>  - We successfully released our first official Apache release (version
>    0.66.0) including several improvements (see release notes
>    https://s.apache.org/2grsk), to name the most prominent changes:
>    completely new dashboard and notification design in UI, more pipeline 
>    elements and improved connectors
>  - Many new pipeline elements have been added by newly elected committers
>  - Both documentation and website were improved in order to increase the
>    adoption of Apache StreamPipes and grow the user base
> 
>  In the next month, we plan to add better support for edge computing and
>  improve the UI.
> 
> ### How would you assess the podling's maturity?
> Please feel free to add your own commentary.
> 
>  - [ ] Initial setup
>  - [ ] Working towards first release
>  - [x] Community building
>  - [ ] Nearing graduation
>  - [ ] Other:
> 
> ### Date of last release:
> 
>  2020-05-19 (Version 0.66.0)
> 
> ### When were the last committers or PPMC members elected?
> 
>  Four new committers were elected and joined the team since the last report
>  aiding in contributing/maturing the project.
> 
>  - Florian Micklich (2020-03-26)
>  - Daniel Ebi (2020-05-12)
>  - Felix John (2020-05-12)
>  - Grainier Perera (2020-05-22)
> 
> ### Have your mentors been helpful and responsive?
> Are things falling through the cracks? If so, please list any open issues that need to be addressed.
> 
>  Our mentors provided very good support in preparing and performing our
>  first Apache release. We would like to thank them for very helpful advice,
>  also for some licensing questions we had on the list.
> 
> ### Is the PPMC managing the podling's brand / trademarks?
> Are 3rd parties respecting and correctly using the podlings name and brand? If not what actions has the PPMC taken to correct this? Has the VP, Brand approved the project name?
> 
>  Yes, we started to prepare a wiki page to develop a communication
>  strategy, which also includes brand management. The next step is to
>  create a new logo that will be voted on by the community. We are
>  constantly monitoring the usage of the Apache StreamPipes name in
>  external websites and posts.
> 
> ### Signed-off-by:
> 
>  - [ ] (streampipes) Christofer Dutz
>     Comments:
>  - [ ] (streampipes) Jean-Baptiste Onofré
>     Comments:
>  - [ ] (streampipes) Julian Feinauer
>     Comments:
>  - [ ] (streampipes) Justin Mclean
>     Comments:
>  - [ ] (streampipes) Kenneth Knowles
>     Comments:
> 
> ### IPMC/Shepherd notes:
> 
> 
>> Am 28.05.2020 um 00:30 schrieb jmclean@apache.org:
>> 
>> 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 June 2020.
>> The report for your podling will form a part of the Incubator PMC 
>> report. The Incubator PMC requires your report to be submitted 2 weeks 
>> before the board meeting, to allow sufficient time for review and 
>> submission (Wed, June 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.
>> 
>> Candidate names should not be made public before people are actually 
>> elected, so please do not include the names of potential committers or 
>> PPMC members in your report.
>> 
>> 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.
>> *   How does the podling rate their own maturity.
>> 
>> This should be appended to the Incubator Wiki page at:
>> 
>> https://cwiki.apache.org/confluence/display/INCUBATOR/June2020
>> 
>> Note: This is manually populated. You may need to wait a little before 
>> this page is created from a template.
>> 
>> Note: The format of the report has changed to use markdown.
>> 
>> 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 Streampipes Report Reminder - June 2020

Posted by Dominik Riemer <ri...@apache.org>.
Hi Patrick,

sounds good, I don't have anything to add!

Dominik

-----Original Message-----
From: Patrick Wiener <wi...@apache.org> 
Sent: Monday, June 1, 2020 11:06 PM
To: dev@streampipes.apache.org
Subject: Re: Podling Streampipes Report Reminder - June 2020

Hi all,

I prepared a first draft for the upcoming report (due on Wed, June 03).

It would be good if you could check the report and provide me with some feedback:

## StreamPipes

  StreamPipes is a self-service (Industrial) IoT toolbox to enable non-
  technical users to connect, analyze and explore (Industrial) IoT data
  streams.

  StreamPipes has been incubating since 2019-11-11.

### Three most important unfinished issues to address before graduating:

  1. Multiple Apache Releases
  2. Grow the developer community
  3. Attract more users

### Are there any issues that the IPMC or ASF Board need to be aware of?

  There are no issues right now.

### How has the community developed since the last report?

  In the past three months, the community developed rather well: New users
  appeared on the mailing lists, and we were able to elect the first
  external committers. The mailing list activity has increased and many
  discussions on development-related tasks were done on the developer
  mailing list. Overall, we feel that the community is more and more
  following the Apache way.

  Some specific community development activities include:
  - We updated the wiki with developer information, getting started guides
    and step-by-step manuals for release management (see
    https://s.apache.org/ocz7t)
  - Updated website to include better overview of existing pipeline elements
  - Intensified work with manufacturing company to use StreamPipes for IIoT
    analytics
  - We published a blog post on how to run StreamPipes on Kubernetes, we now
    plan to publish blog posts at regular intervals
  - Added "communication channels & strategy" page in the wiki and gathered
    potential communication channels in close exchange with our mentors
    planning to intensify community growth
  - Number of Twitter followers increased (last report: 103, currently: 128)
  - Number of Github stars increased (last report: 109, currently: 143)

### How has the project developed since the last report?

  - We successfully released our first official Apache release (version
    0.66.0) including several improvements (see release notes
    https://s.apache.org/2grsk), to name the most prominent changes:
    completely new dashboard and notification design in UI, more pipeline 
    elements and improved connectors
  - Many new pipeline elements have been added by newly elected committers
  - Both documentation and website were improved in order to increase the
    adoption of Apache StreamPipes and grow the user base

  In the next month, we plan to add better support for edge computing and
  improve the UI.

### How would you assess the podling's maturity?
Please feel free to add your own commentary.

  - [ ] Initial setup
  - [ ] Working towards first release
  - [x] Community building
  - [ ] Nearing graduation
  - [ ] Other:

### Date of last release:

  2020-05-19 (Version 0.66.0)

### When were the last committers or PPMC members elected?

  Four new committers were elected and joined the team since the last report
  aiding in contributing/maturing the project.

  - Florian Micklich (2020-03-26)
  - Daniel Ebi (2020-05-12)
  - Felix John (2020-05-12)
  - Grainier Perera (2020-05-22)

### Have your mentors been helpful and responsive?
Are things falling through the cracks? If so, please list any open issues that need to be addressed.

  Our mentors provided very good support in preparing and performing our
  first Apache release. We would like to thank them for very helpful advice,
  also for some licensing questions we had on the list.

### Is the PPMC managing the podling's brand / trademarks?
Are 3rd parties respecting and correctly using the podlings name and brand? If not what actions has the PPMC taken to correct this? Has the VP, Brand approved the project name?

  Yes, we started to prepare a wiki page to develop a communication
  strategy, which also includes brand management. The next step is to
  create a new logo that will be voted on by the community. We are
  constantly monitoring the usage of the Apache StreamPipes name in
  external websites and posts.

### Signed-off-by:

  - [ ] (streampipes) Christofer Dutz
     Comments:
  - [ ] (streampipes) Jean-Baptiste Onofré
     Comments:
  - [ ] (streampipes) Julian Feinauer
     Comments:
  - [ ] (streampipes) Justin Mclean
     Comments:
  - [ ] (streampipes) Kenneth Knowles
     Comments:

### IPMC/Shepherd notes:


> Am 28.05.2020 um 00:30 schrieb jmclean@apache.org:
> 
> 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 June 2020.
> The report for your podling will form a part of the Incubator PMC 
> report. The Incubator PMC requires your report to be submitted 2 weeks 
> before the board meeting, to allow sufficient time for review and 
> submission (Wed, June 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.
> 
> Candidate names should not be made public before people are actually 
> elected, so please do not include the names of potential committers or 
> PPMC members in your report.
> 
> 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.
> *   How does the podling rate their own maturity.
> 
> This should be appended to the Incubator Wiki page at:
> 
> https://cwiki.apache.org/confluence/display/INCUBATOR/June2020
> 
> Note: This is manually populated. You may need to wait a little before 
> this page is created from a template.
> 
> Note: The format of the report has changed to use markdown.
> 
> 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