mirror of
https://github.com/tailscale/tailscale.git
synced 2026-02-07 22:42:02 -05:00
3ec5be3f51
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>
74 lines
2.0 KiB
Go
74 lines
2.0 KiB
Go
// Copyright (c) Tailscale Inc & contributors
|
||
// SPDX-License-Identifier: BSD-3-Clause
|
||
|
||
// Only built on 64-bit platforms to avoid complexity
|
||
|
||
//go:build amd64 || arm64 || mips64le || ppc64le || riscv64
|
||
|
||
package cstruct
|
||
|
||
import "fmt"
|
||
|
||
// This test provides a semi-realistic example of how you can
|
||
// use this package to decode a C structure.
|
||
func ExampleDecoder() {
|
||
// Our example C structure:
|
||
// struct mystruct {
|
||
// char *p;
|
||
// char c;
|
||
// /* implicit: char _pad[3]; */
|
||
// int x;
|
||
// };
|
||
//
|
||
// The Go structure definition:
|
||
type myStruct struct {
|
||
Ptr uintptr
|
||
Ch byte
|
||
Intval uint32
|
||
}
|
||
|
||
// Our "in-memory" version of the above structure
|
||
buf := []byte{
|
||
1, 2, 3, 4, 0, 0, 0, 0, // ptr
|
||
5, // ch
|
||
99, 99, 99, // padding
|
||
78, 6, 0, 0, // x
|
||
}
|
||
d := NewDecoder(buf)
|
||
|
||
// Decode the structure; if one of these function returns an error,
|
||
// then subsequent decoder functions will return the zero value.
|
||
var x myStruct
|
||
x.Ptr = d.Uintptr()
|
||
x.Ch = d.Byte()
|
||
x.Intval = d.Uint32()
|
||
|
||
// Note that per the Go language spec:
|
||
// [...] when evaluating the operands of an expression, assignment,
|
||
// or return statement, all function calls, method calls, and
|
||
// (channel) communication operations are evaluated in lexical
|
||
// left-to-right order
|
||
//
|
||
// Since each field is assigned via a function call, one could use the
|
||
// following snippet to decode the struct.
|
||
// x := myStruct{
|
||
// Ptr: d.Uintptr(),
|
||
// Ch: d.Byte(),
|
||
// Intval: d.Uint32(),
|
||
// }
|
||
//
|
||
// However, this means that reordering the fields in the initialization
|
||
// statement–normally a semantically identical operation–would change
|
||
// the way the structure is parsed. Thus we do it as above with
|
||
// explicit ordering.
|
||
|
||
// After finishing with the decoder, check errors
|
||
if err := d.Err(); err != nil {
|
||
panic(err)
|
||
}
|
||
|
||
// Print the decoder offset and structure
|
||
fmt.Printf("off=%d struct=%#v\n", d.Offset(), x)
|
||
// Output: off=16 struct=cstruct.myStruct{Ptr:0x4030201, Ch:0x5, Intval:0x64e}
|
||
}
|