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 r4ss into nmfs-stock-synthesis organization? #815

Open
1 of 6 tasks
iantaylor-NOAA opened this issue May 25, 2023 · 0 comments
Open
1 of 6 tasks

Move r4ss into nmfs-stock-synthesis organization? #815

iantaylor-NOAA opened this issue May 25, 2023 · 0 comments
Assignees
Labels
style/refactor issues related to cleaning up the code that won't change the user experience
Milestone

Comments

@iantaylor-NOAA
Copy link
Contributor

Moving the r4ss repo (and potentially ss3sim) into the nmfs-stock-synthesis organization (which didn't exist when the r4ss organization on github was created) could consolidate some of the overhead associated with having these related repositories in separate places.

Checklist below copied from nmfs-ost/ss3-workflows#30.

  • move over the r4ss/shiny-selex repo
  • Learn from this experience to decide the details of how to migrate r4ss
  • Clean up other r4ss org repos that aren't used (e.g., r4ss::SS_utils can probably just be deleted; likely true for other repos)
  • Move r4ss over to nmfs-stock-synthesis
  • Announce move of r4ss in release notes
  • Decide on strategy for redirecting folks to the new location of r4ss (e.g., looking at apps that depend on r4ss and letting them know about the change? Potentially forking the new location of r4ss back to the old and adding a message upon trying to download or use r4ss from the old location?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
style/refactor issues related to cleaning up the code that won't change the user experience
Projects
None yet
Development

No branches or pull requests

1 participant