14 Commits (bfa90ea9b38e1b20c9944abade6258db6e3d4157)

Author	SHA1	Message	Date
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>	5 days ago
Andrew Lytvynov	eb6883bb5a	go.mod: upgrade nfpm to v2 (#8786) ... Upgrade the nfpm package to the latest version to pick up 24a43c5ad7. The upgrade is from v0 to v2, so there was some breakage to fix. Generated packages should have the same contents as before. Updates https://github.com/tailscale/tailscale/issues/1882 Signed-off-by: Andrew Lytvynov <awly@tailscale.com>	3 years ago
Will Norris	71029cea2d	all: update copyright and license headers ... This updates all source files to use a new standard header for copyright and license declaration. Notably, copyright no longer includes a date, and we now use the standard SPDX-License-Identifier header. This commit was done almost entirely mechanically with perl, and then some minimal manual fixes. Updates #6865 Signed-off-by: Will Norris <will@tailscale.com>	3 years ago
Anton Tolchanov	e8b695626e	cmd/mkpkg: allow specifying recommended dependencies ... Updates #3151 Signed-off-by: Anton Tolchanov <anton@tailscale.com>	3 years ago
Xe Iaso	55161b3d92	cmd/mkpkg: use package flag (#4373) ... Also removes getopt Signed-off-by: Xe <xe@tailscale.com>	4 years ago
Xe Iaso	be861797b4	cmd/mkpkg: add name argument (#4372) ... * shell.nix: rename goimports to gotools Signed-off-by: Xe <xe@tailscale.com> * cmd/mkpkg: allow specifying description and name in flag args Signed-off-by: Xe <xe@tailscale.com>	4 years ago
David Anderson	1c6946f971	cmd/mkpkg: allow zero files in a package. ... Signed-off-by: David Anderson <danderson@tailscale.com>	5 years ago
Dmytro Shynkevych	68a173bc24	cmd/mkpkg: support adding empty directories. ... Signed-off-by: Dmytro Shynkevych <dmytro@tailscale.com>	6 years ago
Sylvain Rabot	a279032998	cmd/mkpkg: fix missing default value for --depends ... Signed-off-by: Sylvain Rabot <sylvain@abstraction.fr>	6 years ago
David Anderson	ba2774ea27	cmd/mkpkg: support depending on stuff. ... Signed-off-by: David Anderson <dave@natulte.net>	6 years ago
David Anderson	20da44eae3	cmd/mkpkg: support scripts for rpm as well.	6 years ago
David Anderson	21fc5ec371	cmd/mkpkg: support specifying that a package replaces another. ... Both RPM and Deb require us to specify both Replaces and Conflicts: Conflicts tells them that the packages cannot coexist on the system, Replaces tells them which one to keep.	6 years ago
David Anderson	accf868130	cmd/mkpkg: add flags for debian scripts.	6 years ago
David Anderson	cc44e8a443	cmd/mkpkg: add small wrapper around nfpm to build deb/rpm packages. ... Signed-Off-By: David Anderson <dave@natulte.net>	6 years ago