RFC Process v2b - Needs to be reviewed one last time and published
Announcements should be made
Which slack channels?
Reach out directly to individuals we know are working on RFCs
Notes:
Reviewed draft process with attendees
Note in particular that the Abstract Preparation and RFC Preparation stages are to help the submitter prepare, primary actions are with the submitter and on their timeframe.
Draft Refinement stage:
Is there a minimum size for the subgroup and is it necessary?
Is there a standard for the composition of the group?
Goal at this stage is for the RFC to be complete, clear, and have sufficient detail.
Concern that we've built a process that, while this reduces the TC potential to be a bottleneck by delegating much responsibility to the subgroup, it also removes _required_ TC active involvement through most of the process, but leaves implicit an assumption that there will be involvement by some TC members on the subgroup and in the Public Review stage.
Goal for process is to remove TC as a bottleneck and smooth out the process. Concern is that if things go sideways, we won't hear about it until too late.
Public Review stage:
Concern about how strict to be with respect to scope changes at this stage. Some scope issue may arise late, but may also be frustrating for submitter to have to revise scope this late.
Consensus:
This process is in a good enough state to implement and we can iterate in future based on experience.
ToDo:
Will want to take a look at the RFC templates with respect to timing and other changes to process
Put on Monday's agenda for formal TC acceptance.
NA
Zoom Chat
10:51:57 From Marc Johnson To Everyone: I do consider it practically optional at this point 10:52:53 From Marc Johnson To Everyone: And to be explicit, I’m good with iterative improvement of processes
I get concerned that deferring doesn’t help 10:56:24 From Marc Johnson To Everyone: We’ve historically had very little involvement from both much of the TC and the wider community 11:02:11 From Marc Johnson To Everyone: With the new process, all of the applications and platforms RFC will be in flight before we get to iterate again 11:04:36 From Marc Johnson To Everyone: Those earlier stage changes DO NOT apply to the RFCs currently in flight, as we agreed on Monday 11:04:48 From Tod Olson To Everyone: Reacted to "Those earlier stage ..." with ✔️ 11:06:57 From Marc Johnson To Everyone: In effect, for all of the upcoming RFCs, the process we agree today will be in effect
Action Items
Add to Monday's TC agenda for formal acceptance. (Craig McNally)
Review RFC templates with respect to timing and other changes to process. (Who?)