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 #697134, regarding [copyright-format] Introduce a syntax for BSD-3-Clause variants 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.) -- 697134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697134 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: [copyright-format] Introduce a syntax for BSD-3-Clause variants
- From: Jonathan Nieder <jrnieder@gmail.com>
- Date: Tue, 1 Jan 2013 12:41:57 -0800
- Message-id: <20130101204157.GB17933@elie.Belkin>
- In-reply-to: <878v8cit6g.fsf@windlord.stanford.edu>
- References: <20121224103152.GA5201@falafel.plessy.net> <50D99D72.90300@gmx.com> <50D9A0FD.7000409@gmx.com> <87hana3s10.fsf@windlord.stanford.edu> <50E2F4E8.7020509@gmx.com> <87licclthg.fsf@windlord.stanford.edu> <20130101190531.GB16387@elie.Belkin> <87han0iuhj.fsf@windlord.stanford.edu> <20130101193117.GE16387@elie.Belkin> <878v8cit6g.fsf@windlord.stanford.edu>
Package: debian-policy Version: 3.9.4.0 Severity: wishlist Russ Allbery wrote[1]: > Jonathan Nieder <jrnieder@gmail.com> writes: >>> Jonathan Nieder <jrnieder@gmail.com> writes: >>>> Russ Allbery wrote: >>>>> It might be worthwhile to recognize some sort of syntax similar to >>>>> license exceptions so that one can tag the license as "BSD-3-Clause by >>>>> <copyright holder>" or the like. >> [...] >>>> The next sentence "IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE >>>> LIABLE" also varies, and not always in the same way as the first. [...] >> If we change the syntax a little to allow arbitrary identifiers for >> each variant, à la "BSD-3-Clause, MIT variant #1", then I think I was >> just taking a long time to agree completely with your proposed change. >> ;-) > > Oh, yes, that would work. I missed that my proposed "by" syntax implied > that the only thing that changed was the copyright holder. Maybe > "variant" would be a better keyword, taking an arbitrary label. Filing to avoid forgetting. Thanks, Jonathan [1] http://bugs.debian.org/649530
--- End Message ---
--- Begin Message ---
- To: 617938-close@bugs.debian.org, 688363-close@bugs.debian.org, 821363-close@bugs.debian.org, 192571-close@bugs.debian.org, 215549-close@bugs.debian.org, 263448-close@bugs.debian.org, 276160-close@bugs.debian.org, 408500-close@bugs.debian.org, 562863-close@bugs.debian.org, 587377-close@bugs.debian.org, 592564-close@bugs.debian.org, 656569-close@bugs.debian.org, 663917-close@bugs.debian.org, 683570-close@bugs.debian.org, 684673-close@bugs.debian.org, 697134-close@bugs.debian.org, 704233-close@bugs.debian.org, 727754-close@bugs.debian.org, 737559-close@bugs.debian.org, 795783-close@bugs.debian.org, 832654-close@bugs.debian.org, 71621-close@bugs.debian.org, 120418-close@bugs.debian.org, 267142-close@bugs.debian.org, 291631-close@bugs.debian.org, 338219-close@bugs.debian.org, 375502-close@bugs.debian.org, 391240-close@bugs.debian.org, 397939-close@bugs.debian.org, 400112-close@bugs.debian.org, 412668-close@bugs.debian.org, 431109-close@bugs.debian.org, 457364-close@bugs.debian.org, 458824-close@bugs.debian.org, 462996-close@bugs.debian.org, 465140-close@bugs.debian.org, 466550-close@bugs.debian.org, 485559-close@bugs.debian.org, 491055-close@bugs.debian.org, 492144-close@bugs.debian.org, 521810-close@bugs.debian.org, 525843-close@bugs.debian.org, 528453-close@bugs.debian.org, 535577-close@bugs.debian.org, 541872-close@bugs.debian.org, 543417-close@bugs.debian.org, 549910-close@bugs.debian.org, 554194-close@bugs.debian.org, 570141-close@bugs.debian.org, 572571-close@bugs.debian.org, 580135-close@bugs.debian.org, 593177-close@bugs.debian.org, 610298-close@bugs.debian.org, 633994-close@bugs.debian.org, 660705-close@bugs.debian.org, 642914-close@bugs.debian.org, 663762-close@bugs.debian.org, 671503-close@bugs.debian.org, 681289-close@bugs.debian.org, 685992-close@bugs.debian.org, 690495-close@bugs.debian.org, 694384-close@bugs.debian.org, 775318-close@bugs.debian.org, 798714-close@bugs.debian.org, 524461-close@bugs.debian.org, 555981-close@bugs.debian.org, 682282-close@bugs.debian.org, 686143-close@bugs.debian.org, 515837-close@bugs.debian.org, 779506-close@bugs.debian.org, 628174-close@bugs.debian.org, 661417-close@bugs.debian.org, 681562-close@bugs.debian.org, 490605-close@bugs.debian.org, 647570-close@bugs.debian.org
- Subject: Closing inactive Policy bugs
- From: Sean Whitton <spwhitton@spwhitton.name>
- Date: Fri, 11 Aug 2017 12:44:51 -0700
- Message-id: <87o9rlx51o.fsf@iris.silentflame.com>
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 WhittonAttachment: signature.asc
Description: PGP signature
--- End Message ---