Andreas Enge writes:
> Hello,
>
> in the current situation I think the suggestion is putting the horse before
> the cart. In a first step before adding policy, we should make the teams
> functional.
I find debian have various teams, and each team has a page for packages
status: https://tracker.d
Simon Tournier writes:
> Hi,
>
>
> On Sun, 26 Feb 2023 at 16:52, Kyle wrote:
>
>> One idea might be to write a conda importer which looks at the
>> versions of software in the resulting environment and tries to make
>> feasible package variants of make a manifest which matches the
>> existing
Hi,
tl;dr:
If you want to expand the list of committers rapidly,
would it make sense to have a sand-box repo for new committers
which trusted committers could channel cherry-picks from?
Pick your bugaboo, but I consider plausible that some
volunteering committers are there on p
Hello,
in the current situation I think the suggestion is putting the horse before
the cart. In a first step before adding policy, we should make the teams
functional. While working on core-updates, I have been realising we are
already spread too thin: Some important languages have teams with one
