)]}'
{"reference/release-naming.rst":[{"author":{"_account_id":6547,"name":"Andreas Jaeger","email":"jaegerandi@gmail.com","username":"jaegerandi"},"change_message_id":"049c1a27cb5266f17b3b2b30bbbd40deca04194c","unresolved":false,"context_lines":[{"line_number":46,"context_line":""},{"line_number":47,"context_line":"#. The election official, in consultation with the TC, should remove from"},{"line_number":48,"context_line":"   the list any name that feedback suggests would be culturally"},{"line_number":49,"context_line":"   inappropriate in any sector of the OpenStack community. The purpose of"},{"line_number":50,"context_line":"   naming the release after a geographical feature is in part to honor the"},{"line_number":51,"context_line":"   host city, and we owe it to our hosts not to associate them with terms"},{"line_number":52,"context_line":"   that unwittingly conflict with the `Code of Conduct"}],"source_content_type":"text/x-rst","patch_set":1,"id":"7faddb67_163f3a25","line":49,"range":{"start_line":49,"start_character":17,"end_line":49,"end_character":30},"updated":"2019-08-21 17:19:34.000000000","message":"That sounds too broad.\n\nYou state later \"owe it to our hosts\".\n\nI see that that you don\u0027t want to use a name for the summit in country X that is inappropriate for country X. But the wording \"in any sector\" implies it\u0027s worldwide. So, if it\u0027s inappropriate for whatever reason to e.g. myself or those in my village - would that fall under the role? With the wording above, it would for me.\n\nLet\u0027s not open the floodgates.","commit_id":"28b8ed291ad6a542d8a06c1af27beb113b7212ee"},{"author":{"_account_id":4257,"name":"Zane Bitter","email":"zbitter@redhat.com","username":"zaneb"},"change_message_id":"fce787e27435046591a746203076f897d2f24e7d","unresolved":false,"context_lines":[{"line_number":46,"context_line":""},{"line_number":47,"context_line":"#. The election official, in consultation with the TC, should remove from"},{"line_number":48,"context_line":"   the list any name that feedback suggests would be culturally"},{"line_number":49,"context_line":"   inappropriate in any sector of the OpenStack community. The purpose of"},{"line_number":50,"context_line":"   naming the release after a geographical feature is in part to honor the"},{"line_number":51,"context_line":"   host city, and we owe it to our hosts not to associate them with terms"},{"line_number":52,"context_line":"   that unwittingly conflict with the `Code of Conduct"}],"source_content_type":"text/x-rst","patch_set":1,"id":"7faddb67_9fec9d29","line":49,"range":{"start_line":49,"start_character":17,"end_line":49,"end_character":30},"in_reply_to":"7faddb67_163f3a25","updated":"2019-08-21 19:45:19.000000000","message":"I\u0027m literally quoting from the email that resolved the M naming situation, and making it clear that we can and should continue to do that before it gets to that point.","commit_id":"28b8ed291ad6a542d8a06c1af27beb113b7212ee"}]}