On 28/06/20 at 10:54 -0700, Ross Vandegrift wrote: > [removing serpent@d.o from CC, he's resigned as delegate] > > Hi Lucas, > > On Sun, Jun 28, 2020 at 05:26:41PM +0200, Lucas Nussbaum wrote: > > One could argue that the Cloud team delegation does not cover Docker > > images. > > Whether it does or not, I've been told that the docker image maintainers > prefer > to keep their current organization and workflow. I'd welcome their > participation in the team, if they were interested. But I don't think they > need to be.
Well, I think that it would a good thing for Debian to enforce some consistency on Debian images for clouds and software that require VM images, at least about where to find information about such images, and where to report problems. And I don't think that pointing to github for our tooling, and for bug reporting, is really an acceptable solution for something that is officially endorsed by Debian. Solving this for Docker or Vagrant sounds very similar to solving it for cloud images; so it's probably best if the same people are in charge. > Maybe it could be nice, if the people building those images want to use our > tools and work with us. Some would raise concerns in my mind, but I don't > think it's useful to discuss before someone wants to build e.g. raspberry pi > images in cloud-team. I'm surprised by this. I thought of the delegation as a (soft) hammer to enforce some rules, even when people are not nice and don't want to work with the cloud team (I'm not saying it's the case here). I've seen people saying "oh look, the official Debian images for docker point to github! that's funnny!". If those images are not official, then this should be clarified. If they are, then they should probably conform to standard ways of maintaining stuff in Debian. Lucas
