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 <fannin...@gmail.com> 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 <seb...@gmail.com> 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 <wander4...@gmail.com> wrote: > > > > > > +1 (binding) > > > > > > Let's rock. > > > > > > Best, > > > tison. > > > > > > Craig Russell <apache....@gmail.com> 于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 <fannin...@apache.org> 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 <apache....@gmail.com> > > > > > 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 <fannin...@apache.org> 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 Vollmar (nvollmar) > > > > >>> Samuele Resca (samueler) > > > > >>> Sean Glover (seanglover) > > > > >>> > > > > >>> NOW, THEREFORE, BE IT FURTHER RESOLVED, that PJ Fanning be appointed > > > > >>> to the office of Vice President, Apache Pekko, 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 Pekko Project be and hereby is tasked with > > > > >>> the migration and rationalization of the Apache Incubator Pekko > > > > >>> podling; and be it further > > > > >>> > > > > >>> RESOLVED, that all responsibilities pertaining to the Apache > > > > >>> Incubator > > > > >>> Pekko podling encumbered upon the Apache Incubator PMC are hereafter > > > > >>> discharged. > > > > >>> > > > > >>> > > > > >>> Thanks, > > > > >>> PJ > > > > >>> > > > > >>> --------------------------------------------------------------------- > > > > >>> 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 > > > > >> > > > > > > > > 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 > > > > > > > --------------------------------------------------------------------- > > 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
