Migrate Plexus-Interop project to FINOS organisation on GitHub

[mcleo-d]

Description

This task describes migrating plexus-interop from the finos-plexus organisation into the primary finos GitHub organisation following the migration of plexus-interop-desktop-api as described in issue #174.

Solution

• FINOS schedules and migrates plexus-interop from the finos-plexus organisation into the finos organisation on GitHub.
• FINOS notifies the Plexus team of change and supplies URL to plexus-interop on finos.
• Plexus engages the project as normal in accordance with the GitHub Transferring a Repository article highlighted below.

What's transferred with a repository?

https://help.github.com/en/enterprise/2.18/user/github/administering-a-repository/transferring-a-repository

When you transfer a repository, its issues, pull requests, wiki, stars, and watchers are also transferred. If the transferred repository contains webhooks, services, secrets, or deploy keys, they will remain associated after the transfer is complete. Git information about commits, including contributions, is preserved. In addition:

• If the transferred repository is a fork, then it remains associated with the upstream repository.

• If the transferred repository has any forks, then those forks will remain associated with the repository after the transfer is complete.

• If the transferred repository uses Git Large File Storage, all Git LFS objects are automatically moved. This transfer occurs in the background, so if you have a large number of Git LFS objects or if the Git LFS objects themselves are large, it may take some time for the transfer to occur.

• When a repository is transferred between two user accounts, issue assignments are left intact. When you transfer a repository from a user account to an organization, issues assigned to members in the organization remain intact, and all other issue assignees are cleared. Only owners in the organization are allowed to create new issue assignments. When you transfer a repository from an organization to a user account, only issues assigned to the repository's owner are kept, and all other issue assignees are removed.

• If the transferred repository contains a GitHub Pages site, then links to the Git repository on the Web and through Git activity are redirected. However, we don't redirect GitHub Pages associated with the repository.

• All links to the previous repository location are automatically redirected to the new location. When you use git clone, git fetch, or git push on a transferred repository, these commands will redirect to the new repository location or URL. However, to avoid confusion, we strongly recommend updating any existing local clones to point to the new repository URL. You can do this by using git remote on the command line:

$ git remote set-url origin new_url
For more information, see Changing a remote's URL

[mcleo-d]

@maoo, @udalmik and @paulwhitby - This Friday 22nd May FINOS wants to transfer the Plexus Interop project from the finos-plexus organisation to the primary finos organisation on GitHub.

This issue has been updated to reflect the change and to demonstrate how the transfer accounts for redirecting established relationships between the Plexus project, branches, forks, web hooks, developers and the wider Plexus engineering infrastructure.

Please respond by thumbs up that you're aware of this work taking place and are in full agreement.

[maoo]

Roger. Repo transfer is planned for Monday 25 May at 10am CEST .

Note. The URL https://finos-plexus.github.io/plexus-interop will be rewritten to https://finos.github.io/plexus-interop, but I'd suggest to actually setup plexus.finos.org. I can make the changes needed (via PRs), after the repo transfer, if you're interested.

TODO - check backlinks on Google to understand where the URL is used.

Thanks!

[mcleo-d]

The transfer is now done and the new repo URL is https://github.com/finos/plexus-interop
The new website URL is https://plexus.finos.org

Next Actions

The following actions are being coordinated between @mcleo-d and @udalmik

• Announce transfer to Community all hands call - @mcleo-d
• Plexus team confirms that sync works and that everyone accepted invitation to the GitHub plexus-interop team - @udalmik
• All links to plexus-interop website are changed to https://plexus.finos.org - @udalmik

[mcleo-d]

@udalmik - I announced the Plexus-Interop repo transfer during the FINOS All Community call on 11th June and have marked as done on the following comment - #112 (comment)

Can the remaining tasks also be marked as done ?

• Plexus team confirms that sync works and that everyone accepted invitation to the GitHub plexus-interop team - @udalmik
• All links to plexus-interop website are changed to https://plexus.finos.org - @udalmik