Re: [VOTE] Accept Answer into the Apache Incubator
+1 (non-binding) Good Luck! Dominik On 2023/10/03 00:17:16 Willem Jiang wrote: > Following up the [DISCUSS] thread on Answer [1] I would like to call a > VOTE to accept into the Apache Incubator. > > Answer is a question-and-answer (Q&A) platform software for teams at > any scale to build a help center, knowledge base, community forum, > etc. > > Please cast your vote: > > [ ] +1, bring into the Incubator > [ ] +0, I don't care either way > [ ] -1, do not bring Answer into the Incubator, because... > > The vote will open at least for 72 hours and only votes from the > Incubator PMC are binding, but votes from everyone are welcome. > > Please check out the Answer Proposal from the incubator wiki[2]. > > [1]https://lists.apache.org/thread/42tvz3rqfy4w5poqgslh71sm1o1td7zn > [2]https://cwiki.apache.org/confluence/display/INCUBATOR/Answer+Proposal > > Best Regards, > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: License question when including other ASF projects
Hi Alex, EPL 2.0 should be fine in case it is included in binary-only form (see Category B under [1]). Cheers Dominik [1] https://www.apache.org/legal/resolved.html -Original Message- From: Alexander Alten-Lorenz Sent: Saturday, April 29, 2023 11:29 AM To: general@incubator.apache.org Subject: License question when including other ASF projects Hi, We use Apache Calcite, dependabot suggests a bump, but the automation failed since Calcite uses a non-compatible license (if I’m right) https://github.com/apache/incubator-wayang/actions/runs/4751917613/jobs/8441627979?pr=302#step:6:1117 How can we solve this, except not to update ;) Or is this just a false alarm? Thanks for the help, —Alex
[RESULT][VOTE] Graduate Apache StreamPipes to a TLP
Hi everyone, the IPMC vote for graduating Apache StreamPipes (incubating) [1] to a TLP has passed. There are 15 +1 (7 binding) and no 0 or -1 votes. The results are: Binding (7) * Jean-Baptiste Onofré * Christofer Dutz * Calvin Kirs * Lars Francke * Roman Shaposhnik * Willem Jiang * Trista Pan Non-binding (8) * Philipp Zehnder * Gang Li * Zike Yang * Xin Wang * Florian Micklich * Charles Zhang * Patrick Wiener * Heal Chow The vote is successful. We will proceed and submit the graduation proposal to the ASF board. Thank you all for participating in the vote! Cheers Dominik [1] https://lists.apache.org/thread/w3kc40g7koqc9vo9520bkn0qz4td8sqx - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduate Apache StreamPieps to a TLP
Hi everyone, thank you all for voting! I'll close this vote now and send the results soon. Cheers Dominik On 2022/11/10 06:27:12 healchow wrote: > +1 (non-binding) > > Best regards, > Heal Chow > from Apache InLong > > On Thu, Nov 10, 2022 at 11:56 AM Trista Pan wrote: > > > Hello +1 binding > > > > > > > > > > -- > > Trista Pan > > Twitter & Github: tristaZero > > > > > > > > > > On 11/7/2022 05:32，Dominik Riemer wrote： > > Hi everyone, > > > > following the [DISCUSS] thread at [0], I'd like to call a vote to graduate > > StreamPipes to a TLP. > > > > Please vote accordingly: > > > > [ ] +1 Apache StreamPipes (incubating) is ready to graduate from the > > Apache Incubator to a TLP. > > > > [ ] +0 No opinion. > > > > [ ] -1 Apache StreamPipes (Incubating) is not ready to graduate (please > > state reasons) > > > > Thank you for participating in the vote! > > > > Cheers > > Dominik > > > > > > --- > > Project highlights > > --- > > > > * Incubating since 2019-11-11 > > * 5 releases (0.66.0, 0.67.0, 0.68.0, 0.69.0, 0.70.0) > > * 3 different release managers > > * 13 PPMC members (almost all from different organizations), including 5 > > mentors > > * 8 additional committers > > * active community with all discussions happening on the mailing list and > > dedicated user mailing list as support channel > > * community building & talks at ACNA19, 20, 21, 22 + Asia, SF Big Data > > Analytics and many other webinars > > * over 9.000 commits > > * 52 subscribers on the dev list, 57 subscribers on the users list > > * Articles about StreamPipes in the US Linux Magazine [4], and StreamPipes > > was named one of the > > top 5 open source tools for IoT Analytics by OpenSourceForU [5] > > * Number of Github stars has increased to currently 350 > > * Website [6], extensive documentation [7] and a developer wiki [8] > > * Strong connection and integration with other projects in the Apache IoT > > space (e.g., PLC4X) > > * Completed maturity self-assessment [9] > > > > > > --- > > Draft resolution > > --- > > > > 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 Philipp Zehnder be > > appointed to the office of Vice President, Apache StreamPipes, to serve > > in accordance with and subject to the direction of the Board
[VOTE] Graduate Apache StreamPieps to a TLP
Hi everyone, following the [DISCUSS] thread at [0], I'd like to call a vote to graduate StreamPipes to a TLP. Please vote accordingly: [ ] +1 Apache StreamPipes (incubating) is ready to graduate from the Apache Incubator to a TLP. [ ] +0 No opinion. [ ] -1 Apache StreamPipes (Incubating) is not ready to graduate (please state reasons) Thank you for participating in the vote! Cheers Dominik --- Project highlights --- * Incubating since 2019-11-11 * 5 releases (0.66.0, 0.67.0, 0.68.0, 0.69.0, 0.70.0) * 3 different release managers * 13 PPMC members (almost all from different organizations), including 5 mentors * 8 additional committers * active community with all discussions happening on the mailing list and dedicated user mailing list as support channel * community building & talks at ACNA19, 20, 21, 22 + Asia, SF Big Data Analytics and many other webinars * over 9.000 commits * 52 subscribers on the dev list, 57 subscribers on the users list * Articles about StreamPipes in the US Linux Magazine [4], and StreamPipes was named one of the top 5 open source tools for IoT Analytics by OpenSourceForU [5] * Number of Github stars has increased to currently 350 * Website [6], extensive documentation [7] and a developer wiki [8] * Strong connection and integration with other projects in the Apache IoT space (e.g., PLC4X) * Completed maturity self-assessment [9] --- Draft resolution --- 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 Philipp Zehnder 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. --- [0] https://lists.apache.org/thread/dg3z175h2szcg3wgz9tmq770krvscvp8 [1] https://lists.apache.org/thread/18vgpw0jq93rwh9mj9bb27nj7gjhmldg [2] https://lists.apache.org/thread/q6n11kfmmj1vgo6vq19nq1km5p1vow28 [3] https://lists.apache.org/thread/5ybqmx8z768ksdymz2h2gjsx91p1drpp [4] https://www.linux-magazine.com/Issues/2021/244/Apache-StreamPipes [5] https://www.opensourceforu.com/2020/12/top-5-open-source-tools-for-iot-analytics/ [6] https://streampipes.apache.org/ [7] https://streampipes.apache.org/docs/docs/user-guide-introduction.html [8] https://cwiki.apache.org/confluence/display/STREAMPIPES/Apache+StreamPipes+%28incubating%29+Developer+Wiki [9] https://cwiki.apache.org/confluence/display/STREAMPIPES/StreamPipes+Maturity+Checklist - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Graduate Apache StreamPipes to a TLP
Hi, as there don't seem to be any questions, I'll start the vote soon! Cheers Dominik On 2022/11/03 20:34:27 Dominik Riemer wrote: > Hello everyone, > > Apache StreamPipes has been incubating since 2019-11-11. Within this time, > the StreamPipes community has made great progress, has adopted the Apache way > and grown with the help from our mentors. > The StreamPipes community believes that we have met the conditions for > graduation and have discussed [1] and voted [2] for graduation with the > result at [3]. > > Therefore, we'd like to start the discussion and would appreciate any > feedback towards graduation! > We are happy to answer any questions - below are some facts and project > highlights from the incubation phase as well as the draft resolution. > > This is also a good opportunity to say a big thank you to our mentors. I > really appreciated the prompt help at any time during incubation for the many > questions we had. Thanks a lot, Chris, Jean-Baptiste and Justin! > > Cheers > Dominik > > --- > Project highlights > --- > > * Incubating since 2019-11-11 > * 5 releases (0.66.0, 0.67.0, 0.68.0, 0.69.0, 0.70.0) > * 3 different release managers > * 13 PPMC members (almost all from different organizations), including 5 > mentors > * 8 additional committers > * active community with all discussions happening on the mailing list and > dedicated user mailing list as support channel > * community building & talks at ACNA19, 20, 21, 22 + Asia, SF Big Data > Analytics and many other webinars > * over 9.000 commits > * 52 subscribers on the dev list, 57 subscribers on the users list > * Articles about StreamPipes in the US Linux Magazine [4], and StreamPipes > was named one of the > top 5 open source tools for IoT Analytics by OpenSourceForU [5] > * Number of Github stars has increased to currently 350 > * Website [6], extensive documentation [7] and a developer wiki [8] > * Strong connection and integration with other projects in the Apache IoT > space (e.g., PLC4X) > * Completed maturity self-assessment [9] > > > --- > Draft resolution > --- > > 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 Philipp Zehnder 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 Ap
[DISCUSS] Graduate Apache StreamPipes to a TLP
Hello everyone, Apache StreamPipes has been incubating since 2019-11-11. Within this time, the StreamPipes community has made great progress, has adopted the Apache way and grown with the help from our mentors. The StreamPipes community believes that we have met the conditions for graduation and have discussed [1] and voted [2] for graduation with the result at [3]. Therefore, we'd like to start the discussion and would appreciate any feedback towards graduation! We are happy to answer any questions - below are some facts and project highlights from the incubation phase as well as the draft resolution. This is also a good opportunity to say a big thank you to our mentors. I really appreciated the prompt help at any time during incubation for the many questions we had. Thanks a lot, Chris, Jean-Baptiste and Justin! Cheers Dominik --- Project highlights --- * Incubating since 2019-11-11 * 5 releases (0.66.0, 0.67.0, 0.68.0, 0.69.0, 0.70.0) * 3 different release managers * 13 PPMC members (almost all from different organizations), including 5 mentors * 8 additional committers * active community with all discussions happening on the mailing list and dedicated user mailing list as support channel * community building & talks at ACNA19, 20, 21, 22 + Asia, SF Big Data Analytics and many other webinars * over 9.000 commits * 52 subscribers on the dev list, 57 subscribers on the users list * Articles about StreamPipes in the US Linux Magazine [4], and StreamPipes was named one of the top 5 open source tools for IoT Analytics by OpenSourceForU [5] * Number of Github stars has increased to currently 350 * Website [6], extensive documentation [7] and a developer wiki [8] * Strong connection and integration with other projects in the Apache IoT space (e.g., PLC4X) * Completed maturity self-assessment [9] --- Draft resolution --- 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 Philipp Zehnder 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. --- [1] https://lists.apache.org/thread/18vgpw0jq93rwh9mj9bb27nj7gjhmldg [2] https://lists.apache.org/thread/q6n11kfmmj1vgo6vq19nq1km5p1vow28 [3] https://lists.apache.org/thread/5ybqmx8z768ksdymz2h2gjsx91p1drpp [4] https://www.linux-magazine.com/Issues/2021/244/Apache-StreamPipes [5] https://www.opensourceforu.com/2020/12/top-5-open-source-tools-for-iot-analytics/ [6] https://streampipes.apache.org/ [7] https://streampipes.apache.org/docs/docs/user-guide-introduction.html [8] https://cwiki.apache.org/confluence/display/STREAMPIPES/Apache+StreamPipes+%28incubating%29+Developer+Wiki [9] https://cwiki.apache.
StreamPipes community graduation vote started
Dear Apache Incubator Community, a community graduation VOTE at Apache StreamPipes (incubating) is now taking place [1] regarding graduation to a Top-Level Project (TLP). [1] https://lists.apache.org/thread/q6n11kfmmj1vgo6vq19nq1km5p1vow28 Cheers, Dominik - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [VOTE] Accept StreamPark into the Apache Incubator
+1 (non-binding) - good luck! Dominik -Original Message- From: Yu Xiao Sent: Tuesday, August 30, 2022 1:25 PM To: general@incubator.apache.org Subject: Re: [VOTE] Accept StreamPark into the Apache Incubator + 1 non-binding Best wishes! Yu Xiao Apache ShenYu 俊平堵 于2022年8月30日周二 14:33写道： > > +1 (binding). Good luck! > > tison 于2022年8月24日周三 11:56写道： > > > Hi all, > > > > Following up on the [DISCUSS] thread on StreamPark[1], I would like > > to call a VOTE to accept StreamPark into the Apache Incubator, > > please check out the StreamPark Proposal from the incubator wiki[2]. > > > > Please cast your vote: > > > > [ ] +1, bring StreamPark into the Incubator [ ] +0, I don't care > > either way [ ] -1, do not bring StreamPark into the Incubator, > > because... > > > > The vote will open at least for 72 hours, and only votes from the > > Incubator PMC are binding, but votes from everyone are welcome. > > > > Best, > > tison. > > > > [1] https://lists.apache.org/thread/ns5n6ozl1mdvdbhmkfol67lt163m74v3 > > [2] > > https://cwiki.apache.org/confluence/display/INCUBATOR/StreamPark+Pro > > posal > > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [VOTE] Apache StreamPipes 0.69.0 (incubating) RC1 release
Hi Craig, so far we've always managed to get at least three binding votes from our mentors, but this time we're lacking two more binding votes. So any help in checking our release candidate is appreciated and thanks for your support! Cheers Dominik -Original Message- From: Craig Russell Sent: Tuesday, March 15, 2022 6:46 PM To: Incubator Subject: Re: [VOTE] Apache StreamPipes 0.69.0 (incubating) RC1 release Hi Christofer, You have five mentors. Are they all unavailable? Warm regards, Craig > On Mar 15, 2022, at 4:32 AM, Christofer Dutz > wrote: > > Hi all ... > > it would be great if we could get at least one more IPMC to vote on > this > > The StreamPipes team put specially a lot of effort into merging the initially > 3 separate repos into one to also make validating releases a lot easier. It > would be cool, if we could thank them by finally finding a 3rd vote (ideally > a +1 ;-) ). > > Thanks, >Chris > > -Original Message- > From: Zhang Yonglun > Sent: Dienstag, 15. März 2022 07:09 > To: general@incubator.apache.org > Subject: Re: [VOTE] Apache StreamPipes 0.69.0 (incubating) RC1 release > > Hi, > > +1 (non binding) > > I checked: > - incubating in name > - signatures and hashes are fine > - Disclaimer exists > - LICENSE and NOTICE exist > - No unexpected binary files > > Kindly reminder that maybe you would like to update the year in the NOTICE > file from 2022 to 2019-2022 before the next release. > > -- > > Zhang Yonglun > Apache ShenYu (Incubating) > Apache ShardingSphere > > Philipp Zehnder 于2022年3月11日周五 16:53写道： >> >> Hi all, >> >> this is a call for a vote to release Apache StreamPipes (incubating) 0.69.0. >> Apache StreamPipes (incubating) is self-service Industrial IoT toolbox to >> enable non-technical users to connect, analyze and explore IIoT data streams. >> The Apache StreamPipes community has voted on and approved a proposal to >> release Apache StreamPipes (incubating) 0.69.0. >> >> We now kindly request the Incubator PMC members to review and vote on this >> release. >> >> Vote and result threads from the StreamPipes community: >> Result: >> https://lists.apache.org/thread/hmx9wtyjw6tqbx70gpvnr8tqcg0xxlcc >> Vote: >> https://lists.apache.org/thread/b58pym522yqn4qbdym549xh440boy52p >> >> From the PPMC vote, we carry over 1 binding IPMC votes: >> Christofer Dutz >> >> The vote will be open for at least 72 hours. >> >> Please vote accordingly: >> >> [] +1 approve (indicate what you validated - e.g., performed the >> checklist at [6]) [] +0 no opinion [] -1 reject (explanation >> required) >> >> One artifact is relevant for this vote: >> >> incubator-streampipes, staged at [1], available in Nexus at [2], >> release tag: release/0.69.0, hash for the release tag: >> 6893604222cb9c3efc4bf66dc0c21e3223c2c84e >> >> >> Per [3] "Before voting +1, [P]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] >> >> >> Thanks for taking your time for validating this release! >> >> Philipp >> >> >> [1] >> https://dist.apache.org/repos/dist/dev/incubator/streampipes/0.69.0/r >> c >> 1/ [2] >> https://repository.apache.org/content/repositories/orgapachestreampip >> e >> s-1016 [3] >> https://www.apache.org/dev/release.html#approving-a-release >> [4] >> https://cwiki.apache.org/confluence/display/STREAMPIPES/Validating+a+ >> r >> elease [5] >> https://dist.apache.org/repos/dist/dev/incubator/streampipes/KEYS >> >> >> >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org Craig L Russell c...@apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: Can we use the GitHub's "transferring a repository" feature after IP clearance
Hi, we used the "transfer repository" feature when we were transferring StreamPipes to the incubator, which worked smoothly. Infra performs the transfer upon request, the only requirement is that you are able to add someone from Infra as an owner to your existing repository, as only Infra can initiate the transfer due to access rights. Dominik -Original Message- From: Sheng Wu Sent: Wednesday, November 24, 2021 4:24 AM To: Incubator Subject: Re: Can we use the GitHub's "transferring a repository" feature after IP clearance Hi I believe this gets to be accepted once you have IP clearance passed, SGA and ICLA filed, then INFRA will provide a way to do this. Just submit a ticket to Infra team once everything is ready. Sheng Wu 吴晟 Twitter, wusheng1108 Daniel Widdis 于2021年11月24日周三 上午10:42写道： > I can't speak to the specifics of Apache, but I have used the > repository transfer feature to move a project from a personal account > to an organizational account, and it preserves all the issues, PRs, commit > history, etc., simply changing the Github URL. I wouldn't think there > would be any issues at all from an IP standpoint. > > The only "hiccup" I experienced the presence of older releases with > older coordinates in a central repository, for which there should be a > one-time special release process to redirect the groupid for the first > release at new coordinates, e.g. [1] > > [1] - https://maven.apache.org/guides/mini/guide-relocation.html > > On 11/23/21, 6:33 PM, "Sutou Kouhei" wrote: > > Hi, > > I'm not sure that here is a right place to discuss this. If > this is not a right place, please tell me where is a right > place. > > Question: > > Can we use the GitHub's "transferring a repository"[1] after > IP clearance is passed? Apache Arrow project used pull > requests to import donated codes that pass IP clearance but > has never used the GitHub's "transferring a repository". If > there is a case that uses the GitHub's "transferring a > repository", please share it. Any advice is appreciated as > well. > > Background: > > Apache Arrow project has accepted the donation of the Julia > implementation before[2]. But there is a problem in > development process, https://github.com/JuliaData/Arrow.jl > is upstream and > https://github.com/apache/arrow/tree/master/julia/Arrow is > downstream[3]. > > So, Apache Arrow project wants to restart the Julia > implementation with the Apache way development process from > IP clearance. Apache Arrow project wants to use a separated > repository https://github.com/apache/arrow-julia instead of > Apache Arrow's monorepo https://github.com/apache/arrow with > the new development process. Apache Arrow PMC accepted > this[4][5]. > > I assumed that Apache Arrow project uses a pull request for > IP clearance and importing passed codes at import > https://github.com/JuliaData/Arrow.jl . So I've created an > empty Git repository https://github.com/apache/arrow-julia > . But an idea is raised: How about using the GitHub's > "transferring a repository" feature to move existing issues > and pull requests as-is, set redirect to > https://github.com/apache/arrow-julia from > https://github.com/JuliaData/Arrow.jl and so on? > > But I don't know that Apache Arrow project can use the > GitHub's "transferring a repository" feature. So I'm asking > this here. > > > [1] > https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository > [2] https://lists.apache.org/thread/w7szf06rf0qomc5dolhg57x0pcxvqvxr > [3] https://lists.apache.org/thread/1ofhjn37rrlvyv9phhg34hnbrk0dgf4r > [4] https://lists.apache.org/thread/6q333y875v7mfyl2g988b01hqtgr52pt > [5] > https://lists.apache.org/thread/0fty9370vt5rmp48kbjkdzc0g8vc5cgf > > > Thanks, > -- > kou > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[RESULT][VOTE] Release Apache StreamPipes 0.68.0 (incubating) RC1
Hi all, The vote to release Apache StreamPipes (incubating) 0.68.0 has passed with three +1 binding votes. Binding votes: Christofer Dutz Jean-Baptiste Onofre Julian Feinauer Non-Binding votes: Xun Liu Vote thread: https://lists.apache.org/thread.html/r5d9cdb3e5f5be6d09f580a47f303c8b6fa5e40 464d2c26caed7977a1%40%3Cgeneral.incubator.apache.org%3E Thanks a lot to everyone for taking your time to review our release candidate! We will proceed with publishing the approved artifacts and sending out the announcements in the coming days. On behalf of the Apache StreamPipes Community, Dominik - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Apache StreamPipes 0.68.0 (incubating) RC1 release
Hi, thanks for everyone who has voted so far! We are currently missing two IPMC-binding votes for release approval. It would be great if two more IPMC members could find some time to vote on our release candidate. Thanks! Dominik On 2021/07/15 02:13:00, Xun Liu wrote: > +1 (non-binding) from me, I have checked the following items: > > - Incubating in name > - NOTICE is fine > - DISCLAIMER exists > - All links are valid > - All ASF files have ASF headers > - Download all staged artifacts under the url specified in the release vote > email > - Unzip the archive > - Run RAT > - Build Backend > - Build UI > - Build Extensions > - Build and Run Test system on Docker > - Verify the signature is correct > - Verify the SHA512 checksum > > Best regards > Xun Liu > > On Thu, Jul 15, 2021 at 4:00 AM Dominik Riemer wrote: > > > Hi all, > > > > this is a call for a vote to release Apache StreamPipes (incubating) > > 0.68.0. > > Apache StreamPipes (incubating) is self-service Industrial IoT toolbox to > > enable non-technical users to connect, analyze and explore IIoT data > > streams. > > The Apache StreamPipes community has voted on a proposal to release Apache > > StreamPipes (incubating) 0.68.0 > > > > We now kindly ask the Incubator PMC members to review and vote on this > > release. > > > > Vote and result threads from the StreamPipes community: > > Result: > > > > https://lists.apache.org/thread.html/r61928e5e971812dc271fe678c7e9e3202622a8 > > 442635da94f9034f00%40%3Cdev.streampipes.apache.org%3E > > Vote: > > > > https://lists.apache.org/thread.html/r0164a14c229a459a05ff305506238608575270 > > bf5a57111eed2dff3d%40%3Cdev.streampipes.apache.org%3E > > > > From the PPMC vote, we carry over 1 binding IPMC vote: > > Christofer Dutz > > > > The vote will be open for at least 72 hours. > > > > Please vote accordingly: > > > > [] +1 approve (indicate what you validated - e.g., performed the checklist > > at [6]) > > [] +0 no opinion > > [] -1 reject (explanation required) > > > > Three artifacts are relevant for this vote: > > > > incubator-streampipes, staged at [1], available in Nexus at [2], release > > tag: release/0.68.0, hash for the release tag: > > 46859a0e7e9003186e82cc9b96068e83993bd3f0 > > incubator-streampipes-extensions, staged at [3], release tag: > > release/0.68.0, hash for the release tag: > > e387384a52470ab771e2f19c9e9347355b699e7e > > incubator-streampipes-installer, staged at [4], release tag: > > release/0.68.0, > > hash for the release tag: 1d6bc511debc83f63b78cf33f1bfc5efef2da0ce > > > > Per [5] "Before voting +1, [P]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 [6]. The KEYS file is available > > at [7] > > > > As we are missing two more IPMC-binding votes, we would really appreciate > > if > > any IPMC member would be willing to review our release candidate. Thanks > > for > > your support! > > > > Dominik > > > > [1] > > > > https://dist.apache.org/repos/dist/dev/incubator/streampipes/core/0.68.0/rc1 > > [2] > > > > https://repository.apache.org/content/repositories/orgapachestreampipes-1012 > > [3] > > > > https://dist.apache.org/repos/dist/dev/incubator/streampipes/extensions/0.68 > > .0/rc1 > > [4] > > > > https://dist.apache.org/repos/dist/dev/incubator/streampipes/installer/0.68. > > 0/rc1 > > <https://dist.apache.org/repos/dist/dev/incubator/streampipes/installer/0.68.0/rc1> > > [5] https://www.apache.org/dev/release.html#approving-a-release > > [6] > > > > https://cwiki.apache.org/confluence/display/STREAMPIPES/Validating+a+release > > [7] https://dist.apache.org/repos/dist/dev/incubator/streampipes/KEYS > > > > > > > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Apache StreamPipes 0.68.0 (incubating) RC1 release
Hi all, this is a call for a vote to release Apache StreamPipes (incubating) 0.68.0. Apache StreamPipes (incubating) is self-service Industrial IoT toolbox to enable non-technical users to connect, analyze and explore IIoT data streams. The Apache StreamPipes community has voted on a proposal to release Apache StreamPipes (incubating) 0.68.0 We now kindly ask the Incubator PMC members to review and vote on this release. Vote and result threads from the StreamPipes community: Result: https://lists.apache.org/thread.html/r61928e5e971812dc271fe678c7e9e3202622a8 442635da94f9034f00%40%3Cdev.streampipes.apache.org%3E Vote: https://lists.apache.org/thread.html/r0164a14c229a459a05ff305506238608575270 bf5a57111eed2dff3d%40%3Cdev.streampipes.apache.org%3E >From the PPMC vote, we carry over 1 binding IPMC vote: Christofer Dutz The vote will be open for at least 72 hours. Please vote accordingly: [] +1 approve (indicate what you validated - e.g., performed the checklist at [6]) [] +0 no opinion [] -1 reject (explanation required) Three artifacts are relevant for this vote: incubator-streampipes, staged at [1], available in Nexus at [2], release tag: release/0.68.0, hash for the release tag: 46859a0e7e9003186e82cc9b96068e83993bd3f0 incubator-streampipes-extensions, staged at [3], release tag: release/0.68.0, hash for the release tag: e387384a52470ab771e2f19c9e9347355b699e7e incubator-streampipes-installer, staged at [4], release tag: release/0.68.0, hash for the release tag: 1d6bc511debc83f63b78cf33f1bfc5efef2da0ce Per [5] "Before voting +1, [P]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 [6]. The KEYS file is available at [7] As we are missing two more IPMC-binding votes, we would really appreciate if any IPMC member would be willing to review our release candidate. Thanks for your support! Dominik [1] https://dist.apache.org/repos/dist/dev/incubator/streampipes/core/0.68.0/rc1 [2] https://repository.apache.org/content/repositories/orgapachestreampipes-1012 [3] https://dist.apache.org/repos/dist/dev/incubator/streampipes/extensions/0.68 .0/rc1 [4] https://dist.apache.org/repos/dist/dev/incubator/streampipes/installer/0.68. 0/rc1 [5] https://www.apache.org/dev/release.html#approving-a-release [6] https://cwiki.apache.org/confluence/display/STREAMPIPES/Validating+a+release [7] https://dist.apache.org/repos/dist/dev/incubator/streampipes/KEYS - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [MENTORS] April 2021 Incubator report timeline
Hi Justin, I think the list of expected reports below for April refers to reporting group 3 (usually reporting in March), but should be group 1 for April (plus a few podlings who didn't report last month) - is this correct? Dominik On 2021/03/29 03:47:24, Justin Mclean wrote: > Hi, > > Here the report timeline for March report: > Wed April 07 -- Podling reports due by end of day > Sun April 11 -- Shepherd reviews due by end of day > Sun April 11 -- Summary due by end of day > Tue April 13 -- Mentor signoff due by end of day > Wed April 14 -- Report submitted to Board > Wed April 21 -- Board meeting > > Expected to report are: > Age > Brpc > Crail > Doris > EventMesh > Hivemall > Hop > Livy > Marvin-AI > Nemo > NLPCraft > PageSpeed > PonyMail > Spot > StreamPipes > Toree > Wayang > Weex > > As usual you can find the report here [1] > > Thanks, > Justin > > 1. https://cwiki.apache.org/confluence/display/INCUBATOR/April2021 > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [VOTE] Graduate Apache IoTDB as TLP
+1 (non-binding) Great project! Dominik -Original Message- From: Xiangdong Huang Sent: Thursday, September 10, 2020 9:42 AM To: general@incubator.apache.org Subject: [VOTE] Graduate Apache IoTDB as TLP Dear all IPMCs: Following discussions with great support from our mentors, committers and community members. I would like to call for a formal VOTE for graduating Apache IoTDB (Incubating), as a Top Level Project. This is a formal voting thread about Apache IoTDB's graduation, please Vote: [ ] +1 - Recommend graduation of Apache IoTDB as a TLP [ ] 0 [ ] -1 - Do not recommend the graduation of Apache IoTDB because... The VOTE will open for at least 72 hours. Apache IoTDB (Incubating) entered the incubator in Nov 2018, the community has grown vibrantly since, with all the design, development happening on the Apache infrastructure, the "Apache Way". To list a few of the community's achievements, - Apache IoTDB name search has been approved - Accepted > 1300 PRs from 75 contributors - Migrated developer conversations to the list at d...@iotdb.apache.org (more than 3000 mails, without JIRA notifications, and gitbox, are sent by more than 160 persons) - There are 9 versions (3 major versions) released successfully conformant to Apache release policy by 5 release managers; - Invited 12 new committers (all of them accepted) - invited 4 of those new committers to join the PMC (all of them accepted) - Our proposed PMC is diverse and consists of members from more than 10 organizations Preparations and discussions history about the graduation: - The maturity assessment is done [2], - The community agreed on starting the graduation process in a formal vote [3] (result see [4]). And, I'd like to note that all our mentors also participated in the vote with a positive vote! - The community also decided about a suggestion for the initial VP, a charter [5, 6] and the initial PMC list [7]. - We also received positive feedback from the incubator general mailing list [8]. The draft of the resolution: Establish the Apache IoTDB 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 an IoT native database with high performance for data management and analysis, on the edge and the cloud. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache IoTDB Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache IoTDB Project be and hereby is responsible for the creation and maintenance of software related to an IoT native database with high performance for data management and analysis, on the edge and the cloud. and be it further RESOLVED, that the office of "Vice President, Apache IoTDB 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 IoTDB Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache IoTDB 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 IoTDB Project: * Chen Wang * Christofer Dutz * Dawei Liu * Gaofei Cao * Haonan Hou * Jialin Qiao * Jianmin Wang * Jincheng Sun * Jinrui Zhang * Julian Feinauer * Jun Yuan * Justin Mclean * Kevin A. McGrail * Kun Liu * Lei Rui * Rong Kang * Rui Liu * Shuo Zhang * Stefanie Zhao * Tian Jiang * Tianan Li * Willem Ning Jiang * Xiangdong Huang NOW, THEREFORE, BE IT FURTHER RESOLVED, that Xiangdong Huang be appointed to the office of Vice President, Apache IoTDB, 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 initial Apache IoTDB PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache IoTDB Project; and be it further RESOLVED, that the Apache IoTDB Project be and hereby is tasked with the migration and rationalization of the Apache Incubator IoTDB podling; and be
[RESULT][VOTE] Release Apache StreamPipes (incubating) 0.66.0
Hi all, The vote to release Apache StreamPipes (incubating) 0.66.0 has passed with three +1 binding votes. Binding votes: Christofer Dutz Julian Feinauer Justin Mclean Vote thread: https://lists.apache.org/thread.html/r451a554230a558e3035c4d1c870591d50c2cad f00c36b0f9ba4a4616%40%3Cgeneral.incubator.apache.org%3E Thanks a lot to Chris, Julian and Justin for taking your time to review our release candidate and valuable feedback! We will proceed with publishing the approved artifacts and sending out the announcements in the coming days. On behalf of the Apache StreamPipes Community, Dominik - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Release Apache StreamPipes (incubating) 0.66.0
Hi all, this is a call for a vote to release Apache StreamPipes (incubating) 0.66.0. Apache StreamPipes (incubating) is self-service Industrial IoT toolbox to enable non-technical users to connect, analyze and explore IIoT data streams. The Apache StreamPipes community has voted on and approved a proposal to release Apache StreamPipes (incubating) 0.66.0 We now kindly request the Incubator PMC members to review and vote on this release. Vote and result threads from the StreamPipes community: Result: https://lists.apache.org/thread.html/rff5cbadf51c91b27f38fd5fb55b8b1d495c6e9 f101c7552321e454e9%40%3Cdev.streampipes.apache.org%3E Vote: https://lists.apache.org/thread.html/rbac494d62247beec29a6ced23a0deff528c46e fe905828f1d8ec1a9a%40%3Cdev.streampipes.apache.org%3E >From the PPMC vote, we carry over 3 binding IPMC votes: Christofer Dutz Justin Mclean Julian Feinauer The vote will be open for at least 72 hours. Please vote accordingly: [] +1 approve (indicate what you validated - e.g., performed the checklist at [6]) [] +0 no opinion [] -1 reject (explanation required) Three artifacts are relevant for this vote: incubator-streampipes, staged at [1], available in Nexus at [2], release tag: release/0.66.0, hash for the release tag: b8c23e6785eaad79da6dd03072f2c1dcbfa467b4 incubator-streampipes-extensions, staged at [3], release tag: release/0.66.0, hash for the release tag: 44b7dd13c75058811a001f1aa6b3f6805285eb2d incubator-streampipes-installer, staged at [4], release tag: release/0.66.0, hash for the release tag: 1a8054239d8f42d66ee95e7b1282708f5f1266b0 A release validation guide is available at [6]. The KEYS file is available at [7] Thanks for taking your time for validating this release! Dominik [1] https://dist.apache.org/repos/dist/dev/incubator/streampipes/core/0.66.0/rc1 [2] https://repository.apache.org/content/repositories/orgapachestreampipes-1006 [3] https://dist.apache.org/repos/dist/dev/incubator/streampipes/extensions/0.66 .0/rc1 [4] https://dist.apache.org/repos/dist/dev/incubator/streampipes/installer/0.66. 0/rc1 [5] https://www.apache.org/dev/release.html#approving-a-release [6] https://cwiki.apache.org/confluence/display/STREAMPIPES/Validating+a+release [7] https://dist.apache.org/repos/dist/dev/incubator/streampipes/KEYS - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [VOTE] Accept NuttX into the Apache Incubator
+1 (non-binding) Dominik -Original Message- From: 俊平堵 Sent: Wednesday, December 4, 2019 6:32 AM To: general@incubator.apache.org Subject: [VOTE] Accept NuttX into the Apache Incubator Hi folks, The [DISCUSS] thread on NuttX has died down. Accordingly, I would like to call a VOTE to accept NuttX into the Apache Incubator. Please cast your vote: [ ] +1, bring NuttX into the Incubator [ ] +0, I don't care either way [ ] -1, do not bring NuttX into the Incubator, because... The vote will open at least for 72 hours and only votes from the Incubator PMC are binding, but votes from everyone are welcome. =Abstract= NuttX is a mature, real-time embedded operating system (RTOS). It has wide usage in IoT projects, control systems, robotics, drones, and many other systems. Unique properties of NuttX are its strict adherence to standards and its scalability. NuttX follows the Unix standards as defined by OpenGroup.org (POSIX, ANSI, and others). This allows for a high degree of portability. Scalability is supported through a configuration system that allows NuttX to run on the smallest embedded platforms and through high end single board computers. =Proposal= NuttX was released under a BSD 3-Clause license on February 17, 2007. >From that time until now it has been managed by a single person, Gregory Nutt. The user base of NuttX has grown to probably thousands of projects and perhaps a hundred active developments at any time. The code base has grown to around 1.5 million lines of code (according to OpenHub.com). NuttX has benefited from this single person management because this has resulted in a consistent architecture and controlled growth. But now it is time to open this project to the participation of others because this consistent architecture assures solid future growth, and because the magnitude of effort required to support the RTOS exceeds the capability of a single person, but also because users of NuttX require a stable road map going forward that does not depend on a single person. For these reasons, I propose that NuttX enter the Apache Incubator as a first step in opening the project to wider participation. =Initial Goals= The initial goal will be to move the existing BSD code base to Apache and integrate with the Apache development process and infrastructure. A primary goal of incubation will be to grow and diversify the NuttX community. We will convert that code base to the Apache license during incubation. =Current Status= As previously mentioned, NuttX is a mature, stable product in wide use in embedded products. ==Meritocracy== We value meritocracy and we understand that it is the basis for an open community that encourages multiple companies and individuals to contribute and be invested in the project’s future. We will encourage and monitor participation and make sure to extend privileges and responsibilities to all contributors. Being a mature project, NuttX already has an extensive user base with many people who understand the software, who have committed hundreds of changes, and are happy to participate in the project. I believe that with a little guidance and formalization, a PMC and a large group of experienced committers can quickly be established. ==Community== NuttX has a large, active community. Communication is via a Google group at https://groups.google.com/forum/#!forum/nuttx where there are 395 members as of this writing. Code is currently maintained at Bitbucket.org at https://bitbucket.org/nuttx/. Other communications are through Bitbucket issues and also via Slack for focused, interactive discussions. Keeping up with the communications, requests for help, issues, and contributions is more than a full time job at this time. ==Core Developers== NuttX was initially developed by Gregory Nutt, released as an open source project on February 17, 2007, and is still under active development. There are several dozen, active, frequent contributors involved with the project. The core OS can be considered finished at this point, but development continues in specialized areas of networking, IoT, cryptography, tools, and other more specialized functions. =Alignment= NuttX is an original development with some small percentage of ported code. It stands alone depends on no other projects. =Known Risks= ==Orphaned Products== We are committed to the future development of NuttX and understand that graduation to a TLP, while preferable, is not the only positive outcome of incubation. Should the NuttX project be accepted by the Incubator, the prospective PPMC would be willing to agree to a target incubation period of 2 years or less, knowing that every Incubator project incurs a certain cost in terms of ASF infrastructure and volunteer time. ==Inexperience with Open Source== None of the initial committers are Apache members and we will need some help in learning the Apache Way. ==S
RE: [RESULT] [VOTE] Accept StreamPipes into the Apache Incubator
Hi all,
super cool!
Special thanks to Chris Dutz for his great support in creating this proposal.
We absolutely look forward to transitioning StreamPipes to an Apache community
project.
Dominik
-Original Message-
From: Julian Feinauer
Sent: Monday, November 11, 2019 9:56 AM
To: general@incubator.apache.org
Subject: Re: [RESULT] [VOTE] Accept StreamPipes into the Apache Incubator
Congratulations to the Streampipes Team : )
Julian
Am 11.11.19, 09:51 schrieb "Christofer Dutz" :
Hi all,
usually the initiator of the vote also closes it ...
However there were several "+1" without "binding" or "non-binding" so I had
to check the IPMC list in whimsy to find out.
And the results are:
+1 binding: 16
+1 non-binding: 2
0: 0
-1: 0
So the vote passes and I'll start the process on transitioning StreamPipes
into the incubator.
Chris
Am 11.11.19, 05:15 schrieb "Tim Mitsch" :
+1 (non-binding)
Great project & code-base
Good luck!
Am 07.11.19, 20:00 schrieb "Dominik Riemer" :
Hi all,
following up the [DISCUSS] thread on StreamPipes
(https://lists.apache.org/thread.html/1cf79ef65888f695b4b925fd67ef8a2b845f6b0931c251a0ff1115e1@%3Cgeneral.incubator.apache.org%3E),
I would like to call a VOTE to accept StreamPipes into the Apache Incubator.
Please cast your vote:
[ ] +1, bring StreamPipes into the Incubator
[ ] +0, I don't care either way
[ ] -1, do not bring StreamPipes into the Incubator, because...
The vote will open at least for 72 hours and only votes from the
Incubator PMC are binding, but votes from everyone are welcome.
Dominik
StreamPipes Proposal
(https://cwiki.apache.org/confluence/display/INCUBATOR/StreamPipesProposal)
== Abstract ==
StreamPipes is a self-service (Industrial) IoT toolbox to enable
non-technical users to connect, analyze and explore (Industrial) IoT data
streams.
= Proposal =
The goal of StreamPipes (www.streampipes.org) is to provide an
easy-to-use toolbox for non-technical users, e.g., domain experts, to exploit
data streams coming from (Industrial) IoT devices. Such users are provided with
an intuitive graphical user interface with the Pipeline Editor at its core.
Users are able to graphically model processing pipelines based on data sources
(streams), data processors and data sinks. Data processors and sinks are
self-contained microservices, which implement either stateful or stateless
processing logic (e.g., a trend detection or image classifier). Their
processing logic is implemented using one of several provided wrappers (we
currently have wrappers for standalone/Edge-based processing, Apache Flink,
Siddhi and working wrapper prototypes for Apache Kafka Streams and Spark, in
the future we also plan to integrate with Apache Beam). An SDK allows to easily
create new pipeline elements. Pipeline elements can be installed at runtime. To
support users in creating pipelines, an underlying semantics-based data model
enables pipeline elements to express requirements on incoming data streams that
need to be fulfilled, thus reducing modeling errors.
Data streams are integrated by using StreamPipes Connect, which
allows to connect data sources (based on standard protocols, such as MQTT,
Kafka, Pulsar, OPC-UA and further PLC4X-supported protocols) without further
programming using a graphical wizard. Additional user-faced modules of
StreamPipes are a Live dashboard to quickly explore IoT data streams and a
wizard that generates code templates for new pipeline elements, a Pipeline
Element Installer used to extend the algorithm feature set at runtime.
=== Background ===
StreamPipes was started in 2014 by researchers from FZI Research
Center for Information Technology in Karlsruhe, Germany. The original prototype
was funded by an EU project centered around predictive analytics for the
manufacturing domain. Since then, StreamPipes was constantly improved and
extended by public funding mainly from federal German ministries. In early
2018, the source code was officially released under the Apache License 2.0. At
the same time, while we focused on bringing the research prototype to a
production-grade tool, the first companies started to use StreamPipes.
Currently, the primary goal is to widen the user and developer base. At
ApacheCon NA 2019, after having talked to many people from the Apache
Community, we finally decided that we would like to bring StreamPipes to the
Apache Incubator.
[VOTE] Accept StreamPipes into the Apache Incubator
essed by the collaboration among individual projects, we decided that (from our point of view) the ASF is the ideal place to be the future home of StreamPipes. === Initial Goals === * Move the existing codebase to Apache * Fully align with Apache development- and release processes * Perform name search and do a thorough review of existing licenses * First Apache release === Current Status === ** Meritocracy ** We are absolutely committed to strengthen StreamPipes as a real community-driven open source project. The existing committer base is highly motivated to foster the open source way in the industrial IoT sector and, together with existing Apache communities focused on this domain, provide open source tooling for Industrial IoT projects in the same way Apache offers in the Big Data space, for instance. The development philosophy behind StreamPipes has always followed the principles of meritocracy - although most committers are still active in the project, we managed to onboard new, committed developers regularly. 2 people, who are today core of the developer team, have joined during the past year. Therefore, we would aim to continuously expand the PMC and committer base based on merit. ** Community ** Since being open-sourced in 2018, the public interest in StreamPipes has steadily grown. Several companies, mainly from the manufacturing domain, have tested StreamPipes in form of proof-of-concept projects. First companies have started to use StreamPipes in production. This was due to a high number of events from meetups, research conferences, demo sessions up to hackathons we participated or organized during the past two years. After having generated a general interest in StreamPipes, our next focus will be to find more committers to diversify the contributor base. ** Core Developers ** The core developers of the system are Dominik Riemer, Philipp Zehnder, Patrick Wiener and Johannes Tex. All core developers are initial committers in the current proposal. Some former students who recently started to work at companies and who have also worked on the project with great commitment, will be asked to further contribute to the project. ** Alignment ** StreamPipes has dependencies to a lot of existing Apache projects - this is one reason why we think that the ASF is the best future home for StreamPipes. The messaging layer is based on Apache Kafka (and also Apache Pulsar as a future option), and runtime wrappers exist for Apache Flink, Apache Spark and Apache Kafka Streams. StreamPipes Connect already includes adapters for several Apache projects. Most importantly, we integrate (and plan to deepen the integration) with IIoT-focused projects such as Apache PLC4X. Also, several data sinks exist to send messages to tools from other Apache projects (e.g., Apache Kafka, Apache Pulsar, and Apache IoTDB). Together with these tools (and also after having talked to the core developers after this year's ApacheCon) we are absolutely convinced that a tight integration between these tools will strengthen the open source IoT ecosystem. === Known Risks === ** Orphaned Products ** We don't expect the risk of an orphaned product. The initial committers have worked on the project for years and are absolutely committed to making this open source tool a great success. All initial committers are committed to work on StreamPipes in their free time. ** Inexperience with Open Source ** All initial committers have years of expertise related to open source development and understand what open source means. However, none of the initial committers are currently committers to Apache projects, although some have already contributed to some projects. From a variety of events and from intensively studying Apache mailing lists, we are sure that the Apache Way is the way we'd like the project to move into the future. We expect to benefit from the experiences from the ASF in building successful open source projects. ** Length of Incubation ** We are aware that incubation is a process that is focused on building the community, learning the Apache Way and other important things such as learning the release process and handling licensing and trademark issues. We are also aware that, although there is a steadily increasing interest in StreamPipes, a major challenge we would need (and are willing) to work on during the incubation phase is widening the committer base. We look forward to that as a large developer base is exactly what we are striving for. ** Homogeneous Developers ** Most current developers work for the same institution (FZI). The motivation of all developers goes beyond their commitment to work and all current committers work on StreamPipes in their free time. Recently, we have received first pull requests from external contributors and a growing interest from users and companies outside of FZI. First manufacturing companies have already evaluated and ado
RE: [DISCUSS] StreamPipes proposal
Yes, it would be super cool to have you as a mentor, thanks! We'll update the list in the wiki. Dominik -Original Message- From: Jean-Baptiste Onofré Sent: Friday, November 1, 2019 6:49 PM To: general@incubator.apache.org Subject: Re: [DISCUSS] StreamPipes proposal Hi Dominik, it's an interesting proposal ! It sounds kind of integration platform for IoT protocols (a specialized platform compared to frameworks like Apache Camel or NiFi). I would be happy to be mentor on the podling if you want ! Regards JB On 01/11/2019 16:51, Dominik Riemer wrote: > Hi all, > > following up my previous mail, we would now like to start an open discussion > on bringing StreamPipes to the Apache Incubator. StreamPipes is an open > source self-service toolbox for analyzing (Industrial) IoT data streams. We > are aware that one of our main challenges will be to diversify the developer > base and we are willing (and look forward!) to work on that. > > The proposal can be found below and is also listed in the Incubator wiki: > https://cwiki.apache.org/confluence/display/INCUBATOR/StreamPipesProposal, > thanks @Chris Dutz for creating the page! > > We appreciate anyone who would be willing to support us a an additional > mentor! > > > Dominik > > > > StreamPipes Proposal > > == Abstract == > StreamPipes is a self-service (Industrial) IoT toolbox to enable > non-technical users to connect, analyze and explore (Industrial) IoT data > streams. > > = Proposal = > > The goal of StreamPipes (www.streampipes.org) is to provide an easy-to-use > toolbox for non-technical users, e.g., domain experts, to exploit data > streams coming from (Industrial) IoT devices. Such users are provided with an > intuitive graphical user interface with the Pipeline Editor at its core. > Users are able to graphically model processing pipelines based on data > sources (streams), data processors and data sinks. Data processors and sinks > are self-contained microservices, which implement either stateful or > stateless processing logic (e.g., a trend detection or image classifier). > Their processing logic is implemented using one of several provided wrappers > (we currently have wrappers for standalone/Edge-based processing, Apache > Flink, Siddhi and working wrapper prototypes for Apache Kafka Streams and > Spark, in the future we also plan to integrate with Apache Beam). An SDK > allows to easily create new pipeline elements. Pipeline elements can be > installed at runtime. To support users in creating pipelines, an underlying > semantics-based data model enables pipeline elements to express requirements > on incoming data streams that need to be fulfilled, thus reducing modeling > errors. > Data streams are integrated by using StreamPipes Connect, which allows to > connect data sources (based on standard protocols, such as MQTT, Kafka, > Pulsar, OPC-UA and further PLC4X-supported protocols) without further > programming using a graphical wizard. Additional user-faced modules of > StreamPipes are a Live dashboard to quickly explore IoT data streams and a > wizard that generates code templates for new pipeline elements, a Pipeline > Element Installer used to extend the algorithm feature set at runtime. > > === Background === > StreamPipes was started in 2014 by researchers from FZI Research Center for > Information Technology in Karlsruhe, Germany. The original prototype was > funded by an EU project centered around predictive analytics for the > manufacturing domain. Since then, StreamPipes was constantly improved and > extended by public funding mainly from federal German ministries. In early > 2018, the source code was officially released under the Apache License 2.0. > At the same time, while we focused on bringing the research prototype to a > production-grade tool, the first companies started to use StreamPipes. > Currently, the primary goal is to widen the user and developer base. At > ApacheCon NA 2019, after having talked to many people from the Apache > Community, we finally decided that we would like to bring StreamPipes to the > Apache Incubator. > > === Rationale === > The (Industrial) IoT domain is a highly relevant and emerging sector. > Currently, IoT platforms are offered by many vendors ranging from SMEs up to > large enterprises. We believe that open source alternatives are an important > cornerstone for manufacturing companies to easily adopt data-driven decision > making. From our point of view, StreamPipes fits very well into the existing > (I)IoT ecosystem within the ASF, with projects such as Apache PLC4X focusing > on connecting machine data from PLCs, or other tools we are also using either > in the core of
[DISCUSS] StreamPipes proposal
impressed by the collaboration among individual projects, we decided that (from our point of view) the ASF is the ideal place to be the future home of StreamPipes. === Initial Goals === * Move the existing codebase to Apache * Fully align with Apache development- and release processes * Perform name search and do a thorough review of existing licenses * First Apache release === Current Status === ** Meritocracy ** We are absolutely committed to strengthen StreamPipes as a real community-driven open source project. The existing committer base is highly motivated to foster the open source way in the industrial IoT sector and, together with existing Apache communities focused on this domain, provide open source tooling for Industrial IoT projects in the same way Apache offers in the Big Data space, for instance. The development philosophy behind StreamPipes has always followed the principles of meritocracy - although most committers are still active in the project, we managed to onboard new, committed developers regularly. 2 people, who are today core of the developer team, have joined during the past year. Therefore, we would aim to continuously expand the PMC and committer base based on merit. ** Community ** Since being open-sourced in 2018, the public interest in StreamPipes has steadily grown. Several companies, mainly from the manufacturing domain, have tested StreamPipes in form of proof-of-concept projects. First companies have started to use StreamPipes in production. This was due to a high number of events from meetups, research conferences, demo sessions up to hackathons we participated or organized during the past two years. After having generated a general interest in StreamPipes, our next focus will be to find more committers to diversify the contributor base. ** Core Developers ** The core developers of the system are Dominik Riemer, Philipp Zehnder, Patrick Wiener and Johannes Tex. All core developers are initial committers in the current proposal. Some former students who recently started to work at companies and who have also worked on the project with great commitment, will be asked to further contribute to the project. ** Alignment ** StreamPipes has dependencies to a lot of existing Apache projects - this is one reason why we think that the ASF is the best future home for StreamPipes. The messaging layer is based on Apache Kafka (and also Apache Pulsar as a future option), and runtime wrappers exist for Apache Flink, Apache Spark and Apache Kafka Streams. StreamPipes Connect already includes adapters for several Apache projects. Most importantly, we integrate (and plan to deepen the integration) with IIoT-focused projects such as Apache PLC4X. Also, several data sinks exist to send messages to tools from other Apache projects (e.g., Apache Kafka, Apache Pulsar, and Apache IoTDB). Together with these tools (and also after having talked to the core developers after this year's ApacheCon) we are absolutely convinced that a tight integration between these tools will strengthen the open source IoT ecosystem. === Known Risks === ** Orphaned Products ** We don't expect the risk of an orphaned product. The initial committers have worked on the project for years and are absolutely committed to making this open source tool a great success. All initial committers are committed to work on StreamPipes in their free time. ** Inexperience with Open Source ** All initial committers have years of expertise related to open source development and understand what open source means. However, none of the initial committers are currently committers to Apache projects, although some have already contributed to some projects. From a variety of events and from intensively studying Apache mailing lists, we are sure that the Apache Way is the way we'd like the project to move into the future. We expect to benefit from the experiences from the ASF in building successful open source projects. ** Length of Incubation ** We are aware that incubation is a process that is focused on building the community, learning the Apache Way and other important things such as learning the release process and handling licensing and trademark issues. We are also aware that, although there is a steadily increasing interest in StreamPipes, a major challenge we would need (and are willing) to work on during the incubation phase is widening the committer base. We look forward to that as a large developer base is exactly what we are striving for. ** Homogeneous Developers ** Most current developers work for the same institution (FZI). The motivation of all developers goes beyond their commitment to work and all current committers work on StreamPipes in their free time. Recently, we have received first pull requests from external contributors and a growing interest from users and companies outside of FZI. First manufacturing companies have already evaluated and adop
RE: Write Access to Incubator Wiki
Thank you very much Kenn, that's awesome! I'll add you as a mentor once we got access to the wiki, afterwards I'll also start a separate DISCUSS thread to discuss our proposal. Dominik -Original Message- From: Kenneth Knowles Sent: Thursday, October 31, 2019 1:49 AM To: general Subject: Re: Write Access to Incubator Wiki Cool! I see you have mentors lined up. I would love to also be involved as mentor. The list of initial committers seems a little small. Browsing the commit history it does seem to be dominated by just a couple of contributors. I see this is acknowledged (at least implicitly) in the proposal. I expect a principal challenge will be attracting diverse contributors, committers, and PMC to ensure this project survives independent of any particular entity (individual or corporate). Kenn On Wed, Oct 30, 2019 at 1:16 PM Dominik Riemer wrote: > Hi all, > > > > a short introduction to myself: My name is Dominik Riemer and I'm a > co-initiator of StreamPipes, an open source self-service toolbox for > analyzing IoT data streams. After presenting the tool at this year's > ApacheCon NA, followed by very friendly and fruitful discussions with > many people from the Apache community, we are sure that we'd like > continue the development of StreamPipes as an Apache community > project. Before we start a discussion process, I'd like to ask to get > write access to the Incubator wiki (username: riemer). An initial draft of > the proposal is attached below. > > > > Thanks for your help! > > Dominik > > > > > > > > > > StreamPipes - Apache Incubator Proposal, Proposal Draft > > > > == Abstract == > > StreamPipes is a self-service (Industrial) IoT toolbox to enable > non-technical users to connect, analyze and explore (Industrial) IoT > data streams. > > > > = Proposal = > > > > The goal of StreamPipes > (www.streampipes.org<http://www.streampipes.org>) > is to provide an easy-to-use toolbox for non-technical users, e.g., > domain experts, to exploit data streams coming from (Industrial) IoT > devices. Such users are provided with an intuitive graphical user > interface with the Pipeline Editor at its core. Users are able to > graphically model processing pipelines based on data sources (streams), data > processors and data sinks. > Data processors and sinks are self-contained microservices, which > implement either stateful or stateless processing logic (e.g., a trend > detection or image classifier). Their processing logic is implemented > using one of several provided wrappers (we currently have wrappers for > standalone/Edge-based processing, Apache Flink, Siddhi and working > wrapper prototypes for Apache Kafka Streams and Spark, in the future > we also plan to integrate with Apache Beam). An SDK allows to easily > create new pipeline elements. Pipeline elements can be installed at > runtime. To support users in creating pipelines, an underlying > semantics-based data model enables pipeline elements to express > requirements on incoming data streams that need to be fulfilled, thus > reducing modeling errors. > > Data streams are integrated by using StreamPipes Connect, which allows > to connect data sources (based on standard protocols, such as MQTT, > Kafka, Pulsar, OPC-UA and further PLC4X-supported protocols) without > further programming using a graphical wizard. Additional user-faced > modules of StreamPipes are a Live dashboard to quickly explore IoT > data streams and a wizard that generates code templates for new > pipeline elements, a Pipeline Element Installer used to extend the algorithm > feature set at runtime. > > > > === Background === > > StreamPipes was started in 2014 by researchers from FZI Research > Center for Information Technology in Karlsruhe, Germany. The original > prototype was funded by an EU project centered around predictive > analytics for the manufacturing domain. Since then, StreamPipes was > constantly improved and extended by public funding mainly from federal > German ministries. In early 2018, the source code was officially released > under the Apache License 2.0. > At the same time, while we focused on bringing the research prototype > to a production-grade tool, the first companies started to use StreamPipes. > Currently, the primary goal is to widen the user and developer base. > At ApacheCon NA 2019, after having talked to many people from the > Apache Community, we finally decided that we would like to bring > StreamPipes to the Apache Incubator. > > > > === Rationale === > > The (Industrial) IoT domain is a highly relevant and emerging
Write Access to Incubator Wiki
Hi all, a short introduction to myself: My name is Dominik Riemer and I'm a co-initiator of StreamPipes, an open source self-service toolbox for analyzing IoT data streams. After presenting the tool at this year's ApacheCon NA, followed by very friendly and fruitful discussions with many people from the Apache community, we are sure that we'd like continue the development of StreamPipes as an Apache community project. Before we start a discussion process, I'd like to ask to get write access to the Incubator wiki (username: riemer). An initial draft of the proposal is attached below. Thanks for your help! Dominik StreamPipes - Apache Incubator Proposal, Proposal Draft == Abstract == StreamPipes is a self-service (Industrial) IoT toolbox to enable non-technical users to connect, analyze and explore (Industrial) IoT data streams. = Proposal = The goal of StreamPipes (www.streampipes.org<http://www.streampipes.org>) is to provide an easy-to-use toolbox for non-technical users, e.g., domain experts, to exploit data streams coming from (Industrial) IoT devices. Such users are provided with an intuitive graphical user interface with the Pipeline Editor at its core. Users are able to graphically model processing pipelines based on data sources (streams), data processors and data sinks. Data processors and sinks are self-contained microservices, which implement either stateful or stateless processing logic (e.g., a trend detection or image classifier). Their processing logic is implemented using one of several provided wrappers (we currently have wrappers for standalone/Edge-based processing, Apache Flink, Siddhi and working wrapper prototypes for Apache Kafka Streams and Spark, in the future we also plan to integrate with Apache Beam). An SDK allows to easily create new pipeline elements. Pipeline elements can be installed at runtime. To support users in creating pipelines, an underlying semantics-based data model enables pipeline elements to express requirements on incoming data streams that need to be fulfilled, thus reducing modeling errors. Data streams are integrated by using StreamPipes Connect, which allows to connect data sources (based on standard protocols, such as MQTT, Kafka, Pulsar, OPC-UA and further PLC4X-supported protocols) without further programming using a graphical wizard. Additional user-faced modules of StreamPipes are a Live dashboard to quickly explore IoT data streams and a wizard that generates code templates for new pipeline elements, a Pipeline Element Installer used to extend the algorithm feature set at runtime. === Background === StreamPipes was started in 2014 by researchers from FZI Research Center for Information Technology in Karlsruhe, Germany. The original prototype was funded by an EU project centered around predictive analytics for the manufacturing domain. Since then, StreamPipes was constantly improved and extended by public funding mainly from federal German ministries. In early 2018, the source code was officially released under the Apache License 2.0. At the same time, while we focused on bringing the research prototype to a production-grade tool, the first companies started to use StreamPipes. Currently, the primary goal is to widen the user and developer base. At ApacheCon NA 2019, after having talked to many people from the Apache Community, we finally decided that we would like to bring StreamPipes to the Apache Incubator. === Rationale === The (Industrial) IoT domain is a highly relevant and emerging sector. Currently, IoT platforms are offered by many vendors ranging from SMEs up to large enterprises. We believe that open source alternatives are an important cornerstone for manufacturing companies to easily adopt data-driven decision making. From our point of view, StreamPipes fits very well into the existing (I)IoT ecosystem within the ASF, with projects such as Apache PLC4X focusing on connecting machine data from PLCs, or other tools we are also using either in the core of StreamPipes or with integrations (Apache Kafka, Apache IoTDB, Apache Pulsar). StreamPipes itself focuses on enabling self-service IoT data analytics for non-technical users. The whole StreamPipes code is currently on Github. To get a rough estimate of the project size: * streampipes: Backend and core modules, ~3300 commits * streampipes-ui: User Interface, ~1300 commits * streampipes-pipeline-elements: ~100 Pipeline Elements (data processors/algorithms and sinks), ~500 Commits * streampipes-connect-adapters: ~20 Adapters to connect data, ~100 commits To achieve our goal to further extend the code base with new features, new connectors and new algorithms and to grow both the user and developer community, we believe that a community-driven development process is the best way to further develop StreamPipes. Finally, after having talked to commi
