)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":2424,"name":"Felipe Reyes","email":"felipe.reyes@canonical.com","username":"freyes"},"change_message_id":"7f84bdeaf07a58445d1cc457f6ac58a31607afdb","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"008012b2_30f9d71d","updated":"2023-09-27 12:12:07.000000000","message":"+1!, it\u0027s great that more developers are taking on maintenance of charms :)","commit_id":"190fad6552602011ccf2aa81a9f4c9bbb9f8151e"},{"author":{"_account_id":20870,"name":"Alex Kavanagh","email":"alex@ajkavanagh.co.uk","username":"ajkavanagh"},"change_message_id":"cd24ebb80c626111b22590ecd405d1f31c6f0eb0","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"a443c1a3_4fa234c8","updated":"2023-09-27 09:58:26.000000000","message":"I think this is good; it will certainly open up the opportunities to contributions and development velocity for charms that \u0027fit\u0027 into the OpenStack solution but have principle involvement from outside of the charms core.","commit_id":"190fad6552602011ccf2aa81a9f4c9bbb9f8151e"}]}