I've added a topic to the Gobby for tomorrow's meeting: ``` #topic options for release artifact signing for Fedora CoreOS - dustymabe We are exploring options for signing our release artifacts for Fedora CoreOS. We have an open ticket where we have defined various options and narrowed down the options to ones we'd like to explore with Fedora Infrastructure. The ticket and all context can be found here: https://github.com/coreos/fedora-coreos-tracker/issues/187 The TL;DR is that we'd like to deliver an artifact and a detached signature: i.e. `fcos.iso` and `fcos.iso.sig`. We'd like to discuss with infra to see what the limitations are in the infra for achieving this goal and if we can make it happen. ``` On 6/5/19 11:00 AM, smooge@xxxxxxxxx wrote: > Dear all, > > You are kindly invited to the meeting: > Fedora Infrastructure on 2019-06-06 from 15:00:00 to 16:00:00 UTC > At fedora-meeting-1@xxxxxxxxxxxxxxxx > > The meeting will be about: > Weekly Fedora Infrastructure meeting. See infrastructure list for agenda a day before or view it at https://infinote.fedoraproject.org/cgit/infinote/tree/fedora-infrastructure-meeting-next > > > Source: https://apps.fedoraproject.org/calendar/meeting/22/ > > _______________________________________________ > infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx > _______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
