)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"753b173281bc9e0b65c175461067738d2e557a94","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"576e7518_da32ffce","updated":"2024-09-11 16:35:13.000000000","message":"+1, thanks Tim.\n\nNOTE: This needs to be rebased after election are completed and election official propose the election results in governance which add \u0027PTL appointment needed\u0027 for Swift. All vote will be reset that time so I will wait for that rebase to vote.","commit_id":"406f4c1a6aaee0f734445124447ae2896f3c6ad8"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"6230a9e3ffeb3612c8f44cf92ad998384adba664","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"3369f751_083c2653","updated":"2024-09-19 21:48:30.000000000","message":"election result are merged now and you need to rebase this on master for the PTL appointment change https://review.opendev.org/c/openstack/governance/+/929940","commit_id":"406f4c1a6aaee0f734445124447ae2896f3c6ad8"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"147f9b15342ba298d63ecb34b97998db631c40bb","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"e400550c_9be4b664","updated":"2024-09-11 16:38:15.000000000","message":"example https://review.opendev.org/c/openstack/governance/+/878286","commit_id":"406f4c1a6aaee0f734445124447ae2896f3c6ad8"},{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"dffcb24ab4f51ba1839f331b53aa4dd2cdb92a92","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"66880ad4_4225c690","updated":"2024-09-25 22:25:47.000000000","message":"Thank you @tburke@nvidia.com\n\nIs there have been anything we could have done differently to avoid this appointment? We tried a few things during this election cycle:\n\n- The nomination periods were published a couple months in advance of the election cycle on the OpenStack Release Schedule\n- The PTL nomination period was advertised over the OpenStack Mailing list for several weeks; and,\n- election officials sent an email to all project contributors about a week prior to the PTL nomination deadline","commit_id":"58db7ae4c79247acb4fe6c76d77a4f1059940ed0"},{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"9a96b53879904fd98ccc61d2b872500208318466","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"2980ed12_253db172","updated":"2024-10-07 16:28:48.000000000","message":"This patch has had sufficient soak-time and a majority of the TC approving. Lets get it in.. Thanks and all the best, @tburke@nvidia.com","commit_id":"58db7ae4c79247acb4fe6c76d77a4f1059940ed0"},{"author":{"_account_id":15343,"name":"Tim Burke","email":"tburke@nvidia.com","username":"tburke"},"change_message_id":"bb05ce00f8fe6da3dd602804b6c74aba823ddcd2","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"7ced4d82_0e5d0996","in_reply_to":"00623cb7_db0322ff","updated":"2024-10-07 17:01:32.000000000","message":"Oh, we\u0027re definitely aware of the goal, and we\u0027ve been wanting to reduce our dependence upon eventlet for a while -- since at least the hummingbird days. Unfortunately, it\u0027s pretty well entrenched: looking at [the common patterns](https://wiki.openstack.org/wiki/Eventlet-removal#Identifying_Common_Pattern) that were written up, we tick every box except `spawn_after`. Probably the worst of it is our use of eventlet as a WSGI server; we not only [subclass their `HttpProtocol`](https://github.com/openstack/swift/blob/2.34.0/swift/common/http_protocol.py#L31) (which in turn is subclassed from stdlib), but we even [depend upon broken behaviors](https://bugs.launchpad.net/swift/+bug/1496636) which we haven\u0027t reported to eventlet because we don\u0027t want them fixed (yet). It\u0027s gonna be a mess.","commit_id":"58db7ae4c79247acb4fe6c76d77a4f1059940ed0"},{"author":{"_account_id":15343,"name":"Tim Burke","email":"tburke@nvidia.com","username":"tburke"},"change_message_id":"ace21c657743cd4f76dc4cb1becfa2b67376bff4","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"a46da724_29ae1eee","in_reply_to":"66880ad4_4225c690","updated":"2024-10-03 21:28:25.000000000","message":"Probably not? I saw the reminders, thank you -- but every time I went to self-nominate, it inevitably turned into me burning an hour or two mostly navel-gazing about the state of Swift, which isn\u0027t great:\n\n- If you look at [Swift contributions over the last year](https://www.stackalytics.io/report/contribution?module\u003dswift-group\u0026project_type\u003dopenstack\u0026days\u003d365), there are seven most-active reviewers -- six of them work for Nvidia. If we still had tags, I surely should have added the `team:single-vendor` tag a while back.\n- As such, priorities tend to shift more quickly and immediately in response to business demands. I\u0027ve lost track of the number of things I\u0027ve been excited to work on that got tabled indefinitely.\n- Despite the single-company direction that Swift has taken (and in all fairness, it has been trending that way for a loooong while, even prior to Nvidia acquiring SwiftStack), I\u0027ve not seen many of my teammates in-person for literally years. It\u0027s a struggle to maintain a sense of community *even within this limited group*.\n\nOn the whole it makes it hard for me to craft a message of hope, or even one of reasonable expectation-setting regarding what we\u0027ll be working on over the next cycle.","commit_id":"58db7ae4c79247acb4fe6c76d77a4f1059940ed0"},{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"9a96b53879904fd98ccc61d2b872500208318466","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"00623cb7_db0322ff","in_reply_to":"a46da724_29ae1eee","updated":"2024-10-07 16:28:48.000000000","message":"Thank you for responding; this is worth a larger discussion. Swift has seen waves of activity based on use cases; and relative periods of stability where its almost considered \"feature-complete\" - so I can relate your response to that context. We probably set the expectation a while ago that PTL nominations also set the course for the upcoming release - but really they don\u0027t have to be. \n\n\"\"\"\nI\u0027m X, and would like (to continue) to be PTL for Y term.\n\"\"\"\n\nor a version of that is just fine too. \n\nI appreciate the candid feedback; The next \"big\" churn i see in the project is tackling technical debt like eventlet-removal [1]; I hope the team\u0027s been looking at this eventuality :) We might get in touch with you soon with questions. \n\n\n[1] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/YAX2X7C6FCDDNN4SBFN7BNSUA44Z6VXA/","commit_id":"58db7ae4c79247acb4fe6c76d77a4f1059940ed0"}]}