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

Move to github.com/gdcc? Add to Dataverse API Guide? #4

Closed
pdurbin opened this issue Jun 15, 2022 · 10 comments · Fixed by IQSS/dataverse#8991
Closed

Move to github.com/gdcc? Add to Dataverse API Guide? #4

pdurbin opened this issue Jun 15, 2022 · 10 comments · Fixed by IQSS/dataverse#8991

Comments

@pdurbin
Copy link
Member

pdurbin commented Jun 15, 2022

Hi! I spotted your tweet at https://twitter.com/GaelForget/status/1537033362543616005

@poikilotherm and I would like to invite you to move this repo to the @gdcc GitHub org, next to pyDataverse: https://github.com/gdcc/pyDataverse

Totally up to you, of course! 😄

Say the word and we'll create an empty repo, made you admin, etc. Thanks!

(Also, just to foreshadow a future step, we'd also love a pull request to update a future version of https://guides.dataverse.org/en/5.11/api/client-libraries.html to include Julia! Here's the source: https://github.com/IQSS/dataverse/blob/v5.11/doc/sphinx-guides/source/api/client-libraries.rst )

@gaelforget
Copy link
Member

Hi! I spotted your tweet at https://twitter.com/GaelForget/status/1537033362543616005

@poikilotherm and I would like to invite you to move this repo to the @gdcc GitHub org, next to pyDataverse: https://github.com/gdcc/pyDataverse

Totally up to you, of course! 😄

Say the word and we'll create an empty repo, made you admin, etc. Thanks!

Thank you!! Sounds good to me -- absolutely! I am waiting on the package registration to go through ( JuliaRegistries/General#62370 ) before going back to clean some things up.

Next week maybe?

(Also, just to foreshadow a future step, we'd also love a pull request to update a future version of https://guides.dataverse.org/en/5.11/api/client-libraries.html to include Julia! Here's the source: https://github.com/IQSS/dataverse/blob/v5.11/doc/sphinx-guides/source/api/client-libraries.rst )

Sure. Could do that just after my cleaning up & the migration if that would work.

@gaelforget
Copy link
Member

gaelforget commented Jun 20, 2022

Did some updates and just posted a demo. Started a todo list for later #13

Here is a quick demo of Dataverse.jl

(v0.1.3, incl. notebook) https://t.co/Smw407XT3B pic.twitter.com/vNrvHXDyPI

— Gael Forget (@gaelforget) June 20, 2022
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>

@pdurbin
Copy link
Member Author

pdurbin commented Sep 21, 2022

@gaelforget hi! Just checking in. Even if the Julia bindings aren't complete, we're happy to include a link in the Dataverse API Guide. No rush. Just something to think about. 😄

@gaelforget
Copy link
Member

@gaelforget hi! Just checking in. Even if the Julia bindings aren't complete, we're happy to include a link in the Dataverse API Guide. No rush. Just something to think about. 😄

Thanks for the ping. Working on it now

@gaelforget
Copy link
Member

Say the word and we'll create an empty repo, made you admin, etc. Thanks!

Previously when I transferred repo ownership to an org on GitHub, I think that we proceeded by

  • creating a team on the org side for the repo owners
  • adding the repo to the team / making team admin of repo
  • inviting pkg dev to org member
  • adding pkg dev to the team

That's what we do in JuliaClimate and MITgcm for example.

On the org side, only someone with sufficient / owner privileges can create teams and so on. Details may depend on how you have the org set up.

One advantage, as compared to creating a fresh repo, is that everything in the original repo carries over -- i.e., issues, discussions, settings, ci, docs, zenodo links, webhooks, tags, etc. If instead of using the GitHub transfer mechanism I just push the git history into a fresh repo then the rest is lost.

@pdurbin , could we do the transfer this way via the GitHub ownership transfer?

@gaelforget
Copy link
Member

(Also, just to foreshadow a future step, we'd also love a pull request to update a future version of https://guides.dataverse.org/en/5.11/api/client-libraries.html to include Julia! Here's the source: https://github.com/IQSS/dataverse/blob/v5.11/doc/sphinx-guides/source/api/client-libraries.rst )

Done. Please refer to IQSS/dataverse#8991

@pdurbin
Copy link
Member Author

pdurbin commented Sep 23, 2022

@gaelforget thanks! You used the "closes" syntax so automation closed this issue. I guess you could re-open it since you said "closes in part". Exciting to have Juila support!

@poikilotherm
Copy link
Member

poikilotherm commented Sep 23, 2022

I'd have all the necessary permissions to do this move on gdcc side. We should take a look at this next week. Are you with us on Matrix? (chat.dataverse.org) I'm on during usual CEST working hours and sometimes after.

@gaelforget
Copy link
Member

I'd have all the necessary permissions to do this move on gdcc side. We should take a look at this next week. Are you with us on Matrix? (chat.dataverse.org) I'm on during usual CEST working hours and sometimes after.

Sounds good. Will join Matrix and should have time next week

@gaelforget gaelforget reopened this Sep 23, 2022
@pdurbin
Copy link
Member Author

pdurbin commented Nov 5, 2022

@gaelforget thanks for working on this today! 🎉

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

Successfully merging a pull request may close this issue.

3 participants