Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Plan Github migration #678

Open
gubuntu opened this issue May 25, 2022 · 0 comments
Open

Plan Github migration #678

gubuntu opened this issue May 25, 2022 · 0 comments

Comments

@gubuntu
Copy link
Contributor

gubuntu commented May 25, 2022

This Catalogue repo should be transferred from Kartoza to a SANSA org, where SANSA admins own and manage it, granting access to Kartoza and other contractors.

@Maite-Machipi started by creating a (private?) organisation SANSA-Catalogue. My recommendation is that SANSA create or nominate a wider SANSA GH org that can host multiple repos besides the Catalogue.

Once that is established, a Kartoza admin (me for example) will have to be temporarily added to the SANSA org so we can transfer this Catalogue repo to SANSA, which entails creating the repo (hence requiring membership with sufficient rights to create repos. Thereafter, the Kartoza user can be converted to an outside collaborator along with other non-SANSA staff.

Furthermore, users and admins of the Catalogue repo once in the SANSA org must be individual accounts, not anonymous users such as the 'SANSA-EO' that Maite proposed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant