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

Guidance on what to do when your package is approved #150

Closed
Rekyt opened this issue May 6, 2019 · 4 comments
Closed

Guidance on what to do when your package is approved #150

Rekyt opened this issue May 6, 2019 · 4 comments

Comments

@Rekyt
Copy link

Rekyt commented May 6, 2019

rromeo got approved recently by rOpenSci.
I noticed @sckott mentioned a couple of things to do once the package is approved.
In brief he mentioned transferring the repository and change the various links
It could be a useful thing to have somewhere in the development guide.

Woops, I just realized these comments were available in the "Approval comments template" Appendix. So maybe put them in a separate section "What to do when you package got approved by rOpenSci"?

I also struggled a little bit to change AppVeyor CI and didn't know what should be considered the best practice: should AppVeyor App be installed for the whole rOpenSci group?
As I was unsure, I enabled OAuth for AppVeyor to my whole GitHub account giving thus access to community organizations. And that let me create a new project using the transferred repo.

@maelle
Copy link
Member

maelle commented May 6, 2019

👋 @Rekyt!

I don't think having the checklist in an actual chapter would be useful since the maintainers get the checklist via the editor in the submission issue but I am open to suggestions on how to make things such as CI transfer clearer.

@Rekyt
Copy link
Author

Rekyt commented May 6, 2019

Thank you so much @maelle! Then I just need careful reading 👀 as everything is already out there...

@Rekyt Rekyt closed this as completed May 6, 2019
@maelle
Copy link
Member

maelle commented May 6, 2019

But really your advice as "naive reader" (as opposed to us who've worked on this guide) is super helpful so do not hesitate to give further suggestions and feedback, we want the guide to help maintainers!

@sckott
Copy link
Contributor

sckott commented May 6, 2019

thanks for the feedback @Rekyt

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

3 participants