Re: [DISCUSS] Drop the incubator- prefix for podling's GitHub repo
If the `incubator-` prefix significantly burdens the graduation process or introduces inconveniences in package or dependency management, its removal might be considered. However, IMO, maintaining incubating in the description, and website, especially in the *release version*, clearly signals that this is an incubator release of an Apache project, which should be sufficient to alleviate most ambiguity. I mean, `incubating` is just a temporary status label, it's changeable, while the project or product name usually is immutable. Regards, Xinyu Zhou On Mon, Apr 29, 2024 at 5:40 PM tison wrote: > Before starting the vote, I found (perhaps) a final question: Shall we thus > guide all the new podlings to enter the incubator without incubator- prefix > and thus converge all the current podlings are in form apache/foo? > > I'm afraid that if new podling can still have the incubator- prefix, it can > give a confusing impression to end-users. > > I can't find a good place to document this point but perhaps we spread the > consensus when reviewing new podling proposal's "Git Repositories" section. > > Best, > tison. > > > ConradJam 于2024年4月29日周一 14:17写道： > > > As a developer on the Apache Amoro project, I believe it's crucial to > > prominently display the project's status as an incubator, whether by > > attaching it to the project prefix or featuring it on the website. Most > > individuals typically recognize that a project is in incubation through > the > > project's website or GitHub description (including myself when initially > > encountering or learning about a project). Every project developer has an > > obligation to indicate the project's incubation status when promoting or > > publicizing it. Additionally, displaying a clear logo on the website > > indicating its incubation status is essential. As a user, simply having > > that incubator logo or description suffices for me. Therefore, I’m +0 > for > > incubator- prefix . > > > > tison 于2024年4月24日周三 19:49写道： > > > > > Thanks for your participation! > > > > > > For people who support drop the incubator- prefix, please describe you > > > opinion on: > > > > > > > 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. > > > > 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/ > > > > > > Be sure that you know we don't barely drop the prefix, but we need a > > formal > > > way to "make it clear that a podling's repo is in the incubating > status", > > > which can be achieved currently by its prefix. > > > > > > Best, > > > tison. > > > > > > > > > Wilfred Spiegelenburg 于2024年4月23日周二 13:12写道： > > > > > > > For Go based projects dropping the incubator reference in the git > repo > > > > makes things easier also when graduating. Packages and dependencies > are > > > > referenced based on the repository name. Renaming the repository > either > > > > requires changes throughout the code base to remove the incubator > > > reference > > > > or the packages will always have the incubator reference in them. > > > > > > > > Wilfred > > > > > > > > On 2024/04/23 01:22:02 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 > > > > >
Re: [DISCUSS] Drop the incubator- prefix for podling's GitHub repo
Before starting the vote, I found (perhaps) a final question: Shall we thus guide all the new podlings to enter the incubator without incubator- prefix and thus converge all the current podlings are in form apache/foo? I'm afraid that if new podling can still have the incubator- prefix, it can give a confusing impression to end-users. I can't find a good place to document this point but perhaps we spread the consensus when reviewing new podling proposal's "Git Repositories" section. Best, tison. ConradJam 于2024年4月29日周一 14:17写道： > As a developer on the Apache Amoro project, I believe it's crucial to > prominently display the project's status as an incubator, whether by > attaching it to the project prefix or featuring it on the website. Most > individuals typically recognize that a project is in incubation through the > project's website or GitHub description (including myself when initially > encountering or learning about a project). Every project developer has an > obligation to indicate the project's incubation status when promoting or > publicizing it. Additionally, displaying a clear logo on the website > indicating its incubation status is essential. As a user, simply having > that incubator logo or description suffices for me. Therefore, I’m +0 for > incubator- prefix . > > tison 于2024年4月24日周三 19:49写道： > > > Thanks for your participation! > > > > For people who support drop the incubator- prefix, please describe you > > opinion on: > > > > > 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. > > > 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/ > > > > Be sure that you know we don't barely drop the prefix, but we need a > formal > > way to "make it clear that a podling's repo is in the incubating status", > > which can be achieved currently by its prefix. > > > > Best, > > tison. > > > > > > Wilfred Spiegelenburg 于2024年4月23日周二 13:12写道： > > > > > For Go based projects dropping the incubator reference in the git repo > > > makes things easier also when graduating. Packages and dependencies are > > > referenced based on the repository name. Renaming the repository either > > > requires changes throughout the code base to remove the incubator > > reference > > > or the packages will always have the incubator reference in them. > > > > > > Wilfred > > > > > > On 2024/04/23 01:22:02 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
Re: [DISCUSS] Drop the incubator- prefix for podling's GitHub repo
As a developer on the Apache Amoro project, I believe it's crucial to prominently display the project's status as an incubator, whether by attaching it to the project prefix or featuring it on the website. Most individuals typically recognize that a project is in incubation through the project's website or GitHub description (including myself when initially encountering or learning about a project). Every project developer has an obligation to indicate the project's incubation status when promoting or publicizing it. Additionally, displaying a clear logo on the website indicating its incubation status is essential. As a user, simply having that incubator logo or description suffices for me. Therefore, I’m +0 for incubator- prefix . tison 于2024年4月24日周三 19:49写道： > Thanks for your participation! > > For people who support drop the incubator- prefix, please describe you > opinion on: > > > 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. > > 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/ > > Be sure that you know we don't barely drop the prefix, but we need a formal > way to "make it clear that a podling's repo is in the incubating status", > which can be achieved currently by its prefix. > > Best, > tison. > > > Wilfred Spiegelenburg 于2024年4月23日周二 13:12写道： > > > For Go based projects dropping the incubator reference in the git repo > > makes things easier also when graduating. Packages and dependencies are > > referenced based on the repository name. Renaming the repository either > > requires changes throughout the code base to remove the incubator > reference > > or the packages will always have the incubator reference in them. > > > > Wilfred > > > > On 2024/04/23 01:22:02 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:
Re: [DISCUSS] Drop the incubator- prefix for podling's GitHub repo
> https://github.com/apache/incubator-fury/pull/1574/commits/2ac9d808af75d17c0ea74a9755fe165b13de15f2 > > That is, keep the first and most prominent uses in form "Apache Foo > (incubating)" and add a hyperlink to "incubating" to the DISCLAIMER. This > should be a shorter solution and at least as good as the incubator- prefix. > Ensuring the repo description contain "incubating" can help. > that looks good and compensates for the loss of incubating in the name easily. Wilfred - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Drop the incubator- prefix for podling's GitHub repo
Hi Willem, Good point. I suppose the current incubator- prefix doesn't give more information than the "incubator" words itself. Thus, trying to merge the inputs above, I made a third candidate: * https://github.com/apache/incubator-fury/pull/1574/commits/2ac9d808af75d17c0ea74a9755fe165b13de15f2 That is, keep the first and most prominent uses in form "Apache Foo (incubating)" and add a hyperlink to "incubating" to the DISCLAIMER. This should be a shorter solution and at least as good as the incubator- prefix. Ensuring the repo description contain "incubating" can help. I'm going to prepare a patch on the incubator website to review the wording we'd use before next week. Best, tison. Willem Jiang 于2024年4月25日周四 17:02写道： > 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: [DISCUSS] Drop the incubator- prefix for podling's GitHub repo
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: [DISCUSS] Drop the incubator- prefix for podling's GitHub repo
To preview the render result I made https://github.com/apache/incubator-fury/pull/1574 to showcase. You can head to https://github.com/apache/incubator-fury/tree/tisonkun-patch-1 to see the render version. I made two candidates: 1. Inline the DISCLAIMER with an IMPORTANT callout 2. Add a badge with the word "INCUBATING" and link to the DISCLAIM file. IMO 1 doesn't take too much place and 2 is not quite clear to be found by readers. > What is important is that the project is clearly understood to be an incubating p[project and what that means, rather than the exact wording I agree. We can use the expression on Incubator guides, but we'd still better provide some examples so that podlings can easily follow. Best, tison. Justin Mclean 于2024年4月25日周四 13:46写道： > Hi, > > > 4. To clarify that a repo belongs to a podling, introduce a guideline or > > policy to help PPMCs include the DISCLAIMER in the README of all their > > repos. > > Alternatively, perhaps we can come up with something a little shorter > shorter that points to DISCLAIMER? What is important is that the project is > clearly understood to be an incubating p[project and what that means, > rather than the exact wording. > > Kind Regards, > Justin > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [DISCUSS] Drop the incubator- prefix for podling's GitHub repo
Hi, > 4. To clarify that a repo belongs to a podling, introduce a guideline or > policy to help PPMCs include the DISCLAIMER in the README of all their > repos. Alternatively, perhaps we can come up with something a little shorter shorter that points to DISCLAIMER? What is important is that the project is clearly understood to be an incubating p[project and what that means, rather than the exact wording. Kind Regards, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Drop the incubator- prefix for podling's GitHub repo
> For Go based projects dropping the incubator reference in the git repo makes things easier also when graduating I support this statement. For Java or Rust release, we generally don't include the incubator prefix in dep ID. But Golang dependency relies on the name of the GitHub repository. So it can often be: * github.com/apache/incubator-xxx/yyy While redirections can work, IIRC INFRA members sometimes rename before repo transfer and thus apache/xxx won't have the redirection to apache/incubator-xxx then. > I would be for requiring the incubator disclaimer text in the project's README: This sounds reasonable. No matter if we drop the incubator- prefix, as [1] wrote: > Podling web sites MUST include a clear disclaimer on their website and in all documentation (including releases) stating that they are in incubation. The README is somehow documentation. [1] https://incubator.apache.org/guides/branding.html#disclaimers Then I'm going to start a vote in the next week on a bunch of the following resolutions: 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. To clarify that a repo belongs to a podling, introduce a guideline or policy to help PPMCs include the DISCLAIMER in the README of all their repos. I volunteer to go through the Incubator website and update content accordingly if these resolutions are made. To IPMC members: I plan to start a vote in general@incubator.a.o. Do we have other places to record resolutions proposed and concluded? Best, tison. Justin Mclean 于2024年4月25日周四 10:46写道： > Hi, > > I would be for requiring the incubator disclaimer text in the project's > README: > "Apache FOO is an effort undergoing incubation at The Apache Software > Foundation (ASF), sponsored by the Apache Incubator. Incubation is required > of all newly accepted projects until a further review indicates that the > infrastructure, communications, and decision making process have stabilized > in a manner consistent with other successful ASF projects. While incubation > status is not necessarily a reflection of the completeness or stability of > the code, it does indicate that the project has yet to be fully endorsed by > the ASF.” > > Kind Regards, > Justin > > > On 24 Apr 2024, at 9:48 pm, tison wrote: > > > > Thanks for your participation! > > > > For people who support drop the incubator- prefix, please describe you > > opinion on: > > > >> 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. > >> 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/ > > > > Be sure that you know we don't barely drop the prefix, but we need a > formal > > way to "make it clear that a podling's repo is in the incubating status", > > which can be achieved currently by its prefix. > > > > Best, > > tison. > > > > > > Wilfred Spiegelenburg 于2024年4月23日周二 13:12写道： > > > >> For Go based projects dropping the incubator reference in the git repo > >> makes things easier also when graduating. Packages and dependencies are > >> referenced based on the repository name. Renaming the repository either > >> requires changes throughout the code base to remove the incubator > reference > >> or the packages will always have the incubator reference in them. > >> > >> Wilfred > >> > >> On 2024/04/23 01:22:02 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.
Re: [DISCUSS] Drop the incubator- prefix for podling's GitHub repo
Hi, I would be for requiring the incubator disclaimer text in the project's README: "Apache FOO is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.” Kind Regards, Justin > On 24 Apr 2024, at 9:48 pm, tison wrote: > > Thanks for your participation! > > For people who support drop the incubator- prefix, please describe you > opinion on: > >> 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. >> 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/ > > Be sure that you know we don't barely drop the prefix, but we need a formal > way to "make it clear that a podling's repo is in the incubating status", > which can be achieved currently by its prefix. > > Best, > tison. > > > Wilfred Spiegelenburg 于2024年4月23日周二 13:12写道： > >> For Go based projects dropping the incubator reference in the git repo >> makes things easier also when graduating. Packages and dependencies are >> referenced based on the repository name. Renaming the repository either >> requires changes throughout the code base to remove the incubator reference >> or the packages will always have the incubator reference in them. >> >> Wilfred >> >> On 2024/04/23 01:22:02 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 >> >> - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail:
Re: [DISCUSS] Drop the incubator- prefix for podling's GitHub repo
Thanks for your participation! For people who support drop the incubator- prefix, please describe you opinion on: > 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. > 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/ Be sure that you know we don't barely drop the prefix, but we need a formal way to "make it clear that a podling's repo is in the incubating status", which can be achieved currently by its prefix. Best, tison. Wilfred Spiegelenburg 于2024年4月23日周二 13:12写道： > For Go based projects dropping the incubator reference in the git repo > makes things easier also when graduating. Packages and dependencies are > referenced based on the repository name. Renaming the repository either > requires changes throughout the code base to remove the incubator reference > or the packages will always have the incubator reference in them. > > Wilfred > > On 2024/04/23 01:22:02 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: [DISCUSS] Drop the incubator- prefix for podling's GitHub repo
For Go based projects dropping the incubator reference in the git repo makes things easier also when graduating. Packages and dependencies are referenced based on the repository name. Renaming the repository either requires changes throughout the code base to remove the incubator reference or the packages will always have the incubator reference in them. Wilfred On 2024/04/23 01:22:02 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: [DISCUSS] Drop the incubator- prefix for podling's GitHub repo
I think this is a well thought-out and change. It reduces the load on Infra and allows the project's contributors to take ownership of removing the (incubating) disclaimers and annotations after graduation. On 23/04/2024 11:22 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: [DISCUSS] Drop the incubator- prefix for podling's GitHub repo
Repeated my opinion again 1. Incubating should be required for words in README and other places mentioned, such as blogs, videos, website, github repository 2. incubator- prefix is required. 3. DISCLAIMER is required. All of these make sure the incubating status is clear. All these have existed for years and are easy to practice. Basically, nothing needs to be changed about this. Sheng Wu 吴晟 Twitter, wusheng1108 tison 于2024年4月23日周二 09:24写道： > > 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
