#148: Container "Packager" Guildelines and Naming Conventions
-------------------------+---------------------
Reporter: maxamillion | Owner:
Type: task | Status: new
Priority: normal | Milestone: Future
Component: --- | Resolution:
Keywords: meeting |
-------------------------+---------------------
Comment (by mattdm):
Replying to [comment:1 kushal]:
> I guess we have to add more details about what all is allowed to be in
> the containers. Like can we get arbitrary things from Internet into
> those containers? Say a web application which is yet to be packaged in
> Fedora as an rpm.
I'm hoping, in the near future, to have a good way to identify specific
upstream content as acceptable for direct inclusion in Fedora containers
(well, not quite direct — I think we'd need some mechanism to
cache/archive it locally).
In the meantime, it would be cool if we could allow both Fedora-content-
only *and* Fedora + other legally okay and open source content in the
system, but require the latter to be based on a Fedora Remix base image,
which we should provide. (Or, possibly we have a layered image which
replaces Fedora branding with the Fedora Remix branding.)
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/148#comment:2>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
_______________________________________________
cloud mailing list
cloud@xxxxxxxxxxxxxxxxxxxxxxx
http://lists.fedoraproject.org/admin/lists/cloud@xxxxxxxxxxxxxxxxxxxxxxx
