Migrate project to anexia organisation

[nachtjasmin]

Hi,

First of all: a big thanks from our team to you for providing this integration! 😍

You've contacted us quite a while ago and we didn't forget about it. We just had to discuss several things, especially for compliance reasons. Anexians are able to track this internally via ANXOS-394. Unfortunately that took longer than expected, but here we are. 😅

Now, in order to migrate the project to our organisation, the following steps have to be done:

• You're starting the migration process towards the anexia GitHub organisation.
• Once we're aware of it (just ping me here), it'll be approved by someone from the Open Source team.
• We'd rename the repository to external-dns-webhook and change the module inside the go.mod.
• If there are secrets for integration tests, we would replace them with new tokens.
• If not already done, you'd get added as a Contributor to the project again, allowing you to continue with the maintenance.
• We'd have to release a new version, this time with the new project name/namespace.
• Someone (either you or one of us) would have to create a pull request towards the kubernetes-sigs/external-dns repository to adjust the link for the integration.

[ProbstenHias]

Hi @nachtjasmin,
Thanks for opening the issue.

I was just about to start the migration when I was hindered by the fact that I would need permission in the anexia org to create a new repo.

So I suggest I will make you Admin of the new Org I just created.
Then you could transfer the repo over.
An invitation was already sent out.