#13 Resolve github.com/container-images
Opened 5 years ago by ttomecek. Modified 5 years ago

We are a Red Hat team, user-cont, and we started the organization mentioned in the title. The organization was used to kickstart several container images for Fedora Modular Server - Boltron. Unfortunately we no longer have people nor interest in maintaining those. Therefore we would like to donate them to Fedora.

TODO:

  • migrate images from github.com/container-images to fedora dist-git
  • once that's done, mark the github repository as deprecated and remove it over time
  • figure out ownership: will sig own these images? are these images even good enough to be part of Fedora?

https://github.com/container-images/container-image-template is a special case - what'll happen to it?

I'd like to keep it around, or to find another well documented way to create new Fedora-based containers from scratch

My idea was to move it to pagure.io and let this sig own that repo. What do you think, Chris?

my personal thoughts are that moving a whole repo over to be the responsibility of the containers SIG is not the right thing to do. each application is going to take care and feeding. If no one is interested in maintaining it then it will rot. I'd rather pick up each application when someone steps up to want to maintain it.

Dusty, I was specifically referring to the template repo. Sorry for my poor wording. I'm definitely interested in maintaining it myself on behalf of this sig. For the specific applications, it should really be up to the people to decide which should we pull in and who's gonna maintain those.

Dusty, I was specifically referring to the template repo.

ahh.. :thumbsup:

I've just cloned the template repo on pagure as we talked yesterday on the meeting:

https://pagure.io/ContainerSIG/container-image-template

@jlanda cool, one thing is if we might want to grant the access to the all sig members via adding the group in to its members, do we?

IMO it is kind of unfortunate the this have to be done so the repo is discoverable via https://pagure.io/group/ContainerSIG

@jlanda cool, one thing is if we might want to grant the access to the all sig members via adding the group in to its members, do we?
IMO it is kind of unfortunate the this have to be done so the repo is discoverable via https://pagure.io/group/ContainerSIG

Done ;)

Metadata Update from @cverna:
- Issue untagged with: meeting

5 years ago

Login to comment on this ticket.

Metadata