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
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
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
> 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
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
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
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
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
> 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
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
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
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
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
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
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
15 matches
Mail list logo
