Re: a Constitutional interpretation question

2025-04-10 Thread Kurt Roeckx
On Wed, Apr 09, 2025 at 11:31:24AM -0700, Russ Allbery wrote: > > Obviously Kurt has the final say, but if he were to ask me my opinion, > that's what I'd tell him. Is there a need for me to actually make a ruling, or is this just a theoretic question? I prefer not to make a ruling unless it's ac

Re: a Constitutional interpretation question

2025-04-10 Thread G. Branden Robinson
Hi Ian, A brief message from me this time! At 2025-04-10T17:50:16+0100, Ian Jackson wrote: [...] > You're right that we're suffering because of the lack of working > mechanisms, short of GR, for situations like this. I agree with you and Russ that my interpretation "challenge" is not an urgent m

Re: a Constitutional interpretation question

2025-04-10 Thread Ian Jackson
Gerardo Ballabio writes ("Re: a Constitutional interpretation question"): > Ian Jackson wrote: > > I'm not sure this cleanup is a useful use of our time. > > There are more fundamental problems. > > We've just been having a several-dozen-messages-long thread on -vote > about a GR proposal that you

Re: a Constitutional interpretation question

2025-04-10 Thread Russ Allbery
I'm not sure there's much utility in going back and forth on this more, since I think we've both adequately stated our opinion, but I couldn't resist adding a bit more explanation. "G. Branden Robinson" writes: > Yes, but the list _is_ in upright rather than slanted text, making it > normative p

Re: a Constitutional interpretation question

2025-04-10 Thread Matthew Vernon
Russ Allbery writes: > I am not the project secretary, just one random developer, but for > whatever it's worth, I think this interpretation of the constitution is > incorrect and the TC does not have the ability to override a delegate. I am the current TC Chair; what follows is my opinion (whic

Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion

2025-04-10 Thread Simon Josefsson
Matthias Urlichs writes: > On 08.03.25 15:36, Simon Josefsson wrote: >> One difference is that you could chose to trust their hardware (CPUs) >> but don't trust their software (non-free firmware). > > True. But so, again, what's the material difference between "the > firmware is baked into the ha

Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion

2025-04-10 Thread Henrik Ahlgren
Matthias Urlichs writes: > On 08.03.25 15:36, Simon Josefsson wrote: >> One difference is that you could chose to trust their hardware (CPUs) >> but don't trust their software (non-free firmware). > > True. But so, again, what's the material difference between "the > firmware is baked into the ha

Re: a Constitutional interpretation question

2025-04-10 Thread Gerardo Ballabio
IMHO, any time there is a dispute on a technical issue, the Technical Committee is the natural place where the issue should be brought if it can't be resolved between the persons involved, regardless of whether they are DDs, delegates, DPL or whatever, *and* it should have the power to ultimately e

Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion

2025-04-10 Thread tomas
On Thu, Apr 10, 2025 at 10:06:12AM +0200, Matthias Urlichs wrote: > On 08.03.25 15:36, Simon Josefsson wrote: > > One difference is that you could chose to trust their hardware (CPUs) > > but don't trust their software (non-free firmware). > > True. But so, again, what's the material difference be

Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion

2025-04-10 Thread Matthias Urlichs
On 08.03.25 15:36, Simon Josefsson wrote: One difference is that you could chose to trust their hardware (CPUs) but don't trust their software (non-free firmware). True. But so, again, what's the material difference between "the firmware is baked into the hardware and cannot be changed" vs. "t