-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
mandatory and suggested copy-edits #51
Conversation
I wonder if the date range of "2020–2023" is required on the license notice. I did not remove it. But I understand that current advice is that this is not necessary and generally best avoided? Consult a lawyer perhaps! |
these diffs are optional |
Note that these four new definitions are not well developed, rather they are provisional and should it be decided they should remain, they could be worked up. |
That finishes my suggestions. I had though I could submit multiple PRs but it seems that just one outstanding PR is possible. In which case, I would not have named it "mandatory copy-edits". |
Just renamed the PR as indicated above. But I am done in any case. |
Thanks @robbiemorrison for these changes. To speed up the process, I cherry picked them, with some changes, in #52, so closing this now. |
Good luck. And am looking forward to promoting this standard following approval and publication in the areas of open science and transparent public policy analysis. |
mandatory copy-edits — with all further PRs optional: