)]}'
{"resolutions/20190322-namespace-unofficial-projects.rst":[{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"e4ba29ffedc8ca04b05944f24ba0e9b3c903e962","unresolved":false,"context_lines":[{"line_number":7,"context_line":"move git hosting to new URLs and new backends, OpenStack has an opportunity"},{"line_number":8,"context_line":"to revisit previous choices about how projects are namespaced."},{"line_number":9,"context_line":""},{"line_number":10,"context_line":"Once upon a time, OpenStack had a concept of \"stackforge\" to host unofficial"},{"line_number":11,"context_line":"projects. Eventually, the TC :ref:`retired the stackforge name"},{"line_number":12,"context_line":"\u003c20160119_stackforge_resolution\u003e` and git namespace in order to simplify the"},{"line_number":13,"context_line":"logistics of moving projects from unofficial to official, and the \"openstack\""},{"line_number":14,"context_line":"git namespace became a place for all projects hosted on OpenStack\u0027s git"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_941b7cc8","line":11,"range":{"start_line":10,"start_character":0,"end_line":11,"end_character":9},"updated":"2019-03-25 11:42:33.000000000","message":"Ha. As much as I like story-teller vibe. Let\u0027s remove it :) \n\nAnd maybe link to Stackforge if we can. Which we totes can: https://github.com/stackforge","commit_id":"a968dcf2de284d0734d410d83d90818940710c34"},{"author":{"_account_id":10343,"name":"Jim Rollenhagen","email":"jim@jimrollenhagen.com","username":"jimrollenhagen"},"change_message_id":"fac8794ab528d47d453455b88d9e62cc5fc0c292","unresolved":false,"context_lines":[{"line_number":7,"context_line":"move git hosting to new URLs and new backends, OpenStack has an opportunity"},{"line_number":8,"context_line":"to revisit previous choices about how projects are namespaced."},{"line_number":9,"context_line":""},{"line_number":10,"context_line":"Once upon a time, OpenStack had a concept of \"stackforge\" to host unofficial"},{"line_number":11,"context_line":"projects. Eventually, the TC :ref:`retired the stackforge name"},{"line_number":12,"context_line":"\u003c20160119_stackforge_resolution\u003e` and git namespace in order to simplify the"},{"line_number":13,"context_line":"logistics of moving projects from unofficial to official, and the \"openstack\""},{"line_number":14,"context_line":"git namespace became a place for all projects hosted on OpenStack\u0027s git"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_ba677fe9","line":11,"range":{"start_line":10,"start_character":0,"end_line":11,"end_character":9},"in_reply_to":"5fc1f717_941b7cc8","updated":"2019-03-25 12:41:31.000000000","message":"s/Once upon a time/In the past/ maybe?\n\nAnd stackforge is actually empty, the github link is out of sync and deceiving: http://git.openstack.org/cgit/stackforge","commit_id":"a968dcf2de284d0734d410d83d90818940710c34"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"8dc605a56dbb8ec7627112007cc0296b4e1604cf","unresolved":false,"context_lines":[{"line_number":7,"context_line":"move git hosting to new URLs and new backends, OpenStack has an opportunity"},{"line_number":8,"context_line":"to revisit previous choices about how projects are namespaced."},{"line_number":9,"context_line":""},{"line_number":10,"context_line":"Once upon a time, OpenStack had a concept of \"stackforge\" to host unofficial"},{"line_number":11,"context_line":"projects. Eventually, the TC :ref:`retired the stackforge name"},{"line_number":12,"context_line":"\u003c20160119_stackforge_resolution\u003e` and git namespace in order to simplify the"},{"line_number":13,"context_line":"logistics of moving projects from unofficial to official, and the \"openstack\""},{"line_number":14,"context_line":"git namespace became a place for all projects hosted on OpenStack\u0027s git"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_5a1e9bbb","line":11,"range":{"start_line":10,"start_character":0,"end_line":11,"end_character":9},"in_reply_to":"5fc1f717_ba677fe9","updated":"2019-03-25 13:03:58.000000000","message":"Previously, OpenStack* ?","commit_id":"a968dcf2de284d0734d410d83d90818940710c34"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"e4ba29ffedc8ca04b05944f24ba0e9b3c903e962","unresolved":false,"context_lines":[{"line_number":10,"context_line":"Once upon a time, OpenStack had a concept of \"stackforge\" to host unofficial"},{"line_number":11,"context_line":"projects. Eventually, the TC :ref:`retired the stackforge name"},{"line_number":12,"context_line":"\u003c20160119_stackforge_resolution\u003e` and git namespace in order to simplify the"},{"line_number":13,"context_line":"logistics of moving projects from unofficial to official, and the \"openstack\""},{"line_number":14,"context_line":"git namespace became a place for all projects hosted on OpenStack\u0027s git"},{"line_number":15,"context_line":"infrastructure."},{"line_number":16,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_547f54df","line":13,"range":{"start_line":13,"start_character":66,"end_line":13,"end_character":77},"updated":"2019-03-25 11:42:33.000000000","message":"Remove the inverted comma and just have OpenStack","commit_id":"a968dcf2de284d0734d410d83d90818940710c34"},{"author":{"_account_id":1,"name":"James E. Blair","email":"jim@acmegating.com","username":"corvus"},"change_message_id":"897129e13f8370adb507b46ee3365d8060c0afd6","unresolved":false,"context_lines":[{"line_number":22,"context_line":"It\u0027s become clear that OpenStack should use this opportunity to go back to the"},{"line_number":23,"context_line":"old model of a separate namespace for unofficial projects. When the git"},{"line_number":24,"context_line":"repositories are moved to the new OpenDev infrastructure, a new namespace"},{"line_number":25,"context_line":"called \"unknown\" will be created, and all unofficial projects currently"},{"line_number":26,"context_line":"hosted in the OpenStack infrastructure will be re-located there. All official"},{"line_number":27,"context_line":"projects will remain in the \"openstack\" namespace."},{"line_number":28,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_e126f316","line":25,"updated":"2019-03-22 14:36:33.000000000","message":"Since we\u0027re no longer constrained by what orgs we \"own\" on github, I expect projects to be able to select whatever org they want.  To that end, I started https://ethercalc.openstack.org/opendev-transition\n\nOf course, that doesn\u0027t have a lot of uptake, and I guess we need an answer for the folks who don\u0027t care enough to pick an org name but who can\u0027t be in openstack/ anymore.  For *that* case, perhaps \"unknown\" is okay?  \"did-not-select-an-org/project\"?  Or we could just give each their own org.\n\nMaybe once this resolution is decided, we should push a little harder to get folks to self-select a new org.  We can produce a list at that point.","commit_id":"a968dcf2de284d0734d410d83d90818940710c34"},{"author":{"_account_id":10343,"name":"Jim Rollenhagen","email":"jim@jimrollenhagen.com","username":"jimrollenhagen"},"change_message_id":"803eca5576a6cc3279e78a2f98735bae16066865","unresolved":false,"context_lines":[{"line_number":22,"context_line":"It\u0027s become clear that OpenStack should use this opportunity to go back to the"},{"line_number":23,"context_line":"old model of a separate namespace for unofficial projects. When the git"},{"line_number":24,"context_line":"repositories are moved to the new OpenDev infrastructure, a new namespace"},{"line_number":25,"context_line":"called \"unknown\" will be created, and all unofficial projects currently"},{"line_number":26,"context_line":"hosted in the OpenStack infrastructure will be re-located there. All official"},{"line_number":27,"context_line":"projects will remain in the \"openstack\" namespace."},{"line_number":28,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_615f63e5","line":25,"updated":"2019-03-22 14:25:54.000000000","message":"Yes, \"unknown\" is a terrible name. I don\u0027t have any better ideas, but would love to change it.","commit_id":"a968dcf2de284d0734d410d83d90818940710c34"},{"author":{"_account_id":10343,"name":"Jim Rollenhagen","email":"jim@jimrollenhagen.com","username":"jimrollenhagen"},"change_message_id":"fac8794ab528d47d453455b88d9e62cc5fc0c292","unresolved":false,"context_lines":[{"line_number":22,"context_line":"It\u0027s become clear that OpenStack should use this opportunity to go back to the"},{"line_number":23,"context_line":"old model of a separate namespace for unofficial projects. When the git"},{"line_number":24,"context_line":"repositories are moved to the new OpenDev infrastructure, a new namespace"},{"line_number":25,"context_line":"called \"unknown\" will be created, and all unofficial projects currently"},{"line_number":26,"context_line":"hosted in the OpenStack infrastructure will be re-located there. All official"},{"line_number":27,"context_line":"projects will remain in the \"openstack\" namespace."},{"line_number":28,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_5ab53b31","line":25,"in_reply_to":"5fc1f717_14ec6c8d","updated":"2019-03-25 12:41:31.000000000","message":"\u003e Undisclosed\n \u003e literally means \"not revealed or made known publicly\" which is\n \u003e exactly what these projects will be. \n\nHm, we don\u0027t want them to be hidden, they\u0027re just uncategorized.\n\nSeems like decent support for \"unknown\", unless someone wants to fight hard for something else.","commit_id":"a968dcf2de284d0734d410d83d90818940710c34"},{"author":{"_account_id":970,"name":"Dean Troyer","email":"dtroyer@gmail.com","username":"dtroyer"},"change_message_id":"9673ef38b36d47ddd0c2a0189567e84138425fb9","unresolved":false,"context_lines":[{"line_number":22,"context_line":"It\u0027s become clear that OpenStack should use this opportunity to go back to the"},{"line_number":23,"context_line":"old model of a separate namespace for unofficial projects. When the git"},{"line_number":24,"context_line":"repositories are moved to the new OpenDev infrastructure, a new namespace"},{"line_number":25,"context_line":"called \"unknown\" will be created, and all unofficial projects currently"},{"line_number":26,"context_line":"hosted in the OpenStack infrastructure will be re-located there. All official"},{"line_number":27,"context_line":"projects will remain in the \"openstack\" namespace."},{"line_number":28,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_49928d4d","line":25,"in_reply_to":"5fc1f717_411027a9","updated":"2019-03-22 15:11:15.000000000","message":"@Doug, I think you have a good distinction for unofficial projects, some close to OpenStack and some not so close.\n\nI think it is appropriate for the TC to suggest a path for projects \u0027close\u0027 to OpenStack, maybe that is what stackforge[0] becomes and the rest is unspecified here.\n\n[0] Shed painter ahead: The *forge association is long in the tooth (I tend to skip over projects hosted at sourceforge these days), maybe something like stackyard instead?","commit_id":"a968dcf2de284d0734d410d83d90818940710c34"},{"author":{"_account_id":10343,"name":"Jim Rollenhagen","email":"jim@jimrollenhagen.com","username":"jimrollenhagen"},"change_message_id":"30a96d0f368dbe426b00860cb2067153c78f7c14","unresolved":false,"context_lines":[{"line_number":22,"context_line":"It\u0027s become clear that OpenStack should use this opportunity to go back to the"},{"line_number":23,"context_line":"old model of a separate namespace for unofficial projects. When the git"},{"line_number":24,"context_line":"repositories are moved to the new OpenDev infrastructure, a new namespace"},{"line_number":25,"context_line":"called \"unknown\" will be created, and all unofficial projects currently"},{"line_number":26,"context_line":"hosted in the OpenStack infrastructure will be re-located there. All official"},{"line_number":27,"context_line":"projects will remain in the \"openstack\" namespace."},{"line_number":28,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_e12353bd","line":25,"in_reply_to":"5fc1f717_411027a9","updated":"2019-03-22 14:48:37.000000000","message":"I could live with stackforge. \n\nI imagined we\u0027d move all unofficial projects, and then go ahead and encourage them to find a namespace. If we want to try to get unofficial projects to choose a namespace before the migration, I can reword things here.","commit_id":"a968dcf2de284d0734d410d83d90818940710c34"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"15d7a85d86839591d6665b631614eccbe9dd6660","unresolved":false,"context_lines":[{"line_number":22,"context_line":"It\u0027s become clear that OpenStack should use this opportunity to go back to the"},{"line_number":23,"context_line":"old model of a separate namespace for unofficial projects. When the git"},{"line_number":24,"context_line":"repositories are moved to the new OpenDev infrastructure, a new namespace"},{"line_number":25,"context_line":"called \"unknown\" will be created, and all unofficial projects currently"},{"line_number":26,"context_line":"hosted in the OpenStack infrastructure will be re-located there. All official"},{"line_number":27,"context_line":"projects will remain in the \"openstack\" namespace."},{"line_number":28,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_c983dda8","line":25,"in_reply_to":"5fc1f717_49928d4d","updated":"2019-03-22 15:20:03.000000000","message":"I think I\u0027m with Jim.... We should strongly encourage unofficial projects to grab their own opendev namespace, rather than create or resurrect a brand that might make it desirable to stay in a common namespace.\n\nSo I prefer \"unknown\" or \"attic\" or \"tbd\" or \"abandoned\" or anything else that sounds equally bad as the fallback in case people don\u0027t pick a good namespace :)","commit_id":"a968dcf2de284d0734d410d83d90818940710c34"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"8dc605a56dbb8ec7627112007cc0296b4e1604cf","unresolved":false,"context_lines":[{"line_number":22,"context_line":"It\u0027s become clear that OpenStack should use this opportunity to go back to the"},{"line_number":23,"context_line":"old model of a separate namespace for unofficial projects. When the git"},{"line_number":24,"context_line":"repositories are moved to the new OpenDev infrastructure, a new namespace"},{"line_number":25,"context_line":"called \"unknown\" will be created, and all unofficial projects currently"},{"line_number":26,"context_line":"hosted in the OpenStack infrastructure will be re-located there. All official"},{"line_number":27,"context_line":"projects will remain in the \"openstack\" namespace."},{"line_number":28,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_9a6de333","line":25,"in_reply_to":"5fc1f717_5ab53b31","updated":"2019-03-25 13:03:58.000000000","message":"Uncategorized works? Or maybe unclassified? \n\nOtherwise, sure, unknown!","commit_id":"a968dcf2de284d0734d410d83d90818940710c34"},{"author":{"_account_id":4257,"name":"Zane Bitter","email":"zbitter@redhat.com","username":"zaneb"},"change_message_id":"2d64a76e4b7a7f5853d91430b8a900b2ec50f776","unresolved":false,"context_lines":[{"line_number":22,"context_line":"It\u0027s become clear that OpenStack should use this opportunity to go back to the"},{"line_number":23,"context_line":"old model of a separate namespace for unofficial projects. When the git"},{"line_number":24,"context_line":"repositories are moved to the new OpenDev infrastructure, a new namespace"},{"line_number":25,"context_line":"called \"unknown\" will be created, and all unofficial projects currently"},{"line_number":26,"context_line":"hosted in the OpenStack infrastructure will be re-located there. All official"},{"line_number":27,"context_line":"projects will remain in the \"openstack\" namespace."},{"line_number":28,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_a11a2b14","line":25,"in_reply_to":"5fc1f717_615f63e5","updated":"2019-03-22 14:28:56.000000000","message":"Is this the TC\u0027s problem? From our perspective I think the resolution only needs to say that we don\u0027t want any unofficial projects to remain in the openstack/ namespace.\n\nObviously we can be part of the conversation with OpenDev about where the unofficial projects should wind up, but I think that is ultimately a decision for OpenDev.","commit_id":"a968dcf2de284d0734d410d83d90818940710c34"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"e4ba29ffedc8ca04b05944f24ba0e9b3c903e962","unresolved":false,"context_lines":[{"line_number":22,"context_line":"It\u0027s become clear that OpenStack should use this opportunity to go back to the"},{"line_number":23,"context_line":"old model of a separate namespace for unofficial projects. When the git"},{"line_number":24,"context_line":"repositories are moved to the new OpenDev infrastructure, a new namespace"},{"line_number":25,"context_line":"called \"unknown\" will be created, and all unofficial projects currently"},{"line_number":26,"context_line":"hosted in the OpenStack infrastructure will be re-located there. All official"},{"line_number":27,"context_line":"projects will remain in the \"openstack\" namespace."},{"line_number":28,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_14ec6c8d","line":25,"in_reply_to":"5fc1f717_97538c6b","updated":"2019-03-25 11:42:33.000000000","message":"Just to throw my 2 cents in the ring, I quite like the usage of \"undisclosed\", following along with jroll\u0027s suggestion of unknown. To me, the language here is relatively important. Undisclosed literally means \"not revealed or made known publicly\" which is exactly what these projects will be. That being said, I\u0027m not tied to it especially. I just like the usage of it in this instance :)","commit_id":"a968dcf2de284d0734d410d83d90818940710c34"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"f519398bb74100d010cfdec7877a2fa6fca50c56","unresolved":false,"context_lines":[{"line_number":22,"context_line":"It\u0027s become clear that OpenStack should use this opportunity to go back to the"},{"line_number":23,"context_line":"old model of a separate namespace for unofficial projects. When the git"},{"line_number":24,"context_line":"repositories are moved to the new OpenDev infrastructure, a new namespace"},{"line_number":25,"context_line":"called \"unknown\" will be created, and all unofficial projects currently"},{"line_number":26,"context_line":"hosted in the OpenStack infrastructure will be re-located there. All official"},{"line_number":27,"context_line":"projects will remain in the \"openstack\" namespace."},{"line_number":28,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_411027a9","line":25,"in_reply_to":"5fc1f717_a11a2b14","updated":"2019-03-22 14:38:53.000000000","message":"@Zane: I think they\u0027re looking for guidance about where to put things the OpenStack community builds that are not officially part of the OpenStack \"product\". We have quite a few of those. Some will naturally become part of other OIPs or something else, but some remain \"ours\".\n\n@Jim: You make it clear later that this resolution only applies to things that aren\u0027t claimed by someone else who wants to have their own namespace, but this \"all unofficial projects\" phrase tripped me up at first.\n\nHow do people feel about just resurrecting the stackforge name?","commit_id":"a968dcf2de284d0734d410d83d90818940710c34"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"90a15e231e18cf5f3020209c7bc210e89bc5d576","unresolved":false,"context_lines":[{"line_number":22,"context_line":"It\u0027s become clear that OpenStack should use this opportunity to go back to the"},{"line_number":23,"context_line":"old model of a separate namespace for unofficial projects. When the git"},{"line_number":24,"context_line":"repositories are moved to the new OpenDev infrastructure, a new namespace"},{"line_number":25,"context_line":"called \"unknown\" will be created, and all unofficial projects currently"},{"line_number":26,"context_line":"hosted in the OpenStack infrastructure will be re-located there. All official"},{"line_number":27,"context_line":"projects will remain in the \"openstack\" namespace."},{"line_number":28,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_97538c6b","line":25,"in_reply_to":"5fc1f717_c983dda8","updated":"2019-03-25 02:30:40.000000000","message":"I am also ok with the \u0027unknown\u0027 as this can get more attention for them to live under some namespace. Anyways most of them are abandon so calling them \u0027unknown\u0027 is not so bad :)","commit_id":"a968dcf2de284d0734d410d83d90818940710c34"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"e4ba29ffedc8ca04b05944f24ba0e9b3c903e962","unresolved":false,"context_lines":[{"line_number":24,"context_line":"repositories are moved to the new OpenDev infrastructure, a new namespace"},{"line_number":25,"context_line":"called \"unknown\" will be created, and all unofficial projects currently"},{"line_number":26,"context_line":"hosted in the OpenStack infrastructure will be re-located there. All official"},{"line_number":27,"context_line":"projects will remain in the \"openstack\" namespace."},{"line_number":28,"context_line":""},{"line_number":29,"context_line":"Unofficial projects moved to the \"unknown\" namespace are encouraged to find"},{"line_number":30,"context_line":"a home in an existing namespace other than \"openstack\", or to create a new"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_d486e4b9","line":27,"range":{"start_line":27,"start_character":28,"end_line":27,"end_character":39},"updated":"2019-03-25 11:42:33.000000000","message":"Again, keep it just as OpenStack - you\u0027re not insinuating that it\u0027s an openstack namespace, it *is* the OpenStack namespace.","commit_id":"a968dcf2de284d0734d410d83d90818940710c34"},{"author":{"_account_id":10343,"name":"Jim Rollenhagen","email":"jim@jimrollenhagen.com","username":"jimrollenhagen"},"change_message_id":"803eca5576a6cc3279e78a2f98735bae16066865","unresolved":false,"context_lines":[{"line_number":24,"context_line":"repositories are moved to the new OpenDev infrastructure, a new namespace"},{"line_number":25,"context_line":"called \"unknown\" will be created, and all unofficial projects currently"},{"line_number":26,"context_line":"hosted in the OpenStack infrastructure will be re-located there. All official"},{"line_number":27,"context_line":"projects will remain in the \"openstack\" namespace."},{"line_number":28,"context_line":""},{"line_number":29,"context_line":"Unofficial projects moved to the \"unknown\" namespace are encouraged to find"},{"line_number":30,"context_line":"a home in an existing namespace other than \"openstack\", or to create a new"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_415ca7ec","line":27,"updated":"2019-03-22 14:25:54.000000000","message":"Should we make a note like \"other than projects in openstack-dev\" or something here?","commit_id":"a968dcf2de284d0734d410d83d90818940710c34"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"90a15e231e18cf5f3020209c7bc210e89bc5d576","unresolved":false,"context_lines":[{"line_number":24,"context_line":"repositories are moved to the new OpenDev infrastructure, a new namespace"},{"line_number":25,"context_line":"called \"unknown\" will be created, and all unofficial projects currently"},{"line_number":26,"context_line":"hosted in the OpenStack infrastructure will be re-located there. All official"},{"line_number":27,"context_line":"projects will remain in the \"openstack\" namespace."},{"line_number":28,"context_line":""},{"line_number":29,"context_line":"Unofficial projects moved to the \"unknown\" namespace are encouraged to find"},{"line_number":30,"context_line":"a home in an existing namespace other than \"openstack\", or to create a new"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_17cd5c30","line":27,"in_reply_to":"5fc1f717_21139b68","updated":"2019-03-25 02:30:40.000000000","message":"yeah, we have most of the QA tooling under openstack-dev namespace. If we are going with option2 of ML thread[1]\n\nI will say merge them under openstack/ namespace only. also same with openstack-infra repos too. \n\n[1] http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003943.html\n\n+1 on adding the note for them as that will be namespace change for those repos","commit_id":"a968dcf2de284d0734d410d83d90818940710c34"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"f519398bb74100d010cfdec7877a2fa6fca50c56","unresolved":false,"context_lines":[{"line_number":24,"context_line":"repositories are moved to the new OpenDev infrastructure, a new namespace"},{"line_number":25,"context_line":"called \"unknown\" will be created, and all unofficial projects currently"},{"line_number":26,"context_line":"hosted in the OpenStack infrastructure will be re-located there. All official"},{"line_number":27,"context_line":"projects will remain in the \"openstack\" namespace."},{"line_number":28,"context_line":""},{"line_number":29,"context_line":"Unofficial projects moved to the \"unknown\" namespace are encouraged to find"},{"line_number":30,"context_line":"a home in an existing namespace other than \"openstack\", or to create a new"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_a1754bfc","line":27,"in_reply_to":"5fc1f717_415ca7ec","updated":"2019-03-22 14:38:53.000000000","message":"How many exceptions do we have? Can we make a list?","commit_id":"a968dcf2de284d0734d410d83d90818940710c34"},{"author":{"_account_id":10343,"name":"Jim Rollenhagen","email":"jim@jimrollenhagen.com","username":"jimrollenhagen"},"change_message_id":"30a96d0f368dbe426b00860cb2067153c78f7c14","unresolved":false,"context_lines":[{"line_number":24,"context_line":"repositories are moved to the new OpenDev infrastructure, a new namespace"},{"line_number":25,"context_line":"called \"unknown\" will be created, and all unofficial projects currently"},{"line_number":26,"context_line":"hosted in the OpenStack infrastructure will be re-located there. All official"},{"line_number":27,"context_line":"projects will remain in the \"openstack\" namespace."},{"line_number":28,"context_line":""},{"line_number":29,"context_line":"Unofficial projects moved to the \"unknown\" namespace are encouraged to find"},{"line_number":30,"context_line":"a home in an existing namespace other than \"openstack\", or to create a new"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_21139b68","line":27,"in_reply_to":"5fc1f717_a1754bfc","updated":"2019-03-22 14:48:37.000000000","message":"As far as I know, the list is http://git.openstack.org/cgit/?q\u003dopenstack-dev\n\nThough there may be projects in openstack-infra that we continue to own? I\u0027m not sure. http://git.openstack.org/cgit/?q\u003dopenstack-infra","commit_id":"a968dcf2de284d0734d410d83d90818940710c34"},{"author":{"_account_id":10343,"name":"Jim Rollenhagen","email":"jim@jimrollenhagen.com","username":"jimrollenhagen"},"change_message_id":"fac8794ab528d47d453455b88d9e62cc5fc0c292","unresolved":false,"context_lines":[{"line_number":24,"context_line":"repositories are moved to the new OpenDev infrastructure, a new namespace"},{"line_number":25,"context_line":"called \"unknown\" will be created, and all unofficial projects currently"},{"line_number":26,"context_line":"hosted in the OpenStack infrastructure will be re-located there. All official"},{"line_number":27,"context_line":"projects will remain in the \"openstack\" namespace."},{"line_number":28,"context_line":""},{"line_number":29,"context_line":"Unofficial projects moved to the \"unknown\" namespace are encouraged to find"},{"line_number":30,"context_line":"a home in an existing namespace other than \"openstack\", or to create a new"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_7a8b5767","line":27,"range":{"start_line":27,"start_character":28,"end_line":27,"end_character":39},"in_reply_to":"5fc1f717_d486e4b9","updated":"2019-03-25 12:41:31.000000000","message":"++ for moving openstack-dev/infra into openstack/\n\nAnd *the* OpenStack namespace is \"openstack\", does that make sense why it\u0027s quoted this way? It works either way, I guess.","commit_id":"a968dcf2de284d0734d410d83d90818940710c34"},{"author":{"_account_id":10343,"name":"Jim Rollenhagen","email":"jim@jimrollenhagen.com","username":"jimrollenhagen"},"change_message_id":"803eca5576a6cc3279e78a2f98735bae16066865","unresolved":false,"context_lines":[{"line_number":32,"context_line":""},{"line_number":33,"context_line":"New projects added to the OpenDev infrastructure should create their own"},{"line_number":34,"context_line":"namespace, or find an existing namespace to join that is not \"unknown\" or"},{"line_number":35,"context_line":"\"openstack\"."}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_e172737c","line":35,"updated":"2019-03-22 14:25:54.000000000","message":"OpenDev folks - are you okay with us declaring this, or should this be your decision / documented on your end?","commit_id":"a968dcf2de284d0734d410d83d90818940710c34"},{"author":{"_account_id":10343,"name":"Jim Rollenhagen","email":"jim@jimrollenhagen.com","username":"jimrollenhagen"},"change_message_id":"30a96d0f368dbe426b00860cb2067153c78f7c14","unresolved":false,"context_lines":[{"line_number":32,"context_line":""},{"line_number":33,"context_line":"New projects added to the OpenDev infrastructure should create their own"},{"line_number":34,"context_line":"namespace, or find an existing namespace to join that is not \"unknown\" or"},{"line_number":35,"context_line":"\"openstack\"."}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_49028d0b","line":35,"in_reply_to":"5fc1f717_01d53fb7","updated":"2019-03-22 14:48:37.000000000","message":"I think it\u0027s worth writing down what our suggestions are for the unofficial projects; I suspect some would come to us for guidance if we don\u0027t.","commit_id":"a968dcf2de284d0734d410d83d90818940710c34"},{"author":{"_account_id":10343,"name":"Jim Rollenhagen","email":"jim@jimrollenhagen.com","username":"jimrollenhagen"},"change_message_id":"8132bb08bef5d24908f5055e769d2ebb329aa8e0","unresolved":false,"context_lines":[{"line_number":32,"context_line":""},{"line_number":33,"context_line":"New projects added to the OpenDev infrastructure should create their own"},{"line_number":34,"context_line":"namespace, or find an existing namespace to join that is not \"unknown\" or"},{"line_number":35,"context_line":"\"openstack\"."}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_623dc58c","line":35,"in_reply_to":"5fc1f717_34640822","updated":"2019-03-26 19:27:42.000000000","message":"I\u0027m going to remove this.","commit_id":"a968dcf2de284d0734d410d83d90818940710c34"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"e4ba29ffedc8ca04b05944f24ba0e9b3c903e962","unresolved":false,"context_lines":[{"line_number":32,"context_line":""},{"line_number":33,"context_line":"New projects added to the OpenDev infrastructure should create their own"},{"line_number":34,"context_line":"namespace, or find an existing namespace to join that is not \"unknown\" or"},{"line_number":35,"context_line":"\"openstack\"."}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_34640822","line":35,"in_reply_to":"5fc1f717_49028d0b","updated":"2019-03-25 11:42:33.000000000","message":"I agree with both, but perhaps that should be a separate document (albiet, hopefully a small one) and this point to that. I see the need to have suggestions, as I agree that people will look to us for guidance, but we should be focusing on the rules we ant to apply for projects added to the namespaces in *this* doc.","commit_id":"a968dcf2de284d0734d410d83d90818940710c34"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"f519398bb74100d010cfdec7877a2fa6fca50c56","unresolved":false,"context_lines":[{"line_number":32,"context_line":""},{"line_number":33,"context_line":"New projects added to the OpenDev infrastructure should create their own"},{"line_number":34,"context_line":"namespace, or find an existing namespace to join that is not \"unknown\" or"},{"line_number":35,"context_line":"\"openstack\"."}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_01d53fb7","line":35,"in_reply_to":"5fc1f717_e172737c","updated":"2019-03-22 14:38:53.000000000","message":"Perhaps we should focus on the rules we want to apply for having projects added to the namespaces we own, and not worry about the other cases?","commit_id":"a968dcf2de284d0734d410d83d90818940710c34"}]}