On 08/11/16 13:04 +0000, Hayes, Graham wrote:
On 08/11/2016 10:30, Thierry Carrez wrote:That said, I think that if we can have more confidence that our structure can handle it (from infra to release/stable/dep management) and that the OpenStack community will share expertise and best practices on Go and avoid reinventing the wheel in every project, I expect a majority of TC members to take that leap of faith.There was a bit of work done for the previous proposal, but the main objections were not to do with any of points raised in this email / blog. The objections were mainly cultural - about how it would impact the community (which *is* very important), and the exactly why it was needed for the projects who were asking.
I think part of the community-wide concerns that were raised originated from the lack of an actual process for this evaluation to be done and the lack of up front work, which is something that I'm trying to address here. This is a new process and I think defining this expectations is the key to help with future proposals. I believe an early evaluation of the needs for a new language should still be part of the process, though. Likely at the very beginning of the process, before the up front work is even started. Flavio -- @flaper87 Flavio Percoco
signature.asc
Description: PGP signature
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
