Everything an open source maintainer needs to know about open source licensing about benbalter.github.com

[mlinksva]

Needs seems too strong. Disproved by existence of successful open source maintainers who know zero or less about most of the topics listed. Maybe might need? 😁

[lee-dohm]

Q: If I fork a project (in the traditional sense as opposed to the GitHub sense), what is the expectation for me to include in the copyright/license/readme/other documentation? Do I add my name to the original copyright line in the license? Do I include some note in the README that the code originated somewhere else? Something else? All of the above?

[lee-dohm]

Q: Why do end-user applications like Atom have huge license documents that list every component and sub-component and sub-sub-component but other times (most notably when writing a library) only the license for the actual component is included? How do I know when to do which?

[benbalter]

WIP over in #445.

[benbalter]

❤️

what is the expectation for me to include in the copyright/license/readme/other documentation? Do I add my name to the original copyright line in the license? Do I include some note in the README that the code originated somewhere else? Something else? All of the above?

Kinda covered that. TL;DR: It depends on the particular licenses requirements. Some e.g., require documenting changes (which I argue a Git history is sufficient to do).

Why do end-user applications like Atom have huge license documents that list every component and sub-component and sub-sub-component but other times (most notably when writing a library) only the license for the actual component is included? How do I know when to do which?

Again, depends on the license. Some require that all derivative works require a copy of the upstream project's license, others require only copyright, others nothing.

Needs seems too strong. Disproved by existence of successful open source maintainers who know zero or less about most of the topics listed. Maybe might need?

👍

[benbalter]

https://ben.balter.com/2017/11/28/everything-an-open-source-maintainer-might-need-to-know-about-open-source-licensing/