Re: [MENTORS] May report timeline - reports due May 2024
HI, As Sdap has just graduated, it doesn’t need to report. Kind Regards, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[MENTORS] May report timeline - reports due May 2024
Dates for next board report: Wed May 01 - Podling reports due by end of day Sun May 05 - Shepherd reviews due by end of day Sun May 05 - Summary due by end of day Tue May 07 - Mentor signoff due by end of day Wed May 08 - Report submitted to Board Wed May 15 - Board meeting Expected to report this month are: - amoro - annotator - answer - devlake - fury - graphar - hertzbeat - horaedb - liminal - nlpcraft - ponymail - sdap - seata - stormcrawler - streampark - teaclave - toree - training - xtable Reports as usual can be submitted here [1] Thanks, Justin 1. https://s.apache.org/incubator-report 1. https://cwiki.apache.org/confluence/display/INCUBATOR/Report 1. https://cwiki.apache.org/confluence/display/INCUBATOR/May2024 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache ResilientDB, Incubating, v1.10.0-RC1
+ general channel. On Wed, Apr 17, 2024 at 11:03 AM Thamir Qadah wrote: > Dear Junchao, > > I just checked the release notes for this RC. If I remember correctly, PoE > was published in EDBT 2021, not 2011, as mentioned in the change log. > > Best > > Thamir > > > On Wed, Apr 17, 2024 at 3:38 PM Junchao Chen wrote: > > > Hello, > > > > This is a call for vote to release Apache ResilientDB(Incubating) version > > v1.10.0-RC1. > > > > The release candidates: > > > > > https://dist.apache.org/repos/dist/dev//incubator/resilientdb/resilientdb/v1.10.0-rc1 > > > > Release notes: > > > > > https://github.com/apache/incubator-resilientdb/blob/master/CHANGELOG.md#resielientdb-v1100-2024-4-16 > > > > > > Git tag for the release: > > https://github.com/apache/incubator-resilientdb/tree/v1.10.0-rc01 > > > > Keys to verify the Release Candidate: > > https://dist.apache.org/repos/dist/dev//incubator/resilientdb/KEYS > > > > The vote will be open for at least 72 hours or until the necessary number > > of votes are reached. > > > > Please vote accordingly: > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove with the reason > > > > 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 repo. > > [ ] All files have license headers if necessary. > > [ ] No unlicensed compiled archives bundled in the source archive. > > > > To compile from the source, please refer to: > > > > > https://github.com/apache/incubator-resilientdb/tree/v1.10.0-rc01?tab=readme-ov-file#build-and-deploy-resilientdb > > > > > > > > Thanks, > > Junchao > > >
Re: [ANNOUNCE] Apache Answer(Incubating) v1.3.0 available
On Wed, 17 Apr 2024 at 16:40, LinkinStar wrote: > > Hello everyone, > > The Apache Answer(Incubating) v1.3.0 has been released! > > Apache Answer is a Q platform software for teams at any scale. > Whether it's a community forum, help center, or knowledge management > platform, you can always count on Apache Answer. > > Download Links: https://downloads.apache.org/incubator/answer/ Sorry, but that is not a valid download page. > Release Notes: > https://github.com/apache/incubator-answer/releases/tag/v1.3.0 > > Website: https://answer.apache.org/ > > Resources: > - Issue: https://github.com/apache/incubator-answer/issues > - Mailing list: d...@answer.apache.org > > Best regards, > LinkinStar - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[ANNOUNCE] Apache Answer(Incubating) v1.3.0 available
Hello everyone, The Apache Answer(Incubating) v1.3.0 has been released! Apache Answer is a Q platform software for teams at any scale. Whether it's a community forum, help center, or knowledge management platform, you can always count on Apache Answer. Download Links: https://downloads.apache.org/incubator/answer/ Release Notes: https://github.com/apache/incubator-answer/releases/tag/v1.3.0 Website: https://answer.apache.org/ Resources: - Issue: https://github.com/apache/incubator-answer/issues - Mailing list: d...@answer.apache.org Best regards, LinkinStar
Re: Questions about a new project entering Apache Incubator
Hi rat O, Sorry for slowly response, We will clean the non-english language in the codes later. Best Wishes. Tom rat O 于2024年4月17日周三 17:48写道： > > > For projects in incubation, is it no longer necessary for the project > name to have the "incubator-" prefix as it used to be? > > Thanks to the Apache members for responding. It make me know that this > issue is being looked into. > > > 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? > > I would also like to receive a response from Apache regarding this issue > of a significant amount of non-English language in codes. > > > From: tison > Sent: Wednesday, April 17, 2024 5:16 PM > To: general@incubator.apache.org > Subject: Re: Questions about a new project entering Apache Incubator > > And [1] is actually update the community docs without INFRA changes. > Previously (and now?), foo.incubator.apache.org has the same content with > foo.apache.org unless you explicitly ask INFRA to change. > > Like even > https://flink.incubator.apache.org/. > > I guess the main "pain point" is whimsy Web check checks " > foo.incubator.apache.org" in config in some file on SVN before, and thus > cause the Web check having a red mark. > > Best, > tison. > > > tison 于2024年4月17日 周三17:02写道： > > > I vote in [1] since it's how we practice for quite a while and it's a > > clear consensus by the vote. > > > > All the repo of podlings have incubator- prefix, I don't see a motivation > > to change. > > > > In [2] it says: > > > > > make less work for Infra > > > > I wonder if INFRA complained for this process. And what is the associated > > JIRA ticket in INFRA to do the rename. I'd like to take INFRA's opinion > > into consideration. > > > > In my previous experience, keep the name "foo", let INFRA move the repo, > > rename it to "incubator-foo", and drop the prefix on graduation. In this > > way, the link "apache/foo" will always work with GH redirections. > > > > To John: > > > > > , it can be confusing that they do. > > > > What is the certain redirection causing your confusion? > > > > Best, > > tison. > > > > [1] > > https://lists.apache.org/thread/n18gkb23bp005gb176jnwo2nrxty3z84 > > [2] > > https://github.com/apache/amoro/issues/2700 > > > > > > Sheng Wu 于2024年4月17日 周三12:09写道： > > > >> This is not to get the conclusion, and it is not clear, and many other > >> project repositories are with this prefix. > >> > >> > >> > https://incubator.apache.org/guides/transferring.html#first_steps_outside_the_incubator > >> (tison > >> found) > >> > >> Graduation doc is there indicating incaubtor- prefix is expected. This > is > >> just a 10s operation on GitHub admin page, not a heavy work. Graduation > is > >> not happening every day, even not every month. Developer don't have to > >> change remote git, as that redirect forward is supported too. > >> > >> More importantly, I don't agree this is clear without prefix. > >> > >> This us serious change, if you inist this is clear, start a vote. A lot > of > >> ppl in this context don't agree too. > >> > >> Sheng Wu 吴晟 > >> > >> Apache SkyWalking > >> Twitter, wusheng1108 > >> > >> > >> Justin Mclean 于2024年4月17日 周三11:59写道： > >> > >> > Hi, > >> > > >> > Both of these projects are new and just getting set up. I'd give them > a > >> > little time to do that. Infra in recent years have asked to minimise > >> work > >> > for them on graduation. We recently dropped the requirement for having > >> > incubating in podling domain names so I don't see it's needed in repo > >> names > >> > as long as it clear the project is an incubating project. > >> > Kind Regards, > >> > Justin > >> > > >> > > >> > On Wed, 17 Apr 2024, 1:47 pm Willem Jiang, > >> wrote: > >> > > >> > > 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. > >> > > > > >> > > >
[RESULT][VOTE] Release Apache Answer(Incubating) v1.3.0-RC1
Hello Incubator PMC and Community, The vote to release Apache Answer(Incubating) v1.3.0-RC1 has passed with 3 +1 binding and 2 +1 non-binding votes, no +0 or -1 votes. 3 (+1 binding) Xuanwo Willem Jiang Charles Zhang 2 (+1 non-binding) Feng Dong Suyan no further 0 or -1 votes. The vote thread: https://lists.apache.org/thread/lh3nvmr0gr1qh869zg76q6gcjj4ll3w0 Thanks for reviewing and voting for our release candidate. We will proceed with publishing the approved artifacts and sending out the announcement soon. Thanks, LinkinStar
Re: [REMINDER] The Apache Answer project has been waiting for votes for quite some time now
Hi, Yes, I sent it at 17:26+08:00. There seems to be a bit of a delay in the mail today. Charles Zhang has helped us with the vote. Thanks. Best regards, LinkinStar On Wed, Apr 17, 2024 at 7:00 PM tison wrote: > This seems to be a delayed email? I saw it arrived at 18:56+08:00, but the > RESULT email concluded about half an hour ago. > > Best, > tison. > > > LinkinStar 于2024年4月17日周三 18:56写道： > > > Hello, > > > > The Apache Answer project has been waiting for votes way too long … would > > be great, if at least one IPMC member could spare a bit of time to > provide > > the missing third vote. > > > > https://lists.apache.org/thread/lh3nvmr0gr1qh869zg76q6gcjj4ll3w0 > > > > Best regards, > > LinkinStar > > >
Re: [REMINDER] The Apache Answer project has been waiting for votes for quite some time now
This seems to be a delayed email? I saw it arrived at 18:56+08:00, but the RESULT email concluded about half an hour ago. Best, tison. LinkinStar 于2024年4月17日周三 18:56写道： > Hello, > > The Apache Answer project has been waiting for votes way too long … would > be great, if at least one IPMC member could spare a bit of time to provide > the missing third vote. > > https://lists.apache.org/thread/lh3nvmr0gr1qh869zg76q6gcjj4ll3w0 > > Best regards, > LinkinStar >
Re: Questions about a new project entering Apache Incubator
And [1] is actually update the community docs without INFRA changes. Previously (and now?), foo.incubator.apache.org has the same content with foo.apache.org unless you explicitly ask INFRA to change. Like even https://flink.incubator.apache.org/. I guess the main "pain point" is whimsy Web check checks " foo.incubator.apache.org" in config in some file on SVN before, and thus cause the Web check having a red mark. Best, tison. tison 于2024年4月17日 周三17:02写道： > I vote in [1] since it's how we practice for quite a while and it's a > clear consensus by the vote. > > All the repo of podlings have incubator- prefix, I don't see a motivation > to change. > > In [2] it says: > > > make less work for Infra > > I wonder if INFRA complained for this process. And what is the associated > JIRA ticket in INFRA to do the rename. I'd like to take INFRA's opinion > into consideration. > > In my previous experience, keep the name "foo", let INFRA move the repo, > rename it to "incubator-foo", and drop the prefix on graduation. In this > way, the link "apache/foo" will always work with GH redirections. > > To John: > > > , it can be confusing that they do. > > What is the certain redirection causing your confusion? > > Best, > tison. > > [1] > https://lists.apache.org/thread/n18gkb23bp005gb176jnwo2nrxty3z84 > [2] > https://github.com/apache/amoro/issues/2700 > > > Sheng Wu 于2024年4月17日 周三12:09写道： > >> This is not to get the conclusion, and it is not clear, and many other >> project repositories are with this prefix. >> >> >> https://incubator.apache.org/guides/transferring.html#first_steps_outside_the_incubator >> (tison >> found) >> >> Graduation doc is there indicating incaubtor- prefix is expected. This is >> just a 10s operation on GitHub admin page, not a heavy work. Graduation is >> not happening every day, even not every month. Developer don't have to >> change remote git, as that redirect forward is supported too. >> >> More importantly, I don't agree this is clear without prefix. >> >> This us serious change, if you inist this is clear, start a vote. A lot of >> ppl in this context don't agree too. >> >> Sheng Wu 吴晟 >> >> Apache SkyWalking >> Twitter, wusheng1108 >> >> >> Justin Mclean 于2024年4月17日 周三11:59写道： >> >> > Hi, >> > >> > Both of these projects are new and just getting set up. I'd give them a >> > little time to do that. Infra in recent years have asked to minimise >> work >> > for them on graduation. We recently dropped the requirement for having >> > incubating in podling domain names so I don't see it's needed in repo >> names >> > as long as it clear the project is an incubating project. >> > Kind Regards, >> > Justin >> > >> > >> > On Wed, 17 Apr 2024, 1:47 pm Willem Jiang, >> wrote: >> > >> > > 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 < >> wu.sheng.841...@gmail.com> >> > > 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 吴晟 >> > > > >
Re: Questions about a new project entering Apache Incubator
> For projects in incubation, is it no longer necessary for the project name to > have the "incubator-" prefix as it used to be? Thanks to the Apache members for responding. It make me know that this issue is being looked into. > 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? I would also like to receive a response from Apache regarding this issue of a significant amount of non-English language in codes. From: tison Sent: Wednesday, April 17, 2024 5:16 PM To: general@incubator.apache.org Subject: Re: Questions about a new project entering Apache Incubator And [1] is actually update the community docs without INFRA changes. Previously (and now?), foo.incubator.apache.org has the same content with foo.apache.org unless you explicitly ask INFRA to change. Like even https://flink.incubator.apache.org/. I guess the main "pain point" is whimsy Web check checks " foo.incubator.apache.org" in config in some file on SVN before, and thus cause the Web check having a red mark. Best, tison. tison 于2024年4月17日 周三17:02写道： > I vote in [1] since it's how we practice for quite a while and it's a > clear consensus by the vote. > > All the repo of podlings have incubator- prefix, I don't see a motivation > to change. > > In [2] it says: > > > make less work for Infra > > I wonder if INFRA complained for this process. And what is the associated > JIRA ticket in INFRA to do the rename. I'd like to take INFRA's opinion > into consideration. > > In my previous experience, keep the name "foo", let INFRA move the repo, > rename it to "incubator-foo", and drop the prefix on graduation. In this > way, the link "apache/foo" will always work with GH redirections. > > To John: > > > , it can be confusing that they do. > > What is the certain redirection causing your confusion? > > Best, > tison. > > [1] > https://lists.apache.org/thread/n18gkb23bp005gb176jnwo2nrxty3z84 > [2] > https://github.com/apache/amoro/issues/2700 > > > Sheng Wu 于2024年4月17日 周三12:09写道： > >> This is not to get the conclusion, and it is not clear, and many other >> project repositories are with this prefix. >> >> >> https://incubator.apache.org/guides/transferring.html#first_steps_outside_the_incubator >> (tison >> found) >> >> Graduation doc is there indicating incaubtor- prefix is expected. This is >> just a 10s operation on GitHub admin page, not a heavy work. Graduation is >> not happening every day, even not every month. Developer don't have to >> change remote git, as that redirect forward is supported too. >> >> More importantly, I don't agree this is clear without prefix. >> >> This us serious change, if you inist this is clear, start a vote. A lot of >> ppl in this context don't agree too. >> >> Sheng Wu 吴晟 >> >> Apache SkyWalking >> Twitter, wusheng1108 >> >> >> Justin Mclean 于2024年4月17日 周三11:59写道： >> >> > Hi, >> > >> > Both of these projects are new and just getting set up. I'd give them a >> > little time to do that. Infra in recent years have asked to minimise >> work >> > for them on graduation. We recently dropped the requirement for having >> > incubating in podling domain names so I don't see it's needed in repo >> names >> > as long as it clear the project is an incubating project. >> > Kind Regards, >> > Justin >> > >> > >> > On Wed, 17 Apr 2024, 1:47 pm Willem Jiang, >> wrote: >> > >> > > 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,
Re: [VOTE] Release Apache Answer(Incubating) v1.3.0-RC1
+1 (binding) from me, and I checked the following items: - [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. - [X] Building is OK. Best wishes, Charles Zhang from Apache InLong Feng Dong 于2024年4月16日周二 09:51写道： > +1 non-binding > > I checked: > > [x] Download links are valid. > [x] Checksums and PGP signatures are valid. > [x] Source code distributions have correct names matching the current > release. > [x] LICENSE and NOTICE files are correct for each Answer repo. > [x] All files have license headers if necessary. > [x] No unlicensed compiled archives bundled in source archive. > > On Tue, Apr 2, 2024 at 5:45 PM Willem Jiang > wrote: > > > +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 > > > > >
[REMINDER] The Apache Answer project has been waiting for votes for quite some time now
Hello, The Apache Answer project has been waiting for votes way too long … would be great, if at least one IPMC member could spare a bit of time to provide the missing third vote. https://lists.apache.org/thread/lh3nvmr0gr1qh869zg76q6gcjj4ll3w0 Best regards, LinkinStar
Re: Questions about a new project entering Apache Incubator
I vote in [1] since it's how we practice for quite a while and it's a clear consensus by the vote. All the repo of podlings have incubator- prefix, I don't see a motivation to change. In [2] it says: > make less work for Infra I wonder if INFRA complained for this process. And what is the associated JIRA ticket in INFRA to do the rename. I'd like to take INFRA's opinion into consideration. In my previous experience, keep the name "foo", let INFRA move the repo, rename it to "incubator-foo", and drop the prefix on graduation. In this way, the link "apache/foo" will always work with GH redirections. To John: > , it can be confusing that they do. What is the certain redirection causing your confusion? Best, tison. [1] https://lists.apache.org/thread/n18gkb23bp005gb176jnwo2nrxty3z84 [2] https://github.com/apache/amoro/issues/2700 Sheng Wu 于2024年4月17日 周三12:09写道： > This is not to get the conclusion, and it is not clear, and many other > project repositories are with this prefix. > > > https://incubator.apache.org/guides/transferring.html#first_steps_outside_the_incubator > (tison > found) > > Graduation doc is there indicating incaubtor- prefix is expected. This is > just a 10s operation on GitHub admin page, not a heavy work. Graduation is > not happening every day, even not every month. Developer don't have to > change remote git, as that redirect forward is supported too. > > More importantly, I don't agree this is clear without prefix. > > This us serious change, if you inist this is clear, start a vote. A lot of > ppl in this context don't agree too. > > Sheng Wu 吴晟 > > Apache SkyWalking > Twitter, wusheng1108 > > > Justin Mclean 于2024年4月17日 周三11:59写道： > > > Hi, > > > > Both of these projects are new and just getting set up. I'd give them a > > little time to do that. Infra in recent years have asked to minimise work > > for them on graduation. We recently dropped the requirement for having > > incubating in podling domain names so I don't see it's needed in repo > names > > as long as it clear the project is an incubating project. > > Kind Regards, > > Justin > > > > > > On Wed, 17 Apr 2024, 1:47 pm Willem Jiang, > wrote: > > > > > 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
