On 10 June 2014 17:53, Mark McLoughlin mar...@redhat.com wrote:
On Tue, 2014-06-10 at 16:09 +0100, Duncan Thomas wrote:
On 10 June 2014 15:07, Mark McLoughlin mar...@redhat.com wrote:
Exposing which configurations are actively tested is a perfectly sane
thing to do. I don't see why you
On Wed, Jun 11, 2014 at 10:21 AM, Doug Hellmann doug.hellm...@dreamhost.com
wrote:
On Wed, Jun 11, 2014 at 6:29 AM, Thierry Carrez thie...@openstack.org
wrote:
Mark McLoughlin wrote:
On Tue, 2014-06-10 at 16:09 +0100, Duncan Thomas wrote:
On 10 June 2014 15:07, Mark McLoughlin
Mark McLoughlin wrote:
On Tue, 2014-06-10 at 16:09 +0100, Duncan Thomas wrote:
On 10 June 2014 15:07, Mark McLoughlin mar...@redhat.com wrote:
Exposing which configurations are actively tested is a perfectly sane
thing to do. I don't see why you think calling this certification is
necessary
On Wed, Jun 11, 2014 at 6:29 AM, Thierry Carrez thie...@openstack.org wrote:
Mark McLoughlin wrote:
On Tue, 2014-06-10 at 16:09 +0100, Duncan Thomas wrote:
On 10 June 2014 15:07, Mark McLoughlin mar...@redhat.com wrote:
Exposing which configurations are actively tested is a perfectly sane
On Mon, 2014-06-09 at 20:14 -0400, Doug Hellmann wrote:
On Mon, Jun 9, 2014 at 6:11 PM, Eoghan Glynn egl...@redhat.com wrote:
Based on the discussion I'd like to propose these options:
1. Cinder-certified driver - This is an attempt to move the certification
to the project level.
2.
On 10 June 2014 09:33, Mark McLoughlin mar...@redhat.com wrote:
Avoiding dragging the project into those sort of politics is something
I'm really keen on, and why I think the word certification is best
avoided so we can focus on what we're actually trying to achieve.
Avoiding those sorts of
On 06/10/2014 04:33 AM, Mark McLoughlin wrote:
On Mon, 2014-06-09 at 20:14 -0400, Doug Hellmann wrote:
On Mon, Jun 9, 2014 at 6:11 PM, Eoghan Glynn egl...@redhat.com wrote:
Based on the discussion I'd like to propose these options:
1. Cinder-certified driver - This is an attempt to move the
On Tue, 2014-06-10 at 14:06 +0100, Duncan Thomas wrote:
On 10 June 2014 09:33, Mark McLoughlin mar...@redhat.com wrote:
Avoiding dragging the project into those sort of politics is something
I'm really keen on, and why I think the word certification is best
avoided so we can focus on what
On 10 June 2014 15:07, Mark McLoughlin mar...@redhat.com wrote:
Exposing which configurations are actively tested is a perfectly sane
thing to do. I don't see why you think calling this certification is
necessary to achieve your goals.
What is certification except a formal way of saying 'we
On 06/10/2014 10:09 AM, Duncan Thomas wrote:
On 10 June 2014 15:07, Mark McLoughlin mar...@redhat.com wrote:
Exposing which configurations are actively tested is a perfectly sane
thing to do. I don't see why you think calling this certification is
necessary to achieve your goals.
What is
On Tue, 2014-06-10 at 16:09 +0100, Duncan Thomas wrote:
On 10 June 2014 15:07, Mark McLoughlin mar...@redhat.com wrote:
Exposing which configurations are actively tested is a perfectly sane
thing to do. I don't see why you think calling this certification is
necessary to achieve your
So there are certain words that mean certain things, most don't, some do.
If words that mean certain things are used then some folks start using
the word and have expectations around the word and the OpenStack
Technical Committee and other OpenStack programs find themselves on the
hook
On 6 June 2014 18:29, Anita Kuno ante...@anteaya.info wrote:
So there are certain words that mean certain things, most don't, some do.
If words that mean certain things are used then some folks start using
the word and have expectations around the word and the OpenStack
Technical Committee
On 06/09/2014 03:38 AM, Eoghan Glynn wrote:
So there are certain words that mean certain things, most don't, some do.
If words that mean certain things are used then some folks start using
the word and have expectations around the word and the OpenStack
Technical Committee and other
of Vendor-specific
Drivers.
Ramy
-Original Message-
From: Duncan Thomas [mailto:duncan.tho...@gmail.com]
Sent: Monday, June 09, 2014 4:50 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] use of the word certified
On 6 June 2014 18:29, Anita Kuno
of the
certification.
Cheers,
Eoghan
Ramy
-Original Message-
From: Duncan Thomas [mailto:duncan.tho...@gmail.com]
Sent: Monday, June 09, 2014 4:50 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] use of the word certified
On 6 June 2014 18
Thomas [mailto:duncan.tho...@gmail.com]
Sent: Monday, June 09, 2014 4:50 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] use of the word certified
On 6 June 2014 18:29, Anita Kuno ante...@anteaya.info wrote:
So there are certain words that mean
On Fri, 2014-06-06 at 13:29 -0400, Anita Kuno wrote:
The issue I have with the word certify is that it requires someone or a
group of someones to attest to something. The thing attested to is only
as credible as the someone or the group of someones doing the attesting.
We have no process, nor
On Fri, Jun 6, 2014 at 1:29 PM, Anita Kuno ante...@anteaya.info wrote:
So there are certain words that mean certain things, most don't, some do.
If words that mean certain things are used then some folks start using
the word and have expectations around the word and the OpenStack
Technical
19 matches
Mail list logo
