[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#737559: marked as done (copyright-format: author != copyright, add an author field?)

Your message dated Fri, 11 Aug 2017 12:44:51 -0700
with message-id <87o9rlx51o.fsf@iris.silentflame.com>
and subject line Closing inactive Policy bugs
has caused the Debian Bug report #737559,
regarding copyright-format: author != copyright, add an author field?
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
737559: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737559
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: debian-policy

Author and copyright holder are not always the same person/entity.

E.g. the work may be authored by Bob but the copyright is assigned to
his employer Acme, Inc, e.g.

License: GPL2
Copyright: 2014, Acme, Inc http://acme.example.org
Author: Bob, http://example.org/bob

For cases where the License field contains the value public-domain and
the name of the author is known, it is not appropriate to put the name
in the license field, but it would be desirable to record the name of
the author, e.g.

License: public-domain
Copyright: none
Author: Bob, http://example.org/bob

This may also reflect real-life situations where contributor license
agreements require contributors to completely assign their intellectual
property to some organisation (such as FSF)

http://www.gnu.org/licenses/gpl-faq.html#AssignCopyright

Has this not already come up anywhere?  I found a related bug that deals
with part of the issue (must insert "none" in the Copyright field of
public-domain) but that is not the whole issue, maybe they can be
resolved together
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694883

--- End Message ---
--- Begin Message --- 
control: user debian-policy@packages.debian.org
control: usertag -1 +obsolete
control: tag -1 +wontfix

Russ Allbery and I did a round of in-person bug triage at DebConf17 and
we are closing this bug as inactive.

The reasons for closing fall into the following categories, from most
frequent to least frequent:

- issue is appropriate for Policy, there is a consensus on how to fix
  the problem, but preparing the patch is very time-consuming and no-one
  has volunteered to do it, and we do not judge the issue to be
  important enough to keep an open bug around;

- issue is appropriate for Policy but there does not yet exist a
  consensus on what should change, and no recent discussion.  A fresh
  discussion might allow us to reach consensus, and the messages in the
  old bug are unlikely to help very much; or

- issue is not appropriate for Policy.

If you feel this bug is still relevant and want to restart the
discussion, you can re-open the bug.  However, please consider instead
opening a new bug with a message that summarises and condenses the
previous discussion, updates the report for the current state of Debian,
and makes clear exactly what you think should change.

A lot of these old bugs have long side tangents and numerous messages,
and that old discussion is not necessarily helpful for figuring out what
Debian Policy should say today.

-- 
Sean Whitton

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: