)]}'
{"resolutions/20160503-add-go-programming-language.rst":[{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"806f310cf76c76b5e786ad350304c97610728001","unresolved":false,"context_lines":[{"line_number":18,"context_line":"Adding a new supported language comes with associated costs, namely"},{"line_number":19,"context_line":"the risk of a divided community. However the benefits demonstrated"},{"line_number":20,"context_line":"with Go so far mitigate the risks. Both the object storage and DNS"},{"line_number":21,"context_line":"projects have already explored implementing performance-sensitive"},{"line_number":22,"context_line":"parts of their projects in Go, and the initial results have been very"},{"line_number":23,"context_line":"exciting, showing significant improvements over the Python"},{"line_number":24,"context_line":"implementations."},{"line_number":25,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"dab17558_e26b79b7","line":22,"range":{"start_line":21,"start_character":44,"end_line":22,"end_character":5},"updated":"2016-05-16 13:19:44.000000000","message":"Should we explicitly state that we are not allowing two implementations of an OpenStack REST API? i.e. it is still assumed each project will be a single implementation of their REST APIs?","commit_id":"ac36f0daf16206a2876fb0986776605899195676"},{"author":{"_account_id":330,"name":"John Dickinson","email":"me@not.mn","username":"notmyname"},"change_message_id":"b88150065d0d5eb27285b8b53add4dbc71e7dbdf","unresolved":false,"context_lines":[{"line_number":18,"context_line":"Adding a new supported language comes with associated costs, namely"},{"line_number":19,"context_line":"the risk of a divided community. However the benefits demonstrated"},{"line_number":20,"context_line":"with Go so far mitigate the risks. Both the object storage and DNS"},{"line_number":21,"context_line":"projects have already explored implementing performance-sensitive"},{"line_number":22,"context_line":"parts of their projects in Go, and the initial results have been very"},{"line_number":23,"context_line":"exciting, showing significant improvements over the Python"},{"line_number":24,"context_line":"implementations."},{"line_number":25,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"dab17558_52004e34","line":22,"range":{"start_line":21,"start_character":44,"end_line":22,"end_character":5},"in_reply_to":"dab17558_e26b79b7","updated":"2016-05-16 15:30:33.000000000","message":"I\u0027ve added this to a paragraph below","commit_id":"ac36f0daf16206a2876fb0986776605899195676"},{"author":{"_account_id":6159,"name":"Flavio Percoco Premoli","display_name":"flaper87","email":"flavio.percoco@flyrlabs.com","username":"flaper87"},"change_message_id":"b5918338e680fb4a4de36714bc98fe8634e176ab","unresolved":false,"context_lines":[{"line_number":21,"context_line":"projects have already explored implementing performance-sensitive"},{"line_number":22,"context_line":"parts of their projects in Go, and the initial results have been very"},{"line_number":23,"context_line":"exciting, showing significant improvements over the Python"},{"line_number":24,"context_line":"implementations."},{"line_number":25,"context_line":""},{"line_number":26,"context_line":"Additionally, there is a degree of overlap between Python developers"},{"line_number":27,"context_line":"and Go developers (most obviously seen by the two existing Python"}],"source_content_type":"text/x-rst","patch_set":2,"id":"dab17558_489aba64","line":24,"updated":"2016-05-08 16:23:57.000000000","message":"How much of designate is written in Go? Is it just the API? or is the designate team looking to have a pure Go project?\n\nThe reason I\u0027m asking is because I\u0027d like us to have a better plan for new projects, pure Go projects, etc. For example, I kind of expect more and more projects going down the Go path as soon as it is added as a supported language. This has an impact on the community, the possibility of collaboration, etc.\n\nWould it be ok to have new projects that just support Go? What about common libraries and code? Is the Oslo team going to welcome go libraries as well?\n\nI\u0027m probably getting ahead of myself but I believe we\u0027ll face these issues in the future. \n\nI\u0027m not opposed to having Go as a supported language, fwiw.","commit_id":"ac36f0daf16206a2876fb0986776605899195676"},{"author":{"_account_id":8099,"name":"Graham Hayes","email":"gr@ham.ie","username":"graham"},"change_message_id":"f656c797bc4df148da76f2b90d14f8120c03ecb7","unresolved":false,"context_lines":[{"line_number":21,"context_line":"projects have already explored implementing performance-sensitive"},{"line_number":22,"context_line":"parts of their projects in Go, and the initial results have been very"},{"line_number":23,"context_line":"exciting, showing significant improvements over the Python"},{"line_number":24,"context_line":"implementations."},{"line_number":25,"context_line":""},{"line_number":26,"context_line":"Additionally, there is a degree of overlap between Python developers"},{"line_number":27,"context_line":"and Go developers (most obviously seen by the two existing Python"}],"source_content_type":"text/x-rst","patch_set":2,"id":"dab17558_343d03bc","line":24,"in_reply_to":"dab17558_489aba64","updated":"2016-05-09 12:00:37.000000000","message":"Currently none of Designate is written in Go - we have a POC of one of our data plane components written.\n\nWe want to replace our DNS server that was written in python with a Golang based one. We won\u0027t need any of the oslo libs for that currently, as it has no need for RMQ access, or API access.\n\nIt\u0027s entire job is send DNS zone transfers to the customer facing DNS servers, so it just reads from the DB sends the data.","commit_id":"ac36f0daf16206a2876fb0986776605899195676"},{"author":{"_account_id":330,"name":"John Dickinson","email":"me@not.mn","username":"notmyname"},"change_message_id":"4d630461e0017b3180c7f3137c0dfb0ca592f52f","unresolved":false,"context_lines":[{"line_number":21,"context_line":"projects have already explored implementing performance-sensitive"},{"line_number":22,"context_line":"parts of their projects in Go, and the initial results have been very"},{"line_number":23,"context_line":"exciting, showing significant improvements over the Python"},{"line_number":24,"context_line":"implementations."},{"line_number":25,"context_line":""},{"line_number":26,"context_line":"Additionally, there is a degree of overlap between Python developers"},{"line_number":27,"context_line":"and Go developers (most obviously seen by the two existing Python"}],"source_content_type":"text/x-rst","patch_set":2,"id":"dab17558_026fcf2b","line":24,"in_reply_to":"dab17558_489aba64","updated":"2016-05-09 18:02:11.000000000","message":"I\u0027d imagine that approving Go would result in Go-only projects. But I think your question has the answer in it too. If \"more and more projects [go] down the Go path\", then we\u0027ll have more and more devs who can work on common libraries, common standards, and better integration across all OpenStack projects.\n\nWe don\u0027t need to solve every question first. For example, while the question of \"where do common Golang libraries live\" is good, the reality is that we have exactly zero Golang libraries today, much less any that would be candidates for cross-project reuse. Just like with Oslo originally, when the time comes to have cross-project libraries, let\u0027s create them. Let\u0027s solve the problems we have today and find ways to collaborate as we go forward.","commit_id":"ac36f0daf16206a2876fb0986776605899195676"},{"author":{"_account_id":5638,"name":"Davanum Srinivas","email":"davanum@gmail.com","username":"dims-v"},"change_message_id":"0c77cfe42225969df733d3d1756c2424f380f229","unresolved":false,"context_lines":[{"line_number":31,"context_line":""},{"line_number":32,"context_line":"Like with existing languages, projects using Go languages should"},{"line_number":33,"context_line":"continue to collaborate where appropriate to share code in common"},{"line_number":34,"context_line":"libraries, use common style guidelines, and ensure that code is tested"},{"line_number":35,"context_line":"before landing."},{"line_number":36,"context_line":""},{"line_number":37,"context_line":"Further work is needed in the OpenStack community to determine the"}],"source_content_type":"text/x-rst","patch_set":2,"id":"dab17558_9d1cebc2","line":34,"updated":"2016-05-08 01:29:23.000000000","message":"We should add common documentation guidelines as well","commit_id":"ac36f0daf16206a2876fb0986776605899195676"},{"author":{"_account_id":330,"name":"John Dickinson","email":"me@not.mn","username":"notmyname"},"change_message_id":"4d630461e0017b3180c7f3137c0dfb0ca592f52f","unresolved":false,"context_lines":[{"line_number":31,"context_line":""},{"line_number":32,"context_line":"Like with existing languages, projects using Go languages should"},{"line_number":33,"context_line":"continue to collaborate where appropriate to share code in common"},{"line_number":34,"context_line":"libraries, use common style guidelines, and ensure that code is tested"},{"line_number":35,"context_line":"before landing."},{"line_number":36,"context_line":""},{"line_number":37,"context_line":"Further work is needed in the OpenStack community to determine the"}],"source_content_type":"text/x-rst","patch_set":2,"id":"dab17558_a2f7e3f3","line":34,"in_reply_to":"dab17558_5469a7bd","updated":"2016-05-09 18:02:11.000000000","message":"like \"...and ensure that code is tested and documented before landing.\"?","commit_id":"ac36f0daf16206a2876fb0986776605899195676"},{"author":{"_account_id":8099,"name":"Graham Hayes","email":"gr@ham.ie","username":"graham"},"change_message_id":"f656c797bc4df148da76f2b90d14f8120c03ecb7","unresolved":false,"context_lines":[{"line_number":31,"context_line":""},{"line_number":32,"context_line":"Like with existing languages, projects using Go languages should"},{"line_number":33,"context_line":"continue to collaborate where appropriate to share code in common"},{"line_number":34,"context_line":"libraries, use common style guidelines, and ensure that code is tested"},{"line_number":35,"context_line":"before landing."},{"line_number":36,"context_line":""},{"line_number":37,"context_line":"Further work is needed in the OpenStack community to determine the"}],"source_content_type":"text/x-rst","patch_set":2,"id":"dab17558_5469a7bd","line":34,"in_reply_to":"dab17558_9d1cebc2","updated":"2016-05-09 12:00:37.000000000","message":"Yeap  - I think with the 2 projects working on this we would be a good test case to write these as we move progress.","commit_id":"ac36f0daf16206a2876fb0986776605899195676"},{"author":{"_account_id":330,"name":"John Dickinson","email":"me@not.mn","username":"notmyname"},"change_message_id":"b88150065d0d5eb27285b8b53add4dbc71e7dbdf","unresolved":false,"context_lines":[{"line_number":31,"context_line":""},{"line_number":32,"context_line":"Like with existing languages, projects using Go languages should"},{"line_number":33,"context_line":"continue to collaborate where appropriate to share code in common"},{"line_number":34,"context_line":"libraries, use common style guidelines, and ensure that code is tested"},{"line_number":35,"context_line":"before landing."},{"line_number":36,"context_line":""},{"line_number":37,"context_line":"Further work is needed in the OpenStack community to determine the"}],"source_content_type":"text/x-rst","patch_set":2,"id":"dab17558_97174844","line":34,"in_reply_to":"dab17558_a2f7e3f3","updated":"2016-05-16 15:30:33.000000000","message":"Done","commit_id":"ac36f0daf16206a2876fb0986776605899195676"},{"author":{"_account_id":6159,"name":"Flavio Percoco Premoli","display_name":"flaper87","email":"flavio.percoco@flyrlabs.com","username":"flaper87"},"change_message_id":"b5918338e680fb4a4de36714bc98fe8634e176ab","unresolved":false,"context_lines":[{"line_number":36,"context_line":""},{"line_number":37,"context_line":"Further work is needed in the OpenStack community to determine the"},{"line_number":38,"context_line":"best way to manage dependencies, handle deployment artifacts, and"},{"line_number":39,"context_line":"ensure proper gate testing."}],"source_content_type":"text/x-rst","patch_set":2,"id":"dab17558_289db659","line":39,"updated":"2016-05-08 16:23:57.000000000","message":"Should we wait for the above to be figured out before we go ahead with this?","commit_id":"ac36f0daf16206a2876fb0986776605899195676"},{"author":{"_account_id":170,"name":"Mike Perez","email":"thingee@gmail.com","username":"thingee"},"change_message_id":"d2c0733a88265f87c7b235bbf454894a650e355e","unresolved":false,"context_lines":[{"line_number":36,"context_line":""},{"line_number":37,"context_line":"Further work is needed in the OpenStack community to determine the"},{"line_number":38,"context_line":"best way to manage dependencies, handle deployment artifacts, and"},{"line_number":39,"context_line":"ensure proper gate testing."}],"source_content_type":"text/x-rst","patch_set":2,"id":"dab17558_dc72c248","line":39,"in_reply_to":"dab17558_289db659","updated":"2016-05-09 23:51:26.000000000","message":"As with Flavio, I would like to see at a minimum some of the gate specific details figured out and what does infra think of those things it will need to support? How are the unit and functional tests ran? How is dependency management dealt with just for the initial test runners? This would be great for initial swift and designate teams to demonstrate collaboration on a language they are interested in pursuing.","commit_id":"ac36f0daf16206a2876fb0986776605899195676"},{"author":{"_account_id":8099,"name":"Graham Hayes","email":"gr@ham.ie","username":"graham"},"change_message_id":"f656c797bc4df148da76f2b90d14f8120c03ecb7","unresolved":false,"context_lines":[{"line_number":36,"context_line":""},{"line_number":37,"context_line":"Further work is needed in the OpenStack community to determine the"},{"line_number":38,"context_line":"best way to manage dependencies, handle deployment artifacts, and"},{"line_number":39,"context_line":"ensure proper gate testing."}],"source_content_type":"text/x-rst","patch_set":2,"id":"dab17558_349223a0","line":39,"in_reply_to":"dab17558_289db659","updated":"2016-05-09 12:00:37.000000000","message":"I suggested this on the mailing list - but was told it was better to change the policy first and then get the guidelines for this in place as swift and designate move forward with implementation.","commit_id":"ac36f0daf16206a2876fb0986776605899195676"},{"author":{"_account_id":6159,"name":"Flavio Percoco Premoli","display_name":"flaper87","email":"flavio.percoco@flyrlabs.com","username":"flaper87"},"change_message_id":"90370673b36e004fc1ef62349076b2fa0f6ad385","unresolved":false,"context_lines":[{"line_number":36,"context_line":""},{"line_number":37,"context_line":"Further work is needed in the OpenStack community to determine the"},{"line_number":38,"context_line":"best way to manage dependencies, handle deployment artifacts, and"},{"line_number":39,"context_line":"ensure proper gate testing."}],"source_content_type":"text/x-rst","patch_set":2,"id":"dab17558_ee50bf60","line":39,"in_reply_to":"dab17558_349223a0","updated":"2016-05-09 14:49:26.000000000","message":"I should have probably highlighted the section I\u0027m most interested in at this point which is the gate testing. I agree the rest could be figured out later but I feel like we should have, at least, a general idea of how the testing would work.","commit_id":"ac36f0daf16206a2876fb0986776605899195676"},{"author":{"_account_id":330,"name":"John Dickinson","email":"me@not.mn","username":"notmyname"},"change_message_id":"b88150065d0d5eb27285b8b53add4dbc71e7dbdf","unresolved":false,"context_lines":[{"line_number":36,"context_line":""},{"line_number":37,"context_line":"Further work is needed in the OpenStack community to determine the"},{"line_number":38,"context_line":"best way to manage dependencies, handle deployment artifacts, and"},{"line_number":39,"context_line":"ensure proper gate testing."}],"source_content_type":"text/x-rst","patch_set":2,"id":"dab17558_d787105f","line":39,"in_reply_to":"dab17558_425d2514","updated":"2016-05-16 15:30:33.000000000","message":"perhaps one experiment that could be interesting is to take the existing 3rd party CI tests that are in swift and run them in the openstack-infra environment (it\u0027s basically a `make test` script run from jenkins).","commit_id":"ac36f0daf16206a2876fb0986776605899195676"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"806f310cf76c76b5e786ad350304c97610728001","unresolved":false,"context_lines":[{"line_number":36,"context_line":""},{"line_number":37,"context_line":"Further work is needed in the OpenStack community to determine the"},{"line_number":38,"context_line":"best way to manage dependencies, handle deployment artifacts, and"},{"line_number":39,"context_line":"ensure proper gate testing."}],"source_content_type":"text/x-rst","patch_set":2,"id":"dab17558_425d2514","line":39,"in_reply_to":"dab17558_81d5c6ba","updated":"2016-05-16 13:19:44.000000000","message":"I think its right to try and resolve these horizontal team issues before we accept Go. It seems unlikely that it would be a big issue, but it would be good to see this a prototype for get tests and docs before we continue.","commit_id":"ac36f0daf16206a2876fb0986776605899195676"},{"author":{"_account_id":330,"name":"John Dickinson","email":"me@not.mn","username":"notmyname"},"change_message_id":"3398156c602ffe4965ef748234519cfcf901c395","unresolved":false,"context_lines":[{"line_number":36,"context_line":""},{"line_number":37,"context_line":"Further work is needed in the OpenStack community to determine the"},{"line_number":38,"context_line":"best way to manage dependencies, handle deployment artifacts, and"},{"line_number":39,"context_line":"ensure proper gate testing."}],"source_content_type":"text/x-rst","patch_set":2,"id":"dab17558_81d5c6ba","line":39,"in_reply_to":"dab17558_dc72c248","updated":"2016-05-12 17:40:55.000000000","message":"That topic was on the agenda at this week\u0027s -infra meeting[1] and there\u0027s now an etherpad tracking many of these questions.\n\n\n[1] http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-05-10-19.03.log.html\n\n[2] https://etherpad.openstack.org/p/golang-infra-issues-to-solve","commit_id":"ac36f0daf16206a2876fb0986776605899195676"},{"author":{"_account_id":12512,"name":"Deklan Dieterly","email":"deklan.dieterly@hpe.com","username":"deklan"},"change_message_id":"10cb2897792690b1eb45e420d92dbe730bf2265f","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"dab17558_5b42ef68","updated":"2016-05-17 14:21:41.000000000","message":"Substitute any major, generally accepted, statically typed language x for \"Go\" in this document and the argument is still valid. I see nothing specific to \"Go\" in this argument that makes it better than any other language x. In fact, there are many use cases where other languages are more appropriate than Go. Conversely, Go is a fine choice for many situations.\n\nThe real argument is whether projects, teams, and developers should be able to choose the appropriate language for the application under consideration. The counter argument to allowing choice is that the infrastructure must be able to support all the choices and this is admittedly a difficult proposition. Finding a way to balance these two concerns is the real issues.\n\nThis issue is only going to get more pressing as OpenStack matures. In order to develop fast, efficient, maintainable, large distributed systems, projects are going to need to use the best tools. Python has a low barrier to entry and is fast and fun. However, Python does not scale and perform as needed in many domains where OpenStack needs to go. Statically typed languages like Go and Java have proven themselves in the large, distributed systems arena where they dominate. There are certainly other languages that perform well too. As a community, we need to grow and mature in a pragmatic way and not rigidly follow dogma.","commit_id":"d28ac5f305ee8173caddbd7defad62da2411fe2f"},{"author":{"_account_id":12512,"name":"Deklan Dieterly","email":"deklan.dieterly@hpe.com","username":"deklan"},"change_message_id":"6f447800025d0c34a863c7f1f4cddae059d6c76d","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"dab17558_d22d1047","in_reply_to":"dab17558_063c7edf","updated":"2016-05-17 20:00:03.000000000","message":"Some particular things to notice in the OpenStack code base that cry out for using a statically typed language.\n\n1. Developers adding type checks in the code to simulate a statically typed language. \n\n2. Developers creating libraries that exist in statically typed language ecosystems already. I.e., reinventing the wheel with a new library where language x already has an industrial strength, bullet-proof implementation of that library.\n\n3. Developers being forced to use Python libraries to interface with components that are not written in Python. These Python libraries are usually poorly written and maintained.\n\n4. Developers writing Python lint-like utilities to make up for the lack of compiler support in Python that is found in statically typed languages.\n\nIf Go was accepted as an officially supported language in the OpenStack community, I\u0027d be the first to start to rewrite as much code as possible in Go.","commit_id":"d28ac5f305ee8173caddbd7defad62da2411fe2f"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"a13a33612e3924c27f09c1bf84bb190815dd2ced","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"dab17558_691e0960","in_reply_to":"dab17558_5b42ef68","updated":"2016-05-17 14:36:42.000000000","message":"I can see why you might want to open the door here and make this more generally about any language other than Python, but I feel we should focus this particular review on Golang. My gut says if we were to broaden this it would never pass. And it\u0027s unfair to the Swift and Designate folks to make this about something other than the tool they would like to use at this moment (and are already experimenting with).","commit_id":"d28ac5f305ee8173caddbd7defad62da2411fe2f"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"3565d276472c59fff5ee9db35802993468c79d95","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"dab17558_7e6a3cb4","in_reply_to":"dab17558_691e0960","updated":"2016-05-17 15:45:04.000000000","message":"Re: \"Python does not scale and perform as needed in many domains where OpenStack needs to go.\" -- could you expand on what are those domains you think \"OpenStack\" *needs* to go (and for which Python would not scale and perform as needed) ?","commit_id":"d28ac5f305ee8173caddbd7defad62da2411fe2f"},{"author":{"_account_id":12512,"name":"Deklan Dieterly","email":"deklan.dieterly@hpe.com","username":"deklan"},"change_message_id":"a600f12d626ec42068611f3747f4d1d3fd060ad9","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"dab17558_063c7edf","in_reply_to":"dab17558_7e6a3cb4","updated":"2016-05-17 18:53:50.000000000","message":"Big data and Datacenter OS are two examples that come quickly to mind. How about infrastructure management, orchestration, remediation, etc? Maybe machine learning? Anomaly detection? Container management? \n\nIn general OpenStack is providing an open-source software platform for cloud computing. This means scale, scale, and more scale. Performance, resource efficiency, correctness, extensibility, and maintainability are all important aspects of scale. Statically typed languages have a proven track record of handling these. What do Google, Amazon, Microsoft, Twitter, Yahoo, \u003cinsert major web-scale company here\u003e, etc use as implementation languages? \n\nIn addition, if we let theory be our guide, then statically typed languages are superior for developing large, distributed systems. Let the compiler catch the bugs before they land in production. Let the type system help you navigate and understand the code. \n\nOpenStack needs to evolve from a set of operator tools to a performant large, scale distributed system. Using the best tools for the job is the right thing to do.","commit_id":"d28ac5f305ee8173caddbd7defad62da2411fe2f"},{"author":{"_account_id":330,"name":"John Dickinson","email":"me@not.mn","username":"notmyname"},"change_message_id":"f4046d8b76a9983ef12b21baa8fb4186586e8a78","unresolved":false,"context_lines":[{"line_number":32,"context_line":"Like with existing languages, projects using Go languages should"},{"line_number":33,"context_line":"continue to collaborate where appropriate to share code in common"},{"line_number":34,"context_line":"libraries, use common style guidelines, and ensure that code is tested"},{"line_number":35,"context_line":"and documented before landing. We expect that each project using"},{"line_number":36,"context_line":"Golang will still have a single default and supported implementation"},{"line_number":37,"context_line":"of their respective end-user-facing API. This \"single API"},{"line_number":38,"context_line":"implementation\" expectation reinforces unity withing project"},{"line_number":39,"context_line":"communities and gives deployers and operators clear guidance of what"},{"line_number":40,"context_line":"to deploy where."}],"source_content_type":"text/x-rst","patch_set":3,"id":"dab17558_869c376b","line":37,"range":{"start_line":35,"start_character":31,"end_line":37,"end_character":40},"updated":"2016-05-16 15:34:47.000000000","message":"This comment is in response to John G\u0027s review on the previous patch set. I really like making this explicit, and I think it\u0027s a great addition.\n\nThe only thing I am trying to be careful about is to word it so that it\u0027s still possible for a project to transition from one language to another in their API service implementation. Obviously if that happens, there will be some sort of migration period where both implementations necessarily must exist at the same time. Thus my wording about \"expect\" and \"single default and supported\".","commit_id":"d28ac5f305ee8173caddbd7defad62da2411fe2f"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"41b28fcc51b43ecab88cfbba6de88e3ef90e7b95","unresolved":false,"context_lines":[{"line_number":35,"context_line":"and documented before landing. We expect that each project using"},{"line_number":36,"context_line":"Golang will still have a single default and supported implementation"},{"line_number":37,"context_line":"of their respective end-user-facing API. This \"single API"},{"line_number":38,"context_line":"implementation\" expectation reinforces unity withing project"},{"line_number":39,"context_line":"communities and gives deployers and operators clear guidance of what"},{"line_number":40,"context_line":"to deploy where."},{"line_number":41,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"dab17558_3a79ea93","line":38,"updated":"2016-05-17 13:19:41.000000000","message":"Nit: within","commit_id":"d28ac5f305ee8173caddbd7defad62da2411fe2f"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"41b28fcc51b43ecab88cfbba6de88e3ef90e7b95","unresolved":false,"context_lines":[{"line_number":39,"context_line":"communities and gives deployers and operators clear guidance of what"},{"line_number":40,"context_line":"to deploy where."},{"line_number":41,"context_line":""},{"line_number":42,"context_line":"Further work is needed in the OpenStack community to determine the"},{"line_number":43,"context_line":"best way to manage dependencies, handle deployment artifacts, and"},{"line_number":44,"context_line":"ensure proper gate testing as OpenStack projects begin to land Golang"},{"line_number":45,"context_line":"code into master."}],"source_content_type":"text/x-rst","patch_set":3,"id":"dab17558_9aa3b6ff","line":42,"updated":"2016-05-17 13:19:41.000000000","message":"I think it\u0027s fine to say we\u0027ll figure these bits out as we go rather than bikeshed upfront and try to come to consensus on them here on this review. If we\u0027re in agreement we want Golang in OpenStack, then to me lets make it happen and start solving these issues as a community.","commit_id":"d28ac5f305ee8173caddbd7defad62da2411fe2f"}]}