Kendra Albert

PDFR44 | About the Guide This guide covers how to make it easier for others to use your software and how to build on the software that others have written. Today, science involves software. And although many scientists understand that their work stands on the shoulders of others, they may not know how copyright affects their rights to use others’ software, or how they can publish their software tools so others can use or cite it. The Copyright Guide to Scientific Software, a joint project of the Harvard Cyberlaw Clinic and the Center for Astrophysics, in association with the Software Preservation Network, aims to fill that gap, by providing clear, easy-to-read answers to common questions about how scientific software and copyright interact | This guide is aimed at scientists in the United States – we solely focus on U.S. copyright law. If you’re outside the United States or have questions about how copyright applies across international borders, consult a local lawyer | NOTE: Copyright covers the creative portions of any software, but not the underlying facts or ideas | The longer, more complex, and more creative the code is, the more likely it is to be protected. Shortcode, directly tied to underlying equations, or simply a standard implementation of a well-known algorithm is less likely to be protected. Even if the actual lines of code aren’t protected by copyright, the general structure and organization of the code might be protected | ARCHIVE: https://zenodo.org/record/1327327 | https://opensource.org/faq | Implied Copyright Information: http://www.cardozoaelj.com/wp-content/uploads/2014/01/Newman-32-3.pdf | Only the copyright owner can give legal permission for others to copy, modify, or distribute the work (license - https://opensource.org/licenses) | https://choosealicense.com/ | Remember that the Creative Commons licenses are not for software | Attribution Assurance License: https://opensource.org/licenses/AAL | Citation File Format (CFF) - https://citation-file-format.github.io/ | https://guides.github.com/activities/citable-code/ | https://codemeta.github.io/ | More Information - https://arxiv.org/abs/1905.08674 & https://www.software.ac.uk/how-cite-software | Open Source Initiative - https://opensource.org/licenses | Fair Use Applications - https://www.law.cornell.edu/uscode/text/17/107 & https://www.softwarepreservationnetwork.org/bp-fair-use/ |

NOTE: This article is from a LEGAL basis and not from an everyday, exchange with colleagues type of scenario. This means that if code is created and inputted into a corporation, they want a remedy available & https://fairuse.stanford.edu/overview/fair-use/ |

Contents

1. Acknowledgments
2. Who is this Guide For? pg. 1
3. What Does Copyright Have to Do With Software? pg. 2
4. What should I do With the Code I've Written? pg. 4
5. When Can I Use Code Someone Else Has Written? pg. 7
6. References pg. 11
7. Images pg. 13

SA - Patents
RT - Citation
BT - Remedies
NT - Property
UF - To protect the authors of computer code.
SN - An article to guide computer code authors in protecting their property. (This entry does not reference a hierarchical list)… (altro)