Move Stepup-* repositories from GitHub SURFnet organization to OpenConext

[phavekes]

This issue is imported from pivotal - Originaly created at Dec 7, 2016 by Pieter van der Meulen

We plan to move the Stepup development repositories to the OpenConext org. This also means we can use the openconext.org CMS for Stepup project wide communication like general overview, announcement of releases etc.

The Stepup code etc. will remain independent of other OpenConext components.

What will be the impact on this move on Stepup development, release?

• Github does provide redirects when moving repositories
• How does this affect packagist, composer dependencies?

BEFORE MOVING all PR\'s and reviews must be done/closed/merged.

Est.: 8hrs.

[phavekes]

Before making an estimation, we\'ll have to investigate the impact on:

• packagist and composer
• which repo\'s to keep and which not (...-client & ...-client-bundle)
• what to do with naming and namespacing (SURFnet vs OpenConext)
• migration in practice, how to do what. (Daan van Renterghem - Jan 23, 2017)

[phavekes]

The simplest would be to just move repo\'s, see https://github.com/composer/packagist/issues/47#issuecomment-271962248 . Renaming packages (as part of rebranding OpenConext_ would be more involved, see the same issue.

Prior to moving we should select which packages/applications to rename.

For the estimation the assumption is that only applications (being SS, RA, GW and MW) will change namespaces. (Daan van Renterghem - Jan 24, 2017)

[phavekes]

We should move the following Stepup repositories:

1. https://github.com/SURFnet/Stepup-SelfService
2. https://github.com/SURFnet/Stepup-RA
3. https://github.com/SURFnet/Stepup-Middleware
4. https://github.com/SURFnet/Stepup-Gateway
5. https://github.com/SURFnet/Stepup-Middleware-clientbundle
6. https://github.com/SURFnet/Stepup-Deploy
7. https://github.com/SURFnet/Stepup-saml-bundle
8. https://github.com/SURFnet/Stepup-bundle
9. https://github.com/SURFnet/Stepup-u2f-bundle
10. https://github.com/SURFnet/stepup-biometric

Also, we could/should move:

1. https://github.com/SURFnet/yubikey-api-client-bundle
2. https://github.com/SURFnet/yubikey-api-client
3. https://github.com/SURFnet/messagebird-api-client-bundle

Other Stepup repositories:

1. https://github.com/SURFnet/Stepup-Build
2. https://github.com/SURFnet/Stepup-Metadata
3. https://github.com/SURFnet/Stepup-VM
4. https://github.com/SURFnet/Stepup-Tools
5. https://github.com/SURFnet/Stepup-SFO-demo

For each repository, we have to edit the package URL on Packagist to point to the correct repository.

This is going to be a governance move only: the code will remain untouched for now. The rewiring of namespaces will be postponed as it would entail creating a mechanism for re-hydrating the events as they are identifiable by their class name. Internally, "Surfnet" will still be present in namespaces for now. (Alex Rothuis - Jan 26, 2017)

[phavekes]

As discussed.

Not moved and will not move: https://github.com/SURFnet/yubikey-api-client-bundle https://github.com/SURFnet/yubikey-api-client https://github.com/SURFnet/messagebird-api-client-bundle

Of the "Other" repositories (i.e. tooling related) only the ones in active use are moved: https://github.com/SURFnet/Stepup-Build https://github.com/SURFnet/Stepup-VM

Not moved: https://github.com/SURFnet/Stepup-SFO-demo (Pieter van der Meulen - Jan 26, 2017)