Re: [incubation] Additional GitHub Repos

[Kevin Herron <kevinherron@xxxxxxxxx>]

Edward, Jonah - thanks for the advice.

I'm going to look at creating top level "incubating" and "deprecated" folders within the existing repository. Perhaps that will be enough to put this code out of sight and out of mind :)

On Thu, Apr 10, 2025 at 8:20 AM Jonah Graham <jonah@xxxxxxxxxxxxxxxx> wrote:

Hi Kevin,

I agree with Ed's response. However if you are looking to make additional git repos you can do it self-service, see https://github.com/eclipse-milo/.eclipsefdn?tab=readme-ov-file#self-service-of-your-github-organization - although to be fair I do often raise helpdesk tickets on these types of things because I am not always aware of how much otterdog can do.

HTH

Jonah

~~~
Jonah Graham (he/him)
Kichwa Coders
www.kichwacoders.com

On Thu, 10 Apr 2025 at 11:02, Kevin Herron via incubation <incubation@xxxxxxxxxxx> wrote:

Recently I completed the move to a project-specific org on GitHub (e.g. i.e. `eclipse/milo` became `eclipse-milo/milo`).

Now I'm preparing for a long overdue 1.0 release and looking to move some of the modules in my project to separate incubating or deprecated repositories (i.e. create `eclipse-milo/milo-incubating` and `eclipse-milo/milo-deprecated` repositories).

Is this a pattern that other projects have used before? Are there any objections to this? Is this just a simple help desk request? Am I even asking in the right place? :)

Thanks,

Kevin

_______________________________________________
incubation mailing list
incubation@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/incubation