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

Put BOSC 2019 program somewhere more permanent #9

Open
nlharris opened this issue Jul 26, 2019 · 3 comments
Open

Put BOSC 2019 program somewhere more permanent #9

nlharris opened this issue Jul 26, 2019 · 3 comments
Assignees

Comments

@nlharris
Copy link
Member

Zenodo?

(Note: this isn't really about the website, but the bosc_materials repo doesn't seem to have an issue tracker.)

@nlharris nlharris self-assigned this Jul 26, 2019
@hlapp hlapp transferred this issue from OBF/homepage Jul 28, 2019
@hlapp
Copy link
Member

hlapp commented Jul 28, 2019

Enabled issues for this repo, and then transferred issue from the OBF/homepage repo.

@hlapp
Copy link
Member

hlapp commented Jul 28, 2019

@nlharris the program is already here in the repo, so I assume you mean permanent archival? Have we done this for previous years?

It'd easy to activate integration with Zenodo such that every time you make.a release, this repo is automatically archived on Zenodo. Or more precisely, whatever the release includes is archived. We could, for example, create a release with only the program as content. However, if you also consider post-editing the metadata for the archive so that the authors are correct (by default, the Zenodo takes the authors from the commit history), then it's probably just as much or perhaps less effort to archive the program on Zenodo by hand.

@peterjc
Copy link
Member

peterjc commented Jul 29, 2019

Zenodo's GitHub integration seems far more suited to software in a repository, not how we are using the BOSC materials repository.

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