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

[Willem Jiang]

Just have a comment on the Github repo descriptions of Incubating projects:
" We need to have word of  (Incubating) in the repo description."
It can be updated by editing the file of .asf.yaml in the repo.

Willem Jiang

On Tue, Apr 23, 2024 at 9:23 AM tison  wrote:
>
> Hi,
>
> Recently, the new added podlings, namely Amoro and Hertzbeat, have their
> GitHub repo in the names:
>
> * https://github.com/apache/amoro
> * https://github.com/apache/hertzbeat
>
> ... which is different to the other 20+ podlings and 200+ repos [1]
> existing (this number counts retired ones and those for the Incubator PMC
> itself, but it's approximate).
>
> [1]
> https://github.com/orgs/apache/repositories?language==incubator-==all
>
> My opinion is to agree that generally:
>
> 1. The incubator prefix comes from the SVN days where all podlings were under
> the incubator SVN tree.
> 2. Dropping the incubator- prefix for podling's GitHub repo can reduce some
> graduation tasks (although it's somewhat a milestone and ceremony for the
> podling, and INFRA does not find it a large job, as well as it won't break
> downstream almost due to redirections).
> 3. It's still significant to make it clear that a podling is in the
> incubating status and thus a DISCLAIMER to protect the ASF branding.
>
> With these premises, I started this thread with the following proposals and
> questions.
>
> 1. Establish a consensus to allow podling's GitHub repo to have a name
> without incubator- prefix.
> 2. Allow other 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. However, find a way to clarify that a repo belongs to a podling.
>
> For 4, I'd propose to add the "incubating" words to each repo's README.
> This can be regarded as treating those READMEs a homepage for the repo and,
>
> 1. Name the project as "Apache Foo (Incubating)" in its first and most
> prominent uses, hopefully and H1 heading.
> 2. Add a footer including the Incubator logo and DISCLAIMER, like the
> current footer of Apache Answer (Incubating) [3]
>
> [3] https://answer.apache.org/
>
> This method, however, can be a new chore for podlings that have many
> satellite repos that may previously claim their incubating status by naming
> the repos incubator-foo-satellite. But it's just another template to
> follow, so it won't be a big deal.
>
> Looking forward to your thoughts on this proposal and any suggestions to
> improve the implementation part.
>
> Best,
> tison.

-
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

[Willem Jiang]

Hi Zikuan

I just checked the download links from the website of devlake[1].
We need to a page to host the downloads related information just like
this[2], to provide the KEYS and signed asc files.

[1] https://devlake.apache.org/
[2]https://opendal.apache.org/download

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Mon, Apr 22, 2024 at 5:08 PM Zikuan An  wrote:
>
> Hi Sebb,
>
> Thank you very much for your advice and guidance.
> We will reach out to our mentors to ensure that our download page meets the
> required criteria.
>
> Thanks again for your patience and assistance!
>
> Best,
> Zikuan An
>
> sebb  于2024年4月22日周一 16:20写道：
>
> > 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
> >
> >

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

Re: [VOTE] Release Apache DevLake (Incubating) v0.21.0-rc1

[Willem Jiang]

+1 (binding)
Here are the checks I made.

- [X] Download links are valid.
- [X] Checksums and PGP signatures are valid.
- [X] Source code artifacts have correct names matching the current release.
- [X] LICENSE and NOTICE files are correct for the repository.
- [X] All files have license headers if necessary.
- [X] No compiled archives bundled in the source archive.

Thanks,

Willem Jiang

On Thu, Apr 11, 2024 at 8:23 PM Zikuan An  wrote:
>
> Hello everyone,
>
> This is a call for the vote to release Apache DevLake (Incubating)
> v0.21.0-rc1.
> The Apache DevLake community has voted on and approved a proposal
> to release Apache DevLake (Incubating) version v0.21.0-rc1.
>
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Community vote thread:
>
> https://lists.apache.org/thread/j8qowrhfdoqgyghg904bjs8ds639dl90
>
>
> Community vote result thread:
>
> https://lists.apache.org/thread/x32ln363j3rntglrbb1hsqj5bd8ns6y2
>
>
> The release candidates:
>
> https://dist.apache.org/repos/dist/dev/incubator/devlake/0.21.0-incubating-rc1
>
>
> Git tag for the release:
>
> https://github.com/apache/incubator-devlake/releases/tag/v0.21.0-rc1
>
>
> Keys to verify the Release Candidate:
>
> https://downloads.apache.org/incubator/devlake/KEYS
>
>
> How to build:
>
> https://devlake.apache.org/docs/DeveloperManuals/DeveloperSetup
>
>
> 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
>
>
> Thanks
>
> Zikuan An

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

Re: Questions about a new project entering Apache Incubator

[Willem Jiang]

With the "incubator" profix, it's easy for us to tell if the project
belongs to the incubator and it is still in the incubating process.
Currently I cannot find any disclaimer document[1] in the repo root
directory from [2][3] to tell if they are still in the incubator or
not.

[1]https://incubator.apache.org/policy/incubation.html#disclaimers
[2]https://github.com/apache/amoro
[3]https://github.com/apache/hertzbeat

Willem Jiang

On Wed, Apr 17, 2024 at 11:06 AM Calvin Kirs  wrote:
>
> Podlings are not yet fully accepted as part of the Apache Software
> Foundation.
>
> I haven't specifically witnessed any formal decision or process for
> removing the "incubator" prefix from repository names.
>
> Unless there are compelling reasons to remove the "incubator" prefix, I
> believe it's important to maintain a clear distinction between Podlings and
> TLPs, especially in situations where confusion is likely to arise.
>
> On Wed, Apr 17, 2024 at 10:32 AM Sheng Wu  wrote:
>
> > Same mistake for Armoro as Hertzbeat team was misguided from
> > https://github.com/apache/amoro/issues/2700
> >
> > This is not discussed AFAIK, and the description is not correct.
> > GitHub supported renaming and repository path forward automatically
> > years ago. apache/incubator-foo -> apache/foo is transparent and both
> > addresses work.
> >
> > This should not be changed randomly considering many other projects
> > are using incubator- prefix. This renaming causes confusion. IPMC are
> > making sure the website has `incubating` and disclaimer as always,
> > suddenly some projects even could use repository names without
> > prefixes. This is wrong.
> >
> > Mentors of Armoro and Hertzbeat should follow the existing
> > requirements, and PPMC members of these two projects should ask INFRA
> > to rename, adding the incubator- prefix back.
> >
> > Sheng Wu 吴晟
> > Twitter, wusheng1108
> >
> > Xuanwo  于2024年4月17日周三 10:19写道：
> > >
> > > > For projects in incubation, is it no longer necessary for the project
> > > > name to have the "incubator-" prefix as it used to be?
> > >
> > > Based on the discussions in this mailing list, the only change made is
> > the removal of `incubator` from the domain. Now, users access `
> > polding.apache.org` instead of `polding.incubator.apache.org` by default.
> > >
> > > The project and releases are still required to include "incubator", and
> > it's important for the PPMC to clearly communicate that this project
> > remains under incubation.
> > >
> > > In this case, I believe Hertzbeat PPMC made a mistake. I will suggest
> > they rename it to incubator-hertzbeat.
> > >
> > > On Mon, Apr 15, 2024, at 14:23, rat O wrote:
> > > > First of all, congratulations to HertzBeat for successfully entering
> > > > the Apache Incubator.
> > > >
> > > > I noticed that the project has created an issue for an unknown license
> > > > and is ready to address it. I'm sure the project will also address
> > > > other unknown licenses, if they exist.
> > > >
> > > > I wonder if the situation of having a significant amount of non-English
> > > > languages in the codes, like these
> > > >
> > https://github.com/apache/hertzbeat/blob/master/warehouse/src/main/java/org/apache/hertzbeat/warehouse/config/WarehouseProperties.java
> > ,
> > > >
> > https://github.com/apache/hertzbeat/blob/master/common/src/main/java/org/apache/hertzbeat/common/entity/manager/NoticeRule.java
> > ,
> > > >
> > https://github.com/apache/hertzbeat/blob/master/common/src/main/java/org/apache/hertzbeat/common/config/AviatorConfiguration.java
> > > > ...
> > > > , will all of them also be addressed in the future?
> > > >
> > > > For projects in incubation, is it no longer necessary for the project
> > > > name to have the "incubator-" prefix as it used to be?
> > >
> > > --
> > > 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
> >
> >
>
> --
> Best wishes！
> CalvinKirs

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

[Willem Jiang]

+1  (binding)
Apache ID : ningjiang

Here is what I checked:
[x] Download links are valid.
[x] Checksums and signatures.
[x] LICENSE/NOTICE files exist
[x] DISCLAIMER files exist
[x] Artifacts has the Incubating in the name
[x] No unexpected binary files

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Fri, Mar 29, 2024 at 3:46 PM LinkinStar  wrote:
>
> Hello,
>
> This is a call for vote to release Apache Answer(Incubating) version
> v1.3.0-RC1.
>
> The vote thread:
> https://lists.apache.org/thread/8pbh6047ogmdcf3ypdg4kr1k8gzxx6vf
>
> Vote Result:
> https://lists.apache.org/thread/q3d6pgr1rq30ldzfn82gdq1h0qzmgylx
>
> The release candidates:
>
> https://dist.apache.org/repos/dist/dev/incubator/answer/1.3.0-incubating-RC1/
>
> Release notes:
> https://github.com/apache/incubator-answer/releases/tag/v1.3.0-RC1
>
> Git tag for the release:
> https://github.com/apache/incubator-answer/releases/tag/v1.3.0-RC1
>
> Git commit id for the release:
>
> https://github.com/apache/incubator-answer/commit/9ebf95cacecf49ff466e47f3ff54c180eb67627c
>
> Keys to verify the Release Candidate:
> The artifacts signed with PGP key [C34934CC], corresponding to [
> linkins...@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.
>
> To compile from the source, please refer to:
>
> https://github.com/apache/incubator-answer#building-from-source
>
> Thanks,
> LinkinStar

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

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

[Willem Jiang]

+1  (binding)
Apache ID : ningjiang

Here is what I checked:
[x] Download links are valid.
[x] Checksums and signatures.
[x] LICENSE/NOTICE files exist
[x] DISCLAIMER files exist
[x] Artifacts has the Incubating in the name
[x] No unexpected binary files
[x] The 1.3.0 tags on GitHub repos are all good.

Willem

On Fri, Mar 29, 2024 at 10:17 AM Jacky Yang  wrote:
>
> Hello Incubator Community,
>
> This is a call for a vote to release Apache HugeGraph(Incubating)
> version 1.3.0-rc1
>
> The Apache HugeGraph community has voted on and approved a proposal to release
> Apache HugeGraph(Incubating) version 1.3.0-rc1
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> HugeGraph community vote thread:
>   • https://lists.apache.org/thread/80t2qqq7tmszm20l7ztosx4fpkhld50l
>
> Vote result thread:
>   • https://lists.apache.org/thread/wymh634mxc0l3y0j7vy9jx1bdw48d5g0
>
> The release candidate:
>   • https://dist.apache.org/repos/dist/dev/incubator/hugegraph/1.3.0
>
> Git tag for the release:
>   • https://github.com/apache/incubator-hugegraph/tree/1.3.0
>
> Git tag & Commit hash for the release:
>   • https://github.com/apache/incubator-hugegraph/tree/release-1.3.0  
> (6a4041e)
>   • https://github.com/apache/incubator-hugegraph-toolchain/tree/release-1.3.0
>  (0dd2339)
>   • https://github.com/apache/incubator-hugegraph-commons/tree/release-1.3.0
>  (c883f56)
>   • https://github.com/apache/incubator-hugegraph-ai/tree/release-1.3.0
> (4f48116)
>
> Keys to verify the Release Candidate:
>   • https://downloads.apache.org/incubator/hugegraph/KEYS
>
> The release GPG user ID: JackyYang (yangji...@apache.org)
>
>
> The vote will be open for at least 72 hours or until necessary number
> of votes are reached.
>
> Please vote accordingly:
>   [ ] +1 approve
>   [ ] +0 no opinion
>   [ ] -1 disapprove with the reason
>
> More detail checklist  please refer:
>   • 
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
>
> Steps to validate the release，Please refer to:
>   • 
> https://hugegraph.apache.org/docs/contribution-guidelines/validate-release/
> (EN)
>   • 
> https://hugegraph.apache.org/cn/docs/contribution-guidelines/validate-release/
> (CN)
>
>
> Thanks,
> On behalf of Apache HugeGraph(Incubating) community
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

-
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

[Willem Jiang]

+1 （binding）

Willem

On Wed, Mar 13, 2024 at 2: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] Graduate Apache Paimon (Incubating) as a Top Level Project

[Willem Jiang]

+1 binding.


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Fri, Mar 8, 2024 at 6:51 PM Yu Li  wrote:
>
> Hi All,
>
> We've got positive feedback on the DISCUSS thread for graduation [1],
> and would like to start an official VOTE thread now.
>
> Below are some facts and project highlights from the incubation phase
> as well as the draft resolution:
>
> - Currently, our community consists of 18 committers (including
> mentors) from ~10 different companies, with 11 serving as PPMC
> members.
> - So far, we have boasted 132 contributors.
> - Throughout the incubation period, we've made 5 releases in 12
> months, at a stable pace.
> - We've had 3 different release managers to date.
> - Our software is used in production by 20+ well known entities.
> - As yet, we have opened 1,363 issues with 1,083 successfully
> resolved, including the period as a sub-project of Apache Flink.
> - We have submitted a total of 2,166 PRs, out of which 2,091 have been
> merged or closed.
> - We have met all maturity criteria as outlined in [2].
>
> Please vote on the resolution pasted below to graduate Apache Paimon
> from the Incubator to the Top Level Project.
>
>  [ ] +1 Graduate Apache Paimon from the Incubator.
>  [ ] +0 No opinion.
>  [ ] -1 Don't graduate Apache Paimon from the Incubator because ...
>
> This vote will open for at least 72 hours.
>
> We would like to thank everyone who has participated in the Apache
> Paimon community. We would also like to thank the Apache Incubator
> community as well as Apache Infrastructure team and general ASF
> community for your support.
>
> [1] https://lists.apache.org/thread/012rfy2zvnhqh39foncwvdpvy9fzry1q
> [2] 
> https://cwiki.apache.org/confluence/display/PAIMON/Apache+Maturity+Model+Assessment+for+Paimon
>
> ---
>
> Establish the Apache Paimon Project
>
> WHEREAS, the Board of Directors deems it to be in the best interests of
> the Foundation and consistent with the Foundation's purpose to establish
> a Project Management Committee charged with the creation and maintenance
> of open-source software, for distribution at no charge to the public,
> related to a unified lake storage to build dynamic tables for both
> stream and batch processing with big data compute engines, supporting
> high-speed data ingestion and real-time data query.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Paimon Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Paimon Project be and hereby is responsible
> for the creation and maintenance of software related to a unified lake
> storage to build dynamic tables for both stream and batch processing
> with big data compute engines, supporting high-speed data ingestion and
> real-time data query; and be it further
>
> RESOLVED, that the office of "Vice President, Apache Paimon" be and
> hereby is created, the person holding such office to serve at the
> direction of the Board of Directors 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 FURTHER RESOLVED, that Jingsong Lee be appointed
> to the office of Vice President, Apache Paimon, 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 Paimon Project be and hereby is tasked with
> the migration and rationalization of the Apache Incubator Paimon
> podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Paimon podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.
>
> ---
>
> Best Regards,
> Yu (on behalf of the Apache Paimon PPMC)
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

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

[Willem Jiang]

+1 (binding)
Good luck!

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Fri, Mar 8, 2024 at 6:45 PM Yu Li  wrote:
>
> Hi All,
>
> We've got positive feedback on the DISCUSS thread for graduation [1],
> and would like to start an official VOTE thread now.
>
> Below are some facts and project highlights from the incubation phase
> as well as the draft resolution:
>
> - Currently, our community consists of 19 committers (including
> mentors) from more than 10 companies, with 13 serving as PPMC members.
> - So far, we have boasted 81 contributors.
> - Throughout the incubation period, we've made 6 releases in 16
> months, at a stable pace.
> - We've had 6 different release managers to date.
> - Our software is used in production by 10+ well known entities.
> - As yet, we have opened 1,302 issues with 1,191 successfully resolved.
> - We have submitted a total of 1,840 PRs, out of which 1,830 have been
> merged or closed.
> - We have met all maturity criteria as outlined in [2].
>
> Please vote on the resolution pasted below to graduate Apache Celeborn
> from the Incubator to the Top Level Project.
>
>  [ ] +1 Graduate Apache Celeborn from the Incubator.
>  [ ] +0 No opinion.
>  [ ] -1 Don't graduate Apache Celeborn from the Incubator because ...
>
> This vote will open for at least 72 hours.
>
> We would like to thank everyone who have participated in the Apache
> Celeborn community. We would also like to thank the Apache Incubator
> community as well as Apache Infrastructure team and general ASF
> community for your support.
>
> [1] https://lists.apache.org/thread/9gyhhnhj5osjom38v9ws1b7o7fbf7fqh
> [2] 
> https://cwiki.apache.org/confluence/display/CELEBORN/Apache+Maturity+Model+Assessment+for+Celeborn
>
> ---
>
> Establish the Apache Celeborn Project
>
> WHEREAS, the Board of Directors deems it to be in the best interests of
> the Foundation and consistent with the Foundation's purpose to establish
> a Project Management Committee charged with the creation and maintenance
> of open-source software, for distribution at no charge to the public,
> related to an intermediate data service for big data computing engines
> to boost performance, stability, and flexibility.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Celeborn Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Celeborn Project be and hereby is responsible
> for the creation and maintenance of software related to an intermediate
> data service for big data computing engines to boost performance,
> stability, and flexibility; and be it further
>
> RESOLVED, that the office of "Vice President, Apache Celeborn" be and
> hereby is created, the person holding such office to serve at the
> direction of the Board of Directors as the chair of the Apache Celeborn
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache Celeborn
> Project; and be it further
>
> RESOLVED, that the persons listed immediately below be and hereby are
> appointed to serve as the initial members of the Apache Celeborn
> Project:
>
> * Becket Qin 
> * Cheng Pan 
> * Duo Zhang 
> * Ethan Feng 
> * Fu Chen 
> * Jiashu Xiong 
> * Kerwin Zhang 
> * Keyong Zhou 
> * Lidong Dai 
> * Willem Ning Jiang 
> * Wu Wei 
> * Yi Zhu 
> * Yu Li 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Keyong Zhou be appointed to
> the office of Vice President, Apache Celeborn, to serve in accordance
> with and subject to the direction of the Board of Directors and the
> Bylaws of the Foundation until death, resignation, retirement, removal
> or disqualification, or until a successor is appointed; and be it
> further
>
> RESOLVED, that the Apache Celeborn Project be and hereby is tasked with
> the migration and rationalization of the Apache Incubator Celeborn
> podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Celeborn podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.
>
> ---
>
> Best Regards,
> Yu (on behalf of the Apache Celeborn PPMC)
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

Re: [VOTE] Have Amoro join the Incubator

[Willem Jiang]

+1 (binding)

Willem

On Sun, Mar 3, 2024 at 9:45 AM Justin Mclean  wrote:
>
> Hi,
>
> Following on from the discussion of the Amoro proposal [1][2], let's vote on 
> having it join the Incubator.
>
> Please cast your vote:
>
> [ ] +1, have it join the Incubator as an incubating project
> [ ] +0, I have no strong opinion either way
> [ ] -1, do not have it join the Incubator because...
>
> Kind Regards,
> Justin
>
> 1. https://cwiki.apache.org/confluence/display/INCUBATOR/AmoroProposal
> 2. https://lists.apache.org/thread/7t2bm6x19zq2d79cn8jj2wqd3f2t3k00

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

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

[Willem Jiang]

+1 (binding)
Good luck!

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Mon, Feb 26, 2024 at 7:25 PM PJ Fanning  wrote:
>
> Hi everyone,
>
> We have positive feedback on the Pekko Vote thread [1] (result [2]).
>
> I'd like to start an official Incubator VOTE thread now.
>
> Below are some facts and project highlights from the incubation phase
> as well as the draft resolution:
>
> * All modules have at least a v1.0.0 release
> * 19 releases (across 12 modules) [3]
> * Evidence of good uptake of the Pekko releases and a large number of
> ecosystem libs now support Pekko - over 100 non Apache libraries use
> Pekko libs under the hood
> * well over 1000 PRs merged
> * 25+ code contributors
> * We've had 3 different release managers to date.
> * dozens more users who have been involved in discussions, code
> reviews, raising issues, etc.
> * We have met all maturity criteria as outlined in [4].
>
>
> Please vote on the resolution pasted below to graduate Apache Pekko
> from the Incubator to the Top Level Project.
>
>  [ ] +1 Graduate Apache Pekko from the Incubator.
>  [ ] +0 No opinion.
>  [ ] -1 Don't graduate Apache Pekko from the Incubator because ...
>
> This vote will open for at least 72 hours.
>
> I would like to thank everyone who have participated in the Apache
> Pekko community. I would also like to thank the Apache Incubator
> community as well as Apache Infrastructure team and general ASF
> community for your support.
>
>
> [1] https://lists.apache.org/thread/q7jjmp7zpcxko607v5hvj514dyf6o8bx
> [2] https://lists.apache.org/thread/tsb7b8bkgfkts1nstmj413qocztj0s5o
> [3] https://incubator.apache.org/projects/pekko.html
> [4] 
> https://cwiki.apache.org/confluence/display/PEKKO/Apache+Maturity+Model+Assessment+for+Pekko
>
>
>
>  ---
>
> Establish the Apache Pekko Project
>
>
> WHEREAS, the Board of Directors deems it to be in the best interests
> of the Foundation and consistent with the Foundation's purpose to
> establish a Project Management Committee charged with the creation and
> maintenance of open-source software, for distribution at no charge to
> the public, related to Pekko: a toolkit and an ecosystem for building
> highly concurrent, distributed, reactive and resilient applications
> for Java and Scala.
>
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Pekko Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
>
> RESOLVED, that the Apache Pekko Project be and hereby is responsible
> for the creation and maintenance of software related to Pekko: a
> toolkit and an ecosystem for building highly concurrent, distributed,
> reactive and resilient applications for Java and Scala.; and be it
> further
>
>
> RESOLVED, that the office of "Vice President, Apache Pekko" be and
> hereby is created, the person holding such office to serve at the
> direction of the Board of Directors as the chair of the Apache Pekko
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache Pekko
> Project; and be it further
>
>
> RESOLVED, that the persons listed immediately below be and hereby are
> appointed to serve as the initial members of the Apache Pekko Project:
>
> Claude Warren (claude)
> Jean-Baptiste Onofré (jbonofre)
> Justin Mclean (jmclean)
> PJ Fanning (fanningpj)
> Roman Shaposhnik (rvs)
> Ryan Skraba (rskraba)
> Sheng Wu (wu-sheng)
> Alexandru Nedelcu (alexelcu)
> Arnout Engelen (engelen)
> Dani Schroeter (dsc)
> Greg Methvin (gregm)
> Guobin Li (liguobin)
> He Pin (hepin)
> Johannes Rudolph (jrudolph)
> Jonas Chapuis (jchapuis)
> Matthew de Detrich (mdedetrich)
> Nicolas Vollmar (nvollmar)
> Samuele Resca (samueler)
> Sean Glover (seanglover)
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that PJ Fanning be appointed
> to the office of Vice President, Apache Pekko, to serve in accordance
> with and subject to the direction of the Board of Directors and the
> Bylaws of the Foundation until death, resignation, retirement, removal
> or disqualification, or until a successor is appointed; and be it
> further
>
> RESOLVED, that the Apache Pekko Project be and hereby is tasked with
> the migration and rationalization of the Apache Incubator Pekko
> podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Pekko podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.
>
>
> Thanks,
> PJ
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

Re: Update Website Template (WAS: Help to get the Wayang project website in shape)

[Willem Jiang]

+1 for providing some modern templates for the incubating projects.

Cheers,

Willem Jiang


On Sun, Feb 11, 2024 at 1:26 PM tison  wrote:
>
> I've pushed the code to 'docusarus' branch on this repo, and file a
> ticket on INFRA [1] to ask for some privileges actions.
>
> Best,
> tison.
>
> [1] https://issues.apache.org/jira/browse/INFRA-25486
>
> tison  于2024年2月10日周六 18:32写道：
> >
> > It seems that the repo is foundation-wise that I have the permission to 
> > move forward this effort.
> >
> > I'll push the branch and update the README. And then ask for INFRA to make 
> > it the default branch, as well as setting the repo as a repo template.
> >
> > I believe comdev and the Incubator are related to these actions so I post 
> > here for visibility, and welcome any feedback if you second this or have 
> > suggestions.
> >
> > Best,
> > tison.
> >
> >
> > tison 于2024年2月4日 周日23:16写道：
> >>
> >> Hi,
> >>
> >> I finally find some time to prepare a demo for the new website template 
> >> [1].
> >>
> >> It may still open to be improved including a download page template
> >> and a community page template, as well as some guides as its docs. But
> >> I'd like to first collecting feedback and finding which PMC is
> >> responsible for this repository [2].
> >>
> >> The background is that our current template is quite old and not
> >> updated for the past six years. Few people understand those techniques
> >> and have a hard time to build their own site. Also, new policy
> >> compliance and new techniques benefits can be included in the template
> >> to help new projects (podlings) build a wonderful site.
> >>
> >> I'm glad to maintain this repo but I find myself has no permission
> >> over this repo. So again, which PMC is responsible for this
> >> repository?
> >>
> >> Best,
> >> tison.
> >>
> >> [1] https://github.com/tisonkun/apache-website-template/tree/docusaurus
> >> [2] https://github.com/apache/apache-website-template/
> >>
> >> Alex Porcelli  于2024年1月30日周二 04:53写道：
> >> >
> >> > Another shout-out for tison and the Apache Fury to provide such a nice
> >> > starting point for new websites.
> >> >
> >> > I managed to put, for now, a simple placeholder website for Apache KIE
> >> > (incubation).
> >> >
> >> > Thank you tison and the Apache Fury community!
> >> >
> >> > On Fri, Jan 26, 2024 at 4:10 AM Xuanwo  wrote:
> >> > >
> >> > > > I managed to move our old website to Docusaurus in one day - using 
> >> > > > the template
> >> > > > structure from Fury, if you don’t mind.
> >> > >
> >> > > Congrats!
> >> > >
> >> > > On Fri, Jan 26, 2024, at 17:07, Alexander Alten-Lorenz wrote:
> >> > > > Hey tison,
> >> > > >
> >> > > > Thank you for the head-up. I managed to move our old website to
> >> > > > Docusaurus in one day - using the template structure from Fury, if 
> >> > > > you
> >> > > > don’t mind. Awesome stuff, would love when we’d had a template for 
> >> > > > the
> >> > > > podlings to setup a good looking, SEO friendly project page. That’s
> >> > > > needed to grow the community!
> >> > > >
> >> > > > Cheers, thanks again,
> >> > > >  —Alex
> >> > > >
> >> > > >> On Jan 25, 2024, at 12:01, tison  wrote:
> >> > > >>
> >> > > >> Hi Alexander,
> >> > > >>
> >> > > >> I use Docusaurus for Kvrocks and Fury. Their configuration should be
> >> > > >> straightforward to follow already. The most simple one now is
> >> > > >> https://github.com/apache/incubator-fury-site.
> >> > > >>
> >> > > >> Also, Docu is well-documented https://docusaurus.io/docs.
> >> > > >>
> >> > > >> I'm thinking of updating the website template [1] with Docu but have
> >> > > >> not yet had time and understand which PMC manages this project.
> >> > > >>
> >> > > >> Best,
> >> > > >> tison.
> >> > > >>
> >> > > >> [1] https://github.com/ap

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

[Willem Jiang]

+1 （binding）
Here is what I checked:
[x] Download links are valid.
[x] Checksums and signatures.
[x] LICENSE/NOTICE files exist
[x] DISCLAIMER files exist
[x] Artifacts has the Incubating in the name
[x] No unexpected binary files

Thanks，

Willem Jiang



On Tue, Feb 6, 2024 at 11:12 AM LinkinStar  wrote:
>
> Hello,
>
> This is a call for vote to release Apache Answer(Incubating) version
> v1.2.5-RC2.
>
> The vote thread:
> https://lists.apache.org/thread/qjsmh7y4fb946pso5nwrbfjntfydhslh
>
> Vote Result:
> https://lists.apache.org/thread/89jgwznxn69296nxl5fn5jtd9ywcndog
>
> The release candidates:
>
> https://dist.apache.org/repos/dist/dev/incubator/answer/1.2.5-incubating-RC2/
>
> Release notes:
> https://github.com/apache/incubator-answer/releases/tag/v1.2.5-RC2
>
> Git tag for the release:
> https://github.com/apache/incubator-answer/releases/tag/v1.2.5-RC2
>
> Git commit id for the release:
>
> https://github.com/apache/incubator-answer/commit/5132cb391238cf26d3d206403b5b737451fd189a
>
> Keys to verify the Release Candidate:
> The artifacts signed with PGP key [C34934CC], corresponding to [
> linkins...@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.
>
> To compile from the source, please refer to:
>
> https://github.com/apache/incubator-answer#building-from-source
>
> Thanks,
> LinkinStar

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

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

[Willem Jiang]

>From my understanding, we don't need to add the ASF headers on the
markdown or JSON files, as the license header comment could cause some
trouble for other software to consume.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Tue, Jan 16, 2024 at 6:32 PM Jean-Baptiste Onofré  wrote:
>
> +0.8 (binding)
>
> I checked:
> - hash and signature are OK
> - incubating is in name
> NB: some files doesn't contain ASF headers whereas they can (for
> instance few md files like README.md or DevelopmentManual.md).
> NB: I found some binaries (png, svg, ... from the grafana dashboard)
> in the source distribution. That's OK imho but just wanted to mention
> it.
> It would be great to fix that for the next release at least.
>
> Regards
> JB
>
> On Fri, Jan 5, 2024 at 11:30 AM Zikuan An  wrote:
> >
> > Hello everyone,
> >
> > This is a call for the vote to release Apache DevLake (Incubating)
> > v0.19.0-rc4.
> > The Apache DevLake community has voted on and approved a proposal
> > to release Apache DevLake (Incubating) version v0.19.0-rc4.
> >
> >
> > We particularly checked the updates on the license of yarn-3.4.1.cjs (see
> > PR: https://github.com/apache/incubator-devlake/pull/6711) based on the
> > relatively specific and clear parts of the feedback we received and the
> > practices of other ASF projects sharing the similar problems such as Apache
> > BRPC, Apache Dubbo, etc.
> >
> >
> > We now kindly request the Incubator PMC members review and vote on this
> > incubator release.
> >
> > Community vote thread:
> >
> > https://lists.apache.org/thread/pk7w87rdqos6j949dtktzwcosokmw5ql
> >
> >
> > Community vote result thread:
> >
> > https://lists.apache.org/thread/5wb75wyrqylr7gkl4b1jbqjqpvjm6tpm
> >
> >
> > The release candidates:
> >
> > https://dist.apache.org/repos/dist/dev/incubator/devlake/0.19.0-incubating-rc4
> >
> >
> > Git tag for the release:
> >
> > https://github.com/apache/incubator-devlake/releases/tag/v0.19.0-rc4
> >
> >
> > Keys to verify the Release Candidate:
> >
> > https://downloads.apache.org/incubator/devlake/KEYS
> >
> >
> > How to build:
> >
> > https://devlake.apache.org/docs/DeveloperManuals/DeveloperSetup
> >
> >
> > 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
> >
> >
> > Thanks
> >
> > Zikuan An
>
> -
> 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 DevLake (Incubating) v0.19.0-rc4

[Willem Jiang]

+1 (binding)
Here is what I checked:
[x] Download links are valid.
[x] Checksums and signatures.
[x] LICENSE/NOTICE files exist
[x] DISCLAIMER files exist
[x] Artifacts has the Incubating in the name
[x] No unexpected binary files

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem


On Fri, Jan 5, 2024 at 6:32 PM Zikuan An  wrote:
>
> Hello everyone,
>
> This is a call for the vote to release Apache DevLake (Incubating)
> v0.19.0-rc4.
> The Apache DevLake community has voted on and approved a proposal
> to release Apache DevLake (Incubating) version v0.19.0-rc4.
>
>
> We particularly checked the updates on the license of yarn-3.4.1.cjs (see
> PR: https://github.com/apache/incubator-devlake/pull/6711) based on the
> relatively specific and clear parts of the feedback we received and the
> practices of other ASF projects sharing the similar problems such as Apache
> BRPC, Apache Dubbo, etc.
>
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Community vote thread:
>
> https://lists.apache.org/thread/pk7w87rdqos6j949dtktzwcosokmw5ql
>
>
> Community vote result thread:
>
> https://lists.apache.org/thread/5wb75wyrqylr7gkl4b1jbqjqpvjm6tpm
>
>
> The release candidates:
>
> https://dist.apache.org/repos/dist/dev/incubator/devlake/0.19.0-incubating-rc4
>
>
> Git tag for the release:
>
> https://github.com/apache/incubator-devlake/releases/tag/v0.19.0-rc4
>
>
> Keys to verify the Release Candidate:
>
> https://downloads.apache.org/incubator/devlake/KEYS
>
>
> How to build:
>
> https://devlake.apache.org/docs/DeveloperManuals/DeveloperSetup
>
>
> 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
>
>
> Thanks
>
> Zikuan An

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

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

[Willem Jiang]

@Xuanwo
Could you add a summary of the branding and trademark issues which
Justin found out and those OpenDAL PPMC addressed?
It will help us do a quick review to find out if there is any thing we
are missing.

Thanks,

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Wed, Jan 10, 2024 at 9:53 AM Xuanwo  wrote:
>
> Hi all,
>
> The vote for graduating Apache OpenDAL(incubating)[1] to a TLP has passed.
>
> There are 10 binding +1 votes, 14 non-binding +1 votes, and 1 binding -1
> votes.
>
> *+10 Binding*
> - Sheng Wu
> - tison
> - Shaofeng Shi
> - Ted Liu
> - Craig L Russell
> - He Xiaoqiao
> - PJ Fanning
> - 张铎(Duo Zhang)
> - Enrico Olivelli
> - Willem Jiang
>
> *+14 Non-binding*
> - Suyan
> - hulk
> - PsiACE
> - Forward Xu
> - vin jake
> - Pragma Twice
> - Mingzhuo Yin
> - Jun Ouyang
> - Liuqing Yue
> - Chunshao Ren
> - Morris Tai
> - Shawn Yang
> - Huajie Wang
> - Eason Chen
>
> *-1 Binding*
> - Justin Mclean (note: the branding and trademark issues have been resolved 
> and addressed)
>
> Thanks all for participating in the vote. Thanks to the Incubator, the
> OpenDAL community, our mentors, and everyone who helped trough out the
> journey.
>
> We will proceed and submit the graduation proposal to the ASF board.
>
> [1] https://lists.apache.org/thread/l2wgvwjnm6okkjxvrxp37zc06tfdrolk
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

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

[Willem Jiang]

+1 (binding)

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Fri, Dec 29, 2023 at 8:22 AM 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, that the Apache OpenDAL Project be and hereby is tasked with
> the migration and rationalization of the Apache Incubator OpenDAL
> podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> OpenDAL podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.
>
> Xuanwo
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

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

[Willem Jiang]

+1 binding

Here is what I checked:
[x] Download links are valid.
[x] Checksums and signatures.
[x] LICENSE/NOTICE files exist
[x] DISCLAIMER files exist
[x] Artifacts has the Incubating in the name
[x] No unexpected binary files


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem


On Mon, Dec 25, 2023 at 10:55 AM LinkinStar  wrote:
>
> Hello,
>
> This is a call for vote to release Apache Answer(Incubating) version
> v1.2.1-RC1.
>
> There was an issue with the previous signature, so I re-signed the
> release files. The previous vote was
> https://lists.apache.org/thread/mrflkg9j1sv4c3obsbmw9by26sf54vvp.
>
> The vote thread:
> https://lists.apache.org/thread/nlvtcsc8dxowqjy3vdd1d7cvm0pk0w0o
>
> Vote Result:
> https://lists.apache.org/thread/327wbzwr61kyjnkv35v1ppvnzh103myo
>
> The release candidates:
>
> https://dist.apache.org/repos/dist/dev/incubator/answer/1.2.1-incubating-RC1/
>
> Release notes:
> https://github.com/apache/incubator-answer/releases/tag/v1.2.1-RC1
>
> Git tag for the release:
> https://github.com/apache/incubator-answer/releases/tag/v1.2.1-RC1
>
> Git commit id for the release:
>
> https://github.com/apache/incubator-answer/commit/82fdfc77636d8d1ce28710d929a8c22bb52834ef
>
> Keys to verify the Release Candidate:
> The artifacts signed with PGP key [C34934CC], corresponding to [
> linkins...@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.
>
> To compile from the source, please refer to:
>
> https://github.com/apache/incubator-answer#building-from-source
>
> Thanks,
> LinkinStar

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

Re: [VOTE] Accept Gluten Into the ASF Incubator

[Willem Jiang]

+1 (binding)

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Thu, Jan 4, 2024 at 10:48 AM ShaoFeng Shi  wrote:
>
> Hi Incubator,
>
> Following the discussion [DISCUSS] Gluten proposal[1],
> I am starting this official vote for the Gluten project.
>
> Here is their proposal:
> https://cwiki.apache.org/confluence/display/INCUBATOR/GlutenProposal
>
> Please cast your vote:
>
> [ ] +1, bring into the Incubator
> [ ] +0, I don't care either way
> [ ] -1, do not bring Gluten into the Incubator, because...
>
> The vote will open for one week from today.
>
> [1] https://lists.apache.org/thread/xgsm75t721vgnlthgy84909ggqok77j4
>
> Best regards,
>
> Shaofeng Shi 史少锋
> Apache Kylin PMC member,
> Apache Incubator PMC member,
> Email: shaofeng...@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 OpenDAL(incubating) 0.44.1 - Incubator Vote Round 1

[Willem Jiang]

+1 Binding.

Here is what I checked:
[x] Download links are valid.
[x] Checksums and signatures.
[x] LICENSE/NOTICE files exist
[x] DISCLAIMER files exist
[x] Artifacts has the Incubating in the name
[x] No unexpected binary files
[x] All source files have ASF headers


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Wed, Jan 3, 2024 at 3:34 PM Xuanwo  wrote:
>
> Hello Incubator PMC,
>
> The Apache OpenDAL community has voted and approved the release of Apache
> OpenDAL(incubating) 0.44.1. We now kindly request the IPMC members
> review and vote for this release.
>
> OpenDAL is a data access layer that allows users to easily and efficiently
> retrieve data from various storage services in a unified way.
>
> OpenDAL community vote thread:
>
> https://lists.apache.org/thread/r76vnpfm2g1rhf1q33x7bmtmw137dlb4
>
> Vote result thread:
>
> https://lists.apache.org/thread/rbh65l5sbrd1bd45d2nm2h20lqhzy7x1
>
> The release candidate:
>
> https://dist.apache.org/repos/dist/dev/incubator/opendal/0.44.1-rc.1/
>
> This release has been signed with a PGP available here:
>
> https://downloads.apache.org/incubator/opendal/KEYS
>
> Git tag for the release:
>
> https://github.com/apache/incubator-opendal/releases/tag/v0.44.1-rc.1
>
> Maven staging repo:
>
> https://repository.apache.org/content/repositories/orgapacheopendal-1023/
>
> Please download, verify, and test.
>
> The VOTE will be open for at least 72 hours and until the necessary
> number of votes are reached.
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> To learn more about apache opendal, please see https://opendal.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
>
> More detailed checklist please refer to:
> https://github.com/apache/incubator-opendal/tree/main/scripts
>
> To compile from source, please refer to:
> https://github.com/apache/incubator-opendal/blob/main/CONTRIBUTING.md
>
> Here is python script in release to help you verify the release candidate:
>
> ./scripts/verify.py
>
> Thanks
>
> Xuanwo
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

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

[Willem Jiang]

Hi Yu,

"Do release files have the word incubating in their name?" is for the
release kits, not the maven artifacts. I think we can polish the
checklist for it.
The examples that you showed are all the maven artifacts version,
which is not required for the incubator release kit check.

Just my 2 cents.


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Tue, Dec 26, 2023 at 10:37 AM Yu Li  wrote:
>
> Well, this is something worth a double check then.
>
> In the incubator release checklist document [1] it explicitly mentions "Do
> release files have the word incubating in their name?", and we need to
> clarify whether that means the tar file only or binary files inside also.
>
> Checking the jars deployed onto the maven repo, we could see those with
> incubating in their names (such as Spark [2] and Flink [3] in their old
> times, or Livy [4] and Paimon [5] still under incubation) and those
> without. So it seems the standard is not aligned.
>
> For me, include "incubating" in the jar file name could better remind our
> users that they are using something still under apache incubation, no
> matter where they get the binaries from, which has similar effect as the
> DISCLAIMER file in the tar ball. However, if this is *confirmed* to be only
> nice-to-have rather than required, I could withdraw my -1, and I'd suggest
> to document the standard more explicitly in our release checklist.
>
>
> Best Regards,
> Yu
>
> [1]
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> [2]
> https://mvnrepository.com/artifact/org.apache.spark/spark-core_2.10/0.9.0-incubating
> [3]
> https://mvnrepository.com/artifact/org.apache.flink/flink-core/0.7.0-incubating
> [4]
> https://mvnrepository.com/artifact/org.apache.livy/livy-core_2.12/0.8.0-incubating
> [5]
> https://mvnrepository.com/artifact/org.apache.paimon/paimon-common/0.6.0-incubating
>
>
> On Mon, Dec 25, 2023 at 8:46 PM PJ Fanning  wrote:
>
> > The jars don't have to have incubating in the name, as far as I know.
> > The source release file (the tgz) has to but I think it is not
> > required elsewhere.
> >
> > On Mon, 25 Dec 2023 at 12:48, Yu Li  wrote:
> > >
> > > -1 (binding)
> > >
> > >
> > > - Checked sum and signatures: OK
> > >
> > > - Checked DISCLAIMER file exists: OK
> > >
> > > - Checked LICENSE and NOTICE files: OK
> > >
> > > - Checked no binary files in source package: OK
> > >
> > > - Checked release file name and location: FAILED
> > >   - The HugeGraph jar files in apache-hugegraph-incubating-1.2.0.tar.gz
> > > (under the lib directory) don't have the word "incubating" in their
> > names.
> > > For example, I see file with name like "hugegraph-api-1.2.0.jar"
> > >
> > > Best Regards,
> > > Yu
> > >
> > >
> > > On Sat, 23 Dec 2023 at 23:26, simon  wrote:
> > >
> > > > Hello Incubator Community,
> > > >
> > > > This is a call for vote to release Apache HugeGraph (Incubating)
> > version
> > > > 1.2.0
> > > >
> > > > The Apache HugeGraph community has voted on and approved a proposal to
> > > > release Apache HugeGraph(Incubating) version 1.2.0
> > > >
> > > > We now kindly request the Incubator PMC members review and vote on this
> > > > incubator release.
> > > >
> > > > HugeGraph community vote thread:
> > > > - https://lists.apache.org/thread/mnxld09b2ozwldcxb0rpp6s7cdbdnvsw
> > > >
> > > > Vote result thread:
> > > > - https://lists.apache.org/thread/wns67scpfvcltk33pl403jl48pd0hc61
> > > >
> > > > The release candidate:
> > > > - https://dist.apache.org/repos/dist/dev/incubator/hugegraph/1.2.0/
> > > >
> > > > Git tag & Commit hash for the release:
> > > > - https://github.com/apache/incubator-hugegraph/tree/1.2.0  (7635c67)
> > > > - https://github.com/apache/incubator-hugegraph-toolchain/tree/1.2.0
> > > >  (f85dcf3)
> > > > - https://github.com/apache/incubator-hugegraph-computer/tree/1.2.0
> > > >  (0500fec)
> > > > - https://github.com/apache/incubator-hugegraph-commons/tree/1.2.0
> > > >  (33fa9ed)
> > > >
> > > > Release notes:
> > > > -
> > > >
> > https://hugegraph.apache.org/docs/changelog/hugegraph-1.2.0-release-notes/
> > > >
> > > > Keys to verify the Release Candidate:
> > > 

Re: [VOTE] Accept HoraeDB Into the ASF Incubator

[Willem Jiang]

+1 (binding)

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Mon, Dec 4, 2023 at 9:01 PM tison  wrote:
>
> Hi Incubator
>
> Following the discussion [DISCUSS] HoraeDB proposal[1],
> I am starting this official vote for the HoraeDB project.
>
> Here is their proposal:
> https://cwiki.apache.org/confluence/display/INCUBATOR/HoraeDB+Proposal
>
> Please cast your vote:
>
> [ ] +1, bring into the Incubator
> [ ] +0, I don't care either way
> [ ] -1, do not bring HoraeDB into the Incubator, because...
>
> The vote will open for one week from today, Dec. 4th, 2023
>
> Best,
> tison.
>
> [1] https://lists.apache.org/thread/6vbhv4soxw45yf2w9l495ofdqr3029ll
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

Re: [VOTE] Release Apache OpenDAL(incubating) v0.43.0-rc.3 - Incubator Vote Round 1

[Willem Jiang]

+1 Binding.

Here is what I checked:
[x] Download links are valid.
[x] Checksums and signatures.
[x] LICENSE/NOTICE files exist
[x] DISCLAIMER files exist
[x] Artifacts has the Incubating in the name
[x] No unexpected binary files
[x] All source files have ASF headers

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Tue, Dec 5, 2023 at 11:29 AM tison  wrote:
>
> +1 binding
>
> [x] Download links are valid.
> [x] Checksums and signatures.
> [x] LICENSE/NOTICE files exist
> [x] DISCLIAMER files exist
> [x] No unexpected binary files
> [x] All source files have ASF headers
> [x] Can compile from source
>   cargo build
>   cd bindings/java ; ./mvnw test
>
>
> Best,
> tison.
>
> Xuanwo  于2023年12月4日周一 11:40写道：
> >
> > Carrying my non-binding +1 vote from the opendal community.
> >
> > On Mon, Dec 4, 2023, at 11:30, G-XD wrote:
> > > Hello Incubator PMC,
> > >
> > > The Apache OpenDAL community has voted and approved the release of Apache
> > > OpenDAL(incubating) v0.43.0-rc.3. We now kindly request the IPMC members
> > > review and vote for this release.
> > >
> > > OpenDAL is a data access layer that allows users to easily and efficiently
> > > retrieve data from various storage services in a unified way.
> > >
> > > OpenDAL community vote thread:
> > >
> > > https://lists.apache.org/thread/7pt30hmwv4gkdqh72oq680vjsbbw0fns
> > >
> > > Vote result thread:
> > >
> > > https://lists.apache.org/thread/52qd705vs9tf8cw10zvmxtzlq5t31x92
> > >
> > > The release candidate:
> > >
> > > https://dist.apache.org/repos/dist/dev/incubator/opendal/0.43.0-rc.3/
> > >
> > > This release has been signed with a PGP available here:
> > >
> > > https://downloads.apache.org/incubator/opendal/KEYS
> > >
> > > Git tag for the release:
> > >
> > > https://github.com/apache/incubator-opendal/releases/tag/v0.43.0-rc.3
> > >
> > > Maven staging repo:
> > >
> > > https://repository.apache.org/content/repositories/orgapacheopendal-1021/
> > >
> > > Please download, verify, and test.
> > >
> > > The VOTE will be open for at least 72 hours and until the necessary
> > > number of votes are reached.
> > >
> > > [ ] +1 approve
> > > [ ] +0 no opinion
> > > [ ] -1 disapprove with the reason
> > >
> > > To learn more about apache opendal, please see https://opendal.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
> > >
> > > More detailed checklist please refer to:
> > > https://github.com/apache/incubator-opendal/tree/main/scripts
> > >
> > > To compile from source, please refer to:
> > > https://github.com/apache/incubator-opendal/blob/main/CONTRIBUTING.md
> > >
> > > Here is python script in release to help you verify the release candidate:
> > >
> > > ./scripts/verify.py
> > >
> > > Thanks
> > >
> > > Xiangdong Gai
> >
> > --
> > Xuanwo
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

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

[Willem Jiang]

+1(binding).

Here is what I checked:
- The checksums and signatures are validated.
- The LICENSE and NOTICE files look good to me.
- There is a DISCLAIMER file about incubating.
- No binary files in the source release.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Fri, Nov 10, 2023 at 10:28 PM Zikuan An  wrote:
>
> Hello everyone,
>
> This is a call for the vote to release Apache DevLake (Incubating)
> v0.19.0-rc2.
> The Apache DevLake community has voted on and approved a proposal to
> release Apache DevLake (Incubating) version v0.19.0-rc2.
>
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Community vote thread:
>
> https://lists.apache.org/thread/zqhrctqz39xyslfjsd0zz30gtdbv4t20
>
>
> Community vote result thread:
>
> https://lists.apache.org/thread/g06ns1vbqopyw6r460m25pvcvwh932s6
>
>
> The release candidates:
>
> https://dist.apache.org/repos/dist/dev/incubator/devlake/0.19.0-incubating-rc2
>
>
> Git tag for the release:
>
> https://github.com/apache/incubator-devlake/releases/tag/v0.19.0-rc2
>
>
> Keys to verify the Release Candidate:
>
> https://downloads.apache.org/incubator/devlake/KEYS
>
>
> How to build:
>
> https://devlake.apache.org/docs/DeveloperManuals/DeveloperSetup
>
>
> 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
>
>
> Thanks
>
> Zikuan An

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

Re: [VOTE] Release Apache OpenDAL(incubating) v0.42.0-rc.3 - Incubator Vote Round 1

[Willem Jiang]

+1 binding.

I checked
- incubating in the release kit name
- The checksums and signatures are validated.
- The LICENSE and NOTICE files look good to me.
- There is a DISCLAIMER in the release kits
- No binary files in the source release kits


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Sun, Nov 12, 2023 at 10:12 AM Mingzhuo Yin  wrote:
>
> Hello Incubator PMC,
>
> The Apache OpenDAL community has voted and approved the release of Apache
> OpenDAL(incubating) v0.42.0-rc.3. We now kindly request the IPMC members
> review and vote for this release.
>
> OpenDAL is a data access layer that allows users to easily and efficiently
> retrieve data from various storage services in a unified way.
>
> OpenDAL community vote thread:
>
> https://lists.apache.org/thread/2gqd6pm1k0cc1j0lq79d4ply721dmky2
>
> Vote result thread:
>
> https://lists.apache.org/thread/z8pv6c5rdv5ohn4fcgk4n40n9cfxtwdp
>
> The release candidate:
>
> https://dist.apache.org/repos/dist/dev/incubator/opendal/0.42.0-rc.3/
>
> This release has been signed with a PGP available here:
>
> https://downloads.apache.org/incubator/opendal/KEYS
>
> Git tag for the release:
>
> https://github.com/apache/incubator-opendal/releases/tag/v0.42.0-rc.3
>
> Maven staging repo:
>
> https://repository.apache.org/content/repositories/orgapacheopendal-1018/
>
> Please download, verify, and test.
>
> The VOTE will be open for at least 72 hours and until the necessary
> number of votes are reached.
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> To learn more about apache opendal, please see https://opendal.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
>
> More detailed checklist please refer to:
> https://github.com/apache/incubator-opendal/tree/main/scripts
>
> To compile from source, please refer to:
> https://github.com/apache/incubator-opendal/blob/main/CONTRIBUTING.md
>
> Here is python script in release to help you verify the release candidate:
>
> ./scripts/verify.py
>
> Thanks
>
> Sincerely,
> Mingzhuo Yin

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

Re: [VOTE] Accept Seata Into the ASF Incubator

[Willem Jiang]

+1 binding.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Sat, Oct 21, 2023 at 8:51 PM Sheng Wu  wrote:
>
> Hi Incubator
>
> Following the discussion from <[DISCUSS] Incubating Proposal of Seata>[1],
> I am starting this official vote for the Seata project.
>
> Here is their proposal,
> https://cwiki.apache.org/confluence/display/INCUBATOR/Seata+Proposal
>
> Please cast your vote:
>
> [ ] +1, bring into the Incubator
> [ ] +0, I don't care either way
> [ ] -1, do not bring Seata into the Incubator, because...
>
> The vote will open for one week from today, Oct. 21st, 2023
>
> [1] https://lists.apache.org/thread/jtg7tt725r9mf35gqxph65vz8gdbwq94
>
>
> Sheng Wu 吴晟
> Twitter, wusheng1108
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

Re: [VOTE] Release Apache Celeborn(Incubating) 0.3.1-incubating-rc3

[Willem Jiang]

+1 binding.

- incubating in the release kit name
- The checksums and signatures are validated.
- The LICENSE and NOTICE files look good to me.
- There is a DISCLAIMER in the release kits
- No binary files in the source release kits
- I can build the source with the command
./build/make-distribution.sh --release


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem



On Sat, Oct 7, 2023 at 1:29 PM Cheng Pan  wrote:
>
> Hi IPMC,
>
> This is a call for a vote to release Apache Celeborn (Incubating)
> 0.3.1-incubating-rc3
>
> The Apache Celeborn community has voted on and approved a proposal to
> release Apache Celeborn (Incubating) version 0.3.1-incubating-rc3.
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> dev@celeborn vote thread:
> https://lists.apache.org/thread/wt69x5h3jxrmozkjgh2v544sgpdqhnvq
>
> dev@celeborn vote result thread:
> https://lists.apache.org/thread/p6m2ko6lok8wkbbswt1n2qhwm0rh4xf4
>
> The git tag to be voted upon:
> https://github.com/apache/incubator-celeborn/releases/tag/v0.3.1-incubating-rc3
>
> The git commit hash:
> 861788810642ef19769b097b82bee70b92e0ace0
>
> The source and binary artifacts can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/celeborn/v0.3.1-incubating-rc3
>
> The staging repo:
> https://repository.apache.org/content/repositories/orgapacheceleborn-1040
>
> Fingerprint of the PGP key release artifacts are signed with:
> 8FC8075E1FDC303276C676EE8001952629BCC75D
>
> My public key to verify signatures can be found in:
> https://dist.apache.org/repos/dist/release/incubator/celeborn/KEYS
>
> The vote will be open for at least 72 hours or until the necessary
> number of votes are reached.
>
> Please vote accordingly:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and the reason)
>
> Checklist for release:
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
>
> Steps to validate the release:
> https://www.apache.org/info/verification.html
>
> Instructions for making binary artifacts from source:
> build/make-distribution.sh --release
>
> Thanks,
> Cheng Pan
>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

Re: [DISCUSS] Incubating Proposal of ResilientDB

[Willem Jiang]

Unlike the Linux kernel, we use the dev or main branch from the
official upstream repo to accept the PRs from the developer; we do the
release work on the other branch in the same repo.  We don't use
another forked repo to keep those changes first.  It will confuse the
contributor in finding the right developing branch on the project repo
to work on.

I barely find the repo's PR reviews and issue discussions[1].  Without
sharing these development contexts, it is hard for the new contributor
to know the story behind the code change.  We can improve the
situation during the incubation process. You can take the issue and
PRs of OpenDaL[2] as a polling example.

BTW, the license header on the source code[3] is not the ASL
request[4]. We can address this kind of problem during the code
transfer.

[1]https://github.com/resilientdb/resilientdb
[2]https://github.com/apache/incubator-opendal/
[3]https://github.com/resilientdb/resilientdb/blob/master/executor/common/transaction_manager.cpp#L1
[4]https://github.com/msadoghi/resilientdb/blob/hs/LICENSE#L189

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Tue, Oct 10, 2023 at 11:50 AM Mohammad Sadoghi
 wrote:
>
> Dear all,
>
> *Question on Initial Committers:*
> As was mentioned earlier. The criteria that I used was to credit anyone who
> has worked on the ResilientDB project since 2018, acknowledging their
> contributions. Below is the detailed breakdown of our contributors. So we
> can reduce the list as needed in accordance with ASF guidelines. As for the
> broader contributors, these are the folks who have supported ResilientDB,
> e.g., formalization of the research ideas, discussion of how to tackle a
> particular algorithm or its implementation, testing, and analysis. However,
> these broader members have not contributed to the codebase. So this is why
> they were tagged differently.*ResilientDB Core *[all have signed ICLA]
> Mohammad Sadoghi 
> Junchao Chen 
> Dakai Kang 
> Suyash Gupta  [Now at UC Berkeley]
> Sajjad Rahnama  [Now at Oracle]
> Wayne Wang  [Now at Hesai Technology]
> Julieta Duarte 
> Glenn Chen 
> *Tooling/SDK/Wallet/Applications *[all have signed ICLA]
> Thamir Qadah  [Umm Al-Qura University]
> Jinxiao Yu  [Now at Amazon AWS]
> Arindaam Roy  [Now at Square]
> Divjeet Singh Jas 
> Apratim Shukla 
> Priyal Soni  [Now at Amazon AWS]
> Rohan Sogani  [Now at Oracle]
> Kaustubh Shete 
> Gopal Nambiar 
> Saipranav Kotamreddy 
> Haskell Lark Macaraig 
>
> *Deprecated/Obsolete Features *[have been rewritten or removed]
> Jelle Hellings  [Now at McMaster University]
> Shesha Vishnu Prasad  [Now at Path]
> Dhruv Krishnan  [Now at Amazon AWS]
> Shubham Pandey  [Now at Cisco]
> Steve Chen 
> Priya Holani  [Now at Amazon AWS]
> Haojun (Howard) Zhu 
> Robert HE  [Now at Amazon AWS]
> Shreenath Iyer  [Now at Amazon AWS]
> Domenic Cianfichi  [Now at Amazon AWS]
> Erik Linsenmayer  [Now at General Atomics]
> Shreyan Mohanty  [Now at General Atomics]
> Xinyuan Sun  [Now at CertiK]
> Patrick Liao  [Now at Juniper Networks]
> Tim Huang 
> Jared Givens 
> Aditya Bej 
> Seongwoo Choi 
>
> *Question on Private Development:*
> As per request, we have transitioned away from local/private development.
> We have forked our public ResilientDB, and we began the process of moving
> all experimental features into this repo. All these ongoing features are
> available in this repo but are still under development and not yet ready to
> be released to the main repository.*Our New Development Repo: *
> https://github.com/msadoghi/resilientdb/*Notable Branches (Active Projects)*
> Speculative Consensus: https://github.com/msadoghi/resilientdb/tree/poe
> Rotating Leader (lightweight recovery):
> https://github.com/msadoghi/resilientdb/tree/hs
> Queue-Oriented Concurrency Control (concurrent execution):
> https://github.com/msadoghi/resilientdb/tree/QueccBranch
> Smart Contract Concurrency:
> https://github.com/msadoghi/resilientdb/tree/smartcontract_cc
>
> ---
> 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, Oct 9, 2023 at 6:18 PM Dave Fisher  wrote:
>
> >
> >
> > Sent from my iPhone
> >
> > > On Oct 9, 2023, at 7:51 PM, Suyash Gupta 
> > > 
> > wrote:
> > >
> > > Hello All
> > >
> > > Let me try to add to Mohammad's response. We defined an initial committer
> > > list of 40+ members as we wanted to give credit to everyone who has
> > > collaborated with us on projects/papers that were built arou

Re: [DISCUSS] Incubating Proposal of ResilientDB

[Willem Jiang]

I still have a question for the “Broader Contributing Members”: do we
treat them as initial committers?

It makes sense that we keep track of all the contributors on the
project website so that no one will be surprised by the long list of
initial committers.
An extensive initial committer list doesn't mean we have a healthy,
diverse community.  It is incredibly challenging to bring those
graduated students back to the project from my experience with IoTDB.
When we consider the community-building work during the polling
graduation evaluation, we just track the new committers we have during
the incubation process.


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Tue, Oct 10, 2023 at 7:43 PM 俊平堵  wrote:
>
> Agree with Roman and Dave that we can keep the original list.
> I think Willem is just curious on the mismatch between commits and
> committers, and the explanation here make sense to me.
>
> Thanks,
>
> JP
>
> Mohammad Sadoghi  于2023年10月10日周二 11:50写道：
>
> > Dear all,
> >
> > *Question on Initial Committers:*
> > As was mentioned earlier. The criteria that I used was to credit anyone who
> > has worked on the ResilientDB project since 2018, acknowledging their
> > contributions. Below is the detailed breakdown of our contributors. So we
> > can reduce the list as needed in accordance with ASF guidelines. As for the
> > broader contributors, these are the folks who have supported ResilientDB,
> > e.g., formalization of the research ideas, discussion of how to tackle a
> > particular algorithm or its implementation, testing, and analysis. However,
> > these broader members have not contributed to the codebase. So this is why
> > they were tagged differently.*ResilientDB Core *[all have signed ICLA]
> > Mohammad Sadoghi 
> > Junchao Chen 
> > Dakai Kang 
> > Suyash Gupta  [Now at UC Berkeley]
> > Sajjad Rahnama  [Now at Oracle]
> > Wayne Wang  [Now at Hesai Technology]
> > Julieta Duarte 
> > Glenn Chen 
> > *Tooling/SDK/Wallet/Applications *[all have signed ICLA]
> > Thamir Qadah  [Umm Al-Qura University]
> > Jinxiao Yu  [Now at Amazon AWS]
> > Arindaam Roy  [Now at Square]
> > Divjeet Singh Jas 
> > Apratim Shukla 
> > Priyal Soni  [Now at Amazon AWS]
> > Rohan Sogani  [Now at Oracle]
> > Kaustubh Shete 
> > Gopal Nambiar 
> > Saipranav Kotamreddy 
> > Haskell Lark Macaraig 
> >
> > *Deprecated/Obsolete Features *[have been rewritten or removed]
> > Jelle Hellings  [Now at McMaster University]
> > Shesha Vishnu Prasad  [Now at Path]
> > Dhruv Krishnan  [Now at Amazon AWS]
> > Shubham Pandey  [Now at Cisco]
> > Steve Chen 
> > Priya Holani  [Now at Amazon AWS]
> > Haojun (Howard) Zhu 
> > Robert HE  [Now at Amazon AWS]
> > Shreenath Iyer  [Now at Amazon AWS]
> > Domenic Cianfichi  [Now at Amazon AWS]
> > Erik Linsenmayer  [Now at General
> > Atomics]
> > Shreyan Mohanty  [Now at General Atomics]
> > Xinyuan Sun  [Now at CertiK]
> > Patrick Liao  [Now at Juniper Networks]
> > Tim Huang 
> > Jared Givens 
> > Aditya Bej 
> > Seongwoo Choi 
> >
> > *Question on Private Development:*
> > As per request, we have transitioned away from local/private development.
> > We have forked our public ResilientDB, and we began the process of moving
> > all experimental features into this repo. All these ongoing features are
> > available in this repo but are still under development and not yet ready to
> > be released to the main repository.*Our New Development Repo: *
> > https://github.com/msadoghi/resilientdb/*Notable Branches (Active
> > Projects)*
> > Speculative Consensus: https://github.com/msadoghi/resilientdb/tree/poe
> > Rotating Leader (lightweight recovery):
> > https://github.com/msadoghi/resilientdb/tree/hs
> > Queue-Oriented Concurrency Control (concurrent execution):
> > https://github.com/msadoghi/resilientdb/tree/QueccBranch
> > Smart Contract Concurrency:
> > https://github.com/msadoghi/resilientdb/tree/smartcontract_cc
> >
> > ---
> > 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, Oct 9, 2023 at 6:18 PM Dave Fisher  wrote:
> >
> > >
> > >
> > > Sent from my iPhone
> > >
> > > > On Oct 9, 2023, at 7:51 PM, Suyash Gupta  > .invalid>
> > > wrote:
> &g

[RESULT][VOTE]Accept Answer into the Apache Incubator

[Willem Jiang]

Hi all,

Thanks to everyone who participated in the vote[1]. The voting is now
closed, and it has passed with 18 binding +1, 4 non-binding +1, and no 0
or -1 votes.

Binding votes: Sheng Wu，Ted Liu，Uma Maheswara Rao G，Christofer Dutz，
Christian Grobmeier， tison，Calvin Kirs， Furkan KAMACI， Kevin
Ratnasekera， Ayush Saxena， Craig Russell， Felix Cheung， Jean-Baptiste
Onofre， Gang Li， Eason Chen,  Xin Wang,  Duo Zhang,  Willem Jiang.

Non-binding votes: Dominik Riemer，KimmKing, Sargent, Anne Zhu

[1]https://lists.apache.org/thread/295qzlzm9oy3qjpntp6cq97v69kvnmkr

Thanks,

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

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

Re: [DISCUSS] Incubating Proposal of ResilientDB

[Willem Jiang]

I just checked the GitHub issue and PRs of ResilientDB. There is
little discussion on the GitHub issue and review comments on GitHub
PRs.
Please keep Open Communications[1] in mind. We value transparency in
the ASF way. Internal development could block the contributions
outside of the organization and cause us some trouble in building the
community.

Once the development switches to the public repo, the project could be
ready to enter the incubation process.

[1]https://www.apache.org/theapacheway/#what-makes-the-apache-way-so-hard-to-define


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Sun, Oct 8, 2023 at 3:33 PM Mohammad Sadoghi  wrote:
>
> Thank you for your question.
>
> With regards to the initial committers, over the years we had much larger
> set of contributors who worked on the private repo of ResilientDB which
> derives the research. Only when features are stable and well tested over
> time, they have been advanced and promoted to our public repo. Our private
> repo has many more experimental features that as part of our roadmap will
> be released once they reach the same level of maturity.
>
> Best Regards,
> Mohammad Sadoghi, PhD
> Associate Professor
> Exploratory Systems Lab (ExpoLab)
> Department of Computer Science
> University of California, Davis
>
>
> On Sun, Oct 8, 2023 at 12:23 AM Willem Jiang  wrote:
>
> > Hi,
> >
> > I have a quick question about the initial committers.
> > There are about 40+ initial committers, but I can only find about 20
> > contributors in the GitHub group[1] contributor list.
> > Could you explain the initial committer criteria?
> > There is a section of "Broader Contributing Members" in the
> > proposal[2] after the initial committer, if we treat them as initial
> > committers, why do we need to separate them with the initial
> > committer?
> >
> > Thanks,
> >
> > [1]https://github.com/resilientdb
> > [2]
> > https://cwiki.apache.org/confluence/display/INCUBATOR/ResilientDBProposal
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Sun, Oct 8, 2023 at 1:38 PM 俊平堵  wrote:
> > >
> > > +1.
> > > btw, I assume we will have an official vote thread (start with [VOTE])
> > > later?
> > >
> > > Thanks,
> > >
> > > JP
> > >
> > > Atri Sharma  于2023年10月3日周二 19:24写道：
> > >
> > > > We want to propose ResilientDB as a new Apache Incubator project.
> > > >
> > > > ResilientDB[1] is a distributed blockchain framework that is written
> > > > in C++ and integrates with Byzantine Fault-Tolerant (BFT) and Crash
> > > > Fault-Tolerant (CFT) consensus protocols. Code is present at [2].
> > > >
> > > > Key features:
> > > >
> > > > Provides a scalable client-server architecture. Each developer can use
> > > > the ResilientDB framework to deploy a replicated service acting as a
> > > > service. The developer can choose the desired number of replicas and
> > > > the number of clients its system should tolerate.
> > > >
> > > > Provides native integration with PBFT consensus protocol – arguably
> > > > the most popular BFT consensus protocol. PBFT helps replicas reach an
> > > > agreement for ordering the client's requests.
> > > >
> > > > Provides a mechanism to simulate the failure of different replicas
> > > > (including the leader).
> > > >
> > > > Provides a correct implementation of the view-change protocol that
> > > > replaces a faulty (or malicious) leader and moves all replicas to the
> > > > new view.
> > > >
> > > > Provides checkpoint and recovery protocols to facilitate garbage
> > > > collection, recovery of failed replicas, and durably logging of the
> > > > blockchain state.
> > > >
> > > > Eases development and testing of newer and optimized BFT and CFT
> > > > consensus protocols.
> > > > Provides clients with support for three different application
> > interfaces:
> > > >
> > > > Key-Value Stores - where client transactions include key-value pairs.
> > > >
> > > > Smart Contracts - where clients issue smart contracts in Solidity for
> > > > processing.
> > > >
> > > > UTXO - where clients issue unspent transactions similar to ones in
> > Bitcoin.
> > > >
> > > > Facilitates benchmarking system/protocol performance with the help of
>

Re: [DISCUSS] Incubating Proposal of ResilientDB

[Willem Jiang]

Hi,

I have a quick question about the initial committers.
There are about 40+ initial committers, but I can only find about 20
contributors in the GitHub group[1] contributor list.
Could you explain the initial committer criteria?
There is a section of "Broader Contributing Members" in the
proposal[2] after the initial committer, if we treat them as initial
committers, why do we need to separate them with the initial
committer?

Thanks,

[1]https://github.com/resilientdb
[2]https://cwiki.apache.org/confluence/display/INCUBATOR/ResilientDBProposal

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Sun, Oct 8, 2023 at 1:38 PM 俊平堵  wrote:
>
> +1.
> btw, I assume we will have an official vote thread (start with [VOTE])
> later?
>
> Thanks,
>
> JP
>
> Atri Sharma  于2023年10月3日周二 19:24写道：
>
> > We want to propose ResilientDB as a new Apache Incubator project.
> >
> > ResilientDB[1] is a distributed blockchain framework that is written
> > in C++ and integrates with Byzantine Fault-Tolerant (BFT) and Crash
> > Fault-Tolerant (CFT) consensus protocols. Code is present at [2].
> >
> > Key features:
> >
> > Provides a scalable client-server architecture. Each developer can use
> > the ResilientDB framework to deploy a replicated service acting as a
> > service. The developer can choose the desired number of replicas and
> > the number of clients its system should tolerate.
> >
> > Provides native integration with PBFT consensus protocol – arguably
> > the most popular BFT consensus protocol. PBFT helps replicas reach an
> > agreement for ordering the client's requests.
> >
> > Provides a mechanism to simulate the failure of different replicas
> > (including the leader).
> >
> > Provides a correct implementation of the view-change protocol that
> > replaces a faulty (or malicious) leader and moves all replicas to the
> > new view.
> >
> > Provides checkpoint and recovery protocols to facilitate garbage
> > collection, recovery of failed replicas, and durably logging of the
> > blockchain state.
> >
> > Eases development and testing of newer and optimized BFT and CFT
> > consensus protocols.
> > Provides clients with support for three different application interfaces:
> >
> > Key-Value Stores - where client transactions include key-value pairs.
> >
> > Smart Contracts - where clients issue smart contracts in Solidity for
> > processing.
> >
> > UTXO - where clients issue unspent transactions similar to ones in Bitcoin.
> >
> > Facilitates benchmarking system/protocol performance with the help of
> > existing benchmarks, such as YCSB [SoCC’10] and Diablo [EuroSys’23].
> >
> > Stores non-volatile ledger (blockchain) in memory and for further
> > durability, provides APIs to store both client data and blockchain in
> > LevelDB and RocksDB.
> >
> >
> > The serving mentors would be:
> >
> > Junping Du 
> >
> > Calvin Kirs 
> >
> > Kevin Ratnasekera 
> >
> > Roman Shaposhnik 
> >
> > Christian Grobmeier 
> >
> > and I shall be serving as the Champion.
> >
> > We have not done a trademark check yet for the name but that can be
> > pursued independently.
> >
> > [1]
> > https://cwiki.apache.org/confluence/display/INCUBATOR/ResilientDBProposal
> > [2] https://github.com/resilientdb/resilientdb
> >
> > Atri
> >
> > -
> > 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: Re:[VOTE] Accept Answer into the Apache Incubator

[Willem Jiang]

Hi KimmKing,

We had the project name discussion in the discussion thread[1].
Currently the project doesn't have plans to rename the project name.[2]

[1]https://lists.apache.org/thread/42tvz3rqfy4w5poqgslh71sm1o1td7zn
[2]https://lists.apache.org/thread/68n5kz5c3bm3fm5nckj1zwl3xf2vwcvh

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Thu, Oct 5, 2023 at 2:59 PM KimmKing  wrote:
>
> There will be some preferred names for discussion or not? My Suggestion is 
> OpenAnswer/Openswer.
>
>
>
>
> --
>
> Kimm King(kimmk...@apache.org/kimmk...@163.com)
> Apache Dubbo PMC Member
> github: kimmking
>
>
>
>
>
> At 2023-10-05 14:55:27, "KimmKing"  wrote:
> >+1， nobinding
> >
> >
> >
> >
> >--
> >
> >Kimm King(kimmk...@apache.org/kimmk...@163.com)
> >Apache Dubbo PMC Member
> >github: kimmking
> >
> >
> >
> >
> >
> >At 2023-10-03 08:17:16, "Willem Jiang"  wrote:
> >>Following up the [DISCUSS] thread on Answer [1] I would like to call a
> >>VOTE to accept into the Apache Incubator.
> >>
> >>Answer is a question-and-answer (Q) platform software for teams at
> >>any scale to build a help center, knowledge base, community forum,
> >>etc.
> >>
> >>Please cast your vote:
> >>
> >>  [ ] +1, bring into the Incubator
> >>  [ ] +0, I don't care either way
> >>  [ ] -1, do not bring Answer into the Incubator, because...
> >>
> >>The vote will open at least for 72 hours and only votes from the
> >>Incubator PMC are binding, but votes from everyone are welcome.
> >>
> >>Please check out the Answer Proposal from the incubator wiki[2].
> >>
> >>[1]https://lists.apache.org/thread/42tvz3rqfy4w5poqgslh71sm1o1td7zn
> >>[2]https://cwiki.apache.org/confluence/display/INCUBATOR/Answer+Proposal
> >>
> >>Best Regards,
> >>
> >>Willem Jiang
> >>
> >>Twitter: willemjiang
> >>Weibo: 姜宁willem
> >>
> >>-
> >>To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >>For additional commands, e-mail: general-h...@incubator.apache.org

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

Re: [VOTE] Accept Answer into the Apache Incubator

[Willem Jiang]

+1 （binding）

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Tue, Oct 3, 2023 at 8:17 AM Willem Jiang  wrote:
>
> Following up the [DISCUSS] thread on Answer [1] I would like to call a
> VOTE to accept into the Apache Incubator.
>
> Answer is a question-and-answer (Q) platform software for teams at
> any scale to build a help center, knowledge base, community forum,
> etc.
>
> Please cast your vote:
>
>   [ ] +1, bring into the Incubator
>   [ ] +0, I don't care either way
>   [ ] -1, do not bring Answer into the Incubator, because...
>
> The vote will open at least for 72 hours and only votes from the
> Incubator PMC are binding, but votes from everyone are welcome.
>
> Please check out the Answer Proposal from the incubator wiki[2].
>
> [1]https://lists.apache.org/thread/42tvz3rqfy4w5poqgslh71sm1o1td7zn
> [2]https://cwiki.apache.org/confluence/display/INCUBATOR/Answer+Proposal
>
> Best Regards,
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem

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

[VOTE] Accept Answer into the Apache Incubator

[Willem Jiang]

Following up the [DISCUSS] thread on Answer [1] I would like to call a
VOTE to accept into the Apache Incubator.

Answer is a question-and-answer (Q) platform software for teams at
any scale to build a help center, knowledge base, community forum,
etc.

Please cast your vote:

  [ ] +1, bring into the Incubator
  [ ] +0, I don't care either way
  [ ] -1, do not bring Answer into the Incubator, because...

The vote will open at least for 72 hours and only votes from the
Incubator PMC are binding, but votes from everyone are welcome.

Please check out the Answer Proposal from the incubator wiki[2].

[1]https://lists.apache.org/thread/42tvz3rqfy4w5poqgslh71sm1o1td7zn
[2]https://cwiki.apache.org/confluence/display/INCUBATOR/Answer+Proposal

Best Regards,

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

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

Re: [DISCUSS] Incubating Proposal of Answer

[Willem Jiang]

Hi,

After talking with the Answer development team about the brand name
issue, there is some feedback from the team.
They still want to use the answer as the project name, and they don't
plan to provide commercial products or online services based on this
project so far.

Please let me know if there are any other concerns about this project.
I will start a vote next week if there are no other objections.

Best regards,

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Thu, Sep 21, 2023 at 11:14 PM tison  wrote:
>
> Hi,
>
> About the project name and trademark, according to the trademarks@ reply,
>
> > It is possible to use such a name on the understanding that obtaining a
> > trademark for it is likely to be a more difficult (and longer) process.
>
> So it's viable and I also inform the initial committers to think of the
> pros and cons.
>
> Let's say we don't have a blocker here but potential trade-offs. Apache
> Arrow can be
> a compare whose name is also a common word, and the community built up the
> brand recognition so the name is associated with the project.
>
> Best,
> tison.
>
>
> Willem Jiang  于2023年9月21日周四 23:00写道：
>
> > Hi PJ,
> >
> > Thanks for the reply,  I will talk to the team and find out if we can
> > figure out a better name for it.
> > I raised the same question when I first heard about the name, but it's
> > hard for the team to give up the product word they already have
> > without a solid objection.
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> > On Thu, Sep 21, 2023 at 9:36 PM PJ Fanning  wrote:
> > >
> > > For me, Answer is a problematic name. We're trying to move away from
> > > relying on the Apache brand name so project names ideally should work
> > > with or without the Apache name. Answer does not work as a brand on
> > > its own, it depends on being Apache Answer to make it seem like a
> > > brand. I'm not saying that we should stop calling our projects Apache
> > > XYZ yet but I just think the XYZ needs to work as a standalone project
> > > name too. Even something like 'Answer Platform' and 'Apache Answer
> > > Platform' might make the name more specific. Imagine trying to search
> > > online for 'Answer'. There are more than 14 billion matches on Google.
> > >
> > > On Thu, 21 Sept 2023 at 13:51, Sheng Wu 
> > wrote:
> > > >
> > > > Hi
> > > >
> > > > I have a question for the mentors, do you check whether this general
> > > > word, `Answer` is an acceptable project name for the foundation?
> > > >
> > > > Sheng Wu 吴晟
> > > > Twitter, wusheng1108
> > > >
> > > > Jean-Baptiste Onofré  于2023年9月21日周四 20:39写道：
> > > > >
> > > > > Hi,
> > > > >
> > > > > It looks interesting at first glance. I will do a new pass on the
> > > > > proposal (in more details).
> > > > >
> > > > > Regards
> > > > > JB
> > > > >
> > > > > On Thu, Sep 21, 2023 at 2:00 PM Willem Jiang 
> > wrote:
> > > > > >
> > > > > > We want to propose  Answer as a new Apache Incubator project.
> > > > > >
> > > > > > Answer[1] is a question-and-answer (Q) platform software for
> > teams
> > > > > > at any scale to build a help center, knowledge base, community
> > forum,
> > > > > > etc.
> > > > > > The key features of Answer:
> > > > > > 1. Questions and Answers - Ask questions and get answers from your
> > > > > > users and team.
> > > > > > 2. Content Organization and Management - Organize your content with
> > > > > > flag, moderation, and permission.
> > > > > > 3. Content Management - Manage topics and discussions in the
> > community
> > > > > > with tags.
> > > > > > 4. Reputation - Reward users for their contribution: answer,
> > verify,
> > > > > > and upvote correct info. Always keep the information up-to-date.
> > > > > >
> > > > > > I'd be happy to be the Champion of this project, and may Thanks to
> > > > > > Zili Chen ， Justin Mclean  > > > > > apache.org>, and Christofer Dutz   for
> > mentoring
> > > > > > the answer project and helping us polish the incubating
> > proposal[2].
> > > > > >
> > > &

Re: [DISCUSS] Incubating Proposal of Answer

[Willem Jiang]

Hi PJ,

Thanks for the reply,  I will talk to the team and find out if we can
figure out a better name for it.
I raised the same question when I first heard about the name, but it's
hard for the team to give up the product word they already have
without a solid objection.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem
On Thu, Sep 21, 2023 at 9:36 PM PJ Fanning  wrote:
>
> For me, Answer is a problematic name. We're trying to move away from
> relying on the Apache brand name so project names ideally should work
> with or without the Apache name. Answer does not work as a brand on
> its own, it depends on being Apache Answer to make it seem like a
> brand. I'm not saying that we should stop calling our projects Apache
> XYZ yet but I just think the XYZ needs to work as a standalone project
> name too. Even something like 'Answer Platform' and 'Apache Answer
> Platform' might make the name more specific. Imagine trying to search
> online for 'Answer'. There are more than 14 billion matches on Google.
>
> On Thu, 21 Sept 2023 at 13:51, Sheng Wu  wrote:
> >
> > Hi
> >
> > I have a question for the mentors, do you check whether this general
> > word, `Answer` is an acceptable project name for the foundation?
> >
> > Sheng Wu 吴晟
> > Twitter, wusheng1108
> >
> > Jean-Baptiste Onofré  于2023年9月21日周四 20:39写道：
> > >
> > > Hi,
> > >
> > > It looks interesting at first glance. I will do a new pass on the
> > > proposal (in more details).
> > >
> > > Regards
> > > JB
> > >
> > > On Thu, Sep 21, 2023 at 2:00 PM Willem Jiang  
> > > wrote:
> > > >
> > > > We want to propose  Answer as a new Apache Incubator project.
> > > >
> > > > Answer[1] is a question-and-answer (Q) platform software for teams
> > > > at any scale to build a help center, knowledge base, community forum,
> > > > etc.
> > > > The key features of Answer:
> > > > 1. Questions and Answers - Ask questions and get answers from your
> > > > users and team.
> > > > 2. Content Organization and Management - Organize your content with
> > > > flag, moderation, and permission.
> > > > 3. Content Management - Manage topics and discussions in the community
> > > > with tags.
> > > > 4. Reputation - Reward users for their contribution: answer, verify,
> > > > and upvote correct info. Always keep the information up-to-date.
> > > >
> > > > I'd be happy to be the Champion of this project, and may Thanks to
> > > > Zili Chen ， Justin Mclean  > > > apache.org>, and Christofer Dutz   for mentoring
> > > > the answer project and helping us polish the incubating proposal[2].
> > > >
> > > > The word answer is a generic name, and trademarking it is impossible.
> > > > But if we add the prefix of Apache, it could be more reasonable to
> > > > use.  I look forward to your feedback and thank you for your help.
> > > >
> > > > [1]https://github.com/answer.dev/
> > > > [2]https://cwiki.apache.org/confluence/display/INCUBATOR/Answer+Proposal
> > > >
> > > > Best regards,
> > > >
> > > > Willem Jiang
> > > >
> > > > Twitter: willemjiang
> > > > Weibo: 姜宁willem
> > > >
> > > > -
> > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > For additional commands, e-mail: general-h...@incubator.apache.org
> > > >
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> >
> > -
> > 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] Incubating Proposal of Answer

[Willem Jiang]

I sent an email query for feedback on the trademark when sending this proposal.
Let's see the feedback from the trademark VP.
By the way, The Apache Arrow project[1] may hit the same situation as
a common word.


[1]https://arrow.apache.org/


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Thu, Sep 21, 2023 at 8:51 PM Sheng Wu  wrote:
>
> Hi
>
> I have a question for the mentors, do you check whether this general
> word, `Answer` is an acceptable project name for the foundation?
>
> Sheng Wu 吴晟
> Twitter, wusheng1108
>
> Jean-Baptiste Onofré  于2023年9月21日周四 20:39写道：
> >
> > Hi,
> >
> > It looks interesting at first glance. I will do a new pass on the
> > proposal (in more details).
> >
> > Regards
> > JB
> >
> > On Thu, Sep 21, 2023 at 2:00 PM Willem Jiang  wrote:
> > >
> > > We want to propose  Answer as a new Apache Incubator project.
> > >
> > > Answer[1] is a question-and-answer (Q) platform software for teams
> > > at any scale to build a help center, knowledge base, community forum,
> > > etc.
> > > The key features of Answer:
> > > 1. Questions and Answers - Ask questions and get answers from your
> > > users and team.
> > > 2. Content Organization and Management - Organize your content with
> > > flag, moderation, and permission.
> > > 3. Content Management - Manage topics and discussions in the community
> > > with tags.
> > > 4. Reputation - Reward users for their contribution: answer, verify,
> > > and upvote correct info. Always keep the information up-to-date.
> > >
> > > I'd be happy to be the Champion of this project, and may Thanks to
> > > Zili Chen ， Justin Mclean  > > apache.org>, and Christofer Dutz   for mentoring
> > > the answer project and helping us polish the incubating proposal[2].
> > >
> > > The word answer is a generic name, and trademarking it is impossible.
> > > But if we add the prefix of Apache, it could be more reasonable to
> > > use.  I look forward to your feedback and thank you for your help.
> > >
> > > [1]https://github.com/answer.dev/
> > > [2]https://cwiki.apache.org/confluence/display/INCUBATOR/Answer+Proposal
> > >
> > > Best regards,
> > >
> > > Willem Jiang
> > >
> > > Twitter: willemjiang
> > > Weibo: 姜宁willem
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

Re: [DISCUSS] Incubating Proposal of Answer

[Willem Jiang]

Thanks for pointing that out.
The right URL of the GitHub group is https://github.com/answerdev/

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Thu, Sep 21, 2023 at 8:39 PM Xuanwo  wrote:
>
> Hi, there a small typo:
>
> https://github.com/answer.dev/ always returns HTTP 406 error code.
>
> I believe it should be https://github.com/answerdev/
>
> On Thu, Sep 21, 2023, at 20:00, Willem Jiang wrote:
> > We want to propose  Answer as a new Apache Incubator project.
> >
> > Answer[1] is a question-and-answer (Q) platform software for teams
> > at any scale to build a help center, knowledge base, community forum,
> > etc.
> > The key features of Answer:
> > 1. Questions and Answers - Ask questions and get answers from your
> > users and team.
> > 2. Content Organization and Management - Organize your content with
> > flag, moderation, and permission.
> > 3. Content Management - Manage topics and discussions in the community
> > with tags.
> > 4. Reputation - Reward users for their contribution: answer, verify,
> > and upvote correct info. Always keep the information up-to-date.
> >
> > I'd be happy to be the Champion of this project, and may Thanks to
> > Zili Chen ， Justin Mclean  > apache.org>, and Christofer Dutz   for mentoring
> > the answer project and helping us polish the incubating proposal[2].
> >
> > The word answer is a generic name, and trademarking it is impossible.
> > But if we add the prefix of Apache, it could be more reasonable to
> > use.  I look forward to your feedback and thank you for your help.
> >
> > [1]https://github.com/answer.dev/
> > [2]https://cwiki.apache.org/confluence/display/INCUBATOR/Answer+Proposal
> >
> > Best regards,
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
>
> --
> 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

[DISCUSS] Incubating Proposal of Answer

[Willem Jiang]

We want to propose  Answer as a new Apache Incubator project.

Answer[1] is a question-and-answer (Q) platform software for teams
at any scale to build a help center, knowledge base, community forum,
etc.
The key features of Answer:
1. Questions and Answers - Ask questions and get answers from your
users and team.
2. Content Organization and Management - Organize your content with
flag, moderation, and permission.
3. Content Management - Manage topics and discussions in the community
with tags.
4. Reputation - Reward users for their contribution: answer, verify,
and upvote correct info. Always keep the information up-to-date.

I'd be happy to be the Champion of this project, and may Thanks to
Zili Chen ， Justin Mclean , and Christofer Dutz   for mentoring
the answer project and helping us polish the incubating proposal[2].

The word answer is a generic name, and trademarking it is impossible.
But if we add the prefix of Apache, it could be more reasonable to
use.  I look forward to your feedback and thank you for your help.

[1]https://github.com/answer.dev/
[2]https://cwiki.apache.org/confluence/display/INCUBATOR/Answer+Proposal

Best regards,

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

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

Re: [VOTE] Release Apache OpenDAL(incubating) v0.40.0-rc.2 - Incubator Vote Round 1

[Willem Jiang]

Hi

+1(binding)
 Here is what I checked:
- The checksums and signatures are validated.
- The LICENSE and NOTICE files look good to me.
- There is a DISCLAIMER file about incubating.
- No binary files in the source release.

@Xuanwo
I just found out the PPMC vote started yesterday. We must wait 72
hours even if we have more than 3 +1.
If you want to speed up the voting process, you can invite the mentors
to join the PPMC vote.


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem


On Tue, Sep 19, 2023 at 12:10 PM Xuanwo  wrote:
>
> Hello Incubator PMC,
>
> The Apache OpenDAL community has voted and approved the release of Apache
> OpenDAL(incubating) v0.40.0-rc.2. We now kindly request the IPMC members
> review and vote for this release.
>
> OpenDAL is a data access layer that allows users to easily and efficiently
> retrieve data from various storage services in a unified way.
>
> OpenDAL community vote thread:
>
> https://lists.apache.org/thread/x7gns8r31pk785f7ocblj16s7n8hxoy6
>
> Vote result thread:
>
> https://lists.apache.org/thread/x3gfxx6hj48lcjdcl1jtv4o34mhmxjwj
>
> The release candidate:
>
> https://dist.apache.org/repos/dist/dev/incubator/opendal/v0.40.0-rc2/
>
> This release has been signed with a PGP available here:
>
> https://downloads.apache.org/incubator/opendal/KEYS
>
> Git tag for the release:
>
> https://github.com/apache/incubator-opendal/releases/tag/v0.40.0-rc.2
>
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapacheopendal-1014/
>
> Please download, verify, and test.
>
> The VOTE will pass after got 3 binding approve.
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> To learn more about apache opendal, please see https://opendal.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
>
> More detailed checklist please refer to:
> https://github.com/apache/incubator-opendal/tree/main/scripts
>
> To compile from source, please refer to:
> https://github.com/apache/incubator-opendal/blob/main/CONTRIBUTING.md
>
> Thanks
>
> Xuanwo
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

Re: [VOTE] Release Apache DevLake (Incubating) v0.18.0-rc1

[Willem Jiang]

+1(binding).
Here is what I checked:
- The checksums and signatures are validated.
- The LICENSE and NOTICE files look good to me.
- There is a DISCLAIMER file about incubating.
- No binary files in the source release.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Wed, Sep 6, 2023 at 12:17 PM Junren Yu  wrote:
>
> Hello everyone,
>
> This is a call for a vote to release Apache DevLake (Incubating)
> v0.18.0-rc1.
> The Apache DevLake community has voted on and approved a proposal to
> release Apache DevLake (Incubating) version v0.18.0-rc1.
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Community vote thread:
>
> https://lists.apache.org/thread/p187lnld8qr5gn7z21kv1fsb0m420of9
>
> Community vote result thread:
>
> https://lists.apache.org/thread/6g79vnn3c15lz8z0x82p48zr0p8xyj5s
>
> The release candidates:
>
> https://dist.apache.org/repos/dist/dev/incubator/devlake/0.18.0-incubating-rc1
>
> Git tag for the release:
>
> https://github.com/apache/incubator-devlake/releases/tag/v0.18.0-rc1
>
> Keys to verify the Release Candidate:
>
> https://downloads.apache.org/incubator/devlake/KEYS
>
> How to build:
>
> https://devlake.apache.org/docs/DeveloperManuals/DeveloperSetup
>
> 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
>
>
> Regards,
> Junren Yu

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

Re: [VOTE] Release Apache Paimon(incubating) 0.5.0-incubating rc1

[Willem Jiang]

+1 （binding）
I did these checks
- The checksums and signatures are validated.
- The LICENSE and NOTICE files look good to me.
- There is a DISCLAIMER file about incubating.
- No binary files in the source release.
- Can Compile from the source.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem


On Tue, Aug 29, 2023 at 7:30 PM Jingsong Li  wrote:
>
> Hello Incubator PMC,
>
> The Apache Paimon community has voted and approved the release of
> Apache Paimon(incubating) 0.5.0-incubating rc1. We now kindly request
> the IPMC members review and vote for this release.
>
> Apache Paimon(incubating) is a streaming data lake platform that
> supports high-speed data ingestion, change data tracking and efficient
> real-time analytics.
>
> Paimon community vote thread:
>
> https://lists.apache.org/thread/5ftgl4dkjwlyrlc0hkcbzz3c4m6rss62
>
> Vote result thread:
>
> https://lists.apache.org/thread/x5tnf1359jprlr61pc67s0crs7xg7po5
>
> The official Apache source release to be deployed to dist.apache.org:
>
> https://dist.apache.org/repos/dist/dev/incubator/paimon/paimon-0.5.0-incubating-rc1/
>
> This source release has been signed with a PGP available here (Apache
> ID: lzljs3620320):
>
> https://downloads.apache.org/incubator/paimon/KEYS
>
> All artifacts to be deployed to the Maven Central Repository:
>
> https://repository.apache.org/content/repositories/orgapachepaimon-1028/
>
> Git branch for the release:
>
> https://github.com/apache/incubator-paimon/tree/release-0.5.0-incubating-rc1
>
> Please download, verify, and test.
>
> The VOTE will pass after 3 binding approve.
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> To learn more about apache paimon, please see https://paimon.apache.org/
>
> Checklist for reference:
>
> [ ] Download links are valid.
> [ ] Checksums and signatures.
> [ ] LICENSE/NOTICE files exist
> [ ] No unexpected binary files
> [ ] All source files have ASF headers
> [ ] Can compile from source
>
> Best,
> Jingsong
>
> -
> 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: [IP CLEARANCE] pulsar-admin-go

[Willem Jiang]

Hi tison,

You are in the Incubator PMC group. The svn right should be fine for
you. You need to use your Apache ID and password to log in.
I just helped you commit the file of pulsar-admin-go after doing some
tests on my side.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Sat, Aug 12, 2023 at 1:19 AM tison  wrote:
>
> Hi IPMC,
>
> Here is a IP CLEARANCE proposal for accepting pulsar-admin-go into the Apache 
> Pulsar PMC by merging into apache/pulsar-client-go.
>
> The vote thread within Pulsar PMC can be found at [1].
>
> I wrote a IP CLEARANCE record (attached) but I cannot commit it to SVN with 
> `svn ci`. I don't know whether I don't have the permission or I don't "log 
> in" properly. I'll appreciate it if you can guide me the next steps.
>
> $ svn co 
> http://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance
> $ svn add pulsar-admin-go.xml
> A pulsar-admin-go.xml
> $ svn ci -m "document IP clearance entry for pulsar-admin-go"
> svn: E175013: Commit failed (details follow):
> svn: E175013: Access to '/repos/asf/!svn/me' forbidden
>
> Best,
> tison.
>
> [1] https://lists.apache.org/thread/txpxdkzf4n5dd6bm0goqxfycr69g9gc4
>
> -
> 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 DevLake (Incubating) v0.17.0-rc2

[Willem Jiang]

+1(binding). Here is what I checked:
- The checksums and signatures are validated.
- The LICENSE and NOTICE files look good to me.
- There is a DISCLAIMER file about incubating.
- No binary files in the source release.


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Tue, Jul 18, 2023 at 8:49 PM Zikuan An  wrote:
>
> Hello everyone,
>
> This is a call for vote to release Apache DevLake (Incubating) v0.17.0-rc2.
> The Apache DevLake community has voted on and approved a proposal to
> release Apache DevLake (Incubating) version v0.17.0-rc2.
>
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Community vote thread:
>
> https://lists.apache.org/thread/s8dxqob0kcr94klxhd3dlyd3rfy1tsvx
>
>
> Community vote result thread:
>
> https://lists.apache.org/thread/11snoww7k35mlof72870mj56fl5hhrcs
>
>
> The release candidates:
>
> https://dist.apache.org/repos/dist/dev/incubator/devlake/0.17.0-incubating-rc2
>
>
> Git tag for the release:
>
> https://github.com/apache/incubator-devlake/releases/tag/v0.17.0-rc2
>
>
> Keys to verify the Release Candidate:
>
> https://downloads.apache.org/incubator/devlake/KEYS
>
>
> How to build:
>
> https://devlake.apache.org/docs/DeveloperManuals/DeveloperSetup
>
>
> 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
>
>
> Thanks
>
> Zikuan An

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

Re: [VOTE] Release Apache OpenDAL(incubating) 0.38.0-rc1 - Incubator Vote Round 1

[Willem Jiang]

+1. Here is what I checked:
- The checksums and signatures are validated.
- The LICENSE and NOTICE files look good to me.
- There is a DISCLAIMER file about incubating.
- No binary files in the source release.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem


On Wed, Jun 28, 2023 at 10:31 PM Chojan Shang  wrote:
>
> Hello Incubator PMC,
>
> The Apache OpenDAL community has voted and approved the release of Apache
> OpenDAL(incubating) 0.38.0-rc1. We now kindly request the IPMC members
> review and vote for this release.
>
> OpenDAL is a data access layer that allows users to easily and efficiently
> retrieve data from various storage services in a unified way.
>
> OpenDAL community vote thread:
>
> https://lists.apache.org/thread/ny0t1szlkrb8060j0w9gnj45oov18snm
>
> Vote result thread:
>
> https://lists.apache.org/thread/0l64s4w4yh19nzgfhg3cslm7cq10k7yd
>
> The release candidate:
>
> https://dist.apache.org/repos/dist/dev/incubator/opendal/0.38.0-rc1/
>
> This release has been signed with a PGP available here:
>
> https://downloads.apache.org/incubator/opendal/KEYS
>
> Git branch for the release:
>
> https://github.com/apache/incubator-opendal/tree/release-0.38.0-rc1
>
> Please download, verify, and test.
>
> The VOTE will pass after got 3 binding approve.
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> To learn more about apache opendal, please see https://opendal.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
>
> More detailed checklist please refer to:
> https://github.com/apache/incubator-opendal/tree/main/scripts
>
> To compile from source, please refer to:
> https://github.com/apache/incubator-opendal/blob/main/CONTRIBUTING.md
>
>
> Thanks.
>
> Sincerely,
> PsiACE

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

[Willem Jiang]

+1 (binding)
Here is what I checked:
- The checksums and signatures are validated.
- The LICENSE and NOTICE files look good to me.
- There is DISCLAIMER-WIP
- No binary files in the source release
- I can build the binary from the source kit.


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem


On Mon, Jun 26, 2023 at 10:44 AM Chunjin Mu  wrote:
>
> Hello Incubator Community:
>
> This is a call for a vote to release Apache StreamPark(Incubating) version 
> 2.1.1-RC1.
> The Apache StreamPark community has voted on and approved a proposal to 
> release Apache StreamPark(Incubating) version 2.1.1-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/mxrp760t5xy1fd6rs3fggj0cxrh7lohb
>
> Vote result thread:
> https://lists.apache.org/thread/6rhodhnblrs8n1vwcoxzmb0knb81sw66
>
> The release candidates:
> https://dist.apache.org/repos/dist/dev/incubator/streampark/2.1.1-RC1/
>
> Git tag for the release:
> https://github.com/apache/incubator-streampark/releases/tag/v2.1.1-rc1
>
> The artifacts signed with PGP key [E3E3F36B], corresponding to 
> [muchun...@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
>
>
> How to Build:
>
> 1) clone source code:
> > git clone -b v2.1.1-rc1 g...@github.com:apache/incubator-streampark.git
>
> 2) build project:
> > cd incubator-streampark && sh ./build.sh
>
> or compile by
> mvn -Pscala-2.11,shaded,webapp,dist -DskipTests clean install
> mvn -Pscala-2.12,shaded,webapp,dist -DskipTests clean install
>
>
>
>
> Thanks,
>
> On behalf of Apache StreamPark(Incubating) community
>
>
> Best,
> ChunJin Mu

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

Re: [VOTE] Release Apache OpenDAL(incubating) 0.37.0-rc1 - Incubator Vote Round 1

[Willem Jiang]

+1. Here is what I checked:
- The checksums and signatures are validated.
- The LICENSE and NOTICE files look good to me.
- There is a DISCLAIMER file about incubating.
- No binary files in the source release.

I checked the build file of other bindings, we need to add build
instructions for object_store.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Wed, Jun 7, 2023 at 11:08 AM Suyan  wrote:
>
> Hello Incubator PMC,
>
> The Apache OpenDAL community has voted and approved the release of Apache
> OpenDAL(incubating) 0.37.0-rc1. We now kindly request the IPMC members
> review and vote for this release.
>
> OpenDAL is a data access layer that allows users to easily and efficiently
> retrieve data from various storage services in a unified way.
>
> OpenDAL community vote thread:
>
> https://lists.apache.org/thread/v1cw3rtkwbysl2n606n4rqchf7k0x4f4
>
> Vote result thread:
>
> https://lists.apache.org/thread/4k22z387y3fw33x3spmowlmmtkh8tq7f
>
> The release candidate:
>
> https://dist.apache.org/repos/dist/dev/incubator/opendal/0.37.0-rc1/
>
> This release has been signed with a PGP available here:
>
> https://downloads.apache.org/incubator/opendal/KEYS
>
> Git branch for the release:
>
> https://github.com/apache/incubator-opendal/tree/release-0.37.0-rc1
>
> Please download, verify, and test.
>
> The VOTE will pass after got 3 binding approve.
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> To learn more about apache opendal, please see https://opendal.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
>
> More detailed checklist please refer to:
> https://github.com/apache/incubator-opendal/tree/main/scripts
>
> To compile from the source, please refer to:
> https://github.com/apache/incubator-opendal/blob/main/CONTRIBUTING.md
>
> Thanks.
>
> Sincerely,
> Suyan
>
> -
> 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 OpenDAL (incubating) 0.36.0-rc1 (Round 2)

[Willem Jiang]

+1. Here is what I checked:
- The checksums and signatures are validated.
- The LICENSE and NOTICE files look good to me.
- There is a DISCLAIMER file about incubating.
- No binary files in the source release
- I can build the binary from the source kit.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Mon, Jun 5, 2023 at 9:54 PM Xuanwo  wrote:
>
> > NOTE: README.md does not include `how to build.`
>
> Thanks for your NOTE! We have included the instructions on how to build in 
> our Contributing Guide. We will ensure that this is made clearer in future 
> updates.
>
> On Mon, Jun 5, 2023, at 21:41, Xiaoqiao He wrote:
> > +1(binding)
> >
> > [x] Download links are valid.
> > [x] Checksums and PGP signatures are valid.
> > [x] LICENSE files exist.
> > [x] NOTICE is included.
> > [x] DISCLAIMER is included.
> > [x] Source code artifacts have correct names matching the current release.
> > [x] All source files have license headers if necessary.
> > [x] Checked no binary files in source package.
> >
> > NOTE: README.md does not include `how to build.` (Which Willem was
> > concerned about last round.). I try to compile from source with `cargo
> > build`
> > (From tison mentioned above), it works well. IMO it is not a blocker issue.
> >
> > Best Regards,
> > - He Xiaoqiao
> >
> >
> > On Sun, Jun 4, 2023 at 6:48 AM tison  wrote:
> >
> >> +1 (binding)
> >>
> >> I checked -
> >>
> >> [x] Download links are valid.
> >> [x] Checksums and signatures.
> >> [x] + incubating in artifacts name
> >> [x] LICENSE/NOTICE files exist + DISCLAIMER exists
> >> [x] No unexpected binary files
> >> [x] All source files have ASF headers
> >> [x] Can compile from source - with `cargo build'
> >>
> >> Best,
> >> tison.
> >>
> >>
> >> Xuanwo  于2023年6月3日周六 19:50写道：
> >>
> >> > Hello Incubator PMC,
> >> >
> >> > The Apache OpenDAL community has voted and approved the release of Apache
> >> > OpenDAL(incubating) 0.36.0-rc1. We now kindly request the IPMC members
> >> > review and vote for this release.
> >> >
> >> > OpenDAL is a data access layer that allows users to easily and
> >> efficiently
> >> > retrieve data from various storage services in a unified way.
> >> >
> >> > OpenDAL community vote thread:
> >> >
> >> > https://lists.apache.org/thread/c211gqq2yl15jbxqk4rcnq1bdqltjm5l
> >> >
> >> > Vote result thread:
> >> >
> >> > https://lists.apache.org/thread/xk5myl10mztcfotn59oo59s4ckvojds6
> >> >
> >> > The release candidate:
> >> >
> >> > https://dist.apache.org/repos/dist/dev/incubator/opendal/0.36.0-rc1/
> >> >
> >> > This release has been signed with a PGP available here:
> >> >
> >> > https://downloads.apache.org/incubator/opendal/KEYS
> >> >
> >> > Git branch for the release:
> >> >
> >> > https://github.com/apache/incubator-opendal/tree/release-0.36.0-rc1
> >> >
> >> > Please download, verify, and test.
> >> >
> >> > The VOTE will pass after got 3 binding approve.
> >> >
> >> > [ ] +1 approve
> >> > [ ] +0 no opinion
> >> > [ ] -1 disapprove with the reason
> >> >
> >> > To learn more about apache opendal, please see
> >> https://opendal.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
> >> >
> >> > More detailed checklist please refer to:
> >> > https://github.com/apache/incubator-opendal/tree/main/scripts
> >> >
> >> > To compile from source, please refer to:
> >> > https://github.com/apache/incubator-opendal/blob/main/CONTRIBUTING.md
> >> >
> >> > Thanks
> >> >
> >> > Xuanwo
> >> >
> >> > -
> >> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> > For additional commands, e-mail: general-h...@incubator.apache.org
> >> >
> >> >
> >>
>
> --
> Xuanwo
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

Re: [VOTE] Release Apache Paimon(incubating) 0.4.0-incubating rc6

[Willem Jiang]

+1 (binding)
 Here is what I checked:
- Download links are valid.
- The checksums and signatures are validated.
- The LICENSE and NOTICE files look good to me.
- There is a DISCLAIMER file about incubating.
- No binary files in the source release
- I can build the binary from the source kit.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem


On Mon, May 29, 2023 at 11:48 AM Jingsong Li  wrote:
>
> Hello Incubator PMC,
>
> The Apache Paimon community has voted and approved the release of
> Apache Paimon(incubating) 0.4.0-incubating rc6. We now kindly request
> the IPMC members review and vote for this release.
>
> Apache Paimon(incubating) is a streaming data lake platform that
> supports high-speed data ingestion, change data tracking and efficient
> real-time analytics.
>
> Paimon community vote thread:
>
> https://lists.apache.org/thread/j70k0s0wnj4ocldwh5m89zswfwl3lp6q
>
> Vote result thread:
>
> https://lists.apache.org/thread/4w8jl3h1b77pcwkz66ydzcx4zxfcwrd2
>
> The official Apache source release to be deployed to dist.apache.org:
>
> https://dist.apache.org/repos/dist/dev/incubator/paimon/paimon-0.4.0-incubating-rc6/
>
> This source release has been signed with a PGP available here (Apache
> ID: lzljs3620320):
>
> https://downloads.apache.org/incubator/paimon/KEYS
>
> All artifacts to be deployed to the Maven Central Repository:
>
> https://repository.apache.org/content/repositories/orgapachepaimon-1018/
>
> Git branch for the release:
>
> https://github.com/apache/incubator-paimon-shade/tree/release-0.4.0-incubating-rc6
> https://github.com/apache/incubator-paimon/tree/release-0.4.0-incubating-rc6
>
> Previous Voting (Make sure problems are resolved) :
>
> https://lists.apache.org/thread/2fdsps5ggllo56oy61cp0gwb8spov1vf
>
> Please download, verify, and test.
>
> The VOTE will pass after 3 binding approve.
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> To learn more about apache paimon, please see https://paimon.apache.org/
>
> Checklist for reference:
>
> [ ] Download links are valid.
> [ ] Checksums and signatures.
> [ ] LICENSE/NOTICE files exist
> [ ] No unexpected binary files
> [ ] All source files have ASF headers
> [ ] Can compile from source
>
> Best,
> Jingsong
>
> -
> 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 OpenDAL(incubating) 0.35.0-rc1

[Willem Jiang]

Hi,

+1. Here is what I checked:
- The checksums and signatures are validated.
- The LICENSE and NOTICE files look good to me.
- There is a DISCLAIMER file about incubating.
- No binary files in the source release
- I can build the binary from the source kit.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Thu, May 25, 2023 at 2:58 PM Xuanwo  wrote:
>
> Hello Incubator PMC,
>
> The Apache OpenDAL community has voted and approved the release of Apache
> OpenDAL(incubating) 0.35.0-rc1. We now kindly request the IPMC members
> review and vote for this release.
>
> OpenDAL is a data access layer that allows users to easily and efficiently
> retrieve data from various storage services in a unified way.
>
> OpenDAL community vote thread:
>
> https://lists.apache.org/thread/lxn4ssg4tsvgvfwmcfv3h9wzqtprpjdf
>
> Vote result thread:
>
> https://lists.apache.org/thread/ygcyxsoy71zh2gyjh2kyr4qjf2ohd0or
>
> The release candidate:
>
> https://dist.apache.org/repos/dist/dev/incubator/opendal/0.35.0-rc1/
>
> This release has been signed with a PGP available here:
>
> https://downloads.apache.org/incubator/opendal/KEYS
>
> Git branch for the release:
>
> https://github.com/apache/incubator-opendal/tree/release-0.35.0-rc1
>
> Please download, verify, and test.
>
> The VOTE will pass after got 3 binding approve.
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> To learn more about apache opendal, please see https://opendal.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
>
> More detailed checklist please refer to:
> https://github.com/apache/incubator-opendal/tree/main/scripts
>
> To compile from source, please refer to:
> https://github.com/apache/incubator-opendal/blob/main/CONTRIBUTING.md
>
> Thanks
>
>
> Xuanwo
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

Re: [VOTE] Release Apache OpenDAL(incubating) 0.34.0-rc1

[Willem Jiang]

The LICENSE file communicates the licensing of all content in an
Apache product distribution.
It always contains the text of the Apache License and sometimes more
information.[1]
NOTICE file is used for required third-party notices [2]。
If we do the source release， we only include the bundled third-party
license in the License file.
Please take a look at StreamPark Source License[3] as an example。

[1]https://infra.apache.org/licensing-howto.html
[2]https://infra.apache.org/licensing-howto.html#mod-notice
[3]https://github.com/apache/incubator-streampark/blob/dev/LICENSE

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Fri, May 19, 2023 at 10:14 PM tison  wrote:
>
> >These License information should be put into the License file.
>
> Any requirement for this statement?
>
> In ASF projects I involve, I always put dependencies info in the NOTICE
> file and leave the LICENSE file AS IS from
> https://apache.org/licenses/LICENSE-2.0.txt.
>
> Best,
> tison.
>
>
> Willem Jiang  于2023年5月19日周五 22:03写道：
>
> > I checked the NOTICE file, it includs the third-party dependencies
> > license information.
> > These License information should be put into the License file.
> > Some third-party dependency Licenses are Apache or MIT,  we can choose
> > Apache License by default.
> >
> > I cannot find how to build from the README.md file in the root
> > directory.  Did I miss something?
> >
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Wed, May 17, 2023 at 12:14 PM Xuanwo  wrote:
> > >
> > > Hello Incubator PMC,
> > >
> > > The Apache OpenDAL community has voted and approved the release of Apache
> > > OpenDAL(incubating) 0.34.0-rc1. We now kindly request the IPMC members
> > > review and vote for this release.
> > >
> > > OpenDAL is a data access layer that allows users to easily and
> > efficiently
> > > retrieve data from various storage services in a unified way.
> > >
> > > OpenDAL community vote thread:
> > >
> > > https://lists.apache.org/thread/nh80zh9y11frx7ls9fn4dvj1hdh2n4pb
> > >
> > > Vote result thread:
> > >
> > > https://lists.apache.org/thread/hjkxdvqr1dsrq71cr6j7ltjxvwmn0jg2
> > >
> > > The release candidate:
> > >
> > > https://dist.apache.org/repos/dist/dev/incubator/opendal/0.34.0-rc1/
> > >
> > > This release has been signed with a PGP available here:
> > >
> > > https://downloads.apache.org/incubator/opendal/KEYS
> > >
> > > Git branch for the release:
> > >
> > > https://github.com/apache/incubator-opendal/tree/release-0.34.0-rc1
> > >
> > > Please download, verify, and test.
> > >
> > > The VOTE will pass after got 3 binding approve.
> > >
> > > [ ] +1 approve
> > > [ ] +0 no opinion
> > > [ ] -1 disapprove with the reason
> > >
> > > To learn more about apache opendal, please see
> > https://opendal.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
> > >
> > > More detailed checklist please refer to:
> > > https://github.com/apache/incubator-opendal/tree/main/scripts
> > >
> > > To compile from source, please refer to:
> > > https://github.com/apache/incubator-opendal/blob/main/CONTRIBUTING.md
> > >
> > > Thanks
> > >
> > > Xuanwo
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >

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

Re: [VOTE] Release Apache OpenDAL(incubating) 0.34.0-rc1

[Willem Jiang]

I checked the NOTICE file, it includs the third-party dependencies
license information.
These License information should be put into the License file.
Some third-party dependency Licenses are Apache or MIT,  we can choose
Apache License by default.

I cannot find how to build from the README.md file in the root
directory.  Did I miss something?


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Wed, May 17, 2023 at 12:14 PM Xuanwo  wrote:
>
> Hello Incubator PMC,
>
> The Apache OpenDAL community has voted and approved the release of Apache
> OpenDAL(incubating) 0.34.0-rc1. We now kindly request the IPMC members
> review and vote for this release.
>
> OpenDAL is a data access layer that allows users to easily and efficiently
> retrieve data from various storage services in a unified way.
>
> OpenDAL community vote thread:
>
> https://lists.apache.org/thread/nh80zh9y11frx7ls9fn4dvj1hdh2n4pb
>
> Vote result thread:
>
> https://lists.apache.org/thread/hjkxdvqr1dsrq71cr6j7ltjxvwmn0jg2
>
> The release candidate:
>
> https://dist.apache.org/repos/dist/dev/incubator/opendal/0.34.0-rc1/
>
> This release has been signed with a PGP available here:
>
> https://downloads.apache.org/incubator/opendal/KEYS
>
> Git branch for the release:
>
> https://github.com/apache/incubator-opendal/tree/release-0.34.0-rc1
>
> Please download, verify, and test.
>
> The VOTE will pass after got 3 binding approve.
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> To learn more about apache opendal, please see https://opendal.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
>
> More detailed checklist please refer to:
> https://github.com/apache/incubator-opendal/tree/main/scripts
>
> To compile from source, please refer to:
> https://github.com/apache/incubator-opendal/blob/main/CONTRIBUTING.md
>
> Thanks
>
> 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 Kvrocks(incubating) as a TLP

[Willem Jiang]

+1 (binding), and good luck!

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Fri, May 12, 2023 at 11:55 AM hulk  wrote:
>
> Hello all,
>
> We've got positive feedback on the DISCUSS thread[1], I'd like to start an
> official VOTE thread now.
>
> Please vote on the resolution pasted below to graduate Apache Kvrocks from
> the incubator to the Top Level Project.
>
> [ ] +1 Graduate Apache Kvrocks from the Incubator.
> [ ] +0 No opinion.
> [ ] -1 Don't graduate Apache Kvrocks 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/ld8x1wvh1n745j96ksy0pmy92gwn2t06
>
> ---
>
> Establish the Apache Kvrocks 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 distributed key-value NoSQL database, supporting the rich
> data structure.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Kvrocks Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Kvrocks Project be and hereby is responsible
> for the creation and maintenance of software related to a distributed
> key-value NoSQL database, supporting the rich data structure; and be it
> further
>
> RESOLVED, that the office of "Vice President, Apache Kvrocks" 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 Kvrocks
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache Kvrocks
> 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 Kvrocks Project:
>
>  * Alfejik Liu  
>  * Hulk Lin 
>  * Jean-Baptiste Onofré 
>  * Liang Chen   
>  * Mingyang Liu 
>  * Von Gosling  
>  * Xiaoqiao He  
>  * Yaroslav Stepanchuk  
>  * Yuan Wang
>  * Zili Chen
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Hulk Lin be appointed to
> the office of Vice President, Apache Kvrocks, 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 Kvrocks Project be and hereby is tasked with
> the migration and rationalization of the Apache Incubator Kvrocks
> podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Kvrocks podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.

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

[Willem Jiang]

+1,
I just ran the script with JDK11 to build the release kit from the
source with the command without any error.
Here is what I checked:
- The checksums and signatures are validated.
- The LICENSE and NOTICE files look good to me.
- There is DISCLAIMER-WIP
- No binary files in the source release
- I can build the binary from the source kit.

Thanks,

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem
On Sat, May 6, 2023 at 7:57 PM Chunjin Mu  wrote:
>
> Hello mentor, please see line 182 in the build.sh script, the latest
> compilation command is as follows
>
> mvn -Pscala-2.11,shaded,webapp,dist -DskipTests clean install
> mvn -Pscala-2.12,shaded,webapp,dist -DskipTests clean install
>
> Best,
> ChunJin Mu
>
>
> Willem Jiang  于2023年5月6日周六 19:13写道：
>
> > When I tried to build the artifact from the source, I got the below
> > error. I cannot find
> > org.apache.streampark:streampark-shaded-slf4j:jar:1.0.0 from the maven
> > central repo.
> >
> >  Failed to execute goal on project streampark-common_2.12: Could not
> > resolve dependencies for project
> > org.apache.streampark:streampark-common_2.12:jar:2.1.0: The following
> > artifacts could not be resolved:
> > org.apache.streampark:streampark-shaded-slf4j:jar:1.0.0,
> > org.apache.streampark:streampark-shaded-jackson:jar:1.0.0:
> > org.apache.streampark:streampark-shaded-slf4j:jar:1.0.0 was not found
> > in https://repo.maven.apache.org/maven2 during a previous attempt.
> >
> > Did I miss something?
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Fri, May 5, 2023 at 11:47 PM Chunjin Mu  wrote:
> > >
> > > Hello Incubator Community:
> > >
> > > This is a call for a vote to release Apache StreamPark(Incubating)
> > version 2.1.0-RC1.
> > > The Apache StreamPark community has voted on and approved a proposal to
> > release Apache StreamPark(Incubating) version 2.1.0-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/t01b2lbtqzyt7j4dsbdp5qjc3gngjsdq
> > >
> > > Vote result thread:
> > > https://lists.apache.org/thread/t5z58mvrs1drgzfyc48c9lhmd8skswn7
> > >
> > > The release candidate:
> > > https://dist.apache.org/repos/dist/dev/incubator/streampark/2.1.0-RC1/
> > >
> > > Git tag for the release:
> > > https://github.com/apache/incubator-streampark/releases/tag/v2.1.0-rc1
> > >
> > > Maven artifacts are available in a staging repository at:
> > >
> > https://repository.apache.org/content/repositories/orgapachestreampark-1012/
> > >
> > > The artifacts signed with PGP key [05016886], corresponding to [
> > muchun...@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
> > >
> > >
> > > How to Build:
> > >
> > > 1) clone source code:
> > > > git clone -b v2.1.0-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,
> > > ChunJin Mu
> >

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

[Willem Jiang]

When I tried to build the artifact from the source, I got the below
error. I cannot find
org.apache.streampark:streampark-shaded-slf4j:jar:1.0.0 from the maven
central repo.

 Failed to execute goal on project streampark-common_2.12: Could not
resolve dependencies for project
org.apache.streampark:streampark-common_2.12:jar:2.1.0: The following
artifacts could not be resolved:
org.apache.streampark:streampark-shaded-slf4j:jar:1.0.0,
org.apache.streampark:streampark-shaded-jackson:jar:1.0.0:
org.apache.streampark:streampark-shaded-slf4j:jar:1.0.0 was not found
in https://repo.maven.apache.org/maven2 during a previous attempt.

Did I miss something?

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Fri, May 5, 2023 at 11:47 PM Chunjin Mu  wrote:
>
> Hello Incubator Community:
>
> This is a call for a vote to release Apache StreamPark(Incubating) version 
> 2.1.0-RC1.
> The Apache StreamPark community has voted on and approved a proposal to 
> release Apache StreamPark(Incubating) version 2.1.0-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/t01b2lbtqzyt7j4dsbdp5qjc3gngjsdq
>
> Vote result thread:
> https://lists.apache.org/thread/t5z58mvrs1drgzfyc48c9lhmd8skswn7
>
> The release candidate:
> https://dist.apache.org/repos/dist/dev/incubator/streampark/2.1.0-RC1/
>
> Git tag for the release:
> https://github.com/apache/incubator-streampark/releases/tag/v2.1.0-rc1
>
> Maven artifacts are available in a staging repository at:
> https://repository.apache.org/content/repositories/orgapachestreampark-1012/
>
> The artifacts signed with PGP key [05016886], corresponding to 
> [muchun...@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
>
>
> How to Build:
>
> 1) clone source code:
> > git clone -b v2.1.0-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,
> ChunJin Mu

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

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

[Willem Jiang]

+1(binding) and good luck.
BTW,  The email was formatted in a strange way.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Fri, Apr 28, 2023 at 10:52 AM JUN GAO  wrote:
>
> Hello all, We've got positive feedback on the DISCUSS thread [1], I'd like
> to start an official VOTE thread now. Please vote on the resolution pasted
> below to graduate Apache SeaTunnel from the incubator to the Top Level
> Project. [ ] +1 Graduate Apache SeaTunnel from the Incubator. [ ] +0 Don't
> care. [ ] -1 Don't graduate Apache SeaTunnel 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/4kcgth87yxztv6d991p98n2w2mnx8cq5
> -
>
> Establish the Apache SeaTunnel 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 very easy-to-use
> ultra-high-performance distributed data integration platform that supports
> real-time synchronization of massive data. NOW, THEREFORE, BE IT RESOLVED,
> that a Project Management Committee (PMC), to be known as the "Apache
> SeaTunnel Project", be and hereby is established pursuant to Bylaws of the
> Foundation; and be it further RESOLVED, that the Apache SeaTunnel Project
> be and hereby is responsible for the creation and maintenance of software
> related to a very easy-to-use ultra-high-performance distributed data
> integration platform that supports real-time synchronization of massive
> data; and be it further RESOLVED, that the office of "Vice President,
> Apache SeaTunnel" 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 SeaTunnel Project, and to have primary responsibility for management
> of the projects within the scope of responsibility of the Apache SeaTunnel
> 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 SeaTunnel Project: * Calvin Kirs  * Chao Tian <
> tyrantluci...@apache.org> * Gary Gao  * Guo William <
> guo...@apache.org> * Jean-Baptiste Onofré  * Jia Fan <
> fan...@apache.org> * Jiajie Zhong  * Jun Gao <
> gaojun2...@apache.org> * Kevin Ratnasekera  * Lidong
> Dai  * Lifeng Nie  * Ricky Huo <
> ricky...@apache.org> * Shen Jinxin  * Ted Liu <
> ted...@apache.org> * Wenjun Ruan  * Willem Ning Jiang <
> ningji...@apache.org> * Zhenxu Ke  * kid Xiong <
> ridxi...@apache.org> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Jun Gao
> be appointed to the office of Vice President, Apache SeaTunnel, 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 SeaTunnel Project be and hereby is tasked with
> the migration and rationalization of the Apache Incubator SeaTunnel
> podling; and be it further RESOLVED, that all responsibilities pertaining
> to the Apache Incubator SeaTunnel podling encumbered upon the Apache
> Incubator PMC are hereafter discharged.
> 
>
> --
>
> Best Regards
>
> 
>
> EricJoy2048
> gaojun2...@gmail.com

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

Re: [VOTE] Release Apache DevLake (Incubating) v0.16.0-rc2

[Willem Jiang]

+1(binding).

I checked
- The checksums and signatures are validated.
- The LICENSE and NOTICE files look good to me.
- There is DISCLAIMER-WIP
- No binary files in the source release

Willem Jiang


On Mon, Apr 24, 2023 at 9:33 PM Zikuan An  wrote:
>
> Hello everyone,
>
> This is a call for vote to release Apache DevLake (Incubating) v0.16.0-rc2.
> The Apache DevLake community has voted on and approved a proposal to
> release Apache DevLake (Incubating) version v0.16.0-rc2.
>
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Community vote thread:
>
> https://lists.apache.org/thread/2v2so22fj9mg5h7jck1opsqhjyc86k06
>
>
> Community vote result thread:
>
> https://lists.apache.org/thread/wfzzjv53vfxml54098o6dt4913j47d4j
>
>
> The release candidates:
>
> https://dist.apache.org/repos/dist/dev/incubator/devlake/0.16.0-incubating-rc2
>
>
> Git tag for the release:
>
> https://github.com/apache/incubator-devlake/releases/tag/v0.16.0-rc2
>
>
> Keys to verify the Release Candidate:
>
> https://downloads.apache.org/incubator/devlake/KEYS
>
>
> How to build:
>
> https://devlake.apache.org/docs/DeveloperManuals/DeveloperSetup
>
>
> 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
>
>
> Thanks
>
> Zikuan An

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

[jira] [Commented] (INCUBATOR-275) Need to update Incubator statistics on the website landing page

[Willem Jiang (Jira)]

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

Willem Jiang commented on INCUBATOR-275:


[~andreww]
 I didn't find the PR 
[here](https://github.com/apache/incubator/pulls?q=is%3Apr+is%3Aclosed).  
 Could you share the PR link by adding a new comment in this JIRA?


> Need to update Incubator statistics on the website landing page
> ---
>
> Key: INCUBATOR-275
> URL: https://issues.apache.org/jira/browse/INCUBATOR-275
> Project: Incubator
>  Issue Type: Improvement
>  Components: site
>Reporter: Andrew Wetmore
>Priority: Major
>
> h3. The index page for the Incubator website has a brief history that seems 
> to be three or four years out of date. I would be glad to update it, but need 
> the current figures:
>  * Total number of podlings
>  * Number that have graduated
>  * Total number of mentors
>  * Average # of podlings in incubation at any one time
>  * Typical incubation period
> h3. Incubator History
> The Incubator was created [in 
> 2002|https://www.apache.org/foundation/records/minutes/2002/board_minutes_2002_10_16.txt].
>  As of November 2019 it has helped 315 podlings, of which more than 200 have 
> graduated. More than 300 mentors have guided and supported podlings. There 
> are around 45 or 50 podlings in incubation at any one time, and incubation 
> typically takes 1 1/2 years.



--
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: [DISCUSS] Graduate Apache SeaTunnel (incubating) as a TLP

[Willem Jiang]

+1， it is good to see SeaTunnel build up the community and made bunch of 
releases in the incubator.

Willem


> 在 2023年4月11日，下午12:06，david zollo  写道：
> 
> SeaTunnel project has a very active community, many contributors are
> participating in the project, growing from less than 10 contributors before
> the incubation stage to hundreds of contributors now.
> As a mentor of SeaTunnel, glad to see a diverse community being built, this
> project podling is ready to graduate from the incubator.
> 
> 
> 
> Best Regards
> 
> ---
> Apache DolphinScheduler PMC Chair & Apache SeaTunnel Mentor
> David
> Linkedin: https://www.linkedin.com/in/davidzollo
> Twitter: @WorkflowEasy 
> ---
> 
> 
>> On Tue, Apr 11, 2023 at 11:53 AM JUN GAO  wrote:
>> 
>> Hi all,
>> After discussion with the community [1], and a positive vote result [2].
>> We'd like to bring this to a discussion at the IPMC.
>> 
>> Please see the proposed resolution below and let us know what you think.
>> 
>> A few status to help with the discussion:
>> 
>> - Released 8 Apache releases, through 5 different release managers
>> - Invited 15 new committers (all accepted)
>> - Invited 4 new PPMC members (all accepted)
>> - There are 174 contributors for now
>> - There are 456 emails sent by 72 people in dev mailing-list excepted
>> GitBox forwarded
>> - 1364 Issues created during ASF incubating, 1063 Issues resolved during
>> ASF incubating
>> - 2292 PRs created during ASF incubating, 2225 PRs merged during ASF
>> incubating
>> - Apache SeaTunnel name search has been approved [3] - Finished the Podling
>> Maturity Assessment for SeaTunnel [4], all items are passed
>> 
>> We've resolved all branding issues which include Logo, GitHub repo,
>> document, website and others.
>> 
>> [1] https://lists.apache.org/thread/y8p6f78q3logrxhoy2vsvs04h4d5hmbz
>> 
>> [2] https://lists.apache.org/thread/vcg7md4y6ot7r48k3oskwnj4pkpom3f7
>> 
>> [3] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-210
>> 
>> [4]
>> https://docs.google.com/document/d/1dICPxp44OHEktUsMNXkVt5JXRYgDimVyuuikQ4gwBS8/edit#heading=h.n8r0cp4gv8fu
>> 
>> ---
>> 
>> Establish the Apache SeaTunnel 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 very easy-to-use ultra-high-performance distributed data
>> integration platform that supports real-time synchronization of massive
>> data.
>> 
>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
>> (PMC), to be known as the "Apache SeaTunnel Project", be and hereby is
>> established pursuant to Bylaws of the Foundation; and be it further
>> 
>> RESOLVED, that the Apache SeaTunnel Project be and hereby is responsible
>> for the creation and maintenance of software related to a very
>> easy-to-use ultra-high-performance distributed data integration platform
>> that supports real-time synchronization of massive data; and be it
>> further
>> 
>> RESOLVED, that the office of "Vice President, Apache SeaTunnel" 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 SeaTunnel
>> Project, and to have primary responsibility for management of the
>> projects within the scope of responsibility of the Apache SeaTunnel
>> 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 SeaTunnel
>> Project:
>> 
>> * Calvin Kirs  
>> * Chao Tian
>> * Gary Gao 
>> * Guo William  
>> * Jean-Baptiste Onofré 
>> * Jia Fan  
>> * Jiajie Zhong 
>> * Jun Gao  
>> * Kevin Ratnasekera
>> * Lidong Dai   
>> * Lifeng Nie   
>> * Ricky Huo
>> * Shen Jinxin  
>> * Ted Liu  
>> * Wenjun Ruan  
>> * Willem Ning Jiang
>> * Zhenxu Ke
>> * kid Xiong
>> 
>> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Jun Gao be appointed to the
>> office of Vice President, Apache SeaTunnel, 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 SeaTunnel Project be and hereby is tasked with
>> the migration and rationalization of the Apache Incubator SeaTunnel
>> podling; and be it further
>> 
>> RESOLVED, that all responsibilities pertaining to the Apache Incubator
>> SeaTunnel podling encumbered upon the Apache Incubator PMC are 

Re: [VOTE] Release Apache Celeborn(Incubating) 0.2.1-incubating-rc0

[Willem Jiang]

+1 binding.

I checked:
- incubating in the release kit name
- The checksums and signatures are validated.
- The LICENSE and NOTICE files look good to me.
- There is a DISCLAIMER in the release kits
- No binary files in the source release kits
- I can build the source

BTW， there is no maven release for the Apache Celeborn.
We can consider doing a maven release next time.


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem


On Mon, Mar 20, 2023 at 9:47 PM rexxiong  wrote:
>
> Hello Incubator Community,
>
> This is a call for a vote to release Apache Celeborn(Incubating) version
> 0.2.1-incubating-rc0
>
> The Apache Celeborn community has voted on and approved a proposal to
> release
> Apache Celeborn(Incubating) version 0.2.1-incubating-rc0
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Celeborn community vote thread:
> • https://lists.apache.org/thread/7vnm4p3dv9lq1cklj5xh1fzrho381bzy
>
> Vote result thread:
> • https://lists.apache.org/thread/21gjf2v5wn85h37dwdv4yvhbxz48d37r
>
> The release candidate:
> •
> https://dist.apache.org/repos/dist/dev/incubator/celeborn/v0.2.1-incubating-rc0
>
> Git tag for the release:
> •
> https://github.com/apache/incubator-celeborn/releases/tag/v0.2.1-incubating-rc0
>
> Public keys file:
> • https://dist.apache.org/repos/dist/release/incubator/celeborn/KEYS
>
> The change log is available in:
> •
> https://github.com/apache/incubator-celeborn/compare/v0.2.0-incubating...v0.2.1-incubating-rc0
>
> 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
>
> Thanks,
> rexxiong

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

Re: [VOTE] Retire PageSpeed

[Willem Jiang]

+1 (binding)

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Tue, Mar 14, 2023 at 4:47 AM Christian Grobmeier
 wrote:
>
> Hello,
>
> as recently discussed, I think the PageSpeed podling is ready for retirement.
>
> https://lists.apache.org/thread/jxw7mqmpcfxxp0mnnx28o0k78tym507b
>
> There has been no activity for a while; there are no signs of change soon.
>
> Please vote:
>
> [ ] +1, retire
> [ ] -1 don't retire, because...
>
> Please don't hesitate to vote -1 if you feel this podling should remain.
>
> This vote will be kept open for at least the usual 72 hours.
>
> Kind regards,
> Christian
>
> -
> 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] Retire the Spot podling

[Willem Jiang]

+1 (binding)

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Tue, Mar 14, 2023 at 4:42 AM Christian Grobmeier
 wrote:
>
> Hello,
>
> as recently discussed, I think the Spot podling is ready for retirement.
>
> Several roll calls were made, like this one:
> https://lists.apache.org/list?priv...@spot.apache.org:2022-10
>
> There has been no activity for a while; there are no signs of change soon.
>
> Please vote:
>
> [ ] +1, retire
> [ ] -1 don't retire, because...
>
> Please don't hesitate to vote -1 if you feel this podling should remain.
>
> This vote will be kept open for at least the usual 72 hours.
>
> Kind regards,
> Christian
>
> -
> 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: Confluence wiki page gives "Unknown macro: markdown"

[Willem Jiang]

I got the same problem when updating the report of the incubator.
But it's hard to trace the problem without any hit.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Tue, Mar 7, 2023 at 12:17 PM tison  wrote:
>
> For example, https://cwiki.apache.org/confluence/display/INCUBATOR/March2023
>
> I found some possible debugging info, but I don't have permission to try
> it:
> https://community.atlassian.com/t5/Confluence-questions/Unknown-macro-code/qaq-p/820495
>
> Any confluence space maintainer may take a look?
>
> Best,
> tison.

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

Re: [VOTE] Accept Paimon into the Apache Incubator

[Willem Jiang]

+1 （binding）

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Mon, Mar 6, 2023 at 3:59 PM Yu Li  wrote:
>
> Hi All,
>
> Following up on the [DISCUSS] thread on Paimon [1], I would like to call
> a VOTE to accept Paimon into the Apache Incubator, please check out
> the Paimon Proposal from the incubator wiki [2].
>
>
> Please cast your vote:
>
>
> [ ] +1, bring Paimon into the Incubator
>
> [ ] +0, I don't care either way
>
> [ ] -1, do not bring Paimon into the Incubator, because...
>
>
> The vote will open at least for 72 hours, and only votes from the Incubator
> PMC are binding, but votes from everyone are welcome.
>
> Best Regards,
> Yu
>
> [1] https://lists.apache.org/thread/hr3d7tpw02w6ybrnnlf3hcbhfxotwpvn
> [2] https://cwiki.apache.org/confluence/display/INCUBATOR/PaimonProposal

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

Re: [VOTE] Release Apache Celeborn(Incubating) 0.2.0-incubating-rc5

[Willem Jiang]

+1 (binding)

I checked the src kits:
- incubating in the release kit name
- The checksums and signatures are validated.
- The LICENSE and NOTICE files look good to me.
- There is a DISCLAIMER in the release kits
- No binary files in the source release kits
- I can build the source

I have the same question as Justin asked, do we need to add the ASF
License header to this file[1]?
[1] 
./common/src/main/java/org/apache/celeborn/common/network/util/LimitedInputStream.java

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem


On Fri, Feb 24, 2023 at 11:48 AM Ethan Feng  wrote:
>
> Hello Incubator Community,
>
> This is a call for a vote to release Apache Celeborn(Incubating)
> version 0.2.0-incubating-rc5
>
> The Apache Celeborn community has voted on and approved a proposal to release
> Apache Celeborn(Incubating) version 0.2.0-incubating-rc5
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Celeborn community vote thread:
> • https://lists.apache.org/thread/6f28tyvqsqdpjr0wpg2low4hlh39bx4j
>
> Vote result thread:
> • https://lists.apache.org/thread/9bhflkrwrmk81w1stbhvztzc6mb6gjco
>
> The release candidate:
> • 
> https://dist.apache.org/repos/dist/dev/incubator/celeborn/v0.2.0-incubating-rc5
>
> Git tag for the release:
> • 
> https://github.com/apache/incubator-celeborn/releases/tag/v0.2.0-incubating-rc5
>
> Public keys file:
> • https://dist.apache.org/repos/dist/release/incubator/celeborn/KEYS
>
> The change log is available in:
> • 
> https://github.com/apache/incubator-celeborn/compare/v0.1.4...v0.2.0-incubating-rc5
>
> 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
>
> Thanks,
> Ethan Feng
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

Re: [DISCUSS] Incubating Proposal for Paimon

[Willem Jiang]

Hi Yu,

Just so you know, Apache Camel was a subproject of Apache ActiveMQ,
and it became the TLP without going through the incubator process.
It's common to have to turn a subproject into TLP if most developers
know how to run an ASF project.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Fri, Feb 24, 2023 at 4:48 PM Yu Li  wrote:
>
> Thanks all for the interest.
>
> Paimon is already a sub-project of Apache Flink [1], and yes we intend to
> graduate as its own Top Level Project after incubating.
>
> And yes, similar question was raised during discussion in the Flink
> community [2], and  please allow me to quote some content below for easier
> reference:
> ===
> Apache has the tradition to incubate projects out of mature
> sub-projects of top-level
> projects, for example Apache HBase [3] and Apache Ozone [4] are both born
> as sub-projects of Apache Hadoop. Although HBase and Ozone both become
> top-level projects directly, they were also developed for more than 3 years
> as sub-projects, and we wonder whether table store is as mature to be a
> top-level project. On the other hand, we believe the table store project is
> qualified to enter the Apache incubation as an innovative lake storage, and
> has the potential to graduate in a year or two.
> ===
>
> However, it's true that we are not quite sure whether the project is
> qualified to directly become another TLP, thus we took a conservative
> approach. Please feel free to let us know if you have any suggestions.
> Thanks.
>
> Best Regards,
> Yu
>
> [1] https://lists.apache.org/thread/h3hkvt3nq9gfblt3k0w2pr6xrg54pqxt
> [2] https://lists.apache.org/thread/hgpcg6mhhoblzbnh1opkrxynmc93vxzp
> [3] https://www.mail-archive.com/hbase-dev@hadoop.apache.org/msg18236.html
> [4]
> https://cwiki.apache.org/confluence/display/HADOOP/Ozone+Hadoop+subproject+to+Apache+TLP+proposal
>
>
> On Fri, 24 Feb 2023 at 12:16, Justin Mclean 
> wrote:
>
> > Hi,
> >
> > Given that most of the people involved are familiar with the ASF and how
> > projects should operate, I wonder if you should not just become a
> > subproject of Fink or a separate TLP? Are there any reasons you think the
> > project needs to go through incubation?
> >
> > 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] Retire Marvin-AI from Incubator

[Willem Jiang]

+1 (binding)

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Wed, Feb 22, 2023 at 10:11 PM Calvin Kirs  wrote:
>
> Hi,
>
> Marvin-AI has been incubating since 2018-08-27.
>
> Since 2021, activity has been low, and the chances of attracting new
> committers and building a vibrant community seem very slim at this
> point.
>
> At the same time, the project also missed many reports last year, and
> no one responded to the PPMC roll call.
>
> The community discussion and vote can be found here[1],[2].
>
> I therefore propose to retire Marvin-AI from the Incubator.
>
> Voting will start now and will remain open for at least 72 hours.
>
> Notice:
>
> Because the dev vote didn't get enough +1, so it's not a laze vote.
>
> If you are interested in this and are willing to contribute, please
> don't hesitate to vote your -1.
>
>
> [ ] +1 Retire Marvin-AI
> [ ] -1 Keep Marvin-AI and I’m willing to join to make it an Apache Community.
>
> [1]https://lists.apache.org/thread/6w0s115gnvsww3ptjt3f1xcrr02211hr
> [2]https://lists.apache.org/thread/hpd7fmjm138r09jrzd7d8jdyz3360q52
>
>
> --
> Best wishes！
> CalvinKirs
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

Re: [VOTE] Accept OpenDAL into the Apache Incubator

[Willem Jiang]

+1(binding).
I'm looking forward to working with this project as a mentor.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem


On Tue, Feb 21, 2023 at 9:24 PM tison  wrote:
>
> Hi all,
>
> Following up on the [DISCUSS] thread on OpenDAL[1], I would like to call a
> VOTE to accept OpenDAL into the Apache Incubator, please check out the
> OpenDAL Proposal from the incubator wiki[2].
>
> Please cast your vote:
>
> [ ] +1, bring OpenDAL into the Incubator
> [ ] +0, I don't care either way
> [ ] -1, do not bring OpenDAL into the Incubator, because...
>
> The vote will open at least for 72 hours, and only votes from the Incubator
> PMC members are binding, but votes from everyone are welcome.
>
> [1] https://lists.apache.org/thread/px7wjcjy3rd4s59d4d3ll1x6y11d240r
> [2] https://cwiki.apache.org/confluence/display/INCUBATOR/OpenDAL+Proposal
>
> Best,
> tison.

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

[Willem Jiang]

+1 binding

I checked:
- incubating in the release kit
- checked the git tag with the fixes of rc07
- The checksums and signatures are validated.
- The LICENSE and NOTICE files look good to me.
- There is a DISCLAIMER in the release kits
- No binary files in the source release kits

Willem Jiang



On Fri, Feb 17, 2023 at 12:55 PM Huajie Wang  wrote:
>
> Hello Incubator Community:
>
> This is a call for a vote to release Apache StreamPark(Incubating)
> version 2.0.0-rc7
>
> The Apache StreamPark community has voted on and approved a proposal to
> release
> Apache StreamPark(Incubating) version 2.0.0-rc7
>
> 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.
>
> In this vote we fixed some licenses issues mentioned in RC6 vote process:
> https://lists.apache.org/thread/lvpc2hywbkdlvkpmjm0knchyk6vhvmnl
> https://github.com/apache/incubator-streampark/pull/2327
>
> StreamPark community vote thread:
> https://lists.apache.org/thread/78v780mdqh9xb8ntgn6q8qg113nql07c
>
> Vote result thread:
> https://lists.apache.org/thread/y77vc8c3d5x7wtslm99jydgwmp10ypxv
>
> Release notes:
> https://streampark.apache.org/download/release-note/2.0.0/
>
> The release candidates:
> https://dist.apache.org/repos/dist/dev/incubator/streampark/2.0.0-RC7/
>
> Maven artifacts are available in a staging repository at:
> https://repository.apache.org/content/repositories/orgapachestreampark-1010/
>
> Git tag for the release:
> https://github.com/apache/incubator-streampark/releases/tag/v2.0.0-rc7
>
> The artifacts signed with PGP key [5AE01B8E], corresponding to [
> benj...@apache.org], that can be found in keys file:
> https://downloads.apache.org/incubator/streampark/KEYS
>
> Last commit hash:
> •apache-streampark-2.0.0-incubating-src.tar.gz:
> 95c5a44ed13c24c1ba351d93db5cc7a6127a38c346a767d547b2cf8a93eb836e67f196053eb3692601a98f20d25b3e5eb0c6e70ef48a130f9a2f1ce3de080ded
>
> • apache-streampark_2.11-2.0.0-incubating-bin.tar.gz:
> f070eacd87fb641c7745a6b2a62e1de611b2f59d943889aa6ca275d352174b07ff6ea3b7aa9b7af05167915990ddc4a9025f9d85853d2008da02d8e411f04218
>
> • apache-streampark_2.12-2.0.0-incubating-bin.tar.gz:
> fdd555c85ca1d061772b878999da34ec2bfbe25c78b708d2b7153d23e78fdf7b5b74d776610fdbbccb9240b5929208f86120727176cb8a56b092358c7476a223
>
> 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
>
>
> How to Build:
>
> 1) clone source code:
> > git clone -b v2.0.0-rc7 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,
> Huajie Wang

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

Re: [VOTE] Release Apache HugeGraph (Incubating) 1.0.0-rc2

[Willem Jiang]

+1 (binding)
I checked the src kits:
- incubating in the release kit
- The checksums and signatures are validated.
- The LICENSE and NOTICE files look good to me.
- There is a DISCLAIMER in the release kits
- No binary files in the source release kits

Willem Jiang




On Mon, Feb 13, 2023 at 8:07 PM Imba Jin  wrote:
>
> Hello Incubator Community,
>
> This is a call for a vote to release Apache HugeGraph(Incubating)
> version 1.0.0-rc2
>
> The Apache HugeGraph community has voted on and approved a proposal
> to release Apache HugeGraph(Incubating) version 1.0.0-rc2
>
> In this release, we fixed a string of license problems mentioned by
> Willem Jiang & Justin Mclean:
> 1. check and fix all license-headers in source files
> 2. remove copyright in ASF header & refer it in NOTICE file & correct
> the information
> 3. remove all the unnecessary binary files in source release package
> 4. remove swagger-ui's static files & use a download way to handle it
> 5. choose one proper license instead of list them all in the LICENSE
> file for easy review (remove extra *GPL/CC-BY license)
>
> Now we kindly request the Incubator PMC members review and vote on
> this incubator release.
>
> HugeGraph community vote thread:
> • https://lists.apache.org/thread/zt5pw0s5njwy75c49v45ch3hswyq9bd8
>
> Vote result thread:
> • https://lists.apache.org/thread/y4yx1qovsmp3nyc7rgdlrv6298wsoyzr
>
> The release candidate:
> • https://dist.apache.org/repos/dist/dev/incubator/hugegraph/1.0.0
>
> Git tag & Commit hash for the release:
> • https://github.com/apache/incubator-hugegraph/tree/1.0.0-rc2 (c8e0f0c)
> • https://github.com/apache/incubator-hugegraph-toolchain/tree/1.0.0-rc2
> (e2b4eb2)
> • https://github.com/apache/incubator-hugegraph-computer/tree/1.0.0-rc2
> (d2b9526)
> • https://github.com/apache/incubator-hugegraph-commons/tree/1.0.0-rc2 
> (82f2a65)
>
> Release notes:
> • https://hugegraph.apache.org/docs/changelog/hugegraph-1.0.0-release-notes/
>
> Keys to verify the Release Candidate:
> • https://downloads.apache.org/incubator/hugegraph/KEYS
>
> The release GPG user ID: imbajin (j...@apache.org)
>
> The vote will be open for at least 72 hours or until necessary number
> of votes are reached.
>
> Please vote accordingly:
>   [ ] +1 approve
>   [ ] +0 no opinion
>   [ ] -1 disapprove with the reason
>
> More detail checklist  please refer:
> • 
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
>
> Steps to validate the release, could refer to:
> English Version:
> • https://hugegraph.apache.org/docs/contribution-guidelines/validate-release/
> Chinese Version:
> • 
> https://hugegraph.apache.org/cn/docs/contribution-guidelines/validate-release/
>
>
> Thanks,
> On behalf of Apache HugeGraph(Incubating) community
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

Re: [DISCUSS] Incubating Proposal for OpenDAL

[Willem Jiang]

+1, it's an interesting project. I'd like to be a mentor of this project.
BTW, even though there are  37 contributors, I found Xuanwo did most
of the development, which is not a good bus factor[1] of this project.
We can make it better during the incubating process.

[1]https://en.wikipedia.org/wiki/Bus_factor


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Fri, Feb 17, 2023 at 7:22 AM tison  wrote:
>
> Hi IPMC,
>
> I would like to propose OpenDAL[1] as a new apache incubator project, you
> can find the proposal[2] of OpenDAL for more detail.
>
> [1] https://github.com/datafuselabs/opendal
> [2] https://cwiki.apache.org/confluence/display/INCUBATOR/OpenDAL+Proposal
>
> Best,
> tison.
>
> Full text of the proposal below:
>
> ## Abstract
>
> OpenDAL means “Open Data Access Layer”. It’s a Rust library that helps
> developers access data freely, painlessly, and efficiently over multiple
> services, including AWS S3, HDFS, POSIX-compatible file systems, and so on.
>
> ## Proposal
>
> OpenDAL provides the following features to support developers accessing
> data freely, painlessly, and efficiently:
>
> - Freely
> - Access different storage services in the same way
> - Behavior tests for all services
> - Cross-language/project bindings (working in progress)
> - Painlessly
> - **100%** of documents covered
> - Powerful [Layers](
> https://opendal.databend.rs/opendal/layers/index.html)
> - Automatic [retry](
> https://opendal.databend.rs/opendal/layers/struct.RetryLayer.html) support
> - Full observability support: [logging](
> https://opendal.databend.rs/opendal/layers/struct.LoggingLayer.html
> ), [tracing](
> https://opendal.databend.rs/opendal/layers/struct.TracingLayer.html), and
> [metrics](
> https://opendal.databend.rs/opendal/layers/struct.MetricsLayer.html).
> - Native chaos testing
> - Native service-side encryption support
> - Efficiently
> - Zero cost: mapping to underlying API calls directly
> - Best effort: auto-pick the best `read`/`seek`/`next` implementations
> based on services
> - [Auto metadata reuse](
> https://opendal.databend.rs/rfcs/0561-list-metadata-reuse.html): avoid
> extra `metadata` calls
>
> OpenDAL was originally designed to be used by the Databend project but is
> now being used by Mozilla's sccache, DeepETH's mars, and several database
> startups.
>
> We believe that the OpenDAL project will provide diversity value to the
> community if OpenDAL is brought into the Apache incubator.
>
> ## Background
>
> OpenDAL is being developed by an open-source community from day one and is
> owned by DatafuseLabs. The project has been launched in February 2022.
>
> ## Rationale
>
> OpenDAL provides a unified storage abstraction layer that simplifies the
> interfacing of different storage services. In addition, OpenDAL provides
> further advanced storage encapsulation, enabling enhancements such as
> automatic retry, request optimization, and observability. OpenDAL makes it
> possible to develop once and run on any storage service.
>
> ## Initial Goals
>
> By transferring ownership of the project to the ASF, OpenDAL expects to
> ensure its neutrality and further encourage and facilitate the adoption of
> OpenDAL by the community.
>
> Some of the areas we would like to focus on during the Apache incubation
> phase include:
>
> - A healthier community: more maintainers and contributors will be able to
> participate in OpenDAL and own different modules.
> - Wider adoption: OpenDAL can be adopted by more open source/commercial
> projects, which in turn drives its own functionality.
> - Richer integration: OpenDAL enables greater integration of storage
> services and offers a wider range of language bindings.
>
> ## Current Status
>
> ### Meritocracy
>
> We intend to radically expand the initial developer and user community by
> running the project the 'Apache way'. Users and new contributors will be
> respected and welcomed. They will earn credit by participating in the
> community and providing quality patches/support to move the project
> forward. They will also be encouraged to provide non-code contributions
> (documentation, events, community management, etc.) and will be rewarded
> accordingly. Those with a proven track record of support and quality will
> be encouraged to become committers.
>
> ### Community
>
> Contributors: 37
>
> Users:
>
> - Databend: A cloud data warehouse
> - GreptimeDB: A time-series database
> - Sccache: ccache with cloud storage
> - RisingWave: A Distributed SQL Database for Stream Processing
>
> ### Core Developers
>
> The core developers are all experienced open-sour

Re: [VOTE] Graduate Apache EventMesh(incubating) as an Apache Top Level Project

[Willem Jiang]

+1 （binding）
It's great to see EventMesh in good shape for graduation.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Fri, Feb 10, 2023 at 10:32 AM Eason Chen  wrote:
>
> Dear Apache Incubator Community and IPMC members,
>
> After having the graduation discussion in the EventMesh community [1],
> we passed the vote within the EventMesh community [2] and the vote
> result was published[3].
> We then discussed the graduation for EventMesh in the Apache Incubator
> Community [4], where no issues were raised and positive replies were
> received.
>
> I would like to start this voting thread to request graduating Apache
> EventMesh(incubating) from Apache Incubator as a Top Level Project.
>
> Please provide your vote accordingly:
> [ ] +1 Yes, I support the EventMesh project to graduate from the
> Apache Incubator.
> [ ] +0 No opinion.
> [ ] -1 No, the EventMesh project is not ready to graduate, because...
>
> Thank you for participating in the vote. This vote will stay open for
> at least 72 hours.
>
> Here is an overview of the Apache EventMesh(incubating) to help with the vote.
>
> *Community*
>
> ● 5 new PPMC members were added, bringing the total number of PPMC
> members to 14 from at least 9 different organizations.
> ● 20 new Committers were added, bringing the total number of
> committers to 42 from at least 30 different organizations.
> ● 220+ new contributors participate in the community. The number of
> contributors is now 250+ and growing.
> ● 20 Bi-weekly online meetings were held among the committers,
> contributors, and users. The meeting minutes are recorded on the
> mailing list[5] and cwiki [6].
> ● The dev@eventmesh mailing list currently has 117 subscribers.
> ● We've confirmed the VP, PMC, and Committers in the preparation
> discussion at private@eventmesh [7]. Eason
> Chen(chenguangsh...@apache.org) was recommended as Vice President.
>
> *Project*
>
> ● Apache EventMesh(incubating) builds a fully serverless platform for
> distributed event-driven applications.
> ● Project maturity model is detailed in [8].
> ● EventMesh has been incubating [9] since 2021-02-18 for over 23 months.
> ● EventMesh community released a total of 7 Apache releases [10] by 6
> different release managers from 5 different organizations.
> ● 1300+ issues created, and 1100+ issues closed [11].
> ● 1600+ pull requests created, and 1600+ pull requests closed [12],
> 2500+ commits added.
> ● The release cadence is about 3 months, with an average of 180+
> issues and 230+ pull requests per release.
> ● Please refer to the EventMesh project incubation status [13][14] for
> more information.
>
> *Brands, License, and Copyright*
>
> ● We applied the brand [15], which has been reviewed and approved.
> ● EventMesh community maintains project code on GitHub and all modules
> code is under Apache 2.0 license. We have reviewed all the
> dependencies and ensured they do not bring any license issues [16].
> All the status files, license headers, and copyright are up to date.
> ● EventMesh official website [17] is compliant with Apache Foundation
> requirements[18].
>
> -
> BEGINNING OF DRAFT RESOLUTION
> -
>
> Establish the Apache EventMesh 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 fully serverless platform used to build distributed
> event-driven applications.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache EventMesh Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache EventMesh Project be and hereby is responsible
> for the creation and maintenance of software related to a fully
> serverless platform used to build distributed event-driven applications;
> and be it further
>
> RESOLVED, that the office of "Vice President, Apache EventMesh" 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 EventMesh
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache EventMesh
> 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 EventMesh
> Project:
>

Re: [VOTE] Release Apache DevLake (Incubating) v0.15.0-rc5

[Willem Jiang]

+1 （binding）

I checked：

- Checked the changes with the git tag
- Reviewed icons license change
- The checksums and signatures are validated.
- The LICENSE and NOTICE files look good to me.
- There is DISCLAIMER-WIP
- No binary files in the source release

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Fri, Feb 3, 2023 at 10:43 PM Zikuan An  wrote:
>
> Hello everyone,
>
> This is a call for vote to release Apache DevLake (Incubating) v0.15.0-rc5.
> The Apache DevLake community has voted on and approved a proposal to
> release Apache DevLake (Incubating) version v0.15.0-rc5.
>
>
> In this release we fixed the license issues.
>
> 1. Added Apache 2.0 license to all of the icons we have drawn.
>
> 2. Added the license info to the MIT licensed icons.
>
> 3. Removed all files with the ManyPixels licence, which are incompatible
> with Apache 2.0.
>
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Linkis community vote thread:
>
> https://lists.apache.org/thread/d2xy34vqzmw8x5zt4ncd3j3tg79bhkc5
>
>
> Vote result thread:
>
> https://lists.apache.org/thread/8fl0bq79hnm6nlpvytxprl8rmkv4p21w
>
>
> The release candidates:
>
> https://dist.apache.org/repos/dist/dev/incubator/devlake/0.15.0-incubating-rc5
>
>
> Git tag for the release:
>
> https://github.com/apache/incubator-devlake/releases/tag/v0.15.0-rc5
>
>
> Keys to verify the Release Candidate:
> *https://downloads.apache.org/incubator/devlake/KEYS
> <https://downloads.apache.org/incubator/devlake/KEYS>*
>
> How to build:
> *https://devlake.apache.org/docs/DeveloperManuals/DeveloperSetup
> <https://devlake.apache.org/docs/DeveloperManuals/DeveloperSetup>*
>
> 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 unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Does ASF have any agreement with docker?

[Willem Jiang]

After going through the docker application page, it looks like we need
to ask for help from Infra to apply the account for the whole Apache
origination.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem
On Mon, Feb 6, 2023 at 11:25 PM Jason Porter  wrote:
>
> Any news on this? It would be good to get a license for Apache projects.
>
> Jason Porter
> Software Engineer
> He/Him/His
>
> IBM
>
> On Feb 5, 2023, at 20:50, Willem Jiang  wrote:
>
> ASF has the targeted sponsorship with Jetbrain[1], which supports
> applying for the license with an apache email.
> I just found docker is listed as a gold-targeted sponsor[2],  maybe we
> try to apply for the free license with apache org email.
>
> [1]https://www.apache.org/foundation/thanks#targeted-platinum-sponsors
> [2]https://www.apache.org/foundation/thanks#targeted-gold-sponsors
>
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Tue, Jan 31, 2023 at 10:14 AM Jeff Zhang  wrote:
>
> Docker desktop is not free any more, I am wondering whether ASF has any
> agreement with docker. Or does each apache project need to apply for this
> docker open source program separately?
>
> https://www.docker.com/community/open-source/application/
>
>
> --
> Best Regards
>
> Jeff Zhang
>
> -
> 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: Does ASF have any agreement with docker?

[Willem Jiang]

ASF has the targeted sponsorship with Jetbrain[1], which supports
applying for the license with an apache email.
I just found docker is listed as a gold-targeted sponsor[2],  maybe we
try to apply for the free license with apache org email.

[1]https://www.apache.org/foundation/thanks#targeted-platinum-sponsors
[2]https://www.apache.org/foundation/thanks#targeted-gold-sponsors


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Tue, Jan 31, 2023 at 10:14 AM Jeff Zhang  wrote:
>
> Docker desktop is not free any more, I am wondering whether ASF has any
> agreement with docker. Or does each apache project need to apply for this
> docker open source program separately?
>
> https://www.docker.com/community/open-source/application/
>
>
> --
> Best Regards
>
> Jeff Zhang

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

[Willem Jiang]

-1, we need to start a new vote with the tag of rc5.
I just found out that the rc4 tag[1] was created on Feb 3th, it has
some new changes[2] after the vote in the stream park dev on Feb 1st.
Please keep in mind, if we made some changes on the voting release
kit, we need to start a new vote, otherwise the vote is invalid.
We need to include the last commit hash within the voting mail next time.

[1]https://github.com/apache/incubator-streampark/tree/v2.0.0-rc4
[2]https://github.com/apache/incubator-streampark/commits/v2.0.0-rc4


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Sat, Feb 4, 2023 at 7:22 PM Huajie Wang  wrote:
>
> Hello Incubator Community:
>
> This is a call for a vote to release Apache StreamPark(Incubating)
> version 2.0.0-RC4
>
> The Apache StreamPark community has voted on and approved a proposal to
> release
> Apache StreamPark(Incubating) version 2.0.0-RC4
>
> 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.
>
> In this release we fixed some license issues[1].
>
> StreamPark community vote thread:
> https://lists.apache.org/thread/gxdc5d9posbbc3lmbstyw9sr350tthgm
>
> Vote result thread:
> https://lists.apache.org/thread/v3gc6p9xdsohg2xn80ydbtf6tbm1t13n
>
> The release candidate:
> https://dist.apache.org/repos/dist/dev/incubator/streampark/2.0.0-RC4/
>
> Git tag for the release:
> https://github.com/apache/incubator-streampark/releases/tag/v2.0.0-rc4
>
> Release notes:
> https://streampark.apache.org/download/release-note/2.0.0/
>
> Maven artifacts are available in a staging repository at:
> https://repository.apache.org/content/repositories/orgapachestreampark-1008/
>
> The artifacts signed with PGP key [5AE01B8E], corresponding to [
> benj...@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
>
>
> How to Build:
>
> 1) clone source code:
> > git clone -b v2.0.0-rc4 g...@github.com:apache/incubator-streampark.git
>
> 2) build project:
> > cd incubator-streampark && sh ./build.sh
>
>
> Thanks,
>
> On behalf of Apache StreamPark(Incubating) community
>
> [1] https://github.com/apache/incubator-streampark/pull/2294
>
>
> Best,
> Huajie Wang

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

Re: [VOTE] Release Apache HugeGraph(Incubating) 1.0.0

[Willem Jiang]

-1（binding）

There are some License header issues that need to be fixed.
1. The License header of the Java source files has the wrong copyright
declaration.
We can put this copyright information into the NOTICE file[1]
2. The copyright time is not right.  We may need to consider the end
time HugeGraph was donated to ASF.  such as "Copyright 2017-2021
HugeGraph Authors"
3. We cannot put the ASF License header to the swagger-ui files in the
hugegraph-dist/src/assembly/static/swagger-ui/, as these files are
generated.
If we can generate these during the compile time, it could save us
some effort.
4. "It is important to keep NOTICE as brief and simple as possible, as
each addition places a burden on downstream consumers.
Do not add anything to NOTICE which is not legally required."[2][3]


[1]https://www.apache.org/legal/src-headers.html#headers
[2]https://infra.apache.org/licensing-howto.html#mod-notice
[3]https://www.apache.org/legal/src-headers.html#notice



Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Sun, Jan 8, 2023 at 11:19 PM Imba Jin  wrote:
>
> Hello Incubator Community,
>
> This is a call for a vote to release Apache HugeGraph(Incubating) version 
> 1.0.0
>
> The Apache HugeGraph community has voted on and approved a proposal to release
> Apache HugeGraph(Incubating) version 1.0.0
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> HugeGraph community vote thread:
>   • https://lists.apache.org/thread/vsc9gh3obhwzgvj9v36g26w006xr2vjv
>
> Vote result thread:
>   • https://lists.apache.org/thread/9brtvd0l2q9ow83dmvpl3g3kngo7cggz
>
> The release candidate:
>   • https://dist.apache.org/repos/dist/dev/incubator/hugegraph/1.0.0
>
> Git tag for the release:
>   • https://github.com/apache/incubator-hugegraph/tree/1.0.0
>   • https://github.com/apache/incubator-hugegraph-toolchain/tree/1.0.0
>   • https://github.com/apache/incubator-hugegraph-computer/tree/1.0.0
>   • https://github.com/apache/incubator-hugegraph-commons/tree/1.0.0
>
> Release notes:
>   • https://hugegraph.apache.org/docs/changelog/hugegraph-1.0.0-release-notes/
>
> Due to this is the first release version, we have 3 people to participate in 
> it.
>
> The GPG user ID(s): Imba Jin, vaughn, coderzc, corresponding to
>  j...@apache.org, vau...@apache.org, zhaoc...@apache.org
>
> that can be found in public keys file:
>   • https://downloads.apache.org/incubator/hugegraph/KEYS
>
> The vote will be open for at least 72 hours or until necessary number
> of votes are reached.
>
> Please vote accordingly:
>   [ ] +1 approve
>   [ ] +0 no opinion
>   [ ] -1 disapprove with the reason
>
> More detail checklist  please refer:
> • 
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
>
> Steps to validate the release，Please refer to:
> • https://hugegraph.apache.org/docs/contribution-guidelines/validate-release/
> (EN)
> • 
> https://hugegraph.apache.org/cn/docs/contribution-guidelines/validate-release/
> (CN)
>
>
> Thanks,
> On behalf of Apache HugeGraph(Incubating) community
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

Re: [VOTE] Release Apache StreamPark 2.0.0-RC1

[Willem Jiang]

-1.

There are some License related issues we need to address
1. We need to specify the third-party code we include in the source
artifact in the License file.
2. It's good that we list the bundled backend third-party libraries'
Licenses in the binary release License files. Still, we need to choose
the License if the third-party libraries have multiple Licenses.
Please check for more information here[1] if you are not sure
which kind of License we could use in the  Apache project.
3. We don't list the front-end js third-party libraries License.
Please check the nodes license tool to record this information.

There is a minor typo in the NOTICE file, "form" should be replaced
with "from".

[1]https://www.apache.org/legal/resolved.html

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Sun, Dec 25, 2022 at 8:01 AM Huajie Wang  wrote:
>
> Hello Incubator Community:
>
> The Apache StreamPark community has voted on and approved a proposal to
> release, Apache StreamPark version 2.0.0-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/8683w7pwf24qg852px4ngwnorhqz27n1
>
> Vote result thread:
> https://lists.apache.org/thread/4qqw8vpw13ngtc4y2340o37crbf7oqjz
>
> The release candidate:
> https://dist.apache.org/repos/dist/dev/incubator/streampark/2.0.0-RC1/
>
> Git tag for the release:
> https://github.com/apache/incubator-streampark/releases/tag/v2.0.0-rc1
>
> Maven artifacts are available in a staging repository at:
> https://repository.apache.org/content/repositories/orgapachestreampark-1004/
>
>
> The artifacts signed with PGP key [5AE01B8E], corresponding to [
> benj...@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 necessary number of
> votes are reached.
>
> Please vote accordingly:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Best,
> Huajie Wang

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

Re: [VOLUNTEER WANTED]Incubator Shepherds

[Willem Jiang]

Hi Calvin,

Please count me in.
I think I can help with one to two podling reports per month.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Tue, Dec 20, 2022 at 10:46 AM Calvin Kirs  wrote:
>
> Hi,
>
> Shepherd[1] participation has been low for the past two years (maybe
> longer), so I thought of trying to see if any other IPMC members would
> be willing to take on this role.
>
> if possible,  we could allocate them according to everyone's free periods.
> so, if you are interested in this, please leave your name and  time cycle
>
> [1]https://cwiki.apache.org/confluence/display/INCUBATOR/IncubatorShepherds
>
> --
> Best wishes！
> CalvinKirs
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

Re: [VOTE] Apache Tuweni graduation

[Willem Jiang]

I agree we don't need to hold the Tuweni graduation for the release checking.
But if we want to build a sustainable Open Source project, we still
need to pay lots of attention to community building.


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Sun, Dec 11, 2022 at 9:24 AM Antoine Toulme  wrote:
>
> Hello folks,
>
> Apache Tuweni had a much smaller community when it started its incubation at 
> Apache. The path of this project has been impacted by the domain it applies 
> to and the pandemic certainly hasn't helped. Still it has managed to create 
> enough momentum to make regular releases and check off all incubation checks.
> Community building is definitely still on the menu - right now and later as 
> well. We will continue building and including folks. We have onboarded 
> successfully multiple committers and have received contributions. I expect 
> this trend to continue and mature.
>
> The question is whether the best place for us to continue growing is the 
> incubator. The incubator adds additional checks on our releases and slows 
> down our cycles, which has historically driven folks to fork and move away 
> from the project.
>
> The incubator doesn't offer opportunities for community building, from what I 
> know. We will need to continue to build our image and presence to attract 
> contributors on our own.
>
> The project mentors have been nothing short of fantastic. They have been 
> helpful in maturing the project. In my opinion, we are using their precious 
> time when they should be engaged in helping other projects of the incubator.
>
> With this, I want to thank the incubator. We had a great experience building 
> with you all. I personally believe we should free the incubator's time and 
> attention to concentrate on other projects. I also believe the project is 
> mature enough to function outside of the incubator.
>
> I vote +1 to graduate Tuweni from the incubator.
>
> Thanks,
>
> Antoine
>
> > On Dec 7, 2022, at 3:37 PM, larry mccay  wrote:
> >
> > We have also recently seen long term incubating projects with considerable
> > adoption falter.
> > I consider the fact that they did not graduate early enough a contributing
> > factor here.
> >
> > Nothing wrong with incubation but staying in the incubator and encountering
> > attrition is different from TLP
> > with some churn with new folks coming into an official TLP project while
> > others can fall off in a healthy way.
> >
> > Again, having the community test and release 14 separate releases
> > demonstrates contributors in the community
> > even if they aren't all materially contributing code.
> >
> >
> >
> > On Wed, Dec 7, 2022 at 3:45 AM Christofer Dutz 
> > wrote:
> >
> >> Hi all,
> >>
> >> And in the last few months the ASF has sadly seen enough cases, in which
> >> even big projects suffered from the lack of diversity.
> >> So, I would also consider this to be a blocker.
> >>
> >> Community building isn’t something that happens or comes for free.
> >> It’s actually hard work, but it needs to be done.
> >>
> >> Just my opinion on this topic.
> >>
> >> Chris
> >>
> >> From: Willem Jiang 
> >> Date: Wednesday, 7. December 2022 at 02:59
> >> To: general@incubator.apache.org 
> >> Subject: Re: [VOTE] Apache Tuweni graduation
> >> It looks like we need a dedicated community leader[1] to build a
> >> diverse community (just borrow a pattern from InnerSource Common[2]).
> >>
> >> " Communication takes up a significant percentage of a community
> >> leader's daily work. At the same time, he or she will likely also have
> >> to spearhead the initial development, too. In the face of limited
> >> capacity, inexperienced leaders will tend to focus on development and
> >> neglect communication. The barrier for potential contributors to make
> >> their first contribution and to commit to the community will be much
> >> higher if the community leader is hard to reach or is slow to respond
> >> to feedback and questions for lack of time."
> >>
> >> [1]
> >> https://github.com/InnerSourceCommons/InnerSourcePatterns/blob/main/patterns/2-structured/dedicated-community-leader.md#forces
> >> [2]https://innersourcecommons.org/
> >>
> >> Willem Jiang
> >>
> >> Twitter: willemjiang
> >> Weibo: 姜宁willem
> >>
> >> On Tue, Dec 6, 2022 at 9:51 AM larry mccay  wrote:
> >>>
> >>> I'm not so sure that I see this as a blocker f

Re: [VOTE] Apache Tuweni graduation

[Willem Jiang]

It looks like we need a dedicated community leader[1] to build a
diverse community (just borrow a pattern from InnerSource Common[2]).

" Communication takes up a significant percentage of a community
leader's daily work. At the same time, he or she will likely also have
to spearhead the initial development, too. In the face of limited
capacity, inexperienced leaders will tend to focus on development and
neglect communication. The barrier for potential contributors to make
their first contribution and to commit to the community will be much
higher if the community leader is hard to reach or is slow to respond
to feedback and questions for lack of time."

[1]https://github.com/InnerSourceCommons/InnerSourcePatterns/blob/main/patterns/2-structured/dedicated-community-leader.md#forces
[2]https://innersourcecommons.org/

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Tue, Dec 6, 2022 at 9:51 AM larry mccay  wrote:
>
> I'm not so sure that I see this as a blocker for graduation.
> There was enough consensus and testing to spin and publish 14 releases.
> There has been healthy conversation about this very topic among the mentors
> and contributors on the private list.
>
> The nature of this project is that the consumption of these libraries are
> going to get less traction while in incubation and a community may grow
> larger as a TLP as confidence is instilled by that status.
>
> The Tuweni community has demonstrated the ability to publish releases
> within that Apache Way and guidelines, has welcomed new contributors, etc.
> The long term success will require a larger active community but I don't
> think that needs to block graduation as the incubation goals have been met.
>
> My 2 cents.
>
> On Mon, Dec 5, 2022 at 7:41 PM Willem Jiang  wrote:
>
> > I agree with Gang Li. The Bus factor[1] of this project is relatively high.
> >
> > [1]https://en.wikipedia.org/wiki/Bus_factor
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Mon, Dec 5, 2022 at 11:06 PM li gang  wrote:
> > >
> > > I checked the contributions of the Tuweni project[1],the traffic of the
> > > mail list d...@tuweni.apache.org[2] and the KEYS[3].
> > >
> > > It looks like the project is mainly maintained by Antoine Toulme self,
> > > I have a concern this is not comply with the diversity.
> > >
> > > [1]https://github.com/apache/incubator-tuweni/graphs/contributors
> > > [2]https://lists.apache.org/list?d...@tuweni.apache.org
> > > [3]https://downloads.apache.org/incubator/tuweni/KEYS
> > >
> > > Antoine Toulme  于2022年12月5日周一 15:14写道：
> > >
> > > > Dear Apache Incubator Community and IPMC members,
> > > >
> > > > We discussed the graduation for Tuweni in the Apache Incubator
> > > > Community [4], where no issues were raised and positive replies were
> > > > received.
> > > > After having the graduation discussion in the Tuweni community [1], we
> > > > have passed the vote within Tuweni community [2] and the vote result
> > > > was published [3].
> > > >
> > > > I would like to start this voting thread to request graduating Apache
> > > > Tuweni(incubating) from Apache Incubator as a Top Level Project.
> > > >
> > > > Please provide your vote accordingly:
> > > > [ ] +1 Yes, I support Tuweni project to graduate from the Apache
> > Incubator.
> > > > [ ] +0 No opinion.
> > > > [ ] -1 No, the Tuweni project is not ready to graduate, because...
> > > >
> > > > Thank you for participating in the vote. This vote will stay open for
> > at
> > > > least 72 hours.
> > > >
> > > > Here is an overview of the Apache Tuweni(incubating) to help with the
> > > > vote.
> > > >
> > > > *Community*
> > > >
> > > > ● The PPMC is active, with PMC members voting for graduation along with
> > > > mentors.
> > > > ● 6 new committers were added, bringing the total number of committers
> > to
> > > > 14 from 12 different
> > > > organizations.
> > > > ● The number of contributors is now 25 and growing.
> > > > ● The dev@Tuweni mailing list currently has 33 subscribers [4].
> > > >
> > > > *Project*
> > > >
> > > > ● Apache Tuweni (incubating) is a set of libraries and other tools to
> > aid
> > > > development of blockchain and other  decentralized software in Java and
> > > > other JVM languages. It includes a low-level

Re: [VOTE] Apache Tuweni graduation

[Willem Jiang]

I agree with Gang Li. The Bus factor[1] of this project is relatively high.

[1]https://en.wikipedia.org/wiki/Bus_factor

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Mon, Dec 5, 2022 at 11:06 PM li gang  wrote:
>
> I checked the contributions of the Tuweni project[1],the traffic of the
> mail list d...@tuweni.apache.org[2] and the KEYS[3].
>
> It looks like the project is mainly maintained by Antoine Toulme self,
> I have a concern this is not comply with the diversity.
>
> [1]https://github.com/apache/incubator-tuweni/graphs/contributors
> [2]https://lists.apache.org/list?d...@tuweni.apache.org
> [3]https://downloads.apache.org/incubator/tuweni/KEYS
>
> Antoine Toulme  于2022年12月5日周一 15:14写道：
>
> > Dear Apache Incubator Community and IPMC members,
> >
> > We discussed the graduation for Tuweni in the Apache Incubator
> > Community [4], where no issues were raised and positive replies were
> > received.
> > After having the graduation discussion in the Tuweni community [1], we
> > have passed the vote within Tuweni community [2] and the vote result
> > was published [3].
> >
> > I would like to start this voting thread to request graduating Apache
> > Tuweni(incubating) from Apache Incubator as a Top Level Project.
> >
> > Please provide your vote accordingly:
> > [ ] +1 Yes, I support Tuweni project to graduate from the Apache Incubator.
> > [ ] +0 No opinion.
> > [ ] -1 No, the Tuweni project is not ready to graduate, because...
> >
> > Thank you for participating in the vote. This vote will stay open for at
> > least 72 hours.
> >
> > Here is an overview of the Apache Tuweni(incubating) to help with the
> > vote.
> >
> > *Community*
> >
> > ● The PPMC is active, with PMC members voting for graduation along with
> > mentors.
> > ● 6 new committers were added, bringing the total number of committers to
> > 14 from 12 different
> > organizations.
> > ● The number of contributors is now 25 and growing.
> > ● The dev@Tuweni mailing list currently has 33 subscribers [4].
> >
> > *Project*
> >
> > ● Apache Tuweni (incubating) is a set of libraries and other tools to aid
> > development of blockchain and other  decentralized software in Java and
> > other JVM languages. It includes a low-level bytes library, serialization
> > and deserialization codecs (e.g. RLP), various cryptography functions and
> > primitives, and lots of other helpful utilities. Tuweni is developed for
> > JDK 11 or higher.
> > ● Project maturity model and incubation status is detailed in [5]
> > ● Tuweni has been incubating [5] since 2019-02-25 for over 45
> > months.
> > ● Tuweni community released a total of 14 Apache releases [6].
> > ● 331 pull requests created closed [7].
> > ● 76 issues created, and 46 issues closed [8].
> > ● The release cadence is about 3 months.
> >
> > *Brand, License, and Copyright*
> >
> > ● We submitted an application for the brand [9] and it has been
> > reviewed and approved.
> > ● Tuweni community maintains project code on GitHub and all modules
> > code is under Apache 2.0 license. We have reviewed all the
> > dependencies and ensured they do not bring any license issues [10].
> > All the status files, license headers, and copyright are up to date.
> > ● Tuweni official website [11] is compliant with Apache Foundation
> > requirements [12].
> >
> > [1] https://lists.apache.org/thread/z3flpmqcss21xc8vmtwqqfs961p4g9t5
> > [2] https://lists.apache.org/thread/c04cmvfwh1wt2mxmc9zo89o6bnhm2xqk
> > [3] https://lists.apache.org/thread/8m4lq3k1v93m1k482syj7kn1ldb62665
> > [4] https://lists.apache.org/list.html?d...@tuweni.apache.org
> > [5] https://incubator.apache.org/projects/tuweni.html
> > [6] https://github.com/apache/incubator-tuweni/releases
> > [7] https://github.com/apache/incubator-tuweni/pulls
> > [8] https://github.com/apache/incubator-tuweni/issues
> > [9] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-167
> > [10] https://github.com/apache/incubator-tuweni/blob/main/LICENSE
> > [11] https://tuweni.apache.org
> > [12] https://whimsy.apache.org/pods/project/tuweni
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>
> --
>
>
> --
> Best Regards
>
> DolphinScheduler PMC
> Gang Li 李岗
>
> lgcar...@apache.org

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

Re: [DISCUSS] KIE Proposal

[Willem Jiang]

We need to go through the IP clearance and help the project to do the
release that follows the Apache police.
It could be a nightmare for the incubator if we donate an "Umbrella Project."
Can we consider donating sub-projects such as kogito one by one?


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Fri, Dec 2, 2022 at 9:21 AM Niall Pemberton
 wrote:
>
> Wow, 137 GitHub repositories!
>
> OK, so 38 are archived and 19 are forks, but that still leaves 80! Do you
> have a rough idea of how many of those would be part of the incubation?
>
> Historically, Apache has been against "Umbrella Projects" - encouraging
> them to break up and become individual Top Level Projects (TLP) in their
> own right - the biggest example of that was Jakarta which used to be
> anything java related - but there have been others where sub-projects which
> have a life of their own have moved out to become TLPs.
>
> To me this looks like it should be 4 or 5 projects - its not clear whether
> kie is a product in its own right (with releasable artifcats) or just the
> umbrella that the others are grouped under?
>   * drools
>   * jbpm
>   * kogito
>   * optaplanner
>   * kie ???
>
> Niall
>
>
> On Thu, 1 Dec 2022 at 21:36, Jason Porter  wrote:
>
> > Abstract
> >
> > KIE (Knowledge is Everything) is a community of solutions and supporting
> > tooling for knowledge engineering and process automation, focusing on
> > events, rules, and workflows.
> >
> > Proposal<
> > https://cwiki.apache.org/confluence/display/INCUBATOR/New+Podling+Proposal#proposal
> > >
> >
> > KIE is a community dedicated to supporting knowledge engineering and
> > process automation, using standards from groups like OMG (BPMN, CMMN, DMN),
> > CNCF (Serverless Workflow, Cloud Events), and DMG (PMML, PFA). KIE is
> > comprised of leading open-source projects (like Drools and jBPM), which
> > provide modeling and code authoring tools in this space. The work has a
> > strong emphasis on being a first-class citizen for Kubernetes but will
> > continue to support embedded and other environments such as edge computing.
> > Drools and jBPM are well-known projects in their areas of rules and
> > workflow and they will be joined by another project, building on a shared
> > core with jBPM, for CNCF’s Serverless Workflow - this project is going
> > through a naming process at the time of this application. Kogito is the
> > foundation project for workflow which jBPM and CNCF’s Serverless Workflow
> > build on. Services and frameworks are provided to enable those projects in
> > a cloud-native environment and tooling is made available through KIE Tools.
> >
> > Background<
> > https://cwiki.apache.org/confluence/display/INCUBATOR/New+Podling+Proposal#background
> > >
> >
> > Experience has shown that a holistic approach is a practical requirement
> > for any  knowledge engineering and process automation. This requires a
> > breadth of capabilities able to model and execute an application’s data
> > models, rules, workflows, and events. These projects aim to provide a
> > holistic approach with a strong emphasis on congruency across them.
> >
> > Rationale<
> > https://cwiki.apache.org/confluence/display/INCUBATOR/New+Podling+Proposal#rationale
> > >
> >
> > Knowledge engineering and process automation have been and continue to
> > play a large part in today’s software lifecycle. To date, there have been
> > few truly open-source implementations of any of the specifications (DMN,
> > PMML, BPMN, CNCF Workflow, etc). The projects within Red Hat implement
> > these standards and fill that gap of having an open-source implementation.
> >
> >
> > The projects within KIE also mesh well with other Apache projects such as
> > Apache Camel and Apache Airavata. Integrations could be done at the IoT
> > level with Apache PLC4X and others.
> >
> >
> > Developers need a solution that follows, implements, and collaborates with
> > these industry specifications. The Apache Software Foundation would allow
> > these projects to continue to grow in a vendor-neutral environment and
> > promote further collaboration with existing integrations and future
> > partners.
> >
> > Initial Goals<
> > https://cwiki.apache.org/confluence/display/INCUBATOR/New+Podling+Proposal#initial-goals
> > >
> >
> > First and foremost, we aim to enlarge the community. KIE has primarily
> > been an open-source community of Red Hat Developers and users outside of
> > Red Hat. Adding IBM to the list of developers helps

Re: [DISCUSS] Graduate Apache Sedona to a Top Level Project

[Willem Jiang]

I just went through the project status; it is in good shape for graduation.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Fri, Dec 2, 2022 at 5:28 PM Jia Yu  wrote:
>
> Dear Apache Incubator Community (CCed Sedona dev),
>
> Apache Sedona has been incubating since 07-19-2020. For over 2 years, the
> Sedona community has made great progress and grown rapidly under the
> guidance of our mentors. We believe the Sedona project has met the
> conditions for graduation. We'd like to start the discussion and collect
> feedback towards graduation. Please feel free to join the discussion.
>
> The discussion will remain open for at least 72 hours.
>
> Thanks,
> Jia
>
> ***
>
> The incubation status of Sedona can be found in [1]. The Apache Sedona
> community has a discussion thread of graduating Sedona to a TLP [2], passed
> the community vote [3]. The vote result was announced [4]. The PPMC also
> passed a vote [5] to nominate Jia as the chair of Sedona TLP, and the
> result was also announced [6]. We had a discussion about Sedona graduation
> in the incubator this September [12] and all issues have been fixed.
>
> The summary on the state of the community is listed below and the self
> assessment (Apache Project Maturity Model) is in [7].
>
>
> Sedona joined the Apache Incubator on July 19 2020. As of Dec 2 2022:
>
> ** Community **:
>
> * number of contributions (commits) since incubation: 394
> - Overall: 1083
> - 36% of the commits were added since incubation.
>
> * number of contributors (and growth since incubation): 51
> - Overall: 86
> - 59% of the contributors joined since incubation
>
> * email discussions since incubation: 1214 threads on d...@sedona.apache.org
>
> * Number of monthly downloads: grow from 200K per month to 800K per month.
>
> * Marked as critical project on PyPi as Sedona ranks among top 1% most
> downloaded Python projects on PyPi.
>
> ** Project **
>
> * releases: 7
>
> * number of release managers: 3 (Jia Yu, Paweł Kociński, Kanchan Chowdhury)
>
> * Apache Sedona website (sedona.apache.org) is compliant with ASF
> requirement [8]. The GitHub.com used in external resources are compliant
> with ASF privacy requirement [9]
>
> ** Brands ,License, and Copyright **
>
> * We submitted an application for the brand [10] and it has been
> reviewed and approved.
>
> * Apache Sedona community maintains project code on GitHub, and all
> modules
> code is under Apache 2.0 license. We have reviewed all the
> dependencies and ensured they do not bring any license issues [11]. All
> the status files, license headers, and copyright are up to date.
>
> ** PPMC members
>
> * Please see the proposed board resolution below and let us know what you
> think. The initial PMC members were passed by the vote [5] and the result
> was also announced [6].
>
> * affiliations of the current PPMC members of Sedona: 11 PPMC from 10
> different organizations
> Adam Binford: Maxar
> Kanchan Chowdhury: Arizona State University
> Paweł Kociński: GetInData
> Yitao Li: SafeGraph
> Netanel Malka: Upstream Security
> Mohame Sarwat: Wherobots Inc.
> Kengo Seki: NTT Data
> Sachio Wakai: KDDI
> Jinxuan Wu: Bloomberg LP
> Jia Yu: Wherobots Inc.
> Zongsi Zhang: Grab
>
> * new PPMC members since incubation: 5
> Adam Binford: Maxar
> Kanchan Chowdhury: Arizona State University
> Yitao Li: SafeGraph
> Sachio Wakai: KDDI
> Kengo Seki: NTT Data
>
> * Pending new PPMC members (due to pending CCLAs): 1
> Magdalena Wójciak: Billennium
>
> ** Graduation Resolution **
>
> Establish the Apache Sedona 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 big geospatial data processing engine. It provides an easy
> to use APIs for spatial data scientists to manage, wrangle, and process
> geospatial data.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Sedona Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Sedona Project be and hereby is responsible
> for the creation and maintenance of software related to a big geospatial
> data processing engine. It provides an easy to use APIs for spatial data
> scientists to manage, wrangle, and process geospatial data; and be it
> further
>
> RESOLVED, that the office of "Vice President, Apache Sedona" 

Re: [DISCUSS] Graduate NEMO to TLP

[Willem Jiang]

Please address these concerns one by one.
I think Calvin's is much easier to address.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Tue, Nov 29, 2022 at 12:47 PM Byung-Gon Chun  wrote:
>
> We have some concerns from William and Calvin.
> How should we proceed?
>
> Thanks.
> -Gon
>
> On Thu, Nov 17, 2022 at 12:45 PM Willem Jiang 
> wrote:
>
> > I just checked the contribution of the Nemo project[1] and the traffic
> > of d...@nemo.apache.org[2].
> > It looks like the project was quiet for two years.  I have a concern
> > if this project can still be active after graduation.
> >
> > I think we need to provide more evidence that the project already
> > builds up the community.
> >
> > [1]https://github.com/apache/incubator-nemo/graphs/contributors
> > [2]https://lists.apache.org/list?d...@nemo.apache.org
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Mon, Nov 14, 2022 at 6:33 PM Won Wook SONG  wrote:
> > >
> > > Hi,
> > >
> > > Do we have additional opinions or feedback on what we have to do in order
> > > to proceed to our further steps, or are we ready to go?
> > >
> > > Best,
> > > Wonook
> > >
> > >
> > > 2022년 11월 11일 (금) 오후 4:01, Byung-Gon Chun 님이 작성:
> > >
> > > > Hi,
> > > >
> > > > The Nemo codebase has been well established. It's one of Apache Beam
> > > > runners, and it can be used in Google dataproc. Its batch processing is
> > > > mature, and the community has been working on stream processing.
> > > > The current committers will be added to PMC.
> > > > I think the Nemo project should have graduated.
> > > >
> > > > Best,
> > > > Gon
> > > >
> > > >
> > > > On Wed, Nov 9, 2022 at 3:06 PM Won Wook SONG 
> > wrote:
> > > >
> > > > > Hi!
> > > > >
> > > > > Thanks for your feedback :) I've solved the issues related to our
> > > > website.
> > > > > As for the activity level, our system has initially gone over a
> > thorough
> > > > > development period at first. Now that essential features are already
> > > > > developed, we have been adding more specific features like dynamic
> > task
> > > > > offloading, hierarchical aggregation, dynamic skew detection, and
> > > > extending
> > > > > our data plane to special file systems. Such development had been
> > done in
> > > > > units of projects, and their PRs are quite large in terms of size,
> > and
> > > > > could have been reflected as an inactiveness in the Nemo project, but
> > > > this
> > > > > is actually not the case.
> > > > > I'll try to gently push our mentors for additional feedbacks.
> > > > > If you have any additional questions or concerns, please let us know!
> > > > >
> > > > > Thank you!
> > > > >
> > > > > Wonook
> > > > >
> > > > > On Nov 7, 2022, at 5:14 PM, Calvin Kirs  wrote:
> > > > >
> > > > > On Mon, Nov 7, 2022 at 4:09 PM Calvin Kirs  wrote:
> > > > >
> > > > >
> > > > > Hi,
> > > > >
> > > > > Nemo's activity level has been low for the past year or so, so I'm
> > not
> > > > > sure it's the right time to graduate, the last PPMC elected was in
> > > > > September 2021.
> > > > >
> > > > > and also there is only one mentor involved in your graduation
> > > > > discussion, and I would like to hear the thoughts of other mentors.
> > > > >
> > > > > Here are some issues that need to be addressed.
> > > > >
> > > > > The website has some issues, please refer to [1].
> > > > >
> > > > > It is not recommended to list affiliation( in [2], as it can confuse
> > > > > people.
> > > > >
> > > > > Checking google search, I can see a lot of Nemo software products,
> > I'm
> > > > > not sure if the branding issue is addressed, but I see [3]， maybe
> > it's
> > > > > fine. (I'm not familiar with Nemo).
> > > > >
> > > > > [1]: https://whimsy.apache.org/pods/project/nemo
> > > > > [2]https://nemo.apache.org/pages/team/
> > > >

Re: [VOTE] Graduate Apache Linkis(incubating) as an Apache Top Level Project

[Willem Jiang]

+1 (binding)

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Sun, Nov 27, 2022 at 6:17 PM Shuai Di  wrote:
>
> Dear Apache Incubator Community and IPMC members,
>
> After having the graduation discussion in the Linkis community [1], we
> have passed the vote within Linkis community [2] and the vote result
> was published[3].
> We then discussed the graduation for Linkis in the Apache Incubator
> Community [4], where no issues were raised and positive replies were
> received.
>
> I would like to start this voting thread to request graduating Apache
> Linkis(incubating) from Apache Incubator as a Top Level Project.
>
> Please provide your vote accordingly:
> [ ] +1 Yes, I support Linkis project to graduate from the Apache Incubator.
> [ ] +0 No opinion.
> [ ] -1 No, the Linkis project is not ready to graduate, because...
>
> Thank you for participating in the vote. This vote will stay open for at
> least 72 hours.
>
> Here is an overview of the Apache Linkis(incubating) to help with the
> vote.
>
> *Community*
>
> ● 4 new PPMC members were added, bringing the total number of PPMC
> members to 24 from 15 different organizations.
> ● 13 new committers were added(including the new PPMC members),
> bringing the total number of committers to 33 from 21 different
> organizations.
> ● 79 new contributors. The number of contributors is now 128 and growing.
> ● 21 biweekly online meetings were held in the community among PPMC
> members, committers, contributors, and users. The meeting minutes are
> recorded on the cwiki and mailing list [5].
> ● The dev@linkis mailing list currently has 113 subscribers [6].
> ● We've confirmed the VP, PMC, and Committers in the preparation
> discussion at private@linkis [7]. Shuai Di(shua...@apache.org) was
> voted as Vice President.
>
> *Project*
>
> ● Apache Linkis(incubating) builds a computation middleware layer to
> facilitate connection, governance and orchestration between the upper
> applications and the underlying data engines.
> ● Project maturity model is detailed in [8]
> ● Linkis has been incubating [9] since 2021-08-02 for over 15
> months.
> ● Linkis community released a total of 7 Apache releases [10] by 7
> different release managers from 6 different organizations.
> ● 1935 pull requests created, and 1894 pull requests closed [11].
> ● 1488 issues created, and 1271 issues closed [12].
> ● The release cadence is about 2 months, with an average of 200+
> issues and 270+ pull requests per release.
> ● Please refer to the Linkis project incubation status [13][14] for more
> information.
>
> *Brand, License, and Copyright*
>
> ● We submitted an application for the brand [15] and it has been
> reviewed and approved.
> ● Linkis community maintains project code on GitHub and all modules
> code is under Apache 2.0 license. We have reviewed all the
> dependencies and ensured they do not bring any license issues [16].
> All the status files, license headers, and copyright are up to date.
> ● Linkis official website [17] is compliant with Apache Foundation
> requirements [18].
>
> -
> BEGINNING OF DRAFT RESOLUTION
> -
>
> Establish the Apache Linkis 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 distributed and computation middleware to
> facilitate connection, governance, and orchestration between the upper
> applications and the underlying data engines.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Linkis Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Linkis Project be and hereby is responsible
> for the creation and maintenance of software related to a computation
> middleware to facilitate connection, governance and orchestration
> between the upper applications and the underlying data engines; and be
> it further
>
> RESOLVED, that the office of "Vice President, Apache Linkis" 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 Linkis
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache Linkis
> Project; and be it further
>
> RESOLVED, that the persons listed immediate

Re: [DISCUSS] Graduate NEMO to TLP

[Willem Jiang]

I just checked the contribution of the Nemo project[1] and the traffic
of d...@nemo.apache.org[2].
It looks like the project was quiet for two years.  I have a concern
if this project can still be active after graduation.

I think we need to provide more evidence that the project already
builds up the community.

[1]https://github.com/apache/incubator-nemo/graphs/contributors
[2]https://lists.apache.org/list?d...@nemo.apache.org

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Mon, Nov 14, 2022 at 6:33 PM Won Wook SONG  wrote:
>
> Hi,
>
> Do we have additional opinions or feedback on what we have to do in order
> to proceed to our further steps, or are we ready to go?
>
> Best,
> Wonook
>
>
> 2022년 11월 11일 (금) 오후 4:01, Byung-Gon Chun 님이 작성:
>
> > Hi,
> >
> > The Nemo codebase has been well established. It's one of Apache Beam
> > runners, and it can be used in Google dataproc. Its batch processing is
> > mature, and the community has been working on stream processing.
> > The current committers will be added to PMC.
> > I think the Nemo project should have graduated.
> >
> > Best,
> > Gon
> >
> >
> > On Wed, Nov 9, 2022 at 3:06 PM Won Wook SONG  wrote:
> >
> > > Hi!
> > >
> > > Thanks for your feedback :) I've solved the issues related to our
> > website.
> > > As for the activity level, our system has initially gone over a thorough
> > > development period at first. Now that essential features are already
> > > developed, we have been adding more specific features like dynamic task
> > > offloading, hierarchical aggregation, dynamic skew detection, and
> > extending
> > > our data plane to special file systems. Such development had been done in
> > > units of projects, and their PRs are quite large in terms of size, and
> > > could have been reflected as an inactiveness in the Nemo project, but
> > this
> > > is actually not the case.
> > > I'll try to gently push our mentors for additional feedbacks.
> > > If you have any additional questions or concerns, please let us know!
> > >
> > > Thank you!
> > >
> > > Wonook
> > >
> > > On Nov 7, 2022, at 5:14 PM, Calvin Kirs  wrote:
> > >
> > > On Mon, Nov 7, 2022 at 4:09 PM Calvin Kirs  wrote:
> > >
> > >
> > > Hi,
> > >
> > > Nemo's activity level has been low for the past year or so, so I'm not
> > > sure it's the right time to graduate, the last PPMC elected was in
> > > September 2021.
> > >
> > > and also there is only one mentor involved in your graduation
> > > discussion, and I would like to hear the thoughts of other mentors.
> > >
> > > Here are some issues that need to be addressed.
> > >
> > > The website has some issues, please refer to [1].
> > >
> > > It is not recommended to list affiliation( in [2], as it can confuse
> > > people.
> > >
> > > Checking google search, I can see a lot of Nemo software products, I'm
> > > not sure if the branding issue is addressed, but I see [3]， maybe it's
> > > fine. (I'm not familiar with Nemo).
> > >
> > > [1]: https://whimsy.apache.org/pods/project/nemo
> > > [2]https://nemo.apache.org/pages/team/
> > > [3]https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-139
> > >
> > >
> > > There are still some PPMCs not subscribe private@nemo.a.o.
> > >
> > >
> > > On Mon, Nov 7, 2022 at 12:39 PM Won Wook SONG  wrote:
> > >
> > >
> > > Hi all,
> > >
> > > The Apache Nemo podling has discussed[0]
> > > <https://lists.apache.org/thread/hv196tfg6jzltsjxnj28q572y6p3lvq2> and
> > > voted
> > > upon[1] <
> > https://lists.apache.org/thread/dzfq12xdwbtmsn1l527o56kh56kz31mh>
> > > graduation as a TLP. Following the incubation guide[2]
> > > <https://incubator.apache.org/guides/graduation.html>, we now ask for
> > > feedback on our graduation.
> > >
> > > Thanks to everyone who helped this project to get this far!
> > >
> > > Best,
> > > Wonook
> > >
> > > [0]: https://lists.apache.org/thread/hv196tfg6jzltsjxnj28q572y6p3lvq2
> > > [1]: https://lists.apache.org/thread/dzfq12xdwbtmsn1l527o56kh56kz31mh
> > > [2]: https://incubator.apache.org/guides/graduation.html
> > >
> > >
> > > --
> > > X. Establish the Apache Nemo Project
> > >
> >

Re: [VOTE] Graduate Kyuubi from Apache Incubator as a Top Level Project

[Willem Jiang]

As a mentor of Kyuubi, I saw the diverse community being built, and
the PPMC is running well.
Here is my +1 （binding）

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Tue, Nov 15, 2022 at 11:57 AM Kent Yao  wrote:
>
> Hello, Incubator community and IMPC-ers,
>
> Following the discussion[0], I'd like to call a vote to graduate Kyuubi from
> Apache Incubator as a Top-Level Project.
>
> Please vote accordingly:
> [ ] +1 it is ready to graduate from the Apache Incubator to a TLP.
> [ ] +0 No opinion.
> [ ] -1 it is not ready to graduate (please state reasons)
>
> Thank you for participating in the vote. This vote will stay open for at
> least 72 hours.
>
> Best Regards,
> Kent Yao
>
>
> Kyuubi has been an incubating project since 2021-06-21 after the
> proposal[1] was accepted. During the incubation, the Kyuubi project
> and community developed stably and continuously following the Apache
> Way. By sorting out and self-checking the Kyuubi maturity model[2],
> we believe that the Kyuubi project is ready for graduating as a Top
> Level Project. Meanwhile, corresponding threads for both discussions[3]
> and vote[4][5] have been finished in the kyuubi@dev mailing list with
> positive results. Please refer to the Kyuubi project incubation status[15]
> for more information.
>
> Here is a brief overview of the progress of the Apache Kyuubi(incubating)
> project and community since entering the incubator:
>
> ** Community **
>
> - 3 new PPMC members were added, bringing the total number to 12.
> The community strives to be meritocratic and diverse, the current
> PPMC(mentors excluded) consists of individuals from different 
> organizations[16],
> China Mobile(1), Ctrip(1), eBay(1), NetEase(4), and T3(1).
> - 8 new committers were added, bringing the total number to 17. The newly
> added committers(PPMC excluded) are also from different organizations,
> AsiaInfo(1), Bilibili(1), Dingxiangyuan(1), iQiYi(1), and NetEase(1).
> - 60+ new contributors participate in the community. The number of
> contributors are now 99 and still growing.
> - The dev@kyuubi mailing list currently has 89 subscribers, and all major
> project discussions happen there. The GitHub discussions page is also being
> actively used for user questions, feature requests, story sharing, etc.
> - Held 3 meetups by our community, and participated in 20+ events, such as
> ApacheCon, to promote the Kyuubi project.
> - All PPMC members are willing to join the Kyuubi PMC membership after
> graduation[6][7].
> - Kent Yao(y...@apache.org) was voted as Vice President[8].
>
> ** Project **
>
> - 8 releases[9] by 8 different release managers.
> - 1400+ pull requests merged[10], and 900+ issues resolved[11].
> - Kyuubi website[12] is now compliant with the Apache Project Website
> requirements[13].
> - Project maturity model is detailed in[2].
>
> ** Licensing and Branding Issues **
>
> - We have applied the podling name search[14] and it has been reviewed
> and approved.
> - IP Clearance: 2021-06-21
> - Software Grant Received on: 2021-07-04
> - Confirmation of ASF Copyright Headers on Source Code on: 2021-06-21
> - Confirmation of Binary Distribution Licensing: 2021-09-14
>
>
> --
> BEGINNING OF DRAFT RESOLUTION
> --
>
> Establish the Apache Kyuubi 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 distributed and multi-tenant gateway to provide serverless
> SQL on data warehouses and lakehouses.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Kyuubi Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Kyuubi Project be and hereby is responsible
> for the creation and maintenance of software related to a distributed
> and multi-tenant gateway to provide serverless SQL on data warehouses
> and lakehouses.; and be it further
>
> RESOLVED, that the office of "Vice President, Apache Kyuubi" 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 Kyuubi
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache Kyuubi
> Project; and be it further
>
> RESOLVED, that the persons listed immediately below be and hereby are
&g

Re: [VOTE] Release Apache Kyuubi(Incubating) v1.6.1-incubating rc2

[Willem Jiang]

I checked
- The checksums and signatures are validated.
- The LICENSE and NOTICE files look good to me.
- There is DISCLAIMER-WIP
- No binary files in the source release

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Fri, Nov 11, 2022 at 12:53 PM Shaoyun Chen  wrote:
>
> Hello Incubator Community,
>
> The Apache Kyuubi community has voted on and approved a proposal to release
> Apache Kyuubi(Incubating) version v1.6.1-incubating rc2.
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Kyuubi community vote thread:
> https://lists.apache.org/thread/vwyymhxy8fsxo58rwqdv42924p671xx5
>
> Vote result thread:
> https://lists.apache.org/thread/3nd69tjw9c911dsfq33c5pl9l7yt6dhm
>
> [ ] +1 Release this package as Apache Kyuubi v1.6.1-incubating
> [ ] +0
> [ ] -1 Do not release this package because ...
>
> To learn more about Apache Kyuubi (Incubating), please see
> https://kyuubi.apache.org/
>
> The tag to be voted on is v1.6.1-incubating-rc2 (commit
> 7524d817828eb61ce43c668dac7b4890fe96d339):
> https://github.com/apache/incubator-kyuubi/tree/v1.6.1-incubating-rc2
>
> The release files, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/kyuubi/v1.6.1-incubating-rc2/
>
> Signatures used for Kyuubi RCs can be found in this file:
> https://downloads.apache.org/incubator/kyuubi/KEYS
>
> The staging repository for this release can be found at:
> https://repository.apache.org/content/repositories/orgapachekyuubi-1026/
>
> The commit list since the rc1:
> https://github.com/apache/incubator-kyuubi/compare/v1.6.1-incubating-rc1...v1.6.1-incubating-rc2
>
> The release note is available in:
> https://github.com/apache/incubator-kyuubi/compare/v1.6.0-incubating...v1.6.1-incubating-rc2
>
>
> Thanks,
> On behalf of Apache Kyuubi(Incubating) community

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

Re: [VOTE] Graduate Apache bRPC to a TLP

[Willem Jiang]

+1 (binding).
Good luck!

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Fri, Nov 11, 2022 at 10:48 PM Jerry Tan  wrote:
>
> Hello, dear IPMC members,
>
> following the [DISCUSS] thread at [1],
>
> I'd like to call a vote to graduate bRPC to a TLP.
>
>
> Please vote accordingly:
>
> [ ] +1 Apache bRPC (incubating) is ready to graduate to a TLP
>
> [ ] +0 No opinion.
>
> [ ] -1 Apache bRPC (Incubating) is not ready to graduate (please state
> reasons)
>
>
> Thank you for participating in the vote!
>
>
> Best regards
>
> Jerry Tan
>
>
> ---
>
> Project Updates since 2018-11-13:
>
> ---
>
>
> 1. We release 1.0.0,1.1.0, 1.2.0, 1.3.0, 4 apache releases, and
> 0.9.6,0.9.7, 2 disclaim releases; by different release managers (including
> Jerry Tan, Jiashun Zhu, Lorin Lee, Wang Weibing, Shuai Liu, Xiguo Hu) (see
> it at [2])
>
>
> 2. We add 5 new PPMC members including Jiashun Zhu, Wang Weibing, Cai
> Daojin, He Lei, and Lorin Lee. see it at [2]. Now we have 10 PPMC members
> altogether, they are from different companies, including ByteDance (James Ge,
> He Lei), Baidu (Yao Wang, Wang Weibing), Google (Jiashun Zhu), 4Paradigm 
> (Jerry
> Tan), Shopee (Cai Daojin), Momenta.AI (Zhangyi Chen), Ant Group (Bear Jiang
> ), Freelancer (Lorin Lee).
>
>
> 3. We add 9 new committers, including Cai Daojin, He Lei, Mou Gaidong, Lorin
> Lee, Wang Wei, Shuai Liu, Wang Xiaofeng, Xiguo Hu, and Guangming Chen. see
> it at [2].
>
>
> 4. There are 17 members subscribed to the private email list and 60
> engineers subscribed to the dev mail list. The discussion on the dev mail
> list is active, including release, roadmap, committer related topics. see
> it at [3]
>
>
> 5. Branding issues have been solved and name searching has been completed.
> See it at [4]
>
>
> 6. Assessment of the maturity model is available at [5]. All answers to
> these check items are 'Yes'.
>
>
> 7. The bRPC website has passed the Apache Podling Website Checks [6].
>
>
> 8. 1000+ issues resolved[7], and 600+ pull requests merged and closed[8].
>
>
> 9. bRPC has been widely adopted outside Baidu since incubating, including
> iQiyi， Bytedance， Bilibili， Bigo， Didi， Weibo， Vivo，4padradigm， X
> iaohongshu， Ishumei， Doris， Amap， etc.
>
>
> And we plan to move on with new features and new scenarios, such as RDMA
> support has been integrated into the trunk and will be included in the next
> release, and extend bRPC with service mesh features.
>
> ---
>
> Draft resolution
>
> ---
>
> Establish the Apache bRPC 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 industrial-grade RPC framework for building reliable and
>
> high-performance services.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
>
> (PMC), to be known as the "Apache bRPC Project", be and hereby is
>
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache bRPC Project be and hereby is responsible for
>
> the creation and maintenance of software related to an industrial-grade
>
> RPC framework for building reliable and high-performance services; and
>
> be it further
>
> RESOLVED, that the office of "Vice President, Apache bRPC" 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 bRPC Project, and to
>
> have primary responsibility for management of the projects within the
>
> scope of responsibility of the Apache bRPC 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 bRPC Project:
>
> * Bear Jiang 
>
> * Cai Daojin 
>
> * He Lei 
>
> * James Ge 
>
> * Jean-Baptiste Onofré 
>
> * Jerry Tan 
>
> * Jiashun Zhu 
>
> * Juan Pan 
>
> * Lorin Lee 
>
> * Von Gosling 
>
> * Wang Weibing 
>
> * Yao Wang 
>
> * Zhangyi Chen 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that James Ge be appointed to
>
> the office of Vice President, Apache bRPC, 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
>
> disqualifi

Re: [DISCUSS] Graduate Kyuubi from Apache Incubator as Top Level Project

[Willem Jiang]

Because the mentors are still in the PMC team, as long as the PMC
members think of the community's best interest, I don't believe
NetEase can take control of the project.
Besides the PPMC, we also need to look at the committers; they can
become PMC members a few months later.


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Fri, Nov 11, 2022 at 12:45 PM Calvin Kirs  wrote:
>
> I looked at some PPMCs and it seems that some are no longer active.
> If the active PPMC is basically from NetEase, then I worry that the
> continued development of the project still depends on NetEase's
> decision, we have some such examples.
>
> On Fri, Nov 11, 2022 at 10:16 AM Kent Yao  wrote:
> >
> > Hey Calvin,
> >
> > We add three new PPMCs during incubation, and they are all not NetEase-ers.
> > And we also add eight other committers who are still actively contributing 
> > to
> > code and community, and there are only one of them from NetEase. The current
> > PPMC still seeks opportunities to invite them and other active contributors
> > and expand itself based on community-level contributions.
> >
> > > could you list the active PPMC ratio in detail?
> >
> > I'm not sure whether it is good to do detail a ratio number by organization.
> > The current Kyuubi PPMC develops the community based on individual
> > contributions. I will update the discussion if you think this is good and
> > necessary.
> >
> > Bests,
> > Kent
> >
> >
> > On 2022/11/11 01:06:30 Calvin Kirs wrote:
> > > Hi,
> > >
> > > I noticed that the ratio of PPMC from NetEase to PPMC from other
> > > companies has reached 1:1,
> > > I'm a little worried, could you list the active PPMC ratio in detail?
> > >
> > > On Thu, Nov 10, 2022 at 11:20 PM li gang  wrote:
> > > >
> > > > +1 (non-binding)
> > > > BTW,I checked by the [1],here is an issue that has not provided a  wiki
> > > > link,I think it's better to provide the wiki link.
> > > > [1]https://incubator.apache.org/clutch/kyuubi
> > > >
> > > > Kent Yao  于2022年11月7日周一 17:40写道：
> > > >
> > > > > Hello, Incubator community and IMPC-ers,
> > > > >
> > > > > Kyuubi has been an incubating project since 2021-06-21 after the
> > > > > proposal[1] was accepted. During the incubation, the Kyuubi project
> > > > > and community developed stably and continuously following the Apache
> > > > > Way. By sorting out and self-checking the Kyuubi maturity model[2],
> > > > > we believe that the Kyuubi project is ready for graduating as a Top
> > > > > Level Project. Meanwhile, corresponding threads for both 
> > > > > discussions[3]
> > > > > and vote[4][5] have been finished in the kyuubi@dev mailing list with
> > > > > positive results. Hereby, we would like to collect feedback from the
> > > > > incubator community through this discussion.
> > > > >
> > > > > Here is a brief overview of the progress of the Apache 
> > > > > Kyuubi(incubating)
> > > > > project and community since entering the incubator:
> > > > >
> > > > > ** Community **
> > > > >
> > > > > - 3 new PPMC members were added, bringing the total number to 12.
> > > > >   The community strives to be meritocratic and diverse, the current
> > > > >   PPMC(mentors excluded) consists of individuals from different
> > > > >   organizations, China Mobile(1), Ctrip(1), eBay(1), NetEase(4), and 
> > > > > T3(1).
> > > > > - 8 new committers were added, bringing the total number to 17.
> > > > >  The newly added committers(PPMC excluded) are also from
> > > > >   different organizations, AsiaInfo(1), Bilibili(1), Dingxiangyuan(1),
> > > > > iQiYi(1),
> > > > >   and NetEase(1).
> > > > > - 60+ new contributors participate in the community. The number of
> > > > > contributors are now 98 and still growing.
> > > > > - The dev@kyuubi mailing list currently has 75 subscribers, and all 
> > > > > major
> > > > > project discussions happen there. The GitHub discussions page is also 
> > > > > being
> > > > > actively used for user questions, feature requests, story sharing, 
> > > > > etc.
> > > > > - Held 3 meetups by our community, and participated in 20+ events, 
> > > > > su

Re: [DISCUSS] Graduate Apache bRPC（incubating）

[Willem Jiang]

On Wed, Nov 9, 2022 at 5:30 PM Calvin Kirs  wrote:
>
> On Wed, Nov 9, 2022 at 1:15 PM Wang Weibing  wrote:
> >
> > Thanks, Willem.
> >
> > I have update [1] and [2] adding company information about the  PPMC 
> > members and committers.
> >
> > [1] 
> > https://github.com/apache/incubator-brpc/wiki/Maturity-Assessment-for-bRPC
> > [2] https://brpc.apache.org/docs/community/committers/
> >
>
> I don't recommend listing affiliations in [2], as this will cause
> confusion for others.
>
What kind of confusion did you get？
I think we need to keep a track of the affiliations of the PMC members
to avoid a single-company situation.

> Just need to state the corresponding affiliation in [1].
>
> > Best regards
> > Weibing
> >

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

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

Re: [DISCUSS] Graduate Kyuubi from Apache Incubator as Top Level Project

[Willem Jiang]

It's pretty impressive that Kyuubi did eight releases, about one
release per two months.
As a mentor of Kyuubi, I saw the diverse community being built, and
the PPMC is running well.
Here is my +1.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Mon, Nov 7, 2022 at 5:40 PM Kent Yao  wrote:
>
> Hello, Incubator community and IMPC-ers,
>
> Kyuubi has been an incubating project since 2021-06-21 after the
> proposal[1] was accepted. During the incubation, the Kyuubi project
> and community developed stably and continuously following the Apache
> Way. By sorting out and self-checking the Kyuubi maturity model[2],
> we believe that the Kyuubi project is ready for graduating as a Top
> Level Project. Meanwhile, corresponding threads for both discussions[3]
> and vote[4][5] have been finished in the kyuubi@dev mailing list with
> positive results. Hereby, we would like to collect feedback from the
> incubator community through this discussion.
>
> Here is a brief overview of the progress of the Apache Kyuubi(incubating)
> project and community since entering the incubator:
>
> ** Community **
>
> - 3 new PPMC members were added, bringing the total number to 12.
>   The community strives to be meritocratic and diverse, the current
>   PPMC(mentors excluded) consists of individuals from different
>   organizations, China Mobile(1), Ctrip(1), eBay(1), NetEase(4), and T3(1).
> - 8 new committers were added, bringing the total number to 17.
>  The newly added committers(PPMC excluded) are also from
>   different organizations, AsiaInfo(1), Bilibili(1), Dingxiangyuan(1), 
> iQiYi(1),
>   and NetEase(1).
> - 60+ new contributors participate in the community. The number of
> contributors are now 98 and still growing.
> - The dev@kyuubi mailing list currently has 75 subscribers, and all major
> project discussions happen there. The GitHub discussions page is also being
> actively used for user questions, feature requests, story sharing, etc.
> - Held 3 meetups by our community, and participated in 20+ events, such as
> ApacheCon, to promote the Kyuubi project.
> - All PPMC members are willing to join the Kyuubi PMC membership after
>  graduation[6][7].
> - Kent Yao(y...@apache.org) was voted as Vice President[8].
>
> ** Project **
>
> - 8 releases[9] by 8 different release managers.
> - 1400+ pull requests merged[10], and 900+ issues resolved[11].
> - Kyuubi website[12] is now compliant with the Apache Project Website
> requirements[13].
> - Project maturity model is detailed in[2].
>
> ** Licensing and Branding Issues **
>
> - We have applied the podling name search[14] and it has been reviewed
> and approved.
> - IP Clearance: 2021-06-21
> - Software Grant Received on: 2021-07-04
> - Confirmation of ASF Copyright Headers on Source Code on: 2021-06-21
> - Confirmation of Binary Distribution Licensing: 2021-09-14
>
>
> -
> BEGINNING OF DRAFT RESOLUTION
> -
>
> Establish the Apache Kyuubi 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 distributed and multi-tenant gateway to provide serverless
> SQL on data warehouses and lakehouses.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Kyuubi Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Kyuubi Project be and hereby is responsible
> for the creation and maintenance of software related to a distributed
> and multi-tenant gateway to provide serverless SQL on data warehouses
> and lakehouses.; and be it further
>
> RESOLVED, that the office of "Vice President, Apache Kyuubi" 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 Kyuubi
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache Kyuubi
> 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 Kyuubi Project:
>
> * Akira Ajisaka 
> * Cheng Pan 
> * Dongdong Hong 
> * Duo Zhang 
> * Fei Wang 
> * Hongxiang Jiang 
> * Jeff Zhang 
> * Kent Yao 
> * Shaoyun Chen 
> * Vino Yang 
> * Willem Ning Jiang 
> * XiDuo You 
>
> NOW, THEREFOR

Re: [DISCUSS] Graduate Apache bRPC（incubating）

[Willem Jiang]

Hi Weibing，

Thanks for the update. It looks good to me now :)

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Wed, Nov 9, 2022 at 1:15 PM Wang Weibing  wrote:
>
> Thanks, Willem.
>
> I have update [1] and [2] adding company information about the  PPMC members 
> and committers.
>
> [1] https://github.com/apache/incubator-brpc/wiki/Maturity-Assessment-for-bRPC
> [2] https://brpc.apache.org/docs/community/committers/
>
> Best regards
> Weibing
>
> On 2022/11/09 03:59:05 Willem Jiang wrote:
> > I checked the Independency section of the Maturity Assessment for
> > bRPC[1] with the website page[2].
> > It's hard to tell the contribution if the Affiliation is Apache.
> > Could you update the information about these PPMC members and committers?
> >
> > [1]https://github.com/apache/incubator-brpc/wiki/Maturity-Assessment-for-bRPC
> > [2]https://brpc.apache.org/docs/community/committers/
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Wed, Nov 9, 2022 at 8:28 AM Jerry Tan  wrote:
> > >
> > > It looks like there is no issue with this,
> > > I will keep discussing it for 3 days,  and start to vote the next day.
> > >
> > > thanks.
> > >
> > >
> > > On 2022/11/06 16:46:28 Jerry Tan wrote:
> > > > Hi， Dear IPMC members，
> > > >
> > > >
> > > > Apache bRPC has been incubating since 2018-11-13.
> > > >
> > > > Within this time, the bRPC community has made great progress,
> > > >
> > > > has adopted the Apache way and grown with the help of our mentors.
> > > >
> > > > The bRPC community believes that we have met the conditions for 
> > > > graduation
> > > >
> > > > and have discussed [1] and voted [2] for graduation with the result at 
> > > > [3].
> > > >
> > > >
> > > > So, we'd like to start the discussion and would appreciate any feedback
> > > > toward graduation!
> > > >
> > > > We are happy to answer any questions - below are some facts and project
> > > > highlights from the incubation phase as well as the draft resolution.
> > > >
> > > >
> > > > This is also an excellent opportunity to say a big thank you to our 
> > > > mentors.
> > > >
> > > >
> > > > I really appreciated the prompt help at any time during incubation for 
> > > > the
> > > > many questions we had. Thanks a lot, Von, JB and PanJuan!
> > > >
> > > >
> > > > Cheers
> > > >
> > > > Jerry Tan
> > > >
> > > >
> > > > ---
> > > >
> > > > Project Updates since incubation:
> > > >
> > > > ---
> > > >
> > > >
> > > > 1. We release 1.0.0,1.1.0, 1.2.0, 1.3.0, 4 apache releases, and 0.9.6,
> > > > 0.9.7, 2 disclaim releases; by
> > > >
> > > > different release managers (including Jerry Tan, Zhu Jiashun, Lorin Lee,
> > > >
> > > > Wang Weibing, Liu Shuai, Hu Xiguo) (see it at [4])
> > > >
> > > >
> > > > 2. We add 5 new PPMC members including Jiashun Zhu, Wang Weibing, Cai
> > > >
> > > > Daojin, He Lei, and Lorin Lee. see it at [4]. Now we have 10 PPMC 
> > > > members
> > > > altogether, they are from different companies,
> > > >
> > > > Including ByteDance(Ge Jun, He Lei), Baidu(Wang Yao, Wang
> > > > Weibing),Google(Zhu Jiashun), 4Paradigm(Tan Zhongyi), Shopee( Cai 
> > > > Daojin),
> > > > Momenta.AI (Chen Zhangyi), Ant Group(Jiang Rujie),Lorin Lee(Freelancer)
> > > >
> > > >
> > > > 3. We add 9 new committers, including Cai Daojin, He Lei, Mou Guiding,
> > > >
> > > > Lorin Lee, Wang Wei, Liu Shuai, Wang Xiaofeng, and Xiguo Hu. Chen
> > > >
> > > > Guangming. see it at [4]
> > > >
> > > >
> > > > 4. We have 17 members subscribed to the private email list and 61 
> > > > engineers
> > > >
> > > > subscribed to the dev mail list. The discussion on the dev mail list is
> > > > active, including release, roadmap,
> > > >
> > > > committer related topics. see it at [5]
> > > >
> > > >
> > > > 5. Branding issues have been solved and name searching has 

Re: [DISCUSS] Graduate Apache bRPC（incubating）

[Willem Jiang]

I checked the Independency section of the Maturity Assessment for
bRPC[1] with the website page[2].
It's hard to tell the contribution if the Affiliation is Apache.
Could you update the information about these PPMC members and committers?

[1]https://github.com/apache/incubator-brpc/wiki/Maturity-Assessment-for-bRPC
[2]https://brpc.apache.org/docs/community/committers/

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Wed, Nov 9, 2022 at 8:28 AM Jerry Tan  wrote:
>
> It looks like there is no issue with this,
> I will keep discussing it for 3 days,  and start to vote the next day.
>
> thanks.
>
>
> On 2022/11/06 16:46:28 Jerry Tan wrote:
> > Hi， Dear IPMC members，
> >
> >
> > Apache bRPC has been incubating since 2018-11-13.
> >
> > Within this time, the bRPC community has made great progress,
> >
> > has adopted the Apache way and grown with the help of our mentors.
> >
> > The bRPC community believes that we have met the conditions for graduation
> >
> > and have discussed [1] and voted [2] for graduation with the result at [3].
> >
> >
> > So, we'd like to start the discussion and would appreciate any feedback
> > toward graduation!
> >
> > We are happy to answer any questions - below are some facts and project
> > highlights from the incubation phase as well as the draft resolution.
> >
> >
> > This is also an excellent opportunity to say a big thank you to our mentors.
> >
> >
> > I really appreciated the prompt help at any time during incubation for the
> > many questions we had. Thanks a lot, Von, JB and PanJuan!
> >
> >
> > Cheers
> >
> > Jerry Tan
> >
> >
> > ---
> >
> > Project Updates since incubation:
> >
> > ---
> >
> >
> > 1. We release 1.0.0,1.1.0, 1.2.0, 1.3.0, 4 apache releases, and 0.9.6,
> > 0.9.7, 2 disclaim releases; by
> >
> > different release managers (including Jerry Tan, Zhu Jiashun, Lorin Lee,
> >
> > Wang Weibing, Liu Shuai, Hu Xiguo) (see it at [4])
> >
> >
> > 2. We add 5 new PPMC members including Jiashun Zhu, Wang Weibing, Cai
> >
> > Daojin, He Lei, and Lorin Lee. see it at [4]. Now we have 10 PPMC members
> > altogether, they are from different companies,
> >
> > Including ByteDance(Ge Jun, He Lei), Baidu(Wang Yao, Wang
> > Weibing),Google(Zhu Jiashun), 4Paradigm(Tan Zhongyi), Shopee( Cai Daojin),
> > Momenta.AI (Chen Zhangyi), Ant Group(Jiang Rujie),Lorin Lee(Freelancer)
> >
> >
> > 3. We add 9 new committers, including Cai Daojin, He Lei, Mou Guiding,
> >
> > Lorin Lee, Wang Wei, Liu Shuai, Wang Xiaofeng, and Xiguo Hu. Chen
> >
> > Guangming. see it at [4]
> >
> >
> > 4. We have 17 members subscribed to the private email list and 61 engineers
> >
> > subscribed to the dev mail list. The discussion on the dev mail list is
> > active, including release, roadmap,
> >
> > committer related topics. see it at [5]
> >
> >
> > 5. Branding issues have been solved and name searching has been completed.
> > See it at [6]
> >
> >
> > 6. Assessment of the maturity model is available at [7]
> >
> > All answers to these check items are 'Yes'.
> >
> >
> > 7. brpc has been widely adopted outside Baidu since incubating, including
> > iqiyi，bytedance，bilibili，Bigo，Didi，weibo，vivo，4padradigm，xiaohongshu，ishumei，doris，amap，etc.
> > And we plan to move on, such as RDMA support has been integrated into the
> > trunk and will be included in the next release, and extend brpc with
> > service mesh features.
> >
> >
> > Let me express a big ***THANK YOU*** to everyone for helping make this
> >
> > possible!
> >
> > ---
> >
> > Draft resolution
> >
> > ---
> >
> > Establish the Apache brpc 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 industrial-grade RPC framework for building reliable and
> >
> > high-performance services.
> >
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> >
> > (PMC), to be known as the "Apache brpc Project", be and hereby is
> >
> > established pursuant to 

Re: [VOTE] Graduate Apache StreamPieps to a TLP

[Willem Jiang]

+1 (binding)

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Mon, Nov 7, 2022 at 5:32 AM Dominik Riemer  wrote:
>
> Hi everyone,
>
> following the [DISCUSS] thread at [0], I'd like to call a vote to graduate 
> StreamPipes to a TLP.
>
> Please vote accordingly:
>
> [ ] +1 Apache StreamPipes (incubating) is ready to graduate from the
> Apache Incubator to a TLP.
>
> [ ] +0 No opinion.
>
> [ ] -1 Apache StreamPipes (Incubating) is not ready to graduate (please state 
> reasons)
>
> Thank you for participating in the vote!
>
> Cheers
> Dominik
>
>
> ---
> Project highlights
> ---
>
> * Incubating since 2019-11-11
> * 5 releases (0.66.0, 0.67.0, 0.68.0, 0.69.0, 0.70.0)
> * 3 different release managers
> * 13 PPMC members (almost all from different organizations), including 5 
> mentors
> * 8 additional committers
> * active community with all discussions happening on the mailing list and 
> dedicated user mailing list as support channel
> * community building & talks at ACNA19, 20, 21, 22 + Asia, SF Big Data 
> Analytics and many other webinars
> * over 9.000 commits
> * 52 subscribers on the dev list, 57 subscribers on the users list
> * Articles about StreamPipes in the US Linux Magazine [4], and StreamPipes 
> was named one of the
> top 5 open source tools for IoT Analytics by OpenSourceForU [5]
> * Number of Github stars has increased to currently 350
> * Website [6], extensive documentation [7] and a developer wiki [8]
> * Strong connection and integration with other projects in the Apache IoT 
> space (e.g., PLC4X)
> * Completed maturity self-assessment [9]
>
>
> ---
> Draft resolution
> ---
>
> Establish the Apache StreamPipes Project
>
> WHEREAS, the Board of Directors deems it to be in the best interests of
> the Foundation and consistent with the Foundation's purpose to establish
> a Project Management Committee charged with the creation and maintenance
> of open-source software, for distribution at no charge to the public,
> related to a self-service Industrial IoT toolbox which enables
> non-technical users to connect, analyze and explore IoT
> data streams.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache StreamPipes Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache StreamPipes Project be and hereby is
> responsible for the creation and maintenance of software related to a
> self-service Industrial IoT toolbox which enables non-technical users to
> connect, analyze and explore IoT data streams; and be it
> further
>
> RESOLVED, that the office of "Vice President, Apache StreamPipes" be and
> hereby is created, the person holding such office to serve at the
> direction of the Board of Directors as the chair of the Apache
> StreamPipes Project, and to have primary responsibility for management
> of the projects within the scope of responsibility of the Apache
> StreamPipes Project; and be it further
>
> RESOLVED, that the persons listed immediately below be and hereby are
> appointed to serve as the initial members of the Apache StreamPipes
> Project:
>
> * Christofer Dutz 
> * Dominik Riemer 
> * Grainier Perera 
> * Jean-Baptiste Onofré 
> * Johannes Tex 
> * Julian Feinauer 
> * Justin Mclean 
> * Kenneth Knowles 
> * Marco Heyden 
> * Patrick Wiener 
> * Philipp Zehnder 
> * Stefan Obermeier 
> * Tim Bossenmaier 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Philipp Zehnder be
> appointed to the office of Vice President, Apache StreamPipes, to serve
> in accordance with and subject to the direction of the Board of
> Directors and the Bylaws of the Foundation until death, resignation,
> retirement, removal or disqualification, or until a successor is
> appointed; and be it further
>
> RESOLVED, that the Apache StreamPipes Project be and hereby is tasked
> with the migration and rationalization of the Apache Incubator
> StreamPipes podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> StreamPipes podling encumbered upon the Apache Incubator PMC are
> hereafter discharged.
>
> ---
>
> [0] https://lists.apache.org/thread/dg3z175h2szcg3wgz9tmq770krvscvp8
>
> [1] https://lists.apache.org/thread/18vgpw0jq93rwh9mj9bb27nj7gjhmldg
>
> [2] https://lists.apache.org/thread/q6n11kfmmj1vgo6vq19nq1km5p1vow28
>
> [3] https://lists.apache.org/thread/5ybqmx8z768ksdymz2h2gjsx91p1drpp
>
> [4] https://www.linux-magazine.com/Issues/2021/244/Apache-StreamPipes
>
> [5] 
> htt

Re: Re: [VOTE] Graduate Apache NuttX to TLP

[Willem Jiang]

As the trademark concern is addressed, I'd be happy to change my vote to +1.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Wed, Nov 9, 2022 at 2:00 AM Mark Thomas  wrote:
>
> I have reviewed the current trademark status and I am happy to proceed
> on the basis that the transfer will be started after graduation.
>
> Mark
>
> Mark Thomas
> VP, Brand Management
>
> On 2022/11/07 13:13:03 Willem Jiang wrote:
> > Sorry, I need to change my vote to -1.
> > I just discovered a brand issue we need to address before graduation.
> > It looks like the trademark of Nuttx[1] is still not transferred to ASF.
> > We need the trademark VP approval before starting the vote.
> > [1] https://nuttx.apache.org/docs/latest/introduction/trademarks.html
> >
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Mon, Nov 7, 2022 at 9:03 PM Willem Jiang  wrote:
> > >
> > > +1 （binding）
> > >
> > > Willem Jiang
> > >
> > > Twitter: willemjiang
> > > Weibo: 姜宁willem
> > >
> > > On Sat, Nov 5, 2022 at 12:07 AM Nathan Hartman  
> > > wrote:
> > > >
> > > > Dear Apache Incubator Community,
> > > >
> > > > I would like to call a VOTE to graduate Apache NuttX from the
> > > > Incubator to the status of Top-Level-Project (TLP).
> > > >
> > > > The NuttX PPMC has held a community vote to graduate [1] and the vote
> > > > passed [2]. Following a community discussion [3] to draft our
> > > > resolution (see below) and secure a volunteer for Vice President of
> > > > Apache NuttX, and the gentle nudges we've been getting from our
> > > > mentors and the Incubator community to take this important step,
> > > >
> > > > I am pleased to call this VOTE:
> > > >
> > > > [ ] +1 Yes, Apache NuttX (Incubating) is ready to graduate from the
> > > > Apache Incubator to the status of Top Level Project.
> > > >
> > > > [ ] +0 No opinion.
> > > >
> > > > [ ] -1 No, Apache NuttX (Incubating) is NOT ready to graduate (please
> > > > state reason(s)).
> > > >
> > > > This vote will remain open for at least 72 hours.
> > > >
> > > > Some project highlights since incubation:
> > > > * Incubating for over 1000 days (since 2019-12-09)
> > > > * Website migrated to nuttx.apache.org
> > > > * Shipped 9 releases under the ASF Incubator
> > > > * Merged 8000 PRs across incubator-nuttx and incubator-nuttx-apps
> > > > * More than 1000 stars on GitHub
> > > > * More than 500 forks on GitHub
> > > > * More than 250 subscribers to d...@nuttx.apache.org
> > > > * In Top 10 Apache projects of 2021 by number of commits [4]
> > > > * 5 mentors
> > > > * 18 PPMC members
> > > > * 26 committers
> > > > * 75 ICLAs
> > > > * 2 CCLAs
> > > > * 21 SGAs
> > > > * 2 release managers
> > > > * 3 NuttX online workshops
> > > > * And much, much more
> > > >
> > > > Resolution:
> > > >
> > > > [[[
> > > >
> > > > Establish the Apache NuttX 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 mature, real-time embedded operating system
> > > > (RTOS).
> > > >
> > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > > > (PMC), to be known as the "Apache NuttX Project", be and hereby is
> > > > established pursuant to Bylaws of the Foundation; and be it further
> > > >
> > > > RESOLVED, that the Apache NuttX Project be and hereby is responsible
> > > > for the creation and maintenance of software related to a mature, real-
> > > > time embedded operating system (RTOS); and be it further
> > > >
> > > > RESOLVED, that the office of "Vice President, Apache NuttX" 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 NuttX
> &g

Re: [VOTE] Graduate Apache NuttX to TLP

[Willem Jiang]

It may take some time for the trademark transfer process.
We can keep voting once we get the approval of the trademark VP.
I can see a discussion[1] about the trademark transfer in the
trademarks mailing list.

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

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Tue, Nov 8, 2022 at 12:34 AM Gregory Nutt  wrote:
>
> > Sorry, I need to change my vote to -1.
> > I just discovered a brand issue we need to address before graduation.
> > It looks like the trademark of Nuttx[1] is still not transferred to ASF.
> > We need the trademark VP approval before starting the vote.
> > [1] https://nuttx.apache.org/docs/latest/introduction/trademarks.html
> >
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
>
> We can do that, but I do not know the process.  Some legal help will be 
> needed.  The procedure is here: 
> https://www.uspto.gov/trademarks/trademark-assignments-change-search-ownership
>
> - There is a government fee of $40 
> (https://www.uspto.gov/learning-and-resources/fees-and-payment/uspto-fee-schedule#Trademark%20Fees,
>  fee code 8521).
> - We need to file a new trademark ownership assignment.  I think this can be 
> done electronically: https://etas.uspto.gov/
>
> It would be good to have some assistance from a knowledgeable person in the 
> ASF.
>
> Gregory Nutt
>
>
>

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

Re: [VOTE] Graduate Apache NuttX to TLP

[Willem Jiang]

Sorry, I need to change my vote to -1.
I just discovered a brand issue we need to address before graduation.
It looks like the trademark of Nuttx[1] is still not transferred to ASF.
We need the trademark VP approval before starting the vote.
[1] https://nuttx.apache.org/docs/latest/introduction/trademarks.html


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Mon, Nov 7, 2022 at 9:03 PM Willem Jiang  wrote:
>
> +1 （binding）
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Sat, Nov 5, 2022 at 12:07 AM Nathan Hartman  
> wrote:
> >
> > Dear Apache Incubator Community,
> >
> > I would like to call a VOTE to graduate Apache NuttX from the
> > Incubator to the status of Top-Level-Project (TLP).
> >
> > The NuttX PPMC has held a community vote to graduate [1] and the vote
> > passed [2]. Following a community discussion [3] to draft our
> > resolution (see below) and secure a volunteer for Vice President of
> > Apache NuttX, and the gentle nudges we've been getting from our
> > mentors and the Incubator community to take this important step,
> >
> > I am pleased to call this VOTE:
> >
> > [ ] +1 Yes, Apache NuttX (Incubating) is ready to graduate from the
> > Apache Incubator to the status of Top Level Project.
> >
> > [ ] +0 No opinion.
> >
> > [ ] -1 No, Apache NuttX (Incubating) is NOT ready to graduate (please
> > state reason(s)).
> >
> > This vote will remain open for at least 72 hours.
> >
> > Some project highlights since incubation:
> > * Incubating for over 1000 days (since 2019-12-09)
> > * Website migrated to nuttx.apache.org
> > * Shipped 9 releases under the ASF Incubator
> > * Merged 8000 PRs across incubator-nuttx and incubator-nuttx-apps
> > * More than 1000 stars on GitHub
> > * More than 500 forks on GitHub
> > * More than 250 subscribers to d...@nuttx.apache.org
> > * In Top 10 Apache projects of 2021 by number of commits [4]
> > * 5 mentors
> > * 18 PPMC members
> > * 26 committers
> > * 75 ICLAs
> > * 2 CCLAs
> > * 21 SGAs
> > * 2 release managers
> > * 3 NuttX online workshops
> > * And much, much more
> >
> > Resolution:
> >
> > [[[
> >
> > Establish the Apache NuttX 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 mature, real-time embedded operating system
> > (RTOS).
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > (PMC), to be known as the "Apache NuttX Project", be and hereby is
> > established pursuant to Bylaws of the Foundation; and be it further
> >
> > RESOLVED, that the Apache NuttX Project be and hereby is responsible
> > for the creation and maintenance of software related to a mature, real-
> > time embedded operating system (RTOS); and be it further
> >
> > RESOLVED, that the office of "Vice President, Apache NuttX" 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 NuttX
> > Project, and to have primary responsibility for management of the
> > projects within the scope of responsibility of the Apache NuttX
> > 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 NuttX Project:
> >
> >  * Abdelatif Guettouche   
> >  * Alan Carvalho de Assis 
> >  * Alin Jerpelea  
> >  * Anthony Merlino
> >  * Brennan Ashton 
> >  * David Sidrane  
> >  * Duo Zhang  
> >  * Flavio Paiva Junqueira 
> >  * Gregory Nutt   
> >  * Gustavo Henrique Nihei 
> >  * Junping Du 
> >  * Justin Mclean  
> >  * Lup Yuen Lee   
> >  * Masayuki Ishikawa  
> >  * Mohammad Asif Siddiqui 
> >  * Nathan Hartman 
> >  * Sara Monteiro  
> >  * Xiang Xiao 
> >
> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Alin Jerpelea be
> > appointed to the office of Vice President, Apache NuttX, to serve in
> > accordance with and subject to the direction of the Board of Directors
> > and the Bylaws of the Foundation until death, resignatio