Re: [VOTE] Apache StormCrawler (Incubating) 3.1.0 Release Candidate 1

[sebb]

On Tue, 17 Sept 2024 at 09:36, Richard Zowalla  wrote:
>
> Hi folks,
>
> I have posted a 1st release candidate for the Apache StormCrawler 
> (Incubating) 3.1.0 release and it is ready for testing.
>
> This is the 2nd release under the ASF umbrella. Notably, it contains the new 
> playwright module, which can be used for
> dynamic scraping.
>
> 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/blob/main/RELEASING.md
>
> Here is the VOTE on our dev list:
>
> https://lists.apache.org/thread/ow97g52o7vs4z6lg5rp075dkx7xkxpln
>
> Here is the VOTE RESULT on our dev list:
>
> https://lists.apache.org/thread/v8809mrftsllz8g4g9vb412zvc09dfzv
>
> Source:
>
> https://dist.apache.org/repos/dist/dev/incubator/stormcrawler/3.1.0-rc1/
>
> Tag:
>
> https://github.com/apache/incubator-stormcrawler/releases/tag/stormcrawler-3.1.0
>
> Commit Hash:
>
> 95f80689e029a8c63a7cbf8e2a831c412250f245
>
> Maven Repo:
>
> https://repository.apache.org/content/repositories/orgapachestormcrawler-1002
>
> 
> 
> stormcrawler-3.1.0-rc1
> Testing StormCrawler 3.1.0 release candidate
> 
> https://repository.apache.org/content/repositories/orgapachestormcrawler-1002
> 
> 
> 
>
> Preview of website:
>
> https://stormcrawler.staged.apache.org/download/index.html

The KEYS link is broken, otherwise the links look as though they
should work after release.

> Release notes:
>
> https://github.com/apache/incubator-stormcrawler/releases/tag/stormcrawler-3.1.0
>
> Reminder: The up-2-date KEYS file for signature verification can be
> found here: https://downloads.apache.org/incubator/stormcrawler/KEYS
>
> Please vote on releasing these packages as Apache StormCrawler (Incubator) 
> 3.1.0
> The vote is open for at least the next 72 hours.
>
> Only votes from IPMC 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
>

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

Re: [VOTE] Release Apache Answer(Incubating) v1.4.0-RC1

[sebb]

On Tue, 10 Sept 2024 at 11:27, Yubin Ren  wrote:
>
> Hi,
>
> Thank you for your thorough review. I appreciate your feedback and would like 
> to address your points:
>
> 1. The RC download links are currently in the "The release candidates:" 
> section of the vote email. Should we make these more prominent?

I don't see a download page link in that section, only a link to the RC.

> 2. We typically update the official download page after the vote concludes. 
> Is this approach acceptable, or should we include final download links during 
> the voting stage?

The official download page must not link to unreleased code, and code
must not be released without a successful vote, so the links cannot be
added in advance.

However, you could provide a link to a staging site with the updated page.

> 3. You are correct about the problems with our download page and we will 
> correct it.
>
> We'll implement these changes promptly. Do you have any other concerns or 
> suggestions?
>
> Best regards,
> Robin
>
> On 2024/09/10 08:57:47 sebb wrote:
> > On Tue, 10 Sept 2024 at 03:28, Robin Ren  wrote:
> > >
> > > Hello,
> > >
> > > This is a call for vote to release Apache Answer(Incubating) version 
> > > v1.4.0-RC1.
> > >
> > > The vote thread:
> > > https://lists.apache.org/thread/8bqj926l0cwrrcgylxf7hpsb4dswscgq
> > >
> > > Vote Result:
> > > https://lists.apache.org/thread/zkq55vywzxrkqrvzpob7fosv56o0wq8h
> > >
> > > The release candidates:
> > > https://dist.apache.org/repos/dist/dev/incubator/answer/1.4.0-incubating-RC1/
> > >
> > > Release notes:
> > > https://github.com/apache/incubator-answer/releases/tag/v1.4.0-RC1
> > >
> > > Git tag for the release:
> > > https://github.com/apache/incubator-answer/releases/tag/v1.4.0-RC1
> > >
> > > Git commit id for the release:
> > > https://github.com/apache/incubator-answer/commit/465f4bff60944d652a7656cc410629beb18f79d2
> > >
> > > Keys to verify the Release Candidate:
> > > The artifacts signed with PGP key [F4FB827C], corresponding to
> > > [robin0...@apache.org], that can be found in keys file:
> > > https://downloads.apache.org/incubator/answer/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 with the reason
> > >
> > > Checklist for reference:
> > > [ ] Download links are valid.
> >
> > Where are the download links?
> >
> > I found the page
> >
> > https://answer.apache.org/download
> >
> > but the KEYS link is missing from that page, and the artifact links
> > don't use closer.lua.
> > The hashes and sigs are OK.
> >
> > Also the KEYS link at
> > https://answer.apache.org/community/how-to-release/#how-to-verify-the-signatures
> > uses the wrong URL; it must use
> > https://downloads.apache.org/incubator/answer/KEYS
> >
> > > [ ] Checksums and PGP signatures are valid.
> > > [ ] Source code distributions have correct names matching the current
> > > release.
> > > [ ] LICENSE and NOTICE files are correct for each Answer repo.
> > > [ ] All files have license headers if necessary.
> > > [ ] No unlicensed compiled archives bundled in source archive.
> > >
> > > To compile from the source, please refer to:
> > >
> > > https://github.com/apache/incubator-answer#building-from-source
> > >
> > > Thanks,
> > > Robin
> > >
> > > -
> > > 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

Re: [VOTE] Release Apache Answer(Incubating) v1.4.0-RC1

[sebb]

On Tue, 10 Sept 2024 at 03:28, Robin Ren  wrote:
>
> Hello,
>
> This is a call for vote to release Apache Answer(Incubating) version 
> v1.4.0-RC1.
>
> The vote thread:
> https://lists.apache.org/thread/8bqj926l0cwrrcgylxf7hpsb4dswscgq
>
> Vote Result:
> https://lists.apache.org/thread/zkq55vywzxrkqrvzpob7fosv56o0wq8h
>
> The release candidates:
> https://dist.apache.org/repos/dist/dev/incubator/answer/1.4.0-incubating-RC1/
>
> Release notes:
> https://github.com/apache/incubator-answer/releases/tag/v1.4.0-RC1
>
> Git tag for the release:
> https://github.com/apache/incubator-answer/releases/tag/v1.4.0-RC1
>
> Git commit id for the release:
> https://github.com/apache/incubator-answer/commit/465f4bff60944d652a7656cc410629beb18f79d2
>
> Keys to verify the Release Candidate:
> The artifacts signed with PGP key [F4FB827C], corresponding to
> [robin0...@apache.org], that can be found in keys file:
> https://downloads.apache.org/incubator/answer/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 with the reason
>
> Checklist for reference:
> [ ] Download links are valid.

Where are the download links?

I found the page

https://answer.apache.org/download

but the KEYS link is missing from that page, and the artifact links
don't use closer.lua.
The hashes and sigs are OK.

Also the KEYS link at
https://answer.apache.org/community/how-to-release/#how-to-verify-the-signatures
uses the wrong URL; it must use
https://downloads.apache.org/incubator/answer/KEYS

> [ ] Checksums and PGP signatures are valid.
> [ ] Source code distributions have correct names matching the current
> release.
> [ ] LICENSE and NOTICE files are correct for each Answer repo.
> [ ] All files have license headers if necessary.
> [ ] No unlicensed compiled archives bundled in source archive.
>
> To compile from the source, please refer to:
>
> https://github.com/apache/incubator-answer#building-from-source
>
> Thanks,
> Robin
>
> -
> 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: Proposal: Recording votes in podlings

[sebb]

On Sat, 7 Sept 2024 at 01:58, John D. Ament  wrote:
>
> On Fri, Sep 6, 2024 at 5:30 PM Craig Russell  wrote:
>
> > Hi,
> >
> > I'd like to discuss (again) how to register podling votes for new
> > committers, PPMC members, and releases.
> >
> > People often have many names, most of which do not matter for governance
> > purposes:
> > their actual name
> > their email from address
> > their nickname
> > their github id
> > their ASF id
> >
> > It can be difficult for folks to review votes if the ASF id is not
> > included in the vote. So I'm proposing that for votes, that a standard form
> > be used for registering and tallying votes.
> >
> > For registering votes, include the ASF id in the vote line, e.g.
> >
> > +1 clr (IPMC)
> >
> > For tallying votes (in the [RESULT][VOTE] thread):
> >
> > Vote passes:
> > +1 clr (IPMC)
> > +1 sammy (PPMC)
> > +1 jules
> > +1 jmclean (IPMC)
> > +1 cdutz (IPMC)
> >
> > no -1 or +-0 votes
> >
>
>
> I'm assuming here you want folks to vote with their highest ranking, right?
> e.g. if someone is on the IPMC and the PPMC you want them to state (IPMC)
> not (PPMC), right?

Why not both?

Seems to me that PPMC members should perhaps be considered more
important in terms of votes.
It is useful to know how many PPMC members voted.

There may be the occasional person who is not yet an ASF committer who
has feedback on the release - it would be useful to document how they
should record their contribution.

> Assuming so LGTM
>
> John
>
>
> > ...
> >
> > Using this scheme will make it easier for the person calling the vote to
> > quickly know whether the voter is a community member or PPMC member or IPMC
> > member. And it will be easier after a PPMC vote for the IPMC votes to be
> > carried over.
> >
> > 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

Re: [VOTE] Release Apache Gravitino (Incubating) 0.6.0-RC5

[sebb]

On Thu, 5 Sept 2024 at 00:02, Justin Mclean  wrote:
>
> Hi,
>
> > This is the wrong URL for the KEYS
> > Please use the URL
> >
> > https://downloads.apache.org/incubator/gravitino/KEYS
>
> The KEYS also exist here.

Indeed, although there is no guarantee that the version under
dist/dev/ is the same.
It is important for reviewers to use the KEYS file that will be used
for the release.

> > I notice this is your first ASF release, so you yet don't have a
> > standard download page.
>
> The download page is here:
> https://gravitino.apache.org/downloads

Yes, that is fine for non-ASF releases, but does not meet the
requirements for an ASF release.

> And we have a PR for the new release:
> https://github.com/apache/gravitino-site/pull/17

AFAICT that does not change the downloads page.

It would be helpful to provide a link to the staging site.

> 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 Gravitino (Incubating) 0.6.0-RC5

[sebb]

On Wed, 4 Sept 2024 at 21:47, Jerry Shao  wrote:
>
> Hi,
>
> This is a call for a vote to release Apache Gravitino (Incubating) version
> 0.6.0 release candidate 5.
> The Apache Gluten community has voted and approved the release of Apache
> Gravitino (incubating) v0.6.0-rc5. We would like to ask the IPMC members to
> review and vote for this release.
>
> Apache Gravitino community vote thread:
> https://lists.apache.org/thread/91kz09lxltjprcd0cb0ow1ztvd7qmpw6
>
> Vote result thread:
> https://lists.apache.org/thread/tz1wk3xh249loqyx6x9d94lprmyzdnbw
>
> The release candidates:
> https://dist.apache.org/repos/dist/dev/incubator/gravitino/v0.6.0-incubating-rc5/
>
> Git tag for the release:
> https://github.com/apache/gravitino/releases/tag/v0.6.0-incubating-rc5
>
> Git commit ID for the release:
> https://github.com/apache/gravitino/commit/518ea14c60547ace9beb603e87b574fe7aa8c7ff
>
> Keys to verify the Release Candidate:
> https://dist.apache.org/repos/dist/dev/incubator/gravitino/KEYS

This is the wrong URL for the KEYS
Please use the URL

https://downloads.apache.org/incubator/gravitino/KEYS

I notice this is your first ASF release, so you yet don't have a
standard download page.
Is there an RC for the proposed download page?

> The vote will be open for at least 72 hours or until the necessary number
> of votes is reached.

This is ambiguous: the vote should not be closed before 72 hours even
if enough votes have been cast.
There may be late -1 votes that mean the vote does not succeed.

> Please vote accordingly:
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Best,
> Jerry

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

Re: [ANNOUNCE] Apache Gluten (Incubating) 1.2.0 available

[sebb]

On Tue, 3 Sept 2024 at 13:14, WeitingChen  wrote:
>
> Hello everyone,
>
> The Apache Gluten (Incubating) 1.2.0-incubating has been released!
>
> Apache Gluten is a middle layer that offloads the execution of
> JVM-based SQL engines to native engines.
>
> Download Links: https://downloads.apache.org/incubator/gluten/

Sorry, but that is not a valid download page
It does not have links to sigs and hashes; does not use the CDN etc.
Please ask your mentors for guidance.

> Release Notes: https://github.com/apache/incubator-gluten/releases/tag/v1.2.0
>
> Website: https://gluten.apache.org/
>
> Resources:
> - Issue: https://github.com/apache/incubator-gluten/issues
> - Mailing list: d...@gluten.apache.org
>
> Thanks,
> Weiting 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 Gluten (Incubating) 1.2.0-RC1

[sebb]

On Thu, 1 Aug 2024 at 12:43, Weiting Chen  wrote:
>
> Ok, got it.
> So do you suggest to re-send a new vote or we can continue to use this one?

That depends - are the files identical?

And will they remain so for the duration of this vote?

> On 2024/08/01 07:39:18 sebb wrote:
> > On Thu, 1 Aug 2024 at 06:42, Weiting Chen  wrote:
> > >
> > > No worry, I use the same KEYS in 
> > > https://downloads.apache.org/incubator/gluten/KEYS to sign the artifacts.
> >
> > The point is that readers of the email need to use the same KEYS file
> > that is provided on download pages.
> >
> > The file in the dev tree is a particularly poor choice as it may be
> > completely different from the file under downloads.apache.org.
> >
> > > On 2024/07/31 11:44:51 sebb wrote:
> > > > On Wed, 31 Jul 2024 at 09:00, WeitingChen  
> > > > wrote:
> > > > >
> > > > > Hi everyone,
> > > > > This is a call for a vote to release Apache Gluten (Incubating) 
> > > > > version
> > > > > 1.2.0 release candidate 1.
> > > > > The Apache Gluten community has voted and approved the release of 
> > > > > Apache
> > > > > Gluten(incubating) v1.2.0-rc1. We would like to ask the IPMC members 
> > > > > to
> > > > > review and vote for this release.
> > > > > Apache Gluten is a middle layer that offloads JVM-based SQL engines'
> > > > > execution to native engines.
> > > > >
> > > > > Apache Gluten community vote thread:
> > > > > https://lists.apache.org/thread/fryo1hnzmytq3hyxn04rwtf71rgvc4m6
> > > > > Vote result thread:
> > > > > https://lists.apache.org/thread/6dn9dqx0g8wocywyzolssmpxophpsgn1 The
> > > > > release candidates:
> > > > > https://dist.apache.org/repos/dist/dev/incubator/gluten/1.2.0-incubating-rc1
> > > > > Release notes:
> > > > > https://github.com/apache/incubator-gluten/releases/tag/v1.2.0-rc1 
> > > > > Git tag
> > > > > for the release:
> > > > > https://github.com/apache/incubator-gluten/releases/tag/v1.2.0-rc1 Git
> > > > > commit ID for the release:
> > > > > https://github.com/apache/incubator-gluten/commit/c9f3d894fe9a83aed48b9687869027787f665f9a
> > > > > Keys
> > > > > to verify the Release Candidate:
> > > > > https://dist.apache.org/repos/dist/dev/incubator/gluten/KEYS
> > > >
> > > > That is the wrong URL.
> > > > Please use the public KEYS url at
> > > >
> > > > https://downloads.apache.org/incubator/gluten/KEYS
> > > >
> > > > > To compile from the source, please refer to:
> > > > > https://github.com/apache/incubator-gluten/blob/main/docs/get-started/Velox.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
> > > > > Checklist for reference: [ ] Download links are valid.[ ] Checksums 
> > > > > and PGP
> > > > > signatures are valid.[ ] Source code distributions have correct names
> > > > > matching the current release.[ ] LICENSE and NOTICE files are 
> > > > > accurate for
> > > > > each Apache Gluten repo.[ ] All files have license headers if 
> > > > > necessary.[ ]
> > > > > No unlicensed compiled archives are bundled in the source archive
> > > > > Thanks,Weiting
> > > > > 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
> > >
> >
> > -
> > 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 Gluten (Incubating) 1.2.0-RC1

[sebb]

On Thu, 1 Aug 2024 at 06:42, Weiting Chen  wrote:
>
> No worry, I use the same KEYS in 
> https://downloads.apache.org/incubator/gluten/KEYS to sign the artifacts.

The point is that readers of the email need to use the same KEYS file
that is provided on download pages.

The file in the dev tree is a particularly poor choice as it may be
completely different from the file under downloads.apache.org.

> On 2024/07/31 11:44:51 sebb wrote:
> > On Wed, 31 Jul 2024 at 09:00, WeitingChen  wrote:
> > >
> > > Hi everyone,
> > > This is a call for a vote to release Apache Gluten (Incubating) version
> > > 1.2.0 release candidate 1.
> > > The Apache Gluten community has voted and approved the release of Apache
> > > Gluten(incubating) v1.2.0-rc1. We would like to ask the IPMC members to
> > > review and vote for this release.
> > > Apache Gluten is a middle layer that offloads JVM-based SQL engines'
> > > execution to native engines.
> > >
> > > Apache Gluten community vote thread:
> > > https://lists.apache.org/thread/fryo1hnzmytq3hyxn04rwtf71rgvc4m6
> > > Vote result thread:
> > > https://lists.apache.org/thread/6dn9dqx0g8wocywyzolssmpxophpsgn1 The
> > > release candidates:
> > > https://dist.apache.org/repos/dist/dev/incubator/gluten/1.2.0-incubating-rc1
> > > Release notes:
> > > https://github.com/apache/incubator-gluten/releases/tag/v1.2.0-rc1 Git tag
> > > for the release:
> > > https://github.com/apache/incubator-gluten/releases/tag/v1.2.0-rc1 Git
> > > commit ID for the release:
> > > https://github.com/apache/incubator-gluten/commit/c9f3d894fe9a83aed48b9687869027787f665f9a
> > > Keys
> > > to verify the Release Candidate:
> > > https://dist.apache.org/repos/dist/dev/incubator/gluten/KEYS
> >
> > That is the wrong URL.
> > Please use the public KEYS url at
> >
> > https://downloads.apache.org/incubator/gluten/KEYS
> >
> > > To compile from the source, please refer to:
> > > https://github.com/apache/incubator-gluten/blob/main/docs/get-started/Velox.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
> > > Checklist for reference: [ ] Download links are valid.[ ] Checksums and 
> > > PGP
> > > signatures are valid.[ ] Source code distributions have correct names
> > > matching the current release.[ ] LICENSE and NOTICE files are accurate for
> > > each Apache Gluten repo.[ ] All files have license headers if necessary.[ 
> > > ]
> > > No unlicensed compiled archives are bundled in the source archive
> > > Thanks,Weiting
> > > 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
>

-
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, 1.10.0-RC3

[sebb]

On Fri, 19 Jul 2024 at 18:44, Junchao Chen  wrote:
>
> Hello,
>
> This is a call for a vote to release Apache ResilientDB(Incubating) version
> 1.10.0-RC3.
>
>
> The Apache ResilientDB community has voted on and approved a proposal to
> release
> Apache ResilientDB (Incubating) version 1.10.0-RC3.
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Community vote thread:
> • https://lists.apache.org/thread/fzr26wttxrhnpfmkgc9smfgp126fxnpj
>
> Vote result thread:
> • https://lists.apache.org/thread/g120h3759m887ncx9xdd6380b0s41dlo
>
> The release candidates:
> https://dist.apache.org/repos/dist/dev/incubator/resilientdb/1.10.0-rc3/
>
> Release notes:
> https://github.com/apache/incubator-resilientdb/blob/master/CHANGELOG.md#resielientdb-v1100-2024-4-16
>
> Git tag for the release:
> https://github.com/apache/incubator-resilientdb/tree/v1.10.0-rc03
>
> Keys to verify the Release Candidate:
> https://dist.apache.org/repos/dist/dev//incubator/resilientdb/KEYS

Wrong URL.
Please use the public URL at

https://downloads.apache.org/incubator/resilientdb/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 with the reason
>
>
> To compile from the source, please refer to:
> https://github.com/apache/incubator-resilientdb/tree/1.10.0-rc03?tab=readme-ov-file#build-and-deploy-resilientdb
> 
>
>
> Thanks,
> Junchao

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

Re: [VOTE] Release Apache Gluten (Incubating) 1.2.0-RC1

[sebb]

On Wed, 31 Jul 2024 at 09:00, WeitingChen  wrote:
>
> Hi everyone,
> This is a call for a vote to release Apache Gluten (Incubating) version
> 1.2.0 release candidate 1.
> The Apache Gluten community has voted and approved the release of Apache
> Gluten(incubating) v1.2.0-rc1. We would like to ask the IPMC members to
> review and vote for this release.
> Apache Gluten is a middle layer that offloads JVM-based SQL engines'
> execution to native engines.
>
> Apache Gluten community vote thread:
> https://lists.apache.org/thread/fryo1hnzmytq3hyxn04rwtf71rgvc4m6
> Vote result thread:
> https://lists.apache.org/thread/6dn9dqx0g8wocywyzolssmpxophpsgn1 The
> release candidates:
> https://dist.apache.org/repos/dist/dev/incubator/gluten/1.2.0-incubating-rc1
> Release notes:
> https://github.com/apache/incubator-gluten/releases/tag/v1.2.0-rc1 Git tag
> for the release:
> https://github.com/apache/incubator-gluten/releases/tag/v1.2.0-rc1 Git
> commit ID for the release:
> https://github.com/apache/incubator-gluten/commit/c9f3d894fe9a83aed48b9687869027787f665f9a
> Keys
> to verify the Release Candidate:
> https://dist.apache.org/repos/dist/dev/incubator/gluten/KEYS

That is the wrong URL.
Please use the public KEYS url at

https://downloads.apache.org/incubator/gluten/KEYS

> To compile from the source, please refer to:
> https://github.com/apache/incubator-gluten/blob/main/docs/get-started/Velox.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
> Checklist for reference: [ ] Download links are valid.[ ] Checksums and PGP
> signatures are valid.[ ] Source code distributions have correct names
> matching the current release.[ ] LICENSE and NOTICE files are accurate for
> each Apache Gluten repo.[ ] All files have license headers if necessary.[ ]
> No unlicensed compiled archives are bundled in the source archive
> Thanks,Weiting
> Chen

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

Re: PMC is a committee

[sebb]

On Thu, 11 Jul 2024 at 00:17, Craig Russell  wrote:
>
>
> > On Jul 9, 2024, at 01:29, Bertrand Delacretaz  
> > wrote:
> >
> > I don't see what's wrong with saying "Member of a PMC" or "PMC
> > Member". That's clear, factual, and if sometimes people say "PMC" but
> > mean "PMC member" that's not dramatic, and easy to fix.
>
> I believe that the reason we use the acronym PMC is that it's (much) easier 
> to type than Project Management Committee. And similarly, especially for 
> those for whom English is not their primary language, Member of PMC is a 
> whole lot harder to type than MPMC.
>
> I also did a bit of scrolling through PMC onboarding messages and found many 
> examples where the PMC member inviting the new MPMC misused the PMC term. For 
> example:
>
> Invitation to become Apache Airflow PMC: Joe Bleau
> [VOTE] Joe Bleau as Dubbo PMC
> Invitation to become Apache YuniKorn (Incubating) PPMC
> Invitation to become AGE PPMC: Joe Bleau
> RE: Invitation to the Lucene.NET PMC
> Invitation to become Superset PMC: Joe Bleau
>
> I've prepared a message to the communities involved asking them to review 
> their onboarding templates to update the wrong terminology. [1]
>
> I still think we can do a better job of reinforcing our documentation along 
> the lines started by tison.
>
> And I agree that the discussion should continue on the Members list.
>
> Regards,
> Craig (Member hat)
>
>
> [1] Message to 15 PPMC and PMC private lists; review comments welcome:
>
> tl;dr please review and update your onboarding process for new PMC members
>
> There is an ongoing discussion in the Incubator regarding how to refer to PMC 
> members. The discussion is around the misuse of the term PMC to refer to PMC 
> members.
>
> https://apache.org/foundation/glossary.html#PMC
>
> "Avoid referring to a member of a PMC as "a PMC", as it can cause confusion 
> about whether you are talking about the group or an individual."
>
> When I investigated the onboarding process for new PMC members I found 
> several cases where the invitation to the new PMC member explicitly referred 
> to the new PMC member to "become PMC" instead of "become a PMC member". For 
> example,
>
> Invitation to become Apache Airflow PMC: Joe Bleau
> [VOTE] Joe Bleau as Dubbo PMC
> Invitation to become Apache YuniKorn (Incubating) PPMC
> Invitation to become AGE PPMC: Joe Bleau
> RE: Invitation to the Lucene.NET PMC
The previous one is borderline: c.f. 'invitation to team' does not
imply the person is a team.

> Invitation to become Superset PMC: Joe Bleau
>
> Without going deeper into this issue, I assume that there are templates that 
> are used to invite new members into the PMC, and the terminology used in the 
> templates is erroneous.
>
> Can you please review and update your onboarding process and templates to be 
> sure that new PMC members are not referred to as "PMC".

It would be helpful to provide suggested replacements.

For example:

Invitation to join the Apache Airflow PMC: Joe Bleau
[VOTE] Joe Bleau to join the  Dubbo PMC
Invitation to join the  Apache YuniKorn (Incubating) PPMC
Invitation to join the AGE PPMC: Joe Bleau
RE: Invitation to join the Lucene.NET PMC
Invitation to join the Superset PMC: Joe Bleau

or

Invitation to become an Apache Airflow PMC member: Joe Bleau
[VOTE] Joe Bleau as Dubbo PMC member
Invitation to become an Apache YuniKorn (Incubating) PPMC member
or
Invitation to become a member of AGE PPMC: Joe Bleau
RE: Invitation to become a member of Lucene.NET PMC
Invitation to become a member of Superset PMC: Joe Bleau

I slightlly prefer the use of 'join' because it sounds more inclusive,
but 'join' won't work everywhere.

> Thanks,
> Craig
>
> Craig L Russell
> c...@apache.org
>

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

Re: PMC is a committee

[sebb]

If the issue is brevity, then

I am on the XYZ PPMC
is not much longer than
I am a XYZ PPMC

On Tue, 9 Jul 2024 at 11:44, Cédric Champeau  wrote:
>
> As far as I'm concerned, I'm not super fond of more acronyms. "Member of
> PMC" is clear and good enough.
>
> Le mar. 9 juil. 2024 à 12:36, Zhang Yonglun  a
> écrit :
>
> > In the past, this kind of situation occurred more frequently, but most
> > have been corrected in recent years, precisely because people actively
> > pointed out the issues and encouraged corrections. I'd suggest we
> > continue to popularize the notation of PMC Member.
> > Of course, if the MPMC acronyms is perfect and elegant, it would be
> > worth the time to implement. But if we create a new acronyms for the
> > sake of a very few people using it incorrectly, then it might seem a
> > bit contrived.
> > The term PMC Member itself is not wrong, it's just that some people
> > have mistakenly used PMC in its place. Why would we expect that
> > changing PMC Member to MPMC would prevent these people from using it
> > incorrectly?
> > If we introduce MPMC, should we also consider simultaneously add CPMC
> > (PMC Chair) and MASF (ASF Member) to ensure that all roles have a fair
> > acronyms? Otherwise, MPMC might seem a bit out of place.
> >
> > Best Regards,
> > Zhang Yonglun
> >
> > Greg Stein  于2024年7月3日周三 08:05写道：
> > >
> > > Hello all,
> > >
> > > I am getting really tired of seeing people refer to *MEMBERS* of a PMC as
> > > "PMCs".
> > >
> > > PMC stands for Project Management Committee.
> > >
> > > You have MEMBERS of that PMC.
> > >
> > > People are never to be called a PMC, nor a group of them as PMCs. People
> > > are not committees. The acronym "PMC" is short for a committee, not a
> > > person.
> > >
> > > Please stop the confusion. Teach the community how to use the proper
> > terms.
> > >
> > > Thanks,
> > > Greg
> >
> > -
> > 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: PMC is a committee

[sebb]

On Mon, 8 Jul 2024 at 18:21, Craig Russell  wrote:
>
> So, I agree with Greg (! I know) that there is real potential for confusion 
> and we should try to fix it.
>
> Now what we need to do is to bikeshed the name. Either MPMC or PMCM captures 
> the spirit. None of these conflict with any commonly used acronyms. Which of 
> these works best with PPMC and IPMC?
>
> I personally prefer MPMC, MIPMC, and MPPMC. Because we want people to think 
> of member first when writing the acronym. And anyone familiar with governing 
> bodies knows MP for Member of Parliament, MEP for Member of European 
> Parliament.

+1

> Once we decide on the acronym, we need to socialize it by updating all of our 
> "how it works" pages to mention and explain it. Then, when people misuse PMC, 
> we can include a link to the explanation.

Should also be mentioned in the Glossary [1], which should also have
PPMC and IPMC added.

However, we should remember that people outside the ASF also read
mailing lists, so ideally use 'member' wherever possible, at least for
the first mention.
Yes, it's a bit more work for the author, but less effort for the
readers (and there are generally multiple readers versus 1 author).

Sebb
[1] https://apache.org/foundation/glossary.html
> Craig
>
>
> > On Jul 8, 2024, at 03:37, Greg Stein  wrote:
> >
> > On Sun, Jul 7, 2024 at 10:47 PM Joe Witt  wrote:
> >
> >> Greg
> >>
> >> It isnt wrong to correct improper usage particularly when there is a
> >> specific case that caused actual confusion.
> >>
> >
> > I appreciate the concept of "correct the usage when you see it", and I
> > *have* been doing that for several years now. Probably once a month or two,
> > over and over for years. The improper usage isn't stopping, so I'm raising
> > the concern here. The wider community simply needs to understand the
> > acronym means a committee, and stop using it for individuals. It is a
> > simple definitional solution to this longstanding problem that I feel has
> > not improved since my first whack-a-mole message to correct the improper
> > usage.
> >
> > Cheers,.
> > -g
>
> 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: [VOTE] Release Apache ResilientDB, Incubating, v1.10.0-RC1

[sebb]

On Thu, 6 Jun 2024 at 00:22, Apratim Shukla
 wrote:
>
> Greetings,
>
> Thank you for your guidance regarding the management of the Downloads
> section on our website.
>
> I am writing to inform you that the Apache ResilientDB (Incubating) team
> has updated the Downloads section of our website -
> https://resilientdb.incubator.apache.org/. We have clearly labeled the
> available download artifacts to specify that they are non-ASF releases.
> Moreover, we've added a badge to the Downloads section to further highlight
> that these are non-ASF.
>
> Please feel free to review these modifications at your convenience. If
> there are any further changes or additional clarifications needed, do not
> hesitate to let me know.

The contents of the SHA256 link are not in the standard format
expected by automated checkers.

The  'Sign' link downloads a file in UTF-16 format, and are actually a
SHA256 hash for a different file entirely.
The word 'Sign' is not applicable; it should probably be 'Signature'.
Also a signature file requires a KEYS file for verification.
In this case, the Sign link should probably be dropped.

It's also confusing that the download box is headed "GitHubv1.9.0"

> Warm regards,
> Apratim
> apra...@apache.org
> Apache ResilientDB (Incubating) Team
>
> On Thu, May 30, 2024 at 10:35 PM Craig Russell  wrote:
>
> > Hi,
> >
> > Yes, if there are no releases from the project since entering incubation,
> > it's fine to disable the download section.
> >
> > Or if you want to expend the extra effort, you could clearly identify the
> > download artifacts as non-ASF releases.
> >
> > Warm regards,
> > Craig
> >
> >
> > > On May 30, 2024, at 21:51, Apratim Shukla 
> > wrote:
> > >
> > > Greetings,
> > >
> > > I am reaching out to discuss the download section on the Apache
> > ResilientDB
> > > (Incubating) project website - https://resilientdb.incubator.apache.org/
> > .
> > > Since we do not have any approved releases yet, we are considering
> > > temporarily hiding this section to avoid any potential confusion.
> > >
> > > Could we proceed with disabling the download section until our first
> > > official release? Your advice on this matter would be greatly
> > appreciated.
> > >
> > > Thank you for your support.
> > >
> > > Best regards,
> > > Apratim
> > >
> > > On Sat, May 25, 2024 at 1:11 AM sebb  wrote:
> > >
> > >> On Sat, 25 May 2024 at 08:10, Junchao Chen  > >
> > >> wrote:
> > >>>
> > >>> Hi,
> > >>>
> > >>> Currently, we are working on our first release, we don't have any
> > formal
> > >>> released code.
> > >>
> > >> That is not the impression given by the website or GitHub.
> > >> There is no indication that any of the downloads are not approved by
> > >> the Incubator.
> > >>
> > >>> For this channel, we are aiming to obtain votes for our release.
> > >>>
> > >>> For the download links, should it be the link of the
> > >>> https://downloads.apache.org/incubator/
> > >>> ?
> > >>
> > >> Yes, for KEYS, hashes and sigs.
> > >> Source artifacts must use closer.lua.
> > >> Your mentors should be able to help with this.
> > >>
> > >>> Thanks,
> > >>> Junchao
> > >>>
> > >>> On Fri, May 24, 2024 at 1:01 AM sebb  wrote:
> > >>>
> > >>>> The download links are not in compliance with ASF policy.
> > >>>> (and the signature button does not link to the signature)
> > >>>>
> > >>>> Also the quick setup section links directly to code that has not been
> > >>>> formally released.
> > >>>> The quick setup instructions should only reference released code, i.e.
> > >>>> code that has passed a formal vote.
> > >>>>
> > >>>> On Fri, 24 May 2024 at 02:40, Apratim Shukla
> > >>>>  wrote:
> > >>>>>
> > >>>>> Greetings,
> > >>>>>
> > >>>>> I'm pleased to announce the launch of the redesigned Apache
> > >> ResilientDB
> > >>>>> (Incubating) website, now live at
> > >>>> https://resilientdb.incubator.apache.org.
>

Re: [VOTE] Accept Gravitino into the ASF Incubator

[sebb]

Missing reference [1] and proposal?

On Wed, 29 May 2024 at 16:33, Jean-Baptiste Onofré  wrote:
>
> Hi folks,
>
> Following the discussion about Gravitino [1], I would like to start
> the formal vote to accept Gravitino into the ASF Incubator.
>
>  As reminder, this is the Gravitino Proposal:
>
> Please cast your vote:
>
> [ ] +1, accept Gravitino into the ASF Incubator
> [ ] 0, I don't care either way
> [ ] -1, do not accept Gravitino into the ASF Incubator, because ...
>
> The vote will run for one week starting from today.
>
> Thanks !
>
> Regards
> JB
>
> -
> 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: What is sufficient Incubation notification for Git repos?

[sebb]

On Sat, 25 May 2024 at 09:10, tison  wrote:
>
> A lazy consensus is met at [1].

Sorry, but I don't think it is correct to to use that designation here.

I don't think the discussion has been open long enough to say that
consensus has been achieved, nor was there an explicit call for
opinions.
All one can say is that no objections have yet been raised so far.

> I support Justin's opinion that "we were
> not too prescriptive on the exact wording". But this patch can be used as a
> reference for a good starting point for other podlings.

I agree it is a good starting point. But given how many places would
have to be updated if there are any subsequent objections, I think it
would be good to get some more opinions.

> [1]
> https://github.com/apache/incubator-horaedb/pull/1535#issuecomment-2130634831
>
> Best,
> tison.
>
>
> tison  于2024年5月24日周五 13:16写道：
>
> > A concrete proposal for the HoraeDB situation:
> > https://github.com/apache/incubator-horaedb/pull/1535
> >
> > Best,
> > tison.
> >
> >
> > tison  于2024年5月24日周五 08:03写道：
> >
> >> Hi,
> >>
> >> This is a discussed topic at [1].
> >>
> >> [1] https://lists.apache.org/thread/kxvdkrf8g8yr6hww1n08r21xdy67y4ok
> >>
> >> I agree on the '(Incubating)' in the repo description part.
> >>
> >> For the disclaimer part, [1] first had:
> >>
> >> > I would be for requiring the incubator disclaimer text in the project's
> >> > README.
> >>
> >> But later Justin suggested [2]:
> >>
> >> [2] https://lists.apache.org/thread/n1otdvff6fw14xmpjwlc8xy40dh0grms
> >>
> >> > Alternatively, perhaps we can come up with something a little shorter
> >> > shorter that points to DISCLAIMER? What is important is that the
> >> > project is clearly understood to be an incubating p[project and
> >> > what that means, rather than the exact wording.
> >>
> >> I made a few preview candidates at [3].
> >>
> >> [3] https://github.com/apache/incubator-fury/tree/tisonkun-patch-1.
> >>
> >> So now, I think we can evaluate these opinions at HoraeDB's ticket [4] to
> >> make a reference.
> >>
> >> [4] https://issues.apache.org/jira/browse/INFRA-25790
> >>
> >> I can see that either:
> >>
> >> 1. Inline the DISCLAIMER content in the README; or,
> >> 2. Add a link to the '(Incubating)' words to the DISCLAIMER.
> >>
> >> should work.
> >>
> >> cc dev@horaedb.a.o for their information and participation. Please keep
> >> general@incubator.o.o in cc.
> >>
> >> Best,
> >> tison.
> >>
> >>
> >> Justin Mclean  于2024年5月24日周五 07:52写道：
> >>
> >>> Hi,
> >>>
> >>> > Whilst the DISCLAIMER file is helpful, and having '(Incubating)' in
> >>> > the repo description/About, neither of these are all that obvious.
> >>>
> >>> Yep, that should be done.
> >>>
> >>> > It seems to me that the repo README should also contain the Incubator
> >>> > disclaimer, as is done on website pages.
> >>>
> >>> That is also my expectation.
> >>>
> >>> See for instance:
> >>> https://issues.apache.org/jira/browse/INFRA-25790
> >>>
> >>> Kind Regards,
> >>> Justin
> >>>
> >>> -
> >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >>> For additional commands, e-mail: general-h...@incubator.apache.org
> >>>
> >>>

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

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

[sebb]

On Sat, 25 May 2024 at 08:10, Junchao Chen  wrote:
>
> Hi,
>
> Currently, we are working on our first release, we don't have any formal
> released code.

That is not the impression given by the website or GitHub.
There is no indication that any of the downloads are not approved by
the Incubator.

> For this channel, we are aiming to obtain votes for our release.
>
> For the download links, should it be the link of the
> https://downloads.apache.org/incubator/
> ?

Yes, for KEYS, hashes and sigs.
Source artifacts must use closer.lua.
Your mentors should be able to help with this.

> Thanks,
> Junchao
>
> On Fri, May 24, 2024 at 1:01 AM sebb  wrote:
>
> > The download links are not in compliance with ASF policy.
> > (and the signature button does not link to the signature)
> >
> > Also the quick setup section links directly to code that has not been
> > formally released.
> > The quick setup instructions should only reference released code, i.e.
> > code that has passed a formal vote.
> >
> > On Fri, 24 May 2024 at 02:40, Apratim Shukla
> >  wrote:
> > >
> > > Greetings,
> > >
> > > I'm pleased to announce the launch of the redesigned Apache ResilientDB
> > > (Incubating) website, now live at
> > https://resilientdb.incubator.apache.org.
> > >
> > > The website has been rebuilt using Next.js and Tailwind CSS for improved
> > > user experience and scalability, with CircleCI integrated for continuous
> > > deployment. We believe these updates will better serve our community and
> > > showcase the project’s capabilities.
> > >
> > > Please visit the new site and share any feedback or required changes.
> > >
> > > Thank you for your support.
> > >
> > > Best regards,
> > > Apratim
> > >
> > > On Sun, May 12, 2024 at 9:08 PM Mohammad Sadoghi 
> > > wrote:
> > >
> > > > Dear Justin
> > > >
> > > > Thank you for your detailed feedback. We will create a brand version
> > of the
> > > > website to address all your comments.
> > > >
> > > > Here is a quick response to your feedback.
> > > >
> > > >
> > > > *- You list sponsors, how do these companies sponsor the project?*These
> > > > companies funded basic research and development at ExpoLab at UC
> > Davis; no
> > > > commercial interests. So we will keep it separate.
> > > >
> > > > *- You list 1.9.0 for download, but there is no link to the KEYS files*
> > > > We will fix it.
> > > >
> > > > *- You list Mohammad Sadoghi as the “Principle Investigator.” This is
> > > > problematic from an ASF point of view. An ASF community doesn't have a
> > > > leader.*
> > > > I serve as the principal investigator in my research group at UC
> > Davis. We
> > > > will remove this from the website that we are creating. We will use the
> > > > following template.
> > > >
> > > > https://spark.apache.org/
> > > > https://flink.apache.org/
> > > > https://hadoop.apache.org/
> > > > https://sedona.apache.org/
> > > >
> > > > *- There are people listed on the page that are not part of the PMC*
> > > > Members will be removed from the new website for Apache.
> > > >
> > > > *- You list members of a “founding team”, again this is problematic.
> > You
> > > > can’t claim this as it is now an ASF project and run by the community.*
> > > > Same as above. We will mark them as initial committers.
> > > >
> > > > *- you use resilientdb.com <http://resilientdb.com/> email address for
> > > > contact and support.*
> > > > We will use d...@resilientdb.apache.org instead.
> > > >
> > > > *- The relationship between cloud offering and rsview and the ASF
> > project
> > > > is unclear. Are these also open source, or do they intend to be
> > commercial
> > > > offerings?*
> > > > We have a testnet live for public use since last October. It is based
> > > > mostly on cost-effective small cloud installations for development and
> > > > community purposes. Our project has been active since 2018 (and
> > > > open-sourced since 2019). Our focus has been research and development,
> > and
> > > > we do not have any commercialization plan.
> > > >
> > > > *- Again the connection wi

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

[sebb]

The download links are not in compliance with ASF policy.
(and the signature button does not link to the signature)

Also the quick setup section links directly to code that has not been
formally released.
The quick setup instructions should only reference released code, i.e.
code that has passed a formal vote.

On Fri, 24 May 2024 at 02:40, Apratim Shukla
 wrote:
>
> Greetings,
>
> I'm pleased to announce the launch of the redesigned Apache ResilientDB
> (Incubating) website, now live at https://resilientdb.incubator.apache.org.
>
> The website has been rebuilt using Next.js and Tailwind CSS for improved
> user experience and scalability, with CircleCI integrated for continuous
> deployment. We believe these updates will better serve our community and
> showcase the project’s capabilities.
>
> Please visit the new site and share any feedback or required changes.
>
> Thank you for your support.
>
> Best regards,
> Apratim
>
> On Sun, May 12, 2024 at 9:08 PM Mohammad Sadoghi 
> wrote:
>
> > Dear Justin
> >
> > Thank you for your detailed feedback. We will create a brand version of the
> > website to address all your comments.
> >
> > Here is a quick response to your feedback.
> >
> >
> > *- You list sponsors, how do these companies sponsor the project?*These
> > companies funded basic research and development at ExpoLab at UC Davis; no
> > commercial interests. So we will keep it separate.
> >
> > *- You list 1.9.0 for download, but there is no link to the KEYS files*
> > We will fix it.
> >
> > *- You list Mohammad Sadoghi as the “Principle Investigator.” This is
> > problematic from an ASF point of view. An ASF community doesn't have a
> > leader.*
> > I serve as the principal investigator in my research group at UC Davis. We
> > will remove this from the website that we are creating. We will use the
> > following template.
> >
> > https://spark.apache.org/
> > https://flink.apache.org/
> > https://hadoop.apache.org/
> > https://sedona.apache.org/
> >
> > *- There are people listed on the page that are not part of the PMC*
> > Members will be removed from the new website for Apache.
> >
> > *- You list members of a “founding team”, again this is problematic. You
> > can’t claim this as it is now an ASF project and run by the community.*
> > Same as above. We will mark them as initial committers.
> >
> > *- you use resilientdb.com  email address for
> > contact and support.*
> > We will use d...@resilientdb.apache.org instead.
> >
> > *- The relationship between cloud offering and rsview and the ASF project
> > is unclear. Are these also open source, or do they intend to be commercial
> > offerings?*
> > We have a testnet live for public use since last October. It is based
> > mostly on cost-effective small cloud installations for development and
> > community purposes. Our project has been active since 2018 (and
> > open-sourced since 2019). Our focus has been research and development, and
> > we do not have any commercialization plan.
> >
> > *- Again the connection with ResillientApp is unlear.*
> > This is our application stack built on top of ResilientDB. Essentially it
> > is toolsets. The main tools have already been transferred into the Apache
> > incubator repo as well.
> >
> > *- The website is misisng the required ASF links to the foundation, events,
> > license, thanks, security, and privacy. [1]*
> > We will add the missing elseents.
> >
> > ---
> > 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 Mon, May 13, 2024 at 5:20 AM Justin Mclean 
> > wrote:
> >
> > > Hi,
> > >
> > > A few questions occurred to me when looking at the website:
> > > - You list sponsors, how do these companies sponsor the project?
> > > - You list 1.9.0 for download, but there is no link to the KEYS files
> > > - You list Mohammad Sadoghi as the “Principle Investigator” This is
> > > problematic from an ASF point of view. An ASF community doesn't have a
> > > leader.
> > > - There are people listed on the page that are not part of the PMC
> > > - You list members of a “founding team”, again this is problematic. You
> > > can’t claim this as it is now an ASF project and run by the community.
> > > - you use resilientdb.com email address for contact and support.
> > > - The relationship between cloud offering and rsview and the ASF project
> > > is unclear. Are these also open source, or do they intend to be
> > commercial
> > > offerings?
> > > - Again the connection with ResillientApp is unlear.
> > > - The website is misisng the required ASF links to the foundation,
> > events,
> > > license, thanks, security, and privacy. [1]
> > >
> > > I suggest you engage with your mentors and get them to provide advice
> > here.
> > >
> > > Kind Regards,
> > > Justin

What is sufficient Incubation notification for Git repos?

[sebb]

Now that 'incubator' is no longer required as part of Git repo names,
the question arises: what notification is required to ensure users are
aware of the status?

Whilst the DISCLAIMER file is helpful, and having '(Incubating)' in
the repo description/About, neither of these are all that obvious.

It seems to me that the repo README should also contain the Incubator
disclaimer, as is done on website pages.

Sebb

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

Re: [VOTE] Release Apache Answer(Incubating) v1.3.1-RC2

[sebb]

On Mon, 13 May 2024 at 16:40, Suyan  wrote:
>
> -1 binding
>
> When I try to download the candidate, I find that the source file's size is 
> 0B.
> Please recheck it.
>
> I tried the following link:
> https://dist.apache.org/repos/dist/dev/incubator/answer/1.3.1-incubating-RC2/apache-answer-1.3.1-incubating-src.tar.gz

All the archives are empty:

$ svn ls -v 
https://dist.apache.org/repos/dist/dev/incubator/answer/1.3.1-incubating-RC2
  69054 shuai May 09 07:07 ./
  69054 shuai   0 May 09 07:07
apache-answer-1.3.1-incubating-bin-darwin-amd64.tar.gz
  69054 shuai 858 May 09 07:07
apache-answer-1.3.1-incubating-bin-darwin-amd64.tar.gz.asc
  69054 shuai 185 May 09 07:07
apache-answer-1.3.1-incubating-bin-darwin-amd64.tar.gz.sha512
  69054 shuai   0 May 09 07:07
apache-answer-1.3.1-incubating-bin-darwin-arm64.tar.gz
  69054 shuai 858 May 09 07:07
apache-answer-1.3.1-incubating-bin-darwin-arm64.tar.gz.asc
  69054 shuai 185 May 09 07:07
apache-answer-1.3.1-incubating-bin-darwin-arm64.tar.gz.sha512
  69054 shuai   0 May 09 07:07
apache-answer-1.3.1-incubating-bin-linux-amd64.tar.gz
  69054 shuai 858 May 09 07:07
apache-answer-1.3.1-incubating-bin-linux-amd64.tar.gz.asc
  69054 shuai 184 May 09 07:07
apache-answer-1.3.1-incubating-bin-linux-amd64.tar.gz.sha512
  69054 shuai   0 May 09 07:07
apache-answer-1.3.1-incubating-bin-linux-arm64.tar.gz
  69054 shuai 858 May 09 07:07
apache-answer-1.3.1-incubating-bin-linux-arm64.tar.gz.asc
  69054 shuai 184 May 09 07:07
apache-answer-1.3.1-incubating-bin-linux-arm64.tar.gz.sha512
  69054 shuai   0 May 09 07:07
apache-answer-1.3.1-incubating-bin-windows-amd64.tar.gz
  69054 shuai 858 May 09 07:07
apache-answer-1.3.1-incubating-bin-windows-amd64.tar.gz.asc
  69054 shuai 186 May 09 07:07
apache-answer-1.3.1-incubating-bin-windows-amd64.tar.gz.sha512
  69054 shuai   0 May 09 07:07
apache-answer-1.3.1-incubating-src.tar.gz
  69054 shuai 858 May 09 07:07
apache-answer-1.3.1-incubating-src.tar.gz.asc
  69054 shuai 172 May 09 07:07
apache-answer-1.3.1-incubating-src.tar.gz.sha512

> Sincerely,
> Suyan
>
> Shuailing LI  于2024年5月13日周一 15:53写道：
> >
> > Sorry, there was a clerical error in the email I just sent, corrected here.
> >
> > Hello,
> >
> > This is a call for vote to release Apache Answer(Incubating) version
> > v1.3.1-RC2.
> >
> > The vote thread:
> > https://lists.apache.org/thread/0851fqyw36q0xvkjwkxt4fkym623bgmq
> >
> > Vote Result:
> > https://lists.apache.org/thread/3oqn8mqp7jc3sm5nz1k93y1rgys03m13
> >
> > The release candidates:
> > https://dist.apache.org/repos/dist/dev/incubator/answer/1.3.1-incubating-RC2/
> >
> > Release notes:
> > https://github.com/apache/incubator-answer/releases/tag/v1.3.1-RC2
> >
> > Git tag for the release:
> > https://github.com/apache/incubator-answer/releases/tag/v1.3.1-RC2
> >
> > Git commit id for the release:
> > https://github.com/apache/incubator-answer/commit/3a375881b845a529e89dab31da48c822b524d261
> >
> > Keys to verify the Release Candidate:
> > The artifacts signed with PGP key [4C21E346], corresponding to [
> > sh...@apache.org], that can be found in keys file:
> > https://dist.apache.org/repos/dist/release/incubator/answer/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 with the reason
> >
> > Checklist for reference:
> > [ ] Download links are valid.
> > [ ] Checksums and PGP signatures are valid.
> > [ ] Source code distributions have correct names matching the current
> > release.
> > [ ] LICENSE and NOTICE files are correct for each Answer repo.
> > [ ] All files have license headers if necessary.
> > [ ] No unlicensed compiled archives bundled in source archive.
> >
> >
> > Thanks,
> > shuai
>
> -
> 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 Answer(Incubating) v1.3.1-RC2

[sebb]

On Mon, 13 May 2024 at 08:53, Shuailing LI  wrote:
>
> Sorry, there was a clerical error in the email I just sent, corrected here.
>
> Hello,
>
> This is a call for vote to release Apache Answer(Incubating) version
> v1.3.1-RC2.
>
> The vote thread:
> https://lists.apache.org/thread/0851fqyw36q0xvkjwkxt4fkym623bgmq
>
> Vote Result:
> https://lists.apache.org/thread/3oqn8mqp7jc3sm5nz1k93y1rgys03m13
>
> The release candidates:
> https://dist.apache.org/repos/dist/dev/incubator/answer/1.3.1-incubating-RC2/
>
> Release notes:
> https://github.com/apache/incubator-answer/releases/tag/v1.3.1-RC2
>
> Git tag for the release:
> https://github.com/apache/incubator-answer/releases/tag/v1.3.1-RC2
>
> Git commit id for the release:
> https://github.com/apache/incubator-answer/commit/3a375881b845a529e89dab31da48c822b524d261
>
> Keys to verify the Release Candidate:
> The artifacts signed with PGP key [4C21E346], corresponding to [
> sh...@apache.org], that can be found in keys file:
> https://dist.apache.org/repos/dist/release/incubator/answer/KEYS

Please use the official location for the KEYS file, i.e.

https://downloads.apache.org/incubator/answer/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 with the reason
>
> Checklist for reference:
> [ ] Download links are valid.
> [ ] Checksums and PGP signatures are valid.
> [ ] Source code distributions have correct names matching the current
> release.
> [ ] LICENSE and NOTICE files are correct for each Answer repo.
> [ ] All files have license headers if necessary.
> [ ] No unlicensed compiled archives bundled in source archive.
>
>
> Thanks,
> shuai

-
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

[sebb]

On Mon, 13 May 2024 at 08:41, 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 link to the official location, i.e.

https://downloads.apache.org/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

[sebb]

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/

Thanks, however I could not find a download page.

Also, the menu links mostly don't work.

> 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.
> > > > > >
> > > > > >
> > > > > >
> > > > > > Any other suggestions?
> > > > > >
> > > > > > Thanks,
> > > > > > Junchao
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Sun, May 5, 2024 at 4:44 AM John D. Ament <
> > johndam...@apache.org>
> > > > > > wrote:
> > > > > >
> > > > > &g

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

[sebb]

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

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

[sebb]

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.

It's not a crutch if the naming convention satisfies the requirement;
it's just another way of doing it.

> I am +1 (binding) on dropping the prefix myself. Incubation notices
> should be handled during releases, and on the official podling website.

IMO Incubation status needs to be made clear from the very start.
It is not something that can be left until later.

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

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

[sebb]

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.


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  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 :
> > >-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 
> > 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: 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
> > >
> >
>
>
> --
> Best Regards,
> - *Hulk Lin*
>

-
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

[sebb]

On Sun, 5 May 2024 at 05:13, 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.

Product licenses may change, so ideally the LICENSE file should state
the version of each dependency to which it applies.
When a dependency is updated, its license should be re-checked, and
the LICENSE file updated.

> Just wondering, but who are your mentors?  What was their feedback on the
> release? They should be able to help you sort this out.
>
>
> >
> > Thanks,
> > junchao
> >
> > On Sat, May 4, 2024 at 5:36 PM Justin Mclean 
> > 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
> > >
> > >
> >

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

Re: Verification of download pages and links

[sebb]

On Wed, 1 May 2024 at 18:14, tison  wrote:
>
> Hi Sebb,
>
> I'm trying to make a reference in the next OpenDAL release, that staging
> the download pages and links.
>
> Here is a technical issue. Before the release is out, which link should be
> used? IIUC we can use the link at [1]. But it doesn't follow the INFRA
> policy for formal releases. However, before the release it out, no artifact
> of the specific version is available at [2] or [3].

I think the staging download page should show the intended final link values.
These will not point to an actual file (apart from KEYS), but it
should still be possible to check that the links have the correct
format.

> [1] https://dist.apache.org/repos/dist/dev/opendal/
> [2] https://www.apache.org/dyn/closer.lua/opendal/
> [3] https://downloads.apache.org/opendal/
>
> This is the ongoing patch [4] where I left a TODO inline.
>
> [4] https://github.com/apache/opendal/pull/4565
>
> Best,
> tison.
>
>
> tison  于2024年4月29日周一 08:43写道：
>
> > > The link to the source download and keys and hashes is broken.
> >
> > Thank you! File [1] to fix it.
> >
> > [1] https://github.com/apache/opendal/pull/4547
> >
> > This shows the necessity of previewing the download page. At least since
> > we provide it, we should ensure its correctness.
> >
> > Best,
> > tison.
> >
> >
> > Justin Mclean  于2024年4月29日周一 08:15写道：
> >
> >> Hi,
> >>
> >> > Here is a patch to cover a minimal download page [1], which is derived
> >> from
> >> > OpenDAL's download page [2]. Welcome to leave comments if you find any
> >> > issues or things we can improve on.
> >> >
> >> > [1] https://github.com/apache/datafusion/pull/10271
> >> > [2] https://opendal.apache.org/download
> >>
> >> The link to the source download and keys and hashes is broken.
> >>
> >> Kind Regards,
> >> Justin
> >>
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >>

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

Re: Verification of download pages and links

[sebb]

On Sun, 28 Apr 2024 at 19:46, Dave Fisher  wrote:
>
>
>
> > On Apr 28, 2024, at 9:58 AM, tison  wrote:
> >
> > Thank you!
> >
> > I found there is no rationale for these links, and thus, it's quite a bit
> > challenging in memory.
> >
> > IIRC the closer.lua script is for selecting the most proper CDN for
> > source/binary bundles in use. They can, technically, work for SHASUM and
> > signatures also. Why do we use https://downloads.apache.org for the latter
> > two?
>
> Historically we had a mirror network and closer.lua picked out a mirror near 
> you. In order to be sure that the download source or binary on the mirror was 
> not altered on (or on its way to or from) the mirror, the detached signature 
> and checksums must be served from ASF controlled resources.
>
> Whether or not this still makes sense is a discussion for Infra since they 
> are charged with enforcing and supporting the release distribution policy.

As it stands, the policy requires direct links for sigs and hashes and
closer.lua for artifacts.

https://infra.apache.org/release-distribution.html#download-links

> Best,
> Dave
>
> >
> > Best,
> > tison.
> >
> >
> > sebb  于2024年4月29日周一 00:34写道：
> >
> >> On Sun, 28 Apr 2024 at 15:38, tison  wrote:
> >>>
> >>> Yeah. I support that we always need to release sources on our platform.
> >>>
> >>> Given the links to downloads.apache.org, archive.apache.org,
> >>> https://www.apache.org/dyn/closer.lua, can be unintuitive for users, I
> >>> agree that we can have a simple Download page for such library-only
> >>> projects.
> >>
> >> The download page can also be used for links to release notes, and to
> >> provide other support information.
> >>
> >>> Here is a patch to cover a minimal download page [1], which is derived
> >> from
> >>> OpenDAL's download page [2]. Welcome to leave comments if you find any
> >>> issues or things we can improve on.
> >>>
> >>> [1] https://github.com/apache/datafusion/pull/10271
> >>
> >> The closer.lua script is only intended for the source and binary bundles.
> >>
> >> The sigs and hashes (and KEYS) should link directly to
> >> https://downloads.apache.org/datafusion/...
> >>
> >>> [2] https://opendal.apache.org/download
> >>>
> >>> Best,
> >>> tison.
> >>>
> >>>
> >>> Justin Mclean  于2024年4月28日周日 10:02写道：
> >>>
> >>>> Hi,
> >>>>
> >>>> Projects need to make source releases on ASF infrastructure and have a
> >>>> download page for good reasons. Some users need a place to verify and
> >>>> download a trusted release. Having it hosted on ASF infrastructure
> >> means
> >>>> people can 100% trust it, unlike 3rd party providers. 3rd party
> >> providers
> >>>> have gone rogue in the past (e.g . Source Forge), disappeared (e.g.
> >> Google
> >>>> Code), or had multiple serious issues (e.g. NPM). Also by placing a
> >> release
> >>>> in the ASF distribution area / a project download page gives confidence
> >>>> that the ASF release process has been followed and that it is not a
> >> release
> >>>> by a 3rd party or an unofficial release of some sort.  IMO, all
> >> projects
> >>>> need to have a download page, even if it may not be used by the
> >> majority of
> >>>> users.
> >>>>
> >>>> Kind Regards,
> >>>> Justin
> >>>> -
> >>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >>>> For additional commands, e-mail: general-h...@incubator.apache.org
> >>>>
> >>>>
> >>
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >>
>
>
> -
> 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: Verification of download pages and links

[sebb]

On Sun, 28 Apr 2024 at 15:38, tison  wrote:
>
> Yeah. I support that we always need to release sources on our platform.
>
> Given the links to downloads.apache.org, archive.apache.org,
> https://www.apache.org/dyn/closer.lua, can be unintuitive for users, I
> agree that we can have a simple Download page for such library-only
> projects.

The download page can also be used for links to release notes, and to
provide other support information.

> Here is a patch to cover a minimal download page [1], which is derived from
> OpenDAL's download page [2]. Welcome to leave comments if you find any
> issues or things we can improve on.
>
> [1] https://github.com/apache/datafusion/pull/10271

The closer.lua script is only intended for the source and binary bundles.

The sigs and hashes (and KEYS) should link directly to
https://downloads.apache.org/datafusion/...

> [2] https://opendal.apache.org/download
>
> Best,
> tison.
>
>
> Justin Mclean  于2024年4月28日周日 10:02写道：
>
> > Hi,
> >
> > Projects need to make source releases on ASF infrastructure and have a
> > download page for good reasons. Some users need a place to verify and
> > download a trusted release. Having it hosted on ASF infrastructure means
> > people can 100% trust it, unlike 3rd party providers. 3rd party providers
> > have gone rogue in the past (e.g . Source Forge), disappeared (e.g. Google
> > Code), or had multiple serious issues (e.g. NPM). Also by placing a release
> > in the ASF distribution area / a project download page gives confidence
> > that the ASF release process has been followed and that it is not a release
> > by a 3rd party or an unofficial release of some sort.  IMO, all projects
> > need to have a download page, even if it may not be used by the majority of
> > users.
> >
> > Kind Regards,
> > Justin
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >

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

Re: [ANNOUNCE] Apache Baremaps 0.7.3 (incubating) released

[sebb]

On Sun, 28 Apr 2024 at 10:48, Bertil Chapuis  wrote:
>
> Thanks a lot for taking the time to check the announcement. I cross checked 
> everything during the vote and then let my guard down for the announcement.
>
> I now fixed the template for the announcement on our GitHub repository:
> https://github.com/apache/incubator-baremaps/blob/9bb6650142a380f91f4294ed63e53df84001bef3/RELEASE.md?plain=1#L161

The link to https://www.apache.org/dyn/closer.lua/incubator/baremaps//
is not appropriate for an announce email, and is superfluous as the
link is on the download page,

> I also updated the download page to fix the copy paste error:
> https://baremaps.apache.org/download/release-0.7.3

ACK

> hopefully, our next release will go smoothly.
>
>
> > On 28 Apr 2024, at 00:33, sebb  wrote:
> >
> > On Sat, 27 Apr 2024 at 21:17, Bertil Chapuis  wrote:
> >>
> >> Hello Everyone,
> >>
> >> The Apache Baremaps community is pleased to announce the release of Apache 
> >> Baremaps 0.7.3 (incubating). Thank you to everyone who contributed to this 
> >> release.
> >>
> >> Apache Baremaps is a toolkit and a set of infrastructure components for 
> >> creating, publishing, and operating online maps. This new release 
> >> addresses most licensing concerns identified when joining the incubator, 
> >> which is a significant step for the project. In addition, there is now 
> >> support for PMTiles, which enables low-cost and low-maintenance map 
> >> applications. Finally, significant improvements were made to enable the 
> >> creation of vector tiles from the Daylight Map Distribution.
> >>
> >> We are looking to grow our community and welcome new contributors. If you 
> >> are interested in contributing to the project, please contact us on the 
> >> mailing list or on GitHub. We will be happy to help you get started.
> >>
> >> The release notes are available here:
> >> https://github.com/apache/incubator-baremaps/releases/tag/v0.7.3
> >>
> >> The artifacts are available here:
> >> https://dist.apache.org/repos/dist/release/incubator/baremaps/0.7.3
> >
> > Sorry, but that is not a valid download page.
> >
> > The dist.apache.org host is only intended for staging a release, and
> > is not intended for general downloads.
> > Also download pages must have links to KEYS, sigs and hashes, and use
> > closer.lua for artifact links.
> >
> > It looks like the website has a suitable web page here:
> > https://baremaps.apache.org/download/release-0.7.3
> >
> > Please make sure such pages are used in release announcements!
> >
> > BTW, the download page has a copy-paste error: there are two instances
> > of the text:
> >
> > "The SHA checksum for the source distribution is available here:"
> >
> > The second instance actually relates to the binary distribution.
> > Similarly for the PGP signature.
> >
> >> The hashes of the artifacts are as follows:
> >> 3c399626c13e2fc40984d21581a747d6ad2b703c08206ceaf3bf1819551e7a99ca7cfbfae3652de8fa06ccc7a6f06f086277c5ed52574636d8b043f24d85f5cf
> >>   ./apache-baremaps-0.7.3-incubating-src.tar.gz
> >> 3c3213b8cb925eeb67734fbae55369e8c37b6c42cb62f498a62e752b969928e16db522f44e2bf0e8542175e031e9ebe64170bafd97b5cfd3e1636498bf12c15a
> >>   ./apache-baremaps-0.7.3-incubating-bin.tar.gz
> >>
> >> The repository is available here:
> >> https://github.com/apache/incubator-baremaps
> >>
> >> The documentation is available here:
> >> https://baremaps.apache.org
> >>
> >> The mailing list is available here:
> >> https://lists.apache.org/list.html?d...@baremaps.apache.org
> >>
> >> The issue tracker is available here:
> >> https://github.com/apache/incubator-baremaps/issues
> >>
> >> Best regards,
> >>
> >> Bertil Chapuis
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@baremaps.apache.org
> > For additional commands, e-mail: dev-h...@baremaps.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: [ANNOUNCE] Apache Baremaps 0.7.3 (incubating) released

[sebb]

On Sat, 27 Apr 2024 at 21:17, Bertil Chapuis  wrote:
>
> Hello Everyone,
>
> The Apache Baremaps community is pleased to announce the release of Apache 
> Baremaps 0.7.3 (incubating). Thank you to everyone who contributed to this 
> release.
>
> Apache Baremaps is a toolkit and a set of infrastructure components for 
> creating, publishing, and operating online maps. This new release addresses 
> most licensing concerns identified when joining the incubator, which is a 
> significant step for the project. In addition, there is now support for 
> PMTiles, which enables low-cost and low-maintenance map applications. 
> Finally, significant improvements were made to enable the creation of vector 
> tiles from the Daylight Map Distribution.
>
> We are looking to grow our community and welcome new contributors. If you are 
> interested in contributing to the project, please contact us on the mailing 
> list or on GitHub. We will be happy to help you get started.
>
> The release notes are available here:
> https://github.com/apache/incubator-baremaps/releases/tag/v0.7.3
>
> The artifacts are available here:
> https://dist.apache.org/repos/dist/release/incubator/baremaps/0.7.3

Sorry, but that is not a valid download page.

The dist.apache.org host is only intended for staging a release, and
is not intended for general downloads.
Also download pages must have links to KEYS, sigs and hashes, and use
closer.lua for artifact links.

It looks like the website has a suitable web page here:
https://baremaps.apache.org/download/release-0.7.3

Please make sure such pages are used in release announcements!

BTW, the download page has a copy-paste error: there are two instances
of the text:

"The SHA checksum for the source distribution is available here:"

The second instance actually relates to the binary distribution.
Similarly for the PGP signature.

> The hashes of the artifacts are as follows:
> 3c399626c13e2fc40984d21581a747d6ad2b703c08206ceaf3bf1819551e7a99ca7cfbfae3652de8fa06ccc7a6f06f086277c5ed52574636d8b043f24d85f5cf
>   ./apache-baremaps-0.7.3-incubating-src.tar.gz
> 3c3213b8cb925eeb67734fbae55369e8c37b6c42cb62f498a62e752b969928e16db522f44e2bf0e8542175e031e9ebe64170bafd97b5cfd3e1636498bf12c15a
>   ./apache-baremaps-0.7.3-incubating-bin.tar.gz
>
> The repository is available here:
> https://github.com/apache/incubator-baremaps
>
> The documentation is available here:
> https://baremaps.apache.org
>
> The mailing list is available here:
> https://lists.apache.org/list.html?d...@baremaps.apache.org
>
> The issue tracker is available here:
> https://github.com/apache/incubator-baremaps/issues
>
> Best regards,
>
> Bertil Chapuis
> -
> 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: Missing Incubator disclaimer text

[sebb]

On Thu, 25 Apr 2024 at 16:56, tison  wrote:
>
> Thanks for your explanation and good catch. I sent [1] to improve the case
> here and it should be resolved now.
>
> [1] https://github.com/apache/incubator-streampark-website/pull/351
>
> To search other pages, perhaps you can try to read the /sitemap.xml file to
> find pages. Although I can see some hidden pages are included in
> StreamPark's sitemap.xml, it's an issue of the project, not the approach to
> walk through all the pages by sitemap.xml.

The intention is to check a few pages other than the main page.

If any pages don't have disclaimers, then it is likely that there are
others without disclaimers.
Once alerted to this, it is expected that podlings will take
responsibility to follow through and check all their pages.

Note also that not all podlings have a sitemap.xml file

> Best,
> tison.
>
>
> sebb  于2024年4月25日周四 22:43写道：
>
> > On Thu, 25 Apr 2024 at 15:18, tison  wrote:
> > >
> > > > The array is a list of pages in which the disclaimer could not be
> > found.
> > >
> > > I do a quick check for the podlings I'm familiar with:
> > >
> > > For StreamPark, it reports:
> > >"disclaimers": [
> > >   14,
> > >   [
> > > "https://streampark.incubator.apache.org/team";,
> > > "https://streampark.incubator.apache.org/user";
> > >   ]
> > > ]
> > > But both pages should have the disclaimer at the footer.
> >
> > The checker does not currently support pages generated by Javascript.
> >
> > Those pages display as completely empty if Javascript is not enabled;
> > that is not very friendly.
> >
> > >
> > > For Fury, Answer, and HoraeDB, the result seems correct. It reports that
> > > HoraeDB doesn't have the DISCLAIMER on all of its pages; this is the
> > > case. I'll reach out to them to resolve this.
> > >
> > > I mentor a new podling GraphAr, which seems missing in the report.
> > >
> > > Best,
> > > tison.
> > >
> > >
> > > sebb  于2024年4月25日周四 22:11写道：
> > >
> > > > On Wed, 24 Apr 2024 at 13:05, tison  wrote:
> > > > >
> > > > > Hi Sebb,
> > > > >
> > > > > > quite a few podlings where the text is only present on some of the
> > web
> > > > > pages
> > > > >
> > > > > [1] you refers writes:
> > > > >
> > > > > >> Podling web sites MUST include a clear disclaimer on their website
> > > > >
> > > > > So, IMO it's clear that every page should contain such info
> > (typically as
> > > > > part of the footer). If you find any podling violates this policy,
> > you
> > > > can
> > > > > name them and I'd like to give a look.
> > > >
> > > > I updated the Whimsy site scanner to report on top-level links to
> > > > podling pages which don't appear to have the disclaimer.
> > > > This does not yet appear in the Whimsy podlings report, but the raw
> > > > data is in the JSON file at
> > > >
> > > > https://whimsy.apache.org/public/pods-scan.json
> > > >
> > > > Search for "disclaimers", e.g.
> > > >
> > > > "disclaimers": [
> > > >   1,
> > > >   [
> > > > "https://hugegraph.incubator.apache.org/docs/";,
> > > > "
> > https://hugegraph.incubator.apache.org/docs/download/download/";,
> > > > "https://hugegraph.incubator.apache.org/community/";
> > > >   ]
> > > >
> > > > The initial number (1 above) is the count of references that do appear
> > > > to have the disclaimer.
> > > > The array is a list of pages in which the disclaimer could not be
> > found.
> > > >
> > > > In the above case, I think they all need the disclaimer, but there may
> > > > be some cases where it is not appropriate.
> > > >
> > > > > For the podlings I participate in, I spread the docu template [2] to
> > > > ensure
> > > > > that this policy is followed.
> > > > >
> > > > > [2]
> > > > >
> > > >
> > https://github.com/apache/apache-website-template/blob/f8129ca66fdff1c97e0749eb2ed319f1739f6f34/docusauru

Re: Missing Incubator disclaimer text

[sebb]

On Thu, 25 Apr 2024 at 15:18, tison  wrote:
>
> > The array is a list of pages in which the disclaimer could not be found.
>
> I do a quick check for the podlings I'm familiar with:
>
> For StreamPark, it reports:
>"disclaimers": [
>   14,
>   [
> "https://streampark.incubator.apache.org/team";,
> "https://streampark.incubator.apache.org/user";
>   ]
> ]
> But both pages should have the disclaimer at the footer.

The checker does not currently support pages generated by Javascript.

Those pages display as completely empty if Javascript is not enabled;
that is not very friendly.

>
> For Fury, Answer, and HoraeDB, the result seems correct. It reports that
> HoraeDB doesn't have the DISCLAIMER on all of its pages; this is the
> case. I'll reach out to them to resolve this.
>
> I mentor a new podling GraphAr, which seems missing in the report.
>
> Best,
> tison.
>
>
> sebb  于2024年4月25日周四 22:11写道：
>
> > On Wed, 24 Apr 2024 at 13:05, tison  wrote:
> > >
> > > Hi Sebb,
> > >
> > > > quite a few podlings where the text is only present on some of the web
> > > pages
> > >
> > > [1] you refers writes:
> > >
> > > >> Podling web sites MUST include a clear disclaimer on their website
> > >
> > > So, IMO it's clear that every page should contain such info (typically as
> > > part of the footer). If you find any podling violates this policy, you
> > can
> > > name them and I'd like to give a look.
> >
> > I updated the Whimsy site scanner to report on top-level links to
> > podling pages which don't appear to have the disclaimer.
> > This does not yet appear in the Whimsy podlings report, but the raw
> > data is in the JSON file at
> >
> > https://whimsy.apache.org/public/pods-scan.json
> >
> > Search for "disclaimers", e.g.
> >
> > "disclaimers": [
> >   1,
> >   [
> > "https://hugegraph.incubator.apache.org/docs/";,
> > "https://hugegraph.incubator.apache.org/docs/download/download/";,
> > "https://hugegraph.incubator.apache.org/community/";
> >   ]
> >
> > The initial number (1 above) is the count of references that do appear
> > to have the disclaimer.
> > The array is a list of pages in which the disclaimer could not be found.
> >
> > In the above case, I think they all need the disclaimer, but there may
> > be some cases where it is not appropriate.
> >
> > > For the podlings I participate in, I spread the docu template [2] to
> > ensure
> > > that this policy is followed.
> > >
> > > [2]
> > >
> > https://github.com/apache/apache-website-template/blob/f8129ca66fdff1c97e0749eb2ed319f1739f6f34/docusaurus.config.ts#L137
> > >
> > > > and in announcement emails
> > >
> > > This sounds like a new sentence to me. Have we ever had a consensus
> > before?
> > > I agree that such a policy can help convey the project's status more
> > > clearly, and it won't be difficult to add such a section in the
> > > announcement email. Most of the podlings may be unaware of this point,
> > and
> > > I didn't hear about this before.
> > >
> > > Best,
> > > tison.
> > >
> > >
> > > sebb  于2024年4月24日周三 15:58写道：
> > >
> > > > My understanding is that the Incubator disclaimer text [1] should be
> > > > present on all website pages and in announcement emails, so consumers
> > > > are clear about the status of the software.
> > > >
> > > > However there are quite a few podlings where the text is only present
> > > > on some of the web pages, and most announce emails don't include the
> > > > disclaimer.
> > > >
> > > > Note that unlike licensing issues, which can be sorted out during
> > > > incubation, this is something that must be addressed from the very
> > > > beginning.
> > > >
> > > > Sebb
> > > > [1] https://incubator.apache.org/guides/branding.html#disclaimers
> > > >
> > > > -
> > > > 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: Missing Incubator disclaimer text

[sebb]

On Wed, 24 Apr 2024 at 13:05, tison  wrote:
>
> Hi Sebb,
>
> > quite a few podlings where the text is only present on some of the web
> pages
>
> [1] you refers writes:
>
> >> Podling web sites MUST include a clear disclaimer on their website
>
> So, IMO it's clear that every page should contain such info (typically as
> part of the footer). If you find any podling violates this policy, you can
> name them and I'd like to give a look.

I updated the Whimsy site scanner to report on top-level links to
podling pages which don't appear to have the disclaimer.
This does not yet appear in the Whimsy podlings report, but the raw
data is in the JSON file at

https://whimsy.apache.org/public/pods-scan.json

Search for "disclaimers", e.g.

"disclaimers": [
  1,
  [
"https://hugegraph.incubator.apache.org/docs/";,
"https://hugegraph.incubator.apache.org/docs/download/download/";,
"https://hugegraph.incubator.apache.org/community/";
  ]

The initial number (1 above) is the count of references that do appear
to have the disclaimer.
The array is a list of pages in which the disclaimer could not be found.

In the above case, I think they all need the disclaimer, but there may
be some cases where it is not appropriate.

> For the podlings I participate in, I spread the docu template [2] to ensure
> that this policy is followed.
>
> [2]
> https://github.com/apache/apache-website-template/blob/f8129ca66fdff1c97e0749eb2ed319f1739f6f34/docusaurus.config.ts#L137
>
> > and in announcement emails
>
> This sounds like a new sentence to me. Have we ever had a consensus before?
> I agree that such a policy can help convey the project's status more
> clearly, and it won't be difficult to add such a section in the
> announcement email. Most of the podlings may be unaware of this point, and
> I didn't hear about this before.
>
> Best,
> tison.
>
>
> sebb  于2024年4月24日周三 15:58写道：
>
> > My understanding is that the Incubator disclaimer text [1] should be
> > present on all website pages and in announcement emails, so consumers
> > are clear about the status of the software.
> >
> > However there are quite a few podlings where the text is only present
> > on some of the web pages, and most announce emails don't include the
> > disclaimer.
> >
> > Note that unlike licensing issues, which can be sorted out during
> > incubation, this is something that must be addressed from the very
> > beginning.
> >
> > Sebb
> > [1] https://incubator.apache.org/guides/branding.html#disclaimers
> >
> > -
> > 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: Missing Incubator disclaimer text

[sebb]

On Wed, 24 Apr 2024 at 13:05, tison  wrote:
>
> Hi Sebb,
>
> > quite a few podlings where the text is only present on some of the web
> pages
>
> [1] you refers writes:
>
> >> Podling web sites MUST include a clear disclaimer on their website
>
> So, IMO it's clear that every page should contain such info (typically as
> part of the footer). If you find any podling violates this policy, you can
> name them and I'd like to give a look.
>
> For the podlings I participate in, I spread the docu template [2] to ensure
> that this policy is followed.
>
> [2]
> https://github.com/apache/apache-website-template/blob/f8129ca66fdff1c97e0749eb2ed319f1739f6f34/docusaurus.config.ts#L137
>
> > and in announcement emails
>
> This sounds like a new sentence to me. Have we ever had a consensus before?
> I agree that such a policy can help convey the project's status more
> clearly, and it won't be difficult to add such a section in the
> announcement email. Most of the podlings may be unaware of this point, and
> I didn't hear about this before.

The policy at [1] includes the phrase " in all documentation
(including releases) ".
The announce mail is documentation that the release has occurred.

It is vital that consumers are told up-front about the status of
incubator releases.

> Best,
> tison.
>
>
> sebb  于2024年4月24日周三 15:58写道：
>
> > My understanding is that the Incubator disclaimer text [1] should be
> > present on all website pages and in announcement emails, so consumers
> > are clear about the status of the software.
> >
> > However there are quite a few podlings where the text is only present
> > on some of the web pages, and most announce emails don't include the
> > disclaimer.
> >
> > Note that unlike licensing issues, which can be sorted out during
> > incubation, this is something that must be addressed from the very
> > beginning.
> >
> > Sebb
> > [1] https://incubator.apache.org/guides/branding.html#disclaimers
> >
> > -
> > 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

Missing Incubator disclaimer text

[sebb]

My understanding is that the Incubator disclaimer text [1] should be
present on all website pages and in announcement emails, so consumers
are clear about the status of the software.

However there are quite a few podlings where the text is only present
on some of the web pages, and most announce emails don't include the
disclaimer.

Note that unlike licensing issues, which can be sorted out during
incubation, this is something that must be addressed from the very
beginning.

Sebb
[1] https://incubator.apache.org/guides/branding.html#disclaimers

-
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

[sebb]

On Wed, 24 Apr 2024 at 08:29, Shawn Yang  wrote:
>
> Hi Sebb,
>
> I highlight that the current release is not an asf release in the install
> page in PR https://github.com/apache/incubator-fury-site/pull/113.
>
> Could you take a look at it again?

I have just looked at the PR you just raised, and it looks OK.

Note that my comment was about the published install page, which is
still as I described.

> Thanks for taking time to review Fury's release.
>
> Best regards,
> Chaokun Yang
>
> On Wed, Apr 24, 2024 at 3:20 PM sebb  wrote:
>
> > There is now a link to a potential download page, which is great.
> >
> > However, the install page does not make it obvious that the 0.4.1
> > release is not an ASF release.
> > That information should be shown prominently at the start of the page,
> > not buried in a note near the end.
> >
> > On Tue, 23 Apr 2024 at 16:07, Shawn Yang  wrote:
> > >
> > > I updated it in the PR
> > > https://github.com/apache/incubator-fury-site/pull/112. Sorry for my
> > last
> > > reply, I forgot to put the PR link.
> > >
> > > On Tue, Apr 23, 2024 at 10:22 PM sebb  wrote:
> > >
> > > > On Tue, 23 Apr 2024 at 14:05, Shawn Yang 
> > wrote:
> > > > >
> > > > > Hi Sebb,
> > > > >
> > > > > I  updated the content in the install doc and added notes that this
> > is
> > > > not
> > > > > an ASF release.
> > > > >
> > > > > And added a download page for download and verify source release
> > only.
> > > > > Currently this page is basically empty, but will be updated once this
> > > > vote
> > > > > is done, and updated
> > > > > to closer.lua according to download-scripts[1].
> > > > >
> > > > > The cross-links to each other are also added.
> > > >
> > > > I don't see these changes on the fury.apache.org website.
> > > > Are they published anywhere?
> > > >
> > > > > 1.
> > https://infra.apache.org/release-download-pages.html#download-scripts
> > > > >
> > > > > Thanks again for pointing those issues out.
> > > > >
> > > > > -
> > > > > Best Regards,
> > > > > Chaokun Yang
> > > > >
> > > > > On Tue, Apr 23, 2024 at 8:22 PM sebb  wrote:
> > > > >
> > > > > > On Tue, 23 Apr 2024 at 13:08, tison  wrote:
> > > > > > >
> > > > > > > > They could fix the page now, while waiting for the release
> > vote to
> > > > > > > complete.
> > > > > > >
> > > > > > > Make sense. At least remove the page/content now to indicate "no
> > > > Apache
> > > > > > > release" now. Then it won't be some "forth and back" updates.
> > It's a
> > > > > > timing
> > > > > > > issue.
> > > > > > >
> > > > > > > > Note that the page needs more than just an update to version
> > > > numbers.
> > > > > > > > It needs closer.lua links to the source bundle, links to KEYS,
> > sigs
> > > > > > > > and hashes, and verification instructions.
> > > > > > >
> > > > > > > Such an install page can be a simplified quick start page. I
> > suppose
> > > > you
> > > > > > > refer to a download page like [1].
> > > > > > >
> > > > > > > [1] https://hadoop.apache.org/releases.html
> > > > > >
> > > > > > Yes, though ideally use closer.lua rather than closer.cgi.
> > > > > >
> > > > > > > And yes, Fury doesn't have a download page yet, and they should
> > add
> > > > one.
> > > > > >
> > > > > > Agreed.
> > > > > >
> > > > > > > But in my experience it's different from a quickstart install
> > page,
> > > > like
> > > > > > > [2] vs [3].
> > > > > >
> > > > > > Yes, but that should not be at the expense of a source download
> > page.
> > > > > > It must be easy to find the source download.
> > > > > > The website and the announcement email must link to the official
> > > > 

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

[sebb]

There is now a link to a potential download page, which is great.

However, the install page does not make it obvious that the 0.4.1
release is not an ASF release.
That information should be shown prominently at the start of the page,
not buried in a note near the end.

On Tue, 23 Apr 2024 at 16:07, Shawn Yang  wrote:
>
> I updated it in the PR
> https://github.com/apache/incubator-fury-site/pull/112. Sorry for my last
> reply, I forgot to put the PR link.
>
> On Tue, Apr 23, 2024 at 10:22 PM sebb  wrote:
>
> > On Tue, 23 Apr 2024 at 14:05, Shawn Yang  wrote:
> > >
> > > Hi Sebb,
> > >
> > > I  updated the content in the install doc and added notes that this is
> > not
> > > an ASF release.
> > >
> > > And added a download page for download and verify source release only.
> > > Currently this page is basically empty, but will be updated once this
> > vote
> > > is done, and updated
> > > to closer.lua according to download-scripts[1].
> > >
> > > The cross-links to each other are also added.
> >
> > I don't see these changes on the fury.apache.org website.
> > Are they published anywhere?
> >
> > > 1. https://infra.apache.org/release-download-pages.html#download-scripts
> > >
> > > Thanks again for pointing those issues out.
> > >
> > > -
> > > Best Regards,
> > > Chaokun Yang
> > >
> > > On Tue, Apr 23, 2024 at 8:22 PM sebb  wrote:
> > >
> > > > On Tue, 23 Apr 2024 at 13:08, tison  wrote:
> > > > >
> > > > > > They could fix the page now, while waiting for the release vote to
> > > > > complete.
> > > > >
> > > > > Make sense. At least remove the page/content now to indicate "no
> > Apache
> > > > > release" now. Then it won't be some "forth and back" updates. It's a
> > > > timing
> > > > > issue.
> > > > >
> > > > > > Note that the page needs more than just an update to version
> > numbers.
> > > > > > It needs closer.lua links to the source bundle, links to KEYS, sigs
> > > > > > and hashes, and verification instructions.
> > > > >
> > > > > Such an install page can be a simplified quick start page. I suppose
> > you
> > > > > refer to a download page like [1].
> > > > >
> > > > > [1] https://hadoop.apache.org/releases.html
> > > >
> > > > Yes, though ideally use closer.lua rather than closer.cgi.
> > > >
> > > > > And yes, Fury doesn't have a download page yet, and they should add
> > one.
> > > >
> > > > Agreed.
> > > >
> > > > > But in my experience it's different from a quickstart install page,
> > like
> > > > > [2] vs [3].
> > > >
> > > > Yes, but that should not be at the expense of a source download page.
> > > > It must be easy to find the source download.
> > > > The website and the announcement email must link to the official
> > download
> > > > page.
> > > >
> > > > The download and install pages could be cross-linked.
> > > >
> > > > > [2] https://opendal.apache.org/docs/quickstart#java-binding
> > > > > [3] https://opendal.apache.org/download
> > > > >
> > > > > Best,
> > > > > tison.
> > > > >
> > > > >
> > > > > sebb  于2024年4月23日周二 20:00写道：
> > > > >
> > > > > > On Tue, 23 Apr 2024 at 12:46, tison  wrote:
> > > > > > >
> > > > > > > > I would be very disappointed if the podling published the code
> > > > > > > > *knowing* that the download page is missing or incorrect.
> > > > > > >
> > > > > > > IIUC Fury will update the content and delete all the references
> > to
> > > > prior
> > > > > > > releases.
> > > > > >
> > > > > > Note that the page needs more than just an update to version
> > numbers.
> > > > > > It needs closer.lua links to the source bundle, links to KEYS, sigs
> > > > > > and hashes, and verification instrructions.
> > > > > >
> > > > > > > Or instead, Fury can keep these references and state clearly it's
> > >

Re: [ANNOUNCE] Apache HugeGraph(incubating) 1.3.0 available

[sebb]

All pages should have the Incubation disclaimer, but especially the
home page and download page.

On Wed, 3 Apr 2024 at 17:11, sebb  wrote:
>
> On Wed, 3 Apr 2024 at 15:56, Jacky Yang  wrote:
>>
>> Hi,sebb
>>
>> The download page problem has been basically fixed.
>>
>
> There are still some errors:
> - must use closer.lua for artifacts
> - must not link to SNAPSHOT files
> - versions before 1.0 don't have hashes and sigs and don't appear to be 
> official ASF releases
> - page must have an Incubation disclaimer
>
>>
>> Download Links: https://hugegraph.apache.org/docs/download/download/
>>
>> Thanks,
>> JackyYang
>>
>>
>> sebb  于2024年4月3日周三 15:32写道：
>>>
>>> On Tue, 2 Apr 2024 at 17:11, Jacky Yang  wrote:
>>> >
>>> > Hi all,
>>> >
>>> > Apache HugeGraph (Incubating) Team is glad to announce the new release of
>>> > version 1.3.0
>>> >
>>> > HugeGraph is a fast-speed and highly-scalable distributed graph database,
>>> > it provides the basic "Graph Traverser" for OLTP query, and also support
>>> > "Graph Computing" for OLAP needs now. Our (final) goal is to provide a
>>> > one-click "Graph Service", welcome to use and give us feedback, 
>>> > participate
>>> > in research and dev.
>>> >
>>> > In this version, we have fixed some SEC-related issues. And this is the 
>>> > first
>>> > release version of hugegraph-ai, it contains a variety of features,
>>> > including an initialized Python client, knowledge graph construction
>>> > capabilities through LLM, and the integration of RAG based on HugeGraph.
>>> >
>>> >
>>> >
>>> > Download Links: https://hugegraph.apache.org/docs/download/download/
>>>
>>> The download page has some problems:
>>> - it is not clear what the first entry on the page is for, and it does
>>> not have sigs or hashes. Do not link directly to dlcdn.
>>> - artifact links must use closer.lua
>>> - there is no KEYS link
>>> - there is no information on how to verify downloads
>>>
>>> Please fix these ASAP.
>>>
>>> > Github Release Tag:
>>> > - https://github.com/apache/incubator-hugegraph/releases/tag/1.3.0
>>> > - 
>>> > https://github.com/apache/incubator-hugegraph-toolchain/releases/tag/1.3.0
>>> > - https://github.com/apache/incubator-hugegraph-ai/releases/tag/1.3.0
>>> >
>>> > Release Notes:
>>> > - 
>>> > https://hugegraph.apache.org/docs/changelog/hugegraph-1.3.0-release-notes/
>>> > (EN)
>>> > -
>>> > https://hugegraph.apache.org/cn/docs/changelog/hugegraph-1.3.0-release-notes/
>>> > (CN)
>>> >
>>> > Website: https://hugegrapgh.apache.org/
>>> >
>>> > HugeGraph Resources:
>>> > - Issue: https://github.com/apache/incubator-hugegrapgh/issues
>>> > - Mailing list: d...@hugegrapgh.apache.org
>>> >
>>> > JackyYang
>>> > On behalf of Apache HugeGraph(incubating) Team
>>> >
>>> > -
>>> > 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

[sebb]

On Tue, 23 Apr 2024 at 14:05, Shawn Yang  wrote:
>
> Hi Sebb,
>
> I  updated the content in the install doc and added notes that this is not
> an ASF release.
>
> And added a download page for download and verify source release only.
> Currently this page is basically empty, but will be updated once this vote
> is done, and updated
> to closer.lua according to download-scripts[1].
>
> The cross-links to each other are also added.

I don't see these changes on the fury.apache.org website.
Are they published anywhere?

> 1. https://infra.apache.org/release-download-pages.html#download-scripts
>
> Thanks again for pointing those issues out.
>
> -
> Best Regards,
> Chaokun Yang
>
> On Tue, Apr 23, 2024 at 8:22 PM sebb  wrote:
>
> > On Tue, 23 Apr 2024 at 13:08, tison  wrote:
> > >
> > > > They could fix the page now, while waiting for the release vote to
> > > complete.
> > >
> > > Make sense. At least remove the page/content now to indicate "no Apache
> > > release" now. Then it won't be some "forth and back" updates. It's a
> > timing
> > > issue.
> > >
> > > > Note that the page needs more than just an update to version numbers.
> > > > It needs closer.lua links to the source bundle, links to KEYS, sigs
> > > > and hashes, and verification instructions.
> > >
> > > Such an install page can be a simplified quick start page. I suppose you
> > > refer to a download page like [1].
> > >
> > > [1] https://hadoop.apache.org/releases.html
> >
> > Yes, though ideally use closer.lua rather than closer.cgi.
> >
> > > And yes, Fury doesn't have a download page yet, and they should add one.
> >
> > Agreed.
> >
> > > But in my experience it's different from a quickstart install page, like
> > > [2] vs [3].
> >
> > Yes, but that should not be at the expense of a source download page.
> > It must be easy to find the source download.
> > The website and the announcement email must link to the official download
> > page.
> >
> > The download and install pages could be cross-linked.
> >
> > > [2] https://opendal.apache.org/docs/quickstart#java-binding
> > > [3] https://opendal.apache.org/download
> > >
> > > Best,
> > > tison.
> > >
> > >
> > > sebb  于2024年4月23日周二 20:00写道：
> > >
> > > > On Tue, 23 Apr 2024 at 12:46, tison  wrote:
> > > > >
> > > > > > I would be very disappointed if the podling published the code
> > > > > > *knowing* that the download page is missing or incorrect.
> > > > >
> > > > > IIUC Fury will update the content and delete all the references to
> > prior
> > > > > releases.
> > > >
> > > > Note that the page needs more than just an update to version numbers.
> > > > It needs closer.lua links to the source bundle, links to KEYS, sigs
> > > > and hashes, and verification instrructions.
> > > >
> > > > > Or instead, Fury can keep these references and state clearly it's
> > prior
> > > > > releases.
> > > > >
> > > > > My comment above is with an assumption that prior releases ref will
> > be
> > > > > removed. But if the PPMC wants to keep it, they should update the
> > > > > description.
> > > >
> > > > They could fix the page now, while waiting for the release vote to
> > > > complete.
> > > >
> > > > > Best,
> > > > > tison.
> > > > >
> > > > >
> > > > > sebb  于2024年4月23日周二 19:35写道：
> > > > >
> > > > > > On Tue, 23 Apr 2024 at 09:42, tison  wrote:
> > > > > > >
> > > > > > > > There is no indication that 0.4.1 is not an ASF release.
> > > > > > >
> > > > > > > You may found that the group id is not org.apache.fury also.
> > > > > >
> > > > > > Whilst this is true, it is still not obvious that this is not an
> > ASF
> > > > > > release; it is easy to overlook this minor detail.
> > > > > >
> > > > > > Indeed, there is no such indication for the GoLang, Javascript or
> > Rust
> > > > > > binaries.
> > > > > >
> > > > > > > This is an intermediate state that we w

Re: Verification of download pages and links

[sebb]

On Tue, 23 Apr 2024 at 13:25, tison  wrote:
>
> Thanks for starting this thread and thanks a lot for verifying the download
> page for a lot of podlings!
>
> For previewing a staging website, with .asf.yaml config, there is a way [1]
> to do so self-served by any (P)PMC. And I agree that we should spread such
> practices to every project.
>
> [1]
> https://github.com/apache/infrastructure-asfyaml/blob/main/README.md#staging-a-web-site-preview-domain
>
> For example, to recommend every project's verifying release docs (like [2])
> have a check item to verify the (staged) download page. And instruct the RM
> to build such a staged page.
>
> [2] https://opendal.apache.org/community/committers/verify

VOTE emails will need to include:
- a link to the preview site
- checklist for reviewing the download page:
as well as the required contents of the page itself, reviewers should
check that it is easy to find the download page from the home page.

> Best,
> tison.
>
>
> sebb  于2024年4月23日周二 19:52写道：
>
> > The primary mission of the ASF is to produce open SOURCE, so it seems
> > to me that an essential part of a release is a download page with
> > properly constituted links to the source bundle and the associated
> > download verification files.
> >
> > However, no attention seems to be given to this aspect of a release,
> > vital though it is.
> >
> > Obviously, the current download page cannot be updated with the
> > details of an upcoming release, but there are ways of providing access
> > to a staging website which shows how the page will look.
> >
> > Sebb
> >
> > -
> > 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

[sebb]

On Tue, 23 Apr 2024 at 13:08, tison  wrote:
>
> > They could fix the page now, while waiting for the release vote to
> complete.
>
> Make sense. At least remove the page/content now to indicate "no Apache
> release" now. Then it won't be some "forth and back" updates. It's a timing
> issue.
>
> > Note that the page needs more than just an update to version numbers.
> > It needs closer.lua links to the source bundle, links to KEYS, sigs
> > and hashes, and verification instructions.
>
> Such an install page can be a simplified quick start page. I suppose you
> refer to a download page like [1].
>
> [1] https://hadoop.apache.org/releases.html

Yes, though ideally use closer.lua rather than closer.cgi.

> And yes, Fury doesn't have a download page yet, and they should add one.

Agreed.

> But in my experience it's different from a quickstart install page, like
> [2] vs [3].

Yes, but that should not be at the expense of a source download page.
It must be easy to find the source download.
The website and the announcement email must link to the official download page.

The download and install pages could be cross-linked.

> [2] https://opendal.apache.org/docs/quickstart#java-binding
> [3] https://opendal.apache.org/download
>
> Best,
> tison.
>
>
> sebb  于2024年4月23日周二 20:00写道：
>
> > On Tue, 23 Apr 2024 at 12:46, tison  wrote:
> > >
> > > > I would be very disappointed if the podling published the code
> > > > *knowing* that the download page is missing or incorrect.
> > >
> > > IIUC Fury will update the content and delete all the references to prior
> > > releases.
> >
> > Note that the page needs more than just an update to version numbers.
> > It needs closer.lua links to the source bundle, links to KEYS, sigs
> > and hashes, and verification instrructions.
> >
> > > Or instead, Fury can keep these references and state clearly it's prior
> > > releases.
> > >
> > > My comment above is with an assumption that prior releases ref will be
> > > removed. But if the PPMC wants to keep it, they should update the
> > > description.
> >
> > They could fix the page now, while waiting for the release vote to
> > complete.
> >
> > > Best,
> > > tison.
> > >
> > >
> > > sebb  于2024年4月23日周二 19:35写道：
> > >
> > > > On Tue, 23 Apr 2024 at 09:42, tison  wrote:
> > > > >
> > > > > > There is no indication that 0.4.1 is not an ASF release.
> > > > >
> > > > > You may found that the group id is not org.apache.fury also.
> > > >
> > > > Whilst this is true, it is still not obvious that this is not an ASF
> > > > release; it is easy to overlook this minor detail.
> > > >
> > > > Indeed, there is no such indication for the GoLang, Javascript or Rust
> > > > binaries.
> > > >
> > > > > This is an intermediate state that we would update the content as:
> > > > >
> > > > > 
> > > > >   org.apache.fury
> > > > >   fury-core
> > > > >   0.5.0
> > > > > 
> > > > >
> > > > > And then the content is correct.
> > > >
> > > > Strictly speaking the content of the Maven reference to 0.4.1 is not
> > > > 'incorrect'.
> > > > The problem is that the page does not make it clear that the release
> > > > is not an ASF release.
> > > >
> > > > It's OK to refer to prior releases, but the reader must be clearly
> > > > informed of their provenance.
> > > >
> > > > > If we make any workaround or patch to make
> > > > > it "look good", it would be updated as soon as 0.5.0 is released. So
> > I
> > > > > won't treat that as a release blocker.
> > > >
> > > > I would be very disappointed if the podling published the code
> > > > *knowing* that the download page is missing or incorrect.
> > > >
> > > > > Best,
> > > > > tison.
> > > > >
> > > > >
> > > > > sebb  于2024年4月23日周二 15:59写道：
> > > > >
> > > > > > On Mon, 22 Apr 2024 at 10:11, PJ Fanning 
> > wrote:
> > > > > > >
> > > > > > > Hi Sebb,
> > > > > > > This email thread is a vote for an RC. If this vote passes,
> > v0.5.0
> &g

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

[sebb]

On Tue, 23 Apr 2024 at 12:46, tison  wrote:
>
> > I would be very disappointed if the podling published the code
> > *knowing* that the download page is missing or incorrect.
>
> IIUC Fury will update the content and delete all the references to prior
> releases.

Note that the page needs more than just an update to version numbers.
It needs closer.lua links to the source bundle, links to KEYS, sigs
and hashes, and verification instrructions.

> Or instead, Fury can keep these references and state clearly it's prior
> releases.
>
> My comment above is with an assumption that prior releases ref will be
> removed. But if the PPMC wants to keep it, they should update the
> description.

They could fix the page now, while waiting for the release vote to complete.

> Best,
> tison.
>
>
> sebb  于2024年4月23日周二 19:35写道：
>
> > On Tue, 23 Apr 2024 at 09:42, tison  wrote:
> > >
> > > > There is no indication that 0.4.1 is not an ASF release.
> > >
> > > You may found that the group id is not org.apache.fury also.
> >
> > Whilst this is true, it is still not obvious that this is not an ASF
> > release; it is easy to overlook this minor detail.
> >
> > Indeed, there is no such indication for the GoLang, Javascript or Rust
> > binaries.
> >
> > > This is an intermediate state that we would update the content as:
> > >
> > > 
> > >   org.apache.fury
> > >   fury-core
> > >   0.5.0
> > > 
> > >
> > > And then the content is correct.
> >
> > Strictly speaking the content of the Maven reference to 0.4.1 is not
> > 'incorrect'.
> > The problem is that the page does not make it clear that the release
> > is not an ASF release.
> >
> > It's OK to refer to prior releases, but the reader must be clearly
> > informed of their provenance.
> >
> > > If we make any workaround or patch to make
> > > it "look good", it would be updated as soon as 0.5.0 is released. So I
> > > won't treat that as a release blocker.
> >
> > I would be very disappointed if the podling published the code
> > *knowing* that the download page is missing or incorrect.
> >
> > > Best,
> > > tison.
> > >
> > >
> > > sebb  于2024年4月23日周二 15:59写道：
> > >
> > > > On Mon, 22 Apr 2024 at 10:11, PJ Fanning  wrote:
> > > > >
> > > > > 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.
> > > >
> > > > If 0.5.0 is to be the first ASF release, then the Install page is very
> > > > misleading.
> > > >
> > > > There is no indication that 0.4.1 is not an ASF release.
> > > >
> > > > > 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 candida

Verification of download pages and links

[sebb]

The primary mission of the ASF is to produce open SOURCE, so it seems
to me that an essential part of a release is a download page with
properly constituted links to the source bundle and the associated
download verification files.

However, no attention seems to be given to this aspect of a release,
vital though it is.

Obviously, the current download page cannot be updated with the
details of an upcoming release, but there are ways of providing access
to a staging website which shows how the page will look.

Sebb

-
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

[sebb]

On Tue, 23 Apr 2024 at 09:42, tison  wrote:
>
> > There is no indication that 0.4.1 is not an ASF release.
>
> You may found that the group id is not org.apache.fury also.

Whilst this is true, it is still not obvious that this is not an ASF
release; it is easy to overlook this minor detail.

Indeed, there is no such indication for the GoLang, Javascript or Rust binaries.

> This is an intermediate state that we would update the content as:
>
> 
>   org.apache.fury
>   fury-core
>   0.5.0
> 
>
> And then the content is correct.

Strictly speaking the content of the Maven reference to 0.4.1 is not
'incorrect'.
The problem is that the page does not make it clear that the release
is not an ASF release.

It's OK to refer to prior releases, but the reader must be clearly
informed of their provenance.

> If we make any workaround or patch to make
> it "look good", it would be updated as soon as 0.5.0 is released. So I
> won't treat that as a release blocker.

I would be very disappointed if the podling published the code
*knowing* that the download page is missing or incorrect.

> Best,
> tison.
>
>
> sebb  于2024年4月23日周二 15:59写道：
>
> > On Mon, 22 Apr 2024 at 10:11, PJ Fanning  wrote:
> > >
> > > 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.
> >
> > If 0.5.0 is to be the first ASF release, then the Install page is very
> > misleading.
> >
> > There is no indication that 0.4.1 is not an ASF release.
> >
> > > 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://git

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

[sebb]

On Mon, 22 Apr 2024 at 10:11, PJ Fanning  wrote:
>
> 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.

If 0.5.0 is to be the first ASF release, then the Install page is very
misleading.

There is no indication that 0.4.1 is not an ASF release.

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

-
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

[sebb]

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

Re: [ANNOUNCE] Release Apache Devlake(incubating) 0.21.0-incubating

[sebb]

On Mon, 22 Apr 2024 at 03:47, Zikuan An  wrote:
>
> Hello everyone,
>
>
> The Apache Devlake(incubating) 0.21.0-incubating has been released!
>
>
> Apache DevLake is an open-source dev data platform that ingests, analyzes,
> and visualizes the fragmented data from DevOps tools to distill insights
> for engineering productivity.
>
>
> Download Links:  https://downloads.apache.org/incubator/devlake/

Sorry, but that is not a valid download page.

A download page must use closer.lua to link to thw artifacts, and must
include links to KEYS, sigs and hashes, and instructions on
validation.

Your mentors should be able to help with this.

> Changelogs:
>
> - Support circle ci as a data source for the CI/CD domain
>
> - Support opsgenie plugin
>
> - Add original_status and original_result to all CICD entities
>
> - Allow deployment webhook to push deployments to multiple repos in one
> request
> - Simplify the display of the GitHub Scope Config
>
>
> Website: https://devlake.apache.org/
>
>
> Resources:
>
> - Issue: https://github.com/apache/incubator-devlake/issues
>
> - Mailing list: d...@devlake.apache.org
>
>
> Best Regards
>
> Zikuan An

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

Re: [ANNOUNCE] Apache Answer(Incubating) v1.3.0 available

[sebb]

On Wed, 17 Apr 2024 at 16:40, LinkinStar  wrote:
>
> Hello everyone,
>
> The Apache Answer(Incubating) v1.3.0 has been released!
>
> Apache Answer is a Q&A platform software for teams at any scale.
> Whether it's a community forum, help center, or knowledge management
> platform, you can always count on Apache Answer.
>
> Download Links: https://downloads.apache.org/incubator/answer/

Sorry, but that is not a valid download page.

> Release Notes:
> https://github.com/apache/incubator-answer/releases/tag/v1.3.0
>
> Website: https://answer.apache.org/
>
> Resources:
> - Issue: https://github.com/apache/incubator-answer/issues
> - Mailing list: d...@answer.apache.org
>
> Best regards,
> LinkinStar

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

Re: [ANNOUNCE] Apache HugeGraph(incubating) 1.3.0 available

[sebb]

On Wed, 3 Apr 2024 at 15:56, Jacky Yang  wrote:

> Hi,sebb
>
> The download page problem has been basically fixed.
>
>
There are still some errors:
- must use closer.lua for artifacts
- must not link to SNAPSHOT files
- versions before 1.0 don't have hashes and sigs and don't appear to be
official ASF releases
- page must have an Incubation disclaimer


> Download Links: https://hugegraph.apache.org/docs/download/download/
>
> Thanks,
> JackyYang
>
>
> sebb  于2024年4月3日周三 15:32写道：
>
>> On Tue, 2 Apr 2024 at 17:11, Jacky Yang 
>> wrote:
>> >
>> > Hi all,
>> >
>> > Apache HugeGraph (Incubating) Team is glad to announce the new release
>> of
>> > version 1.3.0
>> >
>> > HugeGraph is a fast-speed and highly-scalable distributed graph
>> database,
>> > it provides the basic "Graph Traverser" for OLTP query, and also support
>> > "Graph Computing" for OLAP needs now. Our (final) goal is to provide a
>> > one-click "Graph Service", welcome to use and give us feedback,
>> participate
>> > in research and dev.
>> >
>> > In this version, we have fixed some SEC-related issues. And this is the
>> first
>> > release version of hugegraph-ai, it contains a variety of features,
>> > including an initialized Python client, knowledge graph construction
>> > capabilities through LLM, and the integration of RAG based on HugeGraph.
>> >
>> >
>> >
>> > Download Links: https://hugegraph.apache.org/docs/download/download/
>>
>> The download page has some problems:
>> - it is not clear what the first entry on the page is for, and it does
>> not have sigs or hashes. Do not link directly to dlcdn.
>> - artifact links must use closer.lua
>> - there is no KEYS link
>> - there is no information on how to verify downloads
>>
>> Please fix these ASAP.
>>
>> > Github Release Tag:
>> > - https://github.com/apache/incubator-hugegraph/releases/tag/1.3.0
>> > -
>> https://github.com/apache/incubator-hugegraph-toolchain/releases/tag/1.3.0
>> > - https://github.com/apache/incubator-hugegraph-ai/releases/tag/1.3.0
>> >
>> > Release Notes:
>> > -
>> https://hugegraph.apache.org/docs/changelog/hugegraph-1.3.0-release-notes/
>> > (EN)
>> > -
>> >
>> https://hugegraph.apache.org/cn/docs/changelog/hugegraph-1.3.0-release-notes/
>> > (CN)
>> >
>> > Website: https://hugegrapgh.apache.org/
>> >
>> > HugeGraph Resources:
>> > - Issue: https://github.com/apache/incubator-hugegrapgh/issues
>> > - Mailing list: d...@hugegrapgh.apache.org
>> >
>> > JackyYang
>> > On behalf of Apache HugeGraph(incubating) Team
>> >
>> > -
>> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> > For additional commands, e-mail: general-h...@incubator.apache.org
>> >
>>
>

Re: [ANNOUNCE] Apache HugeGraph(incubating) 1.3.0 available

[sebb]

On Tue, 2 Apr 2024 at 17:11, Jacky Yang  wrote:
>
> Hi all,
>
> Apache HugeGraph (Incubating) Team is glad to announce the new release of
> version 1.3.0
>
> HugeGraph is a fast-speed and highly-scalable distributed graph database,
> it provides the basic "Graph Traverser" for OLTP query, and also support
> "Graph Computing" for OLAP needs now. Our (final) goal is to provide a
> one-click "Graph Service", welcome to use and give us feedback, participate
> in research and dev.
>
> In this version, we have fixed some SEC-related issues. And this is the first
> release version of hugegraph-ai, it contains a variety of features,
> including an initialized Python client, knowledge graph construction
> capabilities through LLM, and the integration of RAG based on HugeGraph.
>
>
>
> Download Links: https://hugegraph.apache.org/docs/download/download/

The download page has some problems:
- it is not clear what the first entry on the page is for, and it does
not have sigs or hashes. Do not link directly to dlcdn.
- artifact links must use closer.lua
- there is no KEYS link
- there is no information on how to verify downloads

Please fix these ASAP.

> Github Release Tag:
> - https://github.com/apache/incubator-hugegraph/releases/tag/1.3.0
> - https://github.com/apache/incubator-hugegraph-toolchain/releases/tag/1.3.0
> - https://github.com/apache/incubator-hugegraph-ai/releases/tag/1.3.0
>
> Release Notes:
> - https://hugegraph.apache.org/docs/changelog/hugegraph-1.3.0-release-notes/
> (EN)
> -
> https://hugegraph.apache.org/cn/docs/changelog/hugegraph-1.3.0-release-notes/
> (CN)
>
> Website: https://hugegrapgh.apache.org/
>
> HugeGraph Resources:
> - Issue: https://github.com/apache/incubator-hugegrapgh/issues
> - Mailing list: d...@hugegrapgh.apache.org
>
> JackyYang
> On behalf of Apache HugeGraph(incubating) Team
>
> -
> 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: Registering a release

[sebb]

On Thu, 21 Mar 2024 at 21:45, Justin Mclean  wrote:
>
> Hi,
>
> >> You might want to remove those old releases there, as they are 
> >> automatically archived here:
> >> https://archive.apache.org/dist/incubator/sdap/
> >
> > Would that affect the closer.lua download links on our website?
>
> Yes, but it’s not needed for old releases because they presumably don’t get 
> as many downloads. See 
> https://infra.apache.org/release-distribution.html#download-links

Archived releases can still be linked from the download page, but it
should be made clear that they are no longer current.
That is not obvious from the current download page.

Rather than include current releases in the history table, it might be
clearer to use that for historic releases only, and reserve the Latest
Components for releases that are still supported.

As it stands, there are two links for each of the current releases,
which is unnecessary and potentially confusing.

> Kind Regards,
> Justin

-
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

[Sebb (Jira)]

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

Sebb commented on INCUBATOR-283:


There is some git hook code that appears to protect certain tags by default.
However, I mis-remembered and such tags are prefixed rel/, not releases/.
So the project should be able to drop the incorrect tag.

It's not clear if the asf.yaml file can change the default protections (if any) 
or merely add to them.
I've raised https://issues.apache.org/jira/browse/INFRA-25622 about the 
asf.yaml documentation.

> 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

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

[Sebb (Jira)]

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

Sebb commented on INCUBATOR-283:


release tags are supposed to be immutable, and cannot normally be deleted.
I think you will need to involve Infra to get this corrected.

> 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] Release Apache StreamPark(Incubating) 2.1.3-rc1

[sebb]

Looks good now, thanks again for the prompt attention to the issue.

On Thu, 14 Mar 2024 at 00:48, Huajie Wang  wrote:
>
> updated, All download links for archived releases use
> https://archive.apache.org/** ,  Can you please double-check? thanks a lot.
>
> Best,
> Huajie Wang
>
>
>
> sebb  于2024年3月14日周四 01:13写道：
>
> > On Wed, 13 Mar 2024 at 16:32, Huajie Wang  wrote:
> > >
> > > hi sebb:
> > >
> > > The download(https://streampark.apache.org/download) links issue has
> > been
> > > fixed and the website has been updated . Thanks for your review
> >
> > Thanks for the very prompt response.
> >
> > However, there are still some issues: all the links in the archive
> > section need to use the archive server, not just the artifacts.
> > [The links will break when the old releases are dropped from
> > downloads.a.o.]
> >
> > The page uses two different link titles for the signature files:
> > 'Sign' and 'signature'; the latter is clearer.
> > Also it would be good to use the same order for the links throughout.
> > Since signature verification is preferred, it should be first i.e (
> > signature | sha512 )
> >
> > The page is very clear and easy to use.
> >
> > >
> > > Best,
> > > Huajie Wang
> > >
> > >
> > >
> > > sebb  于2024年3月13日周三 22:50写道：
> > >
> > > > Not a blocker for the release per se, but the links for the hashes and
> > > > sigs on the download page:
> > > > https://streampark.apache.org/download
> > > > are wrong.
> > > > Only the artifacts should use closer.lua; sigs and hashes must link
> > > > directly to downloads.apache.org,
> > > > e.g.
> > > >
> > > >
> > https://downloads.apache.org/incubator/streampark/2.1.2/apache-streampark-2.1.2-incubating-src.tar.gz.asc
> > > >
> > > > Also note that only releases that are still supported should remain on
> > > > downloads.a.o.
> > > > Archived releases can be linked from the download page, but should use
> > > > the ASF archive server at:
> > > > https://archive.apache.org/dist/incubator/streampark/
> > > > [Fix the download page links before deleting the old releases!]
> > > >
> > > > Is release 2.1.2 archived or current?
> > > > It's a bit confusing to have it under both sections of the page.
> > > >
> > > > Please fix the download page before publishing the new release.
> > > > Thanks!
> > > >
> > > > On Wed, 13 Mar 2024 at 14:38, Jean-Baptiste Onofré 
> > > > wrote:
> > > > >
> > > > > +1 (binding)
> > > > >
> > > > > I checked:
> > > > > - incubating in the name
> > > > > - signature and checksum are good
> > > > > - ASF header is present
> > > > > - No unexpected binary files in the source distribution
> > > > > - LICENSE, NOTICE, DISCLAIMER are there
> > > > >
> > > > > NB: are we sure about SECURITY.md file ? Versions in this file look
> > > > weird.
> > > > >
> > > > > Regards
> > > > > JB
> > > > >
> > > > > On Tue, Mar 12, 2024 at 2:45 PM Qingrong wang 
> > > > wrote:
> > > > > >
> > > > > > Hello Incubator Community:
> > > > > >
> > > > > > This is a call for a vote to release Apache StreamPark(Incubating)
> > > > > > version 2.1.3-RC1.
> > > > > > The Apache StreamPark community has voted on and approved a
> > proposal
> > > > > > to release Apache StreamPark(Incubating) version 2.1.3-RC1.
> > > > > > We now kindly request the Incubator PMC members review and vote on
> > > > > > this incubator release.
> > > > > > Apache StreamPark, Make stream processing easier! Easy-to-use
> > > > > > streaming application development framework and operation platform.
> > > > > >
> > > > > > StreamPark community vote thread:
> > > > > > https://lists.apache.org/thread/l4dd4j70wp7rz40fm2nf2o3fwt5x0zr6
> > > > > >
> > > > > > Vote result thread:
> > > > > > https://lists.apache.org/thread/8vd90kxwdvqtkqbtng7jg0mdzscc46xl
> > > > > >
> > > > > > The release candidate:
&

Re: [VOTE] Release Apache StreamPark(Incubating) 2.1.3-rc1

[sebb]

On Wed, 13 Mar 2024 at 16:32, Huajie Wang  wrote:
>
> hi sebb:
>
> The download(https://streampark.apache.org/download) links issue has been
> fixed and the website has been updated . Thanks for your review

Thanks for the very prompt response.

However, there are still some issues: all the links in the archive
section need to use the archive server, not just the artifacts.
[The links will break when the old releases are dropped from downloads.a.o.]

The page uses two different link titles for the signature files:
'Sign' and 'signature'; the latter is clearer.
Also it would be good to use the same order for the links throughout.
Since signature verification is preferred, it should be first i.e (
signature | sha512 )

The page is very clear and easy to use.

>
> Best,
> Huajie Wang
>
>
>
> sebb  于2024年3月13日周三 22:50写道：
>
> > Not a blocker for the release per se, but the links for the hashes and
> > sigs on the download page:
> > https://streampark.apache.org/download
> > are wrong.
> > Only the artifacts should use closer.lua; sigs and hashes must link
> > directly to downloads.apache.org,
> > e.g.
> >
> > https://downloads.apache.org/incubator/streampark/2.1.2/apache-streampark-2.1.2-incubating-src.tar.gz.asc
> >
> > Also note that only releases that are still supported should remain on
> > downloads.a.o.
> > Archived releases can be linked from the download page, but should use
> > the ASF archive server at:
> > https://archive.apache.org/dist/incubator/streampark/
> > [Fix the download page links before deleting the old releases!]
> >
> > Is release 2.1.2 archived or current?
> > It's a bit confusing to have it under both sections of the page.
> >
> > Please fix the download page before publishing the new release.
> > Thanks!
> >
> > On Wed, 13 Mar 2024 at 14:38, Jean-Baptiste Onofré 
> > wrote:
> > >
> > > +1 (binding)
> > >
> > > I checked:
> > > - incubating in the name
> > > - signature and checksum are good
> > > - ASF header is present
> > > - No unexpected binary files in the source distribution
> > > - LICENSE, NOTICE, DISCLAIMER are there
> > >
> > > NB: are we sure about SECURITY.md file ? Versions in this file look
> > weird.
> > >
> > > Regards
> > > JB
> > >
> > > On Tue, Mar 12, 2024 at 2:45 PM Qingrong wang 
> > wrote:
> > > >
> > > > Hello Incubator Community:
> > > >
> > > > This is a call for a vote to release Apache StreamPark(Incubating)
> > > > version 2.1.3-RC1.
> > > > The Apache StreamPark community has voted on and approved a proposal
> > > > to release Apache StreamPark(Incubating) version 2.1.3-RC1.
> > > > We now kindly request the Incubator PMC members review and vote on
> > > > this incubator release.
> > > > Apache StreamPark, Make stream processing easier! Easy-to-use
> > > > streaming application development framework and operation platform.
> > > >
> > > > StreamPark community vote thread:
> > > > https://lists.apache.org/thread/l4dd4j70wp7rz40fm2nf2o3fwt5x0zr6
> > > >
> > > > Vote result thread:
> > > > https://lists.apache.org/thread/8vd90kxwdvqtkqbtng7jg0mdzscc46xl
> > > >
> > > > The release candidate:
> > > > https://dist.apache.org/repos/dist/dev/incubator/streampark/2.1.3-RC1/
> > > >
> > > > Git tag for the release:
> > > > https://github.com/apache/incubator-streampark/releases/tag/v2.1.3-rc1
> > > >
> > > > The artifacts signed with PGP key [40EE71A2], corresponding
> > > > to[monr...@apache.org], that can be found in keys file:
> > > > https://downloads.apache.org/incubator/streampark/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 with the reason
> > > >
> > > > More detailed checklist please refer:
> > > > •
> > https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> > > >
> > > > Steps to validate the release， Please refer to:
> > > > • https://www.apache.org/info/verification.html
> > > > •
> > https://streampark.apache.org/community/release/how_

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

[sebb]

On Tue, 12 Mar 2024 at 21:27, Craig Russell  wrote:
>
> Hi Sebb,
>
> How many person-hours are wasted by podlings and their Mentors who read the 
> guidance and have to think about podling.yml and 
> podling.incubator.apache.org? And how and whether to change it after 
> graduation?
>
> I'm trying to make it easier to follow the rules and not think about random 
> requirements that serve no purpose.

AIUI the purpose of the requirement is to reinforce the fact that
podlings are not fully adopted by the ASF.

This is not a 'random' requirement; it seems sensible to me,
especially when podlings often fail to add the Incubator disclaimer to
all their pages.

==

The solution to the Whimsy warnings is simple. No need to change any
processes, just use the correct website URL in the YAML file.

I'm unclear as to what else is regarded as a problem, and what else
you think needs changing when a podling graduates?

Also, is this a decision that is in scope for the Incubator, or is M&P
or branding approval needed?

Further, Infra may need to make some changes if the policy is changed.

> Craig
>
> > On Mar 12, 2024, at 13:57, sebb  wrote:
> >
> > Whimsy gets the URL from content/podlings/.yml
> >
> > It looks like all that is needed to fix Whimsy is to ensure the
> > correct value is used for :website:
> > This is a one-off change; AFAIK it does not need to be changed after 
> > graduation.
> >
> > AFAICT, all the podling websites are equally accessible via
> > podling.a.o and podling.incubator.a.o
> >
> > I suggest fixing the podling yml files.
> >
> > On Tue, 12 Mar 2024 at 20:32, Gordon  wrote:
> >>
> >> +1 (binding), thanks.
> >>
> >> On Tue, Mar 12, 2024 at 11:37 AM 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
> >
>
> 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: [VOTE] Release Apache StreamPark(Incubating) 2.1.3-rc1

[sebb]

Not a blocker for the release per se, but the links for the hashes and
sigs on the download page:
https://streampark.apache.org/download
are wrong.
Only the artifacts should use closer.lua; sigs and hashes must link
directly to downloads.apache.org,
e.g.
https://downloads.apache.org/incubator/streampark/2.1.2/apache-streampark-2.1.2-incubating-src.tar.gz.asc

Also note that only releases that are still supported should remain on
downloads.a.o.
Archived releases can be linked from the download page, but should use
the ASF archive server at:
https://archive.apache.org/dist/incubator/streampark/
[Fix the download page links before deleting the old releases!]

Is release 2.1.2 archived or current?
It's a bit confusing to have it under both sections of the page.

Please fix the download page before publishing the new release.
Thanks!

On Wed, 13 Mar 2024 at 14:38, Jean-Baptiste Onofré  wrote:
>
> +1 (binding)
>
> I checked:
> - incubating in the name
> - signature and checksum are good
> - ASF header is present
> - No unexpected binary files in the source distribution
> - LICENSE, NOTICE, DISCLAIMER are there
>
> NB: are we sure about SECURITY.md file ? Versions in this file look weird.
>
> Regards
> JB
>
> On Tue, Mar 12, 2024 at 2:45 PM Qingrong wang  wrote:
> >
> > Hello Incubator Community:
> >
> > This is a call for a vote to release Apache StreamPark(Incubating)
> > version 2.1.3-RC1.
> > The Apache StreamPark community has voted on and approved a proposal
> > to release Apache StreamPark(Incubating) version 2.1.3-RC1.
> > We now kindly request the Incubator PMC members review and vote on
> > this incubator release.
> > Apache StreamPark, Make stream processing easier! Easy-to-use
> > streaming application development framework and operation platform.
> >
> > StreamPark community vote thread:
> > https://lists.apache.org/thread/l4dd4j70wp7rz40fm2nf2o3fwt5x0zr6
> >
> > Vote result thread:
> > https://lists.apache.org/thread/8vd90kxwdvqtkqbtng7jg0mdzscc46xl
> >
> > The release candidate:
> > https://dist.apache.org/repos/dist/dev/incubator/streampark/2.1.3-RC1/
> >
> > Git tag for the release:
> > https://github.com/apache/incubator-streampark/releases/tag/v2.1.3-rc1
> >
> > The artifacts signed with PGP key [40EE71A2], corresponding
> > to[monr...@apache.org], that can be found in keys file:
> > https://downloads.apache.org/incubator/streampark/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 with the reason
> >
> > More detailed checklist please refer:
> > • 
> > https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> >
> > Steps to validate the release， Please refer to:
> > • https://www.apache.org/info/verification.html
> > • https://streampark.apache.org/community/release/how_to_verify_release
> >
> >
> > How to Build:
> >
> > 1) clone source code:
> > > git clone -b v2.1.3-rc1 g...@github.com:apache/incubator-streampark.git
> >
> > 2) build project:
> > > cd incubator-streampark && sh ./build.sh
> >
> >
> > Thanks,
> >
> > On behalf of Apache StreamPark(Incubating) community
> >
> >
> > Best,
> > Qingrong Wang
> >
> > -
> > 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] Podling web sites: make (incubator.) optional in podling urls

[sebb]

Whimsy gets the URL from content/podlings/.yml

It looks like all that is needed to fix Whimsy is to ensure the
correct value is used for :website:
This is a one-off change; AFAIK it does not need to be changed after graduation.

AFAICT, all the podling websites are equally accessible via
podling.a.o and podling.incubator.a.o

I suggest fixing the podling yml files.

On Tue, 12 Mar 2024 at 20:32, Gordon  wrote:
>
> +1 (binding), thanks.
>
> On Tue, Mar 12, 2024 at 11:37 AM 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: [VOTE] Release Apache Pekko, incubating, Sbt Paradox 1.0.1-RC2

[sebb]

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

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

[sebb]

On Fri, 8 Mar 2024 at 22: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

The KEYS file must be linked from

https://downloads.apache.org/incubator/sdap/KEYS

The dist.apache.org host is for staging the files, not for general publication.


> 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&search=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

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

[sebb]

Thanks, that looks better.

===

By the way, the Incubation disclaimer should have been present on all
pages (not just the main ones).
Probably too late for that now, but if graduation fails it should be fixed.

Also, there is no way back to the main page from the doc/ pages.
Not a blocker for graduation, but it does make the site harder to navigate.

On Thu, 7 Mar 2024 at 10:15, Jingsong Li  wrote:
>
> Thanks sebb.
>
> Learn a lot.
> - tar link should use closer.lua.
> - digest and pgp links must use downloads.apache.org
>
> I have updated:
> https://paimon.apache.org/downloads/
>
> Best,
> Jingsong
>
> On Thu, Mar 7, 2024 at 5:02 PM sebb  wrote:
> >
> > I've just noticed that the download page tar links are not correct after 
> > all.
> >
> > They must use closer.lua, but they don't.
> >
> > On Wed, 6 Mar 2024 at 08:42, sebb  wrote:
> > >
> > > Thanks for attending to this promptly.
> > >
> > > Page looks good now.
> > >
> > > On Wed, 6 Mar 2024 at 04:43, Jingsong Li  wrote:
> > > >
> > > > Hi sebb,
> > > >
> > > > Thanks for your check.
> > > >
> > > > I have updated the website: https://paimon.apache.org/downloads/
> > > > (You may need to refresh to see the latest page)
> > > >
> > > > 1. [done] the digest and pgp links must use downloads.apache.org
> > > > 2. [done] information on how to use the digests.
> > > > 3. [done] The download page should not link to GitHub commits; they
> > > > are not official releases.
> > > > 4. [done] Releases that are no longer maintained should be removed
> > > > from downloads.a.o. They can still be linked from the archives.
> > > > 5. [done] It should be obvious which release(s) are currently 
> > > > recommended
> > > >
> > > > Best,
> > > > Jingsong
> > > >
> > > > On Wed, Mar 6, 2024 at 12:37 PM Jingsong Li  
> > > > wrote:
> > > > >
> > > > > Hi Justin,
> > > > >
> > > > > Thank you for pointing it out.
> > > > >
> > > > > > Please do not refer to anyone as a founder of an Apache project.
> > > > >
> > > > > I will deny and explain as soon as possible, and I will inform the 
> > > > > PPMC members of the Paimon community offline.
> > > > >
> > > > > > " from Ververica” [2] is not accurate, again the community runs a 
> > > > > > project not a company
> > > > >
> > > > > I will contact the author of this article to inform him that this 
> > > > > inaccurate statement should not be used.
> > > > >
> > > > > Best,
> > > > > Jingsong
> > > > >
> > > > > On Wed, Mar 6, 2024 at 9:06 AM Justin Mclean 
> > > > >  wrote:
> > > > > >
> > > > > > HI,
> > > > > >
> > > > > > In your discussion on graduation, you refer to the proposed chair 
> > > > > > as “the founder of Paimon”. While this person may have come up with 
> > > > > > the initial design before it was an Apache project, the project is 
> > > > > > run by the community. Please do not refer to anyone as a founder of 
> > > > > > an Apache project. I have noticed this language used in other 
> > > > > > places as well e.g. [1]  Also stating an Apache project is from a 
> > > > > > company e.g " from Ververica” [2] is not accurate, again the 
> > > > > > community runs a project not a company. If possible the PPMC should 
> > > > > > look into getting this corrected.
> > > > > >
> > > > > > Kind Regards,
> > > > > > Justin
> > > > > >
> > > > > > 1. https://www.youtube.com/watch?v=AdRuYgtbzrQ
> > > > > > 2. https://www.youtube.com/watch?v=7cD7eFzaNew
> > > > > > -
> > > > > > 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
>

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

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

[sebb]

I've just noticed that the download page tar links are not correct after all.

They must use closer.lua, but they don't.

On Wed, 6 Mar 2024 at 08:42, sebb  wrote:
>
> Thanks for attending to this promptly.
>
> Page looks good now.
>
> On Wed, 6 Mar 2024 at 04:43, Jingsong Li  wrote:
> >
> > Hi sebb,
> >
> > Thanks for your check.
> >
> > I have updated the website: https://paimon.apache.org/downloads/
> > (You may need to refresh to see the latest page)
> >
> > 1. [done] the digest and pgp links must use downloads.apache.org
> > 2. [done] information on how to use the digests.
> > 3. [done] The download page should not link to GitHub commits; they
> > are not official releases.
> > 4. [done] Releases that are no longer maintained should be removed
> > from downloads.a.o. They can still be linked from the archives.
> > 5. [done] It should be obvious which release(s) are currently recommended
> >
> > Best,
> > Jingsong
> >
> > On Wed, Mar 6, 2024 at 12:37 PM Jingsong Li  wrote:
> > >
> > > Hi Justin,
> > >
> > > Thank you for pointing it out.
> > >
> > > > Please do not refer to anyone as a founder of an Apache project.
> > >
> > > I will deny and explain as soon as possible, and I will inform the PPMC 
> > > members of the Paimon community offline.
> > >
> > > > " from Ververica” [2] is not accurate, again the community runs a 
> > > > project not a company
> > >
> > > I will contact the author of this article to inform him that this 
> > > inaccurate statement should not be used.
> > >
> > > Best,
> > > Jingsong
> > >
> > > On Wed, Mar 6, 2024 at 9:06 AM Justin Mclean  
> > > wrote:
> > > >
> > > > HI,
> > > >
> > > > In your discussion on graduation, you refer to the proposed chair as 
> > > > “the founder of Paimon”. While this person may have come up with the 
> > > > initial design before it was an Apache project, the project is run by 
> > > > the community. Please do not refer to anyone as a founder of an Apache 
> > > > project. I have noticed this language used in other places as well e.g. 
> > > > [1]  Also stating an Apache project is from a company e.g " from 
> > > > Ververica” [2] is not accurate, again the community runs a project not 
> > > > a company. If possible the PPMC should look into getting this corrected.
> > > >
> > > > Kind Regards,
> > > > Justin
> > > >
> > > > 1. https://www.youtube.com/watch?v=AdRuYgtbzrQ
> > > > 2. https://www.youtube.com/watch?v=7cD7eFzaNew
> > > > -
> > > > 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 Celeborn (Incubating) as a Top Level Project

[sebb]

Thanks, looks good now

On Wed, 6 Mar 2024 at 05:44, rexxiong  wrote:
>
> Thank you for sebb's suggestion, the download page has been updated.
>
> Thanks,
> Jiashu Xiong
>
> Cheng Pan  于2024年3月6日周三 11:39写道：
>
> > +1 (non-binding)
> >
> > Thanks,
> > Cheng Pan
> >
> >
> > > On Mar 5, 2024, at 14:00, 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

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

[sebb]

Thanks for attending to this promptly.

Page looks good now.

On Wed, 6 Mar 2024 at 04:43, Jingsong Li  wrote:
>
> Hi sebb,
>
> Thanks for your check.
>
> I have updated the website: https://paimon.apache.org/downloads/
> (You may need to refresh to see the latest page)
>
> 1. [done] the digest and pgp links must use downloads.apache.org
> 2. [done] information on how to use the digests.
> 3. [done] The download page should not link to GitHub commits; they
> are not official releases.
> 4. [done] Releases that are no longer maintained should be removed
> from downloads.a.o. They can still be linked from the archives.
> 5. [done] It should be obvious which release(s) are currently recommended
>
> Best,
> Jingsong
>
> On Wed, Mar 6, 2024 at 12:37 PM Jingsong Li  wrote:
> >
> > Hi Justin,
> >
> > Thank you for pointing it out.
> >
> > > Please do not refer to anyone as a founder of an Apache project.
> >
> > I will deny and explain as soon as possible, and I will inform the PPMC 
> > members of the Paimon community offline.
> >
> > > " from Ververica” [2] is not accurate, again the community runs a project 
> > > not a company
> >
> > I will contact the author of this article to inform him that this 
> > inaccurate statement should not be used.
> >
> > Best,
> > Jingsong
> >
> > On Wed, Mar 6, 2024 at 9:06 AM Justin Mclean  
> > wrote:
> > >
> > > HI,
> > >
> > > In your discussion on graduation, you refer to the proposed chair as “the 
> > > founder of Paimon”. While this person may have come up with the initial 
> > > design before it was an Apache project, the project is run by the 
> > > community. Please do not refer to anyone as a founder of an Apache 
> > > project. I have noticed this language used in other places as well e.g. 
> > > [1]  Also stating an Apache project is from a company e.g " from 
> > > Ververica” [2] is not accurate, again the community runs a project not a 
> > > company. If possible the PPMC should look into getting this corrected.
> > >
> > > Kind Regards,
> > > Justin
> > >
> > > 1. https://www.youtube.com/watch?v=AdRuYgtbzrQ
> > > 2. https://www.youtube.com/watch?v=7cD7eFzaNew
> > > -
> > > 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 Celeborn (Incubating) as a Top Level Project

[sebb]

On Tue, 5 Mar 2024 at 15:53, rexxiong  wrote:
>
> Thanks sebb. I have created a PR to fix the download links.
>
> https://github.com/apache/incubator-celeborn-website/pull/41
>
> For older, non-maintained releases, we have already removed from
> downloads.apache.org.

Thanks, but until such time as the download page is updated, the links
are broken.

Not worth fixing that now, but in future I suggest fixing any
reference before removing the files to which they refer.

> Thanks,
> Jiashu Xiong
>
> sebb  于2024年3月5日周二 18:13写道：
>
> > The download page on the website has some issues.
> > https://celeborn.apache.org/download/
> >
> > Links to artifacts must use closer.lua
> >
> > Links to sigs and hashes must use downloads.apache.org not
> > dlcdn.apache.org.
> >
> > There should be a link entitled KEYS.
> >
> > Older, non-maintained releases should be removed from downloads.apache.org
> > .
> > They can still be linked from the archives.
> >
> > https://infra.apache.org/release-download-pages.html
> >
> > On Tue, 5 Mar 2024 at 08:36, angers zhu  wrote:
> > >
> > > +1 (non-binding)
> > >
> > > Best Regards
> > > Angerszh
> > >
> > > Nicholas  于2024年3月5日周二 15:34写道：
> > >
> > > > +1 (non-binding)
> > > >
> > > > Forward to graduation of Celeborn.
> > > >
> > > > Regards,Nicholas Jiang
> > > >
> > > >
> > > > At 2024-03-05 14: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.
> > > &

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

[sebb]

There are some issues with the download page:

https://paimon.apache.org/downloads/

The tar links are fine, but the digest and pgp links must use
downloads.apache.org, not dlcdn.

There is no information on how to use the digests.

The download page should not link to GitHub commits; they are not
official releases.
Such links should be limited to pages aimed at developers, not the
general public.

Releases that are no longer maintained should be removed from
downloads.a.o. They can still be linked from the archives.

It should be obvious which release(s) are currently recommended.
That is not clear from the page.

See
https://infra.apache.org/release-download-pages.html

On Tue, 5 Mar 2024 at 07:41, yu zelin  wrote:
>
> +1 (non-binding)
>
> Thanks for driving it! I’m looking forward to the graduation of Paimon.
>
> Best Regards,
> Zelin Yu
>
> > 2024年3月5日 14:56，Yu Li  写道：
> >
> > Hi All,
> >
> > About one year ago, we started the discussion to donate Flink Table
> > Store, a sub-project of Apache Flink developed for one year, into the
> > incubator as Apache Paimon, with the purpose to build a more vibrant
> > and neutral community [1] [2]. Since then, with the help of the
> > incubator, we've made significant progress and achieved more than we
> > expected for incubation. Today, besides Flink, Paimon has native
> > support for many other engines such as Spark and Hive, and becomes a
> > really diverse community.
> >
> > Recently, after thorough discussions [3] [4], the community has voted
> > [5] that we would like to proceed with graduation [6]. 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 18 committers (including
> > mentors) from ~10 different companies, with 11 serving as PPMC members
> > [7].
> > - So far, we have boasted 132 contributors.
> > - Throughout the incubation period, we've made 5 releases [2] 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 [8].
> > - As yet, we have opened 1,363 issues with 1,083 successfully resolved
> > [9] [10], 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 [11].
> > - Through self-assessment [12], we have met all maturity criteria as
> > outlined in [13].
> >
> > We've resolved all branding issues which include Logo, GitHub repo,
> > document, website, and others [14] [15].
> >
> > 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, Robert Metzger, Stephan Ewen and Yu Li!
> >
> > ---
> >
> > 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 as the chair of the Apache Paimon
> > Project, and to have primary responsibility for management of the
> > projects within the scope of responsibility of the Apache Paimon
> > 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 Paimon Project:
> >
> > * Becket Qin 
> > * Caizhi Weng 
> > * Fang Yong 
> > * Feng Wang 
> > * Jingsong Lee 
> > * Nicholas Jiang 
> > * Robert Metzger 
> > * Stephan Ewen 
> > * Timo Walther 
> > * Yann Byron (Bi Yan) 
> > * Yu Li 
> > * Zelin Yu 
> >
> > NOW, THEREFORE, BE IT 

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

[sebb]

The download page on the website has some issues.
https://celeborn.apache.org/download/

Links to artifacts must use closer.lua

Links to sigs and hashes must use downloads.apache.org not dlcdn.apache.org.

There should be a link entitled KEYS.

Older, non-maintained releases should be removed from downloads.apache.org.
They can still be linked from the archives.

https://infra.apache.org/release-download-pages.html

On Tue, 5 Mar 2024 at 08:36, angers zhu  wrote:
>
> +1 (non-binding)
>
> Best Regards
> Angerszh
>
> Nicholas  于2024年3月5日周二 15:34写道：
>
> > +1 (non-binding)
> >
> > Forward to graduation of Celeborn.
> >
> > Regards,Nicholas Jiang
> >
> >
> > At 2024-03-05 14: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
> > >Ce

Re: Podling web sites: .incubator. required?

[sebb]

On Wed, 28 Feb 2024 at 15:41, PJ Fanning  wrote:
>
> +1 binding
> Formalises what most podlings are doing anyway.

Not so, according to the podling analysis:

https://whimsy.apache.org/pods/check/uri

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

-
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

[sebb]

Great, thanks for the very prompt fix!

On Wed, 28 Feb 2024 at 10:35, PJ Fanning  wrote:
>
> 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. Th

Re: Podling web sites: .incubator. required?

[sebb]

On Wed, 28 Feb 2024 at 03:28, Xuanwo  wrote:
>
> +1 non-binding
>
> Switching domains and mailing lists requires significant additional effort 
> from the PPMC and INFRA.

I agree that switching mailing lists is a lot of effort.

However, very little effort is needed to switch domains, as redirects
take care of that.
There may be some documentation changes needed, but they can be
largely automated (and can be done piecemeal).

>  I recommand all podling use http://podling.apache.org/ at the very first.

https would be better.

> On Wed, Feb 28, 2024, at 08:16, Craig Russell wrote:
> > It was policy at one point for podlings to have .incubator. in their
> > home page url. But many podlings now have transitioned away from this
> > and simply use their podling.apache.org name. The policy document is a
> > bit iffy on the subject:
> > https://incubator.apache.org/guides/branding.html
> >
> >> After a podling has been approved, the lists are created, and the initial 
> >> code drop has commenced, you MUST refer to the podling as Apache 
> >> Podling-Name AND mention that the project is under Incubation. Suitable 
> >> mentions include:
> >>
> >>  • Inclusion of the http://podling-name.incubator.apache.org/ URL
> >>
> >>  • Apache Podling-Name is currently undergoing Incubation at the 
> >> Apache Software Foundation.
> >>
> >> The Incubator PMC (IPMC) must approve other references before you publish 
> >> them. You only need to make these statements upon the first reference to 
> >> the podling in a document.
> >
> > I feel this is very much like the former requirement for mail lists to
> > include incubator.apache.org as part of their name. This turned out to
> > be a huge waste of time for the podling as well as for infra when upon
> > graduation all of the documentation and tooling for mail lists had to
> > change.
> >
> > I would propose that as part of our official policy we recommend the
> > podling's url as https://podling.apache.org and get rid of the
> > .incubator. in the url.
> >
> > WDYT?
> >
> > Craig L Russell
> > c...@apache.org
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
>
> --
> Xuanwo
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

-
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

[sebb]

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 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]).
> > > > > >>>
> 

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

[sebb]

On Tue, 27 Feb 2024 at 18:45, PJ Fanning  wrote:
>
> Thanks Sebastian. We have an issue already open [1]. We will try to
> fix it as soon as possible but it could take a week or two. I'll
> contact people to see if we can get this moving. The calls are built
> in via some build tooling that we use (called Paradox). Paradox is
> very modular so we will first have to track down the module that is
> adding this and seeing what can be done to remove the call (whether it
> is parameterised or if we will need to patch or fork the module).
>
> My experience with the calls to api.github.com is that it does not
> appear that the auth details are sent. The calls quickly start getting
> rejected because they are not authenticated. I use GitHub all the time
> but the fact that I am logged in in other browser tabs does not appear
> to cause my auth details to be sent with the Pekko web site visits.

FTR, the issue is not that auth details are sent to a 3rd party site.
Rather, it is the mere fact of the user's browser automatically
visiting the site without the explicit consent of the user.

> We still need to get rid of this and I will ensure that this is
> treated as a high priority.

Thanks

> [1] https://github.com/apache/incubator-pekko-sbt-paradox/issues/110
>
> On Tue, 27 Feb 2024 at 18:40, sebb  wrote:
> >
> > The website accesses 3rd party resources (api.github.com).
> > As far as know, this is contrary to the privacy policy.
> >
> > On Tue, 27 Feb 2024 at 16:39, tison  wrote:
> > >
> > > +1 (binding)
> > >
> > > Let's rock.
> > >
> > > Best,
> > > tison.
> > >
> > > Craig Russell  于2024年2月28日周三 00:37写道：
> > > >
> > > > +1 for graduation (binding)
> > > >
> > > > It's a good sign for you to take care of the KEYS and TM so quickly!
> > > > Craig
> > > >
> > > > > On Feb 26, 2024, at 09:41, PJ Fanning  wrote:
> > > > >
> > > > > Thanks Craig. I have created a PR to fix the KEYS link and add 'tm' to
> > > > > Apache Pekko on the main page.
> > > > >
> > > > > https://github.com/apache/incubator-pekko-site/pull/87
> > > > >
> > > > >
> > > > > On Mon, 26 Feb 2024 at 18:14, Craig Russell  
> > > > > wrote:
> > > > >>
> > > > >> Hi,
> > > > >>
> > > > >> I noticed a few items that may be problematic if not resolved before 
> > > > >> the board votes on the resolution:
> > > > >>
> > > > >> 1. The home page https://pekko.apache.org has Apache Pekko in the 
> > > > >> first prominent usage but does not use a TM symbol as in Apache 
> > > > >> Pekko™.
> > > > >> 2. The downloads page https://pekko.apache.org/download.html KEYS 
> > > > >> file for verifying checksums should link to the dist.apache.org file 
> > > > >> not the source repository.
> > > > >> https://dist.apache.org/repos/dist/release/incubator/pekko/KEYS
> > > > >> Of course, this should link to the non-incubator file once you have 
> > > > >> a release as a TLP.
> > > > >>
> > > > >> Other than that, looks good.
> > > > >>
> > > > >> Good luck,
> > > > >> Craig
> > > > >>
> > > > >>> On Feb 26, 2024, at 03:24, PJ Fanning  wrote:
> > > > >>>
> > > > >>> Hi everyone,
> > > > >>>
> > > > >>> We have positive feedback on the Pekko Vote thread [1] (result [2]).
> > > > >>>
> > > > >>> I'd like to start an official Incubator VOTE thread now.
> > > > >>>
> > > > >>> Below are some facts and project highlights from the incubation 
> > > > >>> phase
> > > > >>> as well as the draft resolution:
> > > > >>>
> > > > >>> * All modules have at least a v1.0.0 release
> > > > >>> * 19 releases (across 12 modules) [3]
> > > > >>> * Evidence of good uptake of the Pekko releases and a large number 
> > > > >>> of
> > > > >>> ecosystem libs now support Pekko - over 100 non Apache libraries use
> > > > >>> Pekko libs under the hood
> > > > >>> * well over 1000 PRs merged
> > > 

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

[sebb]

The website accesses 3rd party resources (api.github.com).
As far as know, this is contrary to the privacy policy.

On Tue, 27 Feb 2024 at 16:39, tison  wrote:
>
> +1 (binding)
>
> Let's rock.
>
> Best,
> tison.
>
> Craig Russell  于2024年2月28日周三 00:37写道：
> >
> > +1 for graduation (binding)
> >
> > It's a good sign for you to take care of the KEYS and TM so quickly!
> > Craig
> >
> > > On Feb 26, 2024, at 09:41, PJ Fanning  wrote:
> > >
> > > Thanks Craig. I have created a PR to fix the KEYS link and add 'tm' to
> > > Apache Pekko on the main page.
> > >
> > > https://github.com/apache/incubator-pekko-site/pull/87
> > >
> > >
> > > On Mon, 26 Feb 2024 at 18:14, Craig Russell  wrote:
> > >>
> > >> Hi,
> > >>
> > >> I noticed a few items that may be problematic if not resolved before the 
> > >> board votes on the resolution:
> > >>
> > >> 1. The home page https://pekko.apache.org has Apache Pekko in the first 
> > >> prominent usage but does not use a TM symbol as in Apache Pekko™.
> > >> 2. The downloads page https://pekko.apache.org/download.html KEYS file 
> > >> for verifying checksums should link to the dist.apache.org file not the 
> > >> source repository.
> > >> https://dist.apache.org/repos/dist/release/incubator/pekko/KEYS
> > >> Of course, this should link to the non-incubator file once you have a 
> > >> release as a TLP.
> > >>
> > >> Other than that, looks good.
> > >>
> > >> Good luck,
> > >> Craig
> > >>
> > >>> On Feb 26, 2024, at 03:24, PJ Fanning  wrote:
> > >>>
> > >>> Hi everyone,
> > >>>
> > >>> We have positive feedback on the Pekko Vote thread [1] (result [2]).
> > >>>
> > >>> I'd like to start an official Incubator VOTE thread now.
> > >>>
> > >>> Below are some facts and project highlights from the incubation phase
> > >>> as well as the draft resolution:
> > >>>
> > >>> * All modules have at least a v1.0.0 release
> > >>> * 19 releases (across 12 modules) [3]
> > >>> * Evidence of good uptake of the Pekko releases and a large number of
> > >>> ecosystem libs now support Pekko - over 100 non Apache libraries use
> > >>> Pekko libs under the hood
> > >>> * well over 1000 PRs merged
> > >>> * 25+ code contributors
> > >>> * We've had 3 different release managers to date.
> > >>> * dozens more users who have been involved in discussions, code
> > >>> reviews, raising issues, etc.
> > >>> * We have met all maturity criteria as outlined in [4].
> > >>>
> > >>>
> > >>> Please vote on the resolution pasted below to graduate Apache Pekko
> > >>> from the Incubator to the Top Level Project.
> > >>>
> > >>> [ ] +1 Graduate Apache Pekko from the Incubator.
> > >>> [ ] +0 No opinion.
> > >>> [ ] -1 Don't graduate Apache Pekko from the Incubator because ...
> > >>>
> > >>> This vote will open for at least 72 hours.
> > >>>
> > >>> I would like to thank everyone who have participated in the Apache
> > >>> Pekko community. I would also like to thank the Apache Incubator
> > >>> community as well as Apache Infrastructure team and general ASF
> > >>> community for your support.
> > >>>
> > >>>
> > >>> [1] https://lists.apache.org/thread/q7jjmp7zpcxko607v5hvj514dyf6o8bx
> > >>> [2] https://lists.apache.org/thread/tsb7b8bkgfkts1nstmj413qocztj0s5o
> > >>> [3] https://incubator.apache.org/projects/pekko.html
> > >>> [4] 
> > >>> https://cwiki.apache.org/confluence/display/PEKKO/Apache+Maturity+Model+Assessment+for+Pekko
> > >>>
> > >>>
> > >>>
> > >>> ---
> > >>>
> > >>> Establish the Apache Pekko Project
> > >>>
> > >>>
> > >>> WHEREAS, the Board of Directors deems it to be in the best interests
> > >>> of the Foundation and consistent with the Foundation's purpose to
> > >>> establish a Project Management Committee charged with the creation and
> > >>> maintenance of open-source software, for distribution at no charge to
> > >>> the public, related to Pekko: a toolkit and an ecosystem for building
> > >>> highly concurrent, distributed, reactive and resilient applications
> > >>> for Java and Scala.
> > >>>
> > >>>
> > >>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > >>> (PMC), to be known as the "Apache Pekko Project", be and hereby is
> > >>> established pursuant to Bylaws of the Foundation; and be it further
> > >>>
> > >>>
> > >>> RESOLVED, that the Apache Pekko Project be and hereby is responsible
> > >>> for the creation and maintenance of software related to Pekko: a
> > >>> toolkit and an ecosystem for building highly concurrent, distributed,
> > >>> reactive and resilient applications for Java and Scala.; and be it
> > >>> further
> > >>>
> > >>>
> > >>> RESOLVED, that the office of "Vice President, Apache Pekko" be and
> > >>> hereby is created, the person holding such office to serve at the
> > >>> direction of the Board of Directors as the chair of the Apache Pekko
> > >>> Project, and to have primary responsibility for management of the
> > >>> projects within the scope of responsibility of the Apach

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

[sebb]

On Sat, 24 Feb 2024 at 04:03, Riley Kuttruff  wrote:
>
> Thank you for finding those issues. I've updated the site (sdap.a.o shows the 
> changes but sdap.i.a.o still hasn't updated at the time I'm writing this). I 
> believe I've the issues you've found. Please let me know if this is not the 
> case.

The issues I raised have been fixed, thanks.

> On 2024/02/23 15:59:07 sebb wrote:
> > The Downloads page has some issues:
> > https://sdap.apache.org/downloads
> >
> > No link to KEYS file
> > Links for older releases are broken
> > Copyright page is 2023
> >
> > On Fri, 23 Feb 2024 at 14:30, PJ Fanning  wrote:
> > >
> > > +1 (binding)
> > >
> > > I had a look at the mailing lists and the community seems in a pretty 
> > > good state.
> > >
> > > As a matter of interest, are you still looking at completing the v1.2.0 
> > > release [1]? If so, I could have a look at the RC over the weekend.
> > >
> > > [1] https://lists.apache.org/thread/vr4zf6zhg2yp41bjwvlpm1mp2nrycqcw
> > >
> > > On 2024/02/22 18:01:31 Riley Kuttruff wrote:
> > > > Hi all,
> > > >
> > > > Apache SDAP joined Incubator in October 2017. In the time since, we've
> > > > made significant progress towards maturing our community and our
> > > > project and adopting the Apache Way.
> > > >
> > > > After community discussion [1][2][3], the community has voted [4] that 
> > > > we
> > > > would like to proceed with graduation [5]. We now call upon the 
> > > > Incubator
> > > > PMC to review and discuss our progress and would appreciate any and all
> > > > feedback towards graduation.
> > > >
> > > > Below are some facts and project highlights from the incubation phase as
> > > > well as the draft resolution:
> > > >
> > > > - Our community consists of 21 committers, with 2 being mentors and
> > > > the remaining 19 serving as our PPMC
> > > > - Several pending and planned invites to bring on new committers and/or
> > > > PPMC members from additional organizations
> > > > - Completed 2 releases with 2 release managers - with a 3rd release run 
> > > > by
> > > > a 3rd release manager in progress
> > > > - Our software is currently being utilized by organizations such as NASA
> > > > Jet Propulsion Laboratory, NSF National Center for Atmospheric Research,
> > > > Florida State University, and George Mason University in support of 
> > > > projects
> > > > such as the NASA Sea Level Change Portal, Estimating the Circulation and
> > > > Climate of the Ocean (ECCO) project, GRACE/GRACE-FO, Cloud-based
> > > > Data Match-Up Service, Integrated Digital Earth Analysis System (IDEAS),
> > > > and many others.
> > > > - Opened 400+ PRs across 3 main code repositories, 350+ of which are
> > > > merged or closed (some are pending our next release)
> > > > - Maturity model self assessment [6]
> > > >
> > > > We have resolved all branding issues we are aware of: logo, GitHub,
> > > > Website, etc
> > > >
> > > > We’d like to also extend a sincere thank you to our mentors, current and
> > > > former for their invaluable insight and assistance with getting us to 
> > > > this
> > > > point.
> > > >
> > > > Thank you, Julian, Jörn, Trevor, Lewis, Suneel, and Raphael!
> > > >
> > > > ---
> > > >
> > > > Establish the Apache SDAP Project
> > > >
> > > > WHEREAS, the Board of Directors deems it to be in the best interests of
> > > > the Foundation and consistent with the Foundation's purpose to establish
> > > > a Project Management Committee charged with the creation and maintenance
> > > > of open-source software, for distribution at no charge to the public,
> > > > related to an integrated data analytic center for Big Science problems.
> > > >
> > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > > > (PMC), to be known as the "Apache SDAP Project", be and hereby is
> > > > established pursuant to Bylaws of the Foundation; and be it further
> > > >
> > > > RESOLVED, that the Apache SDAP Project be and hereby is responsible
> > > > for the cre

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

[sebb]

The Downloads page has some issues:
https://sdap.apache.org/downloads

No link to KEYS file
Links for older releases are broken
Copyright page is 2023

On Fri, 23 Feb 2024 at 14:30, PJ Fanning  wrote:
>
> +1 (binding)
>
> I had a look at the mailing lists and the community seems in a pretty good 
> state.
>
> As a matter of interest, are you still looking at completing the v1.2.0 
> release [1]? If so, I could have a look at the RC over the weekend.
>
> [1] https://lists.apache.org/thread/vr4zf6zhg2yp41bjwvlpm1mp2nrycqcw
>
> On 2024/02/22 18:01:31 Riley Kuttruff wrote:
> > Hi all,
> >
> > Apache SDAP joined Incubator in October 2017. In the time since, we've
> > made significant progress towards maturing our community and our
> > project and adopting the Apache Way.
> >
> > After community discussion [1][2][3], the community has voted [4] that we
> > would like to proceed with graduation [5]. We now call upon the Incubator
> > PMC to review and discuss our progress and would appreciate any and all
> > feedback towards graduation.
> >
> > Below are some facts and project highlights from the incubation phase as
> > well as the draft resolution:
> >
> > - Our community consists of 21 committers, with 2 being mentors and
> > the remaining 19 serving as our PPMC
> > - Several pending and planned invites to bring on new committers and/or
> > PPMC members from additional organizations
> > - Completed 2 releases with 2 release managers - with a 3rd release run by
> > a 3rd release manager in progress
> > - Our software is currently being utilized by organizations such as NASA
> > Jet Propulsion Laboratory, NSF National Center for Atmospheric Research,
> > Florida State University, and George Mason University in support of projects
> > such as the NASA Sea Level Change Portal, Estimating the Circulation and
> > Climate of the Ocean (ECCO) project, GRACE/GRACE-FO, Cloud-based
> > Data Match-Up Service, Integrated Digital Earth Analysis System (IDEAS),
> > and many others.
> > - Opened 400+ PRs across 3 main code repositories, 350+ of which are
> > merged or closed (some are pending our next release)
> > - Maturity model self assessment [6]
> >
> > We have resolved all branding issues we are aware of: logo, GitHub,
> > Website, etc
> >
> > We’d like to also extend a sincere thank you to our mentors, current and
> > former for their invaluable insight and assistance with getting us to this
> > point.
> >
> > Thank you, Julian, Jörn, Trevor, Lewis, Suneel, and Raphael!
> >
> > ---
> >
> > Establish the Apache SDAP Project
> >
> > WHEREAS, the Board of Directors deems it to be in the best interests of
> > the Foundation and consistent with the Foundation's purpose to establish
> > a Project Management Committee charged with the creation and maintenance
> > of open-source software, for distribution at no charge to the public,
> > related to an integrated data analytic center for Big Science problems.
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > (PMC), to be known as the "Apache SDAP Project", be and hereby is
> > established pursuant to Bylaws of the Foundation; and be it further
> >
> > RESOLVED, that the Apache SDAP Project be and hereby is responsible
> > for the creation and maintenance of software related to an integrated data
> > analytic center for Big Science problems; and be it further
> >
> > RESOLVED, that the office of "Vice President, Apache SDAP" be and
> > hereby is created, the person holding such office to serve at the
> > direction of the Board of Directors as the chair of the Apache SDAP
> > Project, and to have primary responsibility for management of the
> > projects within the scope of responsibility of the Apache SDAP
> > Project; and be it further
> >
> > RESOLVED, that the persons listed immediately below be and hereby are
> > appointed to serve as the initial members of the Apache SDAP Project:
> >
> > - Edward M Armstrong 
> > - Nga Thien Chung 
> > - Thomas Cram 
> > - Frank Greguska 
> > - Thomas Huang 
> > - Julian Hyde 
> > - Joseph C. Jacob 
> > - Jason Kang 
> > - Riley Kuttruff 
> > - Thomas G Loubrieu 
> > - Kevin Marlis 
> > - Stepheny Perez 
> > - Wai Linn Phyo 
> >
> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Nga Thien Chung
> > be appointed to the office of Vice President, Apache SDAP, to serve in
> > accordance with and subject to the direction of 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] ht

Re: (apache-website-template) branch jekyll created (now f2f8a9e)

[sebb]

On Thu, 22 Feb 2024 at 00:08, tison  wrote:
>
> It's currently a brand new branch. You can check it in the repo.

OK, great. It seems I was misled by the summary page, which says:

"This branch is 5 commits ahead of, 34 commits behind master."

To me, that definitely implies a relationship. Very confusing.

However, try a compare, and it says: "master and docusaurus are
entirely different commit histories."

> Best,
> tison.
>
>
> sebb 于2024年2月22日 周四01:11写道：
>
> > On Wed, 21 Feb 2024 at 09:25, tison  wrote:
> > >
> > > Hi sebb,
> > >
> > > Your comments sound like back to the switching default branch solution (a
> > > new branch with history only adding the README becomes the default).
> >
> > I am saying that if the 3 branch solution is adopted the docusaurus
> > branch should be created as a new branch.
> >
> > > Or you prefer other ways to the same repo direction.
> > >
> > > Also is it possible we go back to the COMDEV dedicated thread so that
> > > people can easily follow the context? If we agree, the context here can
> > be
> > > brought there.
> > >
> > > Best,
> > > tison.
> > >
> > >
> > > sebb 于2024年2月21日 周三16:27写道：
> > >
> > > > On Wed, 21 Feb 2024 at 00:28, tison  wrote:
> > > > >
> > > > > Hi Dave,
> > > > >
> > > > > > One approach is to find good examples of each build technique. If
> > you
> > > > look back at older projects you will see various historical waves of
> > > > technique.
> > > > >
> > > > > I agree, and that's why I'd prefer a multi branches solution with a
> > > > > default branch containing README for redirects.
> > > >
> > > > However, if a repo is shared in this way, such disjoint branches
> > > > should be initially created as empty orphans.
> > > > Replacing all the files with different ones makes for a confusing
> > history.
> > > >
> > > > > From another perspective, it's still valuable to provide a template
> > > > > for new podlings to get started _now_, and if someone (in this case,
> > > > > it's me) volunteers to provide one for help, there is no reason we
> > > > > reject it by the tech will fade _years later_.
> > > > >
> > > > > Best,
> > > > > tison.
> > > > >
> > > > > Dave Fisher  于2024年2月21日周三 08:17写道：
> > > > > >
> > > > > > Hi Tison,
> > > > > >
> > > > > > I’m following along. Infrastructure has a Pelican template site
> > that
> > > > is out of date: https://github.com/apache/template-site/
> > > > > >
> > > > > > One approach is to find good examples of each build technique. If
> > you
> > > > look back at older projects you will see various historical waves of
> > > > technique.
> > > > > >
> > > > > > Best,
> > > > > > Dave
> > > > > >
> > > > > > > On Feb 20, 2024, at 3:48 PM, tison  wrote:
> > > > > > >
> > > > > > > Hi Dave,
> > > > > > >
> > > > > > > Thanks for picking up this commit. You may join the discussion at
> > > > [1].
> > > > > > >
> > > > > > > I have all the permission to follow what I want. But since
> > > > > > > apache-website-template is technically a foundation-wise repo
> > and I'm
> > > > > > > a newcomer here, I'd like to listen to people's opinions before
> > > > moving
> > > > > > > forward; especially there can be some arguments.
> > > > > > >
> > > > > > > Best,
> > > > > > > tison.
> > > > > > >
> > > > > > > [1]
> > https://lists.apache.org/thread/tvry49gdclqqdtdcgk0x9hnl18vlxnm8
> > > > > > >
> > > > > > > Dave Fisher  于2024年2月21日周三 02:35写道：
> > > > > > >>
> > > > > > >> From the commit email it looks like this repository belongs to
> > the
> > > > Incubator.
> > > > > > >>
> > > > > > >>&g

Re: (apache-website-template) branch jekyll created (now f2f8a9e)

[sebb]

On Wed, 21 Feb 2024 at 09:25, tison  wrote:
>
> Hi sebb,
>
> Your comments sound like back to the switching default branch solution (a
> new branch with history only adding the README becomes the default).

I am saying that if the 3 branch solution is adopted the docusaurus
branch should be created as a new branch.

> Or you prefer other ways to the same repo direction.
>
> Also is it possible we go back to the COMDEV dedicated thread so that
> people can easily follow the context? If we agree, the context here can be
> brought there.
>
> Best,
> tison.
>
>
> sebb 于2024年2月21日 周三16:27写道：
>
> > On Wed, 21 Feb 2024 at 00:28, tison  wrote:
> > >
> > > Hi Dave,
> > >
> > > > One approach is to find good examples of each build technique. If you
> > look back at older projects you will see various historical waves of
> > technique.
> > >
> > > I agree, and that's why I'd prefer a multi branches solution with a
> > > default branch containing README for redirects.
> >
> > However, if a repo is shared in this way, such disjoint branches
> > should be initially created as empty orphans.
> > Replacing all the files with different ones makes for a confusing history.
> >
> > > From another perspective, it's still valuable to provide a template
> > > for new podlings to get started _now_, and if someone (in this case,
> > > it's me) volunteers to provide one for help, there is no reason we
> > > reject it by the tech will fade _years later_.
> > >
> > > Best,
> > > tison.
> > >
> > > Dave Fisher  于2024年2月21日周三 08:17写道：
> > > >
> > > > Hi Tison,
> > > >
> > > > I’m following along. Infrastructure has a Pelican template site that
> > is out of date: https://github.com/apache/template-site/
> > > >
> > > > One approach is to find good examples of each build technique. If you
> > look back at older projects you will see various historical waves of
> > technique.
> > > >
> > > > Best,
> > > > Dave
> > > >
> > > > > On Feb 20, 2024, at 3:48 PM, tison  wrote:
> > > > >
> > > > > Hi Dave,
> > > > >
> > > > > Thanks for picking up this commit. You may join the discussion at
> > [1].
> > > > >
> > > > > I have all the permission to follow what I want. But since
> > > > > apache-website-template is technically a foundation-wise repo and I'm
> > > > > a newcomer here, I'd like to listen to people's opinions before
> > moving
> > > > > forward; especially there can be some arguments.
> > > > >
> > > > > Best,
> > > > > tison.
> > > > >
> > > > > [1] https://lists.apache.org/thread/tvry49gdclqqdtdcgk0x9hnl18vlxnm8
> > > > >
> > > > > Dave Fisher  于2024年2月21日周三 02:35写道：
> > > > >>
> > > > >> From the commit email it looks like this repository belongs to the
> > Incubator.
> > > > >>
> > > > >>> On Feb 14, 2024, at 2:27 AM, ti...@apache.org wrote:
> > > > >>>
> > > > >>> This is an automated email from the ASF dual-hosted git repository.
> > > > >>>
> > > > >>> tison pushed a change to branch jekyll
> > > > >>> in repository
> > https://gitbox.apache.org/repos/asf/apache-website-template.git
> > > > >>>
> > > > >>>
> > > > >>> at f2f8a9e  Update download page template
> > > > >>>
> > > > >>> No new revisions were added by this update.
> > > > >>>
> > > > >>>
> > > > >>>
> > -
> > > > >>> To unsubscribe, e-mail: cvs-unsubscr...@incubator.apache.org
> > > > >>> For additional commands, e-mail: cvs-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: dev-unsubscr...@community.apache.org
> > > > > For additional commands, e-mail: dev-h...@community.apache.org
> > > > >
> > > >
> > > >
> > > > -
> > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > For additional commands, e-mail: general-h...@incubator.apache.org
> > > >
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >

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

Re: ResilientDB Bootstrap missing Mailing Lists

[sebb]

The mailing lists already exist.

However the podling status files are out of date so clutch cannot find
the information it needs.

See aso https://incubator.apache.org/projects/resilientdb.html which
is rather out of date.

On Wed, 21 Feb 2024 at 00:22, tison  wrote:
>
> Hi Mohammad,
>
> For this specific issue, you or your mentors should be able to
> self-serve creating the necessary list on [1].
>
> As in your proposal [2], they are:
>
> * resilientdb-private (with moderated subscriptions) ->
> priv...@resilientdb.apache.org
> * resilientdb-dev -> dev@@resilientdb.apache.org
> * resilientdb-commits -> comm...@resilientdb.apache.org
> * resilientdb-user -> u...@resilientdb.apache.org
>
> Generally, you should deal with such questions with your mentors. I
> recommend you read [3][4] for more details about running a podling.
>
> Best,
> tison.
>
> [1] https://selfserve.apache.org/mailinglist-new.html
> [2] https://cwiki.apache.org/confluence/display/INCUBATOR/ResilientDBProposal
> [3] https://incubator.apache.org/guides/roles_and_responsibilities.html
> [4] https://incubator.apache.org/cookbook/
>
> Mohammad Sadoghi  于2024年2月21日周三 08:09写道：
> >
> > Dear Dave,
> >
> > Hope you are safe and well.
> >
> > Thank you for identifying this issue; how can we correct it?
> >
> > ---
> > 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 Mon, Feb 19, 2024 at 3:57 PM Dave Fisher  wrote:
> >
> > > Hi -
> > >
> > > Perhaps the podling status file in svn was not properly updated?
> > >
> > > Best,
> > > Dave
> > >
> > > > On Feb 19, 2024, at 3:51 PM, Dave Fisher  wrote:
> > > >
> > > > Hi -
> > > >
> > > > Please have a look at
> > > https://incubator.apache.org/clutch/resilientdb.html
> > > >
> > > > Where are the mailing lists? Where is the website?
> > > >
> > > > Best,
> > > > Dave
> > > >
> > > > -
> > > > 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

Re: (apache-website-template) branch jekyll created (now f2f8a9e)

[sebb]

On Wed, 21 Feb 2024 at 00:28, tison  wrote:
>
> Hi Dave,
>
> > One approach is to find good examples of each build technique. If you look 
> > back at older projects you will see various historical waves of technique.
>
> I agree, and that's why I'd prefer a multi branches solution with a
> default branch containing README for redirects.

However, if a repo is shared in this way, such disjoint branches
should be initially created as empty orphans.
Replacing all the files with different ones makes for a confusing history.

> From another perspective, it's still valuable to provide a template
> for new podlings to get started _now_, and if someone (in this case,
> it's me) volunteers to provide one for help, there is no reason we
> reject it by the tech will fade _years later_.
>
> Best,
> tison.
>
> Dave Fisher  于2024年2月21日周三 08:17写道：
> >
> > Hi Tison,
> >
> > I’m following along. Infrastructure has a Pelican template site that is out 
> > of date: https://github.com/apache/template-site/
> >
> > One approach is to find good examples of each build technique. If you look 
> > back at older projects you will see various historical waves of technique.
> >
> > Best,
> > Dave
> >
> > > On Feb 20, 2024, at 3:48 PM, tison  wrote:
> > >
> > > Hi Dave,
> > >
> > > Thanks for picking up this commit. You may join the discussion at [1].
> > >
> > > I have all the permission to follow what I want. But since
> > > apache-website-template is technically a foundation-wise repo and I'm
> > > a newcomer here, I'd like to listen to people's opinions before moving
> > > forward; especially there can be some arguments.
> > >
> > > Best,
> > > tison.
> > >
> > > [1] https://lists.apache.org/thread/tvry49gdclqqdtdcgk0x9hnl18vlxnm8
> > >
> > > Dave Fisher  于2024年2月21日周三 02:35写道：
> > >>
> > >> From the commit email it looks like this repository belongs to the 
> > >> Incubator.
> > >>
> > >>> On Feb 14, 2024, at 2:27 AM, ti...@apache.org wrote:
> > >>>
> > >>> This is an automated email from the ASF dual-hosted git repository.
> > >>>
> > >>> tison pushed a change to branch jekyll
> > >>> in repository 
> > >>> https://gitbox.apache.org/repos/asf/apache-website-template.git
> > >>>
> > >>>
> > >>> at f2f8a9e  Update download page template
> > >>>
> > >>> No new revisions were added by this update.
> > >>>
> > >>>
> > >>> -
> > >>> To unsubscribe, e-mail: cvs-unsubscr...@incubator.apache.org
> > >>> For additional commands, e-mail: cvs-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: dev-unsubscr...@community.apache.org
> > > For additional commands, e-mail: dev-h...@community.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] [Assigned] (INCUBATOR-199) Extend podlings.xml to include old names and TLP parent

[Sebb (Jira)]

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

Sebb reassigned INCUBATOR-199:
--

Assignee: (was: Sebb)

> Extend podlings.xml to include old names and TLP parent
> ---
>
> Key: INCUBATOR-199
> URL: https://issues.apache.org/jira/browse/INCUBATOR-199
> Project: Incubator
>  Issue Type: New Feature
>    Reporter: Sebb
>Priority: Major
>
> Podling names change fairly often.
> It would be useful to be able to list old names in the podlings file.
> At present this info is only in the free-form text.
> Also where a podling graduates as a project of a PMC, it would be useful to 
> be able to document the PMC. At present this would have to be extracted from 
> the url field (or the text)
> AFAIK additional attributes do not cause problems for existing parsing 
> routines. However the DTD will have to be extended to allow for the new 
> entries.



--
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] Graduate Apache OpenDAL (incubating) as a TLP - Incubator

[sebb]

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

Re: [VOTE] Graduate Apache OpenDAL (incubating) as a TLP - Incubator

[sebb]

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
> >> > 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 Open Data Access Layer: Access data freely, painlessly, and
> >> > efficiently.
> >> >
> >> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> >> > (PMC), to be known as the "Apache OpenDAL Project", be and hereby is
> >> > established pursuant to Bylaws of the Foundation; and be it further
> >> >
> >> > RESOLVED, that the Apache OpenDAL Project be and hereby is responsible
> >> > for the creation and maintenance of software related to Open Data Access
> >> > Layer: Access data freely, painlessly, and efficiently; and be it
> >> > further
> >> >
> >> > RESOLVED, that the office of "Vice President, Apache OpenDAL" b

Re: [VOTE] Graduate Apache OpenDAL (incubating) as a TLP - Incubator

[sebb]

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
> > 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 Open Data Access Layer: Access data freely, painlessly, and
> > efficiently.
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > (PMC), to be known as the "Apache OpenDAL Project", be and hereby is
> > established pursuant to Bylaws of the Foundation; and be it further
> >
> > RESOLVED, that the Apache OpenDAL Project be and hereby is responsible
> > for the creation and maintenance of software related to Open Data Access
> > Layer: Access data freely, painlessly, and efficiently; and be it
> > further
> >
> > RESOLVED, that the office of "Vice President, Apache OpenDAL" 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 OpenDAL
> > Project, and to have primary responsibility for management of the
> > projects within the scope of responsibility of the Apache OpenDAL
> > 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 OpenDAL Project:
> >
> > * Cai Lue   
> > * Chojan Shang  
> > * Han Xu
> > * Hao Ding  
> > * Jun Ouyang
> > * Mingzhuo Yin  
> > * Sheng Wu  
> > * Sundy Li  
> > * Ted Liu   
> > * Willem Ning Jiang 
> > * Xiangdong 
> > * Xiaoqiao He   
> > * Zheao Li  
> > * Zili Chen 
> >
> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Hao Ding be appointed to
> > the office of Vice President, Apache OpenDAL, 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

Re: svn commit: r1912845 - /incubator/public/trunk/content/podlings.xml

[sebb]

It looks like the error occurred in the jbake stage, not anakia.

It looks like the issue was actually here:

https://github.com/apache/incubator/blob/1c95cfce15d4a5972662cdd844b7989090972c05/bake.sh#L19

I've added https to the property, and changed the podlings.dtd url to
use https, and the site now builds OK.


On Mon, 9 Oct 2023 at 22:04, Dave Fisher  wrote:
>
> FYI - website build has been failing since August 30 due to a switch to use 
> https for the podlings.dtd.
>
> The part of the build with the very, very old ant/anakia build somehow 
> requires http. The change to use https is now reverted. A subsequent comment 
> is added to point to where this anakia process runs. Please test that and fix 
> if you feel we must use https.
>
> Best,
> Dave
>
> Sent from my iPhone
>
> > On Oct 9, 2023, at 5:20 PM, w...@apache.org wrote:
> >
> > Author: wave
> > Date: Mon Oct  9 20:20:04 2023
> > New Revision: 1912845
> >
> > URL: http://svn.apache.org/viewvc?rev=1912845&view=rev
> > Log:
> > revert r1912020 - see 
> > https://builds.apache.org/job/Incubator/job/Incubator-SVN-Clutch-Analysis-part-1/1811/console
> >
> > Modified:
> >incubator/public/trunk/content/podlings.xml
> >
> > Modified: incubator/public/trunk/content/podlings.xml
> > URL: 
> > http://svn.apache.org/viewvc/incubator/public/trunk/content/podlings.xml?rev=1912845&r1=1912844&r2=1912845&view=diff
> > ==
> > --- incubator/public/trunk/content/podlings.xml [utf-8] (original)
> > +++ incubator/public/trunk/content/podlings.xml [utf-8] Mon Oct  9 20:20:04 
> > 2023
> > @@ -24,7 +24,7 @@
> > See the DTD for allowable elements and attributes.
> > Note that description must precede mentors, and most of the podling 
> > attributes are required.
> >  -->
> > - > "https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings.dtd";>
> > + > "http://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings.dtd";>
> >
> > 
> >  > sponsor="Incubator" startdate="2006-06-06" enddate="2008-11-08">
> >
> >
> >
> > -
> > To unsubscribe, e-mail: cvs-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: cvs-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

Tuweni and Datalab cleanup STILL not complete

[sebb]

The Infra work appears to have been done, but as mentioned previously,
there is also work for the Incubator to do.

In particular, the websites need to be addressed.

https://github.com/apache/incubator/tree/master/assets/retired

Sebb

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

[jira] [Commented] (INCUBATOR-279) Tuweni retired, but cleanup is incomplete

[Sebb (Jira)]

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

Sebb commented on INCUBATOR-279:


The index page was updated to point to the Attic, but that was wrong, as the 
Attic only deals with PMCs (and so the link is broken).

> Tuweni retired, but cleanup is incomplete
> -
>
> Key: INCUBATOR-279
> URL: https://issues.apache.org/jira/browse/INCUBATOR-279
> Project: Incubator
>  Issue Type: Bug
>Reporter: Sebb
>Priority: Major
>
> The LDAP project list still needs to be removed.
> Also podlings.xml and tuweni.xml need to be updated, and the website site 
> redirect needs to be set up.
> Maybe the retirement instructions need to be reviewed.



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

[jira] [Commented] (INCUBATOR-279) Tuweni retired, but cleanup is incomplete

[Sebb (Jira)]

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

Sebb commented on INCUBATOR-279:


Still not complete.

 

The website needs to be redirected, see:

 

https://github.com/apache/incubator/tree/master/assets/retired

> Tuweni retired, but cleanup is incomplete
> -
>
> Key: INCUBATOR-279
> URL: https://issues.apache.org/jira/browse/INCUBATOR-279
> Project: Incubator
>  Issue Type: Bug
>Reporter: Sebb
>Priority: Major
>
> The LDAP project list still needs to be removed.
> Also podlings.xml and tuweni.xml need to be updated, and the website site 
> redirect needs to be set up.
> Maybe the retirement instructions need to be reviewed.



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

[jira] [Commented] (INCUBATOR-280) Datalab retired, but cleanup is incomplete

[Sebb (Jira)]

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

Sebb commented on INCUBATOR-280:


Still not complete.

 

The website needs to be redirected; see

 

[https://github.com/apache/incubator/tree/master/assets/retired]

 

> Datalab retired, but cleanup is incomplete
> --
>
> Key: INCUBATOR-280
> URL: https://issues.apache.org/jira/browse/INCUBATOR-280
> Project: Incubator
>  Issue Type: Task
>Reporter: Sebb
>Priority: Major
>
> As the subject says



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

[jira] [Commented] (INCUBATOR-281) Broken link

[Sebb (Jira)]

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

Sebb commented on INCUBATOR-281:


Noticed a blank line where sibling pages had a date, so I restored the date 
lost in the last commit.
The page as been regenerated.

Looks like there needs to be a check of the build to detect such failings.

> Broken link
> ---
>
> Key: INCUBATOR-281
> URL: https://issues.apache.org/jira/browse/INCUBATOR-281
> Project: Incubator
>  Issue Type: Bug
>Reporter: Sebb
>Priority: Major
>
> https://cwiki.apache.org/confluence/display/incubator/RetiringPodlings
> links to
> https://incubator.apache.org/guides/retirement.html
> which does not exist.
> Not sure whether it ever did exist.



--
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: Retired podlings not being cleaned up

[sebb]

It looks like the Wiki retirement banner is controlled from here:

https://github.com/apache/infrastructure-p6/tree/production/modules/cwiki_asf/files/retired_podlings

Perhaps someone from the IPMC could update the relevant instructions.

On Fri, 17 Nov 2023 at 14:59, sebb  wrote:
>
> There are various steps that the Incubator also has to do.
> For example, ensuring the various status files are up to date, and
> implementing website redirects.
>
> Unfortunately the retirement guide at
> https://cwiki.apache.org/confluence/display/incubator/RetiringPodlings
> is a bit vague on how to perform some of the actions, but a search for
> previous retirements in commit messages should give some clues.
>
> On Fri, 17 Nov 2023 at 13:46, PJ Fanning  wrote:
> >
> > I've created https://issues.apache.org/jira/browse/INFRA-25181 to group the 
> > INFRA tasks related to this.
> >
> > On 2023/11/17 09:44:54 sebb wrote:
> > > Still no action as far as I can tell.
> > >
> > > On Mon, 30 Oct 2023 at 14:53, sebb  wrote:
> > > >
> > > > Tuweni and Datalab retired some while ago, but nothing much seems to
> > > > have been done to close them down.
> > > >
> > > > Sebb
> > >
> > > -
> > > 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: Retired podlings not being cleaned up

[sebb]

There are various steps that the Incubator also has to do.
For example, ensuring the various status files are up to date, and
implementing website redirects.

Unfortunately the retirement guide at
https://cwiki.apache.org/confluence/display/incubator/RetiringPodlings
is a bit vague on how to perform some of the actions, but a search for
previous retirements in commit messages should give some clues.

On Fri, 17 Nov 2023 at 13:46, PJ Fanning  wrote:
>
> I've created https://issues.apache.org/jira/browse/INFRA-25181 to group the 
> INFRA tasks related to this.
>
> On 2023/11/17 09:44:54 sebb wrote:
> > Still no action as far as I can tell.
> >
> > On Mon, 30 Oct 2023 at 14:53, sebb  wrote:
> > >
> > > Tuweni and Datalab retired some while ago, but nothing much seems to
> > > have been done to close them down.
> > >
> > > Sebb
> >
> > -
> > 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] [Created] (INCUBATOR-281) Broken link

[Sebb (Jira)]

Sebb created INCUBATOR-281:
--

 Summary: Broken link
 Key: INCUBATOR-281
 URL: https://issues.apache.org/jira/browse/INCUBATOR-281
 Project: Incubator
  Issue Type: Bug
Reporter: Sebb


https://cwiki.apache.org/confluence/display/incubator/RetiringPodlings
links to
https://incubator.apache.org/guides/retirement.html
which does not exist.

Not sure whether it ever did exist.



--
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: Retired podlings not being cleaned up

[sebb]

Still no action as far as I can tell.

On Mon, 30 Oct 2023 at 14:53, sebb  wrote:
>
> Tuweni and Datalab retired some while ago, but nothing much seems to
> have been done to close them down.
>
> Sebb

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

[jira] [Commented] (INCUBATOR-280) Datalab retired, but cleanup is incomplete

[Sebb (Jira)]

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

Sebb commented on INCUBATOR-280:


The Incubator PMC is ultimately responsible. Some parts have to be done by 
Infra on request from the IPMC.

> Datalab retired, but cleanup is incomplete
> --
>
> Key: INCUBATOR-280
> URL: https://issues.apache.org/jira/browse/INCUBATOR-280
> Project: Incubator
>  Issue Type: Task
>Reporter: Sebb
>Priority: Major
>
> As the subject says



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

[jira] [Commented] (INCUBATOR-280) Datalab retired, but cleanup is incomplete

[Sebb (Jira)]

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

Sebb commented on INCUBATOR-280:


AFAIK, nothing has been done on this.
For example, the LDAP group still exists
https://dist.apache.org/repos/dist/dev/incubator/datalab/ still exists
Various resources such as Git, Website, Wiki appear to be still active (they 
should have comments to say the podling is retired)
etc.

> Datalab retired, but cleanup is incomplete
> --
>
> Key: INCUBATOR-280
> URL: https://issues.apache.org/jira/browse/INCUBATOR-280
> Project: Incubator
>  Issue Type: Task
>Reporter: Sebb
>Priority: Major
>
> As the subject says



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

Retired podlings not being cleaned up

[sebb]

Tuweni and Datalab retired some while ago, but nothing much seems to
have been done to close them down.

Sebb

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

[jira] [Commented] (INCUBATOR-279) Tuweni retired, but cleanup is incomplete

[Sebb (Jira)]

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

Sebb commented on INCUBATOR-279:


Ping

> Tuweni retired, but cleanup is incomplete
> -
>
> Key: INCUBATOR-279
> URL: https://issues.apache.org/jira/browse/INCUBATOR-279
> Project: Incubator
>  Issue Type: Bug
>Reporter: Sebb
>Priority: Major
>
> The LDAP project list still needs to be removed.
> Also podlings.xml and tuweni.xml need to be updated, and the website site 
> redirect needs to be set up.
> Maybe the retirement instructions need to be reviewed.



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