On 12/19/2013 12:10 AM, Mike Perez wrote:
On Tue, Dec 17, 2013 at 1:59 PM, Mike Perez thin...@gmail.com
mailto:thin...@gmail.com wrote:
snip
I reviewed the TC meeting notes, and my question still stands.
It seems the committee is touching on the point of there being a worry
because if
Excerpts from Sean Dague's message of 2013-12-19 04:14:51 -0800:
On 12/19/2013 12:10 AM, Mike Perez wrote:
On Tue, Dec 17, 2013 at 1:59 PM, Mike Perez thin...@gmail.com
mailto:thin...@gmail.com wrote:
snip
I reviewed the TC meeting notes, and my question still stands.
It seems the
On Thu, Dec 19, 2013 at 4:14 AM, Sean Dague s...@dague.net wrote:
On 12/19/2013 12:10 AM, Mike Perez wrote:
On Tue, Dec 17, 2013 at 1:59 PM, Mike Perez thin...@gmail.com
mailto:thin...@gmail.com wrote:
snip
I reviewed the TC meeting notes, and my question still stands.
It seems the
On Thu, Dec 12, 2013 at 4:48 PM, Morgan Fainberg m...@metacloud.com wrote:
On December 12, 2013 at 14:32:36, Dolph Mathews
(dolph.math...@gmail.com//dolph.math...@gmail.com)
wrote:
On Thu, Dec 12, 2013 at 2:58 PM, Adam Young ayo...@redhat.com wrote:
On 12/04/2013 08:58 AM, Jarret Raim
Bhandaru, Malini K wrote:
Barbican, key manager is essential to openstack, paves the way to greater
security.
Instead of rejecting the project because of its current existence owed so
heavily to Rackspace and to John Wood, why not we adopt it, code review,
contribute code etc. We can have
On 12/13/2013 03:50 AM, Thierry Carrez wrote:
Russell Bryant wrote:
$ git shortlog -s -e | sort -n -r
172 John Wood john.w...@rackspace.com
150 jfwood john.w...@rackspace.com
65 Douglas Mendizabal douglas.mendiza...@rackspace.com
39 Jarret Raim jarret.r...@rackspace.com
-Original Message-
From: Steven Dake [mailto:sd...@redhat.com]
In this particular case, I believe Barbican is not ready for incubation
because
of their dependence on celery, but ultimately I don't make the decision :)
We've landed the PR that removes celery and replaces it with
On 12/18/2013 10:23 AM, Jarret Raim wrote:
-Original Message-
From: Steven Dake [mailto:sd...@redhat.com]
In this particular case, I believe Barbican is not ready for incubation
because
of their dependence on celery, but ultimately I don't make the decision :)
We've landed the PR
On Tue, Dec 17, 2013 at 1:59 PM, Mike Perez thin...@gmail.com wrote:
On Tue, Dec 17, 2013 at 11:44 AM, Jarret Raim
jarret.r...@rackspace.comwrote:
On 12/13/13, 4:50 AM, Thierry Carrez thie...@openstack.org wrote:
If you remove Jenkins and attach Paul Kehrer, jqxin2006 (Michael Xin),
On 12/13/13, 7:56 AM, Russell Bryant rbry...@redhat.com wrote:
1) Are each of the items you mention big enough to have a sustainable
team that can exist as its own program?
The answer here for Barbican and Keystone is yes.
2) Would there be a benefit of *changing* the scope and mission of the
On 12/13/13, 4:50 AM, Thierry Carrez thie...@openstack.org wrote:
If you remove Jenkins and attach Paul Kehrer, jqxin2006 (Michael Xin),
Arash Ghoreyshi, Chad Lung and Steven Gonzales to Rackspace, then the
picture is:
67% of commits come from a single person (John Wood)
96% of commits come
On Tue, Dec 17, 2013 at 11:44 AM, Jarret Raim jarret.r...@rackspace.comwrote:
On 12/13/13, 4:50 AM, Thierry Carrez thie...@openstack.org wrote:
If you remove Jenkins and attach Paul Kehrer, jqxin2006 (Michael Xin),
Arash Ghoreyshi, Chad Lung and Steven Gonzales to Rackspace, then the
...@rackspace.com]
Sent: Tuesday, December 17, 2013 11:36 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] Incubation Request for Barbican
On 12/13/13, 7:56 AM, Russell Bryant rbry...@redhat.com wrote:
1) Are each of the items you mention big enough
-Original Message-
From: Jarret Raim [mailto:jarret.r...@rackspace.com]
Sent: Tuesday, December 17, 2013 11:44 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] Incubation Request for Barbican
On 12/13/13, 4:50 AM, Thierry Carrez thie
-Original Message-
From: Jarret Raim [mailto:jarret.r...@rackspace.com]
Sent: Tuesday, December 17, 2013 11:44 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] Incubation Request for Barbican
On 12/13/13, 4:50 AM, Thierry Carrez thie
Russell Bryant wrote:
$ git shortlog -s -e | sort -n -r
172John Wood john.w...@rackspace.com
150jfwood john.w...@rackspace.com
65Douglas Mendizabal douglas.mendiza...@rackspace.com
39Jarret Raim jarret.r...@rackspace.com
17Malini K.
$ git shortlog -s -e | sort -n -r
172 John Wood john.w...@rackspace.com
150 jfwood john.w...@rackspace.com
65 Douglas Mendizabal douglas.mendiza...@rackspace.com
39 Jarret Raim jarret.r...@rackspace.com
17 Malini K. Bhandaru malini.k.bhand...@intel.com
10 Paul Kehrer
From: Bryan D. Payne [mailto:bdpa...@acm.org]
Sent: 12 December 2013 16:12
To: OpenStack Development Mailing List (not for usage questions)
Cc: openstack...@lists.openstack.org; cloudkeep@googlegroups. com;
barbi...@lists.rackspace.com
Subject: Re: [openstack-dev] Incubation Request for Barbican
On 12/04/2013 08:58 AM, Jarret Raim wrote:
While I am all for adding a new program, I think we should only add one
if we
rule out all existing programs as a home. With that in mind why not add
this
to the keystone program? Perhaps that may require a tweak to keystones
mission
statement, but
On Thu, Dec 12, 2013 at 2:58 PM, Adam Young ayo...@redhat.com wrote:
On 12/04/2013 08:58 AM, Jarret Raim wrote:
While I am all for adding a new program, I think we should only add one
if we
rule out all existing programs as a home. With that in mind why not add
this
to the keystone
On December 12, 2013 at 14:32:36, Dolph Mathews (dolph.math...@gmail.com) wrote:
On Thu, Dec 12, 2013 at 2:58 PM, Adam Young ayo...@redhat.com wrote:
On 12/04/2013 08:58 AM, Jarret Raim wrote:
While I am all for adding a new program, I think we should only add one
if we
rule out all existing
I'd like to look at keeping things simple when they can be simple. I
need to understand why there¹s
already a key distribution service under keystone?
https://review.openstack.org/#/c/40692/18/openstack-identity-api/v3/src/ma
rkdown/identity-api-v3-os-kds-ext.md
I¹ve said before that I think
While I am all for adding a new program, I think we should only add one
if we
rule out all existing programs as a home. With that in mind why not add
this
to the keystone program? Perhaps that may require a tweak to keystones
mission
statement, but that is doable. I saw a partial answer
Jarret Raim wrote:
The TC is currently working on formalizing requirements for new programs
and projects [3]. I figured I would give them a try against this
application.
First, I'm assuming that the application is for a new program that
contains the new project. The application doesn't
With the introduction of programs (think: official teams), all
incubated/integrated projects must belong to an official program... So
when a project applies for incubation but is not part of an official
program yet, it de-facto also applies to be considered a program.
Ahh, understood. So I guess
On Dec 3, 2013 6:45 PM, Jarret Raim jarret.r...@rackspace.com wrote:
With the introduction of programs (think: official teams), all
incubated/integrated projects must belong to an official program... So
when a project applies for incubation but is not part of an official
program yet, it
All,
Barbican is the OpenStack key management service and we’d like to request
incubation for the Icehouse release. A Rackspace sponsored team has been
working for about 9 months now, including following the Havana release cycle
for our first release.
Our incubation request is here:
On 12/02/2013 10:19 AM, Jarret Raim wrote:
All,
Barbican is the OpenStack key management service and we’d like to
request incubation for the Icehouse release. A Rackspace sponsored team
has been working for about 9 months now, including following the Havana
release cycle for our first
On 12/02/2013 11:53 AM, Russell Bryant wrote:
** Project must have no library dependencies which effectively restrict how
the project may be distributed [1]
http://git.openstack.org/cgit/stackforge/barbican/tree/tools/pip-requires
It looks like the only item here not in the global
The TC is currently working on formalizing requirements for new programs
and projects [3]. I figured I would give them a try against this
application.
First, I'm assuming that the application is for a new program that
contains the new project. The application doesn't make that bit clear,
On 12/02/2013 04:12 PM, Jarret Raim wrote:
The TC is currently working on formalizing requirements for new programs
and projects [3]. I figured I would give them a try against this
application.
First, I'm assuming that the application is for a new program that
contains the new project.
Uses tox, but not pbr or global requirements
I added a ŒTasks¹ section for stuff we need to do from this review and
I¹ve added these tasks. [4]
[4] https://wiki.openstack.org/wiki/Barbican/Incubation
Awesome. Also, if you don't mind - we should add testr to that list.
We're looking at
32 matches
Mail list logo