-
Notifications
You must be signed in to change notification settings - Fork 1
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
Documentation licences and authorship #3
Comments
As mentioned just a moment ago, a recommendation will be coming to the panel for its prompt consideration. CC BY 4.0 will be the proposal.
This chain of provenance (if you will) should be recorded in the Document control section of the colophon e.g. https://labs.gbif.org/documents/effective-nodes-guidance/en/#_document_control. Note that this is in keeping with the Creative Commons legal code, which notes that 'If [a licensed] work is shared in an adapted version, it must be indicated that it is a modified version.'
Yes, as and where needed, definitely.
I would propose that the Secretariat should facilitate this, based on requests for guidance and direction from commissioned authors.
See above.
Thanks for noticing this fine distinction! For the past 4-5 years, GBIF has had a policy of publishing documents with institutional authorship, e.g. GBIF Secretariat. By way of giving some individual credit on these works, however, we cite those who would more generally be considered authors and coauthors as 'Contributors'. Thus, you see @melianieraymond et al. listed as contributors to the nodes guidance doc. I see no good reason not to call authors 'Authors' in commissioned documentation. We should use AsciiDoc conventions. I'll add the relevant 'Autores' element to the OpenRefine guide now. Let me know if you'd like to have your email(s) included (as corresponding author(s)). |
Works as directed in the rendered document, even if it looks a little dicey in the raw form. |
A resolution/document is needed from the EP (in principle) on how to deal with licences and authorship for the documentation. I put this two together as they might overlap in some points...
Some of the topics that would need to be addressed are:
The text was updated successfully, but these errors were encountered: