Excerpts from Ben Nemec's message of 2015-02-27 09:25:37 -0800:
On 02/27/2015 03:54 AM, Thierry Carrez wrote:
Doug Hellmann wrote:
Maybe some of the folks in the meeting who felt more strongly that it
should be a separate document can respond with their thoughts?
I don't feel very
On 02/27/2015 03:54 AM, Thierry Carrez wrote:
Doug Hellmann wrote:
Maybe some of the folks in the meeting who felt more strongly that it
should be a separate document can respond with their thoughts?
I don't feel very strongly and could survive this landing in
openstack-specs. My objection
Doug Hellmann wrote:
Maybe some of the folks in the meeting who felt more strongly that it
should be a separate document can respond with their thoughts?
I don't feel very strongly and could survive this landing in
openstack-specs. My objection was the following:
- Specs are for designing the
On Wed, Feb 25, 2015 at 02:54:35PM -0500, Doug Hellmann wrote:
That leads to two questions, then:
1. Should we have a unified developer guide for the project?
Sounds like a great idea to me, I think we should.
2. Where should it live and how should we manage it?
I like Stefano's idea
So, I'm wondering how much of this is unnecessarily splitting hairs on
what defines a cross-project spec. If you look at the currently merged
specs, they are in fact both Guidelines:
http://specs.openstack.org/openstack/openstack-specs/
Would renaming mine Eventlet Guidelines make it more
On Thu, Feb 26, 2015, at 03:55 PM, Ben Nemec wrote:
So, I'm wondering how much of this is unnecessarily splitting hairs on
what defines a cross-project spec. If you look at the currently merged
specs, they are in fact both Guidelines:
http://specs.openstack.org/openstack/openstack-specs/
On Wed, 2015-02-25 at 14:54 -0500, Doug Hellmann wrote:
1. Should we have a unified developer guide for the project?
Yes. Absolutely. Yes.
2. Where should it live and how should we manage it?
I think the natural destination for it would be the URL
http://docs.openstack.org/developer (which
During yesterday’s cross-project meeting [1], we discussed the Eventlet Best
Practices” spec [2] started by bnemec. The discussion of that spec revolved
around the question of whether our cross-project specs repository is the right
place for this type of document that isn’t a “plan” for a
On Wed, Feb 25, 2015 at 11:54 AM, Doug Hellmann d...@doughellmann.com
wrote:
During yesterday’s cross-project meeting [1], we discussed the Eventlet
Best Practices” spec [2] started by bnemec. The discussion of that spec
revolved around the question of whether our cross-project specs
On Wed, Feb 25, 2015, at 03:14 PM, Joe Gordon wrote:
On Wed, Feb 25, 2015 at 11:54 AM, Doug Hellmann d...@doughellmann.com
wrote:
During yesterday’s cross-project meeting [1], we discussed the Eventlet
Best Practices” spec [2] started by bnemec. The discussion of that spec
revolved
On Wed, Feb 25, 2015 at 12:49 PM, Doug Hellmann d...@doughellmann.com
wrote:
On Wed, Feb 25, 2015, at 03:14 PM, Joe Gordon wrote:
On Wed, Feb 25, 2015 at 11:54 AM, Doug Hellmann d...@doughellmann.com
wrote:
During yesterday’s cross-project meeting [1], we discussed the
Eventlet
On 02/25/2015 02:54 PM, Doug Hellmann wrote:
During yesterday’s cross-project meeting [1], we discussed the Eventlet Best
Practices” spec [2] started by bnemec. The discussion of that spec revolved around
the question of whether our cross-project specs repository is the right place for
this
Sounds like a very good idea. Cross project development shared knowledge.
Miguel Ángel Ajo
On Wednesday, 25 de February de 2015 at 22:32, michael mccune wrote:
On 02/25/2015 02:54 PM, Doug Hellmann wrote:
During yesterday’s cross-project meeting [1], we discussed the Eventlet
Best
13 matches
Mail list logo
