)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":15993,"name":"Amy Marrich","display_name":"Amy Marrich (spotz)","email":"amy@demarco.com","username":"amarrich"},"change_message_id":"a50dba7ff44efa05b535679f1b48a0cffbbb3ca8","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"ddb7a70f_bf548438","updated":"2022-04-29 22:34:42.000000000","message":"I think the name is important for Community and Marketing","commit_id":"9a6130bb8a3f8441a455d1a1eb28749dde1782a3"},{"author":{"_account_id":1004,"name":"Mohammed Naser","email":"mnaser@vexxhost.com","username":"mnaser"},"change_message_id":"6977400ed65a1b03d541cc5267fb6685d23565ed","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"5572b609_27cbf4f6","updated":"2022-04-29 22:24:41.000000000","message":"I think this is a loss for our community, I can name several very large open source projects of different scales that keep a release name:\n\n- OpenDaylight\n- Debian\n- Ubuntu\n\nThere\u0027s probably way more.  If the process is the painful point here, I think the foundation staff expressed that they would take that on in order to conserve the marketing \"terminology\", which is a huge oversight by the technical committee IMHO.\n\nThe process isn\u0027t perfect, there won\u0027t be a perfect process.  but, I think this is worse than a less-than-perfect process.","commit_id":"9a6130bb8a3f8441a455d1a1eb28749dde1782a3"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"747584957545b97d9ceadd46463cb7d476188e52","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"5d6ec618_031caeb8","updated":"2022-04-29 14:49:38.000000000","message":"agree with ideas as discussed in PTG, one comment to explain the reason. ","commit_id":"9a6130bb8a3f8441a455d1a1eb28749dde1782a3"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"ef8c4e7fb5e5a1a477322b3461a0cad906b6a239","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"64029eae_e0c61f61","in_reply_to":"09e00d73_09cb7928","updated":"2022-04-30 02:16:28.000000000","message":"That is also one option we can try, but we tried to limit the scope with few of the proposal I listed in \u0027Tried to solve it in many ways\u0027 section like \u0027name on major city\u0027, \u0027movies\u0027 etc and it did not went through. \n\nI feel any process, schema we use as long as we open those name selection/nomination etc to community we are going to have the issue. And selecting the name without consultation/informing the community also does not feel good to me(maybe it\u0027s just me and this might be ok to do).\n\nI myself do not want to drop name and for that reason I volunteer to drive the process for couple of cycle but by seeing its benefits vs problem and time it cause\nI thought that is best way to do.","commit_id":"9a6130bb8a3f8441a455d1a1eb28749dde1782a3"},{"author":{"_account_id":4690,"name":"melanie witt","display_name":"melwitt","email":"melwittt@gmail.com","username":"melwitt"},"change_message_id":"b7f9536c05cd9b9321ab7c4266b30e86d7f95a1a","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"09e00d73_09cb7928","in_reply_to":"1900540c_6f5a28fd","updated":"2022-04-30 00:56:43.000000000","message":"I wish to keep release names too but I agree that the level of unrest and effort spent on it as a result has been excessive. As for why other projects are able to have release names successfully, I think it\u0027s likely because their naming scheme limits the possibilities for names. Ubuntu uses \"Adjective Animal\" and Ceph uses only/mostly words related to octopus or ocean, for example.\n\nAs I see it, the thing that needs to be solved is, how to avoid anyone having a serious issue with the name. Could we limit the scope of possible names to be more like Ubuntu and Ceph to \"hopefully\" avoid controversies in the future? Could the community agree on such a theme if so? This I don\u0027t know.\n\nSo, as much as I don\u0027t like to lose release names, I sympathize with the TC who has had to spend significant energy on naming controversies.","commit_id":"9a6130bb8a3f8441a455d1a1eb28749dde1782a3"},{"author":{"_account_id":1004,"name":"Mohammed Naser","email":"mnaser@vexxhost.com","username":"mnaser"},"change_message_id":"d1480cd0dea6a57bc4111e7f6b5c8fd27862986a","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"5fb4f9b0_291b2910","in_reply_to":"50190d7a_3ac677b0","updated":"2022-04-30 02:46:24.000000000","message":"I stand by my points and I think the Debian community is probably way bigger and they still manage to get a name out.\n\nThere will be some people who will be unhappy.  There\u0027s way more people that will be unhappy if the release names go.","commit_id":"9a6130bb8a3f8441a455d1a1eb28749dde1782a3"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"50a8446fdecda13892a2cba6ffa5bb200c788d96","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"1900540c_6f5a28fd","in_reply_to":"5572b609_27cbf4f6","updated":"2022-04-29 23:46:54.000000000","message":"yeah, agree that they have name system but I am not sure how many culture/international communities or number of contributors are involved in those communities. I think that is the key here, big communities like OpenStack are more chance having such issues.\n\nI feel keeping name are more problematic then dropping, it hardly matter what process we use or who select the name. Either foundation does, it will not solve the current problem we have (I have added those in review).\n\nI will be more happy to know how foundation or any other team taking these naming process will solve the problem which TC is not able to do.","commit_id":"9a6130bb8a3f8441a455d1a1eb28749dde1782a3"},{"author":{"_account_id":11975,"name":"Slawek Kaplonski","email":"skaplons@redhat.com","username":"slaweq"},"change_message_id":"5cb4692475b0dc95015c16d7a05217df8bba757a","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"bd0e1039_f178683f","in_reply_to":"5fb4f9b0_291b2910","updated":"2022-05-02 09:34:16.000000000","message":"That\u0027s true that there are big projects which are naming their releases. But on the other hand there are also huge open source projects which don\u0027t have any \"marketing\" names (or I don\u0027t know about them at all) and are still doing fine, like e.g. Firefox, Chromium, Linux Kernel (ok, it has some names too but I don\u0027t think it\u0027s really well known and widely used), Fedora and  probably many others.","commit_id":"9a6130bb8a3f8441a455d1a1eb28749dde1782a3"},{"author":{"_account_id":4690,"name":"melanie witt","display_name":"melwitt","email":"melwittt@gmail.com","username":"melwitt"},"change_message_id":"795df1ccc403f13a53ca89f743473ad0ed24f755","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"50190d7a_3ac677b0","in_reply_to":"64029eae_e0c61f61","updated":"2022-04-30 02:43:22.000000000","message":"That is true, I did see the \"cities\" and \"movies\" ideas from the past. Those two IMHO are things that can pretty easily reference some kind of culture/history/politics and have a higher chance of being controversial. It\u0027s not like types of animals or types of trees or types of gemstones, for example. Speaking of animals, I was looking forward to Aardvark :)\n\nYeah, TBH when the idea of selecting the name without consultation of the entire community was first suggested in the past, it felt exclusive in comparison to the prior open nomination and vote. It\u0027s all relative. Personally, at this stage I would rather have someone select names without any input over not having any names at all. And I think the foundation would be well suited for selecting names as they are the ones who know the marketing.\n\nI hear you. That is why I won\u0027t vote -1 on this because I have seen the problems the TC has had to manage and am understanding to the idea of moving away from naming.","commit_id":"9a6130bb8a3f8441a455d1a1eb28749dde1782a3"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"50a8446fdecda13892a2cba6ffa5bb200c788d96","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"4fcf58a0_829bf9f9","in_reply_to":"ddb7a70f_bf548438","updated":"2022-04-29 23:46:54.000000000","message":"yes, we are not denying that. What we are saying that we have to see both side of it, pros and cons and by seeing all the problem we are facing since long, it is clear that name are more problematic than its benefits.","commit_id":"9a6130bb8a3f8441a455d1a1eb28749dde1782a3"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"f211113cb74df957e49734789b1d902a98cb43ab","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"80ccad77_3e1261e7","updated":"2022-04-30 02:18:40.000000000","message":"\u003e Patch Set 2:\n\u003e \n\u003e melanie witt wrote:\n\u003e \n\u003e \u003e Which AFAIK was the first time name issues happened.\n\u003e \n\u003e While I\u0027m disinclined to hunt through the ML archive at the moment, Icehouse was problematic in that it was an English street name in HK, and so representative of their lengthy English occupation (but this was chosen because finding transliterated Cantonese names starting with the Latin \"I\" was essentially impossible).\n\nack, I will add this also.","commit_id":"eab7d63c5cca1f59e19dcefa2b665950e7f2caf9"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"50a8446fdecda13892a2cba6ffa5bb200c788d96","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"770ff3f5_2ae18b64","updated":"2022-04-29 23:46:54.000000000","message":"I am adding the history to record the problems and what all ways we already discussed during Ussuri cycle so that everyone know about it.\n\nBut there is no change than initial proposal so please re-vote or re-read and vote :). I did not mean to remove your feedback vote here.","commit_id":"eab7d63c5cca1f59e19dcefa2b665950e7f2caf9"},{"author":{"_account_id":6476,"name":"Thomas Goirand","email":"thomas@goirand.fr","username":"thomas-goirand"},"change_message_id":"e940896a828a10e42f217bb2e2d2ef3c3d9d2a52","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"26d0f5e4_e26b03a4","updated":"2022-05-12 11:33:08.000000000","message":"Please keep release names.","commit_id":"5ce632f76330b5ec9abe36a376478c25032ba82f"},{"author":{"_account_id":2033,"name":"Belmiro Moreira","email":"moreira.belmiro.email.lists@gmail.com","username":"moreira-belmiro-email-lists"},"change_message_id":"e4d3083e4000b1c162e89b878d88c6a1c204629c","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"ab3f8d61_81a16050","updated":"2022-05-03 07:39:11.000000000","message":"Release names can be problematic as described in this proposal. However, I still think that the release name is important for the community. It’s part of the OpenStack culture! Is something that we have since the release “A” for “Austin”. I never saw anyone mentioning that they are still running the release “2011.3” and need to upgrade. Instead the community mentions the release name, “Diablo”.\n\nHaving said that, I also believe it’s important to have a clear release identification schema without the ambiguity of the alphabet iteration.\n\nIn my opinion both an coexist.\n","commit_id":"5ce632f76330b5ec9abe36a376478c25032ba82f"},{"author":{"_account_id":11975,"name":"Slawek Kaplonski","email":"skaplons@redhat.com","username":"slaweq"},"change_message_id":"c72d1f288b2139d3bf736942cc56e9f3941c8686","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"ec6c7a3a_a5cb9737","updated":"2022-05-02 09:26:33.000000000","message":"Thx gmann for all that historical context which I wasn\u0027t really fully aware of 😊","commit_id":"5ce632f76330b5ec9abe36a376478c25032ba82f"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"5d05e6ab9ab389c5da576fc6b86e113a2c3ab250","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"a45f0208_b3b6c3e5","updated":"2022-05-02 16:38:39.000000000","message":"just recording my vote/agreement on this.","commit_id":"5ce632f76330b5ec9abe36a376478c25032ba82f"}],"reference/release-naming.rst":[{"author":{"_account_id":5263,"name":"Jeremy Stanley","display_name":"fungi","email":"fungi@yuggoth.org","username":"fungi","status":"missing, presumed fed"},"change_message_id":"f749b3f2ddd4b403087ce1de8f2b71dbae9c2223","unresolved":false,"context_lines":[{"line_number":27,"context_line":""},{"line_number":28,"context_line":"The release identification schema replaces the release name."},{"line_number":29,"context_line":"It\u0027s an unambiguous way to identify OpenStack releases and will not cause any"},{"line_number":30,"context_line":"problems with choosing release names."},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"Polls"},{"line_number":33,"context_line":"-----"}],"source_content_type":"text/x-rst","patch_set":1,"id":"ed384bad_3c21fa5c","line":30,"updated":"2022-04-29 11:40:09.000000000","message":"Lack of numbers weren\u0027t causing problems with choosing release names either, after all, release name choosing problems were independent of the presence or absence of version numbers. This would be more clearly phrased as, \"It\u0027s an unambiguous way to identify OpenStack releases, and avoids release naming problems by not having release names.\"","commit_id":"9a6130bb8a3f8441a455d1a1eb28749dde1782a3"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"50a8446fdecda13892a2cba6ffa5bb200c788d96","unresolved":false,"context_lines":[{"line_number":27,"context_line":""},{"line_number":28,"context_line":"The release identification schema replaces the release name."},{"line_number":29,"context_line":"It\u0027s an unambiguous way to identify OpenStack releases and will not cause any"},{"line_number":30,"context_line":"problems with choosing release names."},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"Polls"},{"line_number":33,"context_line":"-----"}],"source_content_type":"text/x-rst","patch_set":1,"id":"d3126945_74a1656c","line":30,"in_reply_to":"67b5fb13_2235f8c7","updated":"2022-04-29 23:46:54.000000000","message":"I added the cases where community raised the issues.\n\nWe had these issue when we had community voting or TC voting only so that hardly matter. overall I am saying it does not matter which process you use to select name or who select the name, *name* will be problematic.","commit_id":"9a6130bb8a3f8441a455d1a1eb28749dde1782a3"},{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"dc1fcafafa148a336c61a86937fa993f0b45818d","unresolved":false,"context_lines":[{"line_number":27,"context_line":""},{"line_number":28,"context_line":"The release identification schema replaces the release name."},{"line_number":29,"context_line":"It\u0027s an unambiguous way to identify OpenStack releases and will not cause any"},{"line_number":30,"context_line":"problems with choosing release names."},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"Polls"},{"line_number":33,"context_line":"-----"}],"source_content_type":"text/x-rst","patch_set":1,"id":"67b5fb13_2235f8c7","line":30,"in_reply_to":"ab690e93_ec94b786","updated":"2022-04-29 18:50:55.000000000","message":"Hi Ghanshyam, slawek, TC members - I\u0027m sorry I didn\u0027t show up in the room where this discussion happened at the Project Teams Gathering - you know how busy PTG gets, and not everyone interested can make it into a room due to project discussions that happen in parallel. \n\n\nI strongly object to this wearing my community mentor hat and my community leader and member hat. The release naming process may have its flaws. However, we\u0027ve persisted. Alphabetically named releases are an attractive feature of this community to new contributors. I\u0027ve had many 1x1 discussions and can attest to how new contributors enjoy working on a release with a code name, and appreciate the storied relevance of the names democratically chosen by the community.  \n\nI would like to know where the problems you mentioned were raised with the wider community. \n\n\n\u003e We are a wider community with many international communities, developers, and cultures and choosing a perfect name satisfying all of them is not possible.\n\nThis is where community voting would help (not TC voting, let us revert to community voting - would you like to run a poll?). I understand there were disagreements in the past; but, could we just tag them as hiccups? Can we introduce a way to record -1 votes with publicly visible reasons and use that as a way to hear other community members\u0027 views about a name? \n\n\n\u003e We as individuals also have some problems with a few names which might be due to emotions. politically, or historically. And filtering them is not possible.\n\nallowing people to promote/demote names with explanation prior to a formal vote will allow filtering organically. The foundation does legal checks anyway.. why is this a problem?\n\n\u003e Name after election need trademark checks from the foundation as a final step and there is always a chance that winning names are filtered out so the electorate might not be happy with that. So the process is also not perfect.\n\nbut, the electorate has lived with it - it\u0027s the reality of trademarking processes... why throw the baby out with the bath water here?","commit_id":"9a6130bb8a3f8441a455d1a1eb28749dde1782a3"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"747584957545b97d9ceadd46463cb7d476188e52","unresolved":false,"context_lines":[{"line_number":27,"context_line":""},{"line_number":28,"context_line":"The release identification schema replaces the release name."},{"line_number":29,"context_line":"It\u0027s an unambiguous way to identify OpenStack releases and will not cause any"},{"line_number":30,"context_line":"problems with choosing release names."},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"Polls"},{"line_number":33,"context_line":"-----"}],"source_content_type":"text/x-rst","patch_set":1,"id":"ab690e93_ec94b786","line":30,"in_reply_to":"ed384bad_3c21fa5c","updated":"2022-04-29 14:49:38.000000000","message":"Also, let\u0027s add a detailed explanation about what problem we faced in the \u0027release name\u0027 process and why we are dropping it so that in future we know what we are going to bring all these roblemes back if we think of release name again.\n\nWhy we dropped the release name:\n--------------------------------\n\nProblem with release name:\n``````````````````````````\n- We are a wider community with many international communities, developers, and cultures and choosing a perfect name satisfying all of them is not possible.\n- We as individuals also have some problems with a few names which might be due to emotions. politically, or historically. And filtering them is not possible.\n- Name after election need trademark checks from the foundation as a final step and there is always a chance that winning names are filtered out so the electorate might not be happy with that. So the process is also not perfect.\n\nTried to solve it in many ways:\n```````````````````````````````\nThere were a lot of proposals to solve the above issues but we could not get any agreement on either of these and live with all these issues until the Zed cycle.\n\n* https://review.opendev.org/c/openstack/governance/+/677749\n* https://review.opendev.org/c/openstack/governance/+/678046\n* https://review.opendev.org/c/openstack/governance/+/677745\n* https://review.opendev.org/c/openstack/governance/+/684688\n* https://review.opendev.org/c/openstack/governance/+/675788\n* https://review.opendev.org/c/openstack/governance/+/687764\n* https://review.opendev.org/c/openstack/governance/+/677827\n* https://review.opendev.org/c/openstack/governance/+/677748\n* https://review.opendev.org/c/openstack/governance/+/677747\n* https://review.opendev.org/c/openstack/governance/+/677746\n*","commit_id":"9a6130bb8a3f8441a455d1a1eb28749dde1782a3"},{"author":{"_account_id":4690,"name":"melanie witt","display_name":"melwitt","email":"melwittt@gmail.com","username":"melwitt"},"change_message_id":"b7f9536c05cd9b9321ab7c4266b30e86d7f95a1a","unresolved":true,"context_lines":[{"line_number":61,"context_line":""},{"line_number":62,"context_line":"* `Zed release name issue 2"},{"line_number":63,"context_line":"  \u003chttps://meetings.opendev.org/irclogs/%23openstack-tc/%23openstack-tc.2022-03-08.log.html#t2022-03-08T14:35:26\u003e`_"},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"Tried to solve it in many ways"},{"line_number":66,"context_line":"``````````````````````````````"},{"line_number":67,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"e526fb46_77f0f089","line":64,"updated":"2022-04-30 00:56:43.000000000","message":"There was also the M release name issue:\n\nhttps://lists.openstack.org/pipermail/openstack-dev/2015-July/068757.html\n\nWhich AFAIK was the first time name issues happened.","commit_id":"eab7d63c5cca1f59e19dcefa2b665950e7f2caf9"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"ef8c4e7fb5e5a1a477322b3461a0cad906b6a239","unresolved":true,"context_lines":[{"line_number":61,"context_line":""},{"line_number":62,"context_line":"* `Zed release name issue 2"},{"line_number":63,"context_line":"  \u003chttps://meetings.opendev.org/irclogs/%23openstack-tc/%23openstack-tc.2022-03-08.log.html#t2022-03-08T14:35:26\u003e`_"},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"Tried to solve it in many ways"},{"line_number":66,"context_line":"``````````````````````````````"},{"line_number":67,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"c920e534_f008ac99","line":64,"in_reply_to":"e526fb46_77f0f089","updated":"2022-04-30 02:16:28.000000000","message":"Yeah, thanks I remember that now.","commit_id":"eab7d63c5cca1f59e19dcefa2b665950e7f2caf9"},{"author":{"_account_id":11975,"name":"Slawek Kaplonski","email":"skaplons@redhat.com","username":"slaweq"},"change_message_id":"c72d1f288b2139d3bf736942cc56e9f3941c8686","unresolved":true,"context_lines":[{"line_number":44,"context_line":""},{"line_number":45,"context_line":"* We as individuals also have some problems with a few names which might be"},{"line_number":46,"context_line":"  due to emotions. politically, or historically. And filtering them is not"},{"line_number":47,"context_line":"  possible."},{"line_number":48,"context_line":""},{"line_number":49,"context_line":"* Name after election need trademark checks from the foundation as a final"},{"line_number":50,"context_line":"  step and there is always a chance that winning names are filtered out so"}],"source_content_type":"text/x-rst","patch_set":3,"id":"fbd7f57c_a8793abf","line":47,"updated":"2022-05-02 09:26:33.000000000","message":"I don\u0027t know if that\u0027s worth to mention but often such concerns are raised even after name was already choosen (see Zed release issue 2 for example). In such case changing the name may be even harder.","commit_id":"5ce632f76330b5ec9abe36a376478c25032ba82f"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"442c0f0968d54f70606fbafdd6ab12b5d70c0691","unresolved":true,"context_lines":[{"line_number":44,"context_line":""},{"line_number":45,"context_line":"* We as individuals also have some problems with a few names which might be"},{"line_number":46,"context_line":"  due to emotions. politically, or historically. And filtering them is not"},{"line_number":47,"context_line":"  possible."},{"line_number":48,"context_line":""},{"line_number":49,"context_line":"* Name after election need trademark checks from the foundation as a final"},{"line_number":50,"context_line":"  step and there is always a chance that winning names are filtered out so"}],"source_content_type":"text/x-rst","patch_set":3,"id":"6614f19b_cf0830e6","line":47,"in_reply_to":"fbd7f57c_a8793abf","updated":"2022-05-02 16:38:03.000000000","message":"True, that will be very costly if we do and if we don\u0027t then disagreement stays so both situation not good.","commit_id":"5ce632f76330b5ec9abe36a376478c25032ba82f"}]}