I’m tremendously happy with the speed we’re seeing minutes of SIP meetings. A big thanks for getting that on the road.
While having these minutes is great, it painfully shines a light on how difficult it is to get an overview of features/proposals for scala 3 and their state. I’d like to volunteer to get that on the road. I appreciate that there is immense pressure on the inside to get things done and not a lot of spare capacity to deal with providing this kind of transparency. I’d like to make documentation on
- What the SIP committee is doing (i.e. determining which features will be part of scala 3.0) and not doing at the moment (things that are not directly involved in what will be in scala 3.0)
- The list of features that has or will go through the SIP committee
- The status of each such feature: To do -> For feedback on discourse -> ready for SIP meeting -> accepted for 3.0, accepted for 3.x, rejected without prejudice/delayed after 3.0, rejected with prejudice, back for further iteration
Is someone in the SIP committee willing to help me with this and review documentation PRs? Is my characterization of the current role of the SIP committee correct? Is the list of features on https://dotty.epfl.ch/docs/reference/overview.html a good approximation of features that are in any of the above mentioned states, or does it need more git archeology and minute-digging to determine rejected proposals fully?