On 3 May 2016, at 12:19, Monty Taylor wrote:
On 05/03/2016 01:45 PM, Michael Krotscheck wrote:
On Tue, May 3, 2016 at 9:03 AM John Dickinson <email@example.com
As a starting point, what would you like to see addressed in the
document I'm drafting?
the things I've had to address:
- Common language formatting rules (ensure that a pep8-like thing exists).
- Mirroring dependencies?
- Building Documentation
Mirroring and building are the ones that we'll definitely want to work together on in terms of figuring out how to support. go get being able to point at any git repo for depends is neat - but it increases the amount of internet surface-area in the gate. Last time I looked (last year) there were options for doing just the fetch part of go get separate from the build part.
Are these the sort of things that need to be in a resolution saying that it's ok to write code in Golang? I'll definitely agree that these questions are important, and I don't have the answers yet (although I expect we will by the time any Golang code lands in Swift). We've already got the Consistent Testing Interface doc which talks about having tests, a coding style, and docs (amongst other things). Does a resolution about Golang being acceptable need to describe dependency management, build tooling, and CI?
OpenStack Development Mailing List (not for usage questions)