modularity_wg
MINUTES

#fedora-meeting-3: Meeting of the Modularity Working Group (once every two weeks)

Meeting started by nils at 14:00:21 UTC (full logs).

Meeting summary

  1. Roll Call (nils, 14:00:29)
  2. Agenda (nils, 14:03:56)
    1. Module naming policies (nils, 14:03:56)
    2. Host & Platform availability (nils, 14:03:56)
    3. Fedora 27 modular design (nils, 14:03:56)
    4. Modular Atomic Host (nils, 14:03:56)
    5. Modular Guidelines and Review Process (nils, 14:04:37)

  3. Module naming policies (nils, 14:05:05)
    1. https://pagure.io/modularity/pull-request/43 Module naming policy proposal (contyk, 14:06:40)

  4. Host & Platform availability (nils, 14:08:14)
    1. The very first builds of Host & Platform are now available and the initial test composes should be ready later today. (contyk, 14:14:56)
    2. Images will be available once we have the new installer module available. The current Platform is messy and will be sanitized over the next week or two. (contyk, 14:15:29)

  5. Fedora 27 modular design (nils, 14:15:42)
    1. We will be going through the list of required modules for Fedora 27, their built-time and runtime dependencies and deciding what buckets they should go into. (contyk, 14:25:44)
    2. We will also generate module templates for upstream maintainers willing to help us with implementation, to guide them (contyk, 14:26:11)
    3. https://github.com/fedora-modularity/dependency-report A helper module dependency reporting tool. WIP. (contyk, 14:26:27)
    4. ACTION: langdon to file a ticket in pungi(?) backlog to create a modulemd -> pungi config generator (langdon, 14:44:57)

  6. Modular Atomic Host (nils, 14:46:03)
    1. https://pagure.io/atomic-wg/issue/312 Experiment with building Atomic Host out of a module (contyk, 14:46:36)
    2. Expect a modular Atomic Host prototype within the next two weeks! (contyk, 14:50:51)

  7. Modular Guidelines and Review Process (nils, 14:52:50)
    1. fedora council approved fesco approving the initial guidelines and process, after that this group will be responsible for maintaining them (langdon, 15:00:05)
    2. contyk, nils and geppetto are updating the spec (based on a couple missing items from the last week or so) and associated guidelines to be as close as possible (langdon, 15:00:23)
    3. ACTION: langdon shooting to file a ticket with fesco by the end of the week to review it at the next fesco meeting next friday (langdon, 15:00:40)
    4. ACTION: needs to get the bz product created to file review requests.. which I don't think we have done or assigned anyone too (langdon, 15:00:50)
    5. ACTION: needs to identify any other gaps in the process that I am not thinking of (langdon, 15:01:03)


Meeting ended at 15:04:11 UTC (full logs).

Action items

  1. langdon to file a ticket in pungi(?) backlog to create a modulemd -> pungi config generator
  2. langdon shooting to file a ticket with fesco by the end of the week to review it at the next fesco meeting next friday
  3. needs to get the bz product created to file review requests.. which I don't think we have done or assigned anyone too
  4. needs to identify any other gaps in the process that I am not thinking of


Action items, by person

  1. langdon
    1. langdon to file a ticket in pungi(?) backlog to create a modulemd -> pungi config generator
    2. langdon shooting to file a ticket with fesco by the end of the week to review it at the next fesco meeting next friday
  2. UNASSIGNED
    1. needs to get the bz product created to file review requests.. which I don't think we have done or assigned anyone too
    2. needs to identify any other gaps in the process that I am not thinking of


People present (lines said)

  1. contyk (100)
  2. langdon (57)
  3. nils (57)
  4. asamalik (29)
  5. jkaluza (29)
  6. threebean (26)
  7. zodbot (15)
  8. ttomecek (14)
  9. tflink (3)
  10. geppetto (2)
  11. sgallagh (1)
  12. jkurik (1)
  13. dgilmore (1)
  14. mikedep333tflink (0)


Generated by MeetBot 0.1.4.