Eclipse Github organisation move for technology.nebula

As part of our ongoing efforts to improve security and allow more self service for projects, we are moving project repositories from the Github Eclipse organisation to individual per-project organisations[1].

We'll use pre-existing project organisations when available, otherwise they'll be created with the 'eclipse-projectshortname'(ie: eclipse-babel) format.

Github provides redirects for moves like this, so the process should be fairly smooth.  That said, committers will need to update any local repositories and build jobs to point at the new remote URL locations once the move is done.

If your project needs to adjust the timing, or has another organisation you'd like to use, we can discuss that here.

If we haven't heard from the project by the due date, Webmaster will simply complete the move and refer the project to the EMO team who will confirm that the project is still active.

[1]#3571

/cc @lcaron /cc @wjongman

changed due date to December 16, 2024

added IT-prioritymedium IT-severitylow Migration team:infra + 1 deleted label

assigned to @chills2023

changed the description

Unfortunately, that org is already taken. https://github.com/eclipse-nebula

@wbeaton has been chasing it without success. What name can we use?

added service:GitHub label and removed 1 deleted label

@mward any idea how we can name this org?

eclipse-nebula-opal is a good name. We merged with the opal project a couple of years ago.

We don't have a project named 'Opal' at the Foundation. Did I miss something?

While not great 'eclipse-tech-nebula' would still keep the shortname at least. Although should the project ever move between top levels that might be a bit messy.

nebula and opal merged a couple of years ago. Opal was a project outside the foundation.

@wjongman @mward what's next with this move?

Well as we haven't been able to get control of 'eclipse-nebula', I'd suggest either 'eclipse-tech-nebula' or 'eclipse-technology-nebula' or 'eclipse-org-nebula'. That last one saves us from needing to consider updating the name if the project ever switches TLPs, so it'd get my vote.

Since Opal isn't one of our projects or a trademark that we assert/own I would avoid using it.

What about https://github.com/eclipsenebula

I already have that and I can move that to the foundation

I'm certainly ok with 'eclipsenebula' as the organisation name.

What should happen to the repositories already in it?

These can be dropped. Who should I transfer ownership to?

'eclipsewebmaster' is the user.

Worst case just invite us to the org with owner permissions and we can set it up from there.

Ok that was done.

You've invited Eclipse Webmaster team to Eclipse Nebula Project! They'll be receiving an email shortly. They can also visit https://github.com/EclipseNebula to accept the invitation.

The Nebula repos have been moved to the eclipsenebula organisation, and committers that have added their Github IDs to their Eclipse.org accounts should receive access in an hour or so when the sync tool runs.

At this time committers should also update the remote URLs for any local copies or build jobs that use these repos.

closed

Whoops, forgot Otterdog.

@heurtemattes would you please enable Otterdog for the eclipsenebula organistation? Thanks!

reopened

mentioned in issue #5351 (closed)

marked this issue as blocking #5351 (closed)

Otterdog has been enabled for the eclipsenebula organization.

The following repo has been created: https://github.com/eclipsenebula/.eclipsefdn

You can find the current configuration at https://github.com/eclipsenebula/.eclipsefdn/blob/main/otterdog/eclipsenebula.jsonnet

A dashboard UI of the configuration can also be accessed at https://eclipsenebula.github.io/.eclipsefdn/ which also provides a playground to test snippets before making a PR. When you want to suggest changes, fork the repo, make changes and create a PR. A workflow will automatically run and show you the changes that will be applied and validate that the configuration is correctly formatted and composed.

The documentation of all supported settings can be found here: https://otterdog.readthedocs.io/en/latest/reference/resource-format/

A list of all Eclipse projects that have it also enabled can be accessed here: https://eclipsefdn.github.io/otterdog-configs/ That is often quite helpful to get ideas about how others do their configurations.

You can also navigate to https://otterdog.eclipse.org/projects/technology.nebula to get more insights for your project in a dashboard like view.

If you have any problems, let us know.

@netomi can you check why the website is not updated? https://otterdog.eclipse.org/projects/technology.nebula

its not in the otterdog.json yet. It has been setup already so maybe a push is missing?

further investigation showed that it is due to mix of uppercase characters in the GitHub organization for nebula. The name is actually EclipseNebula. The GitHub api sometimes returns lowercase sometimes the mixed case which leads to inconsistencies in the datamodel.

Will fix that to make sure the matching can be done all the time.

ok its fixed now: https://otterdog.eclipse.org/projects/technology.nebula#overview

thanks @netomi

closed