Moving to a new Github organization

[RobbeSneyders]

I would like to start the discussion to move Connexion to a new Github organization as first raised in #1365 (comment).

With the recent addition of new non-Zalando maintainers, I see two main benefits in this:

• It removes the responsibility from Zalando over work that is now partially steered by external people.
• It would allow non-Zalando maintainers to receive additional rights on the repo, which could speed up the development and release cycle. Currently there is a blocking issue (Support Flask 2.0 #1401, Support for flask 2.x? #1420), which we cannot move forward on without the Zalando maintainers.

Our first idea was to move to an organization with the name 'Connexion', but this name has been taken already (https://github.com/Connexion). There is no public activity by the organization, but unfortunately I cannot see a way to contact them, and Github has moved away from their previous name squatting policy where you could request transfer of inactive names. I would therefore suggest 'ConnexionAPI' or 'ConnexionOrg' as name, but curious about other suggestions.

The most important step now is to get approval from Zalando side and see how we can credit the work done by Zalando to bring connexion where it is today. @hjacobs can you provide a view on which steps we need to take to move forward with this?

[cognifloyd]

@dtkav what about using github.com/spec-first for this?

[dtkav]

sure, I'm happy to transfer ownership if folks like the name.

[RobbeSneyders]

spec-first sounds perfect to me.

[Ruwann]

I discussed this with Henning on Friday and it is OK for him to move it to the spec-first org.
@hjacobs Are there still other steps needed from Zalando to be able to move it under a new org? Do you have the required permissions on the Zalando org to do this?

We might have to first remove the existing spec-first/connexion fork before we can move it, but not sure.

https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository#transferring-a-repository-owned-by-your-organization

[RobbeSneyders]

@dtkav could you already add @hjacobs, @Ruwann and myself as owners of the spec-first organization?

[dtkav]

@RobbeSneyders
done

[dtkav]

I've deleted all the repositories from the org so you should be able to do the transfer. I could also transfer dtkav/swagger-ui-bundle to the organization as the primary use case is to (optionally) have "batteries included" swagger-ui in connexion.
@RobbeSneyders I saw you had a pull request to update to swagger UI v4. I have very little free time at the moment, sorry for not getting back to you.
FYI the release process is a little bit more complicated than copying the distributable binaries from upstream because there is a jinja template that is used to inject some settings from connexion.

[hjacobs]

@dtkav @RobbeSneyders @Ruwann I would prepare a Zalando blog post (for https://engineering.zalando.com/) explaining the move of Connexion and share a draft with you latest next week. Afterwards we can do the migration between orgs.

[hjacobs]

Blog post: https://engineering.zalando.com/posts/2022/02/releasing-connexion-python-framework-to-the-oss-community.html

I will move this repository from https://github.com/zalando/connexion/ to https://github.com/spec-first/connexion/ today at ~15:30 CET if there is no veto.

GitHub help on transferring repositories for reference: https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository

[hjacobs]

Repository was moved:

[RobbeSneyders]

Thanks @hjacobs!