Bart Martens wrote: > Some readers may argue that an "upstream contact" may not be an "author" if > he/she maintains the upstream software only by accepting patches created by > others.
If so, won't that be a problem everywhere else in policy that refers to upstream authors? For example in section 4.3: If changes to the source code are made that are not specific to the needs of the Debian system, they should be sent to the upstream authors in whatever form they prefer so as to be included in the upstream version of the package. And in section 10.1: Feel free to override the upstream author's ideas about which compilation options are best: they are often inappropriate for our environment. If the notion of an author of a compilation who didn't write any of the individual parts is considered too subtle, these could be changed to 'upstream maintainer' without changing the meaning. -- To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120628095220.GA5625@burratino