2024-07-24 RFC Process Continued

Tod Olson is next, followed by Jason Root

Jenn Colt will take notes today since Tod will be late.

Reminder:  Please copy/paste the Zoom chat into the notes.  If you miss it, this is saved along with the meeting recording, but having it here has benefits.

Notes from last week:

• Craig: Is the RFC format appropriate for this big change, or could it have been split into smaller RFCs with an overview document for all of them?
• Jenn: Supporting diagrams are helpful. Other option: Overview RFC linking to detailed documentation.
• Marc: RFCs can be used to have the discussion and investigating different solutions before the implementation starts; Eureka decisions and development has started before the RFC was created allowing for only yes/no decision.
• Jason and Marc: Both ways are possible.
• Jenn: Even if it's only yes/no decision the RFC process explains the reasons why the solution has been chosen and explains the details.
• Marc: Eureka and Application Formalization might be independent decisions.
• Craig: Wonders whether putting more details into the RFC text help the RFC process or is too much information.
• Tod: Would like a high level RFC about Eureka. All low level details should be separate, whether as RFCs or in other form.
• Marc: Most feedback is from TC members only. SysOps are trying to install Eureka.
• Marc: mod-lists has been accepted before the architectural change RFC has been created.
  Eureka has huge architectural consequences so we should be careful.
• Craig: I can provide an overview RFC. Whether to go this way should be decided by TC on Monday.

Meeting runs out of time. All following topics are moved to next Wednesday.

Today:

• If we have a quorum, we should try to make this decision today.  Otherwise we can aim for Monday 29 Jul 2024.
• DECISION: Craig will move forward with the overview RFC