You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It can be very tricky finding out what exactly happened to a SIP over its life-cycle. I would like to propose an improvement to the SIP template, where for each SIP meeting the SIP where the SIP was put on the agenda, there is a brief note on what was discussed, with links to the video and to the minutes.
I think this adds value to the history section already present, since they track slightly different things. One tracks the change made to the SIP, while the other tracks decisions made about the SIP.
For example, I could imagine it looking something like this for SIP 35
It would allow for someone interested in some SIP to quickly find out what happened to it, when, and look up the minutes. This would make answering questions like "When was this SIP numbered" a lot easier to answer.
The text was updated successfully, but these errors were encountered:
I agree this is desirable, will try to find some time before our next SIP meeting to submit a PR adding this rule and modifying the current template. Thanks @martijnhoekstra 😄.
It can be very tricky finding out what exactly happened to a SIP over its life-cycle. I would like to propose an improvement to the SIP template, where for each SIP meeting the SIP where the SIP was put on the agenda, there is a brief note on what was discussed, with links to the video and to the minutes.
I think this adds value to the history section already present, since they track slightly different things. One tracks the change made to the SIP, while the other tracks decisions made about the SIP.
For example, I could imagine it looking something like this for SIP 35
It would allow for someone interested in some SIP to quickly find out what happened to it, when, and look up the minutes. This would make answering questions like "When was this SIP numbered" a lot easier to answer.
The text was updated successfully, but these errors were encountered: