On 31/03/19 at 09:39 +0200, 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 different, outweight some personal > > preferences". > > Let's cut to the chase of this. > > 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 agree that uniformity is good, and that we should seek more uniformity
in Debian.
However, I wonder why you picked this ("maintained on salsa + upload
rights for all DD") as the first step towards increasing uniformity
(thus I assume that you see this as the most important thing to fix).
In practice, we already have a version control system with full access
to all DDs: the Debian archive (and snapshot.d.o for history). And it's
not that bad. If we were to move to something else, maybe it would be
better to switch to a single big repository (like the Debian Haskell
team does for their packages[1]).
[1] https://salsa.debian.org/haskell-team/DHG_packages
So I wonder if there aren't better targets for uniformity to spend
our energy on.
Which brings me to a question to the DPL candidates:
We all know that discussions about changing practices or procedures
inside Debian are long and difficult: there are many very opinionated
DDs, it's difficult to measure consensus, etc.
Let's imagine for a moment that you have three "full consensus +
peoplepower" magic cards. Using them, you can propose something, and
everyone will automatically agree (no need for a long mailing list
discussion!). Furthermore, people will show up and volunteer to do the
implementation work according to your plan (if there's a need for some
implementation in your plan).
So, what are the important things that you will fix or create within
Debian with those three magic cards? Why? How? Feel free to start with
a disclaimer such as:
> I don't think that this should ever be done in Debian without a proper
> project-wide discussion first. But since you are asking, here is what I
> would like to see changed in Debian, and how.
- Lucas
signature.asc
Description: PGP signature
