* Wouter Verhelst [2022-10-07 19:58]:
I'm not sure I agree with that assessment. I believe DEPs are mostly for
discussing changes that can then be voluntarily implemented by
individual package maintainers; whereas this is intended to allow those
who want the change to actually do the work for
Hi Ansgar,
On Fri, Oct 07, 2022 at 02:07:55PM +0200, Ansgar wrote:
> On Fri, 2022-10-07 at 13:37 +0200, Wouter Verhelst wrote:
> > - After the merits and problems of the proposed new projects are
> > discussed, the release team decides which projects are accepted for
> > the next release.
> >
On Fri, Oct 07, 2022 at 02:21:04PM +0200, Timo Röhling wrote:
> Hi Wouter,
>
> * Wouter Verhelst [2022-10-07 13:37]:
> > I've given this some thought over the past few days, and have come up
> > with something that I believe might work, and I would like to submit it
> > as a proposal to see what
On Fri, Oct 07, 2022 at 05:54:40PM +0100, Luca Boccassi wrote:
> > - After the merits and problems of the proposed new projects are
> > discussed, the release team decides which projects are accepted for
> > the next release.
> > (I specifically do not mention what rules the release team
> "Luca" == Luca Boccassi writes:
>> - After the merits and problems of the proposed new projects are
>> discussed, the release team decides which projects are accepted
>> for the next release. (I specifically do not mention what rules
>> the release team should follow in
> - After the merits and problems of the proposed new projects are
> discussed, the release team decides which projects are accepted for
> the next release.
> (I specifically do not mention what rules the release team should
> follow in deciding which projects to accept -- I trust their
>
(This is the continuation of an unspecified thread in the debian-private list
that generated enough positive content that I deemed it smart enough to jump
off from it, to a public mailing list. I'm not quoting anything from anyone,
but there's certainly inspiration from various participants, so
On Fri, 2022-10-07 at 14:21 +0200, Timo Röhling wrote:
> * Wouter Verhelst [2022-10-07 13:37]:
> > I've given this some thought over the past few days, and have come
> > up
> > with something that I believe might work, and I would like to
> > submit it
> > as a proposal to see what others think.
Hi Wouter,
* Wouter Verhelst [2022-10-07 13:37]:
I've given this some thought over the past few days, and have come up
with something that I believe might work, and I would like to submit it
as a proposal to see what others think.
Great idea, thank you for your thoughts!
It reminds me of the
On Fri, 2022-10-07 at 13:37 +0200, Wouter Verhelst wrote:
> - After the merits and problems of the proposed new projects are
> discussed, the release team decides which projects are accepted for
> the next release.
> (I specifically do not mention what rules the release team should
>
Hi,
Debian does not have a good way to manage projects that require changes
to large numbers of source packages to be successful. Handling projects
like that currently requires buy-in from each individual package
maintainer; if the project does not manage to convince sufficient
numbers of
11 matches
Mail list logo
