Sean Whitton writes ("Re: Are Martin and Sam's platforms equivalent?"):
> On Fri 29 Mar 2019 at 04:43PM +02, Adrian Bunk wrote:
> > 2. Package sponsorship
...
> > There are too few people reviewing packages at sponsorship-requests,
> > but proper and timely reviews would be very important both for
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 candidates: do you agree with this sta
Hi Matthew
On 2019/04/03 00:22, Matthew Garrett wrote:
> Given these upstream shifts, is attempting to package as much software
> as possible something that actually benefits Debian and our users, or is
> it something that brings us a duplication of effort?
I'm not quite convinced that these up
On Wed, Apr 03, 2019 at 12:40:45PM +0100, Ian Jackson wrote:
> I hesitate to bang this drum again, but this would be a great place to
> think about how we can use git more.
>
> Ideally, our default sponsorship workflow would *not involve source
> packages or orig tarballs at all*.
It's too easy t
Sam Hartman writes ("Re: Q to all candidates: what is the long-term role of
traditional Linux distributions?"):
> Debian is great at giving you all the parts of what you need to do that
> aren't your primary focus.
This is a great answer.
> I think packaging free software even from languages tha
[no need to CC me; I'm subscribed to -vote]
Dear Jonathan et al.,
> > - the elected person gets so squeezed that after their service they just
> > prefer to focus in other tasks,
>
> I agree that an overloaded DPL role can be harmful to both Debian and
> the individual in the role. I think it's
> "Chris" == Chris Lamb writes:
Chris> I'd be very interested if you and the other candidates could
Chris> elaborate on their thoughts in this approximate area.
Chris> As a bit of background, I've actually written this reply
Chris> twice before (or, admittedly ones somewhat s
Thanks for asking these questions. I'm *really* interested to see how
all the candidates respond (if they do)
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Jonathan Dowland
⢿⡄⠘⠷⠚⠋⠀ https://jmtd.net
⠈⠳⣄ Please do not CC me, I am subscribed to the list.
Hi Chris
On 2019/04/03 15:00, Chris Lamb wrote:
> On 2019/03/29 16:01, Jonathan Carter wrote:
>> I agree that an overloaded DPL role can be harmful to both Debian and
>> the individual in the role. I think it's important for a DPL to take a
>> step back every now and again and look at the various
On 15361 March 1977, Chris Lamb wrote:
So, in general, I fear that the candidates may be over-estimating how
much of the DPL's tasks can be delegated to teams or other individuals.
[...]
So, reading this back I am not entirely sure what I'm asking here but
I would be interested if our candidat
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
>> commit/push right to every packaging
> "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 on
>>> salsa and every Debian Developer with upload r
On 15361 March 1977, Matthew Garrett wrote:
But upstream development is increasingly diverging from our approach.
I think that depends a bit in which area you look.
Many new software ecosystems are based on external code repositories
rather than relying on the distribution, and in several la
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
-v
14 matches
Mail list logo
