[VOTE] Apache StreamPipes 0.95.0 RC2 release

[Dominik Riemer]

Hi,



Apache StreamPipes 0.95.0 RC2 has been staged and it's time to vote on 
accepting it for release.

Voting will be open for at least 72 hours.

A minimum of 3 binding +1 votes and more binding +1 than binding -1 are 
required to pass, but everyone is welcome to vote!



One artifact is relevant for this vote:



streampipes, staged at [1], available in Nexus at [2], release tag: 
release/0.95.0, hash for the release tag: 
30cbd0bee6afb63e9378b76e46b89790dc6e5e32



Per [3] "Before voting +1, PMC members are required to download the signed 
source code package, compile it as provided, and test the resulting executable 
on their own platform, along with also verifying that the package meets the 
requirements of the ASF policy on releases."



A release validation guide is available at [4]. The KEYS file is available at 
[5]



[ ] +1 accept (indicate what you validated - e.g. performed the checklist at 
the end of [4]) [ ] -1 reject (explanation required)



Thanks for taking your time for validating this release!





[1] https://dist.apache.org/repos/dist/dev/streampipes/0.95.0/rc2/

[2] https://repository.apache.org/content/repositories/orgapachestreampipes-1030

[3] https://www.apache.org/dev/release.html#approving-a-release

[4] https://cwiki.apache.org/confluence/display/STREAMPIPES/Validating+a+release

[5] https://downloads.apache.org/streampipes/KEYS

Re: [VOTE] Apache StreamPipes 0.95.0 RC1 release

[Dominik Riemer]

Hi,
sorry, but I have to cancel the release vote due to a bug in the pipeline 
editor validation.

I'll work on the issue and prepare another RC soon.

Dominik

On 2024/06/02 19:31:21 Dominik Riemer wrote:
> Hi,
> 
> Apache StreamPipes 0.95.0 has been staged and it's time to vote on accepting 
> it for release. 
> Voting will be open for at least 72 hours. 
> A minimum of 3 binding +1 votes and more binding +1 than binding -1 are 
> required to pass, but everyone is welcome to vote! 
> 
> One artifact is relevant for this vote: 
> 
> streampipes, staged at [1], available in Nexus at [2], release tag: 
> release/0.95.0, hash for the release tag: 
> 51f64bf45bfb3c2e007613016f5da565ff314bba
> 
> Per [3] "Before voting +1, PMC members are required to download the signed 
> source code package, 
> compile it as provided, and test the resulting executable on their own 
> platform, 
> along with also verifying that the package meets the requirements of the ASF 
> policy on releases." 
> 
> A release validation guide is available at [4]. The KEYS file is available at 
> [5] 
> 
> [ ] +1 accept (indicate what you validated - e.g. performed the checklist at 
> the end of [4]) 
> [ ] -1 reject (explanation required) 
> 
> Thanks for taking your time for validating this release!
> 
> 
> [1] https://dist.apache.org/repos/dist/dev/streampipes/0.95.0/rc1/
> [2] 
> https://repository.apache.org/content/repositories/orgapachestreampipes-1029
> [3] https://www.apache.org/dev/release.html#approving-a-release 
> [4] 
> https://cwiki.apache.org/confluence/display/STREAMPIPES/Validating+a+release 
> [5] https://downloads.apache.org/streampipes/KEYS
> 

[VOTE] Apache StreamPipes 0.95.0 RC1 release

[Dominik Riemer]

Hi,

Apache StreamPipes 0.95.0 has been staged and it's time to vote on accepting it 
for release. 
Voting will be open for at least 72 hours. 
A minimum of 3 binding +1 votes and more binding +1 than binding -1 are 
required to pass, but everyone is welcome to vote! 

One artifact is relevant for this vote: 

streampipes, staged at [1], available in Nexus at [2], release tag: 
release/0.95.0, hash for the release tag: 
51f64bf45bfb3c2e007613016f5da565ff314bba

Per [3] "Before voting +1, PMC members are required to download the signed 
source code package, 
compile it as provided, and test the resulting executable on their own 
platform, 
along with also verifying that the package meets the requirements of the ASF 
policy on releases." 

A release validation guide is available at [4]. The KEYS file is available at 
[5] 

[ ] +1 accept (indicate what you validated - e.g. performed the checklist at 
the end of [4]) 
[ ] -1 reject (explanation required) 

Thanks for taking your time for validating this release!


[1] https://dist.apache.org/repos/dist/dev/streampipes/0.95.0/rc1/
[2] https://repository.apache.org/content/repositories/orgapachestreampipes-1029
[3] https://www.apache.org/dev/release.html#approving-a-release 
[4] 
https://cwiki.apache.org/confluence/display/STREAMPIPES/Validating+a+release 
[5] https://downloads.apache.org/streampipes/KEYS

Re: Testing Release 0.95.0

[Dominik Riemer]

Hi Tim,
thank you!
I also tested the release branch and don't see any remaining issues which are 
required for the next release in my opinion.
Do you see any blockers for the release?

Cheers
Dominik

On 2024/05/07 07:18:38 Tim Bossenmaier wrote:
> Hi all,
> 
> as discussed, I have created the release branch for our upcoming version
> 0.95.0 [1].
> 
> In case there is anything left out that should be part of this release,
> please let me know.
> In this case, I'll take care of bringing these changes appropriately to the
> release branch.
> 
> Please start testing and validating the release branch.
> 
> If you find any issues, please post them to the wiki [2] or the mailing
> list.
> 
> Cheers,
> Tim
> 
> [1] https://lists.apache.org/thread/vz0db9x321wfgf0bqkd2gotnjbsgmxk5
> [2] 
> https://cwiki.apache.org/confluence/display/STREAMPIPES/0.95.0-Pre-Release-Checklist
> 

RE: [DRAFT] Mai Board report

[Dominik Riemer]

+1

Thanks for creating the report!
Dominik


-Original Message-
From: Philipp Zehnder  
Sent: Monday, May 6, 2024 4:43 PM
To: dev@streampipes.apache.org
Subject: [DRAFT] Mai Board report

Hi all,

here is the draft for our board report.
Please let me know if you have any additional points to add.

## Description:
The mission of Apache StreamPipes is the creation and maintenance of software 
related to a self-service Industrial IoT toolbox which enables non-technical 
users to connect, analyze and explore IoT data streams

## Project Status:
Current project status: Ongoing
Issues for the board: None

## Membership Data:
Apache StreamPipes was founded 2022-11-16 (a year ago) There are currently 31 
committers and 15 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.

Community changes, past quarter:
- No new PMC members. Last addition was Zhenyu Luo on 2023-10-17.
- Isaak Krut was added as committer on 2024-04-24

## Project Activity:
- Latest Release: 2023-11-28 (v0.93.0)
- Commenced testing for upcoming release and established release branch for 
v0.95.0
- Enhanced time series data store API to prepare the integration of Apache IoTDB
- Augmented code testability
- Implemented Go support for the StreamPipes client

## Community Health:
- Increased engagement on social media platforms
- Published a new blog post focusing on the Python client and integration with 
ONNX models


Cheers,
Philipp

Re: [ANNOUNCE] New committer Isaak Krut

[Dominik Riemer]

Congratulations, Isaak!
Well deserved :-)

Cheers
Dominik

Von: Philipp Zehnder 
Gesendet: Wednesday, April 24, 2024 9:07:40 AM
An: dev@streampipes.apache.org 
Betreff: [ANNOUNCE] New committer Isaak Krut

Hi all,

on behalf of the StreamPipes PMC, it is my pleasure to inform you that
Isaak Krut has accepted the offer to become committer of the
StreamPipes project!

He has already done several PR’s for the project and he is currently working on 
a testing framework to make it easier to unit test processing elements.

Please join me in congratulating him. We are very happy to have him on board.


Cheers,
Philipp

RE: New API extension in Apache PLC4X, that might be interesting for you folks?

[Dominik Riemer]

Hi Chris,

sounds great!
I'll give it a try next weekend 

Cheers
Dominik


-Original Message-
From: Christofer Dutz  
Sent: Tuesday, February 20, 2024 11:14 AM
To: dev@streampipes.apache.org
Subject: AW: New API extension in Apache PLC4X, that might be interesting for 
you folks?

Ok …

so PLC4X 0.12.0 has been released this morning.

Chris


Von: Philipp Zehnder 
Datum: Freitag, 16. Februar 2024 um 14:22
An: dev@streampipes.apache.org 
Betreff: AW: New API extension in Apache PLC4X, that might be interesting for 
you folks?
Hi Chris,

thank you very much for the information.
That sounds super interesting. I like the idea of a generic PLC4X adapter that 
supports all protocols.

Cheers,
Philipp


Von: Christofer Dutz 
Datum: Mittwoch, 14. Februar 2024 um 09:30
An: dev@streampipes.apache.org 
Betreff: New API extension in Apache PLC4X, that might be interesting for you 
folks?
Hi all,

I would say one of the major topics for 0.12.0 definitely is an update to the 
API, that allows users of the API to learn a lot more about the drivers the 
DriverManager provides.

So now in the Metadata of a driver, you can learn:

  *   What are the supported transport types for a given driver?
  *   Is there a default transport and if yes, which one is it?
  *   What are the configuration parameters a driver supports?
  *   What are the configuration parameters a transport supports?

The Info for a parameter is:

  *   Name of the option
  *   Type of the option
  *   Description of the option
  *   If it is required
  *   What’s the default value (if there is one)

I guess with this, it should be possible to build a generic PLC4X source/sink 
that automatically configures itself.

With your current approach of hand-coded modules I guess the benefit is rather 
slim, but I think a generic PLC4X module would be an awesome asset.

We’ll probably release 0.12.0 pretty soon, just wanted to give you folks a 
headsup ;-)


Chris

Re: Interest in an Apache IoT Track at EclipseCon EU in Mainz (Germany) later this year?

[Dominik Riemer]

Hi Chris,
I'd be definitely interested in submitting a talk to EclipseCon since it's 
really close to Karlsruhe.

For CoC Europe - is there anyone on the list who would be interested in 
submitting a talk?
ApacheCon/CoC is a really nice event!

Cheers
Dominik

On 2024/01/04 13:04:48 Christofer Dutz wrote:
> Hi folks,
> 
> I was contacted by some of my friends in the IoT Space at the Eclipse 
> Foundation. 
> 
> They are planning this year's EclipseCon to work closer together with the 
> other foundations in this space and proposed an Apache IoT Track in paralel 
> to the EclipseCon. This will be happening in Mainz in Germany I think 4 weeks 
> before Community Over Code NA.
> 
> I promised to reach out to the projects I know at Apache that count to the 
> IoT space.
> 
> I really liked the idea of networking with the other foundation's projects as 
> I think this is something happening far too little.
> 
> So would you folks be interested in submitting talks and attending such a 
> conference?
> 
> Also the CFP for CoC EU in Bratislava is only open for a few more days and so 
> far the IoT related submissions have been ... let's say ... less than I was 
> hoping for. 
> 
> So if you folks are planning on submitting: Do your track-chair (me) a favor 
> and don't submit on the last day ... it's always a hastle to whip up a 
> schedule if you can't do it in an orderly way, but get "shot by what's there" 
> on the last day.
> 
> Looking forward to feedback,
> 
> Chris
> 

Re: AW: [ANNOUNCE] New committer MuYang Ye

[Dominik Riemer]

Hi MuYang,

congratulations and thanks for your contributions which really help to make 
StreamPipes better!

Cheers
Dominik

On 2023/11/30 13:42:12 Philipp Zehnder wrote:
> Hi MuYang Ye,
> 
> congratulations. It's great to have you on the project.
> 
> Cheers,
> Philipp
> 
> Von: Tim Bossenmaier 
> Datum: Donnerstag, 30. November 2023 um 08:16
> An: dev@streampipes.apache.org 
> Betreff: [ANNOUNCE] New committer MuYang Ye
> Hi all,
> 
> on behalf of the StreamPipes PMC, it is my pleasure to inform you that
> MuYang Ye has accepted the offer to become committer of the
> StreamPipes project!
> 
> We are really happy to have you aboard, MuYang Ye!
> Your contributions, including new adapters, writing tests, and working
> on the deletion feature for adapters, already improved StreamPipes a
> lot.
> We are looking forward to your future contributions.
> 
> Best
> Tim
> 

RE: [VOTE] Apache StreamPipes 0.93.0 RC1 release

[Dominik Riemer]

Hi,

+1 (binding).

I checked:

[ok] Download all staged artifacts under the url specified in the release vote 
email
[ok] Verify the signature is correct
[ok] Check if the signature references an Apache email address
[ok] Verify the SHA512 checksum
[ok] Unzip the archive
[ok] Verify the existence of LICENSE, NOTICE, README, RELEASE_NOTES, 
RELEASE_VALIDATION files in the extracted source bundle.
[ok] Run RAT
[ok*] Search for SNAPSHOT dependencies
[ok] Build Backend
[ok] Build UI
[ok]Build and Run Test system on Docker

As I've written in the discussion thread, I was not able to reproduce any 
errors when upgrading the system, so I guess from my side it's ok unless anyone 
else reports problems.

Tested under Windows 11, JDK 17.

* I found a SNAPSHOT reference in the versions.py file, but this was only 
mentioned as an example and another one in the experimental Flink pipeline 
elements which are not part of the build, so it's ok.

Thanks Tim for managing the release!

Dominik




-Original Message-
From: Tim Bossenmaier  
Sent: Tuesday, November 21, 2023 8:58 AM
To: dev@streampipes.apache.org
Subject: [VOTE] Apache StreamPipes 0.93.0 RC1 release

Hi all,

Apache StreamPipes 0.93.0 has been staged and it’s time to vote on accepting it 
for release.
Voting will be open for at least 72 hours.
A minimum of 3 binding +1 votes and more binding +1 than binding -1 are 
required to pass, but everyone is welcome to vote!

One artifact is relevant for this vote:

streampipes, staged at [1], available in Nexus at [2], release tag:
release/0.93.0, hash for the release tag:
39d9986f41b93dbe9060c38b05ccf74e8e349ff6

Per [3] "Before voting +1, PMC members are required to download the signed 
source code package, compile it as provided, and test the resulting executable 
on their own platform, along with also verifying that the package meets the 
requirements of the ASF policy on releases."

A release validation guide is available at [4]. The KEYS file is available at 
[5]

[ ] +1 accept (indicate what you validated - e.g. performed the checklist at 
the end of [4]) [ ] -1 reject (explanation required)

Thanks for taking your time for validating this release!

Best
Tim


[1] https://dist.apache.org/repos/dist/dev/streampipes/0.93.0/rc1/
[2]
https://repository.apache.org/content/repositories/orgapachestreampipes-1027
[3] https://www.apache.org/dev/release.html#approving-a-release
[4]
https://cwiki.apache.org/confluence/display/STREAMPIPES/Validating+a+release
[5] https://downloads.apache.org/streampipes/KEYS

RE: [DISCUSS] [VOTE] Apache StreamPipes 0.93.0 RC1 release

[Dominik Riemer]

Ok, I tried to reproduce this behavior multiple times and didn't see the 
problem again.

Maybe I just had some configuration problem when updating the Docker Images 
from 0.92.0 to 0.93.0.


-Original Message-
From: Dominik Riemer  
Sent: Saturday, November 25, 2023 11:08 AM
To: dev@streampipes.apache.org
Subject: [DISCUSS] [VOTE] Apache StreamPipes 0.93.0 RC1 release

Hi,

I started to validate the current RC and I encounter problems when doing an 
upgrade from 0.92.0 to 0.93.0.

It seems there is a document update conflict when the extension service tries 
to register at the core. I'll investigate further but did anyone else get this 
problem?

Cheers
Dominik

[DISCUSS] [VOTE] Apache StreamPipes 0.93.0 RC1 release

[Dominik Riemer]

Hi,

I started to validate the current RC and I encounter problems when doing an 
upgrade from 0.92.0 to 0.93.0.

It seems there is a document update conflict when the extension service tries 
to register at the core. I'll investigate further but did anyone else get this 
problem?

Cheers
Dominik

Re: [DRAFT] November Board Report

[Dominik Riemer]

Hi Philipp,

thanks for preparing the report, looks good to me!

Cheers
Dominik

On 2023/11/06 13:37:19 Philipp Zehnder wrote:
> Hi all,
> 
> please let me know if you have any other points or if you want me to adjust 
> something.
> 
> ## Description:
> The mission of Apache StreamPipes is the creation and maintenance of software
> related to a self-service Industrial IoT toolbox which enables non-technical
> users to connect, analyze and explore IoT data streams
> 
> ## Project Status:
> Current project status: Ongoing
> Issues for the board: None
> 
> ## Membership Data:
> Apache StreamPipes was founded 2022-11-16 (a year ago)
> There are currently 29 committers and 15 PMC members in this project.
> The Committer-to-PMC ratio is roughly 2:1.
> 
> Community changes, past quarter:
> - Zhenyu Luo was added to the PMC on 2023-10-17
> 
> ## Project Activity:
> - We are currently preparing the release 0.93.0
> - Enhanced update process between versions
> - Developers of processing elements now have the option of 
> implement update scripts
> - Streamlining the adapter model
> - Improve StreamPipes documentation
> - Documentation system improved to automatically create up-to-date docs from 
> pipeline elements
> - Increased End-to-End (e2e) Test Coverage
> 
> ## Community Health:
> - Two projects were supervised by community members at the OSPP
> - Maintained consistent engagement in social media outreach efforts
> - Successful contributions to the Hacktoberfest
> - Several new contributors have appeared with first-time contributions
> - We are very pleased with the progress of our Github discussion page, where 
> users ask for help and background information
> 
> Cheers,
> Philipp
> 

New PMC Member: Zhenyu Luo

[Dominik Riemer]

Hi all,
on behalf of the Apache StreamPipes PMC, it is my pleasure to inform you that
Zhenyu Luo has accepted the offer to become PMC member of the
StreamPipes project!
As a StreamPipes committer, Zhenyu has helped a lot in improving and extending 
our Helm charts for Kubernetes deployment and has implemented the Prometheus 
integration which will be a great addition to the upcoming StreamPipes release.

Please join me in congratulating Zhenyu and thanks for your great commitment 
and excellent work, Zhenyu!

Cheers
Dominik

Re: Request for PR review

[Dominik Riemer]

Dear Qian,

to clarify the point I made in my previous mail: Please don't include the dev 
list in your mails, which is for technical exchange.
Our community follows the ASF Code of Conduct, which you can find at [1]. We 
don't discuss personal matters over public channels and don't forward privately 
sent mails to public channels.

You will get a response over private channels. Since we are all volunteers, 
please allow that people might not be available over the weekend due to other 
obligations.

Thanks for your understanding.

Best,
Dominik


[1] 
https://www.apache.org/foundation/policies/conduct#:~:text=Be%20careful%20in%20the%20words,or%20put%20down%20other%20participants.

On 2023/10/14 13:39:16 Q Yang wrote:
> Hi, Tim!
> Hope the Email finds you well.
> 
> I want to state again: No one could guess exactly and achieve the results
> you want, if you don't give a clear task. Without mentor‘s suggestions, a
> beginner could not do well in a helpless environment, right? A mentor is
> really important and could help a lot, even just to explain the task
> clearly and describe the expectations clearly. Therefore, instead of always
> being silent in the discussion and PR comments and telling me I could not
> achieve the OSPP challenge in private Email, please tell me what are your
> requirements in detailed. I will try my best to achieve these requirements
> and I have confidence I can achieve them.
> 
> Looking forward to hearing from you!
> 
> By the way, although you ignore my advice before, which is maybe a Zoom
> meeting or Teams meeting could help to explain the things clearly, I still
> want to ask for one meeting at your convenience.
> 
> Q Yang  于2023年10月13日周五 17:38写道：
> 
> > Hi Tim,
> >
> > I was surprised to hear you mention that you and others in the community
> > dislike my PR, as I have not received any feedback from others. In
> > addition, to avoid missing your Email and causing mistakes, I checked my
> > email box. I do not think I have received any valuable feedback or
> > suggestions from you since you published the OSPP task as a mentor (as
> > shown in the attachment email file), except the comments in the PR today.
> > Consequently, I'm astonished that I do not meet the requirements.
> >
> >
> > I still have a few questions that I want to clarify:
> >
> >
> > The most important thing is: which part of the challenge do you believe I
> > do not complete? My current implementation is based on the task description
> > in OSPP and the proposal I submitted(which is reviewed and accepted by
> > you). The entire technical implementation process has fully implemented all
> > the details and has achieved the function of having pre-set assets when
> > opening StreamPipes.
> >
> > From your reply, I did not see any challenge which is impossible
> > to achieve. Here are all points I extracted from your email reply and PR
> > reply that need to be improved:
> >
> >1. Enrich the assets in the PR. Your description of the asset is
> >confusing. Could you please give a rough description and an example?
> >2. In the documentation, clearly describe which components are in the
> >default assets and provide a detailed description of each component.
> >3. Adjust the method to wait for backend service.
> >
> > Could you please explicitly tell me whether fixing these three points
> > will allow me to complete the challenge? If so, I can finish it quickly.
> > If not, please tell me the reason.
> >
> >
> > Best wishes!
> > Qian Yang
> > 2023.10.13
> >
> >
> > Q Yang  于2023年10月13日周五 16:05写道：
> >
> >>
> >>
> >> Tim Bossenmaier 于2023年10月13日 周五15:25写道：
> >>
> >>> Hi Qian Yang,
> >>>
> >>> I've just added some comments to your PR in the StreamPipes repository.
> >>>
> >>> Additionally, I just want to make it clear that (as mentioned in earlier
> >>> emails) the two existing PRs in their current state are not sufficient to
> >>> pass the OSPP challenge. This is not only my personal opinion, but also 
> >>> the
> >>> opinion of other Apache StreamPipes PMC members.
> >>> To emphasise this even more than in the PR comments, we simply feel that
> >>> the assets provided in the PR are not suitable for our goal of creating a
> >>> fascinating experience for first-time users of Apache StreamPipes.
> >>> Furthermore, the documentation you provide in the streampipes-website
> >>> repository does not guide the user. Sure, it clearly describes how to use
> >>> Quickstart mode from a technical perspective, but otherwise I think first
> >>> time users are lost once they open StreamPipes. Ideally, this part of the
> >>> documentation would not only show the user how to start the Quickstart
> >>> mode, but also guide them through their first steps in StreamPipes and
> >>> explain the resources available.
> >>>
> >>> I hope I have made my points clear and left no questions unanswered. If
> >>> so, feel free to contact me again.
> >>> In general, your contribution is good on a technical level, but it's
> >>> 

Re: Request for PR review

[Dominik Riemer]

Hi Qian,
since this is a discussion about OSPP performance and therefore somehow 
personal, I'd prefer to discuss the topic in private and not on the dev list 
(which is public to anyone).

We will discuss the matter and your questions in the PMC and come back to you.
If you want to include the PMC in your future mails, you can cc or send an 
email to priv...@streampipes.apache.org at any time (the list is moderated, but 
your message will get through).

Thanks for your understanding and have a nice weekend!

Cheers,
Dominik


On 2023/10/13 09:38:06 Q Yang wrote:
> Hi Tim,
> 
> I was surprised to hear you mention that you and others in the community
> dislike my PR, as I have not received any feedback from others. In
> addition, to avoid missing your Email and causing mistakes, I checked my
> email box. I do not think I have received any valuable feedback or
> suggestions from you since you published the OSPP task as a mentor (as
> shown in the attachment email file), except the comments in the PR today.
> Consequently, I'm astonished that I do not meet the requirements.
> 
> 
> I still have a few questions that I want to clarify:
> 
> 
> The most important thing is: which part of the challenge do you believe I
> do not complete? My current implementation is based on the task description
> in OSPP and the proposal I submitted(which is reviewed and accepted by
> you). The entire technical implementation process has fully implemented all
> the details and has achieved the function of having pre-set assets when
> opening StreamPipes.
> 
> From your reply, I did not see any challenge which is impossible
> to achieve. Here are all points I extracted from your email reply and PR
> reply that need to be improved:
> 
>1. Enrich the assets in the PR. Your description of the asset is
>confusing. Could you please give a rough description and an example?
>2. In the documentation, clearly describe which components are in the
>default assets and provide a detailed description of each component.
>3. Adjust the method to wait for backend service.
> 
> Could you please explicitly tell me whether fixing these three points will
> allow me to complete the challenge? If so, I can finish it quickly. If
> not, please
> tell me the reason.
> 
> 
> Best wishes!
> Qian Yang
> 2023.10.13
> 
> 
> Q Yang  于2023年10月13日周五 16:05写道：
> 
> >
> >
> > Tim Bossenmaier 于2023年10月13日 周五15:25写道：
> >
> >> Hi Qian Yang,
> >>
> >> I've just added some comments to your PR in the StreamPipes repository.
> >>
> >> Additionally, I just want to make it clear that (as mentioned in earlier
> >> emails) the two existing PRs in their current state are not sufficient to
> >> pass the OSPP challenge. This is not only my personal opinion, but also the
> >> opinion of other Apache StreamPipes PMC members.
> >> To emphasise this even more than in the PR comments, we simply feel that
> >> the assets provided in the PR are not suitable for our goal of creating a
> >> fascinating experience for first-time users of Apache StreamPipes.
> >> Furthermore, the documentation you provide in the streampipes-website
> >> repository does not guide the user. Sure, it clearly describes how to use
> >> Quickstart mode from a technical perspective, but otherwise I think first
> >> time users are lost once they open StreamPipes. Ideally, this part of the
> >> documentation would not only show the user how to start the Quickstart
> >> mode, but also guide them through their first steps in StreamPipes and
> >> explain the resources available.
> >>
> >> I hope I have made my points clear and left no questions unanswered. If
> >> so, feel free to contact me again.
> >> In general, your contribution is good on a technical level, but it's just
> >> not enough to meet the requirements of the challenge.
> >>
> >> Best regards
> >> Tim
> >>
> >>  Originalnachricht 
> >> Betreff: Request for PR review
> >> Datum: 10.10.2023 11:23
> >> Von: Q Yang 
> >> An: Tim Bossenmaier 
> >>
> >> Hi,Tim!
> >> I notice that you have approved luoluoyuyu's PR, could you please review
> >> my PR and give me some suggestions? If my PR has some problems, I'd like
> >> to change it as soon as possible. Before the end of the month, I still
> >> could change the PR. Could you give me a chance so that I could do it
> >> better?
> >>
> >> Best wishes!
> >> Qian Yang
> >> 10.10
> >>
> >
> 

RE: Looking forward to Contribute in Stream pipes : Digital twin

[Dominik Riemer]

We applied some changes to the website to fix a trailing slash problem in some 
browsers.
Please have a look at the documentation on info how to create custom elements 
(e.g., [1], [2]). You can use the dev setup (using the CLI) to develop your own 
extensions and can run the system in production either in Docker or K8s.
There are also many examples on Github (make sure to choose the correct branch 
for your version) at [3]

Cheers
Dominik


[1] https://streampipes.apache.org/docs/extend-cli/
[2] https://streampipes.apache.org/docs/extend-archetypes/
[3] https://github.com/apache/streampipes/tree/dev/streampipes-extensions

From: Gaurav P 
Sent: Wednesday, September 27, 2023 2:12 PM
To: dev@streampipes.apache.org
Subject: Re: Looking forward to Contribute in Stream pipes : Digital twin

Hi All ,
Can please let point me to the updated document with instruction that works ? 
for dev setup ...its really urgent as I have demo scheduled

Also is dev setup required ? Can I install and test stream pipes in running 
production /running instance



On Wed, Sep 27, 2023 at 7:17 AM Gaurav P 
mailto:g...@gpism.com>> wrote:
I followed this link https://streampipes.apache.org/docs/user-guide-introduction
almost all the links I clicked  are broken (404) , after that I did google 
search  , is there any working  documentation or instruction which works ? I 
need to give demo to my management team ,with custom adapters , processors but 
so journey is really frustrating though love the concepts
[cid:ii_ln13434c0]

On Wed, Sep 27, 2023 at 2:24 AM Dominik Riemer 
mailto:dominik.rie...@bytefabrik.ai>> wrote:
Hi Gaurav,

0.68.0 is a really old version (more than 2 years old). I suggest that you 
download the latest release and start with a clean installation, making sure 
that any volumes are removed before installing the new version. Newer version 
of StreamPipes are backwards compatible (we support automatic updates from one 
version to the next).

Concerning the website, did you find broken links when you were coming from 
Google or directly in the documentation?
We've changed the path of the documentation, which was obviously a bad idea 
since Google hasn't picked up the changes for months now (guess we need an SEO 
expert in the team), but if you've found broken links in the documentation 
itself, it would be great if you could share the links.

Cheers
Dominik



-Original Message-
From: Gaurav P mailto:g...@gpism.com>>
Sent: Tuesday, September 26, 2023 4:58 AM
To: dev@streampipes.apache.org<mailto:dev@streampipes.apache.org>
Subject: Re: Looking forward to Contribute in Stream pipes : Digital twin

also half of the documentation links are dead , giving 404 , I tried on unbutu 
sever earlier WSL windows  and it partially worked  till I got

Full Logs here
https://gist.github.com/gpism/dc248b24d03420c8a86e78062fb4939d

Pulling connect-worker-main (apachestreampipes/connect-worker:0.68.0)...
ERROR: pull access denied for apachestreampipes/connect-worker, repository does 
not exist or may require 'docker login': denied: requested access to the 
resource is denied I hope this project is still active and I can contribute



On Tue, Sep 26, 2023 at 7:54 AM Gaurav P 
mailto:g...@gpism.com>> wrote:

> Thanks ,
> I followed the links below and having a problem getting the dev setup
> ,
>
> I am getting this issue in  ubuntu running on wsl 2 windows Welcome to
> Apache StreamPipes - wait for installation to be finished...
>
> [INFO] Version: 0.68.0
> [INFO] Environment: 'pipeline-element'
> [INFO] Mode: Development mode, all ports mapped [INFO] Docker network
> 'spnet' already exists. Continuing
>
> more logs on
> https://gist.github.com/gpism/3a256026f8d1c3dd52773d5e76938ee6
>
> Please help me get started with development seup
>
> I have created 5-6 processors but unable to install or test
>
>
> On Tue, Jul 26, 2022 at 11:29 PM Dominik Riemer <
> dominik.rie...@bytefabrik.ai<mailto:dominik.rie...@bytefabrik.ai>> wrote:
>
>> Hi Gaurav,
>>
>> sounds cool!
>>
>> Are you looking for Camel/Nifi adapters to receive data or sinks to
>> publish data from StreamPipes as a sink?
>> We don't have any specific processors for that, but you can probably
>> exchange data over MQTT or some other protocol supported by both systems.
>>
>> Having said that, it would be really cool to have a tighter
>> integration, e.g., for data sinks we have a tutorial at [1], many
>> existing processors as some inspiration at [2] and a project
>> containing configuration examples at [3]. You might also be
>> interested in using the Maven archetypes [4] for processor
>> development, or you can directly extend our extensions module and
>> create a PR. For adapters, we currently don't have a documentation, but you 
>> can also check the examples in

RE: Looking forward to Contribute in Stream pipes : Digital twin

[Dominik Riemer]

Hi Gaurav,

0.68.0 is a really old version (more than 2 years old). I suggest that you 
download the latest release and start with a clean installation, making sure 
that any volumes are removed before installing the new version. Newer version 
of StreamPipes are backwards compatible (we support automatic updates from one 
version to the next).

Concerning the website, did you find broken links when you were coming from 
Google or directly in the documentation?
We've changed the path of the documentation, which was obviously a bad idea 
since Google hasn't picked up the changes for months now (guess we need an SEO 
expert in the team), but if you've found broken links in the documentation 
itself, it would be great if you could share the links.

Cheers
Dominik 



-Original Message-
From: Gaurav P  
Sent: Tuesday, September 26, 2023 4:58 AM
To: dev@streampipes.apache.org
Subject: Re: Looking forward to Contribute in Stream pipes : Digital twin

also half of the documentation links are dead , giving 404 , I tried on unbutu 
sever earlier WSL windows  and it partially worked  till I got

Full Logs here
https://gist.github.com/gpism/dc248b24d03420c8a86e78062fb4939d

Pulling connect-worker-main (apachestreampipes/connect-worker:0.68.0)...
ERROR: pull access denied for apachestreampipes/connect-worker, repository does 
not exist or may require 'docker login': denied: requested access to the 
resource is denied I hope this project is still active and I can contribute



On Tue, Sep 26, 2023 at 7:54 AM Gaurav P  wrote:

> Thanks ,
> I followed the links below and having a problem getting the dev setup 
> ,
>
> I am getting this issue in  ubuntu running on wsl 2 windows Welcome to 
> Apache StreamPipes - wait for installation to be finished...
>
> [INFO] Version: 0.68.0
> [INFO] Environment: 'pipeline-element'
> [INFO] Mode: Development mode, all ports mapped [INFO] Docker network 
> 'spnet' already exists. Continuing
>
> more logs on
> https://gist.github.com/gpism/3a256026f8d1c3dd52773d5e76938ee6
>
> Please help me get started with development seup
>
> I have created 5-6 processors but unable to install or test
>
>
> On Tue, Jul 26, 2022 at 11:29 PM Dominik Riemer < 
> dominik.rie...@bytefabrik.ai> wrote:
>
>> Hi Gaurav,
>>
>> sounds cool!
>>
>> Are you looking for Camel/Nifi adapters to receive data or sinks to 
>> publish data from StreamPipes as a sink?
>> We don't have any specific processors for that, but you can probably 
>> exchange data over MQTT or some other protocol supported by both systems.
>>
>> Having said that, it would be really cool to have a tighter 
>> integration, e.g., for data sinks we have a tutorial at [1], many 
>> existing processors as some inspiration at [2] and a project 
>> containing configuration examples at [3]. You might also be 
>> interested in using the Maven archetypes [4] for processor 
>> development, or you can directly extend our extensions module and 
>> create a PR. For adapters, we currently don't have a documentation, but you 
>> can also check the examples in the repo.
>>
>> Regarding the Slack channel, we are not longer supporting this (need 
>> to update the website ), so the best way is to communicate over the 
>> mailing list or the Apache Slack channel in case you are an ASF committer.
>>
>> Please ask if you have any questions!
>>
>> Best
>> Dominik
>>
>> [1]
>> https://streampipes.apache.org/docs/docs/extend-tutorial-data-sinks.h
>> tml
>> [2]
>> https://github.com/apache/incubator-streampipes/tree/dev/streampipes-
>> extensions
>> [3]
>> https://github.com/apache/incubator-streampipes-examples/tree/dev/str
>> eampipes-pipeline-elements-examples-processors-jvm/src/main/java/org/
>> apache/streampipes/pe/examples/jvm
>> [4] https://streampipes.apache.org/docs/docs/extend-archetypes.html
>>
>>
>>
>> -Original Message-
>> From: Gaurav P 
>> Sent: Tuesday, July 26, 2022 2:42 AM
>> To: dev@streampipes.apache.org
>> Subject: Re: Looking forward to Contribute in Stream pipes : Digital 
>> twin
>>
>> HI Andrews ,
>>
>> I am planning to generate digital twins for industry 4.0 assets like 
>> the entire factory using unreal and display sensor data on 3d model
>>
>> For data processing and sensor data and integration with backend 
>> systems like ERP already deployed, I am experimenting with using 
>> stream pipes
>>
>> For Now, I am exploring the following
>> 1) How ingrate with backend systems, is there any adapter for apache 
>> camel, if not can I build /contribute? so that we access 300+ 
>> integration

Re: [ANNOUNCE] New committer Zhenyu Luo

[Dominik Riemer]

Hi Zhenyu,
congratulations!
Great to have you in the team and thanks for your very cool contributions so 
far.
Cheers
Dominik

Von: Tim Bossenmaier 
Gesendet: Sunday, August 20, 2023 7:34:50 PM
An: dev@streampipes.apache.org 
Betreff: [ANNOUNCE] New committer Zhenyu Luo

Hi all,

on behalf of the StreamPipes PMC, it is my pleasure to inform you that
Zhenyu Luo has accepted the offer to become committer of the
StreamPipes project!

Zhenyu did some great work on improving our integration test suite and our
Helm chart.
I look forward to everything that is to come.

Please join me in congratulating him.

Dear Zhenyu, I am very happy to have you as a committer in the project.

Cheers,
Tim

CVE-2023-31469: Apache StreamPipes: Privilege escalation through non-admin user

[Dominik Riemer]

Severity: important

Affected versions:

- Apache StreamPipes 0.69.0 through 0.91.0

Description:

A REST interface in Apache StreamPipes (versions 0.69.0 to 0.91.0) was not 
properly restricted to admin-only access. This allowed a non-admin user with 
valid login credentials to elevate privileges beyond the initially assigned 
roles.
The issue is resolved by upgrading to StreamPipes 0.92.0.

Credit:

Xun Bai, LJQC Open Source Security Institute (finder)

References:

https://streampipes.apache.org
https://www.cve.org/CVERecord?id=CVE-2023-31469

RE: [VOTE] Apache StreamPipes 0.92.0 RC1 release

[Dominik Riemer]

Hi,

+1 (binding)

I checked:
(ok) Download all staged artifacts under the url specified in the release vote 
email
(ok) Verify the signature is correct
(ok) Check if the signature references an Apache email address
(ok) Verify the SHA512 checksum
(ok) Unzip the archive
(ok) Verify the existence of LICENSE, NOTICE, README, RELEASE_NOTES, 
RELEASE_VALIDATION files in the extracted source bundle.
(ok) Run RAT
(ok) Search for SNAPSHOT dependencies
(ok) Build Backend
(ok) Build UI
(ok) Build and Run Test system on Docker
(ok) Tested migration from 0.91.0 to 0.92.0 with existing pipelines and adapters
(ok) Created, built and started the extensions-all Maven archetype

OS: Ubuntu 20.04
Apache Maven 3.9.1
openjdk 17.0.6
npm -v 8.12.1
Docker version 20.10.12

The archetypes were tested on Windows 10, OpenJDK 17.0.1.

Thank you Philipp for preparing the release!!

Cheers
Dominik

-Original Message-
From: Philipp Zehnder  
Sent: Friday, June 9, 2023 9:22 AM
To: dev@streampipes.apache.org
Subject: [VOTE] Apache StreamPipes 0.92.0 RC1 release

Hi all,

Apache StreamPipes 0.92.0 has been staged and it's time to vote on accepting it 
for release.
Voting will be open for at least 72 hours.
A minimum of 3 binding +1 votes and more binding +1 than binding -1 are 
required to pass, but everyone is welcome to vote!

One artifact is relevant for this vote:

streampipes, staged at [1], available in Nexus at [2], release tag: 
release/0.92.0, hash for the release tag: 
38569af6255ad2475cea42a26159e3fd0ad1b161

Per [3] "Before voting +1, PMC members are required to download the signed 
source code package, compile it as provided, and test the resulting executable 
on their own platform, along with also verifying that the package meets the 
requirements of the ASF policy on releases."

A release validation guide is available at [4]. The KEYS file is available at 
[5]

[ ] +1 accept (indicate what you validated - e.g. performed the checklist at 
the end of [4]) [ ] -1 reject (explanation required)

Thanks for taking your time for validating this release!


[1] https://dist.apache.org/repos/dist/dev/streampipes/0.92.0/rc1/
[2] 
https://repository.apache.org/content/repositories/orgapachestreampipes-1026/
[3] https://www.apache.org/dev/release.html#approving-a-release
[4] https://cwiki.apache.org/confluence/display/STREAMPIPES/Validating+a+release
[5] https://downloads.apache.org/streampipes/KEYS

Re: AW: Merge brach with connect API refactoring

[Dominik Riemer]

Hi Philipp,

great work!
I pushed another commit which fixes a bug when starting multiple adapters of 
the same type and refactored the code structure a bit to have all interfaces in 
the extensions-api module.

>From my point of view, we can merge this into dev and fix the remaining issues 
>over PRs.

Cheers
Dominik

On 2023/05/24 12:59:30 "Obermeier. Stefan" wrote:
> Hi Philipp,
> 
> thank you for this a great improvements!
> I like the idea of removing not much used adapters.
> 
> Cheers,
> Stefan
> 
> 
> PS.
> I have a possibly small issue with the UI.
> In my case the adapters are not shown in /#/connect/create.
> 
> -Ursprüngliche Nachricht-
> Von: Philipp Zehnder 
> Gesendet: Montag, 22. Mai 2023 21:15
> An: dev@streampipes.apache.org
> Betreff: Merge brach with connect API refactoring
> 
> Hi all,
> 
> after the PR [1] has become significantly larger than originally planned, 
> most features should now be implemented. There are still a few minor issues, 
> but the main functions should all work.
> Since we have already started the branch for the release, I would like to 
> merge the branch into the `dev` branch to be able to test everything.
> 
> The adapters in `streampipes-connect-adapters-iiot` [2] are all updated. 
> Regarding the adapters in `streampipes-connect-adapters`[3] I would suggest 
> removing most of them as they are rather less used. Do you see it the same 
> way? (For all adapters we want to keep we should create an issue for the 
> upgrade).
> 
> If you want to get familiar with the new API you can have a look at [4] & 
> [5]. If you have any feedback, you can share it here.
> 
> What is your opinion on the topic, should we merge the branch into dev? Then 
> we can also start with some issues for adapters that we have pushed to the 
> back.
> 
> Cheers,
> Philipp
> 
> [1] https://github.com/apache/streampipes/pull/1290
> [2] 
> https://github.com/apache/streampipes/tree/remove-set-adapters/streampipes-extensions/streampipes-connect-adapters-iiot
> [3] 
> https://github.com/apache/streampipes/tree/remove-set-adapters/streampipes-extensions/streampipes-connect-adapters
> [4] 
> https://github.com/apache/streampipes/blob/remove-set-adapters/streampipes-extensions/streampipes-connect-adapters-iiot/src/main/java/org/apache/streampipes/connect/iiot/adapters/simulator/machine/MachineDataSimulatorAdapter.java
> [5] 
> https://github.com/apache/streampipes/blob/remove-set-adapters/streampipes-extensions/streampipes-connect-adapters-iiot/src/main/java/org/apache/streampipes/connect/iiot/protocol/stream/FileReplayAdapter.java
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> SEEBURGER AGVorstand/SEEBURGER Executive Board:
> Sitz der Gesellschaft/Registered Office:Axel Haas, Michael 
> Kleeberg, Axel Otto, Dr. Martin Kuntz, Matthias Feßenbecker
> Edisonstr. 1
> D-75015 Bretten Vorsitzende des Aufsichtsrats/Chairperson of the 
> SEEBURGER Supervisory Board:
> Tel.: 07252 / 96 - 0Prof. Dr. Simone Zeuchner-Egli
> Fax: 07252 / 96 - 
> Internet: http://www.seeburger.de   Registergericht/Commercial 
> Register:
> e-mail: i...@seeburger.de   HRB 240708 Mannheim
> 
> 
> Dieses E-Mail ist nur für den Empfänger bestimmt, an den es gerichtet ist und 
> kann vertrauliches bzw. unter das Berufsgeheimnis fallendes Material 
> enthalten. Jegliche darin enthaltene Ansicht oder Meinungsäußerung ist die 
> des Autors und stellt nicht notwendigerweise die Ansicht oder Meinung der 
> SEEBURGER AG dar. Sind Sie nicht der Empfänger, so haben Sie diese E-Mail 
> irrtümlich erhalten und jegliche Verwendung, Veröffentlichung, Weiterleitung, 
> Abschrift oder jeglicher Druck dieser E-Mail ist strengstens untersagt. Weder 
> die SEEBURGER AG noch der Absender (Obermeier. Stefan) übernehmen die Haftung 
> für Viren; es obliegt Ihrer Verantwortung, die E-Mail und deren Anhänge auf 
> Viren zu prüfen.
> 
> 
> This email is intended only for the recipient(s) to whom it is addressed. 
> This email may contain confidential material that may be protected by 
> professional secrecy. Any fact or opinion contained, or expression of the 
> material herein, does not necessarily reflect that of SEEBURGER AG. If you 
> are not the addressee or if you have received this email in error, any use, 
> publication or distribution including forwarding, copying or printing is 
> strictly prohibited. Neither SEEBURGER AG, nor the sender (Obermeier. Stefan) 
> accept liability for viruses; it is your responsibility to check this email 
> and its attachments for viruses.
> 
> 

Re: My first PR merged for the GitHub tooling ... allowing to customize GitHub Discussion emails

[Dominik Riemer]

Thank you Chris!
That’s absolutely great and I guess we will add this to the yaml file.

Cheers
Dominik

Von: Christofer Dutz 
Gesendet: Monday, May 15, 2023 4:37:13 PM
An: dev@streampipes.apache.org 
Betreff: AW: My first PR merged for the GitHub tooling ... allowing to 
customize GitHub Discussion emails

Hi all,

I just learned in the plc4x project, that we need the “repository” in the title 
… so here’s what we have:
https://github.com/apache/plc4x/blob/develop/.asf.yaml#L62

  # Attempt to make the auto-generated github emails more easily readable in 
email clients.
  custom_subjects:
new_pr: "[PR] {title} ({repository})"
close_pr: "Re: [PR] {title} ({repository})"
comment_pr: "Re: [PR] {title} ({repository})"
diffcomment: "Re: [PR] {title} ({repository})"
merge_pr: "Re: [PR] {title} ({repository})"
new_issue: "[I] {title} ({repository})"
comment_issue: "Re: [I] {title} ({repository})"
close_issue: "Re: [I] {title} ({repository})"
catchall: "[GH] {title} ({repository})"
new_discussion: "[D] {title} ({repository})"
edit_discussion: "Re: [D] {title} ({repository})"
close_discussion: "Re: [D] {title} ({repository})"
close_discussion_with_comment: "Re: [D] {title} ({repository})"
reopen_discussion: "Re: [D] {title} ({repository})"
new_comment_discussion: "Re: [D] {title} ({repository})"
edit_comment_discussion: "Re: [D] {title} ({repository})"
delete_comment_discussion: "Re: [D] {title} ({repository})"

Chris

Von: Christofer Dutz 
Datum: Montag, 15. Mai 2023 um 16:24
An: dev@streampipes.apache.org 
Betreff: My first PR merged for the GitHub tooling ... allowing to customize 
GitHub Discussion emails
Hi all,

I just also added the documentation on my latest addition to the GitHub tooling.

Now we can customize the email titles sent to the mailinglists … I bet you 
folks will be relieved by that, right?

https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features

I would suggest something like:

  custom_subjects:
new_pr: "[PR] {title}"
close_pr: "Re: [PR] {title}"
comment_pr: "Re: [PR] {title}"
diffcomment: "Re: [PR] {title}"
merge_pr: "Re: [PR] {title}"
new_issue: "[I] {title}"
comment_issue: "Re: [I] {title}"
close_issue: "Re: [I] {title}"
catchall: "[GH] {title}"
  new_discussion: "[D] {title}"
  edit_discussion: "Re: [D] {title}"
  close_discussion: "Re: [D] {title}"
  close_discussion_with_comment: "Re: [D] {title}"
  reopen_discussion: "Re: [D] {title}"
  new_comment_discussion: "Re: [D] {title}"
  edit_comment_discussion: " Re: [D] {title}"
  delete_comment_discussion: " Re: [D] {title}"


Tell me what you think?

Chris

RE: [DRAFT] Mai Board Report

[Dominik Riemer]

Thank you Philipp!

I like the report and don't have any additions besides the items from Tim.

Cheers
Dominik


-Original Message-
From: Philipp Zehnder  
Sent: Friday, May 5, 2023 7:20 AM
To: dev@streampipes.apache.org
Subject: Re: [DRAFT] Mai Board Report

Thanks a lot Tim.
I'll add it. If someone else has any more input please let me know.

Von: Tim 
Gesendet: Thursday, May 4, 2023 8:42:12 PM
An: dev@streampipes.apache.org 
Betreff: Re: [DRAFT] Mai Board Report

Hey Philipp,

thanks a lot for drafting our upcoming board report.

I would suggest to add the following points:

* talks at FOSSGIS and PyCon
* release of Python library

Best
Tim

Am 04.05.2023 16:51 schrieb Philipp Zehnder:
> Hi all,
>
> here is the draft board report. Please let me know if you have any 
> additional points:
>
> ## Description:
> The mission of Apache StreamPipes is the creation and maintenance of 
> software related to a self-service Industrial IoT toolbox which 
> enables non-technical users to connect, analyze and explore IoT data 
> streams
>
> ## Issues:
> No Issues
>
> ## Membership Data:
> Apache StreamPipes was founded 2022-11-16 (6 months ago) There are 
> currently 27 committers and 14 PMC members in this project.
> The Committer-to-PMC ratio is roughly 7:4.
>
> Community changes, past quarter:
> - No new PMC members. Last addition was Zike Yang on 2022-11-26.
> - Xiao Liu was added as committer on 2023-04-21
> - Steve Yurong Su was added as committer on 2023-02-27
>
> ## Project Activity:
> - Version 0.91.0 was released (April 14, 2023) [1].
> - Discussion and first implementation to replace InfluxDB with Apache 
> IoTDB.
> - Refactoring of the Connect library
> - Various automations added to GitHub workflows to improve code 
> quality and the PR process
>
> ## Community Health:
> - Two online community meetings (2023-02-22, 2023-04-05) [2][3]
> - Presentation at the BuildingIoT conference in Munich.
> - Through the discussions on GitHub, we were able to get some feedback 
> from new users
> - Several proposals were submitted for GSoC
> - Two topics were submitted for the OSPP
>
>
> [1]
> https://github.com/apache/streampipes/blob/release/0.91.0/RELEASE_NOTE
> S.md
> [2]
> https://cwiki.apache.org/confluence/display/STREAMPIPES/SPCM-2023-02-2
> 2
> [3]
> https://cwiki.apache.org/confluence/display/STREAMPIPES/SPCM-2023-04-0
> 5
>
> Cheers,
> Philipp

[ANNOUNCE] New Committer: Liu Xiao

[Dominik Riemer]

Hi all,

on behalf of the StreamPipes PMC, it is my pleasure to inform you that
Liu Xiao has accepted the offer to become committer of the
StreamPipes project!

Liu did some great work on improving pipeline elements, improved test coverage 
and contributed improvements to the Kafka publisher.

Please join me in congratulating Liu and welcome to the team!!

Cheers
Dominik

RE: [OSPP] Call for projects and mentors for OSPP 2023

[Dominik Riemer]

Hi Tim,

just to avoid confusion - Zike has asked today in Slack and we would select 
yours and his...hope that's ok for you 

Cheers
Dominik


-Original Message-
From: Tim Bossenmaier  
Sent: Wednesday, April 26, 2023 6:15 PM
To: dev@streampipes.apache.org
Subject: Re: [OSPP] Call for projects and mentors for OSPP 2023

Hi all,

then let's go with Dominik's proposal (and of course Zike's).
I think this is the more interesting one and better suited scope-wise as well.
The quickstart deployment mode can also easily done by us or could also be a 
good-first-issue.

Best
Tim

RE: [OSPP] Call for projects and mentors for OSPP 2023

[Dominik Riemer]

Hi,

@Zike and @Tim, your proposals sound good!

Just to provide another idea, we could also offer the OPC UA challenge, see 
below. But I'm also totally fine to submit your two ideas instead of this one 
and would be willing to help you with both.

Best,
Dominik

## Project Info
Project Name: OPC-UA Browser for Apache StreamPipes

Description: StreamPipes is grown significantly throughout recent years. We 
were able to introduce a lot of new features and attracted both users and 
contributors. Putting the cherry on the cake, we were graduated as an Apache 
top level project in December 2022. We will of course continue developing new 
features and never rest to make StreamPipes even more amazing.

StreamPipes really shines when connecting Industrial IoT data. Such data 
sources typically originate from machine controllers, called PLCs (e.g., 
Siemens S7). But there are also new protocols such as OPC-UA which allow to 
browse available data within the controller. Our goal is to make connectivity 
of industrial data sources a matter of minutes.

Currently, data sources can be connected using the built-in module StreamPipes 
Connect from the UI. We provide a set of adapters for popular protocols that 
can be customized, e.g., connection details can be added.

To make it even easier to connect industrial data sources with StreamPipes, we 
plan to add an OPC-UA browser. This will be part of the entry page of 
StreamPipes connect and should allow users to enter connection details of an 
existing OPC-UA server. Afterwards, a new view in the UI shows available data 
nodes from the server, their status and current value. Users should be able to 
select values that should be part of a new adapter. Afterwards, a new adapter 
can be created by reusing the current workflow to create an OPC-UA data source.

Difficulty Level:
- [] Basic
- [x] Advanced

Project Output Requirements:
* get familiar with the OPC-UA protocol
*  develop mockups which demonstrate the user workflow
*  develop a data model for discovering data from OPC-UA
*  create the backend business logic for the OPC-UA browser (e.g., using 
Eclipse Milo)
*  create the frontend views to asynchronously browse data and to create a new 
adapter
 * write Junit, Component and E2E tests

Project Technical Requirements:
Item 1: Familiar with Git
Item 2: Interest in industrial protocols such as OPC-UA
Item 3: Angular frontend development skills
Item 4: Java development skills

Project Repository: https://github.com/apache/streampipes


## Mentor Info
Mentor Name: Dominik Riemer
Mentor Email: rie...@apache.org


-Original Message-
From: Tim Bossenmaier  
Sent: Tuesday, April 25, 2023 2:11 PM
To: dev@streampipes.apache.org
Subject: Re: [OSPP] Call for projects and mentors for OSPP 2023

Hi all,

To fill in our second project slot, I filled in the template with the idea I 
outlined earlier.
If there is another suggestion, I don't mind keeping it.
So if you have other ideas, feel free to share them and we can discuss which 
one to choose.

## Project Info
Project Name: Quickstart Deployment Mode Project Description: Apache 
StreamPipes currently supports three different deployment modes: docker 
compose, CLI, and Kubernetes. While CLI and Kubernetes are intended for 
advanced use and deployment of StreamPipes, docker compose is intended as an 
entry point for people using StreamPipes for the first time or discovering its 
features. To ease the quick-start process and allow users to discover the scope 
of StreamPipes features from the beginning, a quick-start mode for docker 
compose will be introduced. This deployment mode starts StreamPipes with a few 
adapters (and datasets) and some other resources like dashboards and views in 
the data explorer. In addition, the existing user guide will also be enabled 
and extended for this deployment mode.

Difficulty Level:
- [x] Basic
- [] Advanced

Project Output Requirements:
Item 1: Introduce quickstart deployment that comes with a set of predefined 
StreamPipes assets Item 2: Update documentation & website, promote the new 
deployment mode there Item 3: Activate user guide and extend/improve it in 
accordance with the new deployment mode.

Project Technical Requirements:
Item 1: Familiar with Git, Github operations Item 2: Familiar with Java, REST 
Item 3: Familiar with docker compose

Project Repository: https://github.com/apache/streampipes


## Mentor Info
Mentor Name: Tim Bossenmaier
Mentor Email: bosse...@apache.org

--

Cheers,
Tim

RE: [VOTE] Apache StreamPipes 0.91.0 RC1 release

[Dominik Riemer]

Hi,

+1 (binding)

I checked:

(ok) Download all staged artifacts under the url specified in the release vote 
email
(ok) Verify the signature is correct
(ok) Check if the signature references an Apache email address
(ok) Verify the SHA512 checksum
(ok) Unzip the archive
(ok) Verify the existence of LICENSE, NOTICE, README, RELEASE_NOTES, 
RELEASE_VALIDATION files in the extracted source bundle.
(ok) Run RAT
(ok) Search for SNAPSHOT dependencies
(ok) Build Backend
(ok) Build UI
(ok) Build and Run Test system on Docker
(ok) Test upgrade from 0.90.0 to 0.91.0 by setting INFLUX_INIT_MODE to "upgrade"
(ok) Successfully built and started archetype project

Setup: Ubuntu 20.04, OpenJDK 17.0.6, Maven 3.9.1, Node 16.15.1, npm 8.12.1

Thank you Tim for managing the release!

Cheers
Dominik


-Original Message-
From: Tim Bossenmaier  
Sent: Sunday, April 9, 2023 6:56 PM
To: dev@streampipes.apache.org
Subject: [VOTE] Apache StreamPipes 0.91.0 RC1 release

Hi all,

Apache StreamPipes 0.91.0 has been staged and it’s time to vote on accepting it 
for release.
Voting will be open for at least 72 hours.
A minimum of 3 binding +1 votes and more binding +1 than binding -1 are 
required to pass, but everyone is welcome to vote!

One artifact is relevant for this vote:

streampipes, staged at [1], available in Nexus at [2], release tag:
release/0.90.0, hash for the release tag:
4f6cabc8c74e4441aff305da4599b961b59c7a79

Per [3] "Before voting +1, PMC members are required to download the signed 
source code package, compile it as provided, and test the resulting executable 
on their own platform, along with also verifying that the package meets the 
requirements of the ASF policy on releases."

A release validation guide is available at [4]. The KEYS file is available at 
[5]

[ ] +1 accept (indicate what you validated - e.g. performed the checklist at 
the end of [4]) [ ] -1 reject (explanation required)

Thanks for taking your time for validating this release!

Best
Tim

[1] https://dist.apache.org/repos/dist/dev/streampipes/0.91.0/rc1/
[2] 
https://repository.apache.org/content/repositories/orgapachestreampipes-1021/
[3] https://www.apache.org/dev/release.html#approving-a-release
[4] https://cwiki.apache.org/confluence/display/STREAMPIPES/Validating+a+release
[5] https://downloads.apache.org/streampipes/KEYS

RE: [DISCUSS] Next community meeting

[Dominik Riemer]

+1 Dominik


-Original Message-
From: Philipp Zehnder  
Sent: Wednesday, March 29, 2023 8:21 AM
To: dev@streampipes.apache.org
Subject: AW: [DISCUSS] Next community meeting

Ok, shall we move the community call to next week Wednesday?


Von: Florian Micklich 
Datum: Dienstag, 28. März 2023 um 22:43
An: dev@streampipes.apache.org 
Betreff: Re: [DISCUSS] Next community meeting Unfortunately, a customer 
appointment came in at short notice today. Mainly from from 10 till 12 am. (09 
- 11 UTC).
So I could only participate in the evening :(


Am Dienstag, dem 28.03.2023 um 08:57 + schrieb Dominik Riemer:
> +1
>
>
> -Original Message-
> From: Philipp Zehnder 
> <[philipp.zehn...@bytefabrik.ai](mailto:philipp.zehn...@bytefabrik.ai)
> > 
> Sent: Tuesday, March 28, 2023 10:17 AM
> To: 
> [dev@streampipes.apache.org](mailto:dev@streampipes.apache.org)
> Subject: AW: [DISCUSS] Next community meeting
>
> Hi,
>
> unfortunately, I have an appointment at 5 pm. My suggestion is 
> that we use the other time when everyone is available from 10 to 
> 11.
>
> Is that ok?
>
> Cheers,
> Philipp
>
>
> Von: Dominik Riemer 
> <[dominik.rie...@bytefabrik.ai](mailto:dominik.rie...@bytefabrik.ai)><
> br>
> Datum: Dienstag, 28. März 2023 um 09:19
> An: [dev@streampipes.apache.org](mailto:dev@streampipes.apache.org) 
> <[dev@streampipes.apache.org](mailto:dev@streampipes.apache.org)>
> Betreff: RE: [DISCUSS] Next community meeting Hi,
>
> looking at the Doodle, it seems 5pm would be a good time for 
> tomorrow's meeting.
>
> If that's fine for you, I'll send around a link.
>
> Cheers
> Dominik
>
>
> -Original Message-
> From: Florian Micklich 
> <[mickl...@apache.org](mailto:mickl...@apache.org)>
> Sent: Monday, March 27, 2023 11:37 PM
> To: 
> [dev@streampipes.apache.org](mailto:dev@streampipes.apache.org)
> Subject: Re: [DISCUSS] Next community meeting
>
>
> Hi,
>
> just saw this message.
> Who would attend? I can organise it due Tim has no time. The main 
> topic is variables in StreamPipes by Dominik, as I can remember from 
> last time.
>
> Is this still the case?
> The other topics will be discussed during the meeting.
>
> Florian
>
>
>
>
> Am Montag, dem 13.03.2023 um 11:36 + schrieb Tim:
> > Hi all,
> >
> > it's time for our next community meeting! With respect to our  
> > schedule,  it will take place on the 29th of March.  
> > Unfortunately, I won't be able to attend, so someone else needs to 
> >  take  over of the remaining organization steps. Below 
> > you can  find a link to a new poll:  
> > [[https://terminplaner6.dfn.de/p/816c4fa5501d88438a4ffd49e727f5b7-16
> > 593](https://terminplaner6.dfn.de/p/816c4fa5501d88438a4ffd49e727f5b7
> > -16593)https://terminplaner6.dfn.de/p/816c4fa5501d88438a4ffd49e7
> > 27f5b7-16593%5d(https:/terminplaner6.dfn.de/p/816c4fa5501d88438a4ffd
> > 49e727f5b7-16593)%3cbr>> 
> > 3]([https://terminplaner6.dfn.de/p/816c4fa5501d88438a4ffd49e727f5b7-
> > 165](https://terminplaner6.dfn.de/p/816c4fa5501d88438a4ffd49e727f5b7
> > -165)https://terminplaner6.dfn.de/p/816c4fa5501d88438a4ffd49e727
> > f5b7-165%5d(https:/terminplaner6.dfn.de/p/816c4fa5501d88438a4ffd49e7
> > 27f5b7-165)%3cbr>>
> > 933)
> >
> > Please be aware that you can scroll horizontally ;)
> >
> > Best
> > Tim

RE: [DISCUSS] Next community meeting

[Dominik Riemer]

+1


-Original Message-
From: Philipp Zehnder  
Sent: Tuesday, March 28, 2023 10:17 AM
To: dev@streampipes.apache.org
Subject: AW: [DISCUSS] Next community meeting

Hi,

unfortunately, I have an appointment at 5 pm.
My suggestion is that we use the other time when everyone is available from 10 
to 11.

Is that ok?

Cheers,
Philipp


Von: Dominik Riemer 
Datum: Dienstag, 28. März 2023 um 09:19
An: dev@streampipes.apache.org 
Betreff: RE: [DISCUSS] Next community meeting Hi,

looking at the Doodle, it seems 5pm would be a good time for tomorrow's meeting.

If that's fine for you, I'll send around a link.

Cheers
Dominik


-Original Message-
From: Florian Micklich 
Sent: Monday, March 27, 2023 11:37 PM
To: dev@streampipes.apache.org
Subject: Re: [DISCUSS] Next community meeting


Hi,

just saw this message.
Who would attend? I can organise it due Tim has no time.
The main topic is variables in StreamPipes by Dominik, as I can remember from 
last time.

Is this still the case?
The other topics will be discussed during the meeting.

Florian




Am Montag, dem 13.03.2023 um 11:36 + schrieb Tim:
> Hi all,
>
> it's time for our next community meeting! With respect to our 
> schedule,  it will take place on the 29th of March. 
> Unfortunately, I won't be able to attend, so someone else needs to 
> take  over of the remaining organization steps. Below you can 
> find a link to a new poll: 
> [https://terminplaner6.dfn.de/p/816c4fa5501d88438a4ffd49e727f5b7-16593
> 3](https://terminplaner6.dfn.de/p/816c4fa5501d88438a4ffd49e727f5b7-165
> 933)
>
> Please be aware that you can scroll horizontally ;)
>
> Best
> Tim

RE: [DISCUSS] Next community meeting

[Dominik Riemer]

Hi,

looking at the Doodle, it seems 5pm would be a good time for tomorrow's meeting.

If that's fine for you, I'll send around a link.

Cheers
Dominik


-Original Message-
From: Florian Micklich  
Sent: Monday, March 27, 2023 11:37 PM
To: dev@streampipes.apache.org
Subject: Re: [DISCUSS] Next community meeting


Hi,

just saw this message.
Who would attend? I can organise it due Tim has no time.
The main topic is variables in StreamPipes by Dominik, as I can remember from 
last time.

Is this still the case?
The other topics will be discussed during the meeting.

Florian




Am Montag, dem 13.03.2023 um 11:36 + schrieb Tim:
> Hi all,
> 
> it's time for our next community meeting! With respect to our 
> schedule,  it will take place on the 29th of March. 
> Unfortunately, I won't be able to attend, so someone else needs to 
> take  over of the remaining organization steps. Below you can 
> find a link to a new poll:  
> [https://terminplaner6.dfn.de/p/816c4fa5501d88438a4ffd49e727f5b7-16593
> 3](https://terminplaner6.dfn.de/p/816c4fa5501d88438a4ffd49e727f5b7-165
> 933)
> 
> Please be aware that you can scroll horizontally ;)
> 
> Best
> Tim

New Github Actions Infra Policy

[Dominik Riemer]

Hi,

Infra has activated a new "always require approval for external contributors" 
policy. This means that all Github actions workflows in PRs from contributors 
who or not PMC members or committers need to be manually started.
I personally think that this doesn't fit very well with our development model - 
I typically only review PRs after all checks were executed successfully so I 
don't see any advantage here and it will also slow down our PR process.

There were already some tickets from other projects asking for an exemption of 
this new policy, e.g., Beam [1] and Airflow [2].
Should we also ask for an exemption?

Cheers
Dominik


[1] https://issues.apache.org/jira/browse/INFRA-24200
[2] https://issues.apache.org/jira/browse/INFRA-24201

RE: [ANNOUNCE] New committer Steve Yurong Su

[Dominik Riemer]

Hi Steve,

congratulations!
Thanks a lot for the many and really cool contributions you've made so far and 
I'm really looking forward to continuing working with you on the project!

Cheers
Dominik


-Original Message-
From: Philipp Zehnder  
Sent: Monday, February 27, 2023 1:21 PM
To: dev@streampipes.apache.org
Subject: [ANNOUNCE] New committer Steve Yurong Su

Hi all,

on behalf of the StreamPipes PMC, it is my pleasure to inform you that Steve 
Yurong Su has accepted the offer to become committer of the StreamPipes project!

We are delighted to have you join us and are looking forward to collaborating 
with you.
Your contributions thus far have been impressive, including several PRs that 
introduced new processors, sinks, and adapters, and your active involvement in 
discussions.

Congratulations, I am really looking forward to further work with you!

Cheers,
Philipp

RE: [DRAFT] February Board Report

[Dominik Riemer]

+1
Thanks for preparing the report, Philipp!

Dominik


-Original Message-
From: Christofer Dutz  
Sent: Monday, February 6, 2023 1:47 PM
To: dev@streampipes.apache.org
Subject: Re: [DRAFT] February Board Report

+1  ... like it ;-)

From: Philipp Zehnder 
Date: Monday, 6. February 2023 at 13:38
To: dev@streampipes.apache.org 
Subject: AW: [DRAFT] February Board Report Hi all,

here is the draft board report. Please let me know if you have any additional 
points.

## Description:
The mission of Apache StreamPipes is the creation and maintenance of software 
related to a self-service Industrial IoT toolbox which enables non-technical 
users to connect, analyze and explore IoT data streams

## Issues:
No Issues

## Membership Data:
Apache StreamPipes was founded 2022-11-16 (3 months ago) There are currently 25 
committers and 14 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:4.

Community changes, past quarter:
- Zike Yang was added to the PMC on 2022-11-26
- Cedric Kulbach was added as committer on 2022-12-15
- Sven Oehler was added as committer on 2022-12-15
- Samuel Abt was added as committer on 2023-01-17
- Xin Wang was added as committer on 2022-11-25

## Project Activity:
  -  Work on the Python Client continues to progress
  -  Version 0.90.0 was released (January 17th 2023) [1]
  -  The discussion for the next release has already started on the mailing 
list [2]
  -  The project has updated its third-party service dependencies
  -  The team is working to simplify the model used in the background to make 
it easier to use and understand, especially for new developers.

## Community Health:
-  The project recently held its first online community meeting, which was a 
success. The meeting details can be found here [3] and were also distributed to 
the dev list
-  The mailing list has seen a constant increase in traffic, with December's 
count at 468 and January's count at 734
-  The switch to GitHub discussions has led to an increase in mailing list 
traffic, and we've tried several settings to make the list manageable again


[1] https://github.com/apache/streampipes/blob/release/0.90.0/RELEASE_NOTES.md
[2] 
https://lists.apache.org/list?dev@streampipes.apache.org:lte=1M:Already%20time%20for%20preparing%20the%20next%20release
[3] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=240881564

Cheers,
Philipp



Von: Philipp Zehnder 
Datum: Dienstag, 31. Januar 2023 um 18:29
An: dev@streampipes.apache.org 
Betreff: AW: [DRAFT] February Board Report Hi Chris,

thanks a lot, I will add it.

Cheers,
Philipp

Von: Christofer Dutz 
Datum: Dienstag, 31. Januar 2023 um 18:27
An: dev@streampipes.apache.org 
Betreff: Re: [DRAFT] February Board Report Hi Philip,

Well I would add in "community health" that after enabling github discussions a 
lot of discussions started but the emails completely swamped the mailinglists 
and we're trying to use different settings in order to make the list manageable 
again (This would be the sort of thing that I as a board-member would be 
looking for)

Chris

From: Philipp Zehnder 
Date: Tuesday, 31. January 2023 at 17:49
To: dev@streampipes.apache.org 
Subject: [DRAFT] February Board Report
Hi all,

we have yet to produce one of the monthly reports. After that, then only once a 
quarter.
Below is the report template. If you have points you can send them and I will 
add them:

## Description:
The mission of Apache StreamPipes is the creation and maintenance of software 
related to a self-service Industrial IoT toolbox which enables non-technical 
users to connect, analyze and explore IoT data streams

## Issues:
[Insert your own data here]

## Membership Data:
Apache StreamPipes was founded 2022-11-16 (3 months ago) There are currently 25 
committers and 14 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:4.

Community changes, past quarter:
- Zike Yang was added to the PMC on 2022-11-26
- Cedric Kulbach was added as committer on 2022-12-15
- Sven Oehler was added as committer on 2022-12-15
- Samuel Abt was added as committer on 2023-01-17
- Xin Wang was added as committer on 2022-11-25

## Project Activity:
[Insert your own data here]

## Community Health:
[Insert your own data here]


Cheers,
Philipp

Helm Charts

[Dominik Riemer]

Hi everyone,

I played around a bit with our helm charts for k8s deployment and these are 
quite prototypical and have many things we can improve (e.g., in terms of 
volumes, configuration options, services).
It would be great to improve these so that we can potentially also provide 
these helm charts as convenience artifact as part of our release process.

Does anyone of you have experience in building Helm charts and wants to help or 
guide me in improving them?

Cheers
Dominik

RE: [DISCUSS] Already time for preparing the next release?

[Dominik Riemer]

Hi Tim,

thanks for volunteering!

From my side, I'd like to include dependency updates of our third-party 
services to the next release (CouchDb, Consul and Influx). Apart from that, I'm 
totally +1 for faster release cycles 

So I hope I have at least to of the three updates ready be next week.

Cheers
Dominik


-Original Message-
From: Tim  
Sent: Thursday, January 26, 2023 7:15 PM
To: Dev 
Subject: [DISCUSS] Already time for preparing the next release?

Hi all,

Although we only recently shipped version 0.90.0, we already have merge
63 PRs since we cut our release branch.
Additionally, we merged a lot of dependency updates as well.

Therefore, I would like to propose that we create a new branch for an upcoming 
0.91.0 release soon.
How do you like it? Is there anything that should be included in the release?

I'd suggest not to start the release process directly, but to observe for a 
while if version 0.91.0 is stable.
This might be a good idea since we have touched a lot of code and upgraded a 
lot of dependencies.

Also, I would volunteer to be the release manager for this version.
I look forward to hearing your thoughts.

Best
Tim

RE: AW: Updating the notification schema for GitHub?

[Dominik Riemer]

Hi,

I've updated the asf.yaml according to the PLC4X scheme.

You can find the PR here:
https://github.com/apache/streampipes/pull/1163

Cheers
Dominik


-Original Message-
From: Tim  
Sent: Wednesday, January 25, 2023 5:59 PM
To: dev@streampipes.apache.org
Subject: Re: AW: Updating the notification schema for GitHub?

Hi all,

I'm also in favor of applying the notification schema that PLC4x uses.
Let's try that out and see how this improves our notification mess.

+1 for Philipp's idea to name PRs consistently, but I'd handle this in a 
seperate discussion.

Best
Tim

Am 23.01.2023 17:06 schrieb Philipp Zehnder:
> Hi,
> 
> I like the changes Chris suggested. This week we have a community call
> (see [1]).
> There we will talk about the change from JIRA to GitHub. I suggest
> talking about this as well and then changing the configurations
> accordingly.
> Maybe we can also talk about a convention to set the name for PRs.
> 
> Cheers,
> Philipp
> 
> Von: Christofer Dutz 
> Datum: Montag, 23. Januar 2023 um 11:45
> An: dev@streampipes.apache.org 
> Betreff: Re: Updating the notification schema for GitHub?
> Well, a PR is a PR and an Issue is an Issue …
> 
> If there’s an issue related to a PR … well that’s one thing we can’t
> automate … there will be two email threads.
> But everything is better than the way it currently is … for me without
> any changes this list is unusable.
> 
> Chris
> 
> 
> 
> From: Dominik Riemer 
> Date: Monday, 23. January 2023 at 09:51
> To: dev@streampipes.apache.org 
> Subject: RE: Updating the notification schema for GitHub?
> Hi Chris,
> 
> thanks for the hint, that's a very useful new feature!
> 
> So we could add the same configuration as PLC4X:
> 
>   # Attempt to make the auto-generated github emails more easily
> readable in email clients.
>   custom_subjects:
> new_pr: "[PR] {title} ({repository})"
> close_pr: "Re: [PR] {title} ({repository})"
> comment_pr: "Re: [PR] {title} ({repository})"
> diffcomment: "Re: [PR] {title} ({repository})"
> merge_pr: "Re: [PR] {title} ({repository})"
> new_issue: "[I] {title} ({repository})"
> comment_issue: "Re: [I] {title} ({repository})"
> close_issue: "Re: [I] {title} ({repository})"
> catchall: "[GH] {title} ({repository})"
> 
> Do we need to pay attention that the PR titles match the related issue
> titles with this config?
> 
> What do others think?
> 
> Best,
> Dominik
> 
> 
> -Original Message-
> From: Christofer Dutz 
> Sent: Saturday, January 21, 2023 6:38 PM
> To: dev@streampipes.apache.org
> Subject: Updating the notification schema for GitHub?
> 
> Hi all,
> 
> GitHub emails have been annoying in this project for quite some time,
> with the increased usage of discussions, this has become worse.
> This is not something unique to StreamPipes, but also happens in other 
> projects.
> 
> I did manage to convince Infra to update their notification bot to
> customize the email subjects of auto-generated emails.
> https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-Notificationsettingsforrepositories
> 
> I have updated the settings in PLC4X and now both my email-client as
> also lists.apache.org can correctly thread the emails.
> 
> Perhaps something worth discussing on changing here too?
> 
> https://github.com/apache/plc4x/blob/develop/.asf.yaml
> 
> What do you folks think?
> 
> 
> Chris

RE: [ANNOUNCE] First StreamPipes Community Event

[Dominik Riemer]

Thanks Tim for organizing the event and to everyone who participated!

Looking forward to see even more community members at the next meeting, always 
welcome 

Cheers
Dominik


-Original Message-
From: Tim  
Sent: Wednesday, January 25, 2023 5:55 PM
To: Dev 
Subject: Re: [ANNOUNCE] First StreamPipes Community Event

Thanks to everyone who attended our community meeting.
It was a lot of fun and I personally enjoyed talking with all of you face to 
face about StreamPipes.

For those of you who weren't there, we've written some notes about what we 
discussed [1].
Many thanks to @Dominik for that

I'm looking forward to our next community event, which will be on February 22.

Best
Tim

[1]
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=240881564

Am 24.01.2023 22:23 schrieb Tim:
> Hi everyone,
> 
> Don't miss our first StreamPipes community event tomorrow.
> We start at 8am UTC and you can participate by using the Google Meet 
> link below.
> 
> Best
> Tim
> 
> 
> Am 19.01.2023 20:00 schrieb Tim:
>> Hi all,
>> 
>> the die is cast!
>> We will be holding our first StreamPipes community event on January 
>> 25 at 8am UTC.
>> To participate, simply join our Google Meet session at:
>> https://meet.google.com/zso-bxuu-fdo
>> 
>> I really look forward to meeting all of you.
>> 
>> Best
>> Tim

RE: Python Wrapper

[Dominik Riemer]

Hi Cedric,



Although I'm not fully aware of the wrapper:

It seems that the extension service's host is set to "consul" but should be the 
hostname or IP of the machine where the service is started.

I think there is another env variable which you can set called 
"CONSUL_LOCATION" which sets the hostname of the consul instance (this can be 
localhost for local testing).



Dominik





From: Cedric Kulbach 
Sent: Tuesday, January 24, 2023 1:53 PM
To: dev@streampipes.apache.org
Subject: Python Wrapper



Hi all,



I'm currently trying to run and refactor the python 
wrapper.

Within the example provided in the 
README.md
 and some minor changes with the imports, I'm able to run the 
HelloWorldProcessor and to register it in consul.

However, I still get an error from the processor in consul (see appendix), even 
when changing the host to "localhost".



Does anyone know what the reason is, or would anyone like to build an MVP for 
the wrapper?



Best

Cedric

RE: Usage of Github Discussions

[Dominik Riemer]

Hi Chris,

forwarding discussions to the list is already an asf.yaml feature.

See [1] for the settings and it also seems that all our discussions are 
forwarded to the dev list, e.g. [2] (another reason why so many Github mails 
appear on the dev list) 

Dominik

[1] https://github.com/apache/streampipes/blob/dev/.asf.yaml
[2] https://lists.apache.org/thread/jr9d18ow367bq3vovh6blxqsnlordpj3


-Original Message-
From: Christofer Dutz  
Sent: Monday, January 23, 2023 2:26 PM
To: dev@streampipes.apache.org
Subject: Usage of Github Discussions

Hi all,

while I’m currently focusing on helping communication work again for Apache, 
after mis-configured tools were flooding the lists and hereby rendering them 
useless.
I did stumble over the fact that the StreamPipes community seems to have 
switched to using GitHub Discussions.

While in general there are no objections to this for providing support to 
users, I do however see quite a problem on how it seems to be used.
It seems stuff is being discussed there, that would need to be on the list too.

Right now, only very little information at all is going to the list, this is 
not ideal. …. Well, it’s actually bad as it’s against the Apache policy of 
having the important stuff on the list. (Not just votes)

I think Infra is currently working on some service to replicate GitHub 
Discussions to the list, and together with the latest updates it might even 
produce readable output, but till that’s done, I think we should limit the 
usage of GitHub Discussions.

Chris

RE: Updating the notification schema for GitHub?

[Dominik Riemer]

Hi Chris,

thanks for the hint, that's a very useful new feature!

So we could add the same configuration as PLC4X:

  # Attempt to make the auto-generated github emails more easily readable in 
email clients.
  custom_subjects:
new_pr: "[PR] {title} ({repository})"
close_pr: "Re: [PR] {title} ({repository})"
comment_pr: "Re: [PR] {title} ({repository})"
diffcomment: "Re: [PR] {title} ({repository})"
merge_pr: "Re: [PR] {title} ({repository})"
new_issue: "[I] {title} ({repository})"
comment_issue: "Re: [I] {title} ({repository})"
close_issue: "Re: [I] {title} ({repository})"
catchall: "[GH] {title} ({repository})"

Do we need to pay attention that the PR titles match the related issue titles 
with this config?

What do others think?

Best,
Dominik


-Original Message-
From: Christofer Dutz  
Sent: Saturday, January 21, 2023 6:38 PM
To: dev@streampipes.apache.org
Subject: Updating the notification schema for GitHub?

Hi all,

GitHub emails have been annoying in this project for quite some time, with the 
increased usage of discussions, this has become worse.
This is not something unique to StreamPipes, but also happens in other projects.

I did manage to convince Infra to update their notification bot to customize 
the email subjects of auto-generated emails.
https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-Notificationsettingsforrepositories

I have updated the settings in PLC4X and now both my email-client as also 
lists.apache.org can correctly thread the emails.

Perhaps something worth discussing on changing here too?

https://github.com/apache/plc4x/blob/develop/.asf.yaml

What do you folks think?


Chris

[ANNOUNCE] Apache StreamPipes 0.90.0

[Dominik Riemer]

The Apache StreamPipes community is pleased to announce the immediate
availability of Apache StreamPipes 0.90.0!

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

This release closes 57 issues with a focus on bug fixes and improvements.
It brings several new adapters and data sinks for Nats, RocketMQ and
Pulsar and includes many usability and performance improvements to the
data explorer.

An summary of the release highlights can be found in our blog post:
https://streampipes.apache.org/docs/blog/2023/01/17/release-090.html

The release is available for download on our website:
https://streampipes.apache.org/download

To get an overview of Apache StreamPipes, find a feature overview and tour at:
https://streampipes.apache.org/feature-overview.html
https://streampipes.apache.org/docs/docs/user-guide-introduction.html

More information about the project is available at:
- Website: https://streampipes.apache.org
- Github: https://github.com/apache/streampipes
- Mailing lists: dev@streampipes.apache.org, us...@streampipes.apache.org

Thanks a lot to everyone who contributed to this release!

On behalf of the Apache StreamPipes community,
Dominik

[ANNOUNCE] New PMC member & committer

[Dominik Riemer]

Hi all,

during all the graduation tasks, I totally forgot to announce on behalf of the 
PMC that Zike Yang has accepted the offer to join the PMC and Xin Wang has 
joined as a new committer.
Although this has already happened by the end of last year, I'd like to warmly 
welcome you and thanks a lot for contributing to our community project!

Congratulations to both of you!

Dominik

RE: [ANNOUNCE] New committer Samuel Abt

[Dominik Riemer]

Congrats Samuel!



-Original Message-
From: Philipp Zehnder  
Sent: Wednesday, January 18, 2023 9:11 PM
To: dev@streampipes.apache.org
Subject: AW: [ANNOUNCE] New committer Samuel Abt

Hi all,

Congratulations Samuel, I'm really glad you're still a part of the StreamPipes 
community!
It's great to work together.

Cheers,
Philipp

Von: Tim 
Datum: Mittwoch, 18. Januar 2023 um 20:36
An: Dev 
Betreff: [ANNOUNCE] New committer Samuel Abt Hi all,

on behalf of the StreamPipes PMC, it is my pleasure to inform you that Samuel 
Abt has accepted the offer to become committer of the StreamPipes project!

Congratulations Samuel, I'm super happy to have you on board!
You already shaped StreamPipes in it's early days before the Apache Foundation 
and are now very actively contributing to StreamPipes again.
In doing so, you have already made awesome contributionswith a strong focus on 
the UI and started initiatives to establish best practives and improve the 
codebase.


Cheers
Tim

[RESULT][VOTE] Apache StreamPipes 0.90.0 RC1 release

[Dominik Riemer]

Hi all,

the vote has now closed after the 72h period has passed.
The vote PASSES with 6 votes +1 (4 binding/2 non-binding) and no -1.


+1 (binding)
Tim Bossenmaier
Philipp Zehnder
Patrick Wiener
Dominik Riemer

+1 (non-binding)
Lukas Ott
Sven Oehler

Vote thread: https://lists.apache.org/thread/41y6j4d54vh061ow2rwcl6vzzmk12f23

Thanks a lot to everyone for taking your time to review our release candidate! 
I will proceed with publishing the approved artifacts and send out the 
announcements in the coming days.

Dominik

RE: [VOTE] Apache StreamPipes 0.90.0 RC1 release

[Dominik Riemer]

+1 (binding)

[x] Download all staged artifacts under the url specified in the release vote 
email 
[x] Verify the signature is correct 
[x] Check if the signature references an Apache email address 
[x] Verify the SHA512 checksum 
[x] Unzip the archive 
[x] Verify the existence of LICENSE, NOTICE, README, RELEASE_NOTES, 
RELEASE_VALIDATION files in the extracted source bundle.
[x] Run RAT
[x] Search for SNAPSHOT dependencies
[x] Build Backend
[x] Build UI
[x] Build and Run Test system on Docker
[x] Build archetype project

Build with: 
- Windows 11, WSL2
- OpenJDK 18.0.2
- Node 16.14.0
- NPM 8.3.1

Cheers
Dominik

-Original Message-
From: Dominik Riemer 
Sent: Monday, January 9, 2023 8:46 AM
To: dev@streampipes.apache.org
Subject: [VOTE] Apache StreamPipes 0.90.0 RC1 release 

Hi all,

Apache StreamPipes 0.90.0 has been staged and it's time to vote on accepting it 
for release. 
Voting will be open for at least 72 hours. 
A minimum of 3 binding +1 votes and more binding +1 than binding -1 are 
required to pass, but everyone is welcome to vote! 

One artifact is relevant for this vote: 

streampipes, staged at [1], available in Nexus at [2], release tag: 
release/0.90.0, hash for the release tag: 
4a9a8f38e0bcd4dbea7e859445eabef6f24235e1

Per [3] "Before voting +1, PMC members are required to download the signed 
source code package, compile it as provided, and test the resulting executable 
on their own platform, along with also verifying that the package meets the 
requirements of the ASF policy on releases." 

A release validation guide is available at [4]. The KEYS file is available at 
[5] 

[ ] +1 accept (indicate what you validated - e.g. performed the checklist at 
the end of [4]) [ ] -1 reject (explanation required) 

Thanks for taking your time for validating this release!

Cheers
Dominik


[1] https://dist.apache.org/repos/dist/dev/streampipes/0.90.0/rc1/
[2] 
https://repository.apache.org/content/repositories/orgapachestreampipes-1020/
[3] https://www.apache.org/dev/release.html#approving-a-release
[4] https://cwiki.apache.org/confluence/display/STREAMPIPES/Validating+a+release
[5] https://downloads.apache.org/streampipes/KEYS

License Header in PR notifications

[Dominik Riemer]

Hi,

should we remove the license header from the PR template? As it is included in 
every email in the body, it just makes reading PR info much more difficult, and 
I don't think there is any requirement to include the license header in PR 
notifications.
We could simply add the PR template file to the rat exclusions.

Cheers
DOminik

RE: AW: [DISCUSS] When to run the integration tests?

[Dominik Riemer]

Hi,
just answering again as it seems the Ponymail web interface has somehow eaten 
my last message.

I like the idea to add more control over which tests are running when. As a 
user, when downloading a release, I would expect that all tests are running 
(Junit + Integration Tests) by default when doing an mvn package.
So I would prefer to add a skip flag which skips certain tests by explicit 
command.
E.g., as -DskipTests is the standard command to run the build without any 
tests, we could have some flag such as -DskipIntegrationTests which skips the 
integration tests, but I'm not in favor of having this as default or require a 
specific profile.

Cheers
Dominik


-Original Message-
From: Tim  
Sent: Friday, January 6, 2023 11:10 AM
To: dev@streampipes.apache.org
Subject: Re: AW: [DISCUSS] When to run the integration tests?

Hi Philipp,

I think JUnit's categories could be a solution for this idea.
Base on this stack overflow reference [1] and a blog post [3], I have created a 
minimal example (see here [2]).
With this setup you could run unit tests ("mvn clean test -P UnitTests") apart 
from integration tests ("mvn clean test -P IntegrationTests").
The downside of the current setup is that we would need to categorize every 
existing test but maybe there is also another way how to define the maven 
profiles resp. test groups.

Unfortunately, this runs not out of the box due to some dependecy issues which 
I couldn't resolve immediately.

In case we want to follow up on that idea, we can investigate further.

Best
Tim


[1] https://stackoverflow.com/a/18297553
[2]
https://github.com/apache/streampipes/tree/experimental/test-categories
[3]
https://technicaltesting.wordpress.com/2012/09/24/using-junit-category-and-maven-profiles-to-get-stable-test-suites/



Am 04.01.2023 17:21 schrieb Philipp Zehnder:
> Hi Tim,
> 
> I agree. I think it makes sense to run them once a day. We could 
> integrate them into our nightly test pipeline [1].
> However, I am not sure how to configure maven accordingly. Our goal 
> would be to exclude the integration tests from the regular unit tests 
> and “only” run them during the nightly build.
> 
> Is this a problem that could be solved with prefixes or suffixes of 
> the tests?
> 
> Cheers,
> Philipp
> 
> [1]
> https://github.com/apache/streampipes/blob/dev/.github/workflows/cypre
> ss-test.yml
> 
> 
> Von: Tim 
> Datum: Mittwoch, 4. Januar 2023 um 17:08
> An: dev@streampipes.apache.org 
> Betreff: Re: [DISCUSS] When to run the integration tests?
> Hi Philipp,
> 
> I like the idea of having a (dedicated?) CI pipeline for our 
> integration tests.
> How do you think about running them once per day (probably somewhen in 
> the night) or once per week?
> 
> Is there a possibility to work with contexts or flags in Maven?
> Maybe something towards this direction could allow us to carve out the 
> integration tests.
> 
> Best
> Tim
> 
> Am 03.01.2023 10:49 schrieb Philipp Zehnder:
>> Hi all,
>> 
>> in PR [1] we fixed the unit tests and added them to the GitHub 
>> actions build pipeline.
>> When I ran the unit tests locally, I saw that the new module 
>> "streampipes-integration-test" was also executed.
>> 
>> I wanted to discuss when to run these tests. When I ran `mvn clean 
>> test` locally, it started downloading Docker containers and the 
>> integration tests took over two minutes.
>> I think this is too long for unit tests. So, my suggestion would be 
>> to run them only in the CI/CD pipeline and skip when a developer "only"
>> runs the unit test.
>> 
>> What do you think and how could we configure such behavior?
>> 
>> Cheers,
>> Philipp

Re: AW: [DISCUSS] When to run the integration tests?

[Dominik Riemer]

Hi,
yes, we could use some flag to control execution of certain flags.
I would be in favor of having a default which runs all tests (e.g., as a user 
that downloads our release and performs an mvn package, I would expect that all 
Junit and integration tests are running).
So similar to the -DskipTests flag that disables Junit flags in Maven, we could 
have something like -DskipIntegrationTests which skips integration tests only, 
but in my opinion this should be explicitly called and not be the default.

Best
Dominik

On 2023/01/06 10:10:04 Tim wrote:
> Hi Philipp,
> 
> I think JUnit's categories could be a solution for this idea.
> Base on this stack overflow reference [1] and a blog post [3], I have 
> created a minimal example (see here [2]).
> With this setup you could run unit tests ("mvn clean test -P UnitTests") 
> apart from integration tests ("mvn clean test -P IntegrationTests").
> The downside of the current setup is that we would need to categorize 
> every existing test but maybe there is also another way how to define 
> the maven profiles resp. test groups.
> 
> Unfortunately, this runs not out of the box due to some dependecy issues 
> which I couldn't resolve immediately.
> 
> In case we want to follow up on that idea, we can investigate further.
> 
> Best
> Tim
> 
> 
> [1] https://stackoverflow.com/a/18297553
> [2] 
> https://github.com/apache/streampipes/tree/experimental/test-categories
> [3] 
> https://technicaltesting.wordpress.com/2012/09/24/using-junit-category-and-maven-profiles-to-get-stable-test-suites/
> 
> 
> 
> Am 04.01.2023 17:21 schrieb Philipp Zehnder:
> > Hi Tim,
> > 
> > I agree. I think it makes sense to run them once a day. We could
> > integrate them into our nightly test pipeline [1].
> > However, I am not sure how to configure maven accordingly. Our goal
> > would be to exclude the integration tests from the regular unit tests
> > and “only” run them during the nightly build.
> > 
> > Is this a problem that could be solved with prefixes or suffixes of the 
> > tests?
> > 
> > Cheers,
> > Philipp
> > 
> > [1]
> > https://github.com/apache/streampipes/blob/dev/.github/workflows/cypress-test.yml
> > 
> > 
> > Von: Tim 
> > Datum: Mittwoch, 4. Januar 2023 um 17:08
> > An: dev@streampipes.apache.org 
> > Betreff: Re: [DISCUSS] When to run the integration tests?
> > Hi Philipp,
> > 
> > I like the idea of having a (dedicated?) CI pipeline for our 
> > integration
> > tests.
> > How do you think about running them once per day (probably somewhen in
> > the night) or once per week?
> > 
> > Is there a possibility to work with contexts or flags in Maven?
> > Maybe something towards this direction could allow us to carve out the
> > integration tests.
> > 
> > Best
> > Tim
> > 
> > Am 03.01.2023 10:49 schrieb Philipp Zehnder:
> >> Hi all,
> >> 
> >> in PR [1] we fixed the unit tests and added them to the GitHub actions
> >> build pipeline.
> >> When I ran the unit tests locally, I saw that the new module
> >> "streampipes-integration-test" was also executed.
> >> 
> >> I wanted to discuss when to run these tests. When I ran `mvn clean
> >> test` locally, it started downloading Docker containers and the
> >> integration tests took over two minutes.
> >> I think this is too long for unit tests. So, my suggestion would be to
> >> run them only in the CI/CD pipeline and skip when a developer "only"
> >> runs the unit test.
> >> 
> >> What do you think and how could we configure such behavior?
> >> 
> >> Cheers,
> >> Philipp
> 

[DISCUSS][VOTE] Apache StreamPipes 0.90.0 RC1 release

[Dominik Riemer]

Hi,

this thread is to discuss issues around the 0.90.0 release vote.

@Lukas, thanks for testing the release!
I tried to reproduce your error by running the build under WSL Ubuntu 22.04 
with OpenJDK 18.0.2ea and the build works fine.

Do you have any special setup so that we can investigate the issue? Did you get 
any further output for the tests that are failing? For some background, the 
integration test module makes use of testcontainers [1] and downloads some 
Docker images during the build process - so maybe the failed build is related 
to some download issue instead of failing tests?

Cheers
Dominik

[1] https://www.testcontainers.org/

RE: [DRAFT] January Board Report

[Dominik Riemer]

Hi Philipp,
thanks for creating the report! I don't have any comments.

Cheers
Dominik


-Original Message-
From: Philipp Zehnder  
Sent: Tuesday, January 10, 2023 9:18 AM
To: dev@streampipes.apache.org
Subject: [DRAFT] January Board Report

Hi all,

I have created a draft of the board report. Please provide feedback if I missed 
something or you have something to add:

## Description:
The mission of Apache StreamPipes is the creation and maintenance of software 
related to a self-service Industrial IoT toolbox which enables non-technical 
users to connect, analyze and explore IoT data streams

## Issues:
No Issues

## Membership Data:
Apache StreamPipes was founded 2022-11-16 (2 months ago) There are currently 24 
committers and 14 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.

Community changes, past quarter:
- Zike Yang was added to the PMC on 2022-11-26
- Cedric Kulbach was added as committer on 2022-12-15
- Sven Oehler was added as committer on 2022-12-15
- Xin Wang was added as committer on 2022-11-25

## Project Activity:
- Improve the setup of GitHub to make it more friendly for new developers
  - e.g. mark more issues with the tag 'good first issue'
- The project is currently in the release process for version 0.90.0
  - Last release (0.70.0) October 13, 2022
- Code improvement, dependency update and code base cleanup


## Community Health:
- Constantly growing traffic on the mailing list (November: 399, December: 468).
- Several PRs were submitted by new developers
- Organization of the first community call for the end of January


Cheers,
Philipp

[VOTE] Apache StreamPipes 0.90.0 RC1 release

[Dominik Riemer]

Hi all,

Apache StreamPipes 0.90.0 has been staged and it's time to vote on accepting it 
for release. 
Voting will be open for at least 72 hours. 
A minimum of 3 binding +1 votes and more binding +1 than binding -1 are 
required to pass, but everyone is welcome to vote! 

One artifact is relevant for this vote: 

streampipes, staged at [1], available in Nexus at [2], release tag: 
release/0.90.0, hash for the release tag: 
4a9a8f38e0bcd4dbea7e859445eabef6f24235e1

Per [3] "Before voting +1, PMC members are required to download the signed 
source code package, 
compile it as provided, and test the resulting executable on their own 
platform, 
along with also verifying that the package meets the requirements of the ASF 
policy on releases." 

A release validation guide is available at [4]. The KEYS file is available at 
[5] 

[ ] +1 accept (indicate what you validated - e.g. performed the checklist at 
the end of [4]) 
[ ] -1 reject (explanation required) 

Thanks for taking your time for validating this release!

Cheers
Dominik


[1] https://dist.apache.org/repos/dist/dev/streampipes/0.90.0/rc1/
[2] 
https://repository.apache.org/content/repositories/orgapachestreampipes-1020/
[3] https://www.apache.org/dev/release.html#approving-a-release 
[4] 
https://cwiki.apache.org/confluence/display/STREAMPIPES/Validating+a+release 
[5] https://downloads.apache.org/streampipes/KEYS

RE: loosing track of too many emails about github

[Dominik Riemer]

Hi,
I think the main reason for the currently high message volume is that we use 
pull request to a much greater extent.
We are already sending all issue notifications (created and closed issues + 
issue comments) to iss...@streampipes.apache.org, which has only few 
subscribers.
By looking at asf.yaml configuration options, we could also forward all pull 
request notifications to the issues list (or a newly created separate list?).
The drawback is that less people would see discussions related to PRs and maybe 
that's a good way for new users to follow current work, but I agree that it's 
not easy to follow at the current mail volume.

Cheers
Dominik



-Original Message-
From: Florian Micklich  
Sent: Thursday, January 5, 2023 11:11 PM
To: StreanPipes Dev 
Subject: loosing track of too many emails about github

Hi,

after moving to GitHub with the discussion and issues, my email inbox is 
exploding and I am loosing track of important messages.
For example I did not recognise that I was asked something by mentioning my 
name, just because there are too many emails.

On the one hand it is a good sign of activity.
On the other hand I have way to many emails.

So how do you organise the emails yourself?
I am subscribed to the commits and dev email list.

The Email notification from my GitHub account are separated from this, but 
still to many as well.

Greetings
Florian

 

RE: [DISCUSS] siddhi processors do not work with the new antlr version

[Dominik Riemer]

Hi Grainier,
that's awesome, thanks a lot!

Cheers
Dominik


-Original Message-
From: Grainier Perera  
Sent: Tuesday, January 3, 2023 4:08 PM
To: dev@streampipes.apache.org
Subject: Re: [DISCUSS] siddhi processors do not work with the new antlr version

Quick update, We've released Siddhi v5.1.27 with ANTLR v4.11.1. However, it'll 
take some time to be synced with the public maven repository. Once available, 
I'll test it and send a PR to SP.

Regards,
Grainier Perera.


On Mon, 2 Jan 2023 at 22:03, Philipp Zehnder 
wrote:

> Cool, thanks a lot.
> Let me know if there is anything I can help you with.
>
> Cheers,
> Philipp
>
> Von: Grainier Perera 
> Datum: Montag, 2. Januar 2023 um 16:17
> An: Philipp Zehnder 
> Cc: dev@streampipes.apache.org 
> Betreff: Re: [DISCUSS] siddhi processors do not work with the new 
> antlr version Hi Philipp,
>
> I'll look into the possibility of getting the ANTLR version bumped to
> v4.11.1 in Siddhi.
>
> Regards,
> Grainier Perera.
>
>
> On Mon, 2 Jan 2023 at 19:48, Philipp Zehnder < 
> philipp.zehn...@bytefabrik.ai>
> wrote:
>
> > Hi all,
> >
> >
> >
> > the Siddhi processors do not work with the new ANTLR version (4.11.1).
> >
> >
> >
> > ANTLR is used as a dependency in both Siddhi 
> > (streampipes-wrapper-siddhi) and PLC4X (streampipes-extensions-all-jvm).
> >
> > So far, we have been using ANTRL version 4.9 and everything worked fine.
> > However, with the update of ANTRL to version 4.11.1, the siddhi
> components
> > stopped working. The problem seems to be that ANTLR version 4.10, 
> > introduced braking changes (see [1]).
> >
> >
> >
> > For now, we can stay on the old ANTLR version (see [2]), but as soon 
> > as
> we
> > update PLC4X to the newest version (0.10.0) we will get the same 
> > problem, since this version also uses ANTLR (4.11.1).
> >
> >
> >
> > Does anyone have an idea what we can do?
> >
> > @Grainier do you know a workaround? Is it possible to update ANTLR 
> > in Siddhi?
> >
> >
> >
> > Cheers,
> >
> > Philipp
> >
> >
> >
> > [1] https://github.com/antlr/antlr4/releases
> >
> > [2] https://github.com/apache/streampipes/pull/1011
> >
>

RE: [DISCUSS] Report December

[Dominik Riemer]

Hi Philipp,

thanks for preparing the report, looks good from my side!

Cheers
Dominik



-Original Message-
From: Philipp Zehnder  
Sent: Tuesday, December 13, 2022 11:43 AM
To: dev@streampipes.apache.org
Subject: [DISCUSS] Report December 

Hi all,

we must submit our next board report tomorrow. I created a first draft.
If I forgot something or should change something, please comment.


# ASF Board Report December

## Description:

The mission of Apache StreamPipes is the creation and maintenance of software 
related to a self-service Industrial IoT toolbox which enables non-technical 
users to connect, analyze and explore IoT data streams

## Issues:

No Issues

## Membership Data:

Apache StreamPipes was founded 2022-11-16 (a month ago) There are currently 22 
committers and 14 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.

Community changes, past quarter:

- Zike Yang was added to the PMC on 2022-11-26
- Xin Wang was added as committer on 2022-11-25

## Project Activity:

- The ticket system was migrated from Jira to GitHub Issues
- We have also enabled GitHub Discussions to lower the barrier for discussions 
about problems and new features (with all discussions being forwarded to the 
dev-list)
- A release branch was created for the next release (0.90.0)
- A Python client is developed that gives Python developers access to the data 
processed in StreamPipes
- Several Bug fixes and improvements
- Resources have been transferred from the Incubator to the new PMC

## Community Health:

- Growing community with several new committers and a new PMC
- Increased traffic on the mailing list (October: 175, November: 399)
- Several new contributors appeared asking for help


Cheers,
Philipp

Release branch created

[Dominik Riemer]

Hi,

I've cut the release branch for the upcoming version 0.90.0:
https://github.com/apache/streampipes/tree/rel/0.90.0

Cheers
Dominik

RE: [DISCUSS] Plan to release StreamPipes 1.0

[Dominik Riemer]

Thanks for your feedback!

I am especially interested in the opinion from those of you haven't followed 
the project for years, as you have a "fresh" view on the system:
What do you think are the biggest pain points regarding usability or where do 
you see improvement potential?

I'll start a discussion on Github and we can collect any ideas there.

Cheers
DOminik


-Original Message-
From: Xin Wang  
Sent: Thursday, December 1, 2022 4:02 PM
To: dev@streampipes.apache.org
Subject: Re: [DISCUSS] Plan to release StreamPipes 1.0

Hi,

Agree with you. I think we should focus on usability improvements and mature 
APIs for the 1.0 release. It is more important for users.
Other non-critical features can be released in a later version.

Florian Micklich  于2022年11月27日周日 03:01写道：

> Hi,
>
> I think it really depends on the timing of when 1.0 is released.
>
> In my point if view, the geo operators should be part of the 1.0 
> release as "new features".
> And also focus on the documentation and story line using them O:-)
>
> Florian
>
>
>
>
>
>
> Am Freitag, dem 25.11.2022 um 09:27 + schrieb Philipp Zehnder:
> > Hi,
> >
> > I am also in favor of releasing a 1.0 version soon after the 0.90.0
> version.
> >
> > I think we do not need any new features for the 1.0 release. My 
> > suggestion would be to focus on usability improvements and bug fixes
> for the 1.0 release.
> > Especially that we have a backward compatible system and users can
> easily update to newer versions.
> > Do you have any ideas how we can ensure this? We need a way to test 
> > that
> updates work as expected and do not break anything.
> > It would be cool to have an automated approach to validate this for 
> > each
> release.
> >
> > Cheers,
> > Philipp
> >
> >
> > Von: Dominik Riemer 
> > <[rie...@apache.org](mailto:rie...@apache.org)>
> > Datum: Freitag, 25. November 2022 um 07:08
> > An: [dev@streampipes.apache.org](mailto:dev@streampipes.apache.org) 
> > <[
> dev@streampipes.apache.org](mailto:dev@streampipes.apache.org)>
> > Betreff: Re: [DISCUSS] Plan to release StreamPipes 1.0 Hi 
> > Xin,
> >
> > thanks for bringing up this important question! The current plan 
> > is to release a new version soon together with the TLP
> announcement, which is currently named "0.90.0".
> >
> > I totally agree that a 1.0 version gives more trust to users. So 
> > let's
> say we would go for a 1.0 release after 0.90.0, what do you all think 
> should be part of this release and what improvements should be done? 
> Are any mission-critical features missing?
> >
> > E.g., an important item on my list for the 1.0 release is increased 
> > test
> coverage.
> >
> > Cheers
> > Dominik
> >
> >
> > On 2022/11/25 05:07:54 Xin Wang wrote:
> > > The current StreamPipes version is 0.70. Do we have a plan to 
> > > release
> 1.0?
> > > Because 1.x version may make users feel more mature and stable, 
> > > what
> do you
> > > think?
> > >
> > >
> > > --
> > > Thanks,
> > > Xin
> > >
>


--
Thanks,
Xin

Next release?

[Dominik Riemer]

Hi everyone,

it seems most issues targeting the 0.90.0 milestone are finished or have open 
PRs.
So I suggest that we start planning the first post-graduation release so that 
we can also get the official graduation announcement on the way…

Is there anything against starting the release process?

I’d volunteer as a release manager for the next release (in case no one else 
wants to do it ) and we could cut the release branch in a few days.

Cheers
Dominik

RE: Add functionality of host.docker.internal for linux users?

[Dominik Riemer]

What Philipp says is that you don't have to configure the .env file, but that 
you can provide the env variable directly as a startup argument (e.g., in the 
IDE settings). This doesn't change your source code.

Dominik


-Original Message-
From: Florian Micklich  
Sent: Wednesday, November 30, 2022 1:01 PM
To: dev@streampipes.apache.org
Subject: Re: Add functionality of host.docker.internal for linux users?

Hi Philipp,

I guess we are talking at cross purposes :) Maybe for better understanding. How 
does auto discovery works with the CLI installer?
I thought the auto discovery is done with the host.docker.internal flag?

Everything is working after configure the SP_HOST in the environment list.
But this leads to a changed file in git in the 
../incubator-streampipes/.idea/runConfigurations folder e.g. 
all_pipeline_elements_jvm.xml due this folder / files are not in the gitignore 
list.

So I have to handle this in git all the time and for better programmer 
experiences I though we can add this little feature for linux users as well, so 
that everything is working without extra editing.

Greetings
Florian



Am Dienstag, dem 29.11.2022 um 10:15 + schrieb Philipp Zehnder:
> Hi Florian,
> 
> ah, sorry, I thought we don't have the IP problem anymore. You can 
> take a look at [1], the networking class implements auto-discovery of 
> the IP address. Maybe we can find a solution that will reliably 
> determine the IP address for Linux as well.
> 
> In the meantime, my tip would be to set the environment variable in 
> the IDE so you don't have any changes in the source files.
> 
> Cheers!
> Philipp
> 
> 
> Von: Florian Micklich 
> <[mickl...@apache.org](mailto:mickl...@apache.org)>
> Datum: Samstag, 26. November 2022 um 20:17
> An: [dev@streampipes.apache.org](mailto:dev@streampipes.apache.org) 
> <[dev@streampipes.apache.org](mailto:dev@streampipes.apache.org)>
> Betreff: Re: Add functionality of host.docker.internal for linux 
> users? Hi Philipp,
> 
> are you using Linux with the CLI installation? How is here auto 
> discovery possible? So I need to set the SP_HOST variable in my 
> environment or env file. This constantly results in a changed file in 
> git that I have to pay attention every time I commit, push, ... so I 
> don't accidentally commit it or clash into something else.
> 
> 
> As it is written here [1] on  Example walkthrough for 
> pipeline-elements-jvm-all in IntelliJ:
> -> For Linux user: You must change the environment variables stating 
> -> host.docker.internal to you local machine's IP.
> 
> So I think this will increase compatibility for Linux users to use the 
> default host.docker.internal.
> 
> ```
> >     extra_hosts:
> >   - "host.docker.internal:host-gateway"
> ```
> 
> Greetings
> Florian
> 
> P.S. A short poll, who uses which operating system, would be 
> interesting :-)
> 
> 
> 
> [1] 
> [https://cwiki.apache.org/confluence/display/STREAMPIPES/Extensions](h
> ttps://cwiki.apache.org/confluence/display/STREAMPIPES/Extensions)
> 
> 
> This is a service that wraps all pipeline elements written with the 
> standard Java wrapper, hence the the notion of "jvm-all".
> 
>     You should automatically have a run configuration 
> "all-pipeline-elements-jvm" as we ship in with the repository
>     (Optional) Modifiy environment variables depending on your OS 
> (this is due to the dev setup of partly IDE and partly Docker, we need 
> the local services to be reachable from within the Docker network)
>     For Windows/Mac user: you are good to go
>     For Linux user: You must change the environment variables 
> stating host.docker.internal to you local machine's IP
>     Run the service
>     Navigate to "[http://localhost:7023/](http://localhost:7023/)" to 
> see if the backend is running. You should see something similar to the 
> following:
> 
> Am Mittwoch, dem 23.11.2022 um 16:50 + schrieb Philipp 
> Zehnder:
> > Hi Florian,
> > 
> > what do you need “host.docker.internal” for?
> > 
> > I usually use the auto discovery of the IP address. 
> > Sometimes, when I change the network, I must restart the backend, 
> > but then it will automatically find the correct IP address 
> > again.
> > 
> > Cheers,
> > Philipp
> > 
> > Von: Florian Micklich 
> > <[[mickl...@apache.org](mailto:mickl...@apache.org)](mailto:[micklic
> > h...@apache.org](mailto:mickl...@apache.org))>
> > Datum: Dienstag, 22. November 2022 um 18:03
> > An: StreanPipes Dev 
> > <[[dev@streampipes.apache.org](mailto:dev@streampipes.apache.org)](m
> > ailto:[dev@streampipes.apache.org](mailto:dev@streampipes.apache.org
> > ))>
> > Betreff: Add functionality of host.docker.internal for linux 
> > users? Hi,
> > 
> > unlike Windows or Mac, the  host.docker.internal command is not 
> > working by default in Linux. A solution would be to add 
> > following code snippet the the docker-compose files [1].
> > 
> > 
> > ```
> >     extra_hosts:
> >   - "host.docker.internal:host-gateway"
> > ```
> 

Notification scheme for Github issues

[Dominik Riemer]

Hi,

before migrating to Github, our notification scheme was configured to send all 
newly created issues to the dev list and all other notifications to the issues 
list.
This was a tradeoff between having not too many notification mails on the dev 
list while still allowing everyone on the dev list to see where work is going 
on.

When we started the migration, we changed the asf.yaml settings to send all 
Github issue notifications to the issues list to avoid an email flood on dev.

Which settings do we want to use now?

As far as I can see, asf.yaml supports splitting of notifications between 
comment/status, so there are three options:

1) send all notifications related to issues to the issues list (not my favorite 
since only few people are subscribed to issues@)
2) send all notifications including issue comments to the dev list
3) send open/close notifications to dev@ and comments to issues@

What do you think?

Cheers
Dominik


[1] https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features

RE: Issue migration completed

[Dominik Riemer]

Hi Tim,

I had a look at the new templates and they are absolutely awesome! Very 
welcoming and convenient for new users and I also like the links to the 
discussion page...

Cheers
Dominik


-Original Message-
From: Tim  
Sent: Sunday, November 27, 2022 9:22 PM
To: dev@streampipes.apache.org
Subject: Re: Issue migration completed

Hi all,

I have familiarized myself a bit with GitHub Issues and prepared some aspects 
for our future work with it:

1) Labels
During the migration from Jira to Github, we already put some thought into the 
labels we want to use from now on.
A list of all labels and their description can be found here [1].
What are your thoughts? Are you already missing any? If not, we can just start 
with the current selection and expand it step by step if needed.

2) Release planning/versions
 From what I've seen so far, GitHub milestones are good for managing/scheduling 
our releases, just like we did with JIRA.
So I mapped the upcoming releases that were already in JIRA to Github, see [2].
Can you link that? Do you think we can work this way?

3) Issue templates
Github offers to possibility to provide so called "issue template" that allows 
to provide custom forms that simplifies the process for external people to 
create issues about StreamPipes. Therefore, I've created a pull request [3].
You can see how it would like when visiting my private fork of StreamPipes and 
click on "new issue" [4].
How do you like it? Would you like to change anything? Is there something 
missing?
I'm happy to discuss changes within the PR.

Do you miss anything for working with GitHub issues (besides the "how to" 
manual already mentioned before)?

Best
Tim

[1] https://github.com/apache/streampipes/labels
[2] https://github.com/apache/streampipes/milestones
[3] https://github.com/apache/streampipes/pull/807
[4] https://github.com/bossenti/incubator-streampipes/issues/new/choose

Am 26.11.2022 19:45 schrieb Florian Micklich:
> Thank you all for the work.
> 1307 Emails in my github folder :-P
> 
> Is there a howto "create a ticket" and some basic infos somewhere?
> e.g. how to create a subticket, version number, assign to, basic 
> community rules for creating an issue.
> I come totally from the jira world and this info would be for everyone 
> good.
> 
> 
> Greetings
> Florian
> 
> 
> 
> 
> 
> Am Samstag, dem 26.11.2022 um 18:01 + schrieb Dominik Riemer:
>> Hi all,
>> 
>> the migration of our Jira issues to Github is completed.
>> 
>> All issues should be available here: 
>> [https://github.com/apache/streampipes/issues](https://github.com/apa
>> che/streampipes/issues)
>> 
>> I hope that everything went well, in case there are any errors please 
>> feel free to reassign or modify these issues!
>> 
>> For the migration, we changed the notification settings to only send 
>> mails to 
>> [iss...@streampipes.apache.org](mailto:iss...@streampipes.apache.org)
>> , sorry for the email spam in case you are subscribed to this list 
>> 
>> 
>> Thanks @Tim and Philipp for helping with the migration!
>> 
>> Cheers
>> Dominik

Issue migration completed

[Dominik Riemer]

Hi all,

the migration of our Jira issues to Github is completed.

All issues should be available here: 
https://github.com/apache/streampipes/issues

I hope that everything went well, in case there are any errors please feel free 
to reassign or modify these issues!

For the migration, we changed the notification settings to only send mails to 
iss...@streampipes.apache.org, sorry for the email spam in case you are 
subscribed to this list 

Thanks @Tim and Philipp for helping with the migration!

Cheers
Dominik

[jira] [Created] (STREAMPIPES-651) Migrate Jira issues to Github

[Dominik Riemer (Jira)]

Dominik Riemer created STREAMPIPES-651:
--

 Summary: Migrate Jira issues to Github
 Key: STREAMPIPES-651
 URL: https://issues.apache.org/jira/browse/STREAMPIPES-651
 Project: StreamPipes
  Issue Type: Task
Reporter: Dominik Riemer
 Fix For: 0.90.0






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [DISCUSS] Plan to release StreamPipes 1.0

[Dominik Riemer]

Hi Xin,

thanks for bringing up this important question!
The current plan is to release a new version soon together with the TLP 
announcement, which is currently named "0.90.0".

I totally agree that a 1.0 version gives more trust to users. So let's say we 
would go for a 1.0 release after 0.90.0, what do you all think should be part 
of this release and what improvements should be done? Are any mission-critical 
features missing?

E.g., an important item on my list for the 1.0 release is increased test 
coverage.

Cheers
Dominik


On 2022/11/25 05:07:54 Xin Wang wrote:
> The current StreamPipes version is 0.70. Do we have a plan to release 1.0?
> Because 1.x version may make users feel more mature and stable, what do you
> think?
> 
> 
> -- 
> Thanks,
> Xin
> 

RE: [DISCUSS] Migrate from Jira to Github Issues?

[Dominik Riemer]

Hi everyone,

just to let you know that we will activate Github issues and try to migrate the 
existing issues from Jira to Github later today.

We will use a modified version of Apache Beam's migration tool where we can add 
a mapping from Jira users to Github users [1] so that we can keep all assignee 
info. It seems that this will only work for users with write access to the 
StreamPipes repo due to Github's spam protection. If you have any feedback, 
please feel free to create a PR! 

Cheers
Dominik

[1] 
https://github.com/dominikriemer/jira-to-issues/blob/main/shared/translate.ts

On 2022/11/17 21:40:37 Dominik Riemer wrote:
> Hi,
> together with Tim, I plan to work during the next week to migrate our issues 
> to Github and we'll send a proposal for a migration plan to the list within 
> the next days. The goal is to move all issues from Jira to Github while 
> keeping all relevant issue metadata where possible.
> There won't be any changes to the wiki right now, so it's totally fine to 
> continue updating the Confluence wiki!
> 
> Cheers
> Dominik
> 
> 
> 
> -Original Message-
> From: Philipp Zehnder  
> Sent: Thursday, November 17, 2022 9:30 PM
> To: dev@streampipes.apache.org
> Subject: Re: [DISCUSS] Migrate from Jira to Github Issues?
> 
> Hi,
> 
> @Lukas thanks. We thought it might be helpful to have a single point for all 
> the information relevant for developers on GitHub. I hope this will further 
> lower the entry barrier for new developers. What do you think?
> And you are right, since the wiki is unrelated to the issues, we can also 
> migrate them separately.
> 
> @Florian, there is no timeline yet. If that is something you are interested 
> to work on we can also discuss how the migration can be done.
> 
> Cheers,
> Philipp
> 
> 
> Von: Lukas Ott 
> Gesendet: Donnerstag, November 17, 2022 7:38 PM
> An: dev@streampipes.apache.org 
> Betreff: Re: [DISCUSS] Migrate from Jira to Github Issues?
> 
> Hi Florian,
> 
> As your wiki is on Confluence:
> https://cwiki.apache.org/confluence/display/STREAMPIPES
> 
> Like ours btw.
> https://cwiki.apache.org/confluence/display/PLC4X/PROFINET+Driver
> 
> It is not impacted by moving the JIRA issues to Github.
> 
> So Issue Tracking and Wiki are two separate parts. At least at PLC4X.
> 
> Greetings,
> Lukas
> 
> Am Do., 17. Nov. 2022 um 19:32 Uhr schrieb Florian Micklich <
> mickl...@apache.org>:
> 
> > Hi all,
> >
> > is there a timeline for when we want to start moving?
> > ALso what happens with the wiki.
> > I write on the wiki atm and before butting it into conf maybe it is 
> > easier to start it on github?
> >
> > Greetings
> > Florian
> >
> > Am Freitag, dem 11.11.2022 um 12:49 +0100 schrieb Florian Micklich:
> > > Hi,
> > >
> > > definitely agree.
> > > I think there are a lot of benefits. Big + for moving the wiki 
> > > into github and put it into git as well.
> > >
> > > I come from the gitlab and jira world. So I want to keep in mind 
> > > that
> > there still could occur a "barrier" for new developer.
> > > But I think, if we write down the git "rules" and what to do in what
> > situation, we are on the right side.
> > >
> > > I am happy to write the introduction after getting a short one 
> > > :-)
> > >
> > > Greetings
> > > Florian
> > >
> > >
> > >
> > > Am Donnerstag, dem 10.11.2022 um 16:51 + schrieb Tim:
> > > > Hi all,
> > > >
> > > > I would also like to see us move our issues from JIRA to
> > Github.
> > > > Beyond that, I fully agree with Philipp and would also bring the
> > 
> > > > "discussion" and "wiki" features. It's nice to have 
> > > > everything in one central place. This lowers the
> > 
> > > > barrier to entry in my opinion. Github provides great interaction
> > 
> > > > between these modules.
> > > > Another advantage is that the wiki is then also versioned via Git 
> > > > and
> > 
> > > > simply consists of Markdown files that you can edit with an editor 
> > > > of
> > 
> > > > your choice.
> > > > Last but not least, GitHub is the central entry point for open 
> > > > source
> > 
> > > > projects, so we should make the best use of this entry 
> > > > point.
> > > >
> > > > Best
> > > > Tim
> > > >
> > > 

Re: open GIT Question due rebase

[Dominik Riemer]

Hi Florian,
thanks for finding this! We need to investigate as the last commit message 
deletes a test file which should not have been deleted. 

I can have a deeper look at the PR during the weekend, or maybe somebody else 
has an idea what went wrong?

Cheers
Dominik

On 2022/11/24 09:48:41 Florian Micklich wrote:
> Hi Dominik,
> 
> I have a short git result question on you.
> 
> I am working in my branch STREAMPIPES-642 and before I pushed my commits, I 
> did a rebase on dev.
> During this process an odd result came up.
> I had to merge a file that I did not touch at all.
> 
> As you wrote the code, can you check if I didn't mess up anything?
> Still don't know why this message occurs because it has nothing to do with my 
> code changes at all.
> 
> Sorry for the inconvenience.
> 
> 
> https://github.com/apache/streampipes/commits/STREAMPIPES-642/streampipes-data-explorer/src/test/java/org/apache/streampipesdataexplorer/v4/query/writer
> 
> Florian
> 

Re: Apache License Header Format

[Dominik Riemer]

Hi,

just to summarize the outcome of this discussion:

* We prefer option 1 for license header styling
* Having automated checks for license headers in form of checkstyle config or 
pre-commit hooks is great. Just a side note, it is generally possible to have 
other non-ASF license headers in our code when integrating 3rd party code 
(e.g., MIT, but these files must be explicitly mentioned in the LICENSE file).
* License headers itself should never be added automatically as it is our 
responsibility to make sure correct licenses are used.

Cheers
Dominik 

On 2022/11/24 20:14:19 Christofer Dutz wrote:
> Hi all,
> 
> Automatically sticking Apache Headers to code isn’t a good idea.
> If someone adds something that’s copied from somewhere else, we’re actually 
> not allowed to add Apache headers to it.
> 
> Chris
> 
> From: Tim 
> Date: Tuesday, 22. November 2022 at 20:12
> To: dev@streampipes.apache.org 
> Subject: Re: Apache License Header Format
> Hi Florian,
> 
> no, there is yet no automation for Apache headers in resource files.
> That yould be a future improvement.
> 
> Best
> Tim
> 
> Am 22.11.2022 12:34 schrieb Florian Micklich:
> > Hi,
> >
> > I can answer my question by myself.
> > It is Option 1.
> >
> > Option 2 occurs on my side because of a "wrong" automatic Copyright
> > text.
> > IntelliJ is creating the commends syntax itself, that leads to option
> > 2. If you add the text already with comment syntax, the double comment
> > is the result.
> >
> > I added the info in conf [1]
> >
> > I think there is no option to make a different profile for markdown
> > files.
> > But this is done via STREAMPIPES-590 anyway automatically. Am I right?
> >
> > Greeting
> > Florian
> >
> > [1]
> > https://cwiki.apache.org/confluence/display/STREAMPIPES/License+Requirements
> >
> > Am Montag, dem 21.11.2022 um 19:53 +0100 schrieb Florian Micklich:
> >>
> >> Hi all,
> >>
> >> I saw now two difference License headers in the code. What Option is
> >> correct? ( I know it is only a minor issue because it is only the
> >> format)
> >>
> >> Option 1
> >> ```
> >> /*
> >>  *   Licensed to the Apache Software Foundation (ASF) under one or
> >> more
> >>  *   contributor license agreements.  See the NOTICE file distributed
> >> with
> >>  *   this work for additional information regarding copyright
> >> ownership.
> >>  *   The ASF licenses this file to You under the Apache License,
> >> Version 2.0
> >>  *   (the "License"); you may not use this file except in compliance
> >> with
> >>  *   the License.  You may obtain a copy of the License at
> >>  *
> >>  *
> >> [http://www.apache.org/licenses/LICENSE-2.0](http://www.apache.org/licenses/LICENSE-2.0)http://www.apache.org/licenses/LICENSE-2.0%5d(http:/www.apache.org/licenses/LICENSE-2.0)%3cbr>>
> >>  *
> >>  *   Unless required by applicable law or agreed to in writing,
> >> software
> >>  *   distributed under the License is distributed on an "AS IS"
> >> BASIS,
> >>  *   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
> >> implied.
> >>  *   See the License for the specific language governing permissions
> >> and
> >>  *   limitations under the License.
> >>  */
> >> ```
> >>
> >>
> >> Option 2
> >> ```
> >> /*
> >>  *
> >>  *  * Licensed to the Apache Software Foundation (ASF) under one or
> >> more
> >>  *  * contributor license agreements.  See the NOTICE file distributed
> >> with
> >>  *  * this work for additional information regarding copyright
> >> ownership.
> >>  *  * The ASF licenses this file to You under the Apache License,
> >> Version 2.0
> >>  *  * (the "License"); you may not use this file except in compliance
> >> with
> >>  *  * the License.  You may obtain a copy of the License at
> >>  *  *
> >>  *  *
> >> [http://www.apache.org/licenses/LICENSE-2.0](http://www.apache.org/licenses/LICENSE-2.0)http://www.apache.org/licenses/LICENSE-2.0%5d(http:/www.apache.org/licenses/LICENSE-2.0)%3cbr>>
> >>  *  *
> >>  *  * Unless required by applicable law or agreed to in writing,
> >> software
> >>  *  * distributed under the License is distributed on an "AS IS"
> >> BASIS,
> >>  *  * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
> >> implied.
> >>  *  * See the License for the specific language governing permissions
> >> and
> >>  *  * limitations under the License.
> >>  *  *
> >>  *
> >>  */
> >> ```
> >>
> >>
> >> In markdown this is used. I will add the description here [1] that for
> >> markdown another profile has to be used.
> >> ```
> >> #
> >> # Licensed to the Apache Software Foundation (ASF) under one or
> >> more
> >> # contributor license agreements.  See the NOTICE file distributed
> >> with
> >> # this work for additional information regarding copyright
> >> ownership.
> >> # The ASF licenses this file to You under the Apache License, Version
> >> 2.0
> >> # (the "License"); you may not use this file except in compliance
> >> with
> >> # the License.  You may obtain a copy of the License at
> >> #
> >> #
> >> 

[jira] [Created] (STREAMPIPES-647) Update incubator status file

[Dominik Riemer (Jira)]

Dominik Riemer created STREAMPIPES-647:
--

 Summary: Update incubator status file
 Key: STREAMPIPES-647
 URL: https://issues.apache.org/jira/browse/STREAMPIPES-647
 Project: StreamPipes
  Issue Type: Sub-task
Reporter: Dominik Riemer
Assignee: Dominik Riemer
 Fix For: 0.90.0






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

RE: [DISCUSS] Setup for Coordinate Reference System Reprojection Sources

[Dominik Riemer]

Hi Florian,
thanks for asking!
Then I propose to stick with the Apache SIS/empty database approach and to not 
include any ProJ4j dependencies in our source.

Cheers
Dominik 


-Original Message-
From: Florian Micklich  
Sent: Tuesday, November 22, 2022 10:56 PM
To: dev@streampipes.apache.org
Subject: Re: [DISCUSS] Setup for Coordinate Reference System Reprojection 
Sources

Hi Dominik,

Am Dienstag, dem 22.11.2022 um 15:12 + schrieb Dominik Riemer:
> Hi Florian,
> 
> just to make sure I understand correctly:
> 
> * There is an "SIS approach" which doesn't have any licensing issues 
> as users would need to fill their own database and only Apache SIS 
> dependencies are used in this approach


Yes that is correct.


> * There could be a fallback option which wouldn't require users to 
> have their own database, but that would require pulling in Proj4j, 
> which itself relies on EPSG datasets.

Yes, that was my idea. Also to use only some basic coordinates reference 
systems.
But I had the same question like you in mind so I wrote Martin (maintainer of 
SIS) exactly this kind of questions.
The answer is really worth reading!  I am really surprised and amazed, because 
most Geo Open Source programs are based on proj4.


>Hello Florian
>
>Le 22/11/2022 à 18:44, Florian Micklich a écrit :
>
>> I didn't know that proj4j itself uses EPSG data.
>>
>The CSV files in [1] are derived from EPSG tables. The file structures 
>are different than EPSG database schema, but the data that they contain 
>are EPSG data. The same information is also provided in WKT format in 
>[2] (this file somewhat duplicates the CSV tables). Some peoples on 
>PROJ mailing list have argued that rewriting EPSG data in a different 
>format free them from EPSG licensing terms, but this is not true. 
>Translating a software in a different language is a derivative work and 
>is still subject to the licensing terms of the copyright owner. In the 
>same way that translating a book does not suppress the rights of the 
>original author on the translated book. In the case of EPSG data, IOGP 
>allows us to reformat the data in a different way, but under some 
>conditions specified in their Terms of Use. And doing so does not give 
>us the right to erase the EPSG terms of use from the derivative work.
>
>The value of EPSG geodetic dataset is not in the database schema 
>(converting that to a different data structure is the easy part), but 
>in the data themselves. Creating a new "EPSG-like" dataset from scratch 
>would be a huge effort, well beyond our capability. We would have to 
>visit all national mapping agencies in the world, ask them to provide 
>documentation about the Coordinate Reference System they have defined 
>(including historical ones), consolidate all those information in some 
>tables, etc. So the CSV files [1] in PROJ4 contain an enormous amount 
>of EPSG work, even if the data structures are different.
>
>[1]https://github.com/locationtech/proj4j/tree/master/src/main/resource
>s/proj4 
>[2]https://raw.githubusercontent.com/locationtech/proj4j/master/src/mai
>n/resources/proj4/wkt/epsg.properties
>
>
>> Until now I thought it would be a good alternative lib besides EPSG 
>> approach.
>>
>When creating a Coordinate Reference System (CRS) from an EPSG code 
>such as "EPSG:4326", we are using the EPSG geodetic dataset. I think 
>that if a software contains e.g. 10 EPSG codes (compared to the ~6000 
>definitions in the full dataset), it could be considered Fair Use. But 
>including the full dataset requires that we comply with EPSG Terms Of Use.
>
>However if CRS are created from user-supplied WKT strings (or PROJ4 
>parameter strings), then no EPSG code is involved. The WKT definition 
>string may contain an AUTHORITY["EPSG", 4326] element, but it only 
>means "see EPSG:4326 for more complete information".
>
>
>> So what would be your advise with proj4(j) and how to handle that 
>> kind of implementation in an Apache project?
>>
>EPSG geodetic dataset is not needed when the CRS is built from WKT, GML 
>or some file formats like NetCDF and some (not all) GeoTIFF files. So 
>the approach taken in Apache SIS applications (JavaFX and console
>application) is to start without EPSG data. Then the first time that an 
>EPSG code is really needed, the application popups a dialog box (in
>JavaFX) or an interactive prompt (in console application) asking users 
>if they want to download the EPSG geodetic dataset. If users click 
>"yes", the EPSG Terms of Use is shown and the application asks users if 
>they accept. If they confirm, then the EPSG geodetic dataset is 
>downloaded and a database is created locally.
>
>N

RE: How to add Logger output in processors

[Dominik Riemer]

There shouldn't be anything different, make sure you are using the correct 
import (org.slf4j), and have a look at the other places where we use logging.

Dominik




-Original Message-
From: Florian Micklich  
Sent: Tuesday, November 22, 2022 8:01 PM
To: StreanPipes Dev 
Subject: How to add Logger output in processors

Hi, me again O:-),

I am wondering how to implement a logger output in the 1 class approach.
Is there an example somewhere of how to achieve this?

I tried following code but it is not working anymore.


Define a logger in the Class

```
private static final Logger LOG = 
LoggerFactory.getLogger(ReprojectionProcessor.class);
```

and then use the logger syntax as always in onInvocation or onEvent method.
```
LOG.warn("text text text.");
```

But there is no output at all.

Can some one help please?

Greetings
Florian

 

RE: [DISCUSS] Setup for Coordinate Reference System Reprojection Sources

[Dominik Riemer]

Hi Florian,

just to make sure I understand correctly:

* There is an "SIS approach" which doesn't have any licensing issues as users 
would need to fill their own database and only Apache SIS dependencies are used 
in this approach
* There could be a fallback option which wouldn't require users to have their 
own database, but that would require pulling in Proj4j, which itself relies on 
EPSG datasets.

Is this correct?

Cheers
Dominik


-Original Message-
From: Florian Micklich  
Sent: Tuesday, November 22, 2022 2:59 PM
To: dev@streampipes.apache.org
Subject: Re: [DISCUSS] Setup for Coordinate Reference System Reprojection 
Sources

Hi,

I found an interesting post regarding proj4j.
That's why I prefer the SIS approach with external database.
What do you think about the mentioned "copyright infringement" opinion?

PROJ claims to be under MIT license, but in my understanding this is copyright 
infringement. PROJ license should be MIT + EPSG terms of use.

The whole post is:

> Proj4J (and its parent PROJ project) includes EPSG data, so the use of 
> Proj4J dependency implies accepting EPSG terms of use [1]. PROJ claims 
> to be under MIT license, but in my understanding this is copyright 
> infringement. PROJ license should be MIT + EPSG terms of use.
> 
> EPSG terms of use is a Category X license for Apache. The use of EPSG 
> data has been discussed in Apache Legal [2][3]. The conclusion was 
> that an Apache project can include EPSG data if they are optional 
> (i.e. the application can still do useful work without them), the main 
> release does not contain them, and the data are available in a 
> separated download prominently labelled as under a more restrictive 
> license than Apache.
> 
> [1]https://epsg.org/terms-of-use.html
>
> [2]https://issues.apache.org/jira/browse/LEGAL-183
>
> [3]https://issues.apache.org/jira/browse/LEGAL-347
>




Am Freitag, dem 18.11.2022 um 22:27 +0100 schrieb Florian Micklich:
> Hi,
> 
> the basic sis implementation is done :) I created a pull request 
> [1] and happy about any feedback.
> 
> 
> Form the fallback options I created this ticket [2]
> 
> Florian
> 
> [1] 
> [https://github.com/apache/streampipes/pull/146](https://github.com/ap
> ache/streampipes/pull/146) [2]  
> [https://issues.apache.org/jira/browse/STREAMPIPES-638](https://issues
> .apache.org/jira/browse/STREAMPIPES-638)
> 
> 
> Am Montag, dem 31.10.2022 um 13:23 +0100 schrieb Florian Micklich:
> > Hi,
> > 
> > I updated the Jira Ticket and described the setup little bit 
> > more. If my intellij is working I can run some last tests on 
> > the base implementation.
> > 
> > My thoughts for the setup implementation:
> > 
> > The setup could be visible in the Configuration -> Pipeline Element 
> > Configuration and if the service is available due correct setup and 
> > scripts import. (see picture in jira ticket 
> > 
> > 
> > To have still a plug and play system by default, we could implement 
> > a "fallback" projection system with a limited EPSG Codes. 
> > Therefore we could use  proj4j [2]. So for example we allow 
> > the user to select just a bunch of valid codes from a list 
> > somewhere.
> > 
> > 
> > [1] 
> > [[https://github.com/locationtech/proj4j](https://github.com/locatio
> > ntech/proj4j)](https://github.com/locationtech/proj4j](https://githu
> > b.com/locationtech/proj4j))
> > 
> > What do you think?
> > Greetings
> > Florian
> > 
> > Am Montag, dem 19.09.2022 um 10:18 +0200 schrieb Florian 
> > Micklich:>
> > > Hi Philipp,
> > > 
> > > ok, maybe we can have a deeper discussion next week. I 
> > > am on vacation this week without computer  :)
> > > 
> > > With dataSource I mean the "Registration by Java code" as 
> > > describet here [1]. I startet to write that code 
> > > yesterday but was not able to check it due another 
> > > issue.
> > > 
> > > Florian
> > > 
> > > 
> > > [1] 
> > > [[[https://sis.apache.org/epsg.html](https://sis.apache.org/epsg.h
> > > tml)](https://sis.apache.org/epsg.html](https://sis.apache.org/eps
> > > g.html))](https://sis.apache.org/epsg.html](https://sis.apache.org
> > > /epsg.html)](https://sis.apache.org/epsg.html](https://sis.apache.
> > > org/epsg.html)))
> > > 
> > > 
> > > ⁣BlueMail for Android herunterladen ​
> > > 
> > > Am 19. Sept. 2022, 07:23, um 07:23, Philipp Zehnder 
> > > <[[[philipp.zehn...@bytefabrik.ai](mailto:philipp.zehnder@bytefabr
> > > ik.ai)](mailto:[philipp.zehn...@bytefabrik.ai](mailto:philipp.zehn
> > > d...@bytefabrik.ai))](mailto:[[philipp.zehn...@bytefabrik.ai](mailt
> > > o:philipp.zehn...@bytefabrik.ai)](mailto:[philipp.zehnder@bytefabr
> > > ik.ai](mailto:philipp.zehn...@bytefabrik.ai)))> schrieb:> 
> > > > >
> > > > Hi Florian,
> > > > 
> > > > thanks for opening the issue. I really like the 
> > > > illustration, something like this would also be 
> > > > great for the documentation of the processing 
> > > > elements.
> > > > 
> > > > As for the workflow, I'm not quite sure how we can handle that. 
> > > > 

[jira] [Created] (STREAMPIPES-637) Remove incubating references from source code

[Dominik Riemer (Jira)]

Dominik Riemer created STREAMPIPES-637:
--

 Summary: Remove incubating references from source code
 Key: STREAMPIPES-637
 URL: https://issues.apache.org/jira/browse/STREAMPIPES-637
 Project: StreamPipes
  Issue Type: Sub-task
Reporter: Dominik Riemer
Assignee: Dominik Riemer
 Fix For: 0.90.0


Remove the incubating references from the main repo's source code:
 * Check all pom files and update developer connection
 * Remove disclaimer
 * Update readme



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

RE: Post-graduation tasks

[Dominik Riemer]

Absolutely, thanks for the hint 

-Original Message-
From: Florian Micklich  
Sent: Friday, November 18, 2022 3:55 PM
To: dev@streampipes.apache.org
Subject: Re: Post-graduation tasks

Hi Dominik,

I think you forgot Apache in the URL. Am i right? 

https://github.com/apache/streampipes aka 
https://github.com/apache/streampipes.git
https://github.com/apache/streampipes-website aka 
https://github.com/apache/streampipes-website.git
https://github.com/apache/streampipes-examples aka 
https://github.com/apache/streampipes-examples.git

Greetings
Florian


Am Freitag, dem 18.11.2022 um 14:17 + schrieb Dominik Riemer:
> Hi,
> our repos have now been renamed:
> github.com/streampipes
> github.com/streampipes-website
> github.com/streampipes-examples.
> 
> Please make sure to update your remotes ;-)
> 
> Cheers
> Dominik
> 
> On 2022/11/18 08:33:54 Dominik Riemer wrote:
> > Hi all,
> > 
> > it is my pleasure to inform you that the ASF board has decided to 
> > promote StreamPipes to a top-level project. Congratulations to 
> > everyone!
> > 
> > From now on, our previous PPMC forms the new Apache StreamPipes 
> > PMC.
> > 
> > We will prepare and publish an official announcement, but before a 
> > few steps are needed. the most significant change is that our git 
> > remotes will change from apache/incubator-streampipes to 
> > apache/streampipes (and all other repos as well). I’ll ask Infra 
> > to move the repos and will write to the list once this is done. 
> > Everyone will need to change the git remotes afterwards.
> > 
> > For the remaining tasks, I created a checklist in confluence [1] and 
> > a task in Jira [2] where we can collect all subtasks related to 
> > transferring our resources out of the incubator. Please add or ask 
> > in case you have any additional items!
> > 
> > For our plan to prepare a small release right after graduation and 
> > before the graduation announcement, I updated the Jira roadmap for 
> > the next version and closed outdated tickets. Feel free to change 
> > anything I might have closed for no reason 
> > 
> > So thank you again all for your great effort during the last years 
> > and a big thank you to our mentors and our champion Chris for 
> > helping us navigate through the incubation process!! Looking forward 
> > to the next phase.
> > 
> > Cheers
> > Dominik
> > 
> > 
> > 
> > [1] 
> > [https://cwiki.apache.org/confluence/display/STREAMPIPES/Graduate+to
> > +a+TLP](https://cwiki.apache.org/confluence/display/STREAMPIPES/Grad
> > uate+to+a+TLP) [2] 
> > [https://issues.apache.org/jira/browse/STREAMPIPES-632](https://issu
> > es.apache.org/jira/browse/STREAMPIPES-632)
> > 

[jira] [Created] (STREAMPIPES-636) Activate Github discussions

[Dominik Riemer (Jira)]

Dominik Riemer created STREAMPIPES-636:
--

 Summary: Activate Github discussions
 Key: STREAMPIPES-636
 URL: https://issues.apache.org/jira/browse/STREAMPIPES-636
 Project: StreamPipes
  Issue Type: Sub-task
Reporter: Dominik Riemer


Infra ticket created:

https://issues.apache.org/jira/browse/INFRA-23925



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: Post-graduation tasks

[Dominik Riemer]

Hi,
our repos have now been renamed:
github.com/streampipes
github.com/streampipes-website
github.com/streampipes-examples.

Please make sure to update your remotes ;-)

Cheers
Dominik

On 2022/11/18 08:33:54 Dominik Riemer wrote:
> Hi all,
> 
> it is my pleasure to inform you that the ASF board has decided to promote 
> StreamPipes to a top-level project. Congratulations to everyone!
> 
> From now on, our previous PPMC forms the new Apache StreamPipes PMC.
> 
> We will prepare and publish an official announcement, but before a few steps 
> are needed. the most significant change is that our git remotes will change 
> from apache/incubator-streampipes to apache/streampipes (and all other repos 
> as well).
> I’ll ask Infra to move the repos and will write to the list once this is 
> done. Everyone will need to change the git remotes afterwards.
> 
> For the remaining tasks, I created a checklist in confluence [1] and a task 
> in Jira [2] where we can collect all subtasks related to transferring our 
> resources out of the incubator. Please add or ask in case you have any 
> additional items!
> 
> For our plan to prepare a small release right after graduation and before the 
> graduation announcement, I updated the Jira roadmap for the next version and 
> closed outdated tickets. Feel free to change anything I might have closed for 
> no reason 
> 
> So thank you again all for your great effort during the last years and a big 
> thank you to our mentors and our champion Chris for helping us navigate 
> through the incubation process!! Looking forward to the next phase.
> 
> Cheers
> Dominik
> 
> 
> 
> [1] https://cwiki.apache.org/confluence/display/STREAMPIPES/Graduate+to+a+TLP
> [2] https://issues.apache.org/jira/browse/STREAMPIPES-632
> 

[jira] [Created] (STREAMPIPES-635) Ask infra to move Github repos

[Dominik Riemer (Jira)]

Dominik Riemer created STREAMPIPES-635:
--

 Summary: Ask infra to move Github repos 
 Key: STREAMPIPES-635
 URL: https://issues.apache.org/jira/browse/STREAMPIPES-635
 Project: StreamPipes
  Issue Type: Sub-task
Reporter: Dominik Riemer
Assignee: Dominik Riemer






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Post-graduation tasks

[Dominik Riemer]

Hi all,

it is my pleasure to inform you that the ASF board has decided to promote 
StreamPipes to a top-level project. Congratulations to everyone!

From now on, our previous PPMC forms the new Apache StreamPipes PMC.

We will prepare and publish an official announcement, but before a few steps 
are needed. the most significant change is that our git remotes will change 
from apache/incubator-streampipes to apache/streampipes (and all other repos as 
well).
I’ll ask Infra to move the repos and will write to the list once this is done. 
Everyone will need to change the git remotes afterwards.

For the remaining tasks, I created a checklist in confluence [1] and a task in 
Jira [2] where we can collect all subtasks related to transferring our 
resources out of the incubator. Please add or ask in case you have any 
additional items!

For our plan to prepare a small release right after graduation and before the 
graduation announcement, I updated the Jira roadmap for the next version and 
closed outdated tickets. Feel free to change anything I might have closed for 
no reason 

So thank you again all for your great effort during the last years and a big 
thank you to our mentors and our champion Chris for helping us navigate through 
the incubation process!! Looking forward to the next phase.

Cheers
Dominik



[1] https://cwiki.apache.org/confluence/display/STREAMPIPES/Graduate+to+a+TLP
[2] https://issues.apache.org/jira/browse/STREAMPIPES-632

RE: [DISCUSS] Migrate from Jira to Github Issues?

[Dominik Riemer]

Hi,
together with Tim, I plan to work during the next week to migrate our issues to 
Github and we'll send a proposal for a migration plan to the list within the 
next days. The goal is to move all issues from Jira to Github while keeping all 
relevant issue metadata where possible.
There won't be any changes to the wiki right now, so it's totally fine to 
continue updating the Confluence wiki!

Cheers
Dominik



-Original Message-
From: Philipp Zehnder  
Sent: Thursday, November 17, 2022 9:30 PM
To: dev@streampipes.apache.org
Subject: Re: [DISCUSS] Migrate from Jira to Github Issues?

Hi,

@Lukas thanks. We thought it might be helpful to have a single point for all 
the information relevant for developers on GitHub. I hope this will further 
lower the entry barrier for new developers. What do you think?
And you are right, since the wiki is unrelated to the issues, we can also 
migrate them separately.

@Florian, there is no timeline yet. If that is something you are interested to 
work on we can also discuss how the migration can be done.

Cheers,
Philipp


Von: Lukas Ott 
Gesendet: Donnerstag, November 17, 2022 7:38 PM
An: dev@streampipes.apache.org 
Betreff: Re: [DISCUSS] Migrate from Jira to Github Issues?

Hi Florian,

As your wiki is on Confluence:
https://cwiki.apache.org/confluence/display/STREAMPIPES

Like ours btw.
https://cwiki.apache.org/confluence/display/PLC4X/PROFINET+Driver

It is not impacted by moving the JIRA issues to Github.

So Issue Tracking and Wiki are two separate parts. At least at PLC4X.

Greetings,
Lukas

Am Do., 17. Nov. 2022 um 19:32 Uhr schrieb Florian Micklich <
mickl...@apache.org>:

> Hi all,
>
> is there a timeline for when we want to start moving?
> ALso what happens with the wiki.
> I write on the wiki atm and before butting it into conf maybe it is 
> easier to start it on github?
>
> Greetings
> Florian
>
> Am Freitag, dem 11.11.2022 um 12:49 +0100 schrieb Florian Micklich:
> > Hi,
> >
> > definitely agree.
> > I think there are a lot of benefits. Big + for moving the wiki 
> > into github and put it into git as well.
> >
> > I come from the gitlab and jira world. So I want to keep in mind 
> > that
> there still could occur a "barrier" for new developer.
> > But I think, if we write down the git "rules" and what to do in what
> situation, we are on the right side.
> >
> > I am happy to write the introduction after getting a short one 
> > :-)
> >
> > Greetings
> > Florian
> >
> >
> >
> > Am Donnerstag, dem 10.11.2022 um 16:51 + schrieb Tim:
> > > Hi all,
> > >
> > > I would also like to see us move our issues from JIRA to
> Github.
> > > Beyond that, I fully agree with Philipp and would also bring the
> 
> > > "discussion" and "wiki" features. It's nice to have 
> > > everything in one central place. This lowers the
> 
> > > barrier to entry in my opinion. Github provides great interaction
> 
> > > between these modules.
> > > Another advantage is that the wiki is then also versioned via Git 
> > > and
> 
> > > simply consists of Markdown files that you can edit with an editor 
> > > of
> 
> > > your choice.
> > > Last but not least, GitHub is the central entry point for open 
> > > source
> 
> > > projects, so we should make the best use of this entry 
> > > point.
> > >
> > > Best
> > > Tim
> > >
> > > Am 10.11.2022 08:50 schrieb Philipp Zehnder:>
> > > > Hi Dominik,
> > > >
> > > > I am also in favor of migrating to GitHub issues. I 
> > > > think it will ease the management of open issues and lower the
> entry
> > > > barrier for new developers.
> > > >
> > > > Further, I am in favor of using GitHub discussions, this is a 
> > > > good
> way
> > > > to answer to common questions. I think we should also 
> > > > move the wiki to GitHub, because then we
> have
> > > > all the information for developers in one location.
> > > >
> > > > Cheers,
> > > > Philipp
> > > >
> > > >
> > > > 
> > > > Von: Dominik Riemer <[[dominik.rie...@bytefabrik.ai](mailto:
> dominik.rie...@bytefabrik.ai)](mailto:[dominik.rie...@bytefabrik.ai
> ](mailto:dominik.rie...@bytefabrik.ai))>
> > > > Gesendet: Mittwoch, November 9, 2022 10:52 PM
> > > > An: 
> > > > [[dev@streampipes.apache.org](mailto:dev@streampipes.apache.org
> )

[jira] [Created] (STREAMPIPES-632) Post-graduation tasks

[Dominik Riemer (Jira)]

Dominik Riemer created STREAMPIPES-632:
--

 Summary: Post-graduation tasks
 Key: STREAMPIPES-632
 URL: https://issues.apache.org/jira/browse/STREAMPIPES-632
 Project: StreamPipes
  Issue Type: Task
Reporter: Dominik Riemer


Umbrella issue to track all tasks related to moving from the Incubator the TLP



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (STREAMPIPES-631) UI linting as pre-commit hook

[Dominik Riemer (Jira)]

Dominik Riemer created STREAMPIPES-631:
--

 Summary: UI linting as pre-commit hook
 Key: STREAMPIPES-631
 URL: https://issues.apache.org/jira/browse/STREAMPIPES-631
 Project: StreamPipes
  Issue Type: Task
Reporter: Dominik Riemer
 Fix For: 0.90.0


Create pre-commit support for all UI files



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (STREAMPIPES-630) Migrate from Jira to Github

[Dominik Riemer (Jira)]

Dominik Riemer created STREAMPIPES-630:
--

 Summary: Migrate from Jira to Github
 Key: STREAMPIPES-630
 URL: https://issues.apache.org/jira/browse/STREAMPIPES-630
 Project: StreamPipes
  Issue Type: Task
Reporter: Dominik Riemer
 Fix For: 0.90.0


* Enable Github Issues in asf.yaml
 * Check migration script from Apache Beam
 * Modify migration script
 * Move issues



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (STREAMPIPES-629) Improve tutorials

[Dominik Riemer (Jira)]

Dominik Riemer created STREAMPIPES-629:
--

 Summary: Improve tutorials
 Key: STREAMPIPES-629
 URL: https://issues.apache.org/jira/browse/STREAMPIPES-629
 Project: StreamPipes
  Issue Type: Improvement
  Components: Documentation
Reporter: Dominik Riemer
 Fix For: 0.90.0


Rewrite the existing tutorials:

 
 * Use Connect sources instead of pipeline elements
 * Better use cases instead of the currently used geo operators
 * Check that all mentioned features are unchanged



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Reopened] (STREAMPIPES-122) [Documentation] SDK Reference examples change from Labels.from to withID syntax

[Dominik Riemer (Jira)]

 [ 
https://issues.apache.org/jira/browse/STREAMPIPES-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dominik Riemer reopened STREAMPIPES-122:


> [Documentation] SDK Reference examples change from Labels.from to withID 
> syntax
> ---
>
> Key: STREAMPIPES-122
> URL: https://issues.apache.org/jira/browse/STREAMPIPES-122
> Project: StreamPipes
>  Issue Type: Improvement
>Reporter: Florian Micklich
>Priority: Minor
>
> SDK References examples and text are using the deprecated  Labels.from method 
> in required stream and output strategy.
> Has to be rewritten with withID useage:
>  
> https://streampipes.apache.org/docs/docs/dev-guide-stream-requirements/



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

RE: [DISCUSSION] "cooperate design"

[Dominik Riemer]

Hi Florian,

there's nothing documented, but we use:

* Ubuntu as the logo font
* Roboto as the main font in the app
* The main colors are defined in 
https://github.com/apache/incubator-streampipes/blob/dev/ui/src/scss/_variables.scss

A good place to provide this information would be the wiki, so we make sure all 
resources are available within archived ASF infra.

Cheers
Dominik


-Original Message-
From: Florian Micklich  
Sent: Monday, November 14, 2022 6:29 PM
To: StreanPipes Dev 
Subject: [DISCUSSION] "cooperate design"

Me again,

during drafting the info graph some questions came up for me.

Do we have a "cooperate design" e.g. colors, fonts and size, base icons for 
specific vocabulary we use in the app and later in the documentation?

An internal download pool for icons, fonts e.g. would be cool as well.
So everyone has access to basics. Do we have something like this already?
Otherwise, I have my own Nextcloud instance running and could deploy to a 
separate StreamPipes share folder.


Greetings 
Florian 

RE: [DISCUSS] Automatically created "Persist *" Pipeline is flagged as "own"

[Dominik Riemer]

Hi Tim,
good question.
I think we just never added the "system" flag to pipelines created in 
StreamPipes Connect.
Before we added user management, the "own" endpoint only gave you pipelines 
created by the current user. As of now, the "own" endpoint returns all 
pipelines a user has read access to.

So I think we could create a ticket to properly flag system-created pipelines 
and also maybe to mark them as read-only in the pipeline overview, similar to 
the StreamPipes Conenct-created adapters in the installation view.

Cheers
Dominik


-Original Message-
From: Tim  
Sent: Monday, November 14, 2022 8:58 PM
To: Dev 
Subject: [DISCUSS] Automatically created "Persist *" Pipeline is flagged as 
"own"

Hi everyone,

I was playing around a bit with our StreamPipes API and observed the following.

When creating an adapter and selecting "Persist events" in the last dialog so 
that all events are written directly to the data lake, StreamPipes 
automatically creates a pipeline to do this.
When I query pipelines from the StreamPipes API, I'd expect to get this 
pipeline via the "system endpoint " since it was created by the system.
However, the pipeline was only accessible via the "own pipelines" 
endpoint.

What is your opinion? Is this the correct behavior?
What differentiates "own" pipelines from "system" pipelines?
Maybe I just haven't got the point here ;)


Best
Tim

Re: [DISCUSS] StreamPipes graduation: Draft Resolution

[Dominik Riemer]

Hi everyone,

I would just like to let you know that our IPMC graduation vote was successful 
and that the graduation decision is now up to the ASF board.
I think the next board meeting is scheduled for next Wednesday and I'll inform 
you about the outcome ;-)

Thank you all for participating in the discussions and voting procedures!

Cheers
Dominik


On 2022/10/31 20:05:44 Dominik Riemer wrote:
> Hi all,
> 
> now that our community graduation vote [1] has passed [2], there are a few 
> remaining steps before bringing the vote to the Apache Incubator:
> 
> * Prepare a draft charter
> * Decide on the initial Project Management Committee (PMC)
> * Choose our first PMC Chair
> 
> For the charter, I used the Whimsy tool [3] to generate a draft (see below). 
> Please read it (especially the mission statement) and respond if you have any 
> ideas for improvement.
> In terms of the PMC, the draft resolution lists all current members of the 
> StreamPipes PPMC as the initial PMC. Please let me know in case you feel 
> there should be any changes.
> Regarding the first PMC Chair, the responsibilities of the PMC chair include 
> reporting to the ASF board four times a year, needs to subscribe to the board 
> maliing list and to be aware of board concerns [4]. I'd like to propose 
> Philipp as the initial PMC chair in case he's willing to do that and if there 
> are no objections.
> 
> So here's the draft resolution, any feedback is welcome!
> 
> 
> ---
> 
> Establish the Apache StreamPipes Project
> 
> WHEREAS, the Board of Directors deems it to be in the best interests of
> the Foundation and consistent with the Foundation's purpose to establish
> a Project Management Committee charged with the creation and maintenance
> of open-source software, for distribution at no charge to the public,
> related to a self-service Industrial IoT toolbox which enables
> non-technical users to connect, analyze and explore IoT
> data streams.
> 
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache StreamPipes Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
> 
> RESOLVED, that the Apache StreamPipes Project be and hereby is
> responsible for the creation and maintenance of software related to a
> self-service Industrial IoT toolbox which enables non-technical users to
> connect, analyze and explore IoT data streams; and be it
> further
> 
> RESOLVED, that the office of "Vice President, Apache StreamPipes" be and
> hereby is created, the person holding such office to serve at the
> direction of the Board of Directors as the chair of the Apache
> StreamPipes Project, and to have primary responsibility for management
> of the projects within the scope of responsibility of the Apache
> StreamPipes Project; and be it further
> 
> RESOLVED, that the persons listed immediately below be and hereby are
> appointed to serve as the initial members of the Apache StreamPipes
> Project:
> 
>  * Christofer Dutz  
>  * Dominik Riemer   
>  * Grainier Perera  
>  * Jean-Baptiste Onofré 
>  * Johannes Tex 
>  * Julian Feinauer  
>  * Justin Mclean
>  * Kenneth Knowles  
>  * Marco Heyden 
>  * Patrick Wiener   
>  * Philipp Zehnder  
>  * Stefan Obermeier 
>  * Tim Bossenmaier  
> 
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that [###PMC Chair Name###] be
> appointed to the office of Vice President, Apache StreamPipes, to serve
> in accordance with and subject to the direction of the Board of
> Directors and the Bylaws of the Foundation until death, resignation,
> retirement, removal or disqualification, or until a successor is
> appointed; and be it further
> 
> RESOLVED, that the Apache StreamPipes Project be and hereby is tasked
> with the migration and rationalization of the Apache Incubator
> StreamPipes podling; and be it further
> 
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> StreamPipes podling encumbered upon the Apache Incubator PMC are
> hereafter discharged.
> 
> ---
> 
> Cheers
> Dominik
> 
> [1] https://lists.apache.org/thread/q6n11kfmmj1vgo6vq19nq1km5p1vow28
> [2] https://lists.apache.org/thread/5ybqmx8z768ksdymz2h2gjsx91p1drpp
> [3] https://whimsy.apache.org/roster/ppmc/streampipes (button at the bottom 
> of the page)
> [4] 
> https://www.apache.org/foundation/governance/pmcs#:~:text=The%20primary%20duty%20of%20a,and%20status%20of%20their%20project.
> 
> 
> 
> 
> 
> 

[DISCUSS] Migrate from Jira to Github Issues?

[Dominik Riemer]

Hi everyone,

submitting bugs and feature requests are types of community contributions with 
a very low entry barrier for first-time contributors. To submit bug reports, 
users currently need to register in our Jira, which is not so straightforward 
for non-Apache-folks.
By using Github issues, I'd expect that users find a more convenient way to 
submit issues and we would foster community engagement.

There are more and more ASF projects which are moving to Github issues, e.g., 
our friends from PLC4X have just recently migrated and also Apache Airflow [1] 
and Apache Pulsar [2] are two great examples. I also like the Github discussion 
feature Airflow and Pulsar are using.

For some background information, people from Apache Beam have written a feature 
comparison [3], a migration guide [4] and even a migration tool [5] which we 
could also use to transfer our issues from Jira to Github.

What do you think?

Cheers
Dominik


[1] https://github.com/apache/airflow/issues
[2] https://github.com/apache/pulsar/discussions
[3] 
https://docs.google.com/document/d/1_n7gboVbSKPs-CVcHzADgg8qpNL9igiHqUPCmiOslf0/edit#heading=h.r8qwrrbs8odn
[4] 
https://docs.google.com/document/d/1powrXGbjMLMYl9ibRzMda5o5HM_p44XvBy5MZu75Q5E/edit#heading=h.wskna8eurvjv

[5] https://github.com/google/jira-to-issues

Updated README file

[Dominik Riemer]

Hi,

I’ve updated the Github README file to better reflect our feature set and make 
it more appealing. I also updated some texts and links and added animated GIFs 
as screenshots thanks to Tim’s manual 

The updated page can be seen and compared to dev at [1], and the PR is 
available at [2] – any feedback/comments in the PR or here are welcome!

I’m unsure if we want to keep the current image at the top of the README – I 
think it gives a good first glance at the project, but might let users think 
StreamPipes only includes a pipeline editor…what do you think?

Cheers
Dominik

[1] https://github.com/apache/incubator-streampipes/tree/STREAMPIPES-622
[2] https://github.com/apache/incubator-streampipes/pull/138

RE: sources-vehicle-simulator:0.71.0-SNAPSHOT error

[Dominik Riemer]

Hi Stefan,

totally agree that some initial data source should be available to quickly 
explore the system. We have integrated the machine data simulator into Connect 
and could provide the vehicle simulator as well instead of running it as a 
separate service. 
So users can quickly start with simulated data, but can also easily delete it 
by just removing the adapter instead of having a separate container which only 
produces simulated data.

Do you think we should have more "sophisticated" simulators in the Connect 
library (the machine data simulator produces just some random values)?

Cheers
Dominik

-Original Message-
From: Obermeier. Stefan  
Sent: Wednesday, November 9, 2022 1:37 PM
To: dev@streampipes.apache.org
Subject: AW: sources-vehicle-simulator:0.71.0-SNAPSHOT error

Hi,

I personally use some script which simulate data e.g. writing to a MQTT topic.

But I think a data source (Pipeline element) for nontechnical users are useful 
especially at the beginning of a project.
E.g. to test connections to the field or to evaluate some pipeline ideas  
without having  external data sources.
Is there currently an alternative source for data?

Greetings,
Stefan



-Ursprüngliche Nachricht-
Von: Florian Micklich 
Gesendet: Mittwoch, 9. November 2022 12:42
An: dev@streampipes.apache.org
Betreff: Re: sources-vehicle-simulator:0.71.0-SNAPSHOT error

Hi Philipp,

yes we can remove it.
I am looking anyway for some movement data, we could use via adapter.

But it needs to be removed also in the docker-compose.full.yml here [1].
and have to rebuild the download source here [2].

I can remove it and push it if you want (after I created a jira ticket) but not 
sure how to replace the download source.

Greetings
Florian


[1] 
https://github.com/apache/incubator-streampipes/blob/dev/installer/compose/docker-compose.full.yml
[2] https://streampipes.apache.org/download


Am Mittwoch, dem 09.11.2022 um 08:14 + schrieb Philipp Zehnder:
> Hi Florian,
>
> that is a good point. We currently do not build this image 
> anymore. The goal is to gradually remove the sources docker images 
> and use adapters instead.
>
> Therefore, I suggest to remove the sources-vehicle-simulator from the 
> CLI as well. What do you think?
>
> Cheers,
> Philipp
>
> Von: Florian Micklich
> <[mickl...@apache.org](mailto:mickl...@apache.org)>
> Datum: Montag, 7. November 2022 um 16:59
> An: dev
> <[dev@streampipes.apache.org](mailto:dev@streampipes.apache.org)>
> Betreff: sources-vehicle-simulator:0.71.0-SNAPSHOT error Hi 
> all,
>
> i tried to run the full installer via CLI and got following error 
> message during image pull of the sources-vehicle-simulator. Is 
> this known?
>
>
>
> ```
>  ⠿ sources-vehicle-simulator Error
> 2.2s Error response from daemon: manifest for 
> apachestreampipes/sources-vehicle-simulator:0.71.0-SNAPSHOT not found:
> manifest unknown: manifest unknown ```
>
> Greetings
> Florian








SEEBURGER AGVorstand/SEEBURGER Executive Board:
Sitz der Gesellschaft/Registered Office:Axel Haas, Michael 
Kleeberg, Axel Otto, Dr. Martin Kuntz, Matthias Feßenbecker
Edisonstr. 1
D-75015 Bretten Vorsitzende des Aufsichtsrats/Chairperson of the 
SEEBURGER Supervisory Board:
Tel.: 07252 / 96 - 0Prof. Dr. Simone Zeuchner
Fax: 07252 / 96 - 
Internet: http://www.seeburger.de   Registergericht/Commercial 
Register:
e-mail: i...@seeburger.de   HRB 240708 Mannheim


Dieses E-Mail ist nur für den Empfänger bestimmt, an den es gerichtet ist und 
kann vertrauliches bzw. unter das Berufsgeheimnis fallendes Material enthalten. 
Jegliche darin enthaltene Ansicht oder Meinungsäußerung ist die des Autors und 
stellt nicht notwendigerweise die Ansicht oder Meinung der SEEBURGER AG dar. 
Sind Sie nicht der Empfänger, so haben Sie diese E-Mail irrtümlich erhalten und 
jegliche Verwendung, Veröffentlichung, Weiterleitung, Abschrift oder jeglicher 
Druck dieser E-Mail ist strengstens untersagt. Weder die SEEBURGER AG noch der 
Absender (Obermeier. Stefan) übernehmen die Haftung für Viren; es obliegt Ihrer 
Verantwortung, die E-Mail und deren Anhänge auf Viren zu prüfen.


This email is intended only for the recipient(s) to whom it is addressed. This 
email may contain confidential material that may be protected by professional 
secrecy. Any fact or opinion contained, or expression of the material herein, 
does not necessarily reflect that of SEEBURGER AG. If you are not the addressee 
or if you have received this email in error, any use, publication or 
distribution including forwarding, copying or printing is strictly prohibited. 
Neither SEEBURGER AG, nor the sender (Obermeier. Stefan) accept liability for 
viruses; it is your responsibility to check this email and its attachments for 
viruses.

[jira] [Created] (STREAMPIPES-622) Update Github README file

[Dominik Riemer (Jira)]

Dominik Riemer created STREAMPIPES-622:
--

 Summary: Update Github README file
 Key: STREAMPIPES-622
 URL: https://issues.apache.org/jira/browse/STREAMPIPES-622
 Project: StreamPipes
  Issue Type: Bug
  Components: Global
Reporter: Dominik Riemer
Assignee: Dominik Riemer
 Fix For: 0.90.0


Update the README file with fresh and gif-animated screenshots and update the 
project description  & manual to reflect the latest project status.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (STREAMPIPES-620) Data Explorer does not properly cleanup widget subscriptions

[Dominik Riemer (Jira)]

Dominik Riemer created STREAMPIPES-620:
--

 Summary: Data Explorer does not properly cleanup widget 
subscriptions
 Key: STREAMPIPES-620
 URL: https://issues.apache.org/jira/browse/STREAMPIPES-620
 Project: StreamPipes
  Issue Type: Bug
  Components: UI
Reporter: Dominik Riemer
Assignee: Dominik Riemer
 Fix For: 0.90.0


When leaving a data explorer view, existing widget subscriptions are not 
properly cleaned up leading to multiple requests being loaded when re-opening a 
data view.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (STREAMPIPES-619) Data Explorer: Unexpected edit mode behaviour

[Dominik Riemer (Jira)]

Dominik Riemer created STREAMPIPES-619:
--

 Summary: Data Explorer: Unexpected edit mode behaviour
 Key: STREAMPIPES-619
 URL: https://issues.apache.org/jira/browse/STREAMPIPES-619
 Project: StreamPipes
  Issue Type: Bug
  Components: UI
Reporter: Dominik Riemer
Assignee: Dominik Riemer
 Fix For: 0.90.0


When navigating to a data explorer view in view mode, after selecting "edit 
dashboard" in the menu, the edit mode opens with the designer panel showing the 
selected widget configuration, but the widget itself is not selected.

When switching to edit mode, the first widget should be selected for editing 
and if no widget is present, an empty configuration dialog should be shown.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (STREAMPIPES-618) Data Explorer time selector changes upon refresh

[Dominik Riemer (Jira)]

Dominik Riemer created STREAMPIPES-618:
--

 Summary: Data Explorer time selector changes upon refresh
 Key: STREAMPIPES-618
 URL: https://issues.apache.org/jira/browse/STREAMPIPES-618
 Project: StreamPipes
  Issue Type: Bug
  Components: UI
Reporter: Dominik Riemer
Assignee: Dominik Riemer
 Fix For: 0.90.0


Within the data explorer view, the time range selector changes from a 
pre-selected time (e.g., 15 mins) to "custom" when the refresh button is 
clicked.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: AW: [DISCUSS] StreamPipes graduation: Draft Resolution

[Dominik Riemer]

Hi,

our Incubator PMC vote is now happening on the incubator list [1].
Please feel free to express your support with your binding or non-binding vote 
by replying to [2]!

And yes, I've somehow finally managed to misspell our project name in the mail 
subject, so hopefully we won't graduate as StreamPieps ;-)

Cheers
Dominik

[1] https://lists.apache.org/list.html?gene...@incubator.apache.org
[2] https://lists.apache.org/thread/w3kc40g7koqc9vo9520bkn0qz4td8sqx

On 2022/11/03 20:08:43 Dominik Riemer wrote:
> Thank you all for your feedback!
> As there don't seem to be any more comments, I'll proceed with the next step 
> and start the discussion on the Incubator list.
> 
> Cheers
> Dominik
> 
> On 2022/11/03 08:50:59 Florian Micklich wrote:
> > Hi,
> > 
> > many thanks from my side as well :)
> > I support Philipp for the PMC chair as well.
> > 
> > 
> > If there is anything I can do, let me know.
> > 
> > Greetings 
> > Florian
> > 
> > 
> > Am Mittwoch, dem 02.11.2022 um 20:46 + schrieb Dominik Riemer:
> > > Thanks for your feedback and thanks @Philipp for volunteering!
> > > 
> > > We need a formal vote for the PMC chair which will happen on the private 
> > > list. In case you have any further feedback on the resolution text 
> > > (especially the mission statement), please provide your feedback until 
> > > tomorrow.
> > > 
> > > Cheers,
> > > Dominik
> > > 
> > > On 2022/11/02 19:20:20 Tim wrote:
> > > > Hi Dominik,
> > > > 
> > > > thank you very much for pushing the graduation process.
> > > >  From my side, the charter is also fine. To put it another way, I have 
> > > > no 
> > > > desire to change anything.
> > > > 
> > > > Philip is a great proposal for our first PMC Chair, I fully support 
> > > > it.
> > > > 
> > > > Best
> > > > Tim
> > > > 
> > > > Am 02.11.2022 18:59 schrieb Philipp Zehnder:> 
> > > > > Hi Dominik,
> > > > > 
> > > > > thank you for the preparation and organization of the graduation 
> > > > > process.
> > > > > I think the charter is good and I didn't notice anything.
> > > > > I still find the mission statement very fitting, and I really like 
> > > > > it.
> > > > > 
> > > > > Thank you also for your suggestion. I would be happy to take on 
> > > > > the
> > > > > role of the first PMC chair.
> > > > > If there are other suggestions from the community, I am also happy 
> > > > > to
> > > > > discuss them.
> > > > > 
> > > > > Cheers,
> > > > > Philipp
> > > > > 
> > > > > 
> > > > > 
> > > > > Von: Dominik Riemer 
> > > > > <[dominik.rie...@bytefabrik.ai](mailto:dominik.rie...@bytefabrik.ai)>
> > > > > Datum: Montag, 31. Oktober 2022 um 21:06
> > > > > An: [dev@streampipes.apache.org](mailto:dev@streampipes.apache.org) 
> > > > > <[dev@streampipes.apache.org](mailto:dev@streampipes.apache.org)>
> > > > > Betreff: [DISCUSS] StreamPipes graduation: Draft Resolution
> > > > > Hi all,
> > > > > 
> > > > > now that our community graduation vote [1] has passed [2], there are 
> > > > > a
> > > > > few remaining steps before bringing the vote to the Apache 
> > > > > Incubator:
> > > > > 
> > > > > * Prepare a draft charter
> > > > > * Decide on the initial Project Management Committee (PMC)
> > > > > * Choose our first PMC Chair
> > > > > 
> > > > > For the charter, I used the Whimsy tool [3] to generate a draft 
> > > > > (see
> > > > > below). Please read it (especially the mission statement) and 
> > > > > respond
> > > > > if you have any ideas for improvement.
> > > > > In terms of the PMC, the draft resolution lists all current members 
> > > > > of
> > > > > the StreamPipes PPMC as the initial PMC. Please let me know in 
> > > > > case
> > > > > you feel there should be any changes.
> > > > > Regarding the first PMC Chair, the responsibilities of the PMC 
> > > > > chair
> > > > > include reporting to the ASF board four times a year, needs to
>

RE: talk submission for FOSSGIS 2023 ?

[Dominik Riemer]

Hi Florian,
sorry, I currently don't have time to contribute, but feel free to submit 
something!

Cheers
Dominik


-Original Message-
From: Florian Micklich  
Sent: Monday, November 7, 2022 2:07 PM
To: dev@streampipes.apache.org
Subject: Re: talk submission for FOSSGIS 2023 ?

Hi all,

any votes against a submission?
End of "call for papers" is today.

Greetings
Florian



Am Montag, dem 31.10.2022 um 22:20 +0100 schrieb Florian Micklich:
> Hi all,
> 
> I am thinking about to prepare a 20 min talk at the FOSSGIS 2023 in 
> Berlin [1]. Sorry, the description is only in German. FOSSGIS is 
> the largest German-speaking conference for Open Source Software for 
> geoinformation
> 
> The main part would be about the geo processors due the missing key 
> operator reprojection is almost done. But also a good opportunity 
> to show the main concept of streampipes as well.
> 
> 
> By next Monday we would have to submit a short description [2]
> 
> Basically what we have to do:
> ```
> You write your title and a short description of what it is about. In 
> the Summary text box you describe what it is about in 5-x sentences. 
>  The program committee will read it and evaluate your 
> submission.
> 
> The community gets to read the description during the community 
> voting. The summary will be published in the program when the 
> presentation is accepted. If you want, you can write a longer 
> contribution for the conference proceedings (up to 5 pages with 
> pictures and so on, depending on what you want to write). You will be 
> informed about this by mail. The conference proceedings have an ISBN 
> and can be cited.
> 
> ``` 
> 
> The final paper submission would be on end of January 2023.  What 
> do you think about it.  What base information about streampipes 
> should be in the talk?
> 
> I would prepare a short description and the summary if you want and 
> discuss this later as well
> 
> 
> Greetings
> Florian
> 
> [1] 
> [https://pretalx.com/fossgis2023/cfp](https://pretalx.com/fossgis2023/
> cfp)
> 
> [2] 
> [https://pretalx.com/fossgis2023/submit/8WBm1D/info/](https://pretalx.
> com/fossgis2023/submit/8WBm1D/info/)

RE: Icons for documentation and illustrations

[Dominik Riemer]

Hi Florian,

sounds cool!
I'd like to avoid using images with proprietary licenses in the documentation 
so that the documentation itself remains Apache licensed. You can have a look 
at Google Font Icons, which include a large set of icons and are Apache 
licensed (although not as extensive as other sources). Several creative commons 
licenses are also fine (see [1], unmodified media section).
Many icons we use for pipeline elements are currently self-made. What kind of 
illustrations do you need?

Cheers
Dominik

[1] https://www.apache.org/legal/resolved.html


-Original Message-
From: Florian Micklich  
Sent: Friday, November 4, 2022 2:05 PM
To: dev 
Subject: Icons for documentation and illustrations

Hi all,

I am working on some documentation. Therefore I create some illustrations in 
SVG format.
I think SVGs are much better for resolution  scale and with inkscape exists an 
open source tool to create them. The output still can be an image.

Now my question. In my illustrations I prefer to use predesigned icons.
Therefore I use freepik [1] or flaticon [2] if free available. If I use them I 
have to cite the source. 

How do you create illustrations e.g. for pipeline elements?
Is there another source for Apache projects?
On the other hand I am thinking about to get a premium access.

Greetings
Florian

[1] https://www.freepik.com/

[2] https://www.flaticon.com

RE: [DISCUSS] What is the Master branch currently used for?

[Dominik Riemer]

As our release guide has almost as many different instructions for avoiding 
merge conflicts as the number of releases we've had, doing a force push should 
be definitely worth a try for the next release 

https://cwiki.apache.org/confluence/display/STREAMPIPES/Post-release+steps 




-Original Message-
From: Christofer Dutz  
Sent: Thursday, November 3, 2022 9:27 PM
To: dev@streampipes.apache.org
Subject: Re: [DISCUSS] What is the Master branch currently used for?

Shouldn’t a force push to main/master/release help with that?
That’s what we do in PLC4X.

Chris


From: Tim 
Date: Thursday, 3. November 2022 at 21:15
To: dev@streampipes.apache.org 
Subject: Re: [DISCUSS] What is the Master branch currently used for?
We could also try to not only rename our master branch, but create a new branch 
based on master. In order to then get rid of our lengthy merge conflicts we 
have with each relase.
What do you think about this? Are there any downsides of this that aren't on my 
radar now?

Best
Tim

Am 03.11.2022 21:12 schrieb Tim:
> I'm also in favour of this renaming.
>
> Best
> Tim
>
> Am 03.11.2022 21:01 schrieb Dominik Riemer:
>> Hi,
>>
>> yes, our master branch currently points to the latest release version.
>> I like the idea to rename "master" to "release" and "dev" to 
>> "develop", what do you think?
>>
>> Cheers
>> Dominik
>>
>> On 2022/11/03 14:39:54 Christofer Dutz wrote:
>>> Hi,
>>>
>>> good point … also it tends to upset some people. Most projects 
>>> settled on “main” instead of “master”.
>>> In the PLC4X project however we decided to call the development 
>>> branch “develop” and the banch where we merge releases “release”.
>>> This way the branches sort of explain what they are themselves ;-)
>>>
>>> Chris
>>>
>>>
>>> From: Zike Yang 
>>> Date: Thursday, 3. November 2022 at 15:29
>>> To: dev@streampipes.apache.org 
>>> Subject: [DISCUSS] What is the Master branch currently used for?
>>> Hi all,
>>>
>>> We use the `dev` branch as the default branch. But there still 
>>> exists the master branch.[0] And it was still updated 21 days ago. 
>>> I'm curious about what the master branch is currently used for.
>>>
>>> I think it's better to rename the master branch to another name if 
>>> it has other usage because it will confuse developers if there is 
>>> already a default branch. Sometimes I would accidentally checkout to 
>>> master and then realize something was wrong.
>>>
>>> What's your thought?
>>>
>>> [0] https://github.com/apache/incubator-streampipes/tree/master
>>>
>>> Best,
>>> Zike Yang
>>>

Re: AW: [DISCUSS] StreamPipes graduation: Draft Resolution

[Dominik Riemer]

Thank you all for your feedback!
As there don't seem to be any more comments, I'll proceed with the next step 
and start the discussion on the Incubator list.

Cheers
Dominik

On 2022/11/03 08:50:59 Florian Micklich wrote:
> Hi,
> 
> many thanks from my side as well :)
> I support Philipp for the PMC chair as well.
> 
> 
> If there is anything I can do, let me know.
> 
> Greetings 
> Florian
> 
> 
> Am Mittwoch, dem 02.11.2022 um 20:46 + schrieb Dominik Riemer:
> > Thanks for your feedback and thanks @Philipp for volunteering!
> > 
> > We need a formal vote for the PMC chair which will happen on the private 
> > list. In case you have any further feedback on the resolution text 
> > (especially the mission statement), please provide your feedback until 
> > tomorrow.
> > 
> > Cheers,
> > Dominik
> > 
> > On 2022/11/02 19:20:20 Tim wrote:
> > > Hi Dominik,
> > > 
> > > thank you very much for pushing the graduation process.
> > >  From my side, the charter is also fine. To put it another way, I have no 
> > > 
> > > desire to change anything.
> > > 
> > > Philip is a great proposal for our first PMC Chair, I fully support 
> > > it.
> > > 
> > > Best
> > > Tim
> > > 
> > > Am 02.11.2022 18:59 schrieb Philipp Zehnder:> 
> > > > Hi Dominik,
> > > > 
> > > > thank you for the preparation and organization of the graduation 
> > > > process.
> > > > I think the charter is good and I didn't notice anything.
> > > > I still find the mission statement very fitting, and I really like 
> > > > it.
> > > > 
> > > > Thank you also for your suggestion. I would be happy to take on the
> > > > role of the first PMC chair.
> > > > If there are other suggestions from the community, I am also happy 
> > > > to
> > > > discuss them.
> > > > 
> > > > Cheers,
> > > > Philipp
> > > > 
> > > > 
> > > > 
> > > > Von: Dominik Riemer 
> > > > <[dominik.rie...@bytefabrik.ai](mailto:dominik.rie...@bytefabrik.ai)>
> > > > Datum: Montag, 31. Oktober 2022 um 21:06
> > > > An: [dev@streampipes.apache.org](mailto:dev@streampipes.apache.org) 
> > > > <[dev@streampipes.apache.org](mailto:dev@streampipes.apache.org)>
> > > > Betreff: [DISCUSS] StreamPipes graduation: Draft Resolution
> > > > Hi all,
> > > > 
> > > > now that our community graduation vote [1] has passed [2], there are 
> > > > a
> > > > few remaining steps before bringing the vote to the Apache 
> > > > Incubator:
> > > > 
> > > > * Prepare a draft charter
> > > > * Decide on the initial Project Management Committee (PMC)
> > > > * Choose our first PMC Chair
> > > > 
> > > > For the charter, I used the Whimsy tool [3] to generate a draft (see
> > > > below). Please read it (especially the mission statement) and 
> > > > respond
> > > > if you have any ideas for improvement.
> > > > In terms of the PMC, the draft resolution lists all current members 
> > > > of
> > > > the StreamPipes PPMC as the initial PMC. Please let me know in case
> > > > you feel there should be any changes.
> > > > Regarding the first PMC Chair, the responsibilities of the PMC chair
> > > > include reporting to the ASF board four times a year, needs to
> > > > subscribe to the board maliing list and to be aware of board 
> > > > concerns
> > > > [4]. I'd like to propose Philipp as the initial PMC chair in case 
> > > > he's
> > > > willing to do that and if there are no objections.
> > > > 
> > > > So here's the draft resolution, any feedback is welcome!
> > > > 
> > > > 
> > > > ---
> > > > 
> > > > Establish the Apache StreamPipes Project
> > > > 
> > > > WHEREAS, the Board of Directors deems it to be in the best interests 
> > > > of
> > > > the Foundation and consistent with the Foundation's purpose to 
> > > > establish
> > > > a Project Management Committee charged with the creation and 
> > > > maintenance
> > > > of open-source software, for distribution at no charge to the 
> > > > public,
> > > > related to a self-service Industri

Re: [DISCUSS] What is the Master branch currently used for?

[Dominik Riemer]

Hi,

yes, our master branch currently points to the latest release version.
I like the idea to rename "master" to "release" and "dev" to "develop", what do 
you think?

Cheers
Dominik

On 2022/11/03 14:39:54 Christofer Dutz wrote:
> Hi,
> 
> good point … also it tends to upset some people. Most projects settled on 
> “main” instead of “master”.
> In the PLC4X project however we decided to call the development branch 
> “develop” and the banch where we merge releases “release”. This way the 
> branches sort of explain what they are themselves ;-)
> 
> Chris
> 
> 
> From: Zike Yang 
> Date: Thursday, 3. November 2022 at 15:29
> To: dev@streampipes.apache.org 
> Subject: [DISCUSS] What is the Master branch currently used for?
> Hi all,
> 
> We use the `dev` branch as the default branch. But there still exists
> the master branch.[0] And it was still updated 21 days ago. I'm
> curious about what the master branch is currently used for.
> 
> I think it's better to rename the master branch to another name if it
> has other usage because it will confuse developers if there is already
> a default branch. Sometimes I would accidentally checkout to master
> and then realize something was wrong.
> 
> What's your thought?
> 
> [0] https://github.com/apache/incubator-streampipes/tree/master
> 
> Best,
> Zike Yang
> 

Re: AW: [DISCUSS] StreamPipes graduation: Draft Resolution

[Dominik Riemer]

Thanks for your feedback and thanks @Philipp for volunteering!

We need a formal vote for the PMC chair which will happen on the private list. 
In case you have any further feedback on the resolution text (especially the 
mission statement), please provide your feedback until tomorrow.

Cheers,
Dominik

On 2022/11/02 19:20:20 Tim wrote:
> Hi Dominik,
> 
> thank you very much for pushing the graduation process.
>  From my side, the charter is also fine. To put it another way, I have no 
> desire to change anything.
> 
> Philip is a great proposal for our first PMC Chair, I fully support it.
> 
> Best
> Tim
> 
> Am 02.11.2022 18:59 schrieb Philipp Zehnder:
> > Hi Dominik,
> > 
> > thank you for the preparation and organization of the graduation 
> > process.
> > I think the charter is good and I didn't notice anything.
> > I still find the mission statement very fitting, and I really like it.
> > 
> > Thank you also for your suggestion. I would be happy to take on the
> > role of the first PMC chair.
> > If there are other suggestions from the community, I am also happy to
> > discuss them.
> > 
> > Cheers,
> > Philipp
> > 
> > 
> > 
> > Von: Dominik Riemer 
> > Datum: Montag, 31. Oktober 2022 um 21:06
> > An: dev@streampipes.apache.org 
> > Betreff: [DISCUSS] StreamPipes graduation: Draft Resolution
> > Hi all,
> > 
> > now that our community graduation vote [1] has passed [2], there are a
> > few remaining steps before bringing the vote to the Apache Incubator:
> > 
> > * Prepare a draft charter
> > * Decide on the initial Project Management Committee (PMC)
> > * Choose our first PMC Chair
> > 
> > For the charter, I used the Whimsy tool [3] to generate a draft (see
> > below). Please read it (especially the mission statement) and respond
> > if you have any ideas for improvement.
> > In terms of the PMC, the draft resolution lists all current members of
> > the StreamPipes PPMC as the initial PMC. Please let me know in case
> > you feel there should be any changes.
> > Regarding the first PMC Chair, the responsibilities of the PMC chair
> > include reporting to the ASF board four times a year, needs to
> > subscribe to the board maliing list and to be aware of board concerns
> > [4]. I'd like to propose Philipp as the initial PMC chair in case he's
> > willing to do that and if there are no objections.
> > 
> > So here's the draft resolution, any feedback is welcome!
> > 
> > 
> > ---
> > 
> > Establish the Apache StreamPipes Project
> > 
> > WHEREAS, the Board of Directors deems it to be in the best interests of
> > the Foundation and consistent with the Foundation's purpose to 
> > establish
> > a Project Management Committee charged with the creation and 
> > maintenance
> > of open-source software, for distribution at no charge to the public,
> > related to a self-service Industrial IoT toolbox which enables
> > non-technical users to connect, analyze and explore IoT
> > data streams.
> > 
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > (PMC), to be known as the "Apache StreamPipes Project", be and hereby 
> > is
> > established pursuant to Bylaws of the Foundation; and be it further
> > 
> > RESOLVED, that the Apache StreamPipes Project be and hereby is
> > responsible for the creation and maintenance of software related to a
> > self-service Industrial IoT toolbox which enables non-technical users 
> > to
> > connect, analyze and explore IoT data streams; and be it
> > further
> > 
> > RESOLVED, that the office of "Vice President, Apache StreamPipes" be 
> > and
> > hereby is created, the person holding such office to serve at the
> > direction of the Board of Directors as the chair of the Apache
> > StreamPipes Project, and to have primary responsibility for management
> > of the projects within the scope of responsibility of the Apache
> > StreamPipes Project; and be it further
> > 
> > RESOLVED, that the persons listed immediately below be and hereby are
> > appointed to serve as the initial members of the Apache StreamPipes
> > Project:
> > 
> >  * Christofer Dutz  
> >  * Dominik Riemer   
> >  * Grainier Perera  
> >  * Jean-Baptiste Onofré 
> >  * Johannes Tex 
> >  * Julian Feinauer  
> >  * Justin Mclean
> >  * Kenneth Knowles  
> >  * Marco Heyden 
> >  * Patrick Wiener   
> >  * Phil