Re: [DISCUSS] Graduate Apache SDAP (Incubating) as a Top Level Project
On Sat, Feb 24, 2024 at 11:43 AM Riley Kuttruff wrote: > > Thank you very much. We have actually found an issue with that release (GPL > licensed dependency) and have been working on preparing another release > candidate. It seems we have forgotten to cancel that vote. If you could solve this problem and release a version, my vote would be +1. By the way, Julian, as the sole active mentor of SDAP, has put in a lot of effort for this project. I believe this project will become an excellent TLP. > > On 2024/02/23 14:27:52 PJ Fanning wrote: > > +1 (binding) > > > > I had a look at the mailing lists and the community seems in a pretty good > > state. > > > > As a matter of interest, are you still looking at completing the v1.2.0 > > release [1]? If so, I could have a look at the RC over the weekend. > > > > [1] https://lists.apache.org/thread/vr4zf6zhg2yp41bjwvlpm1mp2nrycqcw > > > > On 2024/02/22 18:01:31 Riley Kuttruff wrote: > > > Hi all, > > > > > > Apache SDAP joined Incubator in October 2017. In the time since, we've > > > made significant progress towards maturing our community and our > > > project and adopting the Apache Way. > > > > > > After community discussion [1][2][3], the community has voted [4] that we > > > would like to proceed with graduation [5]. We now call upon the Incubator > > > PMC to review and discuss our progress and would appreciate any and all > > > feedback towards graduation. > > > > > > Below are some facts and project highlights from the incubation phase as > > > well as the draft resolution: > > > > > > - Our community consists of 21 committers, with 2 being mentors and > > > the remaining 19 serving as our PPMC > > > - Several pending and planned invites to bring on new committers and/or > > > PPMC members from additional organizations > > > - Completed 2 releases with 2 release managers - with a 3rd release run by > > > a 3rd release manager in progress > > > - Our software is currently being utilized by organizations such as NASA > > > Jet Propulsion Laboratory, NSF National Center for Atmospheric Research, > > > Florida State University, and George Mason University in support of > > > projects > > > such as the NASA Sea Level Change Portal, Estimating the Circulation and > > > Climate of the Ocean (ECCO) project, GRACE/GRACE-FO, Cloud-based > > > Data Match-Up Service, Integrated Digital Earth Analysis System (IDEAS), > > > and many others. > > > - Opened 400+ PRs across 3 main code repositories, 350+ of which are > > > merged or closed (some are pending our next release) > > > - Maturity model self assessment [6] > > > > > > We have resolved all branding issues we are aware of: logo, GitHub, > > > Website, etc > > > > > > We’d like to also extend a sincere thank you to our mentors, current and > > > former for their invaluable insight and assistance with getting us to this > > > point. > > > > > > Thank you, Julian, Jörn, Trevor, Lewis, Suneel, and Raphael! > > > > > > --- > > > > > > Establish the Apache SDAP 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 integrated data analytic center for Big Science problems. > > > > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > > > (PMC), to be known as the "Apache SDAP Project", be and hereby is > > > established pursuant to Bylaws of the Foundation; and be it further > > > > > > RESOLVED, that the Apache SDAP Project be and hereby is responsible > > > for the creation and maintenance of software related to an integrated data > > > analytic center for Big Science problems; and be it further > > > > > > RESOLVED, that the office of "Vice President, Apache SDAP" 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 SDAP > > > Project, and to have primary responsibility for management of the > > > projects within the scope of responsibility of the Apache SDAP > > > 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 SDAP Project: > > > > > > - Edward M Armstrong > > > - Nga Thien Chung > > > - Thomas Cram > > > - Frank Greguska > > > - Thomas Huang > > > - Julian Hyde > > > - Joseph C. Jacob > > > - Jason Kang > > > - Riley Kuttruff > > > - Thomas G Loubrieu > > > - Kevin Marlis > > > - Stepheny Perez > > > - Wai Linn Phyo > > > > > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Nga Thien Chung > > > be appointed to the office of Vice President, Apache SDAP, to serve in > > > accordance with and subject to the direction of
Re: Podling web sites: .incubator. required?
+1 non-binding Switching domains and mailing lists requires significant additional effort from the PPMC and INFRA. I recommand all podling use http://podling.apache.org/ at the very first. On Wed, Feb 28, 2024, at 08:16, Craig Russell wrote: > It was policy at one point for podlings to have .incubator. in their > home page url. But many podlings now have transitioned away from this > and simply use their podling.apache.org name. The policy document is a > bit iffy on the subject: > https://incubator.apache.org/guides/branding.html > >> After a podling has been approved, the lists are created, and the initial >> code drop has commenced, you MUST refer to the podling as Apache >> Podling-Name AND mention that the project is under Incubation. Suitable >> mentions include: >> >> • Inclusion of the http://podling-name.incubator.apache.org/ URL >> >> • Apache Podling-Name is currently undergoing Incubation at the Apache >> Software Foundation. >> >> The Incubator PMC (IPMC) must approve other references before you publish >> them. You only need to make these statements upon the first reference to the >> podling in a document. > > I feel this is very much like the former requirement for mail lists to > include incubator.apache.org as part of their name. This turned out to > be a huge waste of time for the podling as well as for infra when upon > graduation all of the documentation and tooling for mail lists had to > change. > > I would propose that as part of our official policy we recommend the > podling's url as https://podling.apache.org and get rid of the > .incubator. in the url. > > WDYT? > > 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 -- Xuanwo - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Podling web sites: .incubator. required?
+1 (non binding) from me, it will release the burden a lot for graduation. Best, Keyong Zhou Craig Russell 于2024年2月28日周三 08:18写道： > It was policy at one point for podlings to have .incubator. in their home > page url. But many podlings now have transitioned away from this and simply > use their podling.apache.org name. The policy document is a bit iffy on > the subject: > https://incubator.apache.org/guides/branding.html > > > After a podling has been approved, the lists are created, and the > initial code drop has commenced, you MUST refer to the podling as Apache > Podling-Name AND mention that the project is under Incubation. Suitable > mentions include: > > > > • Inclusion of the http://podling-name.incubator.apache.org/ URL > > > > • Apache Podling-Name is currently undergoing Incubation at the > Apache Software Foundation. > > > > The Incubator PMC (IPMC) must approve other references before you > publish them. You only need to make these statements upon the first > reference to the podling in a document. > > I feel this is very much like the former requirement for mail lists to > include incubator.apache.org as part of their name. This turned out to be > a huge waste of time for the podling as well as for infra when upon > graduation all of the documentation and tooling for mail lists had to > change. > > I would propose that as part of our official policy we recommend the > podling's url as https://podling.apache.org and get rid of the > .incubator. in the url. > > WDYT? > > 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 > >
Re: Podling web sites: .incubator. required?
+1 for me. While I don't dig into the details, for the podlings I mentored, although we only ask for the name.apache.org domain, there is a name.incubator.apache.org online redirected to name.apache.org. Best, tison. Justin Mclean 于2024年2月28日周三 10:21写道： > > HI, > > > I would propose that as part of our official policy we recommend the > > podling's url as https://podling.apache.org and get rid of the .incubator. > > in the url. > > > > WDYT? > > > +1 from me. > > Kind Regards, > Justin > - > 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: Podling web sites: .incubator. required?
HI, > I would propose that as part of our official policy we recommend the > podling's url as https://podling.apache.org and get rid of the .incubator. in > the url. > > WDYT? +1 from me. Kind Regards, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[ANNOUNCE] Apache Pekko 1.0.3-M1 released
The Apache Pekko (Incubating) Team is happy to announce the release of Apache Pekko (Incubating) 1.0.3-M1. This milestone release is aimed at testing some new support for users who want to add Pekko nodes to an existing Akka cluster. This support is experimental. This release should not be used in production. Apache Pekko (Incubating) is an open source toolkit and runtime simplifying the construction of concurrent and distributed applications on the JVM. It is a fork of Akka and has come about because Akka has moved from being Apache licensed to being licensed under a Business Software License. This release covers the core modules. Other modules like Pekko HTTP are released separately. Download Links: https://pekko.apache.org/download.html#pekko-core Release Notes: https://pekko.apache.org/docs/pekko/1.0/release-notes/index.html#1-0-3-m1 Website: https://pekko.apache.org Issues: https://github.com/apache/incubator-pekko/issues Mailing list: d...@pekko.apache.org Jars are published to Maven Central using the groupId: org.apache.pekko Thanks to everyone who participated in the development and release. Apache Pekko (Incubating) Team
Podling web sites: .incubator. required?
It was policy at one point for podlings to have .incubator. in their home page url. But many podlings now have transitioned away from this and simply use their podling.apache.org name. The policy document is a bit iffy on the subject: https://incubator.apache.org/guides/branding.html > After a podling has been approved, the lists are created, and the initial > code drop has commenced, you MUST refer to the podling as Apache Podling-Name > AND mention that the project is under Incubation. Suitable mentions include: > > • Inclusion of the http://podling-name.incubator.apache.org/ URL > > • Apache Podling-Name is currently undergoing Incubation at the Apache > Software Foundation. > > The Incubator PMC (IPMC) must approve other references before you publish > them. You only need to make these statements upon the first reference to the > podling in a document. I feel this is very much like the former requirement for mail lists to include incubator.apache.org as part of their name. This turned out to be a huge waste of time for the podling as well as for infra when upon graduation all of the documentation and tooling for mail lists had to change. I would propose that as part of our official policy we recommend the podling's url as https://podling.apache.org and get rid of the .incubator. in the url. WDYT? 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
Re: [VOTE] Graduate Apache Pekko (incubating) as a TLP
On Tue, 27 Feb 2024 at 18:45, PJ Fanning wrote: > > Thanks Sebastian. We have an issue already open [1]. We will try to > fix it as soon as possible but it could take a week or two. I'll > contact people to see if we can get this moving. The calls are built > in via some build tooling that we use (called Paradox). Paradox is > very modular so we will first have to track down the module that is > adding this and seeing what can be done to remove the call (whether it > is parameterised or if we will need to patch or fork the module). > > My experience with the calls to api.github.com is that it does not > appear that the auth details are sent. The calls quickly start getting > rejected because they are not authenticated. I use GitHub all the time > but the fact that I am logged in in other browser tabs does not appear > to cause my auth details to be sent with the Pekko web site visits. FTR, the issue is not that auth details are sent to a 3rd party site. Rather, it is the mere fact of the user's browser automatically visiting the site without the explicit consent of the user. > We still need to get rid of this and I will ensure that this is > treated as a high priority. Thanks > [1] https://github.com/apache/incubator-pekko-sbt-paradox/issues/110 > > On Tue, 27 Feb 2024 at 18:40, sebb wrote: > > > > The website accesses 3rd party resources (api.github.com). > > As far as know, this is contrary to the privacy policy. > > > > On Tue, 27 Feb 2024 at 16:39, tison wrote: > > > > > > +1 (binding) > > > > > > Let's rock. > > > > > > Best, > > > tison. > > > > > > Craig Russell 于2024年2月28日周三 00:37写道： > > > > > > > > +1 for graduation (binding) > > > > > > > > It's a good sign for you to take care of the KEYS and TM so quickly! > > > > Craig > > > > > > > > > On Feb 26, 2024, at 09:41, PJ Fanning wrote: > > > > > > > > > > Thanks Craig. I have created a PR to fix the KEYS link and add 'tm' to > > > > > Apache Pekko on the main page. > > > > > > > > > > https://github.com/apache/incubator-pekko-site/pull/87 > > > > > > > > > > > > > > > On Mon, 26 Feb 2024 at 18:14, Craig Russell > > > > > wrote: > > > > >> > > > > >> Hi, > > > > >> > > > > >> I noticed a few items that may be problematic if not resolved before > > > > >> the board votes on the resolution: > > > > >> > > > > >> 1. The home page https://pekko.apache.org has Apache Pekko in the > > > > >> first prominent usage but does not use a TM symbol as in Apache > > > > >> Pekko™. > > > > >> 2. The downloads page https://pekko.apache.org/download.html KEYS > > > > >> file for verifying checksums should link to the dist.apache.org file > > > > >> not the source repository. > > > > >> https://dist.apache.org/repos/dist/release/incubator/pekko/KEYS > > > > >> Of course, this should link to the non-incubator file once you have > > > > >> a release as a TLP. > > > > >> > > > > >> Other than that, looks good. > > > > >> > > > > >> Good luck, > > > > >> Craig > > > > >> > > > > >>> On Feb 26, 2024, at 03:24, PJ Fanning wrote: > > > > >>> > > > > >>> Hi everyone, > > > > >>> > > > > >>> We have positive feedback on the Pekko Vote thread [1] (result [2]). > > > > >>> > > > > >>> I'd like to start an official Incubator VOTE thread now. > > > > >>> > > > > >>> Below are some facts and project highlights from the incubation > > > > >>> phase > > > > >>> as well as the draft resolution: > > > > >>> > > > > >>> * All modules have at least a v1.0.0 release > > > > >>> * 19 releases (across 12 modules) [3] > > > > >>> * Evidence of good uptake of the Pekko releases and a large number > > > > >>> of > > > > >>> ecosystem libs now support Pekko - over 100 non Apache libraries use > > > > >>> Pekko libs under the hood > > > > >>> * well over 1000 PRs merged > > > > >>> * 25+ code contributors > > > > >>> * We've had 3 different release managers to date. > > > > >>> * dozens more users who have been involved in discussions, code > > > > >>> reviews, raising issues, etc. > > > > >>> * We have met all maturity criteria as outlined in [4]. > > > > >>> > > > > >>> > > > > >>> Please vote on the resolution pasted below to graduate Apache Pekko > > > > >>> from the Incubator to the Top Level Project. > > > > >>> > > > > >>> [ ] +1 Graduate Apache Pekko from the Incubator. > > > > >>> [ ] +0 No opinion. > > > > >>> [ ] -1 Don't graduate Apache Pekko from the Incubator because ... > > > > >>> > > > > >>> This vote will open for at least 72 hours. > > > > >>> > > > > >>> I would like to thank everyone who have participated in the Apache > > > > >>> Pekko community. I would also like to thank the Apache Incubator > > > > >>> community as well as Apache Infrastructure team and general ASF > > > > >>> community for your support. > > > > >>> > > > > >>> > > > > >>> [1] https://lists.apache.org/thread/q7jjmp7zpcxko607v5hvj514dyf6o8bx > > > > >>> [2] https://lists.apache.org/thread/tsb7b8bkgfkts1nstmj413qocztj0s5o > > > > >>> [3]
Re: [VOTE] Graduate Apache Pekko (incubating) as a TLP
I have merged a partial fix which removes the api.github.com calls for the Pekko home page and some of the top level pages. There is quite a lot more to do to get rid of them from all of our web pages though. https://github.com/apache/incubator-pekko-site/pull/88 On Tue, 27 Feb 2024 at 19:44, PJ Fanning wrote: > > Thanks Sebastian. We have an issue already open [1]. We will try to > fix it as soon as possible but it could take a week or two. I'll > contact people to see if we can get this moving. The calls are built > in via some build tooling that we use (called Paradox). Paradox is > very modular so we will first have to track down the module that is > adding this and seeing what can be done to remove the call (whether it > is parameterised or if we will need to patch or fork the module). > > My experience with the calls to api.github.com is that it does not > appear that the auth details are sent. The calls quickly start getting > rejected because they are not authenticated. I use GitHub all the time > but the fact that I am logged in in other browser tabs does not appear > to cause my auth details to be sent with the Pekko web site visits. > > We still need to get rid of this and I will ensure that this is > treated as a high priority. > > [1] https://github.com/apache/incubator-pekko-sbt-paradox/issues/110 > > On Tue, 27 Feb 2024 at 18:40, sebb wrote: > > > > The website accesses 3rd party resources (api.github.com). > > As far as know, this is contrary to the privacy policy. > > > > On Tue, 27 Feb 2024 at 16:39, tison wrote: > > > > > > +1 (binding) > > > > > > Let's rock. > > > > > > Best, > > > tison. > > > > > > Craig Russell 于2024年2月28日周三 00:37写道： > > > > > > > > +1 for graduation (binding) > > > > > > > > It's a good sign for you to take care of the KEYS and TM so quickly! > > > > Craig > > > > > > > > > On Feb 26, 2024, at 09:41, PJ Fanning wrote: > > > > > > > > > > Thanks Craig. I have created a PR to fix the KEYS link and add 'tm' to > > > > > Apache Pekko on the main page. > > > > > > > > > > https://github.com/apache/incubator-pekko-site/pull/87 > > > > > > > > > > > > > > > On Mon, 26 Feb 2024 at 18:14, Craig Russell > > > > > wrote: > > > > >> > > > > >> Hi, > > > > >> > > > > >> I noticed a few items that may be problematic if not resolved before > > > > >> the board votes on the resolution: > > > > >> > > > > >> 1. The home page https://pekko.apache.org has Apache Pekko in the > > > > >> first prominent usage but does not use a TM symbol as in Apache > > > > >> Pekko™. > > > > >> 2. The downloads page https://pekko.apache.org/download.html KEYS > > > > >> file for verifying checksums should link to the dist.apache.org file > > > > >> not the source repository. > > > > >> https://dist.apache.org/repos/dist/release/incubator/pekko/KEYS > > > > >> Of course, this should link to the non-incubator file once you have > > > > >> a release as a TLP. > > > > >> > > > > >> Other than that, looks good. > > > > >> > > > > >> Good luck, > > > > >> Craig > > > > >> > > > > >>> On Feb 26, 2024, at 03:24, PJ Fanning wrote: > > > > >>> > > > > >>> Hi everyone, > > > > >>> > > > > >>> We have positive feedback on the Pekko Vote thread [1] (result [2]). > > > > >>> > > > > >>> I'd like to start an official Incubator VOTE thread now. > > > > >>> > > > > >>> Below are some facts and project highlights from the incubation > > > > >>> phase > > > > >>> as well as the draft resolution: > > > > >>> > > > > >>> * All modules have at least a v1.0.0 release > > > > >>> * 19 releases (across 12 modules) [3] > > > > >>> * Evidence of good uptake of the Pekko releases and a large number > > > > >>> of > > > > >>> ecosystem libs now support Pekko - over 100 non Apache libraries use > > > > >>> Pekko libs under the hood > > > > >>> * well over 1000 PRs merged > > > > >>> * 25+ code contributors > > > > >>> * We've had 3 different release managers to date. > > > > >>> * dozens more users who have been involved in discussions, code > > > > >>> reviews, raising issues, etc. > > > > >>> * We have met all maturity criteria as outlined in [4]. > > > > >>> > > > > >>> > > > > >>> Please vote on the resolution pasted below to graduate Apache Pekko > > > > >>> from the Incubator to the Top Level Project. > > > > >>> > > > > >>> [ ] +1 Graduate Apache Pekko from the Incubator. > > > > >>> [ ] +0 No opinion. > > > > >>> [ ] -1 Don't graduate Apache Pekko from the Incubator because ... > > > > >>> > > > > >>> This vote will open for at least 72 hours. > > > > >>> > > > > >>> I would like to thank everyone who have participated in the Apache > > > > >>> Pekko community. I would also like to thank the Apache Incubator > > > > >>> community as well as Apache Infrastructure team and general ASF > > > > >>> community for your support. > > > > >>> > > > > >>> > > > > >>> [1] https://lists.apache.org/thread/q7jjmp7zpcxko607v5hvj514dyf6o8bx > > > > >>> [2]
Re: [VOTE] Graduate Apache Pekko (incubating) as a TLP
Thanks Sebastian. We have an issue already open [1]. We will try to fix it as soon as possible but it could take a week or two. I'll contact people to see if we can get this moving. The calls are built in via some build tooling that we use (called Paradox). Paradox is very modular so we will first have to track down the module that is adding this and seeing what can be done to remove the call (whether it is parameterised or if we will need to patch or fork the module). My experience with the calls to api.github.com is that it does not appear that the auth details are sent. The calls quickly start getting rejected because they are not authenticated. I use GitHub all the time but the fact that I am logged in in other browser tabs does not appear to cause my auth details to be sent with the Pekko web site visits. We still need to get rid of this and I will ensure that this is treated as a high priority. [1] https://github.com/apache/incubator-pekko-sbt-paradox/issues/110 On Tue, 27 Feb 2024 at 18:40, sebb wrote: > > The website accesses 3rd party resources (api.github.com). > As far as know, this is contrary to the privacy policy. > > On Tue, 27 Feb 2024 at 16:39, tison wrote: > > > > +1 (binding) > > > > Let's rock. > > > > Best, > > tison. > > > > Craig Russell 于2024年2月28日周三 00:37写道： > > > > > > +1 for graduation (binding) > > > > > > It's a good sign for you to take care of the KEYS and TM so quickly! > > > Craig > > > > > > > On Feb 26, 2024, at 09:41, PJ Fanning wrote: > > > > > > > > Thanks Craig. I have created a PR to fix the KEYS link and add 'tm' to > > > > Apache Pekko on the main page. > > > > > > > > https://github.com/apache/incubator-pekko-site/pull/87 > > > > > > > > > > > > On Mon, 26 Feb 2024 at 18:14, Craig Russell > > > > wrote: > > > >> > > > >> Hi, > > > >> > > > >> I noticed a few items that may be problematic if not resolved before > > > >> the board votes on the resolution: > > > >> > > > >> 1. The home page https://pekko.apache.org has Apache Pekko in the > > > >> first prominent usage but does not use a TM symbol as in Apache Pekko™. > > > >> 2. The downloads page https://pekko.apache.org/download.html KEYS file > > > >> for verifying checksums should link to the dist.apache.org file not > > > >> the source repository. > > > >> https://dist.apache.org/repos/dist/release/incubator/pekko/KEYS > > > >> Of course, this should link to the non-incubator file once you have a > > > >> release as a TLP. > > > >> > > > >> Other than that, looks good. > > > >> > > > >> Good luck, > > > >> Craig > > > >> > > > >>> On Feb 26, 2024, at 03:24, PJ Fanning wrote: > > > >>> > > > >>> Hi everyone, > > > >>> > > > >>> We have positive feedback on the Pekko Vote thread [1] (result [2]). > > > >>> > > > >>> I'd like to start an official Incubator VOTE thread now. > > > >>> > > > >>> Below are some facts and project highlights from the incubation phase > > > >>> as well as the draft resolution: > > > >>> > > > >>> * All modules have at least a v1.0.0 release > > > >>> * 19 releases (across 12 modules) [3] > > > >>> * Evidence of good uptake of the Pekko releases and a large number of > > > >>> ecosystem libs now support Pekko - over 100 non Apache libraries use > > > >>> Pekko libs under the hood > > > >>> * well over 1000 PRs merged > > > >>> * 25+ code contributors > > > >>> * We've had 3 different release managers to date. > > > >>> * dozens more users who have been involved in discussions, code > > > >>> reviews, raising issues, etc. > > > >>> * We have met all maturity criteria as outlined in [4]. > > > >>> > > > >>> > > > >>> Please vote on the resolution pasted below to graduate Apache Pekko > > > >>> from the Incubator to the Top Level Project. > > > >>> > > > >>> [ ] +1 Graduate Apache Pekko from the Incubator. > > > >>> [ ] +0 No opinion. > > > >>> [ ] -1 Don't graduate Apache Pekko from the Incubator because ... > > > >>> > > > >>> This vote will open for at least 72 hours. > > > >>> > > > >>> I would like to thank everyone who have participated in the Apache > > > >>> Pekko community. I would also like to thank the Apache Incubator > > > >>> community as well as Apache Infrastructure team and general ASF > > > >>> community for your support. > > > >>> > > > >>> > > > >>> [1] https://lists.apache.org/thread/q7jjmp7zpcxko607v5hvj514dyf6o8bx > > > >>> [2] https://lists.apache.org/thread/tsb7b8bkgfkts1nstmj413qocztj0s5o > > > >>> [3] https://incubator.apache.org/projects/pekko.html > > > >>> [4] > > > >>> https://cwiki.apache.org/confluence/display/PEKKO/Apache+Maturity+Model+Assessment+for+Pekko > > > >>> > > > >>> > > > >>> > > > >>> --- > > > >>> > > > >>> Establish the Apache Pekko 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
Re: [VOTE] Graduate Apache Pekko (incubating) as a TLP
The website accesses 3rd party resources (api.github.com). As far as know, this is contrary to the privacy policy. On Tue, 27 Feb 2024 at 16:39, tison wrote: > > +1 (binding) > > Let's rock. > > Best, > tison. > > Craig Russell 于2024年2月28日周三 00:37写道： > > > > +1 for graduation (binding) > > > > It's a good sign for you to take care of the KEYS and TM so quickly! > > Craig > > > > > On Feb 26, 2024, at 09:41, PJ Fanning wrote: > > > > > > Thanks Craig. I have created a PR to fix the KEYS link and add 'tm' to > > > Apache Pekko on the main page. > > > > > > https://github.com/apache/incubator-pekko-site/pull/87 > > > > > > > > > On Mon, 26 Feb 2024 at 18:14, Craig Russell wrote: > > >> > > >> Hi, > > >> > > >> I noticed a few items that may be problematic if not resolved before the > > >> board votes on the resolution: > > >> > > >> 1. The home page https://pekko.apache.org has Apache Pekko in the first > > >> prominent usage but does not use a TM symbol as in Apache Pekko™. > > >> 2. The downloads page https://pekko.apache.org/download.html KEYS file > > >> for verifying checksums should link to the dist.apache.org file not the > > >> source repository. > > >> https://dist.apache.org/repos/dist/release/incubator/pekko/KEYS > > >> Of course, this should link to the non-incubator file once you have a > > >> release as a TLP. > > >> > > >> Other than that, looks good. > > >> > > >> Good luck, > > >> Craig > > >> > > >>> On Feb 26, 2024, at 03:24, PJ Fanning wrote: > > >>> > > >>> Hi everyone, > > >>> > > >>> We have positive feedback on the Pekko Vote thread [1] (result [2]). > > >>> > > >>> I'd like to start an official Incubator VOTE thread now. > > >>> > > >>> Below are some facts and project highlights from the incubation phase > > >>> as well as the draft resolution: > > >>> > > >>> * All modules have at least a v1.0.0 release > > >>> * 19 releases (across 12 modules) [3] > > >>> * Evidence of good uptake of the Pekko releases and a large number of > > >>> ecosystem libs now support Pekko - over 100 non Apache libraries use > > >>> Pekko libs under the hood > > >>> * well over 1000 PRs merged > > >>> * 25+ code contributors > > >>> * We've had 3 different release managers to date. > > >>> * dozens more users who have been involved in discussions, code > > >>> reviews, raising issues, etc. > > >>> * We have met all maturity criteria as outlined in [4]. > > >>> > > >>> > > >>> Please vote on the resolution pasted below to graduate Apache Pekko > > >>> from the Incubator to the Top Level Project. > > >>> > > >>> [ ] +1 Graduate Apache Pekko from the Incubator. > > >>> [ ] +0 No opinion. > > >>> [ ] -1 Don't graduate Apache Pekko from the Incubator because ... > > >>> > > >>> This vote will open for at least 72 hours. > > >>> > > >>> I would like to thank everyone who have participated in the Apache > > >>> Pekko community. I would also like to thank the Apache Incubator > > >>> community as well as Apache Infrastructure team and general ASF > > >>> community for your support. > > >>> > > >>> > > >>> [1] https://lists.apache.org/thread/q7jjmp7zpcxko607v5hvj514dyf6o8bx > > >>> [2] https://lists.apache.org/thread/tsb7b8bkgfkts1nstmj413qocztj0s5o > > >>> [3] https://incubator.apache.org/projects/pekko.html > > >>> [4] > > >>> https://cwiki.apache.org/confluence/display/PEKKO/Apache+Maturity+Model+Assessment+for+Pekko > > >>> > > >>> > > >>> > > >>> --- > > >>> > > >>> Establish the Apache Pekko 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 Pekko: a toolkit and an ecosystem for building > > >>> highly concurrent, distributed, reactive and resilient applications > > >>> for Java and Scala. > > >>> > > >>> > > >>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > > >>> (PMC), to be known as the "Apache Pekko Project", be and hereby is > > >>> established pursuant to Bylaws of the Foundation; and be it further > > >>> > > >>> > > >>> RESOLVED, that the Apache Pekko Project be and hereby is responsible > > >>> for the creation and maintenance of software related to Pekko: a > > >>> toolkit and an ecosystem for building highly concurrent, distributed, > > >>> reactive and resilient applications for Java and Scala.; and be it > > >>> further > > >>> > > >>> > > >>> RESOLVED, that the office of "Vice President, Apache Pekko" 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 Pekko > > >>> Project, and to have primary responsibility for management of the > > >>> projects within the scope of responsibility of the
Re: [VOTE] Graduate Apache Pekko (incubating) as a TLP
+1 (binding) Let's rock. Best, tison. Craig Russell 于2024年2月28日周三 00:37写道： > > +1 for graduation (binding) > > It's a good sign for you to take care of the KEYS and TM so quickly! > Craig > > > On Feb 26, 2024, at 09:41, PJ Fanning wrote: > > > > Thanks Craig. I have created a PR to fix the KEYS link and add 'tm' to > > Apache Pekko on the main page. > > > > https://github.com/apache/incubator-pekko-site/pull/87 > > > > > > On Mon, 26 Feb 2024 at 18:14, Craig Russell wrote: > >> > >> Hi, > >> > >> I noticed a few items that may be problematic if not resolved before the > >> board votes on the resolution: > >> > >> 1. The home page https://pekko.apache.org has Apache Pekko in the first > >> prominent usage but does not use a TM symbol as in Apache Pekko™. > >> 2. The downloads page https://pekko.apache.org/download.html KEYS file for > >> verifying checksums should link to the dist.apache.org file not the source > >> repository. > >> https://dist.apache.org/repos/dist/release/incubator/pekko/KEYS > >> Of course, this should link to the non-incubator file once you have a > >> release as a TLP. > >> > >> Other than that, looks good. > >> > >> Good luck, > >> Craig > >> > >>> On Feb 26, 2024, at 03:24, PJ Fanning wrote: > >>> > >>> Hi everyone, > >>> > >>> We have positive feedback on the Pekko Vote thread [1] (result [2]). > >>> > >>> I'd like to start an official Incubator VOTE thread now. > >>> > >>> Below are some facts and project highlights from the incubation phase > >>> as well as the draft resolution: > >>> > >>> * All modules have at least a v1.0.0 release > >>> * 19 releases (across 12 modules) [3] > >>> * Evidence of good uptake of the Pekko releases and a large number of > >>> ecosystem libs now support Pekko - over 100 non Apache libraries use > >>> Pekko libs under the hood > >>> * well over 1000 PRs merged > >>> * 25+ code contributors > >>> * We've had 3 different release managers to date. > >>> * dozens more users who have been involved in discussions, code > >>> reviews, raising issues, etc. > >>> * We have met all maturity criteria as outlined in [4]. > >>> > >>> > >>> Please vote on the resolution pasted below to graduate Apache Pekko > >>> from the Incubator to the Top Level Project. > >>> > >>> [ ] +1 Graduate Apache Pekko from the Incubator. > >>> [ ] +0 No opinion. > >>> [ ] -1 Don't graduate Apache Pekko from the Incubator because ... > >>> > >>> This vote will open for at least 72 hours. > >>> > >>> I would like to thank everyone who have participated in the Apache > >>> Pekko community. I would also like to thank the Apache Incubator > >>> community as well as Apache Infrastructure team and general ASF > >>> community for your support. > >>> > >>> > >>> [1] https://lists.apache.org/thread/q7jjmp7zpcxko607v5hvj514dyf6o8bx > >>> [2] https://lists.apache.org/thread/tsb7b8bkgfkts1nstmj413qocztj0s5o > >>> [3] https://incubator.apache.org/projects/pekko.html > >>> [4] > >>> https://cwiki.apache.org/confluence/display/PEKKO/Apache+Maturity+Model+Assessment+for+Pekko > >>> > >>> > >>> > >>> --- > >>> > >>> Establish the Apache Pekko 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 Pekko: a toolkit and an ecosystem for building > >>> highly concurrent, distributed, reactive and resilient applications > >>> for Java and Scala. > >>> > >>> > >>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > >>> (PMC), to be known as the "Apache Pekko Project", be and hereby is > >>> established pursuant to Bylaws of the Foundation; and be it further > >>> > >>> > >>> RESOLVED, that the Apache Pekko Project be and hereby is responsible > >>> for the creation and maintenance of software related to Pekko: a > >>> toolkit and an ecosystem for building highly concurrent, distributed, > >>> reactive and resilient applications for Java and Scala.; and be it > >>> further > >>> > >>> > >>> RESOLVED, that the office of "Vice President, Apache Pekko" 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 Pekko > >>> Project, and to have primary responsibility for management of the > >>> projects within the scope of responsibility of the Apache Pekko > >>> 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 Pekko Project: > >>> > >>> Claude Warren (claude) > >>> Jean-Baptiste Onofré (jbonofre) > >>> Justin Mclean (jmclean) > >>> PJ Fanning (fanningpj) > >>> Roman Shaposhnik (rvs) > >>> Ryan Skraba (rskraba) > >>>
Re: [VOTE] Graduate Apache Pekko (incubating) as a TLP
+1 for graduation (binding) It's a good sign for you to take care of the KEYS and TM so quickly! Craig > On Feb 26, 2024, at 09:41, PJ Fanning wrote: > > Thanks Craig. I have created a PR to fix the KEYS link and add 'tm' to > Apache Pekko on the main page. > > https://github.com/apache/incubator-pekko-site/pull/87 > > > On Mon, 26 Feb 2024 at 18:14, Craig Russell wrote: >> >> Hi, >> >> I noticed a few items that may be problematic if not resolved before the >> board votes on the resolution: >> >> 1. The home page https://pekko.apache.org has Apache Pekko in the first >> prominent usage but does not use a TM symbol as in Apache Pekko™. >> 2. The downloads page https://pekko.apache.org/download.html KEYS file for >> verifying checksums should link to the dist.apache.org file not the source >> repository. >> https://dist.apache.org/repos/dist/release/incubator/pekko/KEYS >> Of course, this should link to the non-incubator file once you have a >> release as a TLP. >> >> Other than that, looks good. >> >> Good luck, >> Craig >> >>> On Feb 26, 2024, at 03:24, PJ Fanning wrote: >>> >>> Hi everyone, >>> >>> We have positive feedback on the Pekko Vote thread [1] (result [2]). >>> >>> I'd like to start an official Incubator VOTE thread now. >>> >>> Below are some facts and project highlights from the incubation phase >>> as well as the draft resolution: >>> >>> * All modules have at least a v1.0.0 release >>> * 19 releases (across 12 modules) [3] >>> * Evidence of good uptake of the Pekko releases and a large number of >>> ecosystem libs now support Pekko - over 100 non Apache libraries use >>> Pekko libs under the hood >>> * well over 1000 PRs merged >>> * 25+ code contributors >>> * We've had 3 different release managers to date. >>> * dozens more users who have been involved in discussions, code >>> reviews, raising issues, etc. >>> * We have met all maturity criteria as outlined in [4]. >>> >>> >>> Please vote on the resolution pasted below to graduate Apache Pekko >>> from the Incubator to the Top Level Project. >>> >>> [ ] +1 Graduate Apache Pekko from the Incubator. >>> [ ] +0 No opinion. >>> [ ] -1 Don't graduate Apache Pekko from the Incubator because ... >>> >>> This vote will open for at least 72 hours. >>> >>> I would like to thank everyone who have participated in the Apache >>> Pekko community. I would also like to thank the Apache Incubator >>> community as well as Apache Infrastructure team and general ASF >>> community for your support. >>> >>> >>> [1] https://lists.apache.org/thread/q7jjmp7zpcxko607v5hvj514dyf6o8bx >>> [2] https://lists.apache.org/thread/tsb7b8bkgfkts1nstmj413qocztj0s5o >>> [3] https://incubator.apache.org/projects/pekko.html >>> [4] >>> https://cwiki.apache.org/confluence/display/PEKKO/Apache+Maturity+Model+Assessment+for+Pekko >>> >>> >>> >>> --- >>> >>> Establish the Apache Pekko 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 Pekko: a toolkit and an ecosystem for building >>> highly concurrent, distributed, reactive and resilient applications >>> for Java and Scala. >>> >>> >>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee >>> (PMC), to be known as the "Apache Pekko Project", be and hereby is >>> established pursuant to Bylaws of the Foundation; and be it further >>> >>> >>> RESOLVED, that the Apache Pekko Project be and hereby is responsible >>> for the creation and maintenance of software related to Pekko: a >>> toolkit and an ecosystem for building highly concurrent, distributed, >>> reactive and resilient applications for Java and Scala.; and be it >>> further >>> >>> >>> RESOLVED, that the office of "Vice President, Apache Pekko" 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 Pekko >>> Project, and to have primary responsibility for management of the >>> projects within the scope of responsibility of the Apache Pekko >>> 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 Pekko Project: >>> >>> Claude Warren (claude) >>> Jean-Baptiste Onofré (jbonofre) >>> Justin Mclean (jmclean) >>> PJ Fanning (fanningpj) >>> Roman Shaposhnik (rvs) >>> Ryan Skraba (rskraba) >>> Sheng Wu (wu-sheng) >>> Alexandru Nedelcu (alexelcu) >>> Arnout Engelen (engelen) >>> Dani Schroeter (dsc) >>> Greg Methvin (gregm) >>> Guobin Li (liguobin) >>> He Pin (hepin) >>> Johannes Rudolph (jrudolph) >>> Jonas Chapuis (jchapuis) >>> Matthew de Detrich (mdedetrich) >>> Nicolas
Re: [VOTE] Graduate Apache Pekko (incubating) as a TLP
Hello! I've been following the project since it's inception. They've done an incredible amount of work with the existing code to make it ASF-compatible. The community is entirely self-organising and capable of delivering releases. +1 (binding) All my best! Ryan On Mon, Feb 26, 2024 at 6:43 PM PJ Fanning wrote: > > Thanks Craig. I have created a PR to fix the KEYS link and add 'tm' to > Apache Pekko on the main page. > > https://github.com/apache/incubator-pekko-site/pull/87 > > > On Mon, 26 Feb 2024 at 18:14, Craig Russell wrote: > > > > Hi, > > > > I noticed a few items that may be problematic if not resolved before the > > board votes on the resolution: > > > > 1. The home page https://pekko.apache.org has Apache Pekko in the first > > prominent usage but does not use a TM symbol as in Apache Pekko™. > > 2. The downloads page https://pekko.apache.org/download.html KEYS file for > > verifying checksums should link to the dist.apache.org file not the source > > repository. > > https://dist.apache.org/repos/dist/release/incubator/pekko/KEYS > > Of course, this should link to the non-incubator file once you have a > > release as a TLP. > > > > Other than that, looks good. > > > > Good luck, > > Craig > > > > > On Feb 26, 2024, at 03:24, PJ Fanning wrote: > > > > > > Hi everyone, > > > > > > We have positive feedback on the Pekko Vote thread [1] (result [2]). > > > > > > I'd like to start an official Incubator VOTE thread now. > > > > > > Below are some facts and project highlights from the incubation phase > > > as well as the draft resolution: > > > > > > * All modules have at least a v1.0.0 release > > > * 19 releases (across 12 modules) [3] > > > * Evidence of good uptake of the Pekko releases and a large number of > > > ecosystem libs now support Pekko - over 100 non Apache libraries use > > > Pekko libs under the hood > > > * well over 1000 PRs merged > > > * 25+ code contributors > > > * We've had 3 different release managers to date. > > > * dozens more users who have been involved in discussions, code > > > reviews, raising issues, etc. > > > * We have met all maturity criteria as outlined in [4]. > > > > > > > > > Please vote on the resolution pasted below to graduate Apache Pekko > > > from the Incubator to the Top Level Project. > > > > > > [ ] +1 Graduate Apache Pekko from the Incubator. > > > [ ] +0 No opinion. > > > [ ] -1 Don't graduate Apache Pekko from the Incubator because ... > > > > > > This vote will open for at least 72 hours. > > > > > > I would like to thank everyone who have participated in the Apache > > > Pekko community. I would also like to thank the Apache Incubator > > > community as well as Apache Infrastructure team and general ASF > > > community for your support. > > > > > > > > > [1] https://lists.apache.org/thread/q7jjmp7zpcxko607v5hvj514dyf6o8bx > > > [2] https://lists.apache.org/thread/tsb7b8bkgfkts1nstmj413qocztj0s5o > > > [3] https://incubator.apache.org/projects/pekko.html > > > [4] > > > https://cwiki.apache.org/confluence/display/PEKKO/Apache+Maturity+Model+Assessment+for+Pekko > > > > > > > > > > > > --- > > > > > > Establish the Apache Pekko 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 Pekko: a toolkit and an ecosystem for building > > > highly concurrent, distributed, reactive and resilient applications > > > for Java and Scala. > > > > > > > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > > > (PMC), to be known as the "Apache Pekko Project", be and hereby is > > > established pursuant to Bylaws of the Foundation; and be it further > > > > > > > > > RESOLVED, that the Apache Pekko Project be and hereby is responsible > > > for the creation and maintenance of software related to Pekko: a > > > toolkit and an ecosystem for building highly concurrent, distributed, > > > reactive and resilient applications for Java and Scala.; and be it > > > further > > > > > > > > > RESOLVED, that the office of "Vice President, Apache Pekko" 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 Pekko > > > Project, and to have primary responsibility for management of the > > > projects within the scope of responsibility of the Apache Pekko > > > 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 Pekko Project: > > > > > > Claude Warren (claude) > > > Jean-Baptiste Onofré (jbonofre) > > > Justin Mclean (jmclean) > > > PJ Fanning (fanningpj) > > > Roman Shaposhnik
