)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":15343,"name":"Tim Burke","email":"tburke@nvidia.com","username":"tburke"},"change_message_id":"2a0422f45df7193a06e75034a8da2f681516691c","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"8400d112_4feb0d9e","updated":"2026-02-11 01:48:05.000000000","message":"**If** we want to bring back the badges, I think it\u0027ll look best with inline images, like\n```\n|openstack_badge| |pypi_badge|\n\n.. |openstack_badge| image:: https://governance.openstack.org/tc/badges/python-swiftclient.svg\n\n.. |pypi_badge| image:: https://img.shields.io/pypi/v/python-swiftclient.svg\n    :target: https://pypi.org/project/python-swiftclient/\n    :alt: Latest Version\n```\nThough it then makes me wonder why we wouldn\u0027t just manage the OpenSSF badge ourselve, like\n```\n|openstack_badge| |openssf_badge| |pypi_badge|\n\n.. |openstack_badge| image:: https://governance.openstack.org/tc/badges/python-swiftclient.svg\n    :target: https://governance.openstack.org/tc/reference/projects/\n    :alt: OpenStack Community Project\n\n.. |openssf_badge| image:: https://www.bestpractices.dev/projects/246/badge\n    :target: https://www.bestpractices.dev/projects/246\n    :alt: OpenSSF Best Practices\n\n.. |pypi_badge| image:: https://img.shields.io/pypi/v/python-swiftclient.svg\n    :target: https://pypi.org/project/python-swiftclient/\n    :alt: Latest Version\n```\n(Aside from, y\u0027know, the TC badge trying to do too much.)","commit_id":"c1a2d3918e93937a755dbbf1303317ee2bf41ede"},{"author":{"_account_id":15343,"name":"Tim Burke","email":"tburke@nvidia.com","username":"tburke"},"change_message_id":"a66dc0d1e2ff3654ff3730537cf30846ebd533be","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"5a7aa513_4e67c42a","updated":"2026-02-10 23:25:46.000000000","message":"OK, so the situation has improved since May, when I [left a comment on a similar change for Swift](https://review.opendev.org/c/openstack/swift/+/948495): in particular, the badges are now legible.\n\nI\u0027ve still got some questions/comments, though:\n\n- [The SVG image](https://governance.openstack.org/tc/badges/python-swiftclient.svg) has two separate links for the two separate badges, but [a GitHub rendering of the README](https://github.com/tipabu/python-swiftclient/tree/readme-badge?tab\u003dreadme-ov-file#python-bindings-to-the-openstack-object-storage-api) (that\u0027s the audience we\u0027re doing this for, right?) is just going to link to (a copy of) the badge image itself. Should we pick one of the two to add as a `:target:`?\n- When I click through the `cii best practices | passing` badge on the image, the site seems to indicate that it should read `openssf best practices | passing`.\n- Downstream packagers [seem to prefer that we not include badges](https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/OOHJA4ZYEH4HXX3VF6PS3AQ7TWYVCK2R/#MHYS5JNQ4PVXCJRK2Q2O3ZOBAEIYVETS) -- would we be better off removing the PyPI badge rather than adding another one?\n\nThe other URL changes LGTM though.","commit_id":"c1a2d3918e93937a755dbbf1303317ee2bf41ede"},{"author":{"_account_id":37598,"name":"Ivan Anfimov","display_name":"Ivan Anfimov","email":"lazekteam@gmail.com","username":"anfimovir"},"change_message_id":"27f23f25f6fb200a75ce7c6e4909bcdee6fc0ea9","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"a6acc725_e552cea8","in_reply_to":"5a7aa513_4e67c42a","updated":"2026-02-11 00:31:27.000000000","message":"@gouthampravi@gmail.com hello, please help with this questions.","commit_id":"c1a2d3918e93937a755dbbf1303317ee2bf41ede"}]}