[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Resignation as cloud team delegate



Moin

On Fri, Jul 01, 2022 at 10:21:51PM -0700, Ross Vandegrift wrote:
> Great, most of that seems like a clear improvement.  But there's one change I'm
> not sure about:
> 
> --- original	2022-07-01 21:40:33.826069834 -0700
> +++ draft	2022-07-01 21:40:45.778221446 -0700
> @@ -1,3 +1,3 @@
>  - With the Debian Project Leader and under the auspices of the
>    Trusted Organizations, establish Debian accounts with cloud
> -  providers, negotiating terms and conditions where necessary.
> +  providers for the purpose of managing cloud images
> 
> Are you thinking the delegation needs to enumerate responsibilities more
> specifically?  If so, we have other projects unrelated to VM images:
> - provider-specific mirror infrastructure.
> - build systems for docker images on docker.io and public.ecr.aws.
- QA stuff, like ci.debian.net and archive rebuilds
- random systems for other teams
- infrastructure for cloud team use

With the above change, we can't longer provide those.

> A bigger consequence would be that other teams could establish official
> provider accounts for Debian.

Even before, the delegation was not exclusive.  And the DPL is free to
delegate as they wishes.  So this does not change IMHO.

>                                I'm not sure what I think of that.  There are
> some downsides:
> I'm not sure what I think of these tradeoffs.  But I do think we should
> consider them.  What do you and other team members think?

Even I don't know if we have an overview over the resources Debian have
access to.  I tried to document the ones the cloud team has, including
who can make use of them.  I'm not entirely okay with the form I chose,
but at least we have it.  But what about others?

Bastian

-- 
All your people must learn before you can reach for the stars.
		-- Kirk, "The Gamesters of Triskelion", stardate 3259.2


Reply to: