New answers tagged

3

It is normal for each rightsholder to add a copyright line to freely-licensed code. Who the rightsholder is in this case is a function of the contract between your company and the one that did the work. If the contract specifies that you own the rights in the work, the line should say something like Copyright (c) YourCompany 2020 Otherwise, they own the ...


5

Some projects such as Linux ask for the DCO to be signed in order to do due diligence, and ultimately to protect downstream users. The DCO does not forbid projects from establishing individual processes, such as requiring that it's clearly the committer who has signed off on the commit and to have a clear means of contact later. This has nothing to do with ...


1

A single repository can contain multiple, independent, copyrighted works. There is no requirement anywhere that the contents of one repository must be under a single license. And independent works have the property that their copyright licenses don't affect each other. Based on that, there is very little against a repository that contains both open-source ...


2

The source code itself is available here: https://android.googlesource.com/platform/sdk/+/master/ There is Android Rebuilds project which provides binaries build for this source code without non-free EULA: https://android-rebuilds.beuc.net/


2

Open source style collaboration within a company or group of companies is called inner source. Within a legal entity, no special licensing is needed. Collaboration can be based on (non-binding) internal policies. But between legal entities (e.g. subsidiaries), custom licenses can be useful to establish boundaries of use and contractual obligations. E.g. DB ...


Top 50 recent answers are included