Re: [SUGGESTION] Allow Xuanwo to join Fury as a mentor.

[PJ Fanning]

+1 from me

On Mon, 27 May 2024 at 16:52, tison  wrote:
>
> Cool!
>
> I can add you as a mentor on whimsy later.
>
> Let's also cc dev@fury.a.o for any feedback.
>
> Best,
> tison.
>
>
> Shawn Yang 于2024年5月27日 周一22:46写道：
>
> > Looks great to me,
> >
> > Xuanwo has been continuously active in the incubator and helped the
> > release of many podlings including Fury .
> >
> > His experience in rust and opendal incubation would be a great help to
> > Fury.
> >
> > Looking forward to collaborating with Xuanwo.
> >
> > Best regards,
> > Chaokun Yang
> >
> >
> > On Mon, May 27, 2024 at 9:40 PM Xuanwo  wrote:
> > >
> > > Hi,
> > >
> > > I am willing to join Fury as a mentor, assisting with rust-related
> > projects and release management to help build the community.
> > >
> > > Please consider my suggestion. Thank you!
> > >
> > > Xuanwo
> > >
> > > -
> > > 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

Re: [DISCUSS] OpenServerless Proposal to the incubator

[PJ Fanning]

I've moved the page to appear under the main Proposals page.

The champion needs to be an Apache member or an officer (e.g. a PMC
chair of an existing project).

https://incubator.apache.org/guides/roles_and_responsibilities.html#champion



On Sun, 26 May 2024 at 22:48, Michele Sciabarra  wrote:
>
> Hi PJ,
>
> Thank you a lot for fixing the urls. Can you also move the page under the
> proposals? I am unable to do so, so it is under "New Podling Proposal"
> instead of being under "Proposals".
>
> I was confused by the text that the Champion is also the mentor but I
> missed the requirement that a mentor should be PMC of the Incubator. If you
> are willing to be our mentor I will happily accept your proposal. I just
> edited the proposal adding you and removing me as a mentor.
>
>
> Michele Sciabarra | CEO
>
> m: +44 747 984 8388
> e:  mich...@nuvolaris.io
> l:   https://linkedin.com/in/msciab
> Nuvolaris Inc | 1209 Orange Street , Wilmington DE
> www.nuvolaris.io   [image: linkedin icon]
> <https://www.linkedin.com/company/nuvolaris-io> [image: youtube icon]
> <http://bit.ly/nuvtube> [image: twitter icon]
> <https://twitter.com/NuvolarisIo>
>
>
> On Sun, 26 May 2024 at 21:09, PJ Fanning  wrote:
>
> > Hi Michele,
> >
> > Your proposal looks good on an initial read. I spotted a few small items.
> > * The proposal had some accidental links to gihub.com which is a
> > phishing site that my anti-virus software blocks. I updated the
> > proposal to remove the links that I found.
> > * mentors need to be members of the Incubator PMC and you do not
> > appear to be a member - maybe you could find some other mentors from
> > the existing PMC membership - I can volunteer if you are short
> > * with the mailing lists, you don't need to include the 'incubator'
> > part in the name
> >
> > Regards,
> > PJ
> >
> >
> >
> > On Sun, 26 May 2024 at 20:51, Michele Sciabarra 
> > wrote:
> > >
> > > Hi Apache Incubator members,
> > >
> > > I would like to propose a new project to the ASF incubator -
> > OpenServerless.
> > >
> > > OpenServerless (currently Nuvolaris Community) is a complete Serverless
> > > platform for Kubernetes built on top of Apache OpenWhisk, Redis,
> > PosgreSQL,
> > > FerredDB, Minio, APISIX and Ollama, providing support for back-end and
> > > front-end, with a rich CLI, including development tools and IDE support,
> > > tested on all the leading cloud kubernetes (EKS,AKS,GKE) and Linux
> > > distributions (OpenShift, MicroK8S, K3S).
> > >
> > > Here is the proposal:
> > >
> > https://cwiki.apache.org/confluence/display/INCUBATOR/OpenServerlessProposal
> > >
> > > I would be the Champion of the project. I will mentor and help the
> > project
> > > through the incubator with Bertrand Delacratez [bdelacra...@apache.org]
> > and
> > > Enrico Olivelli [eolive...@apache.org]
> > >
> > > We are open to hearing the feedback from the incubator.
> > >
> > > [1] https://nuvolaris.github.io
> >
> > -
> > 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: [DISCUSS] OpenServerless Proposal to the incubator

[PJ Fanning]

Hi Michele,

Your proposal looks good on an initial read. I spotted a few small items.
* The proposal had some accidental links to gihub.com which is a
phishing site that my anti-virus software blocks. I updated the
proposal to remove the links that I found.
* mentors need to be members of the Incubator PMC and you do not
appear to be a member - maybe you could find some other mentors from
the existing PMC membership - I can volunteer if you are short
* with the mailing lists, you don't need to include the 'incubator'
part in the name

Regards,
PJ



On Sun, 26 May 2024 at 20:51, Michele Sciabarra  wrote:
>
> Hi Apache Incubator members,
>
> I would like to propose a new project to the ASF incubator - OpenServerless.
>
> OpenServerless (currently Nuvolaris Community) is a complete Serverless
> platform for Kubernetes built on top of Apache OpenWhisk, Redis, PosgreSQL,
> FerredDB, Minio, APISIX and Ollama, providing support for back-end and
> front-end, with a rich CLI, including development tools and IDE support,
> tested on all the leading cloud kubernetes (EKS,AKS,GKE) and Linux
> distributions (OpenShift, MicroK8S, K3S).
>
> Here is the proposal:
> https://cwiki.apache.org/confluence/display/INCUBATOR/OpenServerlessProposal
>
> I would be the Champion of the project. I will mentor and help the project
> through the incubator with Bertrand Delacratez [bdelacra...@apache.org] and
> Enrico Olivelli [eolive...@apache.org]
>
> We are open to hearing the feedback from the incubator.
>
> [1] https://nuvolaris.github.io

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] GravitinoProposal to the incubator

[PJ Fanning]

+1 project looks in a good position to join the Apache Incubator

On Fri, 24 May 2024 at 14:55, Jean-Baptiste Onofré  wrote:
>
> Hi Kent
>
> That's a good question, and it's also a fair topic in TLP:
> contribution is not only code, anything helping the project and
> community to grow (documentation, participation on the mailing list,
> events, etc) is as good as code. So, an initial list should balance
> "technical/coding" contributors, non coding contributors (website,
> documentation, promoting project/community), and contributors doing
> both :)
>
> Regards
> JB
>
> On Fri, May 24, 2024 at 10:42 AM Kent Yao  wrote:
> >
> > I have a question about the initial committer list
> >
> > Xiao Xu (GitHub: theoryxu), with only 1 credit[1], has been added to the 
> > list.
> > However, some of the contributors from the TOP10, such as qqqttt123[2]
> > and ch3yne[3], are not included.
> >
> > Could you provide additional details to confirm Xu's contributions to
> > any of the CoPDoC areas? And the reason why those people are excluded?
> >
> > Thanks,
> > Kent Yao
> >
> >
> > [1] https://github.com/datastrato/gravitino/commits?author=theoryxu
> > [2] https://github.com/datastrato/gravitino/commits?author=qqqttt123
> > [3] https://github.com/datastrato/gravitino/commits?author=ch3yne
> >
> > Ayush Saxena  于2024年5月24日周五 16:06写道：
> > >
> > > +1
> > >
> > > -Ayush
> > >
> > > > On 24 May 2024, at 12:20 PM, 张铎  wrote:
> > > >
> > > > +1
> > > >
> > > > The project already has a good community and the mentors and lots of
> > > > the initial committers are already familiar with open source,
> > > > especially the Apache way.
> > > >
> > > > I think joining the incubator will benefit both sides, either the
> > > > project or the ASF.
> > > >
> > > > Thanks.
> > > >
> > > > Xuanwo  于2024年5月24日周五 12:15写道：
> > > >> +1 wish you have fun in the Apache community.
> > > >>> On Fri, May 24, 2024, at 11:59, Nicholas wrote:
> > > >>> +1. Looking forward to unified data catalog service for a
> > > >>> high-performance, geo-distributed and federated metadata lake.
> > > >>> Regards,
> > > >>> Nicholas Jiang
> > > >>> 在 2024-05-24 01:25:31，"larry mccay"  写道：
> > >  Looks interesting to me.
> > >  I would be willing to be an additional mentor or join the initial 
> > >  set of
> > >  team members if there is interest.
> > >  +1
> > >  On Thu, May 23, 2024 at 11:21 AM Charles Zhang 
> > >  
> > >  wrote:
> > > > +1
> > > > It looks like a good project with many application scenarios.
> > > > Best wishes,
> > > > Charles Zhang
> > > > from Apache InLong
> > > > tison  于2024年5月23日周四 23:08写道：
> > > >> +1 looks promising and I believe this initial group and the 
> > > >> mentors :D
> > > >> Best,
> > > >> tison.
> > > >> 俊平堵  于2024年5月23日周四 22:53写道：
> > > >>> +1. Thanks JB for the proposal.
> > > >>> Unified Data Catalog is more and more important in the data and AI
> > > >> domain.
> > > >>> Project gravitino should be the first one in ASF to address this 
> > > >>> area.
> > > >>> The project is very active and has outstanding contributors from
> > > >> different
> > > >>> organizations and companies.
> > > >>> Glad to see it joins the ASF family and grows the community by
> > > > following
> > > >>> the Apache way. :)
> > > >>> Thanks,
> > > >>> JP
> > > >>> Jean-Baptiste Onofré  于2024年5月23日周四 13:08写道：
> > >  Hi folks,
> > >  We would like to propose a new project to the ASF incubator:
> > > > Gravitino.
> > >  Gravitino is a high-performance, geo-distributed, and federated
> > >  metadata lake designed to manage metadata seamlessly across 
> > >  diverse
> > >  data sources, vendors, and regions. Its primary goal is to 
> > >  provide
> > >  users with unified metadata access for both data and AI assets.
> > >  Here is the proposal:
> > > >> https://cwiki.apache.org/confluence/display/INCUBATOR/GravitinoProposal
> > >  Comments and feedback are welcome.
> > >  Thanks !
> > >  Regards
> > >  JB
> > >  -
> > >  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
> > > >
> > > > -
> > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > > 

Re: [VOTE] Release Apache Fury(incubating) v0.5.1-rc2

[PJ Fanning]

+1 (binding)

[x] Download links are valid.
[x] Checksums and signatures.
[x] LICENSE/NOTICE/DISCLAIMER files exist
[x] No unexpected binary files - a lot of image files for docs
[x] All source files have ASF headers
[x] Can compile from source

On 2024/05/24 07:21:40 Shawn Yang wrote:
> Carry my no-binding +1.
> 
> Best Regards,
> Chaokun Yang
> 
> On Thu, May 23, 2024 at 10:21 PM Shawn Yang  wrote:
> >
> > Hello everyone,
> >
> > This is a call for the vote to release Apache Fury(Incubating) v0.5.1-rc2.
> >
> > The Apache Fury community has voted and approved the release of Apache
> > Fury(incubating) v0.5.1-rc2. We now kindly request the IPMC members
> > review and vote for this release.
> >
> > Apache Fury(incubating) - A blazingly fast multi-language serialization
> > framework powered by JIT and zero-copy.
> >
> > Fury community vote thread:
> > https://lists.apache.org/thread/kof226qkft02jcj62kt6wnppdnm2jgzx
> >
> > Vote result thread:
> > https://lists.apache.org/thread/z7cvvw1omdpg76gpbcv2m5crk0mdwc8k
> >
> > The release candidate:
> > https://dist.apache.org/repos/dist/dev/incubator/fury/0.5.1-rc2/
> >
> > This release has been signed with a PGP available here:
> > https://downloads.apache.org/incubator/fury/KEYS
> >
> > Git tag for the release:
> > https://github.com/apache/incubator-fury/releases/tag/v0.5.1-rc2
> >
> > Git commit for the release:
> > https://github.com/apache/incubator-fury/commit/0455ff732b9217785193f8e45f3a013eb5539e46
> >
> > Maven staging repo:
> > https://repository.apache.org/content/repositories/orgapachefury-1010
> >
> > How to Build and Test, please refer to:
> > https://github.com/apache/incubator-fury/blob/main/docs/guide/DEVELOPMENT.md
> >
> > The vote will be open for at least 72 hours or until the necessary number
> > of votes is reached.
> >
> > Please vote accordingly:
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> > To learn more about apache fury, please see https://fury.apache.org/
> >
> > Checklist for reference:
> >
> > [ ] Download links are valid.
> > [ ] Checksums and signatures.
> > [ ] LICENSE/NOTICE files exist
> > [ ] No unexpected binary files
> > [ ] All source files have ASF headers
> > [ ] Can compile from source
> >
> >
> > Thanks,
> >
> > Chaokun Yang
> 
> -
> 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: [QUESTION] KIE - NPM package names

[PJ Fanning]

Podlings are allowed some leeway. Ideally, you should aim to eventually
rename your binary artifacts to include Apache KIE branding. I think it
should be ok to make an initial release with the existing naming,
especially if you comply with the other requirements in the NPM
distribution guidelines [1]. It might be worth waiting to see if anyone
else has a different take on this.

[1] https://incubator.apache.org/guides/distribution.html#npm


On Wed, 15 May 2024 at 16:56, Tiago Bento  wrote:

> Hi general@incubator,
>
> The distribution guidelines [1] say packages published to NPM should
> be named `apache-`, however, at KIE, we have a somewhat big
> set of packages that are published under these scopes:
> - @kie-tools/*
> - @kie-tools-core/*
> - @kie-tools-scripts/*
>
> There are also some VS Code Extensions (which can't have a scope):
> - yard-vscode-extension
> - swf-vscode-extension
> - pmml-vscode-extension
> - dmn-vscode-extension
> - bpmn-vscode-extension
> - vscode-extension-kogito-bundle
> - vscode-extension-kie-ba-bundle
> - vscode-extension-dashbuilder-editor
>
> And a one-off package that is later then transformed into a Maven
> WebJar [2] (which can't have a scope either)
> - sonataflow-deployment-webapp
>
> Those do not conform with the guidelines, but have been published
> under these scopes/names for quite some time now, before KIE became a
> podling.
>
> My question is: Are we required to rename everything prior to
> releasing? Or are we able to pass a vote with the current package
> names? Asking because that's a substantial amount of work prior to
> releasing, and also because renaming everything would mean consumers
> would have to manually "migrate" to the new package names.
>
> Thanks a lot in advance!
>
> Regards,
>
> Tiago Bento
>
>
> [1] https://incubator.apache.org/guides/distribution.html#npm
> [2] https://www.webjars.org/
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: KIE - Question about "staging" binaries/artifacts

[PJ Fanning]

I may be misinterpreting 'live website' but it is quite common for Apache
projects to have a 'staged' version of their website (i.e. a pre-release
version of the web site).
https://kie.apache.org/ could also have a https://kie.staged.apache.org/

https://pekko.staged.apache.org/ is a staged version of
https://pekko.apache.org/ (for instance)

See the .asf.yaml docs:
https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-Stagingawebsitepreviewdomain

For quay.io, you could raise a JIRA for INFRA team to discuss supporting an
account for deployments. Or maybe, the KIE PPMC could set up an account and
share the credentials among the KIE release managers.





On Mon, 13 May 2024 at 22:30, Tiago Bento  wrote:

> Thank you for the prompt responses.
>
> We're aware that for Maven artifacts we could "promote" them after
> publishing them to a staging repo.
>
> But for container images, for example, I'm not sure I understand how such
> process would look like. Prior to being in Apache, we used to push images
> to Quay.io under a "[version]-prerelease" tag for "staging". Then we would
> have a completely new build when we would be ready for a actual release.
>
> I guess for other kinds of artifacts, like the NPM packages, live
> websites, and Chrome and VS Code Extensions, I also still don't understand
> very well how this could be achieved... Any advice? It's hard to tell what
> "promoting" those would look like, as for example, one of our live websites
> is hosted in GitHub Pages.
>
> Thanks again!
>
> Regards,
>
> Tiago Bento
>
>
>
> On 2024/05/13 20:35:35 PJ Fanning wrote:
> > For Java jars, the ASF has repository.apache.org - a Nexus instance that
> > can be used to stage and later release jars.
> > The login credentials are the same credentials you use to access other
> ASF
> > resources.
> >
> >
> > On Mon, 13 May 2024 at 21:28, Enrico Olivelli 
> wrote:
> >
> > > Tiago,
> > >
> > >
> > > Il Lun 13 Mag 2024, 22:11 Tiago Bento  ha
> scritto:
> > >
> > > > Hello general@incubator,
> > > >
> > > > My name is Tiago Bento (@tiagobento on GitHub), and I’m one of the
> > > > committers of the KIE project of the incubator.
> > > >
> > > > We’re gearing towards our first release under Apache, and we’re very
> > > > excited to be approaching this important milestone.
> > > >
> > > > Some resources [1] [2] that we found already guided us in the right
> > > > direction, but still, some questions remain about the release process
> > > > itself.
> > > >
> > > > We understand that in Apache, releases are done from the source code
> > > > perspective, not the binaries/artifacts’. However, we still don’t
> > > > understand very clearly how Apache verifies signatures and checksums
> > > > of the binaries that are eventually published.
> > > >
> > >
> > > It is better that in case you provide binaries to your users those
> binaries
> > > are released together with the sources during the same VOTE.
> > >
> > > Having reproducible builds would help a lot, but that's not always
> easy to
> > > do.
> > >
> > > In your VOTE you should stage all the sources and binaries, signed
> with the
> > > same signature (by the release manager) and the same artifacts will be
> > > promoted in case of a successful VOTE.
> > >
> > > The PMC can at least verify the signatures and any digests that are
> staged
> > > as part of the VOTE.
> > >
> > > Please note that if you don't have a reproducible build the PMC will
> never
> > > be able to verify that the binaries match the sources.
> > >
> > >
> > > > The KIE project has three main types of consumable artifacts: Maven
> > > > modules, Container images, and NPM packages; and we also maintain
> some
> > > > live web pages like https://sandbox.kie.org, and extensions for
> Chrome
> > > > [3] and VS Code [4].
> > > >
> > > > For the release to be voted, we understand we have to provide a .zip
> > > > file containing the source code along with instructions on how to
> > > > build it. Once/if approved, our understanding is that the exact same
> > > > approved source code could be used to build and publish
> > > > binaries/artifacts of any sort to public registries/repositories.
> > > >
> > > > I’m laying out all the info

Re: KIE - Question about "staging" binaries/artifacts

[PJ Fanning]

For Java jars, the ASF has repository.apache.org - a Nexus instance that
can be used to stage and later release jars.
The login credentials are the same credentials you use to access other ASF
resources.


On Mon, 13 May 2024 at 21:28, Enrico Olivelli  wrote:

> Tiago,
>
>
> Il Lun 13 Mag 2024, 22:11 Tiago Bento  ha scritto:
>
> > Hello general@incubator,
> >
> > My name is Tiago Bento (@tiagobento on GitHub), and I’m one of the
> > committers of the KIE project of the incubator.
> >
> > We’re gearing towards our first release under Apache, and we’re very
> > excited to be approaching this important milestone.
> >
> > Some resources [1] [2] that we found already guided us in the right
> > direction, but still, some questions remain about the release process
> > itself.
> >
> > We understand that in Apache, releases are done from the source code
> > perspective, not the binaries/artifacts’. However, we still don’t
> > understand very clearly how Apache verifies signatures and checksums
> > of the binaries that are eventually published.
> >
>
> It is better that in case you provide binaries to your users those binaries
> are released together with the sources during the same VOTE.
>
> Having reproducible builds would help a lot, but that's not always easy to
> do.
>
> In your VOTE you should stage all the sources and binaries, signed with the
> same signature (by the release manager) and the same artifacts will be
> promoted in case of a successful VOTE.
>
> The PMC can at least verify the signatures and any digests that are staged
> as part of the VOTE.
>
> Please note that if you don't have a reproducible build the PMC will never
> be able to verify that the binaries match the sources.
>
>
> > The KIE project has three main types of consumable artifacts: Maven
> > modules, Container images, and NPM packages; and we also maintain some
> > live web pages like https://sandbox.kie.org, and extensions for Chrome
> > [3] and VS Code [4].
> >
> > For the release to be voted, we understand we have to provide a .zip
> > file containing the source code along with instructions on how to
> > build it. Once/if approved, our understanding is that the exact same
> > approved source code could be used to build and publish
> > binaries/artifacts of any sort to public registries/repositories.
> >
> > I’m laying out all the information I could gather so someone can
> > correct me if somehow I got the wrong idea of any part of the process.
> >
> > I guess the main question I have at the moment is: Are we able to pass
> > the release vote only with the sources (without any published
> > artifacts) so that once/if approved, we could publish definitive
> > binaries/artifacts to public registries/repositories?
> >
>
> You can do it. But you should state it very clearly in the downloads pages
> and in any repository.
>
> Also it is better to leverage as much as possible the ASF infra to build
> automatically such derived artifacts.
>
> Foe instance in Apache BookKeeper we build the docker images using a docker
> bot that is handled by the ASF infra
>
>
> > This question comes from the fact that we’re not sure how such a
> > “staging” environment could be created for artifacts/binaries that are
> > not Maven modules. We started a thread [5] on Slack several hours ago,
> > but no luck getting
> > I apologize if I’m lacking obvious information, and appreciate any
> > resource or reply that would put us closer to a successful release.
> >
>
> This is the right place for asking questions, not Slack.
>
>
> > Regards,
> >
>
> I hope that help
>
> Thanks for sharing your problem, this thread will be a good reference for
> other projects
>
> Enrico
>
> >
> > Tiago Bento
> >
> >
> >
> > [1] https://lists.apache.org/thread/ropp09n8m75rl6hlvnmpwcv85oyq5op9
> > [2] https://www.apache.org/info/verification.html
> > [3]
> >
> https://chromewebstore.google.com/detail/bpmn-dmn-test-scenario-ed/mgkfehibfkdpjkfjbikpchpcfimepckf
> > [4]
> >
> https://marketplace.visualstudio.com/items?itemName=kie-group.vscode-extension-kie-ba-bundle
> > [5] https://the-asf.slack.com/archives/CBX4TSBQ8/p1715605377484379
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [VOTE] Apache StormCrawler (Incubating) 3.0 Release Candidate 2

[PJ Fanning]

+1 binding

* license/notice/disclaimer are ok
* incubating in name
* most files have source headers - for future releases, it would be good to
review if the source headers can be added to some of the config files and
scripts
* no compiled binaries - there are a few gzipped binaries used in tests
* compiles from source



On Mon, 13 May 2024 at 11:47, PJ Fanning  wrote:

> The Incubator PMC prefer that the Git commit ids are included. The git
> tags are useful too but git tags can be moved to different commits.
>
> This RC appears to be for git commit
> e15d84d13879d217bd095d25d5cf1f5ca913dade
>
>
> On 2024/05/13 07:41:42 Richard Zowalla wrote:
> > Hi folks,
> >
> > I have posted release candidate for the Apache StormCrawler
> > (Incubating) 3.0 release and it is ready for testing.
> >
> > This is our first release after joining the ASF incubator as a
> > poddling. It is a breaking change with renamings in the group ids and
> > the removal of the elasticsearch module.
> >
> > Thank you to everyone who contributed to this release, including all of
> > our users and the people who submitted bug reports,
> > contributed code or documentation enhancements.
> >
> > The release was made using the Apache StormCrawler (Incubating) release
> > process, documented here:
> > https://github.com/apache/incubator-stormcrawler/RELEASING.md
> >
> > Here is the VOTE and VOTE Result on our dev@stormcrawler.a.o list
> >
> > - https://lists.apache.org/thread/l66fyzf9ly7twmfz1vjw1x3sfl0jkzd3
> > - https://lists.apache.org/thread/19txfl2ykmjzot8nb1mx6krh8ogzjhkp
> >
> >
> > Source:
> >
> >
> https://dist.apache.org/repos/dist/dev/incubator/stormcrawler/stormcrawler-3.0/
> >
> >
> > Tag:
> >
> >
> https://github.com/apache/incubator-stormcrawler/releases/tag/stormcrawler-3.0
> >
> > Maven Repo:
> >
> >
> https://repository.apache.org/content/repositories/orgapachestormcrawler-1001/
> >
> > 
> > 
> > stormcrawler-3.0-rc2
> > Testing StormCrawler 3.0 release candidate
> > 
> >
> >
> https://repository.apache.org/content/repositories/orgapachestormcrawler-1001/
> > 
> > 
> > 
> >
> >
> > Preview of website:
> >
> > https://stormcrawler.staged.apache.org/download/index.html
> >
> > Release notes:
> >
> >
> https://github.com/apache/incubator-stormcrawler/releases/tag/stormcrawler-3.0
> >
> > Reminder: The up-2-date KEYS file for signature verification can be
> > found here:
> > https://dist.apache.org/repos/dist/release/incubator/stormcrawler/KEYS
> >
> > Please vote on releasing these packages as Apache StormCrawler
> > (Incubating) 3.0
> >
> > The vote is open for at least the next 72 hours.
> >
> > Only votes from IPMC members are binding, but everyone is
> > welcome to check the release candidate and vote.
> >
> > The vote passes if at least three binding +1 votes are cast.
> >
> > Please VOTE
> >
> > [+1] go ship it
> > [+0] meh, don't care
> > [-1] stop, there is a ${showstopper}
> >
> > Please include your checklist in your vote:
> >
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> >
> >
> > Thanks!
> > Richard
> >
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Apache StormCrawler (Incubating) 3.0 Release Candidate 2

[PJ Fanning]

The Incubator PMC prefer that the Git commit ids are included. The git tags are 
useful too but git tags can be moved to different commits.

This RC appears to be for git commit e15d84d13879d217bd095d25d5cf1f5ca913dade


On 2024/05/13 07:41:42 Richard Zowalla wrote:
> Hi folks,
> 
> I have posted release candidate for the Apache StormCrawler
> (Incubating) 3.0 release and it is ready for testing.
> 
> This is our first release after joining the ASF incubator as a
> poddling. It is a breaking change with renamings in the group ids and
> the removal of the elasticsearch module.
> 
> Thank you to everyone who contributed to this release, including all of
> our users and the people who submitted bug reports,
> contributed code or documentation enhancements.
> 
> The release was made using the Apache StormCrawler (Incubating) release
> process, documented here:
> https://github.com/apache/incubator-stormcrawler/RELEASING.md
> 
> Here is the VOTE and VOTE Result on our dev@stormcrawler.a.o list
> 
> - https://lists.apache.org/thread/l66fyzf9ly7twmfz1vjw1x3sfl0jkzd3
> - https://lists.apache.org/thread/19txfl2ykmjzot8nb1mx6krh8ogzjhkp
> 
> 
> Source:
> 
> https://dist.apache.org/repos/dist/dev/incubator/stormcrawler/stormcrawler-3.0/
> 
> 
> Tag:
> 
> https://github.com/apache/incubator-stormcrawler/releases/tag/stormcrawler-3.0
> 
> Maven Repo:
> 
> https://repository.apache.org/content/repositories/orgapachestormcrawler-1001/
> 
> 
> 
> stormcrawler-3.0-rc2
> Testing StormCrawler 3.0 release candidate
> 
> 
> https://repository.apache.org/content/repositories/orgapachestormcrawler-1001/
> 
> 
> 
> 
> 
> Preview of website:
> 
> https://stormcrawler.staged.apache.org/download/index.html
> 
> Release notes:
> 
> https://github.com/apache/incubator-stormcrawler/releases/tag/stormcrawler-3.0
> 
> Reminder: The up-2-date KEYS file for signature verification can be
> found here:
> https://dist.apache.org/repos/dist/release/incubator/stormcrawler/KEYS
> 
> Please vote on releasing these packages as Apache StormCrawler
> (Incubating) 3.0
> 
> The vote is open for at least the next 72 hours.
> 
> Only votes from IPMC members are binding, but everyone is
> welcome to check the release candidate and vote.
> 
> The vote passes if at least three binding +1 votes are cast.
> 
> Please VOTE
> 
> [+1] go ship it
> [+0] meh, don't care
> [-1] stop, there is a ${showstopper}
> 
> Please include your checklist in your vote:
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> 
> 
> Thanks!
> Richard
> 
> 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache ResilientDB, Incubating, v1.10.0-RC1

[PJ Fanning]

Hi Apratim,

I think you should change the text in the home page where it says 'Apache
ResilientDB' to say 'Apache ResilientDB (Incubating)'.

The first instance should be changed at least.

Apache ResilientDB (Incubating) offers a high-throughput yielding
distributed ledger built upon scale-centric design principles to
democratize and decentralize computation.

Having the Apache Incubator logo above the button for 'Visit the API
Playground' also seems like a mistake that was made. Shouldn't that have a
different logo - something ResilientDB specific?



On Thu, 9 May 2024 at 21:11, Apratim Shukla 
wrote:

> Greetings,
>
> The website has been updated with the required Incubator disclaimer as
> requested. The changes are now live at
> https://resilientdb.incubator.apache.org/
>
> Best regards,
> Apratim
>
> On Thu, May 9, 2024 at 1:23 AM sebb  wrote:
>
> > The website does not appear to have the required Incubator disclaimer.
> >
> > Also I could not find a download page for the source code (which
> > should also have the disclaimer).
> >
> > On Thu, 9 May 2024 at 08:33, Mohammad Sadoghi 
> > wrote:
> > >
> > > Dear all,
> > >
> > > Are there any other concerns that need to be addressed before advancing
> > to
> > > the voting phase? Thank you kindly.
> > >
> > > ---
> > > Best Regards,
> > > Mohammad Sadoghi, PhD
> > > Associate Professor
> > > Exploratory Systems Lab (ExpoLab)
> > > Department of Computer Science
> > > University of California, Davis
> > >
> > > ExpoLab: https://expolab.org/
> > > ResilientDB: https://resilientdb.com/
> > > Phone: 914-319-7937
> > >
> > >
> > > On Sun, May 5, 2024 at 6:00 PM Junchao Chen
>  > >
> > > wrote:
> > >
> > > > Hi Fanning,
> > > >
> > > > Thanks for the help.
> > > >
> > > > I updated DISCLAIMER-WIP and placed the licenses there.
> > > >
> >
> https://github.com/apache/incubator-resilientdb/blob/master/DISCLAIMER-WIP
> > > >
> > > >
> > > > On Sun, May 5, 2024 at 2:46 PM PJ Fanning 
> > wrote:
> > > >
> > > > > That is not a valid DISCLAIMER-WIP.
> > > > >
> > > > > Please read https://incubator.apache.org/policy/incubation.html
> > > > >
> > > > > It has the correct text for a DISCLAIMER-WIP and you need to spell
> > out
> > > > what
> > > > > your issues are. For instance, it appears that you still have work
> > to do
> > > > to
> > > > > get the license corrected. You could list that in the
> DISCLAIMER-WIP.
> > > > >
> > > > > Apache Liminal has a DISCLAIMER-WIP.
> > > > >
> > > > >
> > https://github.com/apache/incubator-liminal/blob/master/DISCLAIMER-WIP
> > > > >
> > > > > On Sun, 5 May 2024 at 22:35, Junchao Chen
> > 
> > > > > wrote:
> > > > >
> > > > > > hi John,
> > > > > >
> > > > > > Thanks for the suggestions and sorry for the confusion.
> > > > > > We don't support MAC in the current state, the install file
> > > > > INSTALL_MAC.sh
> > > > > > <http://resilientdb-v1.10.0-incubatinginstall_mac.sh/> is
> outdated
> > > > and I
> > > > > > have removed it from our source code.
> > > > > >
> > > > > > I have renamed DISCLAIMER to DISCLAIMER-WIP
> > > > > > <
> > > > > >
> > > > >
> > > >
> >
> https://github.com/apache/incubator-resilientdb/blob/master/DISCLAIMER-WIP
> > > > > > >
> > > > > > and
> > > > > > also fixed the typo.
> > > > > > Also renamed the release source prefix to
> > > > > "apache-resilientdb-incubating":
> > > > > >
> > > > > >
> > > > >
> > > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/resilientdb/resilientdb/v1.10.0-rc1
> > > > > >
> > > > > >
> > > > > > For the LICENSE,
> > > > > > RocksDB and zstd have been removed from our project.
> > > > > > So we don't rely on any GPL code.
> > > > > > I also added the version for each dependency.
> > > > > >
> > > > > >

Re: [VOTE] Drop the incubator- prefix for podling's GitHub repo name

[PJ Fanning]

+0 binding

I'm not enthusiastic about the change but no against it either. For me, I
think the bigger issue is that some new podlings are not doing enough
verification of their repos and docs and proactively getting their mentors
to review the situation before bringing the release to the IPMC.


On Wed, 8 May 2024 at 15:15, Daniel Gruno  wrote:

> On 5/8/24 03:20, Sheng Wu wrote:
> > sebb  于2024年5月8日周三 16:12写道：
> >>
> >> Remember that the purpose of the incubator prefix is to clearly signal
> >> that the code is under Incubation.
> >>
> >> It is essential that this change does not result in losing this
> indication.
> >>
> >> AFAICT, for most podlings, dropping the incubator prefix will require
> >> additional work to ensure that the Incubation status is clear to
> >> users,
> >> and will require additional work by the IPMC to ensure that podlings
> >> adequately display the Incubation status for each repository.
> >
> > Can't agree more on this.
> > In this vote proposal, we implicitly add many more checks for IPMC,
> > and lead more potential arguments about whether the incubating status
> > indicator is clear enough.
> > We are making IPMC pay the price in the future by removing a simple
> > GitHub supported operation.
> >
> > On second thought, I am changing my vote to -1 binding.
>
> This seems to point at more systemic failings of the IPMC if we are
> relying on the incubator- repository prefix for denoting podlings. I'll
> note that, as far as I can tell, the original reason for the incubator
> prefix was that of a technical limitation with the incubator, and
> shouldn't (imho) be used as a crutch for failings elsewhere in the
> branding of podlings.
>
> I am +1 (binding) on dropping the prefix myself. Incubation notices
> should be handled during releases, and on the official podling website.
>
> >
> >>
> >>
> >> On Wed, 8 May 2024 at 08:30, alin.jerpe...@sony.com
> >>  wrote:
> >>>
> >>> +1 (non binding)
> >>>
> >>> from my experience will make the documentation and releases easy to
> migrate after graduation
> >>>
> >>> Best regards
> >>> Alin
> >>> 
> >>> Från: hulk 
> >>> Skickat: den 8 maj 2024 09:06
> >>> Till: general@incubator.apache.org 
> >>> Ämne: Re: [VOTE] Drop the incubator- prefix for podling's GitHub repo
> name
> >>>
> >>> -0 (binding) On Wed, 8 May 2024 at 13: 58, Richard Zowalla  zowalla. com> wrote: > -0 (binding) > > (I like the prefix) > > Am 8. Mai
> 2024 07: 41: 16 MESZ schrieb Sheng Wu : >
> >-0
> >>> ZjQcmQRYFpfptBannerStart
> >>> Caution : This email originated from outside of Sony.
> >>> Do not click links or open any attachments unless you recognize the
> sender and know the content is safe. Please report phishing if unsure.
> >>>
> >>> ZjQcmQRYFpfptBannerEnd
> >>>
> >>> -0 (binding)
> >>>
> >>> On Wed, 8 May 2024 at 13:58, Richard Zowalla 
> wrote:
> >>>
>  -0 (binding)
> 
>  (I like the prefix)
> 
>  Am 8. Mai 2024 07:41:16 MESZ schrieb Sheng Wu <
> wu.sheng.841...@gmail.com>:
> > -0 binding
> >
> > Sheng Wu 吴晟
> > Twitter, wusheng1108
> >
> > Dave Fisher  于2024年5月8日周三 12:16写道：
> >>
> >> +0 (binding) wave
> >>
> >>> On May 7, 2024, at 5:34 PM, Francis Chuang <
> francischu...@apache.org>
>  wrote:
> >>>
> >>> +1 (binding)
> >>>
> >>> I think this is a pragmatic and well-thought out approach.
> >>>
> >>> Francis
> >>>
> >>> On 8/05/2024 10:31 am, tison wrote:
>  Hi,
>  Following the discussion thread [1], I'd start a vote on the
>  following
>  proposals:
>  1. Establish a consensus to allow and finally converge podling's
>  GitHub repo to
>  have a name without the incubator- prefix.
>  2. Allow existing ongoing podlings to ask the INFRA to drop their
>  incubator- prefix by now, not MUST during the graduation.
>  3. Update the docs on incubator.apache.org everywhere if the
>  description
>  can conflict with this consensus.
>  4. Update the docs on incubator.apache.org to guide how to
> describe
>  podling's incubating status on the GitHub repo (namely, including
>  "incubating" in the repo description and README, point to the
>  DISCLAIMER
>  content).
>  [1]
> https://lists.apache.org/thread/kxvdkrf8g8yr6hww1n08r21xdy67y4ok
>  +1 allow podling's GitHub repo to have a name without the
> incubator-
>  prefix, and other items above
>  +0 do not care strongly
>  -1 disagree the proposals above, because ...
>  Please vote with your ASF ID followed by (binding) if you are a
>  member of
>  the Incubator PMC or (not binding) if not.
>  Vote will be open for at least 72 hours.
>  Best,
>  tison.
> >>>
> >>>
> -
> >>> To unsubscribe, e-mail: 

Re: [VOTE] Release Apache ResilientDB, Incubating, v1.10.0-RC1

[PJ Fanning]

That is not a valid DISCLAIMER-WIP.

Please read https://incubator.apache.org/policy/incubation.html

It has the correct text for a DISCLAIMER-WIP and you need to spell out what
your issues are. For instance, it appears that you still have work to do to
get the license corrected. You could list that in the DISCLAIMER-WIP.

Apache Liminal has a DISCLAIMER-WIP.

https://github.com/apache/incubator-liminal/blob/master/DISCLAIMER-WIP

On Sun, 5 May 2024 at 22:35, Junchao Chen 
wrote:

> hi John,
>
> Thanks for the suggestions and sorry for the confusion.
> We don't support MAC in the current state, the install file INSTALL_MAC.sh
>  is outdated and I
> have removed it from our source code.
>
> I have renamed DISCLAIMER to DISCLAIMER-WIP
> <
> https://github.com/apache/incubator-resilientdb/blob/master/DISCLAIMER-WIP
> >
> and
> also fixed the typo.
> Also renamed the release source prefix to "apache-resilientdb-incubating":
>
> https://dist.apache.org/repos/dist/dev/incubator/resilientdb/resilientdb/v1.10.0-rc1
>
>
> For the LICENSE,
> RocksDB and zstd have been removed from our project.
> So we don't rely on any GPL code.
> I also added the version for each dependency.
>
>
>
> Any other suggestions?
>
> Thanks,
> Junchao
>
>
>
> On Sun, May 5, 2024 at 4:44 AM John D. Ament 
> wrote:
>
> > On Sun, May 5, 2024 at 12:12 AM John D. Ament 
> > wrote:
> >
> > >
> > >
> > > On Sat, May 4, 2024 at 8:50 PM Junchao Chen
>  > >
> > > wrote:
> > >
> > >> hi Justin,
> > >>
> > >> I have removed all the related code from the source files, and there
> are
> > >> no
> > >> GPL dependencies there.
> > >> Those dependencies are an optional setting in our project, it is not
> > >> necessary.
> > >>
> > >
> > > Just to put it out there - I think the license listing for RocksDB is
> > > wrong.  It's a dual licensed piece of software (GPLv2 + Apache License
> > > V2).  Similar for zstd, it's a dual license BSD-3 and GPLv2.  So I
> > suspect
> > > the real issue is that you mislabeled it as GPLv2 but you actually
> wanted
> > > to label them under the permissive license we can use.
> > >
> > > And keep in mind, your source license file should represent the
> contents
> > > of your source release.  If you bring in dependencies when building,
> you
> > > should reference those separately, likely under a binary release.
> > >
> > > Just wondering, but who are your mentors?  What was their feedback on
> the
> > > release? They should be able to help you sort this out.
> > >
> >
> > Sorry, I think I understand what's happening now.  You had a mentor vote
> -1
> > at [1] and were looking for other IPMC members to review it since there
> was
> > no additional feedback on the release.  It's a little confusing that you
> > forwarded your dev@ vote thread to general@ so there was likely some
> > context missing on what the ask is.  Apologies for any confusion from me.
> >
> > Looking at your release, I think you just appended
> > "resilientdb-v1.10.0-incubating" to all of your folders and root files.
> > This isn't required, we just ask that the source release be named with
> > "-incubating" somewhere in it.  It would be better if the source release
> > said "apache-resilientdb-incubating" or similar though.  The result of
> > appending the name though is your DISCLAIMER goes missing.  The one
> > distributed talks about Apache Answer, are you in fact using Answer? If
> not
> > maybe there was a copy/paste issue.  You may want to switch to
> > DISCLAIMER-WIP since this is your first release.
> >
> > I attempted to run resilientdb-v1.10.0-incubatingINSTALL_MAC.sh on my
> > machine, it failed.
> >
> > [1]: https://lists.apache.org/thread/d9krfb42262xbbdb75jnz2tsbs367mst
> >
> >
> > >
> > >
> > >>
> > >> Thanks,
> > >> junchao
> > >>
> > >> On Sat, May 4, 2024 at 5:36 PM Justin Mclean <
> jus...@classsoftware.com>
> > >> wrote:
> > >>
> > >> > HI,
> > >> >
> > >> > > Thanks for letting me know.
> > >> > > I have removed those dependencies.
> > >> >
> > >> > What goes in the license file is any 3rd party licenses that are
> > >> included
> > >> > in the source release, not those that are dependencies. But unless
> it
> > is
> > >> > optional, you also can’t have any GPL dependencies.
> > >> >
> > >> > Kind Regards,
> > >> > Justin
> > >> >
> -
> > >> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > >> > For additional commands, e-mail: general-h...@incubator.apache.org
> > >> >
> > >> >
> > >>
> > >
> >
>

Re: [VOTE] Release Apache ResilientDB, Incubating, v1.10.0-RC1

[PJ Fanning]

The list of 'public domain' software in the resilientdb LICENSE [1] seems
incorrect.

* protobuf is not public domain - see its license [2]
* snappy is not public domain - see its license [3]
* zlib has a customised license that we should reproduce [4]
* this is just some of the issues, I haven't looked at every link


[1] https://github.com/apache/incubator-resilientdb/blob/master/LICENSE
[2] https://github.com/protocolbuffers/protobuf/blob/main/LICENSE
[3] https://github.com/google/snappy?tab=License-1-ov-file#readme
[4] https://github.com/madler/zlib


On Sun, 5 May 2024 at 00:41, Justin Mclean  wrote:

> HI,
>
> I assume you mean [1] I’ve not looked at it in detail, but I note you
> include GPL licensed code. GPL-licensed code is Category X and can’t be
> used in an ASF project.
>
> Kind Regards,
> Justin
>
>
> 1. https://github.com/apache/incubator-resilientdb/blob/master/LICENSE

Re: [ANNOUNCE] Apache Fury(incubating) 0.5.0 released

[PJ Fanning]

Looks like this is the right link.

https://fury.apache.org/docs/download

Shawn - could you change the web site to redirect
https://fury.apache.org/download to https://fury.apache.org/docs/download ?

We need what is in the announcement email to work.



On Fri, 3 May 2024 at 18:31, Xuanwo  wrote:

> Congrats to your release. But I found that
> https://fury.apache.org/download is not a valid page. Maybe this link is
> wrong?
>
> On Sat, May 4, 2024, at 01:01, Shawn Yang wrote:
> > Hi all,
> >
> > The Apache Fury(incubating) community is pleased to announce
> > that Apache Fury(incubating) 0.5.0 has been released!
> >
> > Apache Fury(incubating) - A blazingly fast multi-language serialization
> > framework powered by JIT and zero-copy.
> >
> > The release notes are available here:
> > https://github.com/apache/incubator-fury/releases/tag/v0.5.0
> >
> > For the complete list of changes:
> > https://github.com/apache/incubator-fury/compare/v0.4.1...v0.5.0-rc4
> >
> > Apache Fury website: https://fury.apache.org/
> >
> > Download Links: https://fury.apache.org/download
> >
> > Fury Resources:
> > - Fury github repo: https://github.com/apache/incubator-fury
> > - Issue: https://github.com/apache/incubator-fury/issues
> > - Mailing list: d...@fury.apache.org
> >
> > We are looking to grow our community and welcome new contributors. If you
> > are interested in contributing to Fury, please contact us on the mailing
> > list or on GitHub. We will be happy to help you get started.
> >
> > --
> > Best Regards,
> > Chaokun Yang
>
> --
> Xuanwo
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@fury.apache.org
> For additional commands, e-mail: dev-h...@fury.apache.org
>
>

Re: [VOTE] Release Apache Fury(incubating) v0.5.0-rc4

[PJ Fanning]

Also carry my +1 binding from PPMC vote

On Tue 30 Apr 2024, 16:36 tison,  wrote:

> Carry my +1 binding vote.
>
> Best,
> tison.
>
> Shawn Yang  于2024年4月30日周二 22:17写道：
>
> > Hello everyone,
> >
> > This is a call for the vote to release Apache Fury(Incubating)
> v0.5.0-rc4.
> >
> > The Apache Fury community has voted and approved the release of Apache
> > Fury(incubating) v0.5.0-rc4. We now kindly request the IPMC members
> > review and vote for this release.
> >
> > Apache Fury(incubating) - A blazingly fast multi-language serialization
> > framework powered by JIT and zero-copy.
> >
> > Fury community vote thread:
> > https://lists.apache.org/thread/35slclopfngmz5ff47tt32m1fwjz1316
> >
> > Vote result thread:
> > https://lists.apache.org/thread/lnogbwfxw4hlkckl7nxpwwpy94zz6kv8
> >
> > The release candidate:
> > https://dist.apache.org/repos/dist/dev/incubator/fury/0.5.0-rc4/
> >
> > This release has been signed with a PGP available here:
> > https://downloads.apache.org/incubator/fury/KEYS
> >
> > Git tag for the release:
> > https://github.com/apache/incubator-fury/releases/tag/v0.5.0-rc4
> >
> > Git commit for the release:
> >
> >
> https://github.com/apache/incubator-fury/commit/51beb134f517917d572dd0cf2b21534d74ecc726
> >
> > Maven staging repo:
> > https://repository.apache.org/content/repositories/orgapachefury-1006
> >
> > How to Build and Test, please refer to:
> >
> >
> https://github.com/apache/incubator-fury/blob/main/docs/guide/DEVELOPMENT.md
> >
> > The vote will be open for at least 72 hours or until the necessary number
> > of votes is reached.
> >
> > Please vote accordingly:
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> > To learn more about apache fury, please see https://fury.apache.org/
> >
> > Checklist for reference:
> >
> > [ ] Download links are valid.
> > [ ] Checksums and signatures.
> > [ ] LICENSE/NOTICE files exist
> > [ ] No unexpected binary files
> > [ ] All source files have ASF headers
> > [ ] Can compile from source
> >
> >
> > Thanks,
> >
> > Chaokun Yang
> >
>

Re: [VOTE] Release Apache Fury(incubating) v0.5.0-rc3

[PJ Fanning]

Hi Sebb,
This email thread is a vote for an RC. If this vote passes, v0.5.0
will be the first release of Fury since it became a podling.
We will add a download page but at the moment, there is nothing to
link to there (except perhaps a KEYS file).

The Install page does need to be updated to not mention snapshots.

Thanks,
PJ

On Mon, 22 Apr 2024 at 10:35, sebb  wrote:
>
> On Sat, 20 Apr 2024 at 16:26, Shawn Yang  wrote:
> >
> > Hello everyone,
> >
> > This is a call for the vote to release Apache Fury(Incubating) v0.5.0-rc3.
> >
> > The Apache Fury community has voted and approved the release of Apache
> > Fury(incubating) v0.5.0-rc3. We now kindly request the IPMC members
> > review and vote for this release.
> >
> > Apache Fury(incubating) - A blazingly fast multi-language serialization
> > framework powered by JIT and zero-copy.
> >
> > Fury community vote thread:
> > https://lists.apache.org/thread/g49qt1v99d0ncfvonng39lcs1s56m7v5
> >
> > Vote result thread:
> > https://lists.apache.org/thread/9rtl03g650pojyfb5d67785tffyo4hbs
> >
> > The release candidate:
> > https://dist.apache.org/repos/dist/dev/incubator/fury/0.5.0-rc3/
> >
> > This release has been signed with a PGP available here:
> > https://downloads.apache.org/incubator/fury/KEYS
> >
>
> I could not find a proper download page for the release.
> This must have links to the source bundle which must use closer.lua,
> as well as links to KEYS, sigs and hashes, with instructions on how to
> validate downloads.
>
> There is an install page on the website at
> https://fury.apache.org/docs/start/install, but that does not link to
> any source bundle.
>
> Furthermore, the install page links to nightly snapshots; this is not
> allowed except on a page intended for Fury developers, who should be
> made aware that nightly code has not been vetted.
>
> > Git tag for the release:
> > https://github.com/apache/incubator-fury/releases/tag/v0.5.0-rc3
> >
> > Git commit for the release:
> > https://github.com/apache/incubator-fury/commit/fae06330edd049bb960536e978a45b97bca66faf
> >
> > Maven staging repo:
> > https://repository.apache.org/content/repositories/orgapachefury-1003
> >
> > How to Build and Test, please refer to:
> > https://github.com/apache/incubator-fury/blob/main/docs/guide/DEVELOPMENT.md
> >
> > The vote will be open for at least 72 hours or until the necessary number
> > of votes is reached.
> >
> > Please vote accordingly:
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> > To learn more about apache fury, please see https://fury.apache.org/
> >
> > Checklist for reference:
> >
> > [ ] Download links are valid.
> > [ ] Checksums and signatures.
> > [ ] LICENSE/NOTICE files exist
> > [ ] No unexpected binary files
> > [ ] All source files have ASF headers
> > [ ] Can compile from source
> >
> >
> > Thanks,
> >
> > Chaokun Yang
>
> -
> 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] Release Apache Fury(incubating) v0.5.0-rc3

[PJ Fanning]

+1 binding carried over from PPMC vote

On Sat 20 Apr 2024, 17:26 Shawn Yang,  wrote:

> Hello everyone,
>
> This is a call for the vote to release Apache Fury(Incubating) v0.5.0-rc3.
>
> The Apache Fury community has voted and approved the release of Apache
> Fury(incubating) v0.5.0-rc3. We now kindly request the IPMC members
> review and vote for this release.
>
> Apache Fury(incubating) - A blazingly fast multi-language serialization
> framework powered by JIT and zero-copy.
>
> Fury community vote thread:
> https://lists.apache.org/thread/g49qt1v99d0ncfvonng39lcs1s56m7v5
>
> Vote result thread:
> https://lists.apache.org/thread/9rtl03g650pojyfb5d67785tffyo4hbs
>
> The release candidate:
> https://dist.apache.org/repos/dist/dev/incubator/fury/0.5.0-rc3/
>
> This release has been signed with a PGP available here:
> https://downloads.apache.org/incubator/fury/KEYS
>
> Git tag for the release:
> https://github.com/apache/incubator-fury/releases/tag/v0.5.0-rc3
>
> Git commit for the release:
>
> https://github.com/apache/incubator-fury/commit/fae06330edd049bb960536e978a45b97bca66faf
>
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachefury-1003
>
> How to Build and Test, please refer to:
>
> https://github.com/apache/incubator-fury/blob/main/docs/guide/DEVELOPMENT.md
>
> The vote will be open for at least 72 hours or until the necessary number
> of votes is reached.
>
> Please vote accordingly:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> To learn more about apache fury, please see https://fury.apache.org/
>
> Checklist for reference:
>
> [ ] Download links are valid.
> [ ] Checksums and signatures.
> [ ] LICENSE/NOTICE files exist
> [ ] No unexpected binary files
> [ ] All source files have ASF headers
> [ ] Can compile from source
>
>
> Thanks,
>
> Chaokun Yang
>

[RESULT] [IP CLEARANCE] Apache Pekko Connectors AWS SPI

[PJ Fanning]

The vote [1] has passed with no objections. Thanks to everyone who
reviewed this.

[1] https://lists.apache.org/thread/1lddvzn24rmpqrndcwt7o1roqbxh32f1

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [IP CLEARANCE] Apache Pekko Connectors AWS SPI

[PJ Fanning]

If there are no objections I will cause this vote as passed. IP Clearance is 
based on lazy consensus. I'll leave this open for another 24 hours just in case 
anyone wants to vote -1 on this.

On 2024/03/30 00:21:16 Craig Russell wrote:
> On Mar 29, 2024, at 10:47, John D. Ament  wrote:
> > 
> > On Fri, Mar 29, 2024 at 11:13 AM Craig Russell  wrote:
> > 
> >> I read the IP-Clearance and this seems to be pretty straightforward:
> >> 
> >> The code has already been partly adjusted to use Pekko -
> >> https://github.com/pjfanning/aws-spi-pekko-http
> >> 
> >> It is our intention to bring the code in
> >> https://github.com/pjfanning/aws-spi-pekko-http into Apache Pekko. The
> >> code in that repo is forked from
> >> https://github.com/matsluni/aws-spi-akka-http and Matthias Lüneberg has
> >> submitted a Software Grant Agreement (SGA) to allow us to use his original
> >> commits.
> >> 
> > 
> > So just to confirm - there's no issue from your perspective that the fork
> > predates the SGA?  I believe that's my only actual concern, and being able
> > to show it clearer is really what I'm trying to say here (but jumping
> > straight to how to do it instead of properly conveying the problem I see).
> > 
> > John
> 
> There are no restrictions on the grant. So to me that means that there is no 
> time box for the grant. The grant should be good before, during, and after 
> the fork.
> 
> Craig
> 
> > 
> > 
> >> 
> >> The original code written by Matthias Lüneberg was granted to ASF and PJ
> >> has forked the project. There are no restrictions in the grant as to what
> >> commit is being granted. The entire repository is covered by the grant.
> >> 
> >> I do not see a problem.
> >> Craig
> >> 
> >>> On Mar 29, 2024, at 06:42, John D. Ament  wrote:
> >>> 
> >>> On Fri, Mar 29, 2024 at 9:32 AM PJ Fanning  wrote:
> >>> 
> >>>> The Software Grant is on file with the ASF Secretary. I don't know
> >>>> where these are checked in but the file is referenced in the
> >>>> grants.txt in the foundation svn repo.
> >>>> 
> >>>> The template file makes no reference to commit ids.
> >>>> 
> >>>> https://www.apache.org/licenses/software-grant-template.pdf
> >>>> 
> >>>> Matthias has basically given us permission to use his Apache licensed
> >>>> code. I am not a lawyer but I think is reasonable to assume that all
> >>>> commits to his repo up the SGA date are covered.
> >>>> 
> >>>> I have an iCLA so all my commits to my fork are surely acceptable to the
> >>>> ASF?
> >>>> 
> >>>> I don't see why listing commit IDs makes the IP Clearance clearer. I
> >>>> can't see commit IDs in any of the cross section of previous clearance
> >>>> forms I have seen.
> >>>> 
> >>> 
> >>> Commit ID is simply one way it's been done.  There's a few examples, I'll
> >>> list them below.  But basically reading your IP form it isn't clear which
> >>> repo is actually being brought into Pekko, perhaps a PR would work as
> >>> well?  There's a couple of examples like that in this list too.  Anything
> >>> that you feel could be done to make it clearer that it's your repo being
> >>> brought in but going through IP Clearance/SGA due to the derived work
> >>> clause (otherwise, it's not clear why you as an officer of the foundation
> >>> need an IP Clearance to bring in your own work).
> >>> 
> >>> [1]: https://incubator.apache.org/ip-clearance/arrow-datafusion-comet
> >>> (Donation PR w/ repo being stood up by us for the target donation)
> >>> [2]:
> >> https://incubator.apache.org/ip-clearance/daffodil-vscode-debugger.html
> >>> (Full original repo and commit ID)
> >>> [3]: https://incubator.apache.org/ip-clearance/avro-rust-library.html
> >> (Full
> >>> original repo and PR)
> >>> [4]: https://incubator.apache.org/ip-clearance/tinkerpop-gremlint.html
> >>> (Commit ID)
> >>> [5]: https://incubator.apache.org/ip-clearance/tika-tika-helm.html (Full
> >>> original repo pointer)
> >>> [6]:
> >>> 
> >> https://incubator.apache.org/ip-clearance/netbeans-dukescript-presenters.html
> >>> (Commit ID and PR)
> >>> [7]: https://incubator.apache.org/ip-cleara

Re: [IP CLEARANCE] Apache Pekko Connectors AWS SPI

[PJ Fanning]

The Software Grant is on file with the ASF Secretary. I don't know
where these are checked in but the file is referenced in the
grants.txt in the foundation svn repo.

The template file makes no reference to commit ids.

https://www.apache.org/licenses/software-grant-template.pdf

Matthias has basically given us permission to use his Apache licensed
code. I am not a lawyer but I think is reasonable to assume that all
commits to his repo up the SGA date are covered.

I have an iCLA so all my commits to my fork are surely acceptable to the ASF?

I don't see why listing commit IDs makes the IP Clearance clearer. I
can't see commit IDs in any of the cross section of previous clearance
forms I have seen.

On Fri, 29 Mar 2024 at 14:19, John D. Ament  wrote:
>
> On Fri, Mar 29, 2024 at 8:34 AM PJ Fanning  wrote:
>
> > Hi John,
> > My GitHub repo [1] is a fork of Matthias Lüneberg's repo [2]. His
> > original repo was built for Akka. My fork modifies it to use Pekko
> > instead.
> > So it is my code that is being imported but the SGA is to acknowledge
> > that the original code was written by Matthias Lüneberg.
> > We can't bring my fork into Apache Pekko itself without Matthias
> > Lüneberg's software grant.
> >
> > [1] https://github.com/pjfanning/aws-spi-pekko-http
> > [2] https://github.com/matsluni/aws-spi-akka-http
>
>
> Ok, I see, you previously created a derived work from the original author's
> work, and I'm assuming you approached the author about donating to the ASF
> via SGA which they did so that you can bring the derived work into Pekko.
> To make that clearer, I would update the IP Clearance to state that the
> code being imported is from your repo at whatever commit hash which was
> forked from the original author's work as of whatever commit hash.
>
> Was the forked repo's commit hash recorded on the SGA?
>
>
> >
> >
> > On Fri, 29 Mar 2024 at 13:14, John D. Ament  wrote:
> > >
> > > I’m a little confused. You’re referring to a third party Matthias
> > Luneberg
> > > but the code reference is pointing to the officer’s personal GitHub
> > > account.
> > >
> > > Which is being imported?
> > >
> > > John
> > >
> > >
> > > On Wed, Mar 27, 2024 at 14:04 PJ Fanning  wrote:
> > >
> > > > Hi everyone,
> > > >
> > > > Apache Pekko is receiving a donation of an AWS SPI.
> > > > The AWS SPI is used to make client calls to AWS APIs and is built
> > > > using Apache Pekko HTTP. We use the AWS SPI in a few of the Apache
> > > > Pekko Connectors.
> > > >
> > > > Please vote to approve this contribution.
> > > > This is a lazy consensus majority vote, per the IP clearance process
> > > > [2], open for at least 72 hours.
> > > >
> > > > Thanks,
> > > > PJ
> > > >
> > > > [1]
> > > >
> > https://incubator.apache.org/ip-clearance/pekko-connectors-aws-spi.html
> > > > [2] https://incubator.apache.org/ip-clearance/
> > > >
> > > > -
> > > > 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

Re: [VOTE] Accept HertzBeat Into the ASF Incubator

[PJ Fanning]

+1 binding - looks like a good candidate for the Apache Incubator

On Fri, 29 Mar 2024 at 14:17, Sheng Wu  wrote:
>
> I am not holding anything.  I didn't vote -1.
>
> Sheng Wu 吴晟
> Twitter, wusheng1108
>
> John D. Ament  于2024年3月29日周五 21:13写道：
> >
> > On Fri, Mar 29, 2024 at 8:41 AM Sheng Wu  wrote:
> >
> > > Hi
> > >
> > > Yes, a project doesn't have to separate the repository into two for
> > > both website and source codes, once the license has been reviewed.
> > > Calcite is another TLP, which is guaranteed, so it is on their PMC
> > > oversight.
> > >
> > > My suggestion is based on things that may not be suitable in your
> > > final release, such as logos from other vendors,
> > > https://github.com/dromara/hertzbeat/tree/master/home/static/img/icons.
> > > Those may be available to use on your website, but not available for
> > > source tar. Such as Apple Inc. logo is included currently.
> > > - https://github.com/dromara/hertzbeat/tree/master/home/static/img/icons
> > > -
> > > https://github.com/dromara/hertzbeat/blob/master/home/static/img/icons/ios.svg
> > >
> > >
> > >
> > I don't understand what you're trying to ask the proposed project to do.
> > It seems like you're holding them to a bar that is above what podlings are
> > expected to follow when coming in to even be considered accepted to the
> > ASF.  I don't think any of this needs to be resolved before we accept the
> > project, we all know that there's a period between when the project leaves
> > its former home and enters its new home that they are in transition and
> > need to make a large number of changes.
> >
> > None of this blocks acceptance, looks like a great addition
> > +1 from me.
> >
> > John
> >
> >
> > > Sheng Wu 吴晟
> > > Twitter, wusheng1108
> > >
> > > Francis Chuang  于2024年3月29日周五 15:47写道：
> > > >
> > > > Thanks, Chao Gong, for addressing those issues in
> > > >
> > > https://github.com/dromara/hertzbeat/commit/1284914c4a2d42c8355417c164810787fb64e588
> > > >
> > > > Looking at the updated website, the issues raised have been taken care
> > > of.
> > > >
> > > > Regarding keeping the website's source code and project code in the
> > > > project repository, I don't think it's 100% necessary to separate the
> > > > website into a separate repository.
> > > >
> > > > For Calcite, our site is in the same repository as our code:
> > > > https://github.com/apache/calcite/tree/main/site
> > > >
> > > > We include the correct licenses in the LICENSE file when we build a
> > > > release, using a template:
> > > > https://github.com/apache/calcite/blob/main/LICENSE
> > > >
> > > > Francis
> > > >
> > > > On 29/03/2024 6:05 pm, Sheng Wu wrote:
> > > > > Some things should be fixed
> > > > >
> > > > > 1. At the top of the home page,  > > > > GitHub⭐️⭐️> exists, this should be removed.
> > > > > 2. At the top menu,  exists, I don't think this project
> > > > > is Huawei, and please don't use another vendor's brand.
> > > > > 3. Similar with <2>, but for OSPP. That is also another org brand.
> > > > > 4. When I first lands on the homepage, there is a pop up box to ask me
> > > > > star on GitHub. This should be removed too. GitHub repository is just
> > > > > a bi-way synced mirror repository. ASF has its own code repository,
> > > > > which is also the main repository to make sure vendor neutral.
> > > > >
> > > > > A thing you should fix later, your website source codes and resources
> > > > > are in the same repository. Those things may not be able to be
> > > > > included considering the license and binaries(png, videos) may be
> > > > > included. In the ASF, website is usually a separate repository.
> > > > > But the  in your proposal seems not included. Please
> > > > > reach your mentors and fix the proposal.
> > > > >
> > > > > Sheng Wu 吴晟
> > > > > Twitter, wusheng1108
> > > > >
> > > > > Zhang Yonglun  于2024年3月29日周五 14:24写道：
> > > > >>
> > > > >> Hi Incubator,
> > > > >>
> > > > >> Following the discussion [DISCUSS] Incubating Proposal for
> > > HertzBeat[1],
> > > > >> I am starting this official vote for the HertzBeat project.
> > > > >>
> > > > >> Here is their proposal:
> > > > >>
> > > https://cwiki.apache.org/confluence/display/INCUBATOR/HertzBeatProposal
> > > > >>
> > > > >> Please cast your vote:
> > > > >>
> > > > >> [ ] +1, bring into the Incubator
> > > > >> [ ] +0, I don't care either way
> > > > >> [ ] -1, do not bring HertzBeat into the Incubator, because...
> > > > >>
> > > > >> The vote will open for one week from today.
> > > > >>
> > > > >> [1] https://lists.apache.org/thread/snxcdyvqgvhgjdmfv4l192g9tdf8w7rn
> > > > >>
> > > > >> Best Regards,
> > > > >> Zhang Yonglun
> > > > >>
> > > > >> -
> > > > >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > >> For additional commands, e-mail: general-h...@incubator.apache.org
> > > > >>
> > > > >
> > > > > 

Re: [IP CLEARANCE] Apache Pekko Connectors AWS SPI

[PJ Fanning]

Hi John,
My GitHub repo [1] is a fork of Matthias Lüneberg's repo [2]. His
original repo was built for Akka. My fork modifies it to use Pekko
instead.
So it is my code that is being imported but the SGA is to acknowledge
that the original code was written by Matthias Lüneberg.
We can't bring my fork into Apache Pekko itself without Matthias
Lüneberg's software grant.

[1] https://github.com/pjfanning/aws-spi-pekko-http
[2] https://github.com/matsluni/aws-spi-akka-http

On Fri, 29 Mar 2024 at 13:14, John D. Ament  wrote:
>
> I’m a little confused. You’re referring to a third party Matthias Luneberg
> but the code reference is pointing to the officer’s personal GitHub
> account.
>
> Which is being imported?
>
> John
>
>
> On Wed, Mar 27, 2024 at 14:04 PJ Fanning  wrote:
>
> > Hi everyone,
> >
> > Apache Pekko is receiving a donation of an AWS SPI.
> > The AWS SPI is used to make client calls to AWS APIs and is built
> > using Apache Pekko HTTP. We use the AWS SPI in a few of the Apache
> > Pekko Connectors.
> >
> > Please vote to approve this contribution.
> > This is a lazy consensus majority vote, per the IP clearance process
> > [2], open for at least 72 hours.
> >
> > Thanks,
> > PJ
> >
> > [1]
> > https://incubator.apache.org/ip-clearance/pekko-connectors-aws-spi.html
> > [2] https://incubator.apache.org/ip-clearance/
> >
> > -
> > 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] Release Apache HoraeDB(incubating) v2.0.0-RC5 - Incubator Vote Round 1

[PJ Fanning]

The Incubator PMC prefers that git commit ids are included in the vote
emails because git tags can be moved. Git tags are encouraged but we
like to see the Git commit id too.

On Thu, 28 Mar 2024 at 12:06, Xuanwo  wrote:
>
> Hi, I have checked the following and found some issues.
>
> [x] Download links are valid.
> [x] Checksums and signatures.
>
> gpg: Signature made Tue 19 Mar 2024 02:21:30 PM CST
> gpg:using RSA key 8BF38B1BBF93AD717DD63948F3EA26DA0F715C7F
> gpg: checking the trustdb
> gpg: marginals needed: 3  completes needed: 1  trust model: pgp
> gpg: depth: 0  valid:  24  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 24u
> gpg: next trustdb check due at 2024-05-25
> gpg: Good signature from "chunshao.rcs " [ultimate]
> apache-horaedb-incubating-v2.0.0-src.tar.gz: OK
>
> [x] LICENSE/NOTICE files exist
> [-] No unexpected binary files
>
> I have seen many hidden binary files like
>
> - ._.asf.yaml
> - .asf.yaml
> - ._Cargo.lock
> - ._Cargo.toml
> - ._clippy.toml
> - ._CONTRIBUTING.md
> - ._DEPENDENCIES.tsv
>
> Please check the package tool and remove them
>
> [-] All source files have ASF headers
>
> I have seen files like "src/components/skiplist/src/key.rs" been excluded from
> license check, is there a reason for this?
>
> By the way, I recommend relying on released tags rather than individual 
> commits
> in github.
>
> [-] Can compile from source
>
> cargo build failed for:
>
> ```
>1470 |   return std::move(status);
> |  ~^~~~
>   
> /home/xuanwo/.cargo/git/checkouts/rust-rocksdb-a9a28e74c6ead8ef/f04f4dd/librocksdb_sys/rocksdb/db/db_impl/db_impl.cc:1470:19:
>  note: remove ‘std::move’ call
>   cc1plus: all warnings being treated as errors
>   make[3]: *** [CMakeFiles/rocksdb.dir/build.make:555: 
> CMakeFiles/rocksdb.dir/db/db_impl/db_impl.cc.o] Error 1
>   make[2]: *** [CMakeFiles/Makefile2:142: CMakeFiles/rocksdb.dir/all] Error 2
>   make[1]: *** [CMakeFiles/Makefile2:149: CMakeFiles/rocksdb.dir/rule] Error 2
>   make: *** [Makefile:172: rocksdb] Error 2
>   thread 'main' panicked at 
> /home/xuanwo/.cargo/registry/src/index.crates.io-6f17d22bba15001f/cmake-0.1.50/src/lib.rs:1098:5:
>
>   command did not execute successfully, got: exit status: 2
> ```
>
> Maybe we should supress the warnings?
>
> On Wed, Mar 27, 2024, at 11:47, 任春韶 wrote:
> > I'm sorry, there was a problem with the formatting of the email I sent just
> > now.
> >
> > Hello, Incubator Community,
> >
> > This is a call for a vote to release Apache HoraeDB(incubating) version
> > v2.0.0-RC5
> >
> > HoraeDB PPMC Vote Thread
> > https://lists.apache.org/thread/trvhct3nqgkqkb5mxg4sy26gkn90d31v
> >
> > HoraeDB PPMC Vote Result
> > https://lists.apache.org/thread/p6tkbnvt7wrx956d87h077nbls2yls1r
> >
> > The release candidate:
> > https://dist.apache.org/repos/dist/dev/incubator/horaedb/horaedb/v2.0.0-rc.5
> >
> >
> > This release has been signed with a PGP available here:
> > https://downloads.apache.org/incubator/horaedb/KEYS
> >
> > Git tag for the release
> > https://github.com/apache/incubator-horaedb/releases/tag/v2.0.0-rc.5
> >
> > Please download, verify, and test.
> >
> > The VOTE will pass after got 3 binding approve.
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> > To learn more about Apache HoraeDB, please see https://horaedb.apache.org/
> >
> > Checklist for reference:
> >
> > [ ] Download links are valid.
> > [ ] Checksums and signatures.
> > [ ] LICENSE/NOTICE files exist
> > [ ] No unexpected binary files
> > [ ] All source files have ASF headers
> > [ ] Can compile from source
> >
> > Thanks
> >
> > 任春韶  于2024年3月27日周三 11:38写道：
> >
> >> Hello, Incubator Community, This is a call for a vote to release Apache
> >> HoraeDB(incubating) version v2.0.0-RC5 HoraeDB PPMC Vote Thread
> >> https://lists.apache.org/thread/trvhct3nqgkqkb5mxg4sy26gkn90d31v HoraeDB
> >> PPMC Vote Result
> >> https://lists.apache.org/thread/p6tkbnvt7wrx956d87h077nbls2yls1r The
> >> release candidate:
> >> https://dist.apache.org/repos/dist/dev/incubator/horaedb/horaedb/v2.0.0-rc.5
> >> This release has been signed with a PGP available here:
> >> https://downloads.apache.org/incubator/horaedb/KEYS Git tag for the
> >> release:
> >> https://github.com/apache/incubator-horaedb/releases/tag/v2.0.0-rc.5
> >> Please download, verify, and test. The VOTE will pass after got 3 binding
> >> approve. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove with the reason
> >> To learn more about Apache HoraeDB, please see https://horaedb.apache.org/
> >> Checklist for reference: [ ] Download links are valid. [ ] Checksums and
> >> signatures. [ ] LICENSE/NOTICE files exist [ ] No unexpected binary files [
> >> ] All source files have ASF headers [ ] Can compile from source Thanks
> >>
>
> --
> Xuanwo
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: 

[IP CLEARANCE] Apache Pekko Connectors AWS SPI

[PJ Fanning]

Hi everyone,

Apache Pekko is receiving a donation of an AWS SPI.
The AWS SPI is used to make client calls to AWS APIs and is built
using Apache Pekko HTTP. We use the AWS SPI in a few of the Apache
Pekko Connectors.

Please vote to approve this contribution.
This is a lazy consensus majority vote, per the IP clearance process
[2], open for at least 72 hours.

Thanks,
PJ

[1] https://incubator.apache.org/ip-clearance/pekko-connectors-aws-spi.html
[2] https://incubator.apache.org/ip-clearance/

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Graduate Apache SDAP (Incubating) as a Top Level Project

[PJ Fanning]

+1 binding

On Wed, 27 Mar 2024 at 17:11, Riley Kuttruff  wrote:
>
> Hi everyone,
>
> Just a quick reminder that this vote is still open.
>
> Thanks,
> Riley
>
> On 2024/03/15 22:18:34 Riley Kuttruff wrote:
> > Hi all,
> >
> > Following the positive feedback we received in the DISCUSS thread [1],
> > we would like to open the official VOTE to graduate now.
> >
> > 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 3 releases with 3 release managers
> > - 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 [2]
> >
> > Please vote on the resolution below the line to graduate and establish
> > Apache SDAP as a Top-Level Project
> >
> > [ ] +1 Graduate Apache SDAP from the Incubator to a TLP
> > [ ] 0  No opinion
> > [ ] -1 Do not graduate Apache SDAP because…
> >
> > This vote will remain open for at least 72 hours.
> >
> > 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!
> >
> > We’d also like to thank the SDAP community as well as the Incubator
> > community for your time and support in getting us to where we are now.
> >
> > [1] https://lists.apache.org/thread/pv21d9kf05166hkj89lv11s65oyvbdrk
> > [2] 
> > https://github.com/apache/incubator-sdap-website/blob/asf-site/maturity.md
> >
> > ---
> >
> > 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 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 SDAP Project be and hereby is tasked with
> > the migration and rationalization of the Apache Incubator SDAP
> > podling; and be it further
> >
> > RESOLVED, that all responsibilities pertaining to the Apache Incubator
> > SDAP podling encumbered upon the Apache Incubator PMC are hereafter
> > discharged.
> >
> > ---
> >
> > Thank you,
> >
> > Riley Kuttruff
> >
> > -
> > To unsubscribe, e-mail: 

Re: Registering a release

[PJ Fanning]

I don't think this is required for a podling release. Reporter tool
only seems to worry about TLP releases.

The releases have to be announced on mailing lists including this one
and the main ASF announce list.

On Thu, 21 Mar 2024 at 00:30, Julian Hyde  wrote:
>
> Can someone remind me where I go (whimsy or reporter, I presume) to
> register a release from a podling (in this case SDAP)?
>
> In Calcite, a top-level project that deploys Java artifacts to Maven
> Central, the process has been straightforward. I believe I even
> received an email from Reporter sending me to the registration page.
> But for SDAP I can't figure out where to register the release.
>
> Thanks!
>
> Julian
>
> -
> 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] Accept StormCrawler Into the ASF Incubator

[PJ Fanning]

The vote passes [1] with 17 +1s, 13 binding.

Thanks to everyone who participated in the discussion and vote.

Binding
P. Taylor Goetz
Dave Fisher
Furkan Kamaci
Xin Wang
Kent Yao
Charles Zhang
Zhang Yonglun
Yu Xiao
Xuanwo
Jean-Baptiste Onofré
Yu Li
Ayush Saxena
PJ Fanning

Non Binding
Tim Allison
Josh Fischer
Leonard（Lifeng Nie)
Suyan

I will proceed with setting up the Podling.

[1] https://lists.apache.org/thread/nxoykngrbg517kmlcqrrnx3bgcwjnry1

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Accept StormCrawler Into the ASF Incubator

[PJ Fanning]

adding my +1 (binding) for the record

On 2024/03/13 19:31:10 Ayush Saxena wrote:
> +1 (Binding)
> 
> -Ayush
> 
> On Wed, 13 Mar 2024 at 21:25, Yu Li  wrote:
> 
> > +1 (binding)
> >
> > Good luck!
> >
> > Best Regards,
> > Yu
> >
> > On Wed, 13 Mar 2024 at 23:50, Suyan  wrote:
> > >
> > > +1 non-binding
> > >
> > > Good luck!
> > >
> > > Sincerely,
> > > Suyan
> > >
> > > PJ Fanning  于2024年3月13日周三 04:33写道：
> > > >
> > > > Hi everyone,
> > > >
> > > > Following the discussion about the StormCrawler proposal [1], I am
> > > > starting this official vote for the StormCrawler podling. Here is the
> > > > proposal:
> > > >
> > > >
> > https://cwiki.apache.org/confluence/display/INCUBATOR/StormCrawler+Proposal
> > > >
> > > > Please cast your vote:
> > > > [ ] +1, bring into the Incubator
> > > > [ ] +0, I don't care either way
> > > > [ ] -1, do not bring StormCrawler into the Incubator, because...
> > > >
> > > > The vote will open for one week from today, 12 March, 2024.
> > > >
> > > > Thanks,
> > > > PJ
> > > >
> > > > [1] https://lists.apache.org/thread/sjht4k1ojhcgfnzszxb809g1dh2t1dlw
> > > >
> > > > -
> > > > 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

[jira] [Commented] (INCUBATOR-283) Please delete tag v2.0.0 in incubator-horaedb

[PJ Fanning (Jira)]

[ 
https://issues.apache.org/jira/browse/INCUBATOR-283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17828248#comment-17828248
 ] 

PJ Fanning commented on INCUBATOR-283:
--

INFRA team are happy to remove errant tags on the rare occasion that they are 
added by mistake.

I'm not sure if the tags are immutable by default. You can add the your 
.asf.yaml file to make them immutable (but INFRA team are still able to remove 
them, if asked).

https://github.com/apache/incubator-pekko/blob/main/.asf.yaml#L17-L18 (only 
protects tags beginning with `v`)


> Please delete tag v2.0.0 in incubator-horaedb
> -
>
> Key: INCUBATOR-283
> URL: https://issues.apache.org/jira/browse/INCUBATOR-283
> Project: Incubator
>  Issue Type: Task
>Reporter: Chunshao Ren
>Priority: Minor
>
> Please delete the tag v2.0.0, as it was created by mistake earlier. The 
> version 2.0.0 is currently undergoing a vote.
> https://github.com/apache/incubator-horaedb/releases/tag/v2.0.0
>  



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

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] The retirement of Apache Milagro

[PJ Fanning]

+1 (binding)

Email traffic on the Milagro mailing lists is very low. This seems
like the right decision.

On Mon, 18 Mar 2024 at 08:46, jean-frederic clere  wrote:
>
> Hi All,
>
> Based on discussion[1], I would like to call a vote to retire Apache
> Milagro.
>
> Please vote accordingly:
> [] +1 approve
> [] +0 no option
> [] -1 disapprove with a reason
>
> [1]: https://lists.apache.org/thread/kfnro4o2tdctlc6tryxmn70tddpwf5wh
>
> Thank you all for your participation.
>
> --
> Cheers
>
> Jean-Frederic
>
> -
> 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: [DISCUSS] Incubating Proposal for HertzBeat

[PJ Fanning]

Would there be any chance that you could reconsider the name? Hertz is
a very well known international car rental brand.

On Sat, 16 Mar 2024 at 14:24, Zhang Yonglun  wrote:
>
> Hi IPMC members,
>
> I would like to propose a new project to the ASF incubator - HertzBeat.
>
> HertzBeat[1] is an easy-to-use, open source, real-time monitoring
> system. It features an agentless architecture, high-performance
> clustering, Prometheus compatibility, and powerful custom monitoring
> and status page building capabilities.
>
> Here is the proposal -
> https://cwiki.apache.org/confluence/display/INCUBATOR/HertzBeatProposal
>
> I would be the Champion of the project. I will mentor and help the project
> through the incubator with Yu Xiao [xia...@apache.org], Justin Mclean
> (jmcl...@apache.org).
>
> We are open to hearing the feedback from the incubator.
>
> [1] https://hertzbeat.dromara.org/
>
> --
>
> Zhang Yonglun
> Apache ShenYu & ShardingSphere
>
> -
> 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] Accept GraphAr into the ASF Incubator

[PJ Fanning]

+1 binding

On Fri, 15 Mar 2024 at 09:18, Kent Yao  wrote:
>
> +1 binding & Good luck!
>
> Kent Yao
>
> Calvin Kirs  于2024年3月15日周五 14:02写道：
> >
> > +1 binding
> >
> > On Fri, Mar 15, 2024 at 1:58 PM Yu Li  wrote:
> >
> > > Hi All,
> > >
> > > With positive feedback from the proposal discussion [1], I am starting
> > > this official vote to accept GraphAr into the Incubator. Here is the
> > > proposal:
> > >
> > > https://cwiki.apache.org/confluence/display/INCUBATOR/GraphArProposal
> > >
> > > Please cast your vote:
> > > [ ] +1, accept GraphAr into the Incubator
> > > [ ] +0, I don't care either way
> > > [ ] -1, do not accept GraphAr into the Incubator, because...
> > >
> > > The vote will open for one week from today, 15 March, 2024. Thanks.
> > >
> > > Best Regards,
> > > Yu
> > >
> > > [1] https://lists.apache.org/thread/bldz3rnp8nvhlmrd2gqkl30fgk9z3zhx
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
> > --
> > Best wishes！
> > CalvinKirs
>
> -
> 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] Release Apache SDAP (incubating) 1.2.0-rc4

[PJ Fanning]

+1 (binding)

Thanks Stepheny for looking at the issues.

I verified the source tgzs including the checksums and signatures.
The license, notice and disclaimer files seem correct.
No unexpected binary files.
The ASF headers are on the main files.


On 2024/03/12 16:48:53 Stepheny Perez wrote:
> Hi P J,
> 
> I just removed the old RC's from 
> https://dist.apache.org/repos/dist/dev/incubator/sdap/
> 
> Thanks!
> Stepheny
> 
> On 2024/03/08 22:16:17 PJ Fanning wrote:
> > Hi Stepheny,
> > 
> > Can you remove the old RCs from
> > https://dist.apache.org/repos/dist/dev/incubator/sdap/ ?
> > 
> > Is the signing key in
> > https://dist.apache.org/repos/dist/release/incubator/sdap/KEYS ? With
> > releases, you are supposed to point users to this file not provide a
> > link to https://keyserver.ubuntu.com
> > 
> > On Fri, 8 Mar 2024 at 18:55, Stepheny Perez  wrote:
> > >
> > > Hello everyone,
> > >
> > > This is a call for a vote to release Apache SDAP (incubating) version 
> > > 1.2.0-rc4.
> > >
> > > The Apache SDAP community has voted to approve release of Apache SDAP 
> > > (incubating) version 1.2.0-rc4.
> > >
> > > We now request the Incubator PMC review and vote on this release.
> > >
> > > SDAP community thread:
> > > https://lists.apache.org/thread/h9g3cdok0py2vjp1pplz1wq4ofl4sbjx
> > >
> > > Changes made between previous candidate (rc3) and this one (rc4) are as 
> > > follows:
> > > - Updated SDAP to use Poetry package manager to more explicitly manage 
> > > dependencies and transitive dependencies. This was needed to ensure no 
> > > GPL license dependencies are used by the software.
> > > - Patch for domspurge helper script
> > >
> > > Instructions for building docker images from source can be found here:
> > > https://github.com/apache/incubator-sdap-nexus/blob/1.2.0-rc4/docs/build.rst
> > > Instructions for deploying locally to test can be found here:
> > > https://github.com/apache/incubator-sdap-nexus/blob/1.2.0-rc4/docs/quickstart.rst
> > > The release files, including signatures, digests, etc. can be found at:
> > > https://dist.apache.org/repos/dist/dev/incubator/sdap/apache-sdap-1.2.0-rc4/
> > >
> > > For convenience, the tags we built the release artifacts to be voted on
> > > from are 1.2.0-rc4:
> > >
> > > - ingester:
> > > - URL: https://github.com/apache/incubator-sdap-ingester/tree/1.2.0-rc4
> > > - Commit: 5c116badfaf913734d017d41acc765ed3fd978a1
> > >
> > > - nexus:
> > > - URL: https://github.com/apache/incubator-sdap-nexus/tree/1.2.0-rc4
> > > - Commit: 3fce31f08b9057db446036724e8bc62dd6d1560a
> > >
> > > For verification, the hashes (SHA-512) of the .tar.gz artifacts we are 
> > > voting on are as follows:
> > >
> > > apache-sdap-ingester-1.2.0-incubating-src.tar.gz:
> > > 7301c54e765882c45f6efe4a06463b837ace62b6eea2ae5437113357466e52f1d905c3c9d46295f1b1058b9ecf5025942f8a89b2c53a1b0d6b69cd52a8890257
> > >
> > > apache-sdap-nexus-1.2.0-incubating-src.tar.gz:
> > > 1a2907f9c36dbf0b4b25d54c095303ab0602fa9e0a9423deceae402ffd9a360e21ba832c3ea497d8eccbc6c91fedd2926b3b33181a14c22d50d0ec996282bc75
> > >
> > > Release artifacts are signed with the following key:
> > > https://keyserver.ubuntu.com/pks/lookup?op=get=0x2E8418801953621FAA322169D6F360887071C194
> > >
> > > Please vote on releasing this package as Apache SDAP (incubating) 1.2.0.
> > >
> > > The vote is open for 72 hours and passes if at least 3 +1 PMC votes are 
> > > cast.
> > >
> > > [ ] +1 Release this package as Apache SDAP (incubating) 1.2.0
> > > [ ] +0 No opinion
> > > [ ] -1 Do not release this package because ...
> > >
> > > Thank you,
> > > Stepheny
> > >
> > > -
> > > 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

[VOTE] Accept StormCrawler Into the ASF Incubator

[PJ Fanning]

Hi everyone,

Following the discussion about the StormCrawler proposal [1], I am
starting this official vote for the StormCrawler podling. Here is the
proposal:

https://cwiki.apache.org/confluence/display/INCUBATOR/StormCrawler+Proposal

Please cast your vote:
[ ] +1, bring into the Incubator
[ ] +0, I don't care either way
[ ] -1, do not bring StormCrawler into the Incubator, because...

The vote will open for one week from today, 12 March, 2024.

Thanks,
PJ

[1] https://lists.apache.org/thread/sjht4k1ojhcgfnzszxb809g1dh2t1dlw

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Podling web sites: make (incubator.) optional in podling urls

[PJ Fanning]

+1 (binding)

On 2024/03/12 18:36:47 Craig Russell wrote:
> After this discussion
> https://lists.apache.org/thread/frwsy1g1pkx3ppbvzt538xxh9qo9y319
> I'd like to propose that we make the incubator. part of the URL optional for 
> podlings.
> 
> This is a way to minimize the work needed to graduate. No redirect or 
> reimplementation of the web site is required. 
> 
> https://incubator.apache.org/guides/branding.html will need to change only 
> the URL requirement. Other branding requirements are still applicable.
> 
> While most podlings do have incubator. in their URL, several do not and it is 
> a flag for the web site checker.
> 
> +1 make incubator. optional in URL
> +0 do not care strongly
> -1 keep the requirement for incubator. in URL
> 
> Please vote with your ASF id followed by (binding) if you are a member of the 
> Incubator PMC or (not binding) if not.
> 
> Vote will be open for at least 72 hours.
> 
> Here is my +1
> 
> 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: [DISCUSS] Incubating Proposal for StormCrawler

[PJ Fanning]

Thanks Ayush. We could certainly do with another experienced mentor.
I've added you to the mentor list in the proposal.

On Mon, 11 Mar 2024 at 10:19, Ayush Saxena  wrote:
>
> +1 (Binding)
> I can volunteer as an additional mentor if needed.
>
> -Ayush
>
> On Fri, 8 Mar 2024 at 02:43, Dave Fisher  wrote:
>
> > There are options. I helped establish ASF Pelican by converting the main
> > ASF website from the Apache CMS. See GitHub.com/apache/www-site/. I don’t
> > think it needs to be decided in the proposal. It can be decided at he
> > beginning of Incubation.
> >
> > Best,
> > Dave
> >
> > > On Mar 7, 2024, at 1:37 PM, tison  wrote:
> > >
> > > A minor comment:
> > >
> > >> We are planning to build the https://stormcrawler.apache.org website
> > with Jekyll, maybe based on
> > https://github.com/apache/apache-website-template.
> > >
> > > This branch is unmaintained for years (although some volunteers show
> > > their interests, there is no move so far) and you may encounter many
> > > issues.
> > >
> > > I suggest you use Fury site as a template (PJ is also a mentor of
> > > Fury) and adjust to your content. I'm also working on a Docusaurus
> > > based website template [1] recently.
> > >
> > > Best,
> > > tison.
> > >
> > > [1] https://github.com/apache/apache-website-template/tree/docusaurus
> > >
> > > PJ Fanning  于2024年3月8日周五 02:29写道：
> > >>
> > >> Thanks Lewis. It would be great if you can act as a menot. I will
> > >> update the proposal to add you to the mentor list.
> > >>
> > >> On Thu, 7 Mar 2024 at 19:09, Lewis John McGibbney 
> > wrote:
> > >>>
> > >>> I think StromCrawler would be an excellent candidate for the Incubator.
> > >>> If the podling is looking for an additional mentor, I would be happy
> > to chip in.
> > >>> lewismc
> > >>>
> > >>> On 2024/03/03 23:24:38 PJ Fanning wrote:
> > >>>> Hi everyone,
> > >>>>
> > >>>> I would like to propose StormCrawler [1] as a new Apache Incubator
> > project,
> > >>>> and you can examine the proposal [2] for more details.
> > >>>>
> > >>>> StormCrawler is a collection of resources for building low-latency,
> > >>>> customisable and scalable web crawlers on Apache Storm.
> > >>>>
> > >>>> Proposal
> > >>>>
> > >>>> The aim of StormCrawler is to help build web crawlers that are:
> > >>>>
> > >>>> * scalable
> > >>>> * resilient
> > >>>> * low latency
> > >>>> * easy to extend
> > >>>> * polite yet efficient
> > >>>>
> > >>>> StormCrawler achieves this partly with Apache Storm, which it is based
> > >>>> on. To use an analogy, Apache Storm is to StormCrawler what Apache
> > >>>> Hadoop is to Apache Nutch.
> > >>>>
> > >>>> StormCrawler is mature (26 releases to date) and is used by many
> > >>>> organisations world-wide.
> > >>>>
> > >>>> Initial Committers
> > >>>>
> > >>>> Julien Nioche [jnio...@apache.org https://github.com/jnioche]
> > >>>> Sebastian Nagel [sna...@apache.org https://github.com/sebastian-nagel
> > ]
> > >>>> Richard Zowalla [r...@apache.org  https://github.com/rzo1]
> > >>>> Tim Allison [talli...@apache.org https://github.com/tballison]
> > >>>> Michael Dinzinger [michael.dinzin...@uni-passau.de
> > >>>> https://github.com/michaeldinzinger]
> > >>>>
> > >>>> Most of the existing StormCrawler contributors are existing ASF
> > >>>> committers and are looking to build a vibrant community following the
> > >>>> Apache Way.
> > >>>>
> > >>>> I will help this project as the champion and mentor. We would welcome
> > >>>> additional mentors, if anyone has an interest in helping.
> > >>>>
> > >>>> We are looking forward to your questions and feedback.
> > >>>>
> > >>>> Thanks,
> > >>>> PJ
> > >>>>
> > >>>> [1] https://github.com/DigitalPebble/storm-cr

Re: [VOTE] Release Apache Pekko, incubating, Sbt Paradox 1.0.1-RC2

[PJ Fanning]

carrying over my +1 binding from the Pekko community vote.

On 2024/03/09 09:57:49 Matthew de Detrich wrote:
> > Please use the official URL for KEYS:
> 
> > https://downloads.apache.org/incubator/pekko/KEYS
> > This says that the KEYS file can be obtained from the source archive.
> 
> > This is totally insecure.
> 
> > Anyone could create their own key and add it to the KEYS file in their
> own version of the source.
> 
> > The KEYS file should not be included in the source, and documentation
> should only refer to fetching the KEYS file directly from the official
> location.
> 
> Apologies, we have an email template that is used and evidently it needs
> to be updated which I have just done[1]
> 
> 1:
> https://github.com/apache/incubator-pekko-site/wiki/Pekko-Release-Process/_compare/74fb418670e2524f5765e1155c63b7244e2b2669
> 
> Thanks,
> Matthew de Detrich
> 
> On Sat, Mar 9, 2024 at 10:44 AM sebb  wrote:
> 
> > On Sat, 9 Mar 2024 at 09:01, Matthew de Detrich
> >  wrote:
> > >
> > > Hello Incubator Community,
> > >
> > > This is a call for a vote to release Apache Pekko(incubating) Sbt Paradox
> > > version 1.0.1-RC2.
> > >
> > > The discussion thread:
> > >
> > > https://lists.apache.org/thread/8wp7h76dktr99hz6lrclmz7z5or19kdn
> > >
> > > The Pekko vote thread:
> > >
> > > https://lists.apache.org/thread/vmxqly8ttsrq82czpcpto34zgk2ndl7x
> > >
> > > The Pekko vote result:
> > >
> > > https://lists.apache.org/thread/405ph9bl73zm5rf96p6yp7dcf2tthqc6
> > >
> > > The release candidate:
> > >
> > >
> > https://dist.apache.org/repos/dist/dev/incubator/pekko/SBT-PARADOX-1.0.1-RC2/
> > >
> > > This release has been signed with a PGP key, available here:
> > >
> > > https://dist.apache.org/repos/dist/release/incubator/pekko/KEYS
> >
> > Please use the official URL for KEYS:
> >
> > https://downloads.apache.org/incubator/pekko/KEYS
> >
> > > Purpose:
> > >
> > > This is a build tool used in Apache Pekko projects to build the web
> > pages.
> > >
> > > Git branch for the release:
> > >
> > >
> > https://github.com/apache/incubator-pekko-sbt-paradox/releases/tag/v1.0.1-RC2
> > > Git commit ID: 810043faf10780020a6742b0c2af5dde83dfd628
> > >
> > > Please download, verify, and test.
> > >
> > > We have also staged jars in the Apache Nexus Repository. These were
> > > built with the same code as appears in this Source Release Candidate. We
> > > would appreciate if users could test with these too.
> > > If anyone finds any serious problems with these jars, please also notify
> > us
> > > on this thread.
> > >
> > > https://repository.apache.org/content/groups/staging/org/apache/pekko/
> > >
> > > In sbt, you can add this resolver.
> > >
> > > resolvers += "Apache Pekko Staging" at "
> > > https://repository.apache.org/content/groups/staging;
> > >
> > > The vote will be left open for at least 72 hours.
> > >
> > > [ ] +1 approve
> > > [ ] +0 no opinion
> > > [ ] -1 disapprove with the reason
> > >
> > > To learn more about Apache Pekko, please see https://pekko.apache.org/
> > >
> > > Checklist for reference:
> > >
> > > [ ] Download links are valid.
> > > [ ] Checksums and signatures.
> > > [ ] LICENSE/NOTICE files exist
> > > [ ] No unexpected binary files
> > > [ ] Source files have ASF headers
> > > [ ] Can compile from source
> > >
> > > To compile from the source, please refer to:
> > >
> > >
> > https://github.com/apache/incubator-pekko-http/blob/main/README.md#building-from-source
> > >
> > > Some notes about verifying downloads can be found at:
> > >
> > > https://pekko.apache.org/download.html#verifying-downloads
> >
> > This says that the KEYS file can be obtained from the source archive.
> >
> > This is totally insecure.
> >
> > Anyone could create their own key and add it to the KEYS file in their
> > own version of the source.
> >
> > The KEYS file should not be included in the source, and documentation
> > should only refer to fetching the KEYS file directly from the official
> > location.
> >
> >
> > > Here is my +1 (binding).
> > >
> > > Thanks,
> > > Matthew de Detrich
> > >
> > > --
> > >
> > > Matthew de Detrich
> > >
> > > *Aiven Deutschland GmbH*
> > >
> > > Immanuelkirchstraße 26, 10405 Berlin
> > >
> > > Alexanderufer 3-7, 10117 Berlin
> > >
> > > Amtsgericht Charlottenburg, HRB 209739 B
> > >
> > > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> > >
> > > *m:* +491603708037
> > >
> > > *w:* aiven.io *e:* matthew.dedetr...@aiven.io
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
> 
> -- 
> 
> Matthew de Detrich
> 
> *Aiven Deutschland GmbH*
> 
> Immanuelkirchstraße 26, 10405 Berlin
> 
> Alexanderufer 3-7, 10117 Berlin
> 
> Amtsgericht Charlottenburg, HRB 209739 B
> 
> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> 
> *m:* +491603708037
> 
> *w:* aiven.io *e:* matthew.dedetr...@aiven.io
> 

Re: [VOTE] Graduate Apache Paimon (Incubating) as a Top Level Project

[PJ Fanning]

+1 binding

On Sun, 10 Mar 2024 at 13:02, Kent Yao  wrote:
>
> +1 binding
>
> 张铎(Duo Zhang) 于2024年3月10日 周日14:50写道：
>
> > +1 binding
> >
> > tison  于2024年3月9日周六 15:47写道：
> > >
> > > +1 binding
> > >
> > > Good project.
> > >
> > > Best,
> > > tison.
> > >
> > > Xin Wang  于2024年3月9日周六 15:18写道：
> > > >
> > > > +1, binding
> > > >
> > > > Becket Qin  于2024年3月9日周六 11:24写道：
> > > >
> > > > > +1 (binding)
> > > > >
> > > > > Cheers,
> > > > >
> > > > > Jiangjie (Becket) Qin
> > > > >
> > > > >
> > > > >
> > > > > On Fri, Mar 8, 2024 at 4:49 PM Calvin Kirs  wrote:
> > > > >
> > > > > > +1 binding
> > > > > >
> > > > > > On Fri, Mar 8, 2024 at 7:05 PM Nicholas 
> > wrote:
> > > > > > >
> > > > > > > +1(non-binding)
> > > > > > >
> > > > > > >
> > > > > > > Regards,
> > > > > > > Nicholas Jiang
> > > > > > >
> > > > > > >
> > > > > > > - Original Message -
> > > > > > > From: "Yu Li" 
> > > > > > > To: general@incubator.apache.org
> > > > > > > Sent: Fri, 8 Mar 2024 18:50:36 +0800
> > > > > > > Subject: [VOTE] Graduate Apache Paimon (Incubating) as a Top
> > Level
> > > > > > Project
> > > > > > >
> > > > > > > Hi All,
> > > > > > >
> > > > > > > We've got positive feedback on the DISCUSS thread for graduation
> > [1],
> > > > > > > and would like to start an official VOTE thread now.
> > > > > > >
> > > > > > > Below are some facts and project highlights from the incubation
> > phase
> > > > > > > as well as the draft resolution:
> > > > > > >
> > > > > > > - Currently, our community consists of 18 committers (including
> > > > > > > mentors) from ~10 different companies, with 11 serving as PPMC
> > > > > > > members.
> > > > > > > - So far, we have boasted 132 contributors.
> > > > > > > - Throughout the incubation period, we've made 5 releases in 12
> > > > > > > months, at a stable pace.
> > > > > > > - We've had 3 different release managers to date.
> > > > > > > - Our software is used in production by 20+ well known entities.
> > > > > > > - As yet, we have opened 1,363 issues with 1,083 successfully
> > > > > > > resolved, including the period as a sub-project of Apache Flink.
> > > > > > > - We have submitted a total of 2,166 PRs, out of which 2,091
> > have been
> > > > > > > merged or closed.
> > > > > > > - We have met all maturity criteria as outlined in [2].
> > > > > > >
> > > > > > > Please vote on the resolution pasted below to graduate Apache
> > Paimon
> > > > > > > from the Incubator to the Top Level Project.
> > > > > > >
> > > > > > >  [ ] +1 Graduate Apache Paimon from the Incubator.
> > > > > > >  [ ] +0 No opinion.
> > > > > > >  [ ] -1 Don't graduate Apache Paimon from the Incubator because
> > ...
> > > > > > >
> > > > > > > This vote will open for at least 72 hours.
> > > > > > >
> > > > > > > We would like to thank everyone who has participated in the
> > Apache
> > > > > > > Paimon community. We 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/012rfy2zvnhqh39foncwvdpvy9fzry1q
> > > > > > > [2]
> > > > > >
> > > > >
> > https://cwiki.apache.org/confluence/display/PAIMON/Apache+Maturity+Model+Assessment+for+Paimon
> > > > > > >
> > > > > > >
> > ---
> > > > > > >
> > > > > > > Establish the Apache Paimon 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 unified lake storage to build dynamic tables for
> > both
> > > > > > > stream and batch processing with big data compute engines,
> > supporting
> > > > > > > high-speed data ingestion and real-time data query.
> > > > > > >
> > > > > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> > Committee
> > > > > > > (PMC), to be known as the "Apache Paimon Project", be and hereby
> > is
> > > > > > > established pursuant to Bylaws of the Foundation; and be it
> > further
> > > > > > >
> > > > > > > RESOLVED, that the Apache Paimon Project be and hereby is
> > responsible
> > > > > > > for the creation and maintenance of software related to a
> > unified lake
> > > > > > > storage to build dynamic tables for both stream and batch
> > processing
> > > > > > > with big data compute engines, supporting high-speed data
> > ingestion and
> > > > > > > real-time data query; and be it further
> > > > > > >
> > > > > > > RESOLVED, that the office of "Vice President, Apache Paimon" be
> > and
> > > > > > > hereby is created, the person holding such office to serve at the
> > > > > > > direction of the Board of Directors 

Re: [VOTE] Release Apache SDAP (incubating) 1.2.0-rc4

[PJ Fanning]

Hi Stepheny,

Can you remove the old RCs from
https://dist.apache.org/repos/dist/dev/incubator/sdap/ ?

Is the signing key in
https://dist.apache.org/repos/dist/release/incubator/sdap/KEYS ? With
releases, you are supposed to point users to this file not provide a
link to https://keyserver.ubuntu.com

On Fri, 8 Mar 2024 at 18:55, Stepheny Perez  wrote:
>
> Hello everyone,
>
> This is a call for a vote to release Apache SDAP (incubating) version 
> 1.2.0-rc4.
>
> The Apache SDAP community has voted to approve release of Apache SDAP 
> (incubating) version 1.2.0-rc4.
>
> We now request the Incubator PMC review and vote on this release.
>
> SDAP community thread:
> https://lists.apache.org/thread/h9g3cdok0py2vjp1pplz1wq4ofl4sbjx
>
> Changes made between previous candidate (rc3) and this one (rc4) are as 
> follows:
> - Updated SDAP to use Poetry package manager to more explicitly manage 
> dependencies and transitive dependencies. This was needed to ensure no GPL 
> license dependencies are used by the software.
> - Patch for domspurge helper script
>
> Instructions for building docker images from source can be found here:
> https://github.com/apache/incubator-sdap-nexus/blob/1.2.0-rc4/docs/build.rst
> Instructions for deploying locally to test can be found here:
> https://github.com/apache/incubator-sdap-nexus/blob/1.2.0-rc4/docs/quickstart.rst
> The release files, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/sdap/apache-sdap-1.2.0-rc4/
>
> For convenience, the tags we built the release artifacts to be voted on
> from are 1.2.0-rc4:
>
> - ingester:
> - URL: https://github.com/apache/incubator-sdap-ingester/tree/1.2.0-rc4
> - Commit: 5c116badfaf913734d017d41acc765ed3fd978a1
>
> - nexus:
> - URL: https://github.com/apache/incubator-sdap-nexus/tree/1.2.0-rc4
> - Commit: 3fce31f08b9057db446036724e8bc62dd6d1560a
>
> For verification, the hashes (SHA-512) of the .tar.gz artifacts we are voting 
> on are as follows:
>
> apache-sdap-ingester-1.2.0-incubating-src.tar.gz:
> 7301c54e765882c45f6efe4a06463b837ace62b6eea2ae5437113357466e52f1d905c3c9d46295f1b1058b9ecf5025942f8a89b2c53a1b0d6b69cd52a8890257
>
> apache-sdap-nexus-1.2.0-incubating-src.tar.gz:
> 1a2907f9c36dbf0b4b25d54c095303ab0602fa9e0a9423deceae402ffd9a360e21ba832c3ea497d8eccbc6c91fedd2926b3b33181a14c22d50d0ec996282bc75
>
> Release artifacts are signed with the following key:
> https://keyserver.ubuntu.com/pks/lookup?op=get=0x2E8418801953621FAA322169D6F360887071C194
>
> Please vote on releasing this package as Apache SDAP (incubating) 1.2.0.
>
> The vote is open for 72 hours and passes if at least 3 +1 PMC votes are cast.
>
> [ ] +1 Release this package as Apache SDAP (incubating) 1.2.0
> [ ] +0 No opinion
> [ ] -1 Do not release this package because ...
>
> Thank you,
> Stepheny
>
> -
> 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 Celeborn (Incubating) as a Top Level Project

[PJ Fanning]

+1 (binding) - Apache Celeborn seems to be in good health

On Fri, 8 Mar 2024 at 12:57, Ethan Feng  wrote:
>
> +1 (non-binding)
>
> Thanks,
> Ethan Feng
>
> Cheng Pan  于2024年3月8日周五 19:08写道：
> >
> > +1 (non-binding)
> >
> > Thanks,
> > Cheng Pan
> >
> >
> > > On Mar 8, 2024, at 19:04, Nicholas  wrote:
> > >
> > >
> > > +1(non-binding)
> > >
> > >
> > > Regards,
> > > Nicholas Jiang
> > >
> > >
> > > - Original Message -
> > > From: "Yu Li" 
> > > To: general@incubator.apache.org
> > > Sent: Fri, 8 Mar 2024 18:44:19 +0800
> > > Subject: [VOTE] Graduate Apache Celeborn (Incubating) as a Top Level 
> > > Project
> > >
> > > Hi All,
> > >
> > > We've got positive feedback on the DISCUSS thread for graduation [1],
> > > and would like to start an official VOTE thread now.
> > >
> > > Below are some facts and project highlights from the incubation phase
> > > as well as the draft resolution:
> > >
> > > - Currently, our community consists of 19 committers (including
> > > mentors) from more than 10 companies, with 13 serving as PPMC members.
> > > - So far, we have boasted 81 contributors.
> > > - Throughout the incubation period, we've made 6 releases in 16
> > > months, at a stable pace.
> > > - We've had 6 different release managers to date.
> > > - Our software is used in production by 10+ well known entities.
> > > - As yet, we have opened 1,302 issues with 1,191 successfully resolved.
> > > - We have submitted a total of 1,840 PRs, out of which 1,830 have been
> > > merged or closed.
> > > - We have met all maturity criteria as outlined in [2].
> > >
> > > Please vote on the resolution pasted below to graduate Apache Celeborn
> > > from the Incubator to the Top Level Project.
> > >
> > > [ ] +1 Graduate Apache Celeborn from the Incubator.
> > > [ ] +0 No opinion.
> > > [ ] -1 Don't graduate Apache Celeborn from the Incubator because ...
> > >
> > > This vote will open for at least 72 hours.
> > >
> > > We would like to thank everyone who have participated in the Apache
> > > Celeborn community. We 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/9gyhhnhj5osjom38v9ws1b7o7fbf7fqh
> > > [2] 
> > > https://cwiki.apache.org/confluence/display/CELEBORN/Apache+Maturity+Model+Assessment+for+Celeborn
> > >
> > > ---
> > >
> > > Establish the Apache Celeborn 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 intermediate data service for big data computing engines
> > > to boost performance, stability, and flexibility.
> > >
> > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > > (PMC), to be known as the "Apache Celeborn Project", be and hereby is
> > > established pursuant to Bylaws of the Foundation; and be it further
> > >
> > > RESOLVED, that the Apache Celeborn Project be and hereby is responsible
> > > for the creation and maintenance of software related to an intermediate
> > > data service for big data computing engines to boost performance,
> > > stability, and flexibility; and be it further
> > >
> > > RESOLVED, that the office of "Vice President, Apache Celeborn" 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 Celeborn
> > > Project, and to have primary responsibility for management of the
> > > projects within the scope of responsibility of the Apache Celeborn
> > > 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 Celeborn
> > > Project:
> > >
> > > * Becket Qin 
> > > * Cheng Pan 
> > > * Duo Zhang 
> > > * Ethan Feng 
> > > * Fu Chen 
> > > * Jiashu Xiong 
> > > * Kerwin Zhang 
> > > * Keyong Zhou 
> > > * Lidong Dai 
> > > * Willem Ning Jiang 
> > > * Wu Wei 
> > > * Yi Zhu 
> > > * Yu Li 
> > >
> > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Keyong Zhou be appointed to
> > > the office of Vice President, Apache Celeborn, 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 Celeborn Project be and hereby is tasked with
> > > the migration and rationalization of the Apache Incubator Celeborn
> > > podling; and be it further
> > >
> > > RESOLVED, that all responsibilities pertaining to the Apache Incubator
> > > 

Re: [DISCUSS] Graduate Apache Celeborn (Incubating) as a Top Level Project

[PJ Fanning]

+1 (binding)

Celeborn community looks in a good state to proceed to become a TLP.

On Thu, 7 Mar 2024 at 19:05, Lewis John McGibbney  wrote:
>
> +1
> Excellent work on the Incubating releases and community building,
> lewismc
>
> On 2024/03/05 06:00:49 Yu Li wrote:
> > Hi All,
> >
> > Apache Celeborn joined Incubator in October 2022 [1]. Since then,
> > we've made significant progress towards maturing our community and
> > adopting the Apache Way.
> >
> > After a thorough discussion [2], the community has voted [3] that we
> > would like to proceed with graduation [4]. Furthermore, we'd like to
> > 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:
> >
> > - Currently, our community consists of 19 committers (including
> > mentors) from more than 10 companies, with 13 serving as PPMC members
> > [5].
> > - So far, we have boasted 81 contributors.
> > - Throughout the incubation period, we've made 6 releases [6] in 16
> > months, at a stable pace.
> > - We've had 6 different release managers to date.
> > - Our software is used in production by 10+ well known entities [7].
> > - As yet, we have opened 1,302 issues with 1,191 successfully resolved [8].
> > - We have submitted a total of 1,840 PRs, out of which 1,830 have been
> > merged or closed [9].
> > - Through self-assessment [10], we have met all maturity criteria as
> > outlined in [11].
> >
> > We've resolved all branding issues which include Logo, GitHub repo,
> > document, website, and others [12] [13].
> >
> > We'd also like to take this opportunity to extend a sincere thank you
> > to our mentors, for their invaluable insight and assistance with
> > getting us to this point.
> >
> > Thanks a lot, Becket Qin, Duo Zhang, Lidong Dai, Willem Ning Jiang and Yu 
> > Li!
> >
> > ---
> >
> > Establish the Apache Celeborn 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 intermediate data service for big data computing engines
> > to boost performance, stability, and flexibility.
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > (PMC), to be known as the "Apache Celeborn Project", be and hereby is
> > established pursuant to Bylaws of the Foundation; and be it further
> >
> > RESOLVED, that the Apache Celeborn Project be and hereby is responsible
> > for the creation and maintenance of software related to an intermediate
> > data service for big data computing engines to boost performance,
> > stability, and flexibility; and be it further
> >
> > RESOLVED, that the office of "Vice President, Apache Celeborn" 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 Celeborn
> > Project, and to have primary responsibility for management of the
> > projects within the scope of responsibility of the Apache Celeborn
> > 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 Celeborn
> > Project:
> >
> > * Becket Qin 
> > * Cheng Pan 
> > * Duo Zhang 
> > * Ethan Feng 
> > * Fu Chen 
> > * Jiashu Xiong 
> > * Kerwin Zhang 
> > * Keyong Zhou 
> > * Lidong Dai 
> > * Willem Ning Jiang 
> > * Wu Wei 
> > * Yi Zhu 
> > * Yu Li 
> >
> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Keyong Zhou be appointed to
> > the office of Vice President, Apache Celeborn, 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 Celeborn Project be and hereby is tasked with
> > the migration and rationalization of the Apache Incubator Celeborn
> > podling; and be it further
> >
> > RESOLVED, that all responsibilities pertaining to the Apache Incubator
> > Celeborn podling encumbered upon the Apache Incubator PMC are hereafter
> > discharged.
> >
> > ---
> >
> > Best Regards,
> > Yu (on behalf of the Apache Celeborn PPMC)
> >
> > [1] https://incubator.apache.org/projects/celeborn.html
> > [2] https://lists.apache.org/thread/z17rs0mw4nyv0s112dklmv7s3j053mby
> > [3] https://lists.apache.org/thread/p1gykvxog456v5chvwmr4wk454qzmh3o
> > [4] https://lists.apache.org/thread/tqhh28q9r38czx677nh2ktc97tnlndw3
> > [5] 

Re: [DISCUSS] Incubating Proposal for StormCrawler

[PJ Fanning]

Thanks Lewis. It would be great if you can act as a menot. I will
update the proposal to add you to the mentor list.

On Thu, 7 Mar 2024 at 19:09, Lewis John McGibbney  wrote:
>
> I think StromCrawler would be an excellent candidate for the Incubator.
> If the podling is looking for an additional mentor, I would be happy to chip 
> in.
> lewismc
>
> On 2024/03/03 23:24:38 PJ Fanning wrote:
> > Hi everyone,
> >
> > I would like to propose StormCrawler [1] as a new Apache Incubator project,
> > and you can examine the proposal [2] for more details.
> >
> > StormCrawler is a collection of resources for building low-latency,
> > customisable and scalable web crawlers on Apache Storm.
> >
> > Proposal
> >
> > The aim of StormCrawler is to help build web crawlers that are:
> >
> > * scalable
> > * resilient
> > * low latency
> > * easy to extend
> > * polite yet efficient
> >
> > StormCrawler achieves this partly with Apache Storm, which it is based
> > on. To use an analogy, Apache Storm is to StormCrawler what Apache
> > Hadoop is to Apache Nutch.
> >
> > StormCrawler is mature (26 releases to date) and is used by many
> > organisations world-wide.
> >
> > Initial Committers
> >
> > Julien Nioche [jnio...@apache.org https://github.com/jnioche]
> > Sebastian Nagel [sna...@apache.org https://github.com/sebastian-nagel]
> > Richard Zowalla [r...@apache.org  https://github.com/rzo1]
> > Tim Allison [talli...@apache.org https://github.com/tballison]
> > Michael Dinzinger [michael.dinzin...@uni-passau.de
> > https://github.com/michaeldinzinger]
> >
> > Most of the existing StormCrawler contributors are existing ASF
> > committers and are looking to build a vibrant community following the
> > Apache Way.
> >
> > I will help this project as the champion and mentor. We would welcome
> > additional mentors, if anyone has an interest in helping.
> >
> > We are looking forward to your questions and feedback.
> >
> > Thanks,
> > PJ
> >
> > [1] https://github.com/DigitalPebble/storm-crawler
> > [2] 
> > https://cwiki.apache.org/confluence/display/INCUBATOR/StormCrawler+Proposal
> >
> > -
> > 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

Re: Request for Temporary Exception for LGPL Dependency in Apache KIE Podling

[PJ Fanning]

https://incubator.apache.org/policy/incubation.html#disclaimers

Have a look at the Disclaimers doc. If you use the WIP Disclaimer then you
can do releases that are not fully ASF compliant. It would be good to
document clearly about this dependency license issue.



On Tue 5 Mar 2024, 17:53 Alex Porcelli,  wrote:

> Dear Members of the Apache Incubator,
>
> I hope this email finds you well. My name is Alex Porcelli, and I am
> part of the Apache KIE podling community [1]. I am reaching out to
> discuss a matter regarding a dependency we have under LGPL, which
> falls under Category X according to Apache guidelines.
>
> The dependency is Hibernate ORM [2], the only supported JPA provider
> for Quarkus [3] - the primary runtime provider for Apache KIE podling.
>
> However, I'd like to emphasize the urgency of our situation. Our
> community has dedicated substantial effort over the past six months to
> prepare for our initial Apache release. Unfortunately, this delay in
> releasing Apache KIE is unprecedented for this community, and it is
> critical for us to deliver new releases promptly. Not only does our
> large user base eagerly anticipate a new release, but older versions
> may also pose security vulnerabilities (CVEs). Additionally, with our
> previous release process through Red Hat decommissioned, Apache now
> stands as our sole means of distribution.
>
> Given these circumstances, I kindly ask the Apache Incubator to
> consider granting us a temporary exception to maintain the LGPL
> dependency for our initial releases. We understand the importance of
> adhering to Apache licensing requirements and are willing to make
> necessary adjustments while ensuring compliance. However, we believe
> that allowing us to proceed with proper disclaimers in place would
> enable us to maintain momentum and meet the expectations of our user
> community.
>
> Furthermore, I would like to inform you that the Hibernate team is in
> the process of relicensing from LGPL to ASLv3, as indicated in their
> recent blog post [4]. This transition aligns with our long-term goals
> and demonstrates our commitment to compliance with Apache guidelines.
>
> We are open to any guidance or suggestions from the Incubator PMC on
> how best to proceed.
>
> Thank you for considering our request.
>
> Best regards,
> Alex Porcelli
> Apache KIE Podling Community Member
>
> [1] - Apache KIE: https://kie.apache.org/
> [2] - Hibernate ORM: https://hibernate.org/orm/
> [3] - Quarkus: https://quarkus.io/
> [4] - Blog post on relicensing: https://in.relation.to/2023/11/18/license/
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

[DISCUSS] Incubating Proposal for StormCrawler

[PJ Fanning]

Hi everyone,

I would like to propose StormCrawler [1] as a new Apache Incubator project,
and you can examine the proposal [2] for more details.

StormCrawler is a collection of resources for building low-latency,
customisable and scalable web crawlers on Apache Storm.

Proposal

The aim of StormCrawler is to help build web crawlers that are:

* scalable
* resilient
* low latency
* easy to extend
* polite yet efficient

StormCrawler achieves this partly with Apache Storm, which it is based
on. To use an analogy, Apache Storm is to StormCrawler what Apache
Hadoop is to Apache Nutch.

StormCrawler is mature (26 releases to date) and is used by many
organisations world-wide.

Initial Committers

Julien Nioche [jnio...@apache.org https://github.com/jnioche]
Sebastian Nagel [sna...@apache.org https://github.com/sebastian-nagel]
Richard Zowalla [r...@apache.org  https://github.com/rzo1]
Tim Allison [talli...@apache.org https://github.com/tballison]
Michael Dinzinger [michael.dinzin...@uni-passau.de
https://github.com/michaeldinzinger]

Most of the existing StormCrawler contributors are existing ASF
committers and are looking to build a vibrant community following the
Apache Way.

I will help this project as the champion and mentor. We would welcome
additional mentors, if anyone has an interest in helping.

We are looking forward to your questions and feedback.

Thanks,
PJ

[1] https://github.com/DigitalPebble/storm-crawler
[2] https://cwiki.apache.org/confluence/display/INCUBATOR/StormCrawler+Proposal

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [RESULT] [VOTE] Graduate Apache Pekko (incubating) as a TLP

[PJ Fanning]

Andrea Cosentino voted just as I was preparing the vote result so the
result is 17 +1s, 14 binding.

Thanks again to everyone for your involvement.


On Sun, 3 Mar 2024 at 13:29, PJ Fanning  wrote:
>
> The vote [1] has passed with 16 +1s, 13 binding.
>
> Binding
> Ayush Saxena
> Ryan Skraba
> Craig Russell
> Zili Chen (tison)
> Willem Jiang
> Sheng Wu
> Matthew de Detrich
> Justin Mclean
> Paul King
> Yu Xiao
> Yu Li
> Jean-Baptiste Onofré
> PJ Fanning
>
> Non-Binding
> Cheng Pan
> Xuanwo
> Suyan
>
>
>
> Thanks to everyone for participating in the vote. Thanks to the
> Incubator, the Pekko community, our mentors, and everyone who helped
> throughout the journey. We will proceed and submit the graduation
> proposal to the ASF board.
>
> [1] https://lists.apache.org/thread/dfmym4fgpwyvztk30jd7f5ffsko91v8p

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[RESULT] [VOTE] Graduate Apache Pekko (incubating) as a TLP

[PJ Fanning]

The vote [1] has passed with 16 +1s, 13 binding.

Binding
Ayush Saxena
Ryan Skraba
Craig Russell
Zili Chen (tison)
Willem Jiang
Sheng Wu
Matthew de Detrich
Justin Mclean
Paul King
Yu Xiao
Yu Li
Jean-Baptiste Onofré
PJ Fanning

Non-Binding
Cheng Pan
Xuanwo
Suyan



Thanks to everyone for participating in the vote. Thanks to the
Incubator, the Pekko community, our mentors, and everyone who helped
throughout the journey. We will proceed and submit the graduation
proposal to the ASF board.

[1] https://lists.apache.org/thread/dfmym4fgpwyvztk30jd7f5ffsko91v8p

-
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

[PJ Fanning]

I'm going to add my +1 (binding) and announce the vote result.


On 2024/03/01 15:44:53 Jean-Baptiste Onofré wrote:
> +1 (binding)
> 
> nit: I still think there are some pre-existing code to improve
> (existing at donation time), but it can be done once TLP
> 
> Regards
> JB
> 
> On Mon, Feb 26, 2024 at 12:24 PM 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 Vollmar (nvollmar)
> > Samuele Resca (samueler)
> > Sean Glover (seanglover)
> >
> > NOW, THEREFORE, BE IT FURTHER RESOLVED, tha

Re: [VOTE] Have Amoro join the Incubator

[PJ Fanning]

+1 (binding)

On 2024/03/03 07:08:53 Imba Jin wrote:
> +1 (non-binding)
> 
> Good luck~
> 
> On 2024/03/03 01:44:24 Justin Mclean wrote:
> > Hi,
> > 
> > Following on from the discussion of the Amoro proposal [1][2], let's vote 
> > on having it join the Incubator.
> > 
> > Please cast your vote:
> > 
> > [ ] +1, have it join the Incubator as an incubating project
> > [ ] +0, I have no strong opinion either way
> > [ ] -1, do not have it join the Incubator because...
> > 
> > Kind Regards,
> > Justin
> > 
> > 1. https://cwiki.apache.org/confluence/display/INCUBATOR/AmoroProposal
> > 2. https://lists.apache.org/thread/7t2bm6x19zq2d79cn8jj2wqd3f2t3k00
> 
> -
> 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: Access to Incubator Wiki

[PJ Fanning]

Hi Mirko,
Have you tried your Apache login?

On Sat, 2 Mar 2024 at 17:53, Mirko Kämpf  wrote:
>
> Hey,
>
> I want to contribute to the Apache Incubator Wiki.
> The podling report for Apache Training is on the way, but I still miss the
> right
> permissions to add it to the official report page.
>
> It is added already to the Apache Training Wiki page.
>
> I would like to apply for the write permissions for the Apache Incubator
> Wiki
> for my account *kamir (mirko.kae...@gmail.com )*.
>
> Many thanks.
> Have a great weekend.
> Cheers,
> Mirko
>
>
>
> --
>
> Dr. rer. nat. Mirko Kämpf
> Müchelner Str. 23
> 06259 Frankleben

-
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?

[PJ Fanning]

+1 binding
Formalises what most podlings are doing anyway.

On Wed 28 Feb 2024, 16:13 Alex Porcelli,  wrote:

> +1 (non-binding)
>
> On Wed, Feb 28, 2024 at 10:01 AM Suyan  wrote:
> >
> > +1 non-binding
> >
> > This looks a little more concise.
> >
> > Sincerely,
> > Suyan
> >
> > 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
> > >
> >
> > -
> > 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 Pekko (incubating) as a TLP

[PJ Fanning]

Thanks for pointing those link issues out. I have corrected them using:

https://github.com/apache/incubator-pekko-site/pull/90

On Wed, 28 Feb 2024 at 11:14, sebb  wrote:
>
> I've noticed another issue: the download page links to dist.apache.org
> for the KEYS file.
> It must link to downloads.apache.org.
>
> Also the sigs and hashes link to dlcdn.apache.org.
> The canonical place for these is currently downloads.apache.org
>
> https://infra.apache.org/release-download-pages.html#links
>
> On Tue, 27 Feb 2024 at 22:56, sebb  wrote:
> >
> > 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 tha

Re: [VOTE] Graduate Apache Pekko (incubating) as a TLP

[PJ Fanning]

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
> > > >

Re: [VOTE] Graduate Apache Pekko (incubating) as a TLP

[PJ Fanning]

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 ...
&

Re: [VOTE] Graduate Apache Pekko (incubating) as a TLP

[PJ Fanning]

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 (jmc

[VOTE] Graduate Apache Pekko (incubating) as a TLP

[PJ Fanning]

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

RE: Re: [DISCUSS] Apache Amoro proposal

[PJ Fanning]

+1. Looks like a good candidate with a good number of contributors already.

On 2024/02/24 05:24:33 nathan ma wrote:
> hi, JB
> 
> As co-creator of this project, I’d love to explain more about the
> positioning of lakehouse management system.
> 
> When discussing databases or traditional data warehouses, we often used the
> term DBMS (Database Management System) to describe them. Traditional
> databases, including MPP databases, are typically considered “out-of-box”
> solutions. Unlike big data systems, they don’t require various components
> like compute engines, data lake formats, or metadata stores. When we need a
> database management tool, lightweight options like Navicat are commonly
> used.
> 
> If we further abstract the capabilities of a DBMS and map them to the
> modern data stack, we find that the data read/write part of a DBMS is now
> shared among different compute engines such as Spark, Flink, Trino, and
> cloud-native services like Athena. Another part of a DBMS deals with data
> files, index files, and metadata (also known as the information schema)
> maintenance. Currently, there are successful open-source and commercial
> projects dedicated to managing metadata, such as HiveMetastore,
> UnityCatalog, and more recently, Gravitino. In practice, developers often
> combine these projects with compute engines to optimize data files. For
> example, many commercial compute engines include an optimize command.
> 
> Amoro, as a lakehouse management system, aims to encapsulate the
> maintenance and management of data lake files, index files, and metadata in
> a way that is transparent and easy-to-use for users. The richness of
> diverse computing engines is a distinctive feature of the modern data
> stack, opening up a multitude of possibilities for various application
> scenarios. Additionally, concerning the part analogous to DBMS, we aspire
> to have a mature system in place—one that seamlessly accommodates data
> written to the lakehouse by any engine, in any manner, ensuring high data
> availability across all other engines. For instance, when Flink writes to
> Iceberg, Amoro’s self-optimizing mechanism ensures efficient data analysis
> performance by Trino or other engines while controlling compacting costs.
> Additionally, Amoro handles historical data, snapshots, and orphan file
> cleanup in the background.
> 
> By positioning Amoro in this way, we aim to provide an ‘out-of-box’
> experience that feels as straightforward as traditional DBMS while keeping
> openness to various computing engines. At the same time, Amoro hopes to
> empower data product builders with a lightweight solution that integrates
> seamlessly into their modern data workflows.
> 
> 
> 
> Thanks.
> Jin Ma
> 
> 
> On 2024/02/23 14:16:43 Jean-Baptiste Onofré wrote:
> > Hi Justin
> >
> > Even if it looks interesting, I'm not sure to understand exactly the
> > purpose of the proposal.
> >
> > What lakehouse management system means exactly ? Is it an abstraction
> > layer on top of Iceberg, Paimon + query engine powered by Flink,
> > Spark, Trino ?
> >
> > Please let me know if you want an additional mentor, I would be happy to
> help.
> >
> > Thanks !
> > Regards
> > JB
> >
> > On Fri, Feb 23, 2024 at 9:44 AM Justin Mclean 
> wrote:
> > >
> > > Hi,
> > >
> > > I would like to propose a new project to the ASF incubator - Apache
> Amoro. I’m one of the mentors, but there are a lot of other people involved
> who have done all of the hard work.
> > >
> > > Amoro is a Lakehouse management system built on open data lake formats
> like Apache Iceberg and Apache Paimon (Incubating). Working with compute
> engines including Apache Flink, Apache Spark, and Trino, Amoro brings
> pluggable and self-managed features for Lakehouse to provide out-of-the-box
> data warehouse experience, and helps data platforms or products easily
> build infra-decoupled, stream-and-batch-fused and lake-native architecture.
> You can find the proposal here. [1]
> > >
> > > We are looking forward to anyone's feedback or questions.
> > >
> > > Thanks,
> > > Justin
> > >
> > > [1] https://cwiki.apache.org/confluence/display/INCUBATOR/AmoroProposal
> > > -
> > > 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

Re: [DISCUSS] Graduate Apache SDAP (Incubating) as a Top Level Project

[PJ Fanning]

+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 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 SDAP Project be and hereby is tasked with
> the migration and rationalization of the Apache Incubator SDAP
> podling; and be it further
> 
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> SDAP podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.
> 
> [1] https://lists.apache.org/thread/vjwjmp0h2f22dv423h262cvdg5x7jl03
> [2] https://lists.apache.org/thread/m9vqwv23jdsofwgmhgxg25f5l1v2j7nz
> [3] https://lists.apache.org/thread/4o1qjsk2cly2ppxcsmm2swzd6pcg3lxj
> [4] https://lists.apache.org/thread/qtxlxl4gj6n33wvm164vdxxnwdlppttl
> [5] https://lists.apache.org/thread/rr74c35fojc7ythmcgnoplyjllhbslj4
> [6] 

Re: [VOTE] Release Apache Pekko(Incubating) HTTP 1.0.3-M1-RC1

[PJ Fanning]

Carrying over my +1 (binding) from the Pekko PPMC vote.

On Mon, 19 Feb 2024 at 22:54, Arnout Engelen  wrote:
>
> Hello Incubator Community,
>
> This is a call for a vote to release Apache Pekko(incubating) version
> 1.0.3-M1-RC1.
>
> The discussion thread:
>
> https://lists.apache.org/thread/4cm4xmqz5t3l5p8qfvm72rzv58jj3rym
>
> The Pekko vote thread:
>
> https://lists.apache.org/thread/lcpdv1w27f8vsqq4cp93dgxvtm8zjcdm
>
> The Pekko vote result:
>
> https://lists.apache.org/thread/0n1d7ohbmrmm0x6nbng9pv7zn6ws1t94
>
> The release candidate:
>
> https://dist.apache.org/repos/dist/dev/incubator/pekko/1.0.3-M1-RC1/
>
> This release has been signed with a PGP key, available here:
>
> https://dist.apache.org/repos/dist/release/incubator/pekko/KEYS
>
> Release Notes:
>
> https://github.com/apache/incubator-pekko/blob/v1.0.3-M1-RC1/docs/src/main/paradox/release-notes/index.md#103-m1
>
> Git tag for the release:
>
> https://github.com/apache/incubator-pekko/tree/v1.0.3-M1-RC1
> Git commit ID: 7bdd230acc228ba0e99fe027165af1cf5451ffc8
>
> Please download, verify, and test.
>
> We have also staged jars in the Apache Nexus Repository. These were
> built with the same code as appears in this Source Release Candidate. We
> would appreciate if users could test with these too.
> If anyone finds any serious problems with these jars, please also notify us
> on this thread.
>
> https://repository.apache.org/content/groups/staging/org/apache/pekko/
>
> In sbt, you can add this resolver.
>
> resolvers += "Apache Pekko Staging" at "
> https://repository.apache.org/content/groups/staging;
>
> The vote will be left open for at least 72 hours.
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> To learn more about Apache Pekko, please see https://pekko.apache.org/
>
> Checklist for reference:
>
> [ ] Download links are valid.
> [ ] Checksums and signatures.
> [ ] LICENSE/NOTICE files exist
> [ ] No unexpected binary files
> [ ] Source files have ASF headers
> [ ] Can compile from source
>
> To compile from the source, please refer to:
>
> https://github.com/apache/incubator-pekko-http/blob/main/README.md#building-from-source
>
> Some notes about verifying downloads can be found at:
>
> https://pekko.apache.org/download.html#verifying-downloads
>
>
> Here is my +1 (non-binding).
>
> Thanks,
> Arnout Engelen (Apache Pekko PPMC member)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: ASF at Jetbrains

[PJ Fanning]

Hi Lukasz,

Could you raise an INFRA JIRA to transfer the GitHub repo?

An alternative is to create a new ASF git repo and copy the history
from an existing repo. You can create the new repo using
https://selfserve.apache.org/

And GitHub provides the tooling for copying git history from an
existing repo into an empty repo.

Regards,
PJ

On Mon, 19 Feb 2024 at 17:36, Lukasz Lenart  wrote:
>
> Hi,
>
> The Apache Struts team took over the IntelliJ IDEA Struts 2 plugin
> ownership - the code has been donated by the Jetbrains (the papers
> have been signed and already confirmed by the secretary). Right now
> they would like to transfer ownership of the plugin's page as well and
> they ask if ASF owns an organization at https://plugins.jetbrains.com/
> already. Could you help?
>
> > We also would like to transfer plugin page ownership for 
> > https://plugins.jetbrains.com/plugin/1698-struts-2
> > Does ASF have an organization on https://plugins.jetbrains.com/ ?
> > Please let us know the organization ID and we will arrange the transfer of 
> > the plugin page.
>
>
> Thanks in advance
> Łukasz
> Struts PMC
>
> -
> 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

[ANNOUNCE] Apache Pekko (Incubating) HTTP 1.0.1 available

[PJ Fanning]

Hi everyone,

The Apache Pekko (Incubating) Team is happy to announce the release of
Apache Pekko (Incubating) HTTP 1.0.1.

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.

Download Links:
https://pekko.apache.org/download.html#pekko-http

Release Notes:
https://pekko.apache.org/docs/pekko-http/1.0/release-notes/index.html

Website:
https://pekko.apache.org/

Issues:
https://github.com/apache/incubator-pekko-http/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

===

*Disclaimer*

Apache Pekko (incubating) is an effort undergoing incubation at The
Apache Software Foundation (ASF), sponsored by the Apache Incubator.
Incubation is required of all newly accepted projects until a further
review indicates that the infrastructure, communications, and decision
making process have stabilized in a manner consistent with other
successful ASF projects. While incubation status is not necessarily a
reflection of the completeness or stability of the code, it does
indicate that the project has yet to be fully endorsed by the ASF.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[RESULT] [VOTE] Release Apache Pekko(Incubating) HTTP 1.0.1-RC2

[PJ Fanning]

The vote passes with 6 +1s and no negative votes. There were 4 binding +1s.

Vote Thread
https://lists.apache.org/thread/13gwlvob37mnjpl0qwkcylz6qc32mz9n

Votes
Suyan
Xuanwo
Tison (binding)
Ayush Saxena (binding)
Matthew de Detrich (binding)
PJ Fanning (binding)

Thanks to everyone who participated in the development and review. I
will proceed with the release.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Pekko(Incubating) HTTP 1.0.1-RC2

[PJ Fanning]

Hi everyone,

We are still short on binding votes to release this. Would any of the Pekko 
mentors or any other IPMC member have time to review this?

This release contains a security hardening option related to the HTTP/2 Rapid 
Reset issue.

Thanks,
PJ

On 2024/01/31 17:45:16 Xuanwo wrote:
> Hi, PJ Fanning
> 
> Thanks for the explaination.
> 
> > I will post something on the Pekko Dec
> > mailing list seeking volunteers. We have 2 more releases under discussion
> > and some more that we could be looking at.
> 
> Thanks for the effort!
> 
> > The release guide is at
> > https://github.com/apache/incubator-pekko-site/wiki/Pekko-HTTP-Release
> 
> I created a PR[1] for adding links to "How to Contribute". I hope it can be 
> helpful for future reference.
> 
> [1] https://github.com/apache/incubator-pekko-site/pull/83
> 
> On Wed, Jan 31, 2024, at 23:19, PJ Fanning wrote:
> > Thanks Xuanwo for the review and comments. I agree that we need to get more
> > people involved in the releases. I will post something on the Pekko Dec
> > mailing list seeking volunteers. We have 2 more releases under discussion
> > and some more that we could be looking at.
> >
> > The release guide is at
> > https://github.com/apache/incubator-pekko-site/wiki/Pekko-HTTP-Release
> >
> > This page is a few comments that highlight diffs from the main release
> > guide linked on that page.
> >
> >
> > On Wed 31 Jan 2024, 15:35 Xuanwo,  wrote:
> >
> >> Hi, PJ Fanning
> >>
> >> Before starting my check, I noticed that almost all releases are handled
> >> by you
> >> (please correct me if I'm mistaken). Additionally, I observed that
> >> pekko.apache.org
> >> does not currently have a release guide. I would like to inquire whether
> >> it is
> >> possible to involve other PPMC members in the release process. I believe
> >> it is
> >> important to have multiple release managers.
> >>
> >> Here is my checks and vote.
> >>
> >> +1 non-binding
> >>
> >> [x] Download links are valid.
> >> [x] Checksums and signatures.
> >>
> >> apache-pekko-http-1.0.1-incubating-src-20240128.tgz
> >> gpg: Signature made Sun 28 Jan 2024 08:45:20 PM CST
> >> gpg:using RSA key 6BA4DA8B1C88A49428A29C3D0C69C1EF41181E13
> >> gpg: Good signature from "PJ Fanning (GitHub noreply address) <
> >> pjfann...@users.noreply.github.com>" [ultimate]
> >> gpg: aka "PJ Fanning " [ultimate]
> >> gpg: aka "PJ Fanning (http://www.apache.org/) <
> >> fannin...@apache.org>" [ultimate]
> >>
> >> [x] LICENSE/NOTICE files exist
> >> [x] No unexpected binary files
> >> [x] Source files have ASF headers
> >> [x] Can compile from source
> >>
> >> Build passed on archlinux x86_64
> >>
> >> [info] compiling 14 Scala sources to
> >> /tmp/HTTP-1.0.1-RC2/apache-pekko-http-1.0.1-incubating-src-20240128/http-bench-jmh/target/scala-2.13/classes
> >> ...
> >> [success] Total time: 61 s (01:01), completed Jan 31, 2024 10:28:40 PM
> >> sbt compile  318.89s user 6.99s system 308% cpu 1:45.50 total
> >>
> >> On Wed, Jan 31, 2024, at 21:23, PJ Fanning wrote:
> >> > Hello Incubator Community,
> >> >
> >> > This is a call for a vote to release Apache Pekko(incubating) HTTP
> >> > version 1.0.1-RC2.
> >> >
> >> > The discussion thread:
> >> >
> >> > https://lists.apache.org/thread/c8vrl4cfgjzrfckxxbc1rt60cxocfy66
> >> >
> >> > The Pekko vote thread:
> >> >
> >> > https://lists.apache.org/thread/psspc2sqn7nqjomk26dc6zzp18h43q81
> >> >
> >> > The Pekko vote result:
> >> >
> >> > https://lists.apache.org/thread/rjh6flb5q5fnyd4y7f87bzt4l3ywzt0t
> >> >
> >> > The release candidate:
> >> >
> >> > https://dist.apache.org/repos/dist/dev/incubator/pekko/HTTP-1.0.1-RC2/
> >> >
> >> > This release has been signed with a PGP key, available here:
> >> >
> >> > https://dist.apache.org/repos/dist/release/incubator/pekko/KEYS
> >> >
> >> > Release Notes:
> >> >
> >> > https://github.com/apache/incubator-pekko-http/pull/442/files
> >> >
> >> > Git branch for the release:
> >> >
> >> > https://github.com

Re: [VOTE] Release Apache Pekko(Incubating) HTTP 1.0.1-RC2

[PJ Fanning]

Thanks Xuanwo for the review and comments. I agree that we need to get more
people involved in the releases. I will post something on the Pekko Dec
mailing list seeking volunteers. We have 2 more releases under discussion
and some more that we could be looking at.

The release guide is at
https://github.com/apache/incubator-pekko-site/wiki/Pekko-HTTP-Release

This page is a few comments that highlight diffs from the main release
guide linked on that page.


On Wed 31 Jan 2024, 15:35 Xuanwo,  wrote:

> Hi, PJ Fanning
>
> Before starting my check, I noticed that almost all releases are handled
> by you
> (please correct me if I'm mistaken). Additionally, I observed that
> pekko.apache.org
> does not currently have a release guide. I would like to inquire whether
> it is
> possible to involve other PPMC members in the release process. I believe
> it is
> important to have multiple release managers.
>
> Here is my checks and vote.
>
> +1 non-binding
>
> [x] Download links are valid.
> [x] Checksums and signatures.
>
> apache-pekko-http-1.0.1-incubating-src-20240128.tgz
> gpg: Signature made Sun 28 Jan 2024 08:45:20 PM CST
> gpg:using RSA key 6BA4DA8B1C88A49428A29C3D0C69C1EF41181E13
> gpg: Good signature from "PJ Fanning (GitHub noreply address) <
> pjfann...@users.noreply.github.com>" [ultimate]
> gpg: aka "PJ Fanning " [ultimate]
> gpg: aka "PJ Fanning (http://www.apache.org/) <
> fannin...@apache.org>" [ultimate]
>
> [x] LICENSE/NOTICE files exist
> [x] No unexpected binary files
> [x] Source files have ASF headers
> [x] Can compile from source
>
> Build passed on archlinux x86_64
>
> [info] compiling 14 Scala sources to
> /tmp/HTTP-1.0.1-RC2/apache-pekko-http-1.0.1-incubating-src-20240128/http-bench-jmh/target/scala-2.13/classes
> ...
> [success] Total time: 61 s (01:01), completed Jan 31, 2024 10:28:40 PM
> sbt compile  318.89s user 6.99s system 308% cpu 1:45.50 total
>
> On Wed, Jan 31, 2024, at 21:23, PJ Fanning wrote:
> > Hello Incubator Community,
> >
> > This is a call for a vote to release Apache Pekko(incubating) HTTP
> > version 1.0.1-RC2.
> >
> > The discussion thread:
> >
> > https://lists.apache.org/thread/c8vrl4cfgjzrfckxxbc1rt60cxocfy66
> >
> > The Pekko vote thread:
> >
> > https://lists.apache.org/thread/psspc2sqn7nqjomk26dc6zzp18h43q81
> >
> > The Pekko vote result:
> >
> > https://lists.apache.org/thread/rjh6flb5q5fnyd4y7f87bzt4l3ywzt0t
> >
> > The release candidate:
> >
> > https://dist.apache.org/repos/dist/dev/incubator/pekko/HTTP-1.0.1-RC2/
> >
> > This release has been signed with a PGP key, available here:
> >
> > https://dist.apache.org/repos/dist/release/incubator/pekko/KEYS
> >
> > Release Notes:
> >
> > https://github.com/apache/incubator-pekko-http/pull/442/files
> >
> > Git branch for the release:
> >
> > https://github.com/apache/incubator-pekko-http/tree/v1.0.1-RC2 Git
> > commit ID: c231269c72f4a95e28bada1bbcddc0cf396ee17a
> >
> > Please download, verify, and test.
> >
> > We have also staged jars in the Apache Nexus Repository. These were
> > built with the same code as appears in this Source Release Candidate.
> > We would appreciate if users could test with these too. If anyone
> > finds any serious problems with these jars, please also notify us on
> > this thread.
> >
> > https://repository.apache.org/content/groups/staging/org/apache/pekko/
> >
> > In sbt, you can add this resolver.
> >
> > resolvers += "Apache Pekko Staging" at "
> > https://repository.apache.org/content/groups/staging;
> >
> >
> > The vote will be left open for at least 72 hours.
> >
> > [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove with the reason
> >
> > To learn more about Apache Pekko, please see https://pekko.apache.org/
> >
> > Checklist for reference:
> >
> > [ ] Download links are valid. [ ] Checksums and signatures. [ ]
> > LICENSE/NOTICE files exist [ ] No unexpected binary files [ ] Source
> > files have ASF headers [ ] Can compile from source
> >
> > To compile from the source, please refer to:
> >
> >
> https://github.com/apache/incubator-pekko-http/blob/main/README.md#building-from-source
> >
> > Some notes about verifying downloads can be found at:
> >
> > https://pekko.apache.org/download.html#verifying-downloads
> >
> >
> > Here is my +1 (binding).
> >
> > Thanks, PJ Fanning (Apache Pekko PPMC member)
> >
> > -
> > 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
>
>

[VOTE] Release Apache Pekko(Incubating) HTTP 1.0.1-RC2

[PJ Fanning]

Hello Incubator Community,

This is a call for a vote to release Apache Pekko(incubating)
HTTP version 1.0.1-RC2.

The discussion thread:

https://lists.apache.org/thread/c8vrl4cfgjzrfckxxbc1rt60cxocfy66

The Pekko vote thread:

https://lists.apache.org/thread/psspc2sqn7nqjomk26dc6zzp18h43q81

The Pekko vote result:

https://lists.apache.org/thread/rjh6flb5q5fnyd4y7f87bzt4l3ywzt0t

The release candidate:

https://dist.apache.org/repos/dist/dev/incubator/pekko/HTTP-1.0.1-RC2/

This release has been signed with a PGP key, available here:

https://dist.apache.org/repos/dist/release/incubator/pekko/KEYS

Release Notes:

https://github.com/apache/incubator-pekko-http/pull/442/files

Git branch for the release:

https://github.com/apache/incubator-pekko-http/tree/v1.0.1-RC2
Git commit ID: c231269c72f4a95e28bada1bbcddc0cf396ee17a

Please download, verify, and test.

We have also staged jars in the Apache Nexus Repository. These were
built with the same code
as appears in this Source Release Candidate. We would appreciate if
users could test with these too.
If anyone finds any serious problems with these jars, please also
notify us on this thread.

https://repository.apache.org/content/groups/staging/org/apache/pekko/

In sbt, you can add this resolver.

resolvers += "Apache Pekko Staging" at
"https://repository.apache.org/content/groups/staging;


The vote will be left open for at least 72 hours.

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove with the reason

To learn more about Apache Pekko, please see https://pekko.apache.org/

Checklist for reference:

[ ] Download links are valid.
[ ] Checksums and signatures.
[ ] LICENSE/NOTICE files exist
[ ] No unexpected binary files
[ ] Source files have ASF headers
[ ] Can compile from source

To compile from the source, please refer to:

https://github.com/apache/incubator-pekko-http/blob/main/README.md#building-from-source

Some notes about verifying downloads can be found at:

https://pekko.apache.org/download.html#verifying-downloads


Here is my +1 (binding).

Thanks,
PJ Fanning (Apache Pekko PPMC member)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[ANNOUNCE] Apache Pekko (Incubating) Connectors 1.0.2 available

[PJ Fanning]

Hi everyone,

The Apache Pekko (Incubating) Team is happy to announce the release of
Apache Pekko (Incubating) Connectors 1.0.2.

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.

Download Links:
https://pekko.apache.org/download.html#pekko-connectors

Release Notes:
https://pekko.apache.org/docs/pekko-connectors/current/release-notes/index.html

Website:
https://pekko.apache.org/

Issues:
https://github.com/apache/incubator-pekko-connectors/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

===

*Disclaimer*

Apache Pekko (incubating) is an effort undergoing incubation at The
Apache Software Foundation (ASF), sponsored by the Apache Incubator.
Incubation is required of all newly accepted projects until a further
review indicates that the infrastructure, communications, and decision
making process have stabilized in a manner consistent with other
successful ASF projects. While incubation status is not necessarily a
reflection of the completeness or stability of the code, it does
indicate that the project has yet to be fully endorsed by the ASF.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[RESULT] [VOTE] Release Apache Pekko(incubating) Connectors 1.0.2-RC1

[PJ Fanning]

The vote passes with 5 +1s and no negative votes. 3 of the +1s were binding.

Vote Thread
https://lists.apache.org/thread/7j7v0r4rd2v8nyzrrmmkljkst5ymdsys

Votes
Xuanwo (non-binding)
Suyan (non-binding)
Tison (binding)
Matthew de Detrich (binding)
PJ Fanning (binding)

I will proceed with the release and announcements. Thanks to everyone
who participated in the release.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Pekko(incubating) Connectors 1.0.2-RC1 Inbox

[PJ Fanning]

Thanks Tison,

The files with the license header that mentions Akka is put on files
that are derived from Akka. The standard ASF header is put on new
files.

https://issues.apache.org/jira/browse/LEGAL-626 gives the background
to the Akka header.


On Thu, 25 Jan 2024 at 10:46, tison  wrote:
>
> +1 binding
>
> + Download link valid
> + Checksum and signature match
> + LICENSE, NOTICE and DISCLAIMER exist
> + Can build from source with: sbt compile
>
> Find some binary files for testing in the release. While I don't think
> it's a release blocker, you may try to generate it on the fly:
>
> ./s3/src/test/resources/keystore.jks
> ./google-cloud-pub-sub-grpc/src/main/resources/GSR2.crt
> ./file/src/test/resources/nested-sample.tar
>
> Also, I find the license header is something the ASF "standard" one,
> but otherwise:
>
> > Licensed to the Apache Software Foundation (ASF) under one or more
> > license agreements; and to You under the Apache License, version 2.0:
> >
> >   https://www.apache.org/licenses/LICENSE-2.0
> >
> > This file is part of the Apache Pekko project, which was derived from Akka.
>
> Is there any reason for different styles? How do you check that the
> license headers are properly included?
>
> Best,
> tison.
>
> PJ Fanning  于2024年1月25日周四 17:05写道：
> >
> > Hi everyone,
> >
> > We still need 1 more binding vote on this vote before we can proceed with a 
> > release.
> >
> > Would anyone have time to review this RC? It includes a few bug fixes that 
> > would be good to get released.
> >
> > Thanks,
> > PJ
> >
> > On 2024/01/21 12:01:08 PJ Fanning wrote:
> > > Thanks Xuanwo. I have created PRs to update our NOTICE files.
> > >
> > > On 2024/01/21 08:53:47 Xuanwo wrote:
> > > > +1 non-binding
> > > >
> > > > [x] Download links are valid.
> > > > [x] Checksums and signatures.
> > > >
> > > > apache-pekko-connectors-1.0.2-incubating-src-20240109.tgz
> > > > gpg: Signature made Tue 09 Jan 2024 08:45:04 PM CST
> > > > gpg:using RSA key 
> > > > 6BA4DA8B1C88A49428A29C3D0C69C1EF41181E13
> > > > gpg: checking the trustdb
> > > > gpg: marginals needed: 3  completes needed: 1  trust model: pgp
> > > > gpg: depth: 0  valid:  16  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 16u
> > > > gpg: next trustdb check due at 2024-05-25
> > > > gpg: Good signature from "PJ Fanning (GitHub noreply address) 
> > > > " [ultimate]
> > > > gpg: aka "PJ Fanning " [ultimate]
> > > > gpg: aka "PJ Fanning (http://www.apache.org/) 
> > > > " [ultimate]
> > > >
> > > > [x] LICENSE/NOTICE/DISCLAIMER files exist
> > > >
> > > > nit: The NOTICE file seems not mention that Pekko is an incubating 
> > > > project.
> > > >
> > > > [x] No unexpected binary files
> > > > [x] Source files have ASF headers
> > > > [x] Can compile from source
> > > >
> > > > [success] Total time: 239 s (03:59), completed Jan 21, 2024, 4:53:04 PM
> > > > sbt compile  459.14s user 14.09s system 154% cpu 5:05.48 total
> > > >
> > > > Build success on archlinux x86_64
> > > >
> > > > BTW, sbt is much faster than mvn!
> > > >
> > > > On Sat, Jan 13, 2024, at 03:20, PJ Fanning wrote:
> > > > > Hello Incubator Community,
> > > > >
> > > > > This is a call for a vote to release Apache Pekko(incubating)
> > > > > Connectors version 1.0.2-RC1.
> > > > >
> > > > > The discussion thread:
> > > > > https://lists.apache.org/thread/31tvbff0j880v3kvpmdq3st32dkynvnb
> > > > >
> > > > > Pekko PPMC Vote Thread
> > > > > https://lists.apache.org/thread/nosrvwphtwmcg7dw9pz6y1qbtm3zhgpn
> > > > >
> > > > > Pekko PPMC Vote Result
> > > > > https://lists.apache.org/thread/n27jqcy4160981lhdr01ljqs0c31nshh
> > > > >
> > > > > The release candidate:
> > > > >
> > > > > https://dist.apache.org/repos/dist/dev/incubator/pekko/CONNECTORS-1.0.2-RC1/
> > > > >
> > > > > This release has been signed with a PGP key, available here:
> > > > >
> > > > > https://dist.apache.org/repos/dist/release/incubator/pekko/KEYS
> > > > >
> > >

Re: [VOTE] Release Apache Pekko(incubating) Connectors 1.0.2-RC1 Inbox

[PJ Fanning]

Hi everyone,

We still need 1 more binding vote on this vote before we can proceed with a 
release.

Would anyone have time to review this RC? It includes a few bug fixes that 
would be good to get released.

Thanks,
PJ

On 2024/01/21 12:01:08 PJ Fanning wrote:
> Thanks Xuanwo. I have created PRs to update our NOTICE files.
> 
> On 2024/01/21 08:53:47 Xuanwo wrote:
> > +1 non-binding
> > 
> > [x] Download links are valid.
> > [x] Checksums and signatures.
> > 
> > apache-pekko-connectors-1.0.2-incubating-src-20240109.tgz
> > gpg: Signature made Tue 09 Jan 2024 08:45:04 PM CST
> > gpg:using RSA key 6BA4DA8B1C88A49428A29C3D0C69C1EF41181E13
> > gpg: checking the trustdb
> > gpg: marginals needed: 3  completes needed: 1  trust model: pgp
> > gpg: depth: 0  valid:  16  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 16u
> > gpg: next trustdb check due at 2024-05-25
> > gpg: Good signature from "PJ Fanning (GitHub noreply address) 
> > " [ultimate]
> > gpg: aka "PJ Fanning " [ultimate]
> > gpg: aka "PJ Fanning (http://www.apache.org/) 
> > " [ultimate]
> > 
> > [x] LICENSE/NOTICE/DISCLAIMER files exist
> > 
> > nit: The NOTICE file seems not mention that Pekko is an incubating project.
> > 
> > [x] No unexpected binary files
> > [x] Source files have ASF headers
> > [x] Can compile from source
> > 
> > [success] Total time: 239 s (03:59), completed Jan 21, 2024, 4:53:04 PM
> > sbt compile  459.14s user 14.09s system 154% cpu 5:05.48 total
> > 
> > Build success on archlinux x86_64
> > 
> > BTW, sbt is much faster than mvn!
> > 
> > On Sat, Jan 13, 2024, at 03:20, PJ Fanning wrote:
> > > Hello Incubator Community,
> > >
> > > This is a call for a vote to release Apache Pekko(incubating)
> > > Connectors version 1.0.2-RC1.
> > >
> > > The discussion thread:
> > > https://lists.apache.org/thread/31tvbff0j880v3kvpmdq3st32dkynvnb
> > >
> > > Pekko PPMC Vote Thread
> > > https://lists.apache.org/thread/nosrvwphtwmcg7dw9pz6y1qbtm3zhgpn
> > >
> > > Pekko PPMC Vote Result
> > > https://lists.apache.org/thread/n27jqcy4160981lhdr01ljqs0c31nshh
> > >
> > > The release candidate:
> > >
> > > https://dist.apache.org/repos/dist/dev/incubator/pekko/CONNECTORS-1.0.2-RC1/
> > >
> > > This release has been signed with a PGP key, available here:
> > >
> > > https://dist.apache.org/repos/dist/release/incubator/pekko/KEYS
> > >
> > > Release Notes:
> > >
> > > https://github.com/apache/incubator-pekko-connectors/pull/310/files
> > >
> > > Git branch for the release:
> > >
> > > https://github.com/apache/incubator-pekko-connectors/tree/v1.0.2-RC1
> > > Git commit ID: 8b4d6f7db0d1c8e1482f8fcd913022ef7fe357ab
> > >
> > > Please download, verify, and test.
> > >
> > > We have also staged jars in the Apache Nexus Repository. These were
> > > built with the same code
> > > as appears in this Source Release Candidate. We would appreciate if
> > > users could test with these too.
> > > If anyone finds any serious problems with these jars, please also
> > > notify us on this thread.
> > >
> > > https://repository.apache.org/content/groups/staging/org/apache/pekko/
> > >
> > > In sbt, you can add this resolver.
> > >
> > > resolvers += "Apache Pekko Staging" at
> > > "https://repository.apache.org/content/groups/staging;
> > >
> > >
> > > The vote will be left open for at least 72 hours.
> > >
> > > [ ] +1 approve
> > > [ ] +0 no opinion
> > > [ ] -1 disapprove with the reason
> > >
> > > To learn more about Apache Pekko, please see https://pekko.apache.org/
> > >
> > > Checklist for reference:
> > >
> > > [ ] Download links are valid.
> > > [ ] Checksums and signatures.
> > > [ ] LICENSE/NOTICE files exist
> > > [ ] No unexpected binary files
> > > [ ] Source files have ASF headers
> > > [ ] Can compile from source
> > >
> > > To compile from the source, please refer to:
> > >
> > > https://github.com/apache/incubator-pekko/blob/main/README.md#building-from-source
> > >
> > > Some notes about verifying downloads can be found at:
> > >
> > > https://pekko.apache.org/download.html#verifying-downloads
> 

Re: [QUESTION] Reproducible build for container images

[PJ Fanning]

Hi Alex,

While reproducible builds are a great idea, the Incubator PMC does not
require them. Plugging away at improving things so that reproducible
builds can be produced in future is a useful thing to do.

Regards,
PJ

On Tue, 23 Jan 2024 at 14:58, Alex Porcelli  wrote:
>
> In the KIE podling, we regularly publish container images as part of
> our releases. We've achieved semantically identical images, verified
> using the 'diffoci' tool. However, due to current Docker/OCI engine
> limitations, we can't eliminate variations in file metadata caused by
> automatically appended timestamps.
>
> The latest version of Buildkit offers a solution but still needs to be
> integrated into the build engines. I want to ask the Incubator PMC: Is
> achieving semantically verifiable images sufficient for now, as we
> await the integration of Buildkit changes into Docker/OCI build
> engines?
>
> Regards,
> -
> Alex
> Apache KIE PPMC
>
> -
> 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] Release Apache Paimon (Incubating) 0.6.1-RC2

[PJ Fanning]

+1 (binding)

- source distribution has valid LICENSE/NOTICE/DISCLAIMER
- tgz has valid checksum and is correctly signed
- no unexpected binary files in source dist (one zip file but used in a test)
- source files have Apache headers
- can build source dist using mvn (Mac with JDK 11 - Temurin-11.0.21+9)

I do not see any unusual files in 
paimon-test-utils/src/main/java/org/apache/paimon/testutils/assertj/ - not in 
the tgz or even after the build.



On 2024/01/22 07:53:22 Suyan wrote:
> The java version on my machine:
> openjdk version "1.8.0_402"
> OpenJDK Runtime Environment (Temurin)(build 1.8.0_402-b06)
> OpenJDK 64-Bit Server VM (Temurin)(build 25.402-b06, mixed mode)
> 
> Sincerely,
> Suyan
> 
> > 2024年1月22日 11:55，Bi Yan  写道：
> > 
> > Hi Suyan, thanks for checking and voting.
> > 
> > Paimon supports Jdk8 and Jdk11 currently. Can you check your jdk version?
> > If yes, is there more details for me to address this? Thank you.
> > 
> > --
> > 谢谢 ~
> > Best Wishes ~
> > 
> > -
> > 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

Re: [VOTE] Release Apache Celeborn(Incubating) 0.4.0-incubating-rc4

[PJ Fanning]

+1 (binding)

- source and bin distributions have valid LICENSE/NOTICE/DISCLAIMER
- tgzs have valid checksums and are correctly signed
- no unexpected binary files in source dist
- source files have Apache headers
- can build source dist using sbt

On 2024/01/22 17:49:15 Fu Chen wrote:
> Hi Suyan,
> 
> Thank you for your vote. The GPG key was generated when I first released
> the Kyuubi project. Regarding the GPG key name, it's merely an identifier,
> and I believe it should not be a blocking issue.
> 
> Thanks,
> Fu Chen
> 
> Suyan  于2024年1月22日周一 22:01写道：
> 
> > +1 non-binding
> >
> > [x] Download links are valid
> > [x] Checksums and signatures
> > gpg: assuming signed data in
> > './apache-celeborn-0.4.0-incubating-source.tgz'
> > gpg: Signature made 四  1/18 21:06:45 2024 CST
> > gpg:using RSA key 92AF4750DAFCB5E25B5B83EA76F54B977EB5C09B
> > gpg: checking the trustdb
> > gpg: marginals needed: 3  completes needed: 1  trust model: pgp
> > gpg: depth: 0  valid:  12  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 12u
> > gpg: next trustdb check due at 2024-05-25
> > gpg: Good signature from "Fu Chen (For Kyuubi release)
> > " [ultimate]
> >
> > [x] LICENSE/NOTICE files exist
> > [x] NO unexpected binary files
> > [x] Source files have ASF headers
> > [x] Can compile from source
> >
> > Build successed on Apple Silicon M1(arm64).
> >
> >
> > I noticed the release manager's key name  'Fu Chen (for Kyuubi
> > release)', maybe a different name would be better? lol
> >
> > Sincerely,
> > Suyan
> >
> > Fu Chen  于2024年1月22日周一 00:25写道：
> > >
> > > Hi IPMC,
> > >
> > > This is a call for a vote to release Apache Celeborn (Incubating)
> > > 0.4.0-incubating-rc4
> > >
> > > The Apache Celeborn community has voted on and approved a proposal to
> > > release Apache Celeborn (Incubating) version 0.4.0-incubating-rc4.
> > > We now kindly request the Incubator PMC members review and vote on this
> > > incubator release.
> > >
> > > celeborn@dev vote thread:
> > >
> > > https://lists.apache.org/thread/w91n2vgwts06gskoc5y19gl49myjm1jq
> > >
> > > celeborn@dev vote result thread:
> > >
> > > https://lists.apache.org/thread/7ylzdq6htzvlnnjzb5lhdd1nsfv4cjmn
> > >
> > > The git tag to be voted upon:
> > >
> > >
> > https://github.com/apache/incubator-celeborn/releases/tag/v0.4.0-incubating-rc4
> > >
> > > The git commit hash:
> > > 8bc07466dd85a90216820617015e329fb806c7dd
> > >
> > > The source and binary artifacts can be found at:
> > >
> > >
> > https://dist.apache.org/repos/dist/dev/incubator/celeborn/v0.4.0-incubating-rc4
> > >
> > > The staging repo:
> > >
> > >
> > https://repository.apache.org/content/repositories/orgapacheceleborn-1051
> > >
> > > Fingerprint of the PGP key release artifacts are signed with:
> > > 92AF4750DAFCB5E25B5B83EA76F54B977EB5C09B
> > >
> > > My public key to verify signatures can be found in:
> > >
> > > https://dist.apache.org/repos/dist/release/incubator/celeborn/KEYS
> > >
> > > The vote will be open for at least 72 hours or until the necessary
> > >
> > > number of votes are reached.
> > >
> > > Please vote accordingly:
> > >
> > > [ ] +1 approve
> > > [ ] +0 no opinion
> > > [ ] -1 disapprove (and the reason)
> > >
> > > Checklist for release:
> > >
> > >
> > https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> > >
> > > Steps to validate the release:
> > >
> > > https://www.apache.org/info/verification.html
> > >
> > > Please be aware that there has been a transition in the Celeborn
> > project's
> > > build tool, shifting from Maven to SBT. The SBT build documentation is
> > > available at https://celeborn.apache.org/docs/latest/developers/sbt/.
> > >
> > > For illustrative purposes:
> > >
> > > Packaging the project
> > > ```
> > > ./build/sbt clean package
> > > ```
> > >
> > > Creating the distribution
> > > ```
> > > ./build/make-distribution.sh --sbt-enabled --release
> > > ```
> > >
> > > Regards,
> > > Fu Chen
> >
> > -
> > 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] Release Apache Pekko(incubating) Connectors 1.0.2-RC1 Inbox

[PJ Fanning]

Thanks Xuanwo. I have created PRs to update our NOTICE files.

On 2024/01/21 08:53:47 Xuanwo wrote:
> +1 non-binding
> 
> [x] Download links are valid.
> [x] Checksums and signatures.
> 
> apache-pekko-connectors-1.0.2-incubating-src-20240109.tgz
> gpg: Signature made Tue 09 Jan 2024 08:45:04 PM CST
> gpg:using RSA key 6BA4DA8B1C88A49428A29C3D0C69C1EF41181E13
> gpg: checking the trustdb
> gpg: marginals needed: 3  completes needed: 1  trust model: pgp
> gpg: depth: 0  valid:  16  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 16u
> gpg: next trustdb check due at 2024-05-25
> gpg: Good signature from "PJ Fanning (GitHub noreply address) 
> " [ultimate]
> gpg: aka "PJ Fanning " [ultimate]
> gpg: aka "PJ Fanning (http://www.apache.org/) 
> " [ultimate]
> 
> [x] LICENSE/NOTICE/DISCLAIMER files exist
> 
> nit: The NOTICE file seems not mention that Pekko is an incubating project.
> 
> [x] No unexpected binary files
> [x] Source files have ASF headers
> [x] Can compile from source
> 
> [success] Total time: 239 s (03:59), completed Jan 21, 2024, 4:53:04 PM
> sbt compile  459.14s user 14.09s system 154% cpu 5:05.48 total
> 
> Build success on archlinux x86_64
> 
> BTW, sbt is much faster than mvn!
> 
> On Sat, Jan 13, 2024, at 03:20, PJ Fanning wrote:
> > Hello Incubator Community,
> >
> > This is a call for a vote to release Apache Pekko(incubating)
> > Connectors version 1.0.2-RC1.
> >
> > The discussion thread:
> > https://lists.apache.org/thread/31tvbff0j880v3kvpmdq3st32dkynvnb
> >
> > Pekko PPMC Vote Thread
> > https://lists.apache.org/thread/nosrvwphtwmcg7dw9pz6y1qbtm3zhgpn
> >
> > Pekko PPMC Vote Result
> > https://lists.apache.org/thread/n27jqcy4160981lhdr01ljqs0c31nshh
> >
> > The release candidate:
> >
> > https://dist.apache.org/repos/dist/dev/incubator/pekko/CONNECTORS-1.0.2-RC1/
> >
> > This release has been signed with a PGP key, available here:
> >
> > https://dist.apache.org/repos/dist/release/incubator/pekko/KEYS
> >
> > Release Notes:
> >
> > https://github.com/apache/incubator-pekko-connectors/pull/310/files
> >
> > Git branch for the release:
> >
> > https://github.com/apache/incubator-pekko-connectors/tree/v1.0.2-RC1
> > Git commit ID: 8b4d6f7db0d1c8e1482f8fcd913022ef7fe357ab
> >
> > Please download, verify, and test.
> >
> > We have also staged jars in the Apache Nexus Repository. These were
> > built with the same code
> > as appears in this Source Release Candidate. We would appreciate if
> > users could test with these too.
> > If anyone finds any serious problems with these jars, please also
> > notify us on this thread.
> >
> > https://repository.apache.org/content/groups/staging/org/apache/pekko/
> >
> > In sbt, you can add this resolver.
> >
> > resolvers += "Apache Pekko Staging" at
> > "https://repository.apache.org/content/groups/staging;
> >
> >
> > The vote will be left open for at least 72 hours.
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> > To learn more about Apache Pekko, please see https://pekko.apache.org/
> >
> > Checklist for reference:
> >
> > [ ] Download links are valid.
> > [ ] Checksums and signatures.
> > [ ] LICENSE/NOTICE files exist
> > [ ] No unexpected binary files
> > [ ] Source files have ASF headers
> > [ ] Can compile from source
> >
> > To compile from the source, please refer to:
> >
> > https://github.com/apache/incubator-pekko/blob/main/README.md#building-from-source
> >
> > Some notes about verifying downloads can be found at:
> >
> > https://pekko.apache.org/download.html#verifying-downloads
> >
> >
> > Here is my +1 (binding).
> >
> > Thanks,
> > PJ Fanning
> >
> > -
> > 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
> 
> 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Paimon (Incubating) Shade 0.6.0-RC1

[PJ Fanning]

+1 (binding)

- Download links are valid.
- The checksums and signatures are validated.
- The LICENSE and NOTICE files look good to me.
- There is a DISCLAIMER file about incubating.
- source headers seem ok
- No binary files in the source release
- I can build the shade jars


On 2024/01/18 08:37:38 Xuanwo wrote:
> +1 (non-binding)
> 
> [x] Download links are valid
> [x] Checksums and signatures
> 
> apache-paimon-shade-0.6.0-incubating-src.tgz
> gpg: Signature made Tue 09 Jan 2024 02:49:37 PM CST
> gpg:using EDDSA key C81651102A8CE408792BA26FBD268155D61737A1
> gpg: checking the trustdb
> gpg: marginals needed: 3  completes needed: 1  trust model: pgp
> gpg: depth: 0  valid:  13  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 13u
> gpg: next trustdb check due at 2024-08-23
> gpg: Good signature from "Zelin Yu " [ultimate]
> 
> [x] LICENSE/NOTICE files exist
> 
> nit: The copyright in NOTICE is not updated to 2024. And do we need to
>  refer Apache Flink in this file?
> 
> [x] NO unexpected binary files
> [x] Source files have ASF headers
> [x] Can compile from source
> 
> Compiled succeed on Archlinux x86_64
> 
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO]
> [INFO] paimon-shade 0.6.0-incubating .. SUCCESS [11:42 
> min]
> [INFO] paimon-shade-guava-30 30.1.1-jre-0.6.0-incubating .. SUCCESS [03:54 
> min]
> [INFO] paimon-shade-caffeine-2 2.9.3-0.6.0-incubating . SUCCESS [ 33.974 
> s]
> [INFO] paimon-shade-jackson-parent 2.14.2-0.6.0-incubating  SUCCESS [  0.012 
> s]
> [INFO] paimon-shade-jackson-2 2.14.2-0.6.0-incubating . SUCCESS [ 55.544 
> s]
> [INFO] paimon-shade-jackson-module-jsonSchema-2 2.14.2-0.6.0-incubating 
> SUCCESS [  4.850 s]
> [INFO] paimon-shade-netty-4 4.1.100.Final-0.6.0-incubating  SUCCESS [02:20 
> min]
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time:  19:34 min
> [INFO] Finished at: 2024-01-18T15:40:34+08:00
> [INFO] 
> 
> 
> 
> On Thu, Jan 18, 2024, at 14:44, yu zelin wrote:
> > Hello Incubator Community,
> >
> > The Apache Paimon community has voted and approved the release of
> > Apache Paimon (incubating) Shade version 0.6.0-RC1. We now kindly
> > request the IPMC members to review and vote for this release.
> >
> > Apache Paimon (incubating) is a streaming data lake platform that supports
> > high-speed data ingestion, change data tracking and efficient real-time
> > analytics.
> >
> > The Paimon community vote thread:
> >
> > https://lists.apache.org/thread/b18zg4nn4k8d1z9kyp5ft1x777hy9kbb
> >
> > The vote result thread:
> >
> > https://lists.apache.org/thread/3316hkn78oqpvok4s9272ohjjzrnbrbf
> >
> > The official Apache source release to be deployed to dist.apache.org:
> >
> > https://dist.apache.org/repos/dist/dev/incubator/paimon/paimon-shade-0.6.0-incubating-rc1/
> >
> > This release has been signed with a PGP key, available here:
> >
> > https://dist.apache.org/repos/dist/release/incubator/paimon/KEYS
> >
> > All artifacts to be deployed to the Maven Central Repository:
> >
> > https://repository.apache.org/content/repositories/orgapachepaimon-1033/
> >
> > Git branch for the release:
> >
> > https://github.com/apache/incubator-paimon-shade/tree/release-0.6.0-incubating-rc1
> >
> > Git commit ID:
> > 24bbf2b991cff2402f9c8d37f1b52830a7204174
> >
> > Please download, verify, and test.
> >
> > The vote will be left open for at least 72 hours (excluding weekend days).
> > The vote will pass after 3 binding approval.
> >
> > [ ] +1 approve
> > [ ] +0 no option
> > [ ] -1 disapprove with the reason
> >
> > To learn more about Apache Paimon, please see https://paimon.apache.org/
> >
> > Checklist for reference:
> >
> > [ ] Download links are valid
> > [ ] Checksums and signatures
> > [ ] LICENSE/NOTICE files exist
> > [ ] NO unexpected binary files
> > [ ] Source files have ASF headers
> > [ ] Can compile from source
> >
> > To compile from the source, please refer to:
> > https://github.com/apache/incubator-paimon-shade/blob/main/README.md#sources
> >
> > Some notes about verifying downloads can be found at:
> > https://cwiki.apache.org/confluence/display/PAIMON/Verifying+a+Paimon+Release
> >
> > Best,
> > Zelin Yu
> 
> -- 
> Xuanwo
> 
> -
> 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] Release Apache Pekko(incubating) Connectors 1.0.2-RC1 Inbox

[PJ Fanning]

Would any of the Pekko mentors or any other Incubator PMC member have time to 
review this RC?

Any assistance would be appreciated.

On 2024/01/13 03:25:45 Matthew de Detrich wrote:
> Carrying over +1 (binding) from
> https://lists.apache.org/thread/dh18kgo4p50588c3yk8pfm83n6of21dt
> 
> On Sat, Jan 13, 2024 at 6:20 AM PJ Fanning  wrote:
> 
> > Hello Incubator Community,
> >
> > This is a call for a vote to release Apache Pekko(incubating)
> > Connectors version 1.0.2-RC1.
> >
> > The discussion thread:
> > https://lists.apache.org/thread/31tvbff0j880v3kvpmdq3st32dkynvnb
> >
> > Pekko PPMC Vote Thread
> > https://lists.apache.org/thread/nosrvwphtwmcg7dw9pz6y1qbtm3zhgpn
> >
> > Pekko PPMC Vote Result
> > https://lists.apache.org/thread/n27jqcy4160981lhdr01ljqs0c31nshh
> >
> > The release candidate:
> >
> >
> > https://dist.apache.org/repos/dist/dev/incubator/pekko/CONNECTORS-1.0.2-RC1/
> >
> > This release has been signed with a PGP key, available here:
> >
> > https://dist.apache.org/repos/dist/release/incubator/pekko/KEYS
> >
> > Release Notes:
> >
> > https://github.com/apache/incubator-pekko-connectors/pull/310/files
> >
> > Git branch for the release:
> >
> > https://github.com/apache/incubator-pekko-connectors/tree/v1.0.2-RC1
> > Git commit ID: 8b4d6f7db0d1c8e1482f8fcd913022ef7fe357ab
> >
> > Please download, verify, and test.
> >
> > We have also staged jars in the Apache Nexus Repository. These were
> > built with the same code
> > as appears in this Source Release Candidate. We would appreciate if
> > users could test with these too.
> > If anyone finds any serious problems with these jars, please also
> > notify us on this thread.
> >
> > https://repository.apache.org/content/groups/staging/org/apache/pekko/
> >
> > In sbt, you can add this resolver.
> >
> > resolvers += "Apache Pekko Staging" at
> > "https://repository.apache.org/content/groups/staging;
> >
> >
> > The vote will be left open for at least 72 hours.
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> > To learn more about Apache Pekko, please see https://pekko.apache.org/
> >
> > Checklist for reference:
> >
> > [ ] Download links are valid.
> > [ ] Checksums and signatures.
> > [ ] LICENSE/NOTICE files exist
> > [ ] No unexpected binary files
> > [ ] Source files have ASF headers
> > [ ] Can compile from source
> >
> > To compile from the source, please refer to:
> >
> >
> > https://github.com/apache/incubator-pekko/blob/main/README.md#building-from-source
> >
> > Some notes about verifying downloads can be found at:
> >
> > https://pekko.apache.org/download.html#verifying-downloads
> >
> >
> > Here is my +1 (binding).
> >
> > Thanks,
> > PJ Fanning
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
> 
> -- 
> 
> Matthew de Detrich
> 
> *Aiven Deutschland GmbH*
> 
> Immanuelkirchstraße 26, 10405 Berlin
> 
> Alexanderufer 3-7, 10117 Berlin
> 
> Amtsgericht Charlottenburg, HRB 209739 B
> 
> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> 
> *m:* +491603708037
> 
> *w:* aiven.io *e:* matthew.dedetr...@aiven.io
> 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [RESULT][VOTE] Release Apache DevLake (Incubating) v0.19.0-rc4

[PJ Fanning]

One thing that I notice about the DevLake web site is that there does
not appear to be a prominent place to download the source release.

https://devlake.apache.org/

Apologies if I just missed the link. If it isn't there, I'm pretty
sure that it is required.

On Wed, 17 Jan 2024 at 10:54, Zikuan An  wrote:
>
> Hello everyone,
>
> I am pleased to announce that the vote for Apache DevLake(Incubating)
> v0.19.0-rc4 has now concluded. Thank you all for your review and
> participation in the voting process.
>
> The release voting has passed with 3 binding votes and no +0 or -1 votes.
>
> The individuals who provided binding votes are:
> - Jean-Baptiste Onofré
> - Willem Jiang
> - David Zello
>
> You can find the voting thread at the following link:
> https://lists.apache.org/thread/ck2fs4knnjb9dxxb1cn1hxf7d5d8qys9
>
> In closing, I want to express my gratitude to everyone who has offered us
> help, advice, and guidance throughout this process. We will proceed with
> completing the remaining tasks.
>
> Thank you all once again!
>
>
> Best Regards
>
> Zikuan An

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[VOTE] Release Apache Pekko(incubating) Connectors 1.0.2-RC1 Inbox

[PJ Fanning]

Hello Incubator Community,

This is a call for a vote to release Apache Pekko(incubating)
Connectors version 1.0.2-RC1.

The discussion thread:
https://lists.apache.org/thread/31tvbff0j880v3kvpmdq3st32dkynvnb

Pekko PPMC Vote Thread
https://lists.apache.org/thread/nosrvwphtwmcg7dw9pz6y1qbtm3zhgpn

Pekko PPMC Vote Result
https://lists.apache.org/thread/n27jqcy4160981lhdr01ljqs0c31nshh

The release candidate:

https://dist.apache.org/repos/dist/dev/incubator/pekko/CONNECTORS-1.0.2-RC1/

This release has been signed with a PGP key, available here:

https://dist.apache.org/repos/dist/release/incubator/pekko/KEYS

Release Notes:

https://github.com/apache/incubator-pekko-connectors/pull/310/files

Git branch for the release:

https://github.com/apache/incubator-pekko-connectors/tree/v1.0.2-RC1
Git commit ID: 8b4d6f7db0d1c8e1482f8fcd913022ef7fe357ab

Please download, verify, and test.

We have also staged jars in the Apache Nexus Repository. These were
built with the same code
as appears in this Source Release Candidate. We would appreciate if
users could test with these too.
If anyone finds any serious problems with these jars, please also
notify us on this thread.

https://repository.apache.org/content/groups/staging/org/apache/pekko/

In sbt, you can add this resolver.

resolvers += "Apache Pekko Staging" at
"https://repository.apache.org/content/groups/staging;


The vote will be left open for at least 72 hours.

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove with the reason

To learn more about Apache Pekko, please see https://pekko.apache.org/

Checklist for reference:

[ ] Download links are valid.
[ ] Checksums and signatures.
[ ] LICENSE/NOTICE files exist
[ ] No unexpected binary files
[ ] Source files have ASF headers
[ ] Can compile from source

To compile from the source, please refer to:

https://github.com/apache/incubator-pekko/blob/main/README.md#building-from-source

Some notes about verifying downloads can be found at:

https://pekko.apache.org/download.html#verifying-downloads


Here is my +1 (binding).

Thanks,
PJ Fanning

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

podling reports for January 2024

[PJ Fanning]

Hi,

There doesn't appear to be a setup to provide podling reports for January 2024.

I'm going to be away for a few days so I have put together a report
for Apache Pekko.

https://cwiki.apache.org/confluence/display/PEKKO/Pekko+Podling+Report+-+January+2024

Feel free to modify this or to replace it with a completely different report.

Regards,
PJ

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[ANNOUNCE] Apache Pekko (Incubating) gRPC 1.0.2 available

[PJ Fanning]

Hi everyone,

The Apache Pekko (Incubating) Team is happy to announce the release of
Apache Pekko (Incubating) gRPC 1.0.2.

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.

Download Links:
https://pekko.apache.org/download.html#pekko-grpc

Release Notes:
https://pekko.apache.org/docs/pekko-grpc/current/release-notes/index.html

Website:
https://pekko.apache.org/

Issues:
https://github.com/apache/incubator-pekko-grpc/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

===

*Disclaimer*

Apache Pekko (incubating) is an effort undergoing incubation at The
Apache Software Foundation (ASF), sponsored by the Apache Incubator.
Incubation is required of all newly accepted projects until a further
review indicates that the infrastructure, communications, and decision
making process have stabilized in a manner consistent with other
successful ASF projects. While incubation status is not necessarily a
reflection of the completeness or stability of the code, it does
indicate that the project has yet to be fully endorsed by the ASF.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [RESULT] [VOTE] Release Apache Pekko(incubating) gRPC 1.0.2-RC1

[PJ Fanning]

Thanks Tison for checking. I did vote on the initial email.

https://lists.apache.org/thread/og2mtjv4nsgrh1mc96cfxbqzz8poysp8

On Mon, 8 Jan 2024 at 11:10, tison  wrote:
>
> Hi PJ,
>
> Congrats.
>
> I was told that the RM who drives the release doesn't implicitly vote
> a +1. So you'd better cast your own +1 the next time when running a
> release.
>
> But I don't find a policy sentence to mention it. While I think the
> argument is valid, I may prepare a patch on
> https://www.apache.org/foundation/voting.html to mention this
> explicitly.
>
> Best,
> tison.
>
> PJ Fanning  于2024年1月8日周一 17:48写道：
> >
> > The vote passes with 3 +1s and no negative votes. All votes were binding.
> >
> > Vote Thread
> > https://lists.apache.org/thread/og2mtjv4nsgrh1mc96cfxbqzz8poysp8
> >
> > Votes
> > Zili Chen (tison)
> > Matthew de Detrich
> > PJ Fanning
> >
> > I will proceed with the release and make the announcements.
> >
> > Thanks to everyone who participated in the development and review of
> > this release.
> >
> > -
> > 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 Pekko(incubating) gRPC 1.0.2-RC1

[PJ Fanning]

The vote passes with 3 +1s and no negative votes. All votes were binding.

Vote Thread
https://lists.apache.org/thread/og2mtjv4nsgrh1mc96cfxbqzz8poysp8

Votes
Zili Chen (tison)
Matthew de Detrich
PJ Fanning

I will proceed with the release and make the announcements.

Thanks to everyone who participated in the development and review of
this release.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Pekko(incubating) gRPC 1.0.2-RC1

[PJ Fanning]

Thanks Tison for the suggestion about the release notes. I think that is 
something we can use.


On 2024/01/08 06:12:42 tison wrote:
> +1 binding
> 
> I checked
> 
> + Download links valid
> + Checksum and signature matches
> + NOTICE and LICENSE present
> + DISCLAIMER present
> + No unexpected binaries
> + Can compile from source with `sbt compile` on Darwin Kernel Version
> 22.5.0 ARM64
> 
> One suggestion:
> 
> Perhaps you should stage the release note as a PR and only make it
> visible on the website once the VOTE has passed.
> 
> Best,
> tison.
> 
> Matthew de Detrich  于2024年1月6日周六 06:51写道：
> >
> > Carrying over +1 from
> > https://lists.apache.org/thread/txbp6w48yv2kmjwozrmdg0ltlxcjl8jj
> >
> > On Thu, Jan 4, 2024 at 10:46 PM PJ Fanning  wrote:
> >
> > > Hello Incubator Community,
> > >
> > > This is a call for a vote to release Apache Pekko(incubating)
> > > gRPC version 1.0.2-RC1.
> > >
> > > The discussion thread:
> > > https://lists.apache.org/thread/dmz52zk06byjy389f4qcrl7y9n0h00by
> > >
> > > Pekko PPMC Vote Thread:
> > > https://lists.apache.org/thread/7yfn04qlg7kcjrmx2dyosrrthj0qvnqf
> > >
> > > Pekko PPMC Vote Result:
> > > https://lists.apache.org/thread/d3ncdsyvgjwlg7sk0td55wjftbrk0wt7
> > >
> > > The release candidate:
> > >
> > > https://dist.apache.org/repos/dist/dev/incubator/pekko/GRPC-1.0.2-RC1/
> > >
> > > This release has been signed with a PGP key, available here:
> > >
> > > https://dist.apache.org/repos/dist/release/incubator/pekko/KEYS
> > >
> > > Release Notes:
> > >
> > > https://pekko.apache.org/docs/pekko-grpc/1.0/release-notes/index.html
> > >
> > > Git branch for the release:
> > >
> > > https://github.com/apache/incubator-pekko-grpc/tree/v1.0.2-RC1
> > > Git commit ID: 50cd4d8da37db570eb44a3348b21028f69942077
> > >
> > > Please download, verify, and test.
> > >
> > > We have also staged jars in the Apache Nexus Repository. These were
> > > built with the same code
> > > as appears in this Source Release Candidate. We would appreciate if
> > > users could test with these too.
> > > If anyone finds any serious problems with these jars, please also
> > > notify us on this thread.
> > >
> > > https://repository.apache.org/content/groups/staging/org/apache/pekko/
> > >
> > > In sbt, you can add this resolver.
> > >
> > > resolvers += "Apache Pekko Staging" at
> > > "https://repository.apache.org/content/groups/staging;
> > >
> > >
> > > The vote will be left open for at least 72 hours.
> > >
> > > [ ] +1 approve
> > > [ ] +0 no opinion
> > > [ ] -1 disapprove with the reason
> > >
> > > To learn more about Apache Pekko, please see https://pekko.apache.org/
> > >
> > > Checklist for reference:
> > >
> > > [ ] Download links are valid.
> > > [ ] Checksums and signatures.
> > > [ ] LICENSE/NOTICE files exist
> > > [ ] No unexpected binary files
> > > [ ] Source files have ASF headers
> > > [ ] Can compile from source
> > >
> > > To compile from the source, please refer to:
> > >
> > >
> > > https://github.com/apache/incubator-pekko-grpc/blob/main/README.md#building-from-source
> > >
> > > Some notes about verifying downloads can be found at:
> > >
> > > https://pekko.apache.org/download.html#verifying-downloads
> > >
> > >
> > > Here is my +1 (binding).
> > >
> > > Thanks,
> > > PJ Fanning
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
> > --
> >
> > Matthew de Detrich
> >
> > *Aiven Deutschland GmbH*
> >
> > Immanuelkirchstraße 26, 10405 Berlin
> >
> > Alexanderufer 3-7, 10117 Berlin
> >
> > Amtsgericht Charlottenburg, HRB 209739 B
> >
> > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> >
> > *m:* +491603708037
> >
> > *w:* aiven.io *e:* matthew.dedetr...@aiven.io
> 
> -
> 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 OpenDAL (incubating) as a TLP - Incubator

[PJ Fanning]

+1 (binding)

I think the various issues that have been raised on this thread are already 
addressed or can be addressed soon. The project seems ready to graduate.

Best of Luck.

On 2024/01/08 04:53:49 Xiaoqiao He wrote:
> +1(binding).  Good luck!
> 
> Best Regards,
> - He Xiaoqiao
> 
> 
> 
> On Mon, Jan 8, 2024 at 12:51 AM sebb  wrote:
> 
> > On Sun, 7 Jan 2024 at 10:04, tison  wrote:
> > >
> > > Hi sebb,
> > >
> > > Thanks for your suggestion :D
> > >
> > > Would you provide some examples (perhaps from TLPs) for a proper
> > description?
> > >
> > > Also, this doesn't seem to be a blocker for graduation. So if it takes
> > > a few conversations to polish, you may create an issue on [1] or email
> > > to dev@opendal.a.o.
> >
> > I agree that it is not a blocker for graduation.
> >
> > It is merely unnecessary work for your users.
> >
> > "When downloading a release, please verify the OpenPGP compatible
> > signature (or failing that, check the SHA-512); these should be
> > fetched from the main Apache site."
> >
> > > Best,
> > > tison.
> > >
> > > [1] https://github.com/apache/incubator-opendal/issues/
> > >
> > > sebb  于2024年1月7日周日 17:11写道：
> > > >
> > > > Thanks, that looks fine.
> > > >
> > > > I just noticed that the text regarding the use of hashes and sigs is
> > > > not quite correct.
> > > > There is no point checking both the hash and the sig.
> > > > Ideally check the sig, failing that check the hash.
> > > >
> > > > On Sun, 7 Jan 2024 at 02:58, Xuanwo  wrote:
> > > > >
> > > > > > There is a problem with the download page links; they do not agree
> > > > > > with Infra rules [1]
> > > > >
> > > > > Hi, sebb
> > > > >
> > > > > Thank you for bringing this to our attention. We have resolved all
> > issues
> > > > > with the links on the download page. It should now be fully
> > compliant with
> > > > > INFRA rules. Please take another look.
> > > > >
> > > > > On Sat, Jan 6, 2024, at 23:50, sebb wrote:
> > > > > > There is a problem with the download page links; they do not agree
> > > > > > with Infra rules [1]
> > > > > >
> > > > > > Artifact links must use closer.lua
> > > > > > Hashes and sigs must use https://downloads.apache.org/
> > > > > >
> > > > > > Also Releases which are not currently maintained should be dropped
> > [2]
> > > > > >
> > > > > > The KEYS file is correctly linked.
> > > > > >
> > > > > > [1]
> > https://infra.apache.org/release-download-pages.html#download-page
> > > > > > [2]
> > > > > >
> > https://infra.apache.org/release-download-pages.html#current-and-older-releases
> > > > > >
> > > > > > Sebb
> > > > > > On Sat, 6 Jan 2024 at 15:45, Craig Russell 
> > wrote:
> > > > > >>
> > > > > >> +1 binding
> > > > > >>
> > > > > >> Good Luck,
> > > > > >> Craig
> > > > > >>
> > > > > >> > On Dec 28, 2023, at 16:21, Xuanwo  wrote:
> > > > > >> >
> > > > > >> > Hello all,
> > > > > >> >
> > > > > >> > We've got positive feedback on the DISCUSS thread[1], I'd like
> > to start an
> > > > > >> > official VOTE thread now.
> > > > > >> >
> > > > > >> > Below are some facts and project highlights from the incubation
> > phase
> > > > > >> > as well as the draft resolution:
> > > > > >> >
> > > > > >> > - Currently, our community consists of 19 committers, including
> > mentors,
> > > > > >> >  with 12 serving as PPMC members.
> > > > > >> > - At present, we boast 164 contributors.
> > > > > >> > - Throughout the incubation period, we've made 9
> > releases—averaging at
> > > > > >> >  least one per month.
> > > > > >> > - We've had 7 different release managers to date.
> > > > > >> > - Our software is in production use by 10 known entities and is
> > a dependency
> > > > > >> >  for 263 GitHub projects and 18 crates.io packages.
> > > > > >> > - To date, we have opened 1,200+ issues with 1,100+
> > successfully resolved.
> > > > > >> > - We have submitted a total of 2,400+ PRs, most of them have
> > been merged
> > > > > >> >  or closed.
> > > > > >> > - We have met all maturity criteria as outlined in [2].
> > > > > >> >
> > > > > >> > Please vote on the resolution pasted below to graduate Apache
> > OpenDAL from
> > > > > >> > the incubator to the Top Level Project.
> > > > > >> >
> > > > > >> > [ ] +1 Graduate Apache OpenDAL from the Incubator.
> > > > > >> > [ ] +0 No opinion.
> > > > > >> > [ ] -1 Don't graduate Apache OpenDAL from the Incubator because
> > ...
> > > > > >> >
> > > > > >> > This vote will open for at least 72 hours.
> > > > > >> >
> > > > > >> > Many thanks to our mentors and everyone else for their support.
> > > > > >> >
> > > > > >> > [1]
> > https://lists.apache.org/thread/3lwt4zkm1ovoskrz77y69pwntvn27xvs
> > > > > >> > [2] https://opendal.apache.org/community/maturity
> > > > > >> >
> > > > > >> >
> > ---
> > > > > >> >
> > > > > >> > Establish the Apache OpenDAL Project
> > > > > >> >
> > > > > >> > WHEREAS, the Board of Directors deems it to be in the best
> > interests of
> > > > > >> > 

[VOTE] Release Apache Pekko(incubating) gRPC 1.0.2-RC1

[PJ Fanning]

Hello Incubator Community,

This is a call for a vote to release Apache Pekko(incubating)
gRPC version 1.0.2-RC1.

The discussion thread:
https://lists.apache.org/thread/dmz52zk06byjy389f4qcrl7y9n0h00by

Pekko PPMC Vote Thread:
https://lists.apache.org/thread/7yfn04qlg7kcjrmx2dyosrrthj0qvnqf

Pekko PPMC Vote Result:
https://lists.apache.org/thread/d3ncdsyvgjwlg7sk0td55wjftbrk0wt7

The release candidate:

https://dist.apache.org/repos/dist/dev/incubator/pekko/GRPC-1.0.2-RC1/

This release has been signed with a PGP key, available here:

https://dist.apache.org/repos/dist/release/incubator/pekko/KEYS

Release Notes:

https://pekko.apache.org/docs/pekko-grpc/1.0/release-notes/index.html

Git branch for the release:

https://github.com/apache/incubator-pekko-grpc/tree/v1.0.2-RC1
Git commit ID: 50cd4d8da37db570eb44a3348b21028f69942077

Please download, verify, and test.

We have also staged jars in the Apache Nexus Repository. These were
built with the same code
as appears in this Source Release Candidate. We would appreciate if
users could test with these too.
If anyone finds any serious problems with these jars, please also
notify us on this thread.

https://repository.apache.org/content/groups/staging/org/apache/pekko/

In sbt, you can add this resolver.

resolvers += "Apache Pekko Staging" at
"https://repository.apache.org/content/groups/staging;


The vote will be left open for at least 72 hours.

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove with the reason

To learn more about Apache Pekko, please see https://pekko.apache.org/

Checklist for reference:

[ ] Download links are valid.
[ ] Checksums and signatures.
[ ] LICENSE/NOTICE files exist
[ ] No unexpected binary files
[ ] Source files have ASF headers
[ ] Can compile from source

To compile from the source, please refer to:

https://github.com/apache/incubator-pekko-grpc/blob/main/README.md#building-from-source

Some notes about verifying downloads can be found at:

https://pekko.apache.org/download.html#verifying-downloads


Here is my +1 (binding).

Thanks,
PJ Fanning

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[ANNOUNCE] Apache Pekko (Incubating) Persistence R2DBC 1.0.0 available

[PJ Fanning]

Hi everyone,

The Apache Pekko (Incubating) Team is happy to announce the release of
Apache Pekko (Incubating) Persistence R2DBC 1.0.0.

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.

Download Links:
https://pekko.apache.org/download.html#pekko-persistence-r2dbc

Website:
https://pekko.apache.org/
https://pekko.apache.org/docs/pekko-persistence-r2dbc/current/

Issues:
https://github.com/apache/incubator-pekko-persistence-r2dbc/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

===

*Disclaimer*

Apache Pekko (incubating) is an effort undergoing incubation at The
Apache Software Foundation (ASF), sponsored by the Apache Incubator.
Incubation is required of all newly accepted projects until a further
review indicates that the infrastructure, communications, and decision
making process have stabilized in a manner consistent with other
successful ASF projects. While incubation status is not necessarily a
reflection of the completeness or stability of the code, it does
indicate that the project has yet to be fully endorsed by the ASF.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[RESULT] [VOTE] Release Apache Pekko(incubating) Persistence R2DBC 1.0.0-RC1

[PJ Fanning]

The vote passes with 3 binding +1s.

Vote Thread
https://lists.apache.org/thread/rschhjdlqqqjhngbhgn5z8hr4jkyvvbh

Votes
Duo Zhang
Matthew de Detrich
PJ Fanning

I will proceed with the release and make the announcements over the coming days.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Pekko(incubating) Persistence R2DBC 1.0.0-RC1

[PJ Fanning]

Thanks Duo Zhang. I'll see about getting some build docs ready for the next RC.

I did include this in the vote email but it is definitely better to
have proper build docs.

{snip}
Some of the tests rely on postgresql running locally on port 5432 and
the DDL is at ddl-scripts/create_tables_postgres.sql
{snip}

On Wed, 27 Dec 2023 at 12:54, 张铎(Duo Zhang)  wrote:
>
> +1 binding
>
> Checked sigs and sums: Matched
> LICENSE and NOTICE: Looks fine
> DISCLAIMER: In place
> Built from src:
>   I pulled the docker image
> 'eclipse-temurin-focal-11.0.21_9_1.9.8_3.3.1' and then type sbt,
> passed
> Run tests:
>   I just typed test in the sbt shell but it failed with 'Cannot
> connect to localhost:5432', seems we need to start some external
> services while running tests but I did not find any related
> documentation about how to test
>
> Thanks.
>
> PJ Fanning  于2023年12月27日周三 18:04写道：
> >
> > Would any of the Pekko mentors or indeed, any Incubator PMC members have 
> > time to review this Pekko RC? It marks the final set of Pekko modules that 
> > have yet to be released.
> >
> > On 2023/12/20 23:10:25 Matthew de Detrich wrote:
> > > Carrying over my +1 vote from
> > > https://lists.apache.org/thread/yyhoygwhox5yzrxy716kjmy7gcd4hm1r
> > >
> > > On Tue, Dec 19, 2023 at 7:16 PM PJ Fanning  wrote:
> > >
> > > > Hello Incubator Community,
> > > >
> > > > This is a call for a vote to release Apache Pekko(incubating)
> > > > Persistence R2DBC version 1.0.0-RC1.
> > > >
> > > > The Pekko vote result:
> > > > https://lists.apache.org/thread/w06swd1nd5jphtlronffw4jw18orn4hy
> > > >
> > > > Pekko Vote Thread
> > > > https://lists.apache.org/thread/k9xn5gyldpq0dypdo7cxgjjxkc04xtco
> > > >
> > > > The discussion thread:
> > > > https://lists.apache.org/thread/108tfnxofmp5bvq9y60pmwn34d6bs5s6
> > > >
> > > > The release candidate:
> > > >
> > > >
> > > > https://dist.apache.org/repos/dist/dev/incubator/pekko/PERSISTENCE-R2DBC-1.0.0-RC1/
> > > >
> > > > This release has been signed with a PGP key, available here:
> > > >
> > > > https://dist.apache.org/repos/dist/release/incubator/pekko/KEYS
> > > >
> > > > Git branch for the release:
> > > >
> > > > https://github.com/apache/incubator-pekko-persistence-r2dbc/tree/v1.0.0-RC1
> > > > Git commit ID: 3fc28f10a4570c9834495fef1d104a2dbd07fb44
> > > >
> > > > Please download, verify, and test.
> > > >
> > > > We have also staged jars in the Apache Nexus Repository. These were
> > > > built with the same code
> > > > as appears in this Source Release Candidate. We would appreciate if
> > > > users could test with these too.
> > > > If anyone finds any serious problems with these jars, please also
> > > > notify us on this thread.
> > > >
> > > > https://repository.apache.org/content/groups/staging/org/apache/pekko/
> > > >
> > > > In sbt, you can add this resolver.
> > > >
> > > > resolvers += "Apache Pekko Staging" at
> > > > "https://repository.apache.org/content/groups/staging;
> > > >
> > > >
> > > > The vote will be left open for at least 72 hours.
> > > >
> > > > [ ] +1 approve
> > > > [ ] +0 no opinion
> > > > [ ] -1 disapprove with the reason
> > > >
> > > > To learn more about Apache Pekko, please see https://pekko.apache.org/
> > > >
> > > > Checklist for reference:
> > > >
> > > > [ ] Download links are valid.
> > > > [ ] Checksums and signatures.
> > > > [ ] LICENSE/NOTICE files exist
> > > > [ ] No unexpected binary files
> > > > [ ] Source files have ASF headers
> > > > [ ] Can compile from source
> > > >
> > > > To compile from the source, please refer to:
> > > >
> > > >
> > > > https://github.com/apache/incubator-pekko/blob/main/README.md#building-from-source
> > > >
> > > > Some of the tests rely on postgresql running locally on port 5432 and
> > > > the DDL is at ddl-scripts/create_tables_postgres.sql
> > > >
> > > > Some notes about verifying downloads can be found at:
> > > >
>

Re: [VOTE] Release Apache Pekko(incubating) Persistence R2DBC 1.0.0-RC1

[PJ Fanning]

Would any of the Pekko mentors or indeed, any Incubator PMC members have time 
to review this Pekko RC? It marks the final set of Pekko modules that have yet 
to be released.

On 2023/12/20 23:10:25 Matthew de Detrich wrote:
> Carrying over my +1 vote from
> https://lists.apache.org/thread/yyhoygwhox5yzrxy716kjmy7gcd4hm1r
> 
> On Tue, Dec 19, 2023 at 7:16 PM PJ Fanning  wrote:
> 
> > Hello Incubator Community,
> >
> > This is a call for a vote to release Apache Pekko(incubating)
> > Persistence R2DBC version 1.0.0-RC1.
> >
> > The Pekko vote result:
> > https://lists.apache.org/thread/w06swd1nd5jphtlronffw4jw18orn4hy
> >
> > Pekko Vote Thread
> > https://lists.apache.org/thread/k9xn5gyldpq0dypdo7cxgjjxkc04xtco
> >
> > The discussion thread:
> > https://lists.apache.org/thread/108tfnxofmp5bvq9y60pmwn34d6bs5s6
> >
> > The release candidate:
> >
> >
> > https://dist.apache.org/repos/dist/dev/incubator/pekko/PERSISTENCE-R2DBC-1.0.0-RC1/
> >
> > This release has been signed with a PGP key, available here:
> >
> > https://dist.apache.org/repos/dist/release/incubator/pekko/KEYS
> >
> > Git branch for the release:
> >
> > https://github.com/apache/incubator-pekko-persistence-r2dbc/tree/v1.0.0-RC1
> > Git commit ID: 3fc28f10a4570c9834495fef1d104a2dbd07fb44
> >
> > Please download, verify, and test.
> >
> > We have also staged jars in the Apache Nexus Repository. These were
> > built with the same code
> > as appears in this Source Release Candidate. We would appreciate if
> > users could test with these too.
> > If anyone finds any serious problems with these jars, please also
> > notify us on this thread.
> >
> > https://repository.apache.org/content/groups/staging/org/apache/pekko/
> >
> > In sbt, you can add this resolver.
> >
> > resolvers += "Apache Pekko Staging" at
> > "https://repository.apache.org/content/groups/staging;
> >
> >
> > The vote will be left open for at least 72 hours.
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> > To learn more about Apache Pekko, please see https://pekko.apache.org/
> >
> > Checklist for reference:
> >
> > [ ] Download links are valid.
> > [ ] Checksums and signatures.
> > [ ] LICENSE/NOTICE files exist
> > [ ] No unexpected binary files
> > [ ] Source files have ASF headers
> > [ ] Can compile from source
> >
> > To compile from the source, please refer to:
> >
> >
> > https://github.com/apache/incubator-pekko/blob/main/README.md#building-from-source
> >
> > Some of the tests rely on postgresql running locally on port 5432 and
> > the DDL is at ddl-scripts/create_tables_postgres.sql
> >
> > Some notes about verifying downloads can be found at:
> >
> > https://pekko.apache.org/download.html#verifying-downloads
> >
> >
> > Here is my +1 (binding).
> >
> > Thanks,
> >
> > PJ Fanning
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
> 
> -- 
> 
> Matthew de Detrich
> 
> *Aiven Deutschland GmbH*
> 
> Immanuelkirchstraße 26, 10405 Berlin
> 
> Alexanderufer 3-7, 10117 Berlin
> 
> Amtsgericht Charlottenburg, HRB 209739 B
> 
> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> 
> *m:* +491603708037
> 
> *w:* aiven.io *e:* matthew.dedetr...@aiven.io
> 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache HugeGraph (Incubating) 1.2.0 rc1

[PJ Fanning]

The jars don't have to have incubating in the name, as far as I know.
The source release file (the tgz) has to but I think it is not
required elsewhere.

On Mon, 25 Dec 2023 at 12:48, Yu Li  wrote:
>
> -1 (binding)
>
>
> - Checked sum and signatures: OK
>
> - Checked DISCLAIMER file exists: OK
>
> - Checked LICENSE and NOTICE files: OK
>
> - Checked no binary files in source package: OK
>
> - Checked release file name and location: FAILED
>   - The HugeGraph jar files in apache-hugegraph-incubating-1.2.0.tar.gz
> (under the lib directory) don't have the word "incubating" in their names.
> For example, I see file with name like "hugegraph-api-1.2.0.jar"
>
> Best Regards,
> Yu
>
>
> On Sat, 23 Dec 2023 at 23:26, simon  wrote:
>
> > Hello Incubator Community,
> >
> > This is a call for vote to release Apache HugeGraph (Incubating) version
> > 1.2.0
> >
> > The Apache HugeGraph community has voted on and approved a proposal to
> > release Apache HugeGraph(Incubating) version 1.2.0
> >
> > We now kindly request the Incubator PMC members review and vote on this
> > incubator release.
> >
> > HugeGraph community vote thread:
> > - https://lists.apache.org/thread/mnxld09b2ozwldcxb0rpp6s7cdbdnvsw
> >
> > Vote result thread:
> > - https://lists.apache.org/thread/wns67scpfvcltk33pl403jl48pd0hc61
> >
> > The release candidate:
> > - https://dist.apache.org/repos/dist/dev/incubator/hugegraph/1.2.0/
> >
> > Git tag & Commit hash for the release:
> > - https://github.com/apache/incubator-hugegraph/tree/1.2.0  (7635c67)
> > - https://github.com/apache/incubator-hugegraph-toolchain/tree/1.2.0
> >  (f85dcf3)
> > - https://github.com/apache/incubator-hugegraph-computer/tree/1.2.0
> >  (0500fec)
> > - https://github.com/apache/incubator-hugegraph-commons/tree/1.2.0
> >  (33fa9ed)
> >
> > Release notes:
> > -
> > https://hugegraph.apache.org/docs/changelog/hugegraph-1.2.0-release-notes/
> >
> > Keys to verify the Release Candidate:
> > - https://downloads.apache.org/incubator/hugegraph/KEYS
> >
> > The release GPG user ID: simon (m...@apache.org)
> >
> > The vote will be open for at least 72 hours or until the necessary number
> > of votes are reached.
> >
> > Please vote accordingly:
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> > More detail checklist please refer:
> > -
> > https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> >
> > Steps to validate the release，Please refer to:
> > English Version:
> > -
> > https://hugegraph.apache.org/docs/contribution-guidelines/validate-release/
> > Chinese Version:
> > -
> > https://hugegraph.apache.org/cn/docs/contribution-guidelines/validate-release/
> >
> > Thanks,
> > On behalf of Apache HugeGraph(Incubating) community
> >
> >

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Accept XTable into the ASF Incubator

[PJ Fanning]

+1 (binding)

On Tue, 19 Dec 2023 at 19:08, Subramaniam Krishnan  wrote:
>
> +1 (non-binding).
>
> Looking forward to this as will be very useful.
>
> Thanks,
> Subru
>
> On 2023/12/19 02:15:02 roryqi wrote:
> > +1
> >
> > larry mccay  于2023年12月19日周二 05:30写道：
> >
> > > +1 (binding)
> > >
> > >
> > > On Sun, Dec 17, 2023 at 11:32 PM Rakesh Radhakrishnan 
> > > wrote:
> > >
> > > > +1 (non-binding)
> > > >
> > > > I'm contributing to the Apache Hadoop project and mentoring Hive
> > > > contributors in my company. It's a great initiative. The project looks
> > > > interesting to me and can be really useful to the ecosystem.
> > > >
> > > > Thanks,
> > > > Rakesh
> > > >
> > > > On Sat, Dec 16, 2023 at 9:48 AM Jesus Camacho Rodriguez <
> > > > jcama...@apache.org>
> > > > wrote:
> > > >
> > > > > Hi All,
> > > > >
> > > > > Following the discussion in the incubator mailing list [1], I am
> > > starting
> > > > > this official vote for the XTable project.
> > > > >
> > > > > Here is the proposal -
> > > > > https://cwiki.apache.org/confluence/display/INCUBATOR/XTable+Proposal
> > > > >
> > > > > Please cast your vote:
> > > > >
> > > > > [ ] +1, bring XTable into the Incubator
> > > > > [ ] +0, I don't care either way
> > > > > [ ] -1, do not bring XTable into the Incubator, because...
> > > > >
> > > > > This majority vote is open for at least 96 hours (due to the weekend).
> > > > >
> > > > > Only votes from Incubator PMC members are binding, but other votes are
> > > > > welcome!
> > > > >
> > > > > Thanks,
> > > > > Jesús
> > > > >
> > > > > [1] https://lists.apache.org/thread/rx9z8ffrf37qjhpkf1vp5rqg5lhht7jm
> > > > >
> > > >
> > >
> >
>
> -
> 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] Release Apache Pekko(incubating) Persistence R2DBC 1.0.0-RC1

[PJ Fanning]

Hello Incubator Community,

This is a call for a vote to release Apache Pekko(incubating)
Persistence R2DBC version 1.0.0-RC1.

The Pekko vote result:
https://lists.apache.org/thread/w06swd1nd5jphtlronffw4jw18orn4hy

Pekko Vote Thread
https://lists.apache.org/thread/k9xn5gyldpq0dypdo7cxgjjxkc04xtco

The discussion thread:
https://lists.apache.org/thread/108tfnxofmp5bvq9y60pmwn34d6bs5s6

The release candidate:

https://dist.apache.org/repos/dist/dev/incubator/pekko/PERSISTENCE-R2DBC-1.0.0-RC1/

This release has been signed with a PGP key, available here:

https://dist.apache.org/repos/dist/release/incubator/pekko/KEYS

Git branch for the release:

https://github.com/apache/incubator-pekko-persistence-r2dbc/tree/v1.0.0-RC1
Git commit ID: 3fc28f10a4570c9834495fef1d104a2dbd07fb44

Please download, verify, and test.

We have also staged jars in the Apache Nexus Repository. These were
built with the same code
as appears in this Source Release Candidate. We would appreciate if
users could test with these too.
If anyone finds any serious problems with these jars, please also
notify us on this thread.

https://repository.apache.org/content/groups/staging/org/apache/pekko/

In sbt, you can add this resolver.

resolvers += "Apache Pekko Staging" at
"https://repository.apache.org/content/groups/staging;


The vote will be left open for at least 72 hours.

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove with the reason

To learn more about Apache Pekko, please see https://pekko.apache.org/

Checklist for reference:

[ ] Download links are valid.
[ ] Checksums and signatures.
[ ] LICENSE/NOTICE files exist
[ ] No unexpected binary files
[ ] Source files have ASF headers
[ ] Can compile from source

To compile from the source, please refer to:

https://github.com/apache/incubator-pekko/blob/main/README.md#building-from-source

Some of the tests rely on postgresql running locally on port 5432 and
the DDL is at ddl-scripts/create_tables_postgres.sql

Some notes about verifying downloads can be found at:

https://pekko.apache.org/download.html#verifying-downloads


Here is my +1 (binding).

Thanks,

PJ Fanning

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

podling security issues

[PJ Fanning]

Hi everyone,

I'm wondering if podlings should include some details about their
security issues [1] in their 3 podling reports. We won't want to
release information about any security issues that are still under
investigation or where the fix is not yet released. I still think
there is little harm in podlings giving high level numbers and maybe
some indication of how quickly security issues are being dealt with.

I've seen evidence that some TLPs are unaware of the importance of
dealing quickly with security reports and I think the Incubator team
could help with ensuring that podlings are aware of the requirements.

I will certainly be having a close look at a podling's record of
handling security reports when it comes to discussions about
graduation.

I'm wondering if we could have some consensus on what is expected of podlings.

Regards,
PJ

[1] https://www.apache.org/security/

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [RFR] PODLINGNAMESEARCH-217

[PJ Fanning]

Brand Management approve the names. Example:
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-210


On Tue, 12 Dec 2023 at 18:26, tison  wrote:
>
> Hi,
>
> As part of a check item for podling, OpenDAL started
> PODLINGNAMESEARCH-217 [1] one week ago. This email is a message for
> seeking review on the name search request.
>
> IIRC, proceeding such requests can take one week or two, but I found a
> few backlog doesn't receive responses one month later also [2]. I
> understand that this is a volunteer based effort to proceed such
> requests, so I wonder if there is an approach for contributors to help
> in this scope?
>
> Or, it doesn't seem PODLINGNAMESEARCH being a TLP itself, so which
> PMC/committee oversees this project?
>
> Best,
> tison.
>
> [1] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-217
> [2] https://issues.apache.org/jira/projects/PODLINGNAMESEARCH
>
> -
> 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] Accept Fury Into the ASF Incubator

[PJ Fanning]

+1 (binding)

On Fri, 8 Dec 2023 at 12:49, Xin Wang  wrote:
>
> +1 (binding)
>
> tison  于2023年12月8日周五 19:05写道：
>
> > Hi Incubator
> >
> > Following the discussion [DISCUSS] Incubating Proposal of Fury [1], I
> > am starting this official vote for the Fury project.
> >
> > Here is their proposal:
> > https://cwiki.apache.org/confluence/display/INCUBATOR/Fury+Proposal
> >
> > Please cast your vote:
> >
> > [ ] +1, bring into the Incubator
> > [ ] +0, I don't care either way
> > [ ] -1, do not bring Fury into the Incubator, because...
> >
> > The vote will open for one week from today, Dec. 8th, 2023
> >
> > Best,
> > tison.
> >
> > [1] https://lists.apache.org/thread/jr3qwzxg2m6507zsll5fs8mopcco3ny3
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>
> --
> Thanks,
> Xin

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] OneTable proposal

[PJ Fanning]

Hi Ismaël,
Could you make a request to join the Incubator PMC? ASF members will
be accepted into the PMC. It's just that podling mentors need to be
part of the PMC.
Requests are made to the priv...@incubator.apache.org list.

Regards,
PJ

On Thu, 7 Dec 2023 at 23:20, Ismaël Mejía  wrote:
>
> Hello Jesus,
>
> I am interested on both contributing to this project as a committer, and as
> an ASF member I want to volunteer to mentor the project during incubation.
> I am a committer and part of the PMC of both Apache Beam and Apache Avro so
> I am close to this space so glad to help where I can.
>
> Regards,
> Ismaël
>
>
> On Mon, Dec 4, 2023 at 10:24 PM Jesus Camacho Rodriguez 
> wrote:
>
> > Hi All,
> >
> > I would like to propose a new project to the ASF incubator - OneTable.
> >
> > OneTable[1] is an omni-directional converter for table formats that
> > facilitates interoperability across data processing systems and query
> > engines. Currently, OneTable supports widely adopted open-source table
> > formats such as Apache Hudi, Apache Iceberg, and Delta Lake.
> >
> > Here is the proposal -
> > https://cwiki.apache.org/confluence/display/INCUBATOR/OneTable+Proposal
> >
> > I would be the Champion of the project. I will mentor and help the project
> > through the incubator with Hitesh Shah [hit...@apache.org], Stamatis
> > Zampetakis [zabe...@apache.org], and Jean-Baptiste Onofré [
> > jbono...@apache.org].
> >
> > We are looking forward to your feedback!
> >
> > Thanks,
> > Jesús
> >
> > [1] https://github.com/onetable-io/onetable
> >

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Accept HoraeDB Into the ASF Incubator

[PJ Fanning]

+1 (binding)

On Mon, 4 Dec 2023 at 14:17, li gang  wrote:
>
> +1 (binding)
>
> tison  于2023年12月4日周一 21:01写道：
>
> > Hi Incubator
> >
> > Following the discussion [DISCUSS] HoraeDB proposal[1],
> > I am starting this official vote for the HoraeDB project.
> >
> > Here is their proposal:
> > https://cwiki.apache.org/confluence/display/INCUBATOR/HoraeDB+Proposal
> >
> > Please cast your vote:
> >
> > [ ] +1, bring into the Incubator
> > [ ] +0, I don't care either way
> > [ ] -1, do not bring HoraeDB into the Incubator, because...
> >
> > The vote will open for one week from today, Dec. 4th, 2023
> >
> > Best,
> > tison.
> >
> > [1] https://lists.apache.org/thread/6vbhv4soxw45yf2w9l495ofdqr3029ll
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>
> --
>
>
> --
> Best Regards
> Gang Li 李岗
>
> lgcar...@apache.org

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[ANNOUNCE] Apache Pekko (Incubating) 1.0.2 available

[PJ Fanning]

Hi everyone,

The Apache Pekko (Incubating) Team is happy to announce the release of
Apache Pekko (Incubating) 1.0.2.

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.

Download Links:
https://pekko.apache.org/download.html#pekko-core

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

===

*Disclaimer*

Apache Pekko (incubating) is an effort undergoing incubation at The
Apache Software Foundation (ASF), sponsored by the Apache Incubator.
Incubation is required of all newly accepted projects until a further
review indicates that the infrastructure, communications, and decision
making process have stabilized in a manner consistent with other
successful ASF projects. While incubation status is not necessarily a
reflection of the completeness or stability of the code, it does
indicate that the project has yet to be fully endorsed by the ASF.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Pegasus (Incubating) 2.5.0 [RC1]

[PJ Fanning]

Both links under `Compile Pegasus` section are broken. The 2nd one is
a localhost link.

https://cwiki.apache.org/confluence/display/PEGASUS/Validating+a+staged+release

On Fri, 1 Dec 2023 at 09:00, Dan Wang  wrote:
>
> Hello all,
>
> This is a call for a vote to release Apache Pegasus (Incubating) version
> 2.5.0.
>
> The Apache Pegasus community has voted on and approved a proposal to
> release Apache Pegasus (Incubating) version 2.5.0.
>
> We now kindly request the Incubator PMC members review and vote on
> this incubator release.
>
> Apache Pegasus is a distributed key-value storage system that is designed
> to be simple, horizontally scalable, strongly consistent, and
> high-performance.
>
> Apache Pegasus community vote and result thread:
> Vote: https://lists.apache.org/thread/ob0h55oq9yr0d77czprftw24wwx2xchr
> Result: https://lists.apache.org/thread/p54269djfbwgllwp7trj0c12x07w4xp8
>
> The source tarball, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/pegasus/2.5.0-RC1/
>
> It is tagged in Git as v2.5.0-RC1 on Github:
> https://github.com/apache/incubator-pegasus/tree/v2.5.0-RC1
>
> The corresponding hash is the following:
> https://gitbox.apache.org/repos/asf?p=incubator-pegasus.git;a=commit;h=0ca31b70eac7321bb17fb034105695597245d47b
>
> For information about the contents of this release, see release notes:
> https://github.com/apache/incubator-pegasus/blob/50563ea33b33c5ae1a6d9b8e4cf74a7d1d9133b0/HISTORY.md
>
> The artifacts have been signed with Key : 8041A06E53E4312A, which can
> be found in KEYS file:
> https://downloads.apache.org/incubator/pegasus/KEYS
>
> Look at here for how to verify this release candidate:
> https://cwiki.apache.org/confluence/display/PEGASUS/Validating+a+staged+release
>
> The vote will be open for at least 72 hours or until the necessary number
> of votes are reached.
>
> Please vote accordingly:
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
>
> Best regards,
> Dan Wang

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

December Podling reports

[PJ Fanning]

Hi everyone,

Just in case, things seem a little behind with the setup of the podling 
reporting for December (i.e. the cwiki page hasn't been setup).

It looks like these podlings need to report based on having reported in 
September.

Baremaps
KIE
Liminal
Nemo
Uniffle
Wayang

These 3 failed to report last month and should report for next month.

Livy
Ponymail
Teaclave

All 3 same to be a few months late.


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[RESULT] [VOTE] Release Apache Pekko(incubating) Core 1.0.2-RC1

[PJ Fanning]

The vote carries with 3 +1s (all binding).

Vote Thread
https://lists.apache.org/thread/8fxdmj1rjw6x6x5p9w09vn5g43wm6lzp

Votes
Paul King
Matthew de Detrich
PJ Fanning

I will proceed with the release and announcements over the next few
days. Thanks to everyone who participated in the development and the
review of this release.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org