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 <wander4...@gmail.com> 于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 <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 > > > > > -- Best ConradJam
