You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This repository has some documents that people may want to cite. For example, the overview file has a bunch of useful info not found anywhere else.
GitHub has official documentation on how to make repositories citable here by using Zenodo to generate Digital Object Identifiers (DOIs).
If the WASI team does not have bandwidth to do this. May I fork the repo and archive it on Zenodo? Preferably the owners of the repo can do it so it can stay up to date.
Here's an instructional video I found that teaches you how to integrate GitHub with Zenodo so that DOIs are created automatically.
Because Zenodo requires access at the organization level and not just the repo level, I don't have the rights to grant the permissions it needs. I'll need to run this by the WebAssembly CG chairs and have them grant access..
It also requires cutting releases, which is something that we haven't historically done. I don't see any reason not to, but would like to bring it up in a subgroup meeting to make sure no one else sees a problem with that.
The next subgroup meeting is next Thursday, so I'll hopefully have an answer shortly after that.
Just to provide a quick update here, we will be enabling this (unless there are any unforeseen technical difficulties). There are a couple of remaining steps which I'll need to work with the CG chairs to complete, but they've already been helping with this so I don't expect that to be an issue.
Activity
linclark commentedon Nov 23, 2020
I'll go ahead and take a crack at this. Will report back if I run into any problems.
linclark commentedon Nov 24, 2020
Quick update:
Because Zenodo requires access at the organization level and not just the repo level, I don't have the rights to grant the permissions it needs. I'll need to run this by the WebAssembly CG chairs and have them grant access..
It also requires cutting releases, which is something that we haven't historically done. I don't see any reason not to, but would like to bring it up in a subgroup meeting to make sure no one else sees a problem with that.
The next subgroup meeting is next Thursday, so I'll hopefully have an answer shortly after that.
linclark commentedon Dec 9, 2020
Just to provide a quick update here, we will be enabling this (unless there are any unforeseen technical difficulties). There are a couple of remaining steps which I'll need to work with the CG chairs to complete, but they've already been helping with this so I don't expect that to be an issue.
Add DOI link to README
Add DOI link to README
Add DOI link to README
Add DOI link to README