Bug#975075: tech-ctte: Should maintainers be able to block init compatibility changes?

2020-11-19 Thread Elana Hashman
On Thu, Nov 19, 2020 at 04:20:46PM -0800, Tianon Gravi wrote: > > On Wed, 18 Nov 2020 at 23:33, Josh Triplett wrote: > > Any inclusion of work into a package necessitates *some* amount of > > development and packaging resources by the maintainer of that package. > > Even if someone else offers

Bug#975075: tech-ctte: Should maintainers be able to block init compatibility changes?

2020-11-19 Thread Tianon Gravi
(Going to leave my own opinions on the underlying discussion here aside, but wanted to highlight/echo this bit:) On Wed, 18 Nov 2020 at 23:33, Josh Triplett wrote: > Any inclusion of work into a package necessitates *some* amount of > development and packaging resources by the maintainer of that

Bug#971515: Status as of last tech-ctte meeting

2020-11-19 Thread Josh Triplett
On Wed, Nov 18, 2020 at 10:26:21AM -0800, Russ Allbery wrote: > There are a lot of fascinating edge cases and precedents and philosophical > questions about the function of a distribution here, and I think they > rightfully attract a lot of energy, but I'm worried this is at the cost of > losing

Bug#975075: tech-ctte: Should maintainers be able to block init compatibility changes?

2020-11-19 Thread Josh Triplett
On Thu, 19 Nov 2020 13:04:56 -0700 Sean Whitton wrote: > On Wed 18 Nov 2020 at 11:18PM -08, Josh Triplett wrote: > > First, as a point of order (for which some authoritative guidance from > > the Secretary, CCed, would potentially prove useful): while the > > technical committee is empowered to

Bug#975075:

2020-11-19 Thread Josh Triplett
[I have consolidated responses to multiple bits of quoted text here, in an effort to consolidate responses to variations on the same points, in the hopes that doing so will avoid proliferating variations on a common theme. Also, the title of this bug itself presumes a disputed point of view.] On

Bug#975075: tech-ctte: Should maintainers be able to block init compatibility changes?

2020-11-19 Thread Josh Triplett
On Thu, 19 Nov 2020 12:00:45 -0700 Sean Whitton wrote: > Hello, > > On Wed 18 Nov 2020 at 11:18PM -08, Josh Triplett wrote: > > I'd also like to address one other issue here. It would be easy to > > hypothesize, at this point, that some additional communication (or more > > verbose

Bug#975075: tech-ctte: Should maintainers be able to block init compatibility changes?

2020-11-19 Thread Sean Whitton
Hello, On Wed 18 Nov 2020 at 11:18PM -08, Josh Triplett wrote: > First, as a point of order (for which some authoritative guidance from > the Secretary, CCed, would potentially prove useful): while the > technical committee is empowered to handle various types of disputes (up > to and including

Bug#975075: tech-ctte: Should maintainers be able to block init compatibility changes?

2020-11-19 Thread Sean Whitton
Hello, On Wed 18 Nov 2020 at 11:18PM -08, Josh Triplett wrote: > I'd also like to address one other issue here. It would be easy to > hypothesize, at this point, that some additional communication (or more > verbose communication) from the maintainer might have helped here. > However, I would

Bug#975075: tech-ctte: Should maintainers be able to block init compatibility changes?

2020-11-19 Thread Sean Whitton
Hello, On Wed 18 Nov 2020 at 11:18PM -08, Josh Triplett wrote: > I'd also like to address one other issue here. It would be easy to > hypothesize, at this point, that some additional communication (or more > verbose communication) from the maintainer might have helped here. > However, I would

Bug#971515: Status as of last tech-ctte meeting

2020-11-19 Thread Shengjing Zhu
On Wed, Nov 18, 2020 at 10:26:21AM -0800, Russ Allbery wrote: > > I maintain a bunch of Kubernetes clusters as part of my job. Those > clusters are run by other people (cloud providers, data centers, etc.). I > need clients to talk to those clusters. When I first started working with >

Bug#971515: Status as of last tech-ctte meeting

2020-11-19 Thread Ian Jackson
Russ Allbery writes ("Bug#971515: Status as of last tech-ctte meeting"): > [much stuff] Oh, wow, Russ. Thank you very much. What an excellent piece of writing. I agree entirely with all of it. Ian. (And I speak as someone who thinks that this newfangled "vendor everything" and "just download

Bug#975075: tech-ctte: Should maintainers be able to block init compatibility changes?

2020-11-19 Thread Felix Lechner
Hi, On Wed, Nov 18, 2020 at 11:33 PM Josh Triplett wrote: > > I do not believe it falls within the scope of the technical committee > to override a decision already decided by a project-wide GR In the State of California we follow such a strict interpretation of ballot measures. While

Bug#975075: tech-ctte: Should maintainers be able to block init compatibility changes?

2020-11-19 Thread Ian Jackson
1. Basic principles Josh Triplett writes: > I do not believe it falls within the scope of the technical > committee to override a decision already decided by a project-wide > GR, No-one is asking the TC to override the GR. In fact, Matthew is asking the TC to *implement* the GR. > or to

Bug#975075: tech-ctte: Should maintainers be able to block init compatibility changes?

2020-11-19 Thread Matthew Vernon
[I don't need a CC, thanks] Hi, I know it was mentioned back in the day, but trying to re-ask it now: Wouldn't it be possible to ship init scripts for compatibility purposes from a sysvinit (or maybe a sysvinit-support) package? This would be the inverse of what happened back when systemd was