Wikimedia Technical Committee/Minutes/2020-07-01
See also TechCom-RFC workboard in Phabricator. (Private minutes)
For more information, see the public notes.
TechCom is currently evaluating the communication channels used to distribute committee updates like the TechCom Radar. If you would like to continue receiving the TechCom Radar through this newsletter instead of through the wikitech-l mailing list, please leave a comment on the talk page.
- Moved from open to stalled: RFC Frontend build step <https://phabricator.wikimedia.org/T199004>
- The question on the RFC was originally: How can we implement a build step? The discussion on the RFC has been centered around whether we should implement a build step. The authors are trying to address concerns to enable them to implement it since it’s an industry-wide practice.
- This impacts security for the developers running insecure code on developer host machines, security for production (can be contained/network isolated), and security for the end-user (this isn’t just helping create commits or run tests, it modifies and adds code we sent to a billion people’s devices). Reproducing the same locally, in CI and prod. Workflow problems like cherry-pick and revert in production branches.
- TechCom to continue discussing these topics with stakeholders
- Moved from Inbox to In progress: Send regular overview about Wikimedia development policies <https://phabricator.wikimedia.org/T164538>
- On last call ending July 8: RFC Amendment to the Stability interface policy <https://phabricator.wikimedia.org/T255803>
- Ongoing discussion: RFC Hybrid extension management <https://phabricator.wikimedia.org/T250406>
- No public IRC discussion scheduled for next week