)]}'
{"doc/source/vmt-process.rst":[{"author":{"_account_id":10342,"name":"Jay Faulkner","display_name":"JayF","email":"jay@jvf.cc","username":"JayF","status":"youtube.com/@oss-gr / podcast.gr-oss.io"},"change_message_id":"0be5d66ea1163821df5f0390b5c1c38b3eac3a76","unresolved":true,"context_lines":[{"line_number":85,"context_line":"   the bug as important, and the VMT may thereby make it public before the"},{"line_number":86,"context_line":"   end of the embargo period on the theory that it is better to have work"},{"line_number":87,"context_line":"   done on the issue in public rather than no work done on the issue while"},{"line_number":88,"context_line":"   it is private."},{"line_number":89,"context_line":""},{"line_number":90,"context_line":"   *What can you (the bug reporter) do?* As part of the intake process,"},{"line_number":91,"context_line":"   the VMT will have subscribed the appropriate people to the Launchpad"}],"source_content_type":"text/x-rst","patch_set":1,"id":"4a7ae65c_f2120521","line":88,"updated":"2025-10-30 13:51:06.000000000","message":"I agree with the sentiment of this, but I\u0027d almost prefer having something more black and white; perhaps: \"A bug that doesn\u0027t have meaningful updates for a business week or longer, without communication to the security team of any delay or planned timeline, may have it\u0027s embargo cancelled\"\n\nMaking it explicit helps...\n- downstream teams understand the limitations and communicate them better (e.g. \"No boss, I can\u0027t wait until next sprint)\n- VMT members apply the policy more universally\n- encourage project team members to be openly communicative about their process with the VMT","commit_id":"916508f8512238abe3a1c4655c12b868ee4868ac"}]}