)]}'
{"resolutions/20161128-driver-teams.rst":[{"author":{"_account_id":5263,"name":"Jeremy Stanley","display_name":"fungi","email":"fungi@yuggoth.org","username":"fungi","status":"missing, presumed fed"},"change_message_id":"13d8b82e2a4ecf30e4831e41671c23dd31d57272","unresolved":false,"context_lines":[{"line_number":14,"context_line":"and so following the same open principles as the rest of OpenStack,"},{"line_number":15,"context_line":"may qualify as \"official\" community activity and those responsible"},{"line_number":16,"context_line":"can be eligible for resources granted to teams within the \"Big"},{"line_number":17,"context_line":"Tent.\""}],"source_content_type":"text/x-rst","patch_set":1,"id":"ba5201f7_c8f8c54c","line":17,"updated":"2017-01-09 16:07:08.000000000","message":"Alternative wording suggestions are certainly welcome. The goal here was to encourage open/transparent and well-specified systems so that anyone _could_ write drivers for them without needing to be employed by their vendors or sign gnarly NDAs. Similar pressure from Linux and BSD kernel communities has helped reform the hardware industry in that regard over the years, and I have hopes we\u0027re perhaps well-placed to provide that sort of benefit to our community as well.","commit_id":"82250350f00034ef6a54f87d9adee1b8a610d57c"},{"author":{"_account_id":5263,"name":"Jeremy Stanley","display_name":"fungi","email":"fungi@yuggoth.org","username":"fungi","status":"missing, presumed fed"},"change_message_id":"51625038094544b285b1e1b1c542196f7781c614","unresolved":false,"context_lines":[{"line_number":14,"context_line":"and so following the same open principles as the rest of OpenStack,"},{"line_number":15,"context_line":"may qualify as \"official\" community activity and those responsible"},{"line_number":16,"context_line":"can be eligible for resources granted to teams within the \"Big"},{"line_number":17,"context_line":"Tent.\""}],"source_content_type":"text/x-rst","patch_set":1,"id":"3a461143_2eaa0a71","line":17,"updated":"2017-02-02 19:09:11.000000000","message":"I should probably also point out that the _specific_ resolution in this change is a reinforcement of our current status quo: approval here would be explicitly stating that we don\u0027t think there\u0027s anything \"different\" about driver development allowing it to be held to a separate set of standards from other projects under our governance. If the authors of a piece of software rely on exclusive access to unpublished specifications/standards for the hardware or protocols their software is written to support then that excludes effective contribution from others outside their closed circle and so disqualifies that effort from official participation in OpenStack\u0027s governance (whether or not the software in question is a \"driver\").","commit_id":"82250350f00034ef6a54f87d9adee1b8a610d57c"},{"author":{"_account_id":5263,"name":"Jeremy Stanley","display_name":"fungi","email":"fungi@yuggoth.org","username":"fungi","status":"missing, presumed fed"},"change_message_id":"cc66cc22e5adf3080be5d33cccab39ac66b6f9bb","unresolved":false,"context_lines":[{"line_number":14,"context_line":"and so following the same open principles as the rest of OpenStack,"},{"line_number":15,"context_line":"may qualify as \"official\" community activity and those responsible"},{"line_number":16,"context_line":"can be eligible for resources granted to teams within the \"Big"},{"line_number":17,"context_line":"Tent.\""}],"source_content_type":"text/x-rst","patch_set":1,"id":"3a461143_6eedf224","line":17,"updated":"2017-02-02 19:00:01.000000000","message":"I\u0027m speaking only on behalf of myself and not the rest of the TC here, but my understanding is that we already have officially recognized at least some (currently, though not necessarily so) single-vendor teams developing free software that only depends on other free software and commodity/standards-copmpliant hardware as part of OpenStack, and I don\u0027t see that the software in question being a \"driver\" changes the reasons for acceptability there. The push with the various alternative driver team proposals was to determine whether we can find a way to extend this possibility for inclusion to developers working on drivers for proprietary systems who would otherwise be excluded by our \"unfair advantage\" proscriptions.","commit_id":"82250350f00034ef6a54f87d9adee1b8a610d57c"},{"author":{"_account_id":1561,"name":"Russell Bryant","email":"rbryant@redhat.com","username":"russellb"},"change_message_id":"3cfed25381673b20a3bbfd6f27f0c10c975f89b5","unresolved":false,"context_lines":[{"line_number":14,"context_line":"and so following the same open principles as the rest of OpenStack,"},{"line_number":15,"context_line":"may qualify as \"official\" community activity and those responsible"},{"line_number":16,"context_line":"can be eligible for resources granted to teams within the \"Big"},{"line_number":17,"context_line":"Tent.\""}],"source_content_type":"text/x-rst","patch_set":1,"id":"ba5201f7_e6d69f26","line":17,"updated":"2017-01-09 14:29:28.000000000","message":"This seems to value drivers where a vendor *doesn\u0027t* participate vs ones that do.  Wouldn\u0027t we want to encourage vendor participation?  In cases that a vendor *does* participate, it would not be surprising for them to dominate the development.\n\nPerhaps it\u0027s just a wording issue here ...","commit_id":"82250350f00034ef6a54f87d9adee1b8a610d57c"},{"author":{"_account_id":5263,"name":"Jeremy Stanley","display_name":"fungi","email":"fungi@yuggoth.org","username":"fungi","status":"missing, presumed fed"},"change_message_id":"cf9d622e7d135d240b41b466eee542e4bea71a22","unresolved":false,"context_lines":[{"line_number":14,"context_line":"and so following the same open principles as the rest of OpenStack,"},{"line_number":15,"context_line":"may qualify as \"official\" community activity and those responsible"},{"line_number":16,"context_line":"can be eligible for resources granted to teams within the \"Big"},{"line_number":17,"context_line":"Tent.\""}],"source_content_type":"text/x-rst","patch_set":1,"id":"1a430d35_8341320e","line":17,"updated":"2017-02-03 18:28:41.000000000","message":"To be more precise the \"driver teams\" proposal could also be used by teams developing completely free/open drivers, however I think applying to be a usual and proper contributor team under the TC makes more sense for that case.","commit_id":"82250350f00034ef6a54f87d9adee1b8a610d57c"},{"author":{"_account_id":13734,"name":"Nell Jerram","email":"nell@tigera.io","username":"neiljerram"},"change_message_id":"efccaf46cdce1a167ed8fb2b9c5b2d3e35f89ca0","unresolved":false,"context_lines":[{"line_number":14,"context_line":"and so following the same open principles as the rest of OpenStack,"},{"line_number":15,"context_line":"may qualify as \"official\" community activity and those responsible"},{"line_number":16,"context_line":"can be eligible for resources granted to teams within the \"Big"},{"line_number":17,"context_line":"Tent.\""}],"source_content_type":"text/x-rst","patch_set":1,"id":"1a430d35_5172c27d","line":17,"in_reply_to":"3a461143_2eaa0a71","updated":"2017-02-03 11:31:22.000000000","message":"Thanks Jeremy.  I\u0027m afraid, though, that it is far from clear, in the alternative proposals, that this is all about drivers that have or rely on proprietary software or specifications.  You or others might like to get that clarified, especially in the proposal that looks best placed to win.\n\n(FYI, and to flesh out how this has confused *me*: I was drawn to this discussion because I have been reviewing the governance options for networking-calico.  networking-calico was part of the Neutron stadium but has recently been removed from that, so I was wondering whether (1) to continue as an unofficial OpenStack project, or (2) to apply for official project status, or (3) to consider the driver project status that may soon exist - and so I was reviewing these proposals in order to understand (3).\n\nUntil this exchange of comments here, I didn\u0027t realise that (3) was in fact for proprietary projects.  Now that I do realise that, I can eliminate it as an option for networking-calico because networking-calico is completely open.)","commit_id":"82250350f00034ef6a54f87d9adee1b8a610d57c"},{"author":{"_account_id":13734,"name":"Nell Jerram","email":"nell@tigera.io","username":"neiljerram"},"change_message_id":"0e7511c33188adfbbbf67fd0827ac87b84e4ce8a","unresolved":false,"context_lines":[{"line_number":14,"context_line":"and so following the same open principles as the rest of OpenStack,"},{"line_number":15,"context_line":"may qualify as \"official\" community activity and those responsible"},{"line_number":16,"context_line":"can be eligible for resources granted to teams within the \"Big"},{"line_number":17,"context_line":"Tent.\""}],"source_content_type":"text/x-rst","patch_set":1,"id":"3a461143_01f718f6","line":17,"in_reply_to":"ba5201f7_c8f8c54c","updated":"2017-02-01 15:22:28.000000000","message":"Hmm, is this whole debate about \u0027drivers for proprietary systems\u0027?\n\nThat wasn\u0027t clear to me, if so.  I thought it might be about drivers for fully open-source systems, but where the developers tend to come from a single vendor.","commit_id":"82250350f00034ef6a54f87d9adee1b8a610d57c"}]}
