Bug#975637: debian-policy: deprecate Rules-Requires-Root other than "no", "binary-targets" in Debian

2020-12-01 Thread Sam Hartman
> "Ansgar" == Ansgar writes: Ansgar> using other choices of "Rules-Requires-Root" than "no" and Ansgar> "binary-targets". The query [1] found two uses: Can you help me understand how options other than binary-targets or no were supposed to work/what they make possible? I have found

Bug#975250: clarify gathering together of copyright information

2020-12-01 Thread Sam Hartman
Here's my take on the discussion so far. And I want to stress that I am not a policy editor, and to the extent that they read the discusssion differently than I do, their reading controls. * Russ and I would be willing to accept either outcome--either you can collapse years or you cannot. * Hol

Bug#975637: debian-policy: deprecate Rules-Requires-Root other than "no", "binary-targets" in Debian

2020-12-01 Thread Ansgar
On Tue, 2020-12-01 at 08:00 -0500, Sam Hartman wrote: > > > > > "Ansgar" == Ansgar  writes:     Ansgar> using other choices of "Rules-Requires-Root" than "no" and     Ansgar> "binary-targets".  The query [1] found two uses: Can you help me understand how options other than binary-targets or no w

Bug#975250: clarify gathering together of copyright information

2020-12-01 Thread Guillem Jover
On Thu, 2020-11-26 at 08:55:21 +, Holger Levsen wrote: > AIUI the first year of contributions and the last year of contributions are > important data points for each contributor for a project, and mostly only > the last year as that might be used to calculate when a project becomes > public dom

Bug#975250: clarify gathering together of copyright information

2020-12-01 Thread Russ Allbery
Guillem Jover writes: > Personally I see a big distinction between someone doing it for their > own copyright claims, and doing that for someone else's. Yeah, this is where I'm at too. It feels weird, and I'm not sure it's technically compliant with the license requirement to preserve the copyr

Bug#975250: clarify gathering together of copyright information

2020-12-01 Thread Sam Hartman
> "Russ" == Russ Allbery writes: Russ> That said, I tend to be hyper-conservative and nit-picky about Russ> things like this, accurately representing copyright years Russ> isn't in my top thousand things I want people to work on in Russ> Debian, and I'm highly dubious that it

Bug#975250: clarify gathering together of copyright information

2020-12-01 Thread Bill Allombert
On Tue, Dec 01, 2020 at 02:03:59PM -0500, Sam Hartman wrote: > > "Russ" == Russ Allbery writes: > > Russ> That said, I tend to be hyper-conservative and nit-picky about > Russ> things like this, accurately representing copyright years > Russ> isn't in my top thousand things I wan

Bug#975250: clarify gathering together of copyright information

2020-12-01 Thread Sam Hartman
> "Bill" == Bill Allombert writes: Bill> Let us be honest with ourselves: what matter for most purpose Bill> is the position of the ftp-master team that processes the NEW Bill> queue. What policy says is secondary. I absolutely agree we should coordinate appropriately with the f

Bug#975250: clarify gathering together of copyright information

2020-12-01 Thread Holger Levsen
On Tue, Dec 01, 2020 at 02:03:59PM -0500, Sam Hartman wrote: > My rationale is that debian/copyright is a summary, it's not the license > text in the files. > I absolutely agree we shouldn't go change people's actual copyright > notices in the files. that. and what Bill said. > As a copyright hol