geneontology / helpdesk

The Gene Ontology Helpdesk
http://help.geneontology.org
16 stars 6 forks source link

Clarify CC BY 4.0 licensing terms for attribution #423

Closed kltm closed 1 year ago

kltm commented 1 year ago

We recently received an email on the helpdesk asking for specific guidance WRT attribution for the GO as defined in the CC BY 4.0 license within the context of an online platform. Currently, we do not give such specific guidance and only refer to the license itself. We should define what attribution should be given for data reuse, with examples for a couple of categories so that our intent is clear.

kltm commented 1 year ago

Wording for CC BY 4.0 attribution; section 3a of: https://creativecommons.org/licenses/by/4.0/legalcode

CC BY 4.0 attribution elements: https://wiki.creativecommons.org/wiki/License_Versions#Detailed_attribution_comparison_chart

pgaudet commented 1 year ago

Whatever new text we agree on should also go on this page: http://geneontology.org/docs/go-citation-policy/

kltm commented 1 year ago

Okay, after the managers' call, I'll go ahead and put something together that hits the points of:

kltm commented 1 year ago

Text added. Not sure who is "owner" here. Added to "GO Website Improvements" for lack of better location.

kltm commented 1 year ago

@suzialeksander Ah--you're owner!

suzialeksander commented 1 year ago

I think the only thing to be added here, possibly, are links to each software licence. I'm not sure what the complete list is- Amigo, PANTHER, Noctua ??. It would be nice to have a kinda current list of active-ish tools.

@kltm what tools/licences are we missing?

kltm commented 1 year ago

I think the scope of this ticket is specifically the changes to the CC BY 4.0 verbiage wrt what qualifies as attribution.

Software licensing should be another matter or ticket. Technically speaking, every software repo needs to have a LICENSE file at the top level: https://github.com/orgs/geneontology/repositories (there are a lot)

suzialeksander commented 1 year ago

OK that settles it for me. @pgaudet does this new text look sufficient to close this ticket?

pgaudet commented 1 year ago

Just wondering - is the '2023-01-01 release' an example?

If that's the case, it may be better to have YYYY-MM-DD release', so this dont look out of date in a few months/years?

kltm commented 1 year ago

@pgaudet For example, if you are... I think that it's clear that it's an example, but please feel free to change the text to whatever you feel is necessary to close this out.

suzialeksander commented 1 year ago

@pgaudet I do also try and update the years that appear in the text of the site so it doesn't look old, including the FAQ but also these other pages. It's fairly trivial to update these every year or two, like the copyright dates.