> 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 <jus...@classsoftware.com> 于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 <wander4...@gmail.com> 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 <wilfr...@apache.org> 于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=&q=incubator-&sort=&type=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: general-h...@incubator.apache.org > >
