diff options
author | Lars Wirzenius <liw@liw.fi> | 2021-05-16 08:07:25 +0000 |
---|---|---|
committer | Lars Wirzenius <liw@liw.fi> | 2021-05-16 08:07:25 +0000 |
commit | 4d88c47cedf4f901157d948ff091b48437e503cb (patch) | |
tree | 3837703b511f0cba315de3ace56ae59c36f5488a | |
parent | 0709f8146606cae947e6c80b9a19c6cbb961e016 (diff) | |
parent | 3fbe745e47e84754d4f4ab7e8cb8925ec6d8c68f (diff) | |
download | ideas-4d88c47cedf4f901157d948ff091b48437e503cb.tar.gz |
Merge branch 'sponsored-by' into 'main'
add sponsored-by.md
See merge request larswirzenius/ideas!9
-rw-r--r-- | sponsored-by.md | 69 |
1 files changed, 69 insertions, 0 deletions
diff --git a/sponsored-by.md b/sponsored-by.md new file mode 100644 index 0000000..2c5c7ec --- /dev/null +++ b/sponsored-by.md @@ -0,0 +1,69 @@ +# Executive summary + +To make sponsorship of free and open source software more visible, add +a `Sponsored-By` pseudo-header to git commit messages. + +# The problem + +Free and open source software is sometimes funded by its authors: they +work on it in their free time. Sometimes development is funded by a +company who employs people to develop the software. Sometimes it's +fully or partially funded by donations or gifts: some party gives +money to the developers so they can work on the software, but not as +employment; we call this sponsorship. + +Overall, for any particular project, it's unclear how it's funded. +Sometimes the project makes it clear, but often it's not clear. In a +large project, with partied funding parts of the work such as the +Linux kernel, it's hard to keep track of who funds the work. Currently +it is done by heuristics based on author commit email addresses. + +One of the problems is that employment and sponsorship tends to be +scarce, and difficult to get, and even many important, popular +software projects do not have people who can work on it full time. +This hurts the quality of the software, and slows down its development +significantly. + +# A partial solution + +We propose that it would help to make sponsorship more obvious. Apart +from the project's web site, each commit could label the work as +sponsored using a pseudo-header: + +~~~ +Sponsored-by: Example Corp. +~~~ + +Any commits done as part of sponsored work would have this. This would +raise the visibility of sponsorship, thereby hopefully making it more +interesting to sponsor. + +# Specification + +We suggest the following specification as a base of discussion: + +* sponsorship of work to produce a commit is marked by one or more + `Sponsored-by` pseudo-headers in the commit message +* lack of such a header does not say anything about whether the work + was sponsored; use of the header is optional +* a header only applies to the commit it appears in +* all headers referring to the same sponsor should try to use the same + value so it's easier to collect statistics +* the value has the same format as a git commit author field; it can + be a bare email address, or lack an email address +* the special value `author` means the work was done without + sponsorship + +Examples: + +* `Sponsored-by: author` +* `Sponsored-by: Lars Wirzenius <liw@liw.fi>` +* `Sponsored-by: Wikimedia Foundation` +* `Sponsored-by: IBM <https://www.ibm.com/>` + + +--- +title: Sponsored-By in git commit messages +author: L.W. and D.S. +documentclass: report +... |