)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"30e86b610ad825bc4e62e899f7912ca4376030e8","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"1ebd1cf6_e8008909","updated":"2024-04-05 17:14:51.000000000","message":"I am not 100% sure if we should include such lib/tooling in TC repo. I know we had to move the Technical writing SIG (doc team) under TC but that was because there was no maintainers for doc and that time olso took the tooling repo to maintain. is oslo team does not want to maintain these tooling and TC have to take care?\n\nI am more incline towards TC have more of policy/governance doc than tooling where we might face issue of who will actually maintain those in TC. Even we should work on finding/re-forming the doc repo team and move them away from TC.\n\nI am not adding -1 here as I am not so strong of against of it but not in favor too. I would like other TC memebrs + oslo team opinion on this.","commit_id":"082196791d26d455a27e473d08e08f6727c1e84d"},{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"b01c11a5cde47739a7465082c6f4188cf4c89c3d","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"e4dbbdca_63d4adb2","updated":"2024-04-05 13:10:01.000000000","message":"My main reasoning is that changes like https://review.opendev.org/c/openstack/openstackdocstheme/+/915129 are more related to policy than actual implementation and would thus be better handled by the TC.\n\nI also proposed this move in the #-oslo channel and got a bit of support and to negative feedback https://meetings.opendev.org/irclogs/%23openstack-oslo/%23openstack-oslo.2024-04-02.log.html#t2024-04-02T08:15:01","commit_id":"082196791d26d455a27e473d08e08f6727c1e84d"},{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"582d2d42cc5f9d167e1967ed08a11def46572c09","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"79204c8e_ba296286","updated":"2024-04-23 16:17:02.000000000","message":"Thank you for proposing this; a couple of points.. I see the main reason for proposing this is one change: https://review.opendev.org/c/openstack/openstackdocstheme/+/915129\n\nIt\u0027s debatable whether that\u0027s a governance change imo; i.e., many projects make individual decisions on how they handle unmaintained versions; for example, tempest and all their plugins tag a \"last\" release to cater to unmaintained branches... so, I can think of openstackdocstheme\u0027s change in that light. I agree openstackdocstheme is used all over the place, and any decision like this will affect nearly all projects under the TC\u0027s governance.. however, decisions like this can solicit wider consensus by going to the openstack-discuss mailing list. Further, if the TC wants to make a change like this, we\u0027d still be able to propose it, despite this tooling being under oslo. wdyt?","commit_id":"082196791d26d455a27e473d08e08f6727c1e84d"},{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"35121b47a103451c683153be6abaa2632964e25c","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"84949514_f068f6f9","in_reply_to":"79204c8e_ba296286","updated":"2024-04-23 17:43:06.000000000","message":"I see the oslo team being next to inactive, but then the TC also isn\u0027t a fountain of activity. So let\u0027s keep things as they are for now and see how long it takes to actually make progress on the content side.","commit_id":"082196791d26d455a27e473d08e08f6727c1e84d"}]}