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

Repository clean-up #73

Open
ocefpaf opened this issue Jul 24, 2020 · 5 comments
Open

Repository clean-up #73

ocefpaf opened this issue Jul 24, 2020 · 5 comments

Comments

@ocefpaf
Copy link
Member

ocefpaf commented Jul 24, 2020

  • archive past tutorials and projects (links will still work)
  • rename tutorials to a common prefix (links will need to be fixed)
  • archive wiki, etc.

Ping @emiliom and @leewujung

@emiliom
Copy link
Member

emiliom commented Jul 25, 2020

  • archive past projects: 👍. Except when the project is still active, which will be the rare exception -- https://github.com/oceanhackweek/ohw19-project-co_locators may be the only one. Is it worth renaming repos to ensure, say, a consistent prefix? Should some project repos be deleted, if they never had much material to begin with? Specially older ones, from ohw18.
  • archive/rename past tutorials:
    • Tutorials have been developed and organized in different ways. Some (most) repos contain multiple tutorials (notebooks), while some tutorials were developed in individual repos
    • Is there room for a model where some tutorials can have a longer life, as opposed to restarting every year on a new repo? Can those have annual releases/branches to preserve the annual snapshot?
  • archive wiki, etc.:
    • We haven't the fate of the wiki is undetermined. We hid it from the OHW20 web site until we decided what to do with it. Also, I don't what this jekyll-hackweek-wiki repo is, but I assume it was an experiment that didn't go anywhere.
    • For comparison, see what ICESat-2 Hackweek did this year: a minimal web site, pointing to a Learning Resources built on MkDocs and serving the role of the wiki, former web site content pages (eg, schedule), and tutorial resources

@ocefpaf
Copy link
Member Author

ocefpaf commented Jul 25, 2020

  • archive past projects: +1. Except when the project is still active, which will be the rare exception -- oceanhackweek/ohw19-project-co_locators may be the only one. Is it worth renaming repos to ensure, say, a consistent prefix? Should some project repos be deleted, if they never had much material to begin with? Specially older ones, from ohw18.

@leewujung thought about that. Arching is reversible so the plan is to archive everything we can and, if someone wants to work on them, restore. Of course those that we know we'll use this year we are not archiving.

  • archive/rename past tutorials:

    • Tutorials have been developed and organized in different ways. Some (most) repos contain multiple tutorials (notebooks), while some tutorials were developed in individual repos
    • Is there room for a model where some tutorials can have a longer life, as opposed to restarting every year on a new repo? Can those have annual releases/branches to preserve the annual snapshot?

That is the goal. Archive the past, starting from 2020 we can do branches for the years and rename the directory to "OHW-tutorials."

  • archive wiki, etc.:

    • We haven't the fate of the wiki is undetermined. We hid it from the OHW20 web site until we decided what to do with it. Also, I don't what this jekyll-hackweek-wiki repo is, but I assume it was an experiment that didn't go anywhere.
    • For comparison, see what ICESat-2 Hackweek did this year: a minimal web site, pointing to a Learning Resources built on MkDocs and serving the role of the wiki, former web site content pages (eg, schedule), and tutorial resources

Same as the tutorials the goals is to archive what is "past" and hold that information in the pre-hackweek reository.

@leewujung
Copy link
Member

@ocefpaf : seems like it's time to archive the repos you listed above from OHW18-19, except for those that are still active, the co-locator.

For the wiki, we have 2 repos needing archival: wiki and jekyll-hackweek-wiki.

We also need to prefix past tutorials and fix any links referring to them (as much as possible).

Do you have time to do this or we could ask others to help?

@ocefpaf
Copy link
Member Author

ocefpaf commented Aug 31, 2020

We are down to 29 repos! Most of them are OHW19 tutorials and OHW20 projects.
See https://github.com/oceanhackweek?page=1&type=source

We'll try to move the OHW18 page to the same place as the OHW19/20 and archive it and the jekyll templates.

Also, we plan to archive the OHW19 tutorials once we consolidate things more for 2021.

@emiliom
Copy link
Member

emiliom commented Aug 31, 2020

We are down to 29 repos! Most of them are OHW19 tutorials and OHW20 projects.

🎉

We'll try to move the OHW18 page to the same place as the OHW19/20 and archive it and the jekyll templates.

That'd be awesome! I would've said it's not worth the effort, but hey, it's your time 😉

Also, we plan to archive the OHW19 tutorials once we consolidate things more for 2021.

Great.

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