-
Notifications
You must be signed in to change notification settings - Fork 73
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
move https://github.com/baskaufs/tdwg-standards repo to the TDWG github site #170
Comments
The only thing blocking this is me having some time to do this 😄
|
|
I'll need admin rights: In settings > Collaborators & teams > Look for my name > Update permission level from the dropdown to admin. |
I'm not seeing that as an option in my repo. I'm wondering if it is because I have an individual repo rather than an organizational one. Another option might be to transfer the ownership of the repo to TDWG. However, that may not be an option since it says "Transfer this repository to another user or to an organization where you have the ability to create repositories". Since I don't have the ability to create repositories on the TDWG site, that might be a problem. |
Ok, I'll give you temp access to the TDWG org to make the move yourself. |
Cool, just tell me when. |
Now. :-) |
OK, it's done. It says that it might take a few minutes to happen. I wasn't able to give it a new name, but presumably that can be done after the move. I gave the "admin" team rights to it. |
Nice, so real time collaboration here 👍 |
It is showing up now |
|
@peterdesmet Is there anything blocking moving the TDWG standards metadata repo that I've constructed into the TDWG github site now? I think I've done most of the work on it that I'm going to be doing for a while and it now has a nice descriptive landing page.
As I said earlier, I don't think this belongs within the DwC repo - it should have its own repo within the TDWG site. I would like to wrap this up and move on to something else. But it needs to exist in order to close some of the open DwC issues.
The text was updated successfully, but these errors were encountered: