-
Notifications
You must be signed in to change notification settings - Fork 93
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 Issues from Spec Registries to DID Core #367
Comments
This is waiting on me to move things over. |
I have still not done this, I'm trying to preserve history... need to track down the tool to do that. |
I've gone through them all and many of them look semi addressed at this point. I've left comments to get authors to respond if they still want to transfer the issues to did-core and if so I can do it @msporny (from the looks of it I can handle it with my permissions on the two repos) |
@kdenhartog wrote:
Yes, please move them if you have permissions to do so @kdenhartog ... I am utterly failing to get to this item on my todo list. There is some tool on the Internet that lets you move Github issues (along with all comments) from one repo to another. It's not perfect, all comments show up as you (but it saves the original commenters name somehow). I believe @kimdhamilton used this tool at some point in the distant past. Thank you in advance @kdenhartog! |
@kdenhartog can you update us on the status of this? |
The only issue that was left has been moved: #478 The rest have either been addressed in a PR and closed/pending close or were no longer relevant and closed. I suggest declaring this issue complete and will label it pending close. |
No objections raised since marked pending close, closing. |
Not getting enough contribution to the following spec registries issues: https://github.com/w3c/did-spec-registries/issues?q=is%3Aissue+is%3Aopen+label%3Amove-to-did-core
proposing we move them to did core.
The text was updated successfully, but these errors were encountered: