* Stefano Zacchiroli [2019-03-31 09:39]:
> 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.
>
> DPL candidates: do you agree with this
On 15361 March 1977, Sean Whitton wrote:
Yes. The amount of effort that we would need to expend on implementing
zack's Statement seems out of proportion to the benefit, given that it
mandates no particular git workflow.
That's because you are all in way too deep in technical stuff. This is
>>>>> "Sean" == Sean Whitton writes:
Sean> Hello,
Sean> On Wed 03 Apr 2019 at 12:51PM +01, Ian Jackson wrote:
>> Stefano Zacchiroli writes ("Re: Bikeshedding"):
>>> Statement: every Debian package must be maintained in Git
Hello,
On Wed 03 Apr 2019 at 12:51PM +01, Ian Jackson wrote:
> Stefano Zacchiroli writes ("Re: Bikeshedding"):
>> Statement: every Debian package must be maintained in Git on salsa and
>> every Debian Developer with upload rights to the archive should have
>> commi
Stefano Zacchiroli writes ("Re: Bikeshedding"):
> 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.
>
> DPL
Hi,
On 02.04.19 05:59, Louis-Philippe Véronneau wrote:
> Some teams might dislike it, but I guess those people will also dislike
> the idea of giving all DDs commit access on all packages VCS.
Y'all are still solving social problems with technical solutions here,
and it's a bad technical
On 2019/04/02 09:53, Jonas Meurer wrote:
> Gitlab subgroups would solve this problem: Move every Debian package
> into the 'debian' group, but allow subgroups in there:
>
> https://salsa.debian.org/debian/foo-team/libfoo
Yeah I was thinking along that too. It seems like subgroups under
/debian
On 15360 March 1977, Jonas Meurer wrote:
Gitlab subgroups would solve this problem: Move every Debian package
into the 'debian' group, but allow subgroups in there:
Not in the current way they work, no. Though there is a gitlab upstream
bug about it.
--
bye, Joerg
Raphael Hertzog:
> Hi,
>
> On Mon, 01 Apr 2019, Louis-Philippe Véronneau wrote:
>>> So if i had to decide how to implement this technique, i think the
>>> simplest thing would be to move every
>>> https://salsa.debian.org/foo-team/libfoo to
>>> https://salsa.debian.org/debian/libfoo and let the
Hi,
On Mon, 01 Apr 2019, Louis-Philippe Véronneau wrote:
> > So if i had to decide how to implement this technique, i think the
> > simplest thing would be to move every
> > https://salsa.debian.org/foo-team/libfoo to
> > https://salsa.debian.org/debian/libfoo and let the debian/ grouping
> >
On 19-04-01 18 h 18, Daniel Kahn Gillmor wrote:
> On Mon 2019-04-01 15:17:27 -0400, Louis-Philippe Véronneau wrote:
>> On 19-03-31 03 h 39, Stefano Zacchiroli wrote:
>>>
>>> Statement: every Debian package must be maintained in Git on salsa and
>>> every Debian Developer with upload rights to the
On Mon 2019-04-01 15:17:27 -0400, Louis-Philippe Véronneau wrote:
> On 19-03-31 03 h 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
Hi Jelmer
On 2019/04/01 11:00, Jelmer Vernooij 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 of a
On 19-03-31 03 h 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 packaging repository on salsa.
I'm curious to how this would be
On Sun, Mar 31, 2019 at 10:42:10AM +0200, Jonathan Carter wrote:
> 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
On 15359 March 1977, Russ Allbery wrote:
I agree with what you are saying here. However, I am concerned that the
"push == automatic package upload" idea may be a step too far in some
cases.
I assume this would only happen if you push a signed tag. I wouldn't want
every random commit I push
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
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
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
> "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
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
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
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
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
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)
> "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
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
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
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
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
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.
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
On 15356 March 1977, Anthony Towns wrote:
Did anything happen to that? (Or perhaps, that's better phrased as:
did anything cause it to stall other than ENOTIME?) I'm guessing not?
[1]
ENOTIME. And ENOONEELSEINTERESTEDINCODING.
Unless the things that caused it to stall were legal concerns or
Hi aj
On 2019/03/29 06:32, Anthony Towns wrote:
> FWIW, I think giving every DD their own bikeshed that they can paint
> whatever colour they like would be by far the biggest improvement possible
> in Debian today. [2]
>
> As a result, I kind of disagree with Joerg's statement in his platform
>
.html
Anthony> https://lists.debian.org/debian-devel/2015/09/msg00340.html
Anthony> https://lists.debian.org/debian-devel/2015/09/msg00404.html
With respect, I don't actually think bikeshedding helps that much with
the sort of situations where people want the project
Hi *,
"More of a comment than a question..."
On Wed, Mar 20, 2019 at 06:17:00AM -0400, Sam Hartman wrote:
> I am disappointed when people leave bitter and disheartened.
That's still kind-of better than if they're bitter and disheartened,
but won't go away though!
One of the things I often
36 matches
Mail list logo
