: general-h...@incubator.apache.org
>
>
>> From: Sheng Wu
>> Sent: Monday, April 22, 2024 11:46 PM
>> To: general@incubator.apache.org ;
>> d...@armoro.apache.org ; d...@hertzbeat.apache.org
>>
>> Subject: Re: Questions about a new project entering Ap
HI,
So, I had an informal chat with Infra, and they don't care which one they do,
but is it some work for them to change from “incubator-foo” to “foo” on
graduation. I’m curious as to why some people in this thread think this is a
big issue if the project clearly states it is an incubating proj
> 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.
h 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 witho
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
egarding 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
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 assoc
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
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
a
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
On Tue, Apr 16, 2024 at 11:06 PM 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 r
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
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
> 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 `
First of all, congratulations to HertzBeat for successfully entering the Apache
Incubator.
I noticed that the project has created an issue for an unknown license and is
ready to address it. I'm sure the project will also address other unknown
licenses, if they exist.
I wonder if the situation
15 matches
Mail list logo
