Re: Bikeshedding

2019-03-31 Thread Russ Allbery
Roberto C. Sánchez writes: > On Sun, Mar 31, 2019 at 03:47:26PM -0700, Russ Allbery wrote: >> One of the great things about Git is that there's really no such thing >> as a "primary place of development" since every clone of the repository >> is equal and it's nearly trivial to push a repository

Re: Bikeshedding

2019-03-31 Thread Roberto C . Sánchez
On Sun, Mar 31, 2019 at 03:47:26PM -0700, Russ Allbery wrote: > Roberto C. Sánchez writes: > > > I suppose requiring that they be pull-mirrored to Salsa might make > > sense, but requiring that the primary place of development for Debian > > packaging actually be in Salsa would present an

Re: Bikeshedding

2019-03-31 Thread Russ Allbery
Roberto C. Sánchez writes: > I suppose requiring that they be pull-mirrored to Salsa might make > sense, but requiring that the primary place of development for Debian > packaging actually be in Salsa would present an obstacle for some of my > current packages. Of course, that would mean that

Re: Are Martin and Sam's platforms equivalent?

2019-03-31 Thread Jonathan Carter
Hi Sean On 2019/03/31 21:05, Sean Whitton wrote: > On Sat 30 Mar 2019 at 10:23AM +02, Jonathan Carter wrote: >> That leaves less than 10 packages that need reviewing right now. I do >> think that reviewing/sponsoring should be a lot better, and that more >> DDs should play their part, and that

Re: Are Martin and Sam's platforms equivalent?

2019-03-31 Thread Sean Whitton
Hello Jonathan, On Sat 30 Mar 2019 at 10:23AM +02, Jonathan Carter wrote: > That leaves less than 10 packages that need reviewing right now. I do > think that reviewing/sponsoring should be a lot better, and that more > DDs should play their part, and that our tooling can improve to bring > more

Re: Bikeshedding

2019-03-31 Thread Sam Hartman
> "Stefano" == Stefano Zacchiroli writes: Stefano> I respectfully disagree. While it's not DPL's Stefano> responsibility to implement (and maybe even drive) any Stefano> specific technical/workflow change in the project, knowing Stefano> what the DPL *thinks* about matters

Re: Bikeshedding

2019-03-31 Thread Jonathan Carter
On 2019/03/31 14:12, Stefano Zacchiroli wrote: > I respectfully disagree. While it's not DPL's responsibility to > implement (and maybe even drive) any specific technical/workflow change > in the project, knowing what the DPL *thinks* about matters like this > one is a fundamental element when

Re: Bikeshedding

2019-03-31 Thread Joerg Jaspert
On 15358 March 1977, Stefano Zacchiroli wrote: I'm not fundamentally against that being a "must", but we should just be aware that there might be some use cases that we'll end up sacrificing in order to make such a unification of source control hosting possible. I agree with your analysis

Re: Bikeshedding

2019-03-31 Thread Joerg Jaspert
On 15358 March 1977, Stefano Zacchiroli wrote: > Statement: every Debian package must be maintained in Git on salsa and > every Debian Developer with upload rights to the archive should have > commit/push right to every packaging repository on salsa. Well, you took it from one of my mails, so

Re: Bikeshedding

2019-03-31 Thread Stefano Zacchiroli
Hi Sam, thanks for your detailed follow-up, which fully answer my question. Just a minor point on this: On Sun, Mar 31, 2019 at 07:52:46AM -0400, Sam Hartman wrote: > I'd encourage you to think more carefully before asking DPL candidates > to strongly state things that aren't the DPL's business

Re: Bikeshedding

2019-03-31 Thread Jonathan Carter
Hi Zack On 2019/03/31 12:07, Stefano Zacchiroli wrote: > I know well where I'm placed on that trade-off: I'd take uniformity > every day. I'm convinced Debian's inability to impose one way of > maintaining packages is holding us back in our ability to implement (by > the means of semi-automation)

Re: Bikeshedding

2019-03-31 Thread Sam Hartman
> "Stefano" == Stefano Zacchiroli writes: Stefano> On Sat, Mar 30, 2019 at 11:38:43PM +0100, Joerg Jaspert wrote: >> And less "I'm the package maintainer, this is my castle, go away" >> and more "This is how the majority does it, you follow, the >> benefit of it being one

Re: Bikeshedding

2019-03-31 Thread Roberto C . Sánchez
On Sun, Mar 31, 2019 at 10:42:10AM +0200, Jonathan Carter wrote: > On 2019/03/31 09:39, Stefano Zacchiroli wrote: > > > > Statement: every Debian package must be maintained in Git on salsa and > > every Debian Developer with upload rights to the archive should have > > commit/push right to every

Re: Bikeshedding

2019-03-31 Thread Stefano Zacchiroli
On Sun, Mar 31, 2019 at 10:42:10AM +0200, Jonathan Carter wrote: > In general, I think so. I'm unsure about the first "must" though, I tend > to like that we're not so rigid and inflexible in our policies that we > can't cater for a few exceptions. For example, I could understand that > packagers

Re: Bikeshedding

2019-03-31 Thread Stefano Zacchiroli
On Sun, Mar 31, 2019 at 10:23:29AM +0200, Joerg Jaspert wrote: > On 15358 March 1977, Stefano Zacchiroli wrote: > > Statement: every Debian package must be maintained in Git on salsa and > > every Debian Developer with upload rights to the archive should have > > commit/push right to every

Re: Bikeshedding

2019-03-31 Thread Jonathan Carter
Hi Zack On 2019/03/31 09:39, Stefano Zacchiroli wrote: > On Sat, Mar 30, 2019 at 11:38:43PM +0100, Joerg Jaspert wrote: >> And less "I'm the package maintainer, this is my castle, go away" and >> more "This is how the majority does it, you follow, the benefit of it >> being one way, not a dozen

Re: Bikeshedding

2019-03-31 Thread Joerg Jaspert
On 15358 March 1977, Stefano Zacchiroli wrote: And less "I'm the package maintainer, this is my castle, go away" and more "This is how the majority does it, you follow, the benefit of it being one way, not a dozen different, outweight some personal preferences". Let's cut to the chase of this.

Re: Bikeshedding

2019-03-31 Thread Stefano Zacchiroli
On Sat, Mar 30, 2019 at 11:38:43PM +0100, Joerg Jaspert wrote: > And less "I'm the package maintainer, this is my castle, go away" and > more "This is how the majority does it, you follow, the benefit of it > being one way, not a dozen different, outweight some personal > preferences". Let's cut