#38: Dopr ------------------------+--------------------- Reporter: msuchy | Owner: Status: new | Priority: normal Component: Trademarks | Resolution: Keywords: meeting | ------------------------+--------------------- Comment (by mattdm): Replying to [comment:26 msuchy]: > Replying to [comment:22 mattdm]: > > Dopr devs, can you contact him directly about that? > I just wrote him. Any update? > > > On a related note, I still think we should restrict the service to Fedora and CentOS bases, although it occurs to me that we shouldn't restrict it to just the base image, but also the layered images Fedora/CentOS produce + any other Dopr. That seems like it'd be reasonably easy to implement technically, especially if all Dopr containers are built in one Docker Hub namespace. > > 1) Why? (just being curious). Why to which part? > 2) I will check if it is technically possible. I think it's simply a matter of validating the FROM lines, isn't it? > > Is there any plan to integrate this directly into Copr rather than being a stand-alone service? > > Technically it is so different so having it on the same machine does not have too much sense. But of course we can concat it via UI and links so for users it will be nearly the same. > However I want to do one step at the time. Let see how it will work in production and if it will work, then lets bind it together with Copr. As a user, I don't care what's happening under the hood -- the nice thing would be a single check box which says "make a docker image from this", without having to go to a separate service. -- Ticket URL: <https://fedorahosted.org/council/ticket/38#comment:27> council <https://fedorahosted.org/council> Fedora Council Public Tickets _______________________________________________ council-discuss mailing list council-discuss@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct https://admin.fedoraproject.org/mailman/listinfo/council-discuss The Fedora Project's mission is to lead the advancement of free and open source software and content as a collaborative community.