You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
tailscale/licenses
Will Norris 3ec5be3f51 all: remove AUTHORS file and references to it
This file was never truly necessary and has never actually been used in
the history of Tailscale's open source releases.

A Brief History of AUTHORS files
---

The AUTHORS file was a pattern developed at Google, originally for
Chromium, then adopted by Go and a bunch of other projects. The problem
was that Chromium originally had a copyright line only recognizing
Google as the copyright holder. Because Google (and most open source
projects) do not require copyright assignemnt for contributions, each
contributor maintains their copyright. Some large corporate contributors
then tried to add their own name to the copyright line in the LICENSE
file or in file headers. This quickly becomes unwieldy, and puts a
tremendous burden on anyone building on top of Chromium, since the
license requires that they keep all copyright lines intact.

The compromise was to create an AUTHORS file that would list all of the
copyright holders. The LICENSE file and source file headers would then
include that list by reference, listing the copyright holder as "The
Chromium Authors".

This also become cumbersome to simply keep the file up to date with a
high rate of new contributors. Plus it's not always obvious who the
copyright holder is. Sometimes it is the individual making the
contribution, but many times it may be their employer. There is no way
for the proejct maintainer to know.

Eventually, Google changed their policy to no longer recommend trying to
keep the AUTHORS file up to date proactively, and instead to only add to
it when requested: https://opensource.google/docs/releasing/authors.
They are also clear that:

> Adding contributors to the AUTHORS file is entirely within the
> project's discretion and has no implications for copyright ownership.

It was primarily added to appease a small number of large contributors
that insisted that they be recognized as copyright holders (which was
entirely their right to do). But it's not truly necessary, and not even
the most accurate way of identifying contributors and/or copyright
holders.

In practice, we've never added anyone to our AUTHORS file. It only lists
Tailscale, so it's not really serving any purpose. It also causes
confusion because Tailscalars put the "Tailscale Inc & AUTHORS" header
in other open source repos which don't actually have an AUTHORS file, so
it's ambiguous what that means.

Instead, we just acknowledge that the contributors to Tailscale (whoever
they are) are copyright holders for their individual contributions. We
also have the benefit of using the DCO (developercertificate.org) which
provides some additional certification of their right to make the
contribution.

The source file changes were purely mechanical with:

    git ls-files | xargs sed -i -e 's/\(Tailscale Inc &\) AUTHORS/\1 contributors/g'

Updates #cleanup

Change-Id: Ia101a4a3005adb9118051b3416f5a64a4a45987d
Signed-off-by: Will Norris <will@tailscale.com>
3 days ago
..
README.md licenses: add README 11 months ago
android.md net/portmapper, go.mod: unfork our goupnp dependency 3 weeks ago
apple.md net/portmapper, go.mod: unfork our goupnp dependency 3 weeks ago
licenses.go all: remove AUTHORS file and references to it 3 days ago
tailscale.md licenses: update license notices 2 months ago
windows.md licenses: update license notices 2 months ago

README.md

Licenses

This directory contains a list of dependencies, and their licenses, that are included in the Tailscale clients. These lists are generated using the go-licenses tool to analyze all Go packages in the Tailscale binaries, as well as a set of custom output templates that includes any additional non-Go dependencies. For example, the clients for macOS and iOS include some additional Swift libraries.

These lists are updated roughly every week, so it is possible to see the dependencies in a given release by looking at the release tag. For example, the dependences for the 1.80.0 release of the macOS client can be seen at https://github.com/tailscale/tailscale/blob/v1.80.0/licenses/apple.md.

Other formats

The go-licenses tool can output other formats like CSV, but that wouldn't include the non-Go dependencies. We can generate a CSV file if that's really needed by running a regex over the markdown files:

cat apple.md | grep "^ -" | sed -E "s/- \[(.*)\]\(.*?\) \(\[(.*)\]\((.*)\)\)/\1,\2,\3/"

Reviewer instructions

The majority of changes in this directory are from updating dependency versions. In that case, only the URL for the license file will change to reflect the new version. Occasionally, a dependency is added or removed, or the import path is changed.

New dependencies require the closest review to ensure the license is acceptable. Because we generate the license reports after dependencies are changed, the new dependency would have already gone through one review when it was initially added. This is just a secondary review to double-check the license. If in doubt, ask legal.

Always do a normal GitHub code review on the license PR with a brief summary of what changed. For example, see #13936 or #14064. Then approve and merge the PR.