Create a document list our accounts and who has access #98
Conversation
The document also includes some guidance on what's expected from people who have access to our accounts.
|
Just leaving a quick thought: we might want to create a organization account on Zenodo for uploading new versions of our packages. Would be nice to figure out how we can transfer current entries to the future Fatiando account. I'll review this PR later on |
Just checked and apparently we have one... |
|
Just sent them a message asking how to transfer to the Fatiando account. |
|
Wow Zenodo support is awesome! Already got a response saying that:
So I'll email them about transferring the ones under my own account to the Fatiando one. I'll include the DOI for each upload I want to transfer. @santisoler you have some of the uploads on your account right? Could you do the same so we can get everything on the Fatiando account? |
I knew that.. I don't know why I asked haha 🤦🏼 . I knew that Zenodo will allow us to do that! I do have Harmonica, the Southern Africa topography and gravity datasets (from Fatiando Data), and the old Rockhound. I'll transfer all of them. |
|
@leouieda could you share the zenodo email that we would need to write to? (feel free to share the address through Element if you don't want to make it public) |
|
@santisoler I think it's info@zenodo.org At least that's the one I'm writing to. |
|
The fatiando.org domain has now been moved to the Fatiando Hover account. |
|
My Zenodo repositories (Harmonica, Rockhound and Fatiando a Terra Data: Southern Africa - Topography and Bathymetry) where moved to the Fatiando a Terra Zenodo account. |
|
Alright, merging this in now! I think everything is now under a Fatiando owned account that multiple people have access. So I can walk off into the sunset now and be happy that Fatiando can live on. |
The document is a simple logbook to track social media and website posts. It should be improved later with some automatization <!-- Thank you for contributing a pull request to Fatiando! 💖 👆🏽 ABOVE: Describe the changes proposed and WHY you made them. 👇🏽 BELOW: Link to any relevant issue or pull request. Please ensure you have taken a look at the CONTRIBUTING.md file in this repository (if available) and the general guidelines at https://github.com/fatiando/community/blob/main/CONTRIBUTING.md --> **Relevant issues/PRs:** Fixes #107 / For account access, see ACCOUNTS.md, and #98 / For community manager responsibilities, see GOVERNANCE.md and #78 <!-- Example: "Fixes #1234" / "See also #345" / "Relevant to #111" Use keywords (e.g., Fixes, Closes) to create the links and automatically close issues when this PR is merged. See https://github.com/blog/1506-closing-issues-via-pull-requests -->
The document also includes some guidance on what's expected from people who have access to our accounts.
Relevant issues/PRs: Fixes #34