)]}'
{"resolutions/20150901-programming-languages.rst":[{"author":{"_account_id":5623,"name":"David Lyle","email":"dklyle0@gmail.com","username":"david-lyle"},"change_message_id":"fefcce382f4c904c6c06c624a98af4e8dae73215","unresolved":false,"context_lines":[{"line_number":21,"context_line":""},{"line_number":22,"context_line":"Furthermore, every added language creates a de-facto new silo inside our"},{"line_number":23,"context_line":"community: those people that are able (or willing) to touch that language."},{"line_number":24,"context_line":"People in that silo are less likely to work on other OpenStack projects, need"},{"line_number":25,"context_line":"more attention to converge to common culture, and are less likely to help with"},{"line_number":26,"context_line":"cross-project efforts. As a community today, we don\u0027t need anything that"},{"line_number":27,"context_line":"creates more silos, we need more people caring about OpenStack as a whole,"}],"source_content_type":"text/x-rst","patch_set":1,"id":"da20952f_40498930","line":24,"updated":"2015-08-27 14:49:15.000000000","message":"the need clause is unclear.\n\nmaybe\n\"have increased difficulty converging to a common culture\"","commit_id":"a5b76f04d01d461e94f7147d759022c83210fe69"},{"author":{"_account_id":6316,"name":"Anita Kuno","email":"anteaya@anteaya.info","username":"anteaya"},"change_message_id":"cdda3ae5ff4b45bb464754661e005ae6a7acdcb5","unresolved":false,"context_lines":[{"line_number":33,"context_line":"the technical benefits of supporting the new language against the community"},{"line_number":34,"context_line":"costs of supporting it. In particular, we should refrain from adding a"},{"line_number":35,"context_line":"language purely for convenience, when one of the already-supported languages"},{"line_number":36,"context_line":"could totally address the same problem space. Short-term experimentations"},{"line_number":37,"context_line":"in feature branches are fine, as is legacy code on its way to complete"},{"line_number":38,"context_line":"removal. But long-term investments in a new language should first be vet by"},{"line_number":39,"context_line":"the Technical Committee. Given how difficult it is to reverse such a decision,"}],"source_content_type":"text/x-rst","patch_set":1,"id":"da20952f_eff43888","line":36,"updated":"2015-08-27 21:06:29.000000000","message":"I would remove \"totally\" here, it doesn\u0027t add to the meaning of \"address\" and sounds like an exclamation rather than adding clarity.","commit_id":"a5b76f04d01d461e94f7147d759022c83210fe69"},{"author":{"_account_id":5623,"name":"David Lyle","email":"dklyle0@gmail.com","username":"david-lyle"},"change_message_id":"fefcce382f4c904c6c06c624a98af4e8dae73215","unresolved":false,"context_lines":[{"line_number":35,"context_line":"language purely for convenience, when one of the already-supported languages"},{"line_number":36,"context_line":"could totally address the same problem space. Short-term experimentations"},{"line_number":37,"context_line":"in feature branches are fine, as is legacy code on its way to complete"},{"line_number":38,"context_line":"removal. But long-term investments in a new language should first be vet by"},{"line_number":39,"context_line":"the Technical Committee. Given how difficult it is to reverse such a decision,"},{"line_number":40,"context_line":"language addition motions will require a two-thirds majority (like TC charter"},{"line_number":41,"context_line":"changes)."}],"source_content_type":"text/x-rst","patch_set":1,"id":"da20952f_2526e7ce","line":38,"updated":"2015-08-27 14:49:15.000000000","message":"s/vet/vetted/","commit_id":"a5b76f04d01d461e94f7147d759022c83210fe69"},{"author":{"_account_id":10980,"name":"Doug Wiegley","email":"dougwig@parkside.io","username":"dougw"},"change_message_id":"39056327bf18647bd198f2ed9f753a7fed2be878","unresolved":false,"context_lines":[{"line_number":29,"context_line":"that line *very* carefully."},{"line_number":30,"context_line":""},{"line_number":31,"context_line":"As a result, the OpenStack Technical Committee will consider supporting"},{"line_number":32,"context_line":"additional languages to OpenStack on a case-by-case basis, carefully weighing"},{"line_number":33,"context_line":"the technical benefits of supporting the new language against the community"},{"line_number":34,"context_line":"costs of supporting it. In particular, we should refrain from adding a"},{"line_number":35,"context_line":"language purely for convenience, when one of the already-supported languages"}],"source_content_type":"text/x-rst","patch_set":3,"id":"da20952f_e9a9c17c","line":32,"updated":"2015-09-02 03:22:08.000000000","message":"I think it\u0027d be useful to break this down a little bit, like:\n\n- \"standard\" openstack projects that are a rest server plus glue to a backend should be python + pecan, and exceptions must go through the TC.  (And such an edict would open the door to an oslo framework, which might punt repeating all the same server and security bugs in every new project.)\n\n- new pure backends should be in a language chosen by the project team in question.  (e.g. swift and go)\n\n- infra related stuff should be xxx.\n\nCurrently approved exceptions are: yyy, zzz.\n\nThe point being that not all projects are the same, and thus don\u0027t benefit the community in the same way by using the same paradigms. But the stuff that is similar, which is the vast majority of rest server/glue, benefits more from consistency than the cost of reduced innovation.","commit_id":"e0f12c56370d229279e86263184025573bc7e3f2"},{"author":{"_account_id":964,"name":"Anne Gentle","email":"annegentle@justwriteclick.com","username":"annegentle"},"change_message_id":"462b56511fc72711ec9948a0f691a3e142c4bc12","unresolved":false,"context_lines":[{"line_number":10,"context_line":"Python was either suboptimal (system scripts) or not available (in-browser"},{"line_number":11,"context_line":"execution). We should *not* limit OpenStack to these three programming"},{"line_number":12,"context_line":"languages in the future, as it would either mean using suboptimal tools,"},{"line_number":13,"context_line":"not being able to address specific problem spaces, or artificially excluding"},{"line_number":14,"context_line":"specific project teams."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"At the same time, we recognize that supporting more programming languages"}],"source_content_type":"text/x-rst","patch_set":4,"id":"da20952f_769a8070","line":13,"updated":"2015-09-08 16:25:08.000000000","message":"I\u0027d still like clarity, perhaps here, about whether this only applies to service projects? \n\nIf I make a deployment project that uses Ruby that\u0027s already fine, correct?","commit_id":"f7c46b7d57eedac74ccd4d9327500108108d075f"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"6f8ea0c072624b28ba71f0971a4e16461134b98c","unresolved":false,"context_lines":[{"line_number":10,"context_line":"Python was either suboptimal (system scripts) or not available (in-browser"},{"line_number":11,"context_line":"execution). We should *not* limit OpenStack to these three programming"},{"line_number":12,"context_line":"languages in the future, as it would either mean using suboptimal tools,"},{"line_number":13,"context_line":"not being able to address specific problem spaces, or artificially excluding"},{"line_number":14,"context_line":"specific project teams."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"At the same time, we recognize that supporting more programming languages"}],"source_content_type":"text/x-rst","patch_set":4,"id":"ba15a1d1_25eda78b","line":13,"in_reply_to":"da20952f_769a8070","updated":"2015-09-14 11:50:21.000000000","message":"Added","commit_id":"f7c46b7d57eedac74ccd4d9327500108108d075f"},{"author":{"_account_id":2750,"name":"Sean Dague","email":"sean@dague.net","username":"sdague"},"change_message_id":"161ff3595ba89318ef132782add3e46cbff4dff8","unresolved":false,"context_lines":[{"line_number":11,"context_line":"execution). We should *not* limit OpenStack to these three programming"},{"line_number":12,"context_line":"languages in the future, as it would either mean using suboptimal tools,"},{"line_number":13,"context_line":"not being able to address specific problem spaces, or artificially excluding"},{"line_number":14,"context_line":"specific project teams."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"At the same time, we recognize that supporting more programming languages"},{"line_number":17,"context_line":"comes with a community cost. Every added language needs to be properly"}],"source_content_type":"text/x-rst","patch_set":4,"id":"da20952f_d559f95c","line":14,"updated":"2015-09-08 20:56:31.000000000","message":"while this paragraph does eventually answer the question, we should probably have a clear statement above this paragraph that is:\n\nThe currently supported languages in OpenStack are: bash, javascript, python","commit_id":"f7c46b7d57eedac74ccd4d9327500108108d075f"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"6f8ea0c072624b28ba71f0971a4e16461134b98c","unresolved":false,"context_lines":[{"line_number":11,"context_line":"execution). We should *not* limit OpenStack to these three programming"},{"line_number":12,"context_line":"languages in the future, as it would either mean using suboptimal tools,"},{"line_number":13,"context_line":"not being able to address specific problem spaces, or artificially excluding"},{"line_number":14,"context_line":"specific project teams."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"At the same time, we recognize that supporting more programming languages"},{"line_number":17,"context_line":"comes with a community cost. Every added language needs to be properly"}],"source_content_type":"text/x-rst","patch_set":4,"id":"ba15a1d1_c502ab3e","line":14,"in_reply_to":"da20952f_d559f95c","updated":"2015-09-14 11:50:21.000000000","message":"Added","commit_id":"f7c46b7d57eedac74ccd4d9327500108108d075f"},{"author":{"_account_id":2750,"name":"Sean Dague","email":"sean@dague.net","username":"sdague"},"change_message_id":"161ff3595ba89318ef132782add3e46cbff4dff8","unresolved":false,"context_lines":[{"line_number":20,"context_line":"already struggle keeping up with the current set of languages (JavaScript"},{"line_number":21,"context_line":"is still not totally supported by those). Every added language also further"},{"line_number":22,"context_line":"fragments our community, and requires extra care to converge to our common"},{"line_number":23,"context_line":"culture, which defines \"are you OpenStack\" in the context of the big tent."},{"line_number":24,"context_line":""},{"line_number":25,"context_line":"As a result, the OpenStack Technical Committee will consider supporting"},{"line_number":26,"context_line":"additional languages to OpenStack on a case-by-case basis, carefully weighing"}],"source_content_type":"text/x-rst","patch_set":4,"id":"da20952f_b53244f1","line":23,"updated":"2015-09-08 20:56:31.000000000","message":"I\u0027d personally be much happier with: groups are welcome to bring forward new languages to OpenStack, but will be expected to bear the burden of creating and supporting these cross project infrastructure efforts for a new language environment.","commit_id":"f7c46b7d57eedac74ccd4d9327500108108d075f"},{"author":{"_account_id":964,"name":"Anne Gentle","email":"annegentle@justwriteclick.com","username":"annegentle"},"change_message_id":"462b56511fc72711ec9948a0f691a3e142c4bc12","unresolved":false,"context_lines":[{"line_number":26,"context_line":"additional languages to OpenStack on a case-by-case basis, carefully weighing"},{"line_number":27,"context_line":"the technical benefits of supporting the new language against the community"},{"line_number":28,"context_line":"costs of supporting it."},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"There are a number of exceptions to the rule. Short-term experimentations"},{"line_number":31,"context_line":"in feature branches are fine, as is temporary legacy code on its way to"},{"line_number":32,"context_line":"complete removal. Downstream packaging (or infra configuration files) will"}],"source_content_type":"text/x-rst","patch_set":4,"id":"da20952f_56f09c91","line":29,"updated":"2015-09-08 16:25:08.000000000","message":"This sentence is a bit off to me, \"will consider supporting additional languages to OpenStack\"\nHow about:\nBecause we recognize these considerations, the OpenStack Technical Committee will allow additional language support in OpenStack projects (services only?) on a case-by-case basis, carefully weighing the technical benefits of supporting the new language against the community costs of supporting it.\"","commit_id":"f7c46b7d57eedac74ccd4d9327500108108d075f"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"6f8ea0c072624b28ba71f0971a4e16461134b98c","unresolved":false,"context_lines":[{"line_number":26,"context_line":"additional languages to OpenStack on a case-by-case basis, carefully weighing"},{"line_number":27,"context_line":"the technical benefits of supporting the new language against the community"},{"line_number":28,"context_line":"costs of supporting it."},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"There are a number of exceptions to the rule. Short-term experimentations"},{"line_number":31,"context_line":"in feature branches are fine, as is temporary legacy code on its way to"},{"line_number":32,"context_line":"complete removal. Downstream packaging (or infra configuration files) will"}],"source_content_type":"text/x-rst","patch_set":4,"id":"ba15a1d1_45953be2","line":29,"in_reply_to":"da20952f_56f09c91","updated":"2015-09-14 11:50:21.000000000","message":"Next patchset uses your wording","commit_id":"f7c46b7d57eedac74ccd4d9327500108108d075f"},{"author":{"_account_id":2750,"name":"Sean Dague","email":"sean@dague.net","username":"sdague"},"change_message_id":"161ff3595ba89318ef132782add3e46cbff4dff8","unresolved":false,"context_lines":[{"line_number":27,"context_line":"the technical benefits of supporting the new language against the community"},{"line_number":28,"context_line":"costs of supporting it."},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"There are a number of exceptions to the rule. Short-term experimentations"},{"line_number":31,"context_line":"in feature branches are fine, as is temporary legacy code on its way to"},{"line_number":32,"context_line":"complete removal. Downstream packaging (or infra configuration files) will"},{"line_number":33,"context_line":"obviously use the tools of their particular trade, like Puppet recipes in"}],"source_content_type":"text/x-rst","patch_set":4,"id":"da20952f_d52019b3","line":30,"updated":"2015-09-08 20:56:31.000000000","message":"the exceptions should be called out explicitly, otherwise people are going to believe they fit in some other rule, but not realize they are off in an exception branch.","commit_id":"f7c46b7d57eedac74ccd4d9327500108108d075f"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"6f8ea0c072624b28ba71f0971a4e16461134b98c","unresolved":false,"context_lines":[{"line_number":27,"context_line":"the technical benefits of supporting the new language against the community"},{"line_number":28,"context_line":"costs of supporting it."},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"There are a number of exceptions to the rule. Short-term experimentations"},{"line_number":31,"context_line":"in feature branches are fine, as is temporary legacy code on its way to"},{"line_number":32,"context_line":"complete removal. Downstream packaging (or infra configuration files) will"},{"line_number":33,"context_line":"obviously use the tools of their particular trade, like Puppet recipes in"}],"source_content_type":"text/x-rst","patch_set":4,"id":"ba15a1d1_25a4c755","line":30,"in_reply_to":"da20952f_d52019b3","updated":"2015-09-14 11:50:21.000000000","message":"Next patchset enumerates exceptions more clearly","commit_id":"f7c46b7d57eedac74ccd4d9327500108108d075f"},{"author":{"_account_id":2243,"name":"John Griffith","email":"john.griffith8@gmail.com","username":"john-griffith"},"change_message_id":"ccb81186c6a2939db097013f80796dcbff6379eb","unresolved":false,"context_lines":[{"line_number":32,"context_line":"complete removal. Downstream packaging (or infra configuration files) will"},{"line_number":33,"context_line":"obviously use the tools of their particular trade, like Puppet recipes in"},{"line_number":34,"context_line":"Ruby. Language bindings and SDKs (if any) would also obviously be coded in the"},{"line_number":35,"context_line":"corresponding languages. Let\u0027s use common sense: this resolution applies to"},{"line_number":36,"context_line":"common OpenStack services and libraries which are our main deliverables."}],"source_content_type":"text/x-rst","patch_set":4,"id":"da20952f_d9388af0","line":35,"updated":"2015-09-07 14:43:57.000000000","message":"\"Let\u0027s use common sense:\"\n\nYES, let\u0027s !!!","commit_id":"f7c46b7d57eedac74ccd4d9327500108108d075f"},{"author":{"_account_id":964,"name":"Anne Gentle","email":"annegentle@justwriteclick.com","username":"annegentle"},"change_message_id":"462b56511fc72711ec9948a0f691a3e142c4bc12","unresolved":false,"context_lines":[{"line_number":32,"context_line":"complete removal. Downstream packaging (or infra configuration files) will"},{"line_number":33,"context_line":"obviously use the tools of their particular trade, like Puppet recipes in"},{"line_number":34,"context_line":"Ruby. Language bindings and SDKs (if any) would also obviously be coded in the"},{"line_number":35,"context_line":"corresponding languages. Let\u0027s use common sense: this resolution applies to"},{"line_number":36,"context_line":"common OpenStack services and libraries which are our main deliverables."}],"source_content_type":"text/x-rst","patch_set":4,"id":"da20952f_b621f8fe","line":35,"updated":"2015-09-08 16:25:08.000000000","message":"I would also like clarifying language around whether we want SDKs that use cloud resources to submit to OpenStack governance. I\u0027m not sure of the cost/benefit ratio working well for SDKs. What are the costs/benefits for both sides (SDK maintenance team and our governance work)? Let\u0027s discuss at the next TC meeting.","commit_id":"f7c46b7d57eedac74ccd4d9327500108108d075f"},{"author":{"_account_id":964,"name":"Anne Gentle","email":"annegentle@justwriteclick.com","username":"annegentle"},"change_message_id":"52fef1e8f2f3c16580a1e16bef72e8c93f7e2c3e","unresolved":false,"context_lines":[{"line_number":32,"context_line":"complete removal. Downstream packaging (or infra configuration files) will"},{"line_number":33,"context_line":"obviously use the tools of their particular trade, like Puppet recipes in"},{"line_number":34,"context_line":"Ruby. Language bindings and SDKs (if any) would also obviously be coded in the"},{"line_number":35,"context_line":"corresponding languages. Let\u0027s use common sense: this resolution applies to"},{"line_number":36,"context_line":"common OpenStack services and libraries which are our main deliverables."}],"source_content_type":"text/x-rst","patch_set":4,"id":"ba15a1d1_f60be37b","line":35,"in_reply_to":"da20952f_64d3a160","updated":"2015-09-14 12:56:05.000000000","message":"Doug, this line of thinking is actually keeping SDK contributors away due to the level of effort implied by this thinking. There\u0027s not enough motivation and the cost out-weighs the benefits. I can dig into further examples if you like but what our team sees is PR/GitHub workflow so far shows more contributions in non-Python language SDKs.","commit_id":"f7c46b7d57eedac74ccd4d9327500108108d075f"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"d940e82b0cb1624283fcf4169e37a38d0c78f42d","unresolved":false,"context_lines":[{"line_number":32,"context_line":"complete removal. Downstream packaging (or infra configuration files) will"},{"line_number":33,"context_line":"obviously use the tools of their particular trade, like Puppet recipes in"},{"line_number":34,"context_line":"Ruby. Language bindings and SDKs (if any) would also obviously be coded in the"},{"line_number":35,"context_line":"corresponding languages. Let\u0027s use common sense: this resolution applies to"},{"line_number":36,"context_line":"common OpenStack services and libraries which are our main deliverables."}],"source_content_type":"text/x-rst","patch_set":4,"id":"da20952f_64d3a160","line":35,"in_reply_to":"da20952f_b621f8fe","updated":"2015-09-08 19:17:42.000000000","message":"I think we do want SDK projects to seek official status, but I also think we would want them to contribute to making the language used work in CI, with docs, etc.","commit_id":"f7c46b7d57eedac74ccd4d9327500108108d075f"},{"author":{"_account_id":964,"name":"Anne Gentle","email":"annegentle@justwriteclick.com","username":"annegentle"},"change_message_id":"7be495e755beca6c03075a3afbd07bfce3caca96","unresolved":false,"context_lines":[{"line_number":41,"context_line":"* downstream language SDKs, which obviously are implemented in the local idiom"},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"The general idea is that this resolution applies to upstream OpenStack"},{"line_number":44,"context_line":"services and libraries which are our main deliverables, not to downstream"},{"line_number":45,"context_line":"integration projects or development infrastructure. The Technical Committee"},{"line_number":46,"context_line":"will use common sense when considering those requests on a case-by-case basis."}],"source_content_type":"text/x-rst","patch_set":5,"id":"ba15a1d1_96d8671f","line":44,"updated":"2015-09-14 12:55:29.000000000","message":"Thierry, I think the language of recognizing exceptions above, along with the \"services and libraries\" line here, is what I was seeking. Thanks.","commit_id":"48ae706431afff34b89b3339bf80873e11adc1ee"}]}
