)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"defda8c44d7fd2815ff0329500922984e019fd1d","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"e01fa3b8_3cbf3410","updated":"2026-06-26 21:37:06.000000000","message":"Couple of things to flag: \n\nthe elections repo\u0027s update_governance.py (write_tc_members) [1] uses yaml.indent(mapping\u003d2, sequence\u003d4, offset\u003d2) i.e., 2-space leading indent on sequence items). So the next time that tool runs after an election, it\u0027ll re-introduce the leading indent and create a noisy diff against this change.\n\nNot a blocker, nothing breaks; but worth aligning the indent config in the elections tool.. \n\nNext, new SIG proposals may introduce new keys. The RISC-V proposal [2] adds a couple of things (wechat and working-language). That\u0027s a heads up for me to ensure we\u0027re negotiating the schema in that change or a prior change :D","commit_id":"b0a11945e67d88898fa37613d9e700b6dd4ccc7a"}]}