Re: [openstack-dev] [glance] Glance Mitaka: Passing the torch

2016-03-14 Thread Kekane, Abhishek
Thanks for all your leadership, Flavio! Really appreciated all help from you!


Abhishek


-Original Message-
From: Flavio Percoco [mailto:fla...@redhat.com] 
Sent: 09 March 2016 19:45
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [glance] Glance Mitaka: Passing the torch


Greetings,

I'm not going to run for Glance's PTL position for the Newton timeframe.

There are many motivations behind this choice. Some of them I'm willing to 
discuss in private if people are interested but I'll go as far as saying there 
are personal and professional reasons for me to not run again.

As I've always done in my past cycles as PTL, I'd like to take some time to 
summarize what's happened in the past cycle not only for the new PTL to know 
what's coming up but for the community to know how things went.

Before I even start, I'd like to thank everyone in the Glance community. I 
truly believe this was a great cycle for the project and the community has 
gotten stronger. None of this would have been possible without the help of all 
of you and for that, I'm deeply in debt with you all. It does not just take an 
employer to get someone to contribute to a project. Being paid, for those who 
are, to do Open Source is not enough. It takes passion, motivation and a lot of 
patience to analyze a technology, think out of the box and look for ways it can 
be improved either by fixing bugs or by implementing new features. The amount 
of time and dedication this process requires is probably worth way more than 
what we get back from it.

Now, with all that being said, here's Glance Mitaka for all of you:

Completed Features
==

I think I've mentioned this already but I'm proud of it so I'll say it again.
The prioritization and scheduling of Glance Mitaka went so well that we managed 
to release M-3 without any feature freeze exception (FFE) request. This doesn't 
mean all the features were implemented. In fact, at least 4 were pushed back to 
Newton. However, the team communicated, reviewed, sprinted and coded in such a 
way that we were able to re-organize the schedule to avoid wasting time on 
things we new weren't going to make it. This required transparency and hard 
decisions but that's part of the job, right?

* [0] CIM Namespace Metadata
* [1] Support download from and upload to Cinder volumes
* [2] Glance db purge utility
* [3] Deprecate Glance v3 API
* [4] Implement trusts for Glance
* [5] Migrate the HTTP Store to Use Requests
* [6] Glance Image Signing and Verification
* [7] Supporting OVF Single Disk Image Upload
* [8] Prevention of Unauthorized errors during upload/download in Swift driver
* [9] Add filters using an ‘in’ operator

[0] 
http://specs.openstack.org/openstack/glance-specs/specs/mitaka/implemented/cim-namespace-metadata-definitions.html
[1] 
http://specs.openstack.org/openstack/glance-specs/specs/mitaka/implemented/cinder-store-upload-download.html
[2] 
http://specs.openstack.org/openstack/glance-specs/specs/mitaka/implemented/database-purge.html
[3] 
http://specs.openstack.org/openstack/glance-specs/specs/mitaka/implemented/deprecate-v3-api.html
[4] 
http://specs.openstack.org/openstack/glance-specs/specs/mitaka/implemented/glance-trusts.html
[5] 
http://specs.openstack.org/openstack/glance-specs/specs/mitaka/implemented/http-store-on-requests.html
[6] 
http://specs.openstack.org/openstack/glance-specs/specs/mitaka/implemented/image-signing-and-verification-support.html
[7] 
http://specs.openstack.org/openstack/glance-specs/specs/mitaka/implemented/ovf-lite.html
[8] 
http://specs.openstack.org/openstack/glance-specs/specs/mitaka/implemented/prevention-of-401-in-swift-driver.html
[9] 
http://specs.openstack.org/openstack/glance-specs/specs/mitaka/implemented/v2-add-filters-with-in-operator.html

If the above doesn't sound impressive to you, let me fill you in with some 
extra info about Glance's community.

Community
=

Glance's community currently has 12 core members, 3 of which joined during 
Mitaka and 2 of those 3 members joined at the end of the cycle. That means the 
team ran on 9 reviewers for most of the cycle except that out of those 9, 1 
left the team and joined later in the cycle and 3 folks weren't super active 
this cycle. That left the team with 5 constant reviewers throughout the cycle.

Now, the above is *NOT* to say that the success of the cycle is thanks to those
5 constant reviewers. On the contrary, it's to say that we've managed to build 
a community capable of working together with other non-core reviewers. This was 
a key thing for this cycle.

I don't think it's a secret to anyone that, at the beginning of the cycle, the 
community was fragile and somewhat split. There were different opinions on what 
Glance should (or shouldn't) look like, what new features Glance should (or
shouldn't) have and where the project should be headed in the next 6 months.

The team sat down, the team talked and the team agreed on what the project 
should

Re: [openstack-dev] [glance] Glance Mitaka: Passing the torch

2016-03-13 Thread Fei Long Wang

You've been fantastic.  Thanks for all you have done, Fla.


On 10/03/16 03:15, Flavio Percoco wrote:


Greetings,

I'm not going to run for Glance's PTL position for the Newton timeframe.

There are many motivations behind this choice. Some of them I'm 
willing to
discuss in private if people are interested but I'll go as far as 
saying there

are personal and professional reasons for me to not run again.

As I've always done in my past cycles as PTL, I'd like to take some 
time to
summarize what's happened in the past cycle not only for the new PTL 
to know

what's coming up but for the community to know how things went.

Before I even start, I'd like to thank everyone in the Glance 
community. I truly
believe this was a great cycle for the project and the community has 
gotten
stronger. None of this would have been possible without the help of 
all of you
and for that, I'm deeply in debt with you all. It does not just take 
an employer
to get someone to contribute to a project. Being paid, for those who 
are, to do
Open Source is not enough. It takes passion, motivation and a lot of 
patience to
analyze a technology, think out of the box and look for ways it can be 
improved
either by fixing bugs or by implementing new features. The amount of 
time and
dedication this process requires is probably worth way more than what 
we get

back from it.

Now, with all that being said, here's Glance Mitaka for all of you:

Completed Features
==

I think I've mentioned this already but I'm proud of it so I'll say it 
again.
The prioritization and scheduling of Glance Mitaka went so well that 
we managed
to release M-3 without any feature freeze exception (FFE) request. 
This doesn't
mean all the features were implemented. In fact, at least 4 were 
pushed back to
Newton. However, the team communicated, reviewed, sprinted and coded 
in such a
way that we were able to re-organize the schedule to avoid wasting 
time on
things we new weren't going to make it. This required transparency and 
hard

decisions but that's part of the job, right?

* [0] CIM Namespace Metadata
* [1] Support download from and upload to Cinder volumes
* [2] Glance db purge utility
* [3] Deprecate Glance v3 API
* [4] Implement trusts for Glance
* [5] Migrate the HTTP Store to Use Requests
* [6] Glance Image Signing and Verification
* [7] Supporting OVF Single Disk Image Upload
* [8] Prevention of Unauthorized errors during upload/download in 
Swift driver

* [9] Add filters using an ‘in’ operator

[0] 
http://specs.openstack.org/openstack/glance-specs/specs/mitaka/implemented/cim-namespace-metadata-definitions.html
[1] 
http://specs.openstack.org/openstack/glance-specs/specs/mitaka/implemented/cinder-store-upload-download.html
[2] 
http://specs.openstack.org/openstack/glance-specs/specs/mitaka/implemented/database-purge.html
[3] 
http://specs.openstack.org/openstack/glance-specs/specs/mitaka/implemented/deprecate-v3-api.html
[4] 
http://specs.openstack.org/openstack/glance-specs/specs/mitaka/implemented/glance-trusts.html
[5] 
http://specs.openstack.org/openstack/glance-specs/specs/mitaka/implemented/http-store-on-requests.html
[6] 
http://specs.openstack.org/openstack/glance-specs/specs/mitaka/implemented/image-signing-and-verification-support.html
[7] 
http://specs.openstack.org/openstack/glance-specs/specs/mitaka/implemented/ovf-lite.html
[8] 
http://specs.openstack.org/openstack/glance-specs/specs/mitaka/implemented/prevention-of-401-in-swift-driver.html
[9] 
http://specs.openstack.org/openstack/glance-specs/specs/mitaka/implemented/v2-add-filters-with-in-operator.html


If the above doesn't sound impressive to you, let me fill you in with 
some extra

info about Glance's community.

Community
=

Glance's community currently has 12 core members, 3 of which joined 
during
Mitaka and 2 of those 3 members joined at the end of the cycle. That 
means the
team ran on 9 reviewers for most of the cycle except that out of those 
9, 1 left
the team and joined later in the cycle and 3 folks weren't super 
active this

cycle. That left the team with 5 constant reviewers throughout the cycle.

Now, the above is *NOT* to say that the success of the cycle is thanks 
to those
5 constant reviewers. On the contrary, it's to say that we've managed 
to build a
community capable of working together with other non-core reviewers. 
This was a

key thing for this cycle.

I don't think it's a secret to anyone that, at the beginning of the 
cycle, the
community was fragile and somewhat split. There were different 
opinions on what
Glance should (or shouldn't) look like, what new features Glance 
should (or
shouldn't) have and where the project should be headed in the next 6 
months.


The team sat down, the team talked and the team agreed on what the 
project
should be and that's what the team did in the Mitaka cycle. Sharing 
one message

with the rest of the OpenStack community (and especially new Glance
contributors) was a key for the 

Re: [openstack-dev] [glance] Glance Mitaka: Passing the torch

2016-03-10 Thread Ronald Bradford
I am not involved in Glance, however this was well worth reading for the
experiences during the cycle, not just as a PTL but as a team and the
communication of improving the software development process.




On Wed, Mar 9, 2016 at 11:47 PM, Bhandaru, Malini K <
malini.k.bhand...@intel.com> wrote:

> Flavio, Glance and OpenStack benefited during your reign or period of
> humble service.
> Will miss you at the helm. Also thank you for anointing/attracting two new
> solid cores: Brian and Sabari
> Malini
>
>
> -Original Message-
> From: Tom Fifield [mailto:t...@openstack.org]
> Sent: Wednesday, March 09, 2016 7:55 PM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [glance] Glance Mitaka: Passing the torch
>
> A beautiful post, sir. Thank you for everything!
>
> On 09/03/16 22:15, Flavio Percoco wrote:
> >
> > Greetings,
> >
> > I'm not going to run for Glance's PTL position for the Newton timeframe.
> >
> > There are many motivations behind this choice. Some of them I'm
> > willing to discuss in private if people are interested but I'll go as
> > far as saying there are personal and professional reasons for me to
> > not run again.
> >
> > As I've always done in my past cycles as PTL, I'd like to take some
> > time to summarize what's happened in the past cycle not only for the
> > new PTL to know what's coming up but for the community to know how
> > things went.
> >
> > Before I even start, I'd like to thank everyone in the Glance community.
> > I truly
> > believe this was a great cycle for the project and the community has
> > gotten stronger. None of this would have been possible without the
> > help of all of you and for that, I'm deeply in debt with you all. It
> > does not just take an employer to get someone to contribute to a
> > project. Being paid, for those who are, to do Open Source is not
> > enough. It takes passion, motivation and a lot of patience to analyze
> > a technology, think out of the box and look for ways it can be
> > improved either by fixing bugs or by implementing new features. The
> > amount of time and dedication this process requires is probably worth
> > way more than what we get back from it.
> >
> > Now, with all that being said, here's Glance Mitaka for all of you:
> >
> > Completed Features
> > ==
> >
> > I think I've mentioned this already but I'm proud of it so I'll say it
> > again.
> > The prioritization and scheduling of Glance Mitaka went so well that
> > we managed to release M-3 without any feature freeze exception (FFE)
> > request. This doesn't mean all the features were implemented. In fact,
> > at least 4 were pushed back to Newton. However, the team communicated,
> > reviewed, sprinted and coded in such a way that we were able to
> > re-organize the schedule to avoid wasting time on things we new
> > weren't going to make it. This required transparency and hard
> > decisions but that's part of the job, right?
> >
> > * [0] CIM Namespace Metadata
> > * [1] Support download from and upload to Cinder volumes
> > * [2] Glance db purge utility
> > * [3] Deprecate Glance v3 API
> > * [4] Implement trusts for Glance
> > * [5] Migrate the HTTP Store to Use Requests
> > * [6] Glance Image Signing and Verification
> > * [7] Supporting OVF Single Disk Image Upload
> > * [8] Prevention of Unauthorized errors during upload/download in
> > Swift driver
> > * [9] Add filters using an ‘in’ operator
> >
> > [0]
> > http://specs.openstack.org/openstack/glance-specs/specs/mitaka/impleme
> > nted/cim-namespace-metadata-definitions.html
> >
> > [1]
> > http://specs.openstack.org/openstack/glance-specs/specs/mitaka/impleme
> > nted/cinder-store-upload-download.html
> >
> > [2]
> > http://specs.openstack.org/openstack/glance-specs/specs/mitaka/impleme
> > nted/database-purge.html
> >
> > [3]
> > http://specs.openstack.org/openstack/glance-specs/specs/mitaka/impleme
> > nted/deprecate-v3-api.html
> >
> > [4]
> > http://specs.openstack.org/openstack/glance-specs/specs/mitaka/impleme
> > nted/glance-trusts.html
> >
> > [5]
> > http://specs.openstack.org/openstack/glance-specs/specs/mitaka/impleme
> > nted/http-store-on-requests.html
> >
> > [6]
> > http://specs.openstack.org/openstack/glance-specs/specs/mitaka/impleme
> > nted/image-signing-and-verification-support.html
> >
> > [7]
> > http://specs.openstack.org/openstack/glance-specs/specs/mitaka/impleme
> > nted/ov

Re: [openstack-dev] [glance] Glance Mitaka: Passing the torch

2016-03-09 Thread Bhandaru, Malini K
Flavio, Glance and OpenStack benefited during your reign or period of humble 
service.
Will miss you at the helm. Also thank you for anointing/attracting two new 
solid cores: Brian and Sabari
Malini


-Original Message-
From: Tom Fifield [mailto:t...@openstack.org] 
Sent: Wednesday, March 09, 2016 7:55 PM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [glance] Glance Mitaka: Passing the torch

A beautiful post, sir. Thank you for everything!

On 09/03/16 22:15, Flavio Percoco wrote:
>
> Greetings,
>
> I'm not going to run for Glance's PTL position for the Newton timeframe.
>
> There are many motivations behind this choice. Some of them I'm 
> willing to discuss in private if people are interested but I'll go as 
> far as saying there are personal and professional reasons for me to 
> not run again.
>
> As I've always done in my past cycles as PTL, I'd like to take some 
> time to summarize what's happened in the past cycle not only for the 
> new PTL to know what's coming up but for the community to know how 
> things went.
>
> Before I even start, I'd like to thank everyone in the Glance community.
> I truly
> believe this was a great cycle for the project and the community has 
> gotten stronger. None of this would have been possible without the 
> help of all of you and for that, I'm deeply in debt with you all. It 
> does not just take an employer to get someone to contribute to a 
> project. Being paid, for those who are, to do Open Source is not 
> enough. It takes passion, motivation and a lot of patience to analyze 
> a technology, think out of the box and look for ways it can be 
> improved either by fixing bugs or by implementing new features. The 
> amount of time and dedication this process requires is probably worth 
> way more than what we get back from it.
>
> Now, with all that being said, here's Glance Mitaka for all of you:
>
> Completed Features
> ==
>
> I think I've mentioned this already but I'm proud of it so I'll say it 
> again.
> The prioritization and scheduling of Glance Mitaka went so well that 
> we managed to release M-3 without any feature freeze exception (FFE) 
> request. This doesn't mean all the features were implemented. In fact, 
> at least 4 were pushed back to Newton. However, the team communicated, 
> reviewed, sprinted and coded in such a way that we were able to 
> re-organize the schedule to avoid wasting time on things we new 
> weren't going to make it. This required transparency and hard 
> decisions but that's part of the job, right?
>
> * [0] CIM Namespace Metadata
> * [1] Support download from and upload to Cinder volumes
> * [2] Glance db purge utility
> * [3] Deprecate Glance v3 API
> * [4] Implement trusts for Glance
> * [5] Migrate the HTTP Store to Use Requests
> * [6] Glance Image Signing and Verification
> * [7] Supporting OVF Single Disk Image Upload
> * [8] Prevention of Unauthorized errors during upload/download in 
> Swift driver
> * [9] Add filters using an ‘in’ operator
>
> [0]
> http://specs.openstack.org/openstack/glance-specs/specs/mitaka/impleme
> nted/cim-namespace-metadata-definitions.html
>
> [1]
> http://specs.openstack.org/openstack/glance-specs/specs/mitaka/impleme
> nted/cinder-store-upload-download.html
>
> [2]
> http://specs.openstack.org/openstack/glance-specs/specs/mitaka/impleme
> nted/database-purge.html
>
> [3]
> http://specs.openstack.org/openstack/glance-specs/specs/mitaka/impleme
> nted/deprecate-v3-api.html
>
> [4]
> http://specs.openstack.org/openstack/glance-specs/specs/mitaka/impleme
> nted/glance-trusts.html
>
> [5]
> http://specs.openstack.org/openstack/glance-specs/specs/mitaka/impleme
> nted/http-store-on-requests.html
>
> [6]
> http://specs.openstack.org/openstack/glance-specs/specs/mitaka/impleme
> nted/image-signing-and-verification-support.html
>
> [7]
> http://specs.openstack.org/openstack/glance-specs/specs/mitaka/impleme
> nted/ovf-lite.html
>
> [8]
> http://specs.openstack.org/openstack/glance-specs/specs/mitaka/impleme
> nted/prevention-of-401-in-swift-driver.html
>
> [9]
> http://specs.openstack.org/openstack/glance-specs/specs/mitaka/impleme
> nted/v2-add-filters-with-in-operator.html
>
>
> If the above doesn't sound impressive to you, let me fill you in with 
> some extra info about Glance's community.
>
> Community
> =
>
> Glance's community currently has 12 core members, 3 of which joined 
> during Mitaka and 2 of those 3 members joined at the end of the cycle. 
> That means the team ran on 9 reviewers for most of the cycle except 
> that out of those 9, 1 left the team and joined later in the cycle and 
> 3 folks weren't s

Re: [openstack-dev] [glance] Glance Mitaka: Passing the torch

2016-03-09 Thread Tom Fifield

A beautiful post, sir. Thank you for everything!

On 09/03/16 22:15, Flavio Percoco wrote:


Greetings,

I'm not going to run for Glance's PTL position for the Newton timeframe.

There are many motivations behind this choice. Some of them I'm willing to
discuss in private if people are interested but I'll go as far as saying
there
are personal and professional reasons for me to not run again.

As I've always done in my past cycles as PTL, I'd like to take some time to
summarize what's happened in the past cycle not only for the new PTL to
know
what's coming up but for the community to know how things went.

Before I even start, I'd like to thank everyone in the Glance community.
I truly
believe this was a great cycle for the project and the community has gotten
stronger. None of this would have been possible without the help of all
of you
and for that, I'm deeply in debt with you all. It does not just take an
employer
to get someone to contribute to a project. Being paid, for those who
are, to do
Open Source is not enough. It takes passion, motivation and a lot of
patience to
analyze a technology, think out of the box and look for ways it can be
improved
either by fixing bugs or by implementing new features. The amount of
time and
dedication this process requires is probably worth way more than what we
get
back from it.

Now, with all that being said, here's Glance Mitaka for all of you:

Completed Features
==

I think I've mentioned this already but I'm proud of it so I'll say it
again.
The prioritization and scheduling of Glance Mitaka went so well that we
managed
to release M-3 without any feature freeze exception (FFE) request. This
doesn't
mean all the features were implemented. In fact, at least 4 were pushed
back to
Newton. However, the team communicated, reviewed, sprinted and coded in
such a
way that we were able to re-organize the schedule to avoid wasting time on
things we new weren't going to make it. This required transparency and hard
decisions but that's part of the job, right?

* [0] CIM Namespace Metadata
* [1] Support download from and upload to Cinder volumes
* [2] Glance db purge utility
* [3] Deprecate Glance v3 API
* [4] Implement trusts for Glance
* [5] Migrate the HTTP Store to Use Requests
* [6] Glance Image Signing and Verification
* [7] Supporting OVF Single Disk Image Upload
* [8] Prevention of Unauthorized errors during upload/download in Swift
driver
* [9] Add filters using an ‘in’ operator

[0]
http://specs.openstack.org/openstack/glance-specs/specs/mitaka/implemented/cim-namespace-metadata-definitions.html

[1]
http://specs.openstack.org/openstack/glance-specs/specs/mitaka/implemented/cinder-store-upload-download.html

[2]
http://specs.openstack.org/openstack/glance-specs/specs/mitaka/implemented/database-purge.html

[3]
http://specs.openstack.org/openstack/glance-specs/specs/mitaka/implemented/deprecate-v3-api.html

[4]
http://specs.openstack.org/openstack/glance-specs/specs/mitaka/implemented/glance-trusts.html

[5]
http://specs.openstack.org/openstack/glance-specs/specs/mitaka/implemented/http-store-on-requests.html

[6]
http://specs.openstack.org/openstack/glance-specs/specs/mitaka/implemented/image-signing-and-verification-support.html

[7]
http://specs.openstack.org/openstack/glance-specs/specs/mitaka/implemented/ovf-lite.html

[8]
http://specs.openstack.org/openstack/glance-specs/specs/mitaka/implemented/prevention-of-401-in-swift-driver.html

[9]
http://specs.openstack.org/openstack/glance-specs/specs/mitaka/implemented/v2-add-filters-with-in-operator.html


If the above doesn't sound impressive to you, let me fill you in with
some extra
info about Glance's community.

Community
=

Glance's community currently has 12 core members, 3 of which joined during
Mitaka and 2 of those 3 members joined at the end of the cycle. That
means the
team ran on 9 reviewers for most of the cycle except that out of those
9, 1 left
the team and joined later in the cycle and 3 folks weren't super active
this
cycle. That left the team with 5 constant reviewers throughout the cycle.

Now, the above is *NOT* to say that the success of the cycle is thanks
to those
5 constant reviewers. On the contrary, it's to say that we've managed to
build a
community capable of working together with other non-core reviewers.
This was a
key thing for this cycle.

I don't think it's a secret to anyone that, at the beginning of the
cycle, the
community was fragile and somewhat split. There were different opinions
on what
Glance should (or shouldn't) look like, what new features Glance should (or
shouldn't) have and where the project should be headed in the next 6
months.

The team sat down, the team talked and the team agreed on what the project
should be and that's what the team did in the Mitaka cycle. Sharing one
message
with the rest of the OpenStack community (and especially new Glance
contributors) was a key for the community to become stronger.

What changed? What did the 

[openstack-dev] [glance] Glance Mitaka: Passing the torch

2016-03-09 Thread Flavio Percoco


Greetings,

I'm not going to run for Glance's PTL position for the Newton timeframe.

There are many motivations behind this choice. Some of them I'm willing to
discuss in private if people are interested but I'll go as far as saying there
are personal and professional reasons for me to not run again.

As I've always done in my past cycles as PTL, I'd like to take some time to
summarize what's happened in the past cycle not only for the new PTL to know
what's coming up but for the community to know how things went.

Before I even start, I'd like to thank everyone in the Glance community. I truly
believe this was a great cycle for the project and the community has gotten
stronger. None of this would have been possible without the help of all of you
and for that, I'm deeply in debt with you all. It does not just take an employer
to get someone to contribute to a project. Being paid, for those who are, to do
Open Source is not enough. It takes passion, motivation and a lot of patience to
analyze a technology, think out of the box and look for ways it can be improved
either by fixing bugs or by implementing new features. The amount of time and
dedication this process requires is probably worth way more than what we get
back from it.

Now, with all that being said, here's Glance Mitaka for all of you:

Completed Features
==

I think I've mentioned this already but I'm proud of it so I'll say it again.
The prioritization and scheduling of Glance Mitaka went so well that we managed
to release M-3 without any feature freeze exception (FFE) request. This doesn't
mean all the features were implemented. In fact, at least 4 were pushed back to
Newton. However, the team communicated, reviewed, sprinted and coded in such a
way that we were able to re-organize the schedule to avoid wasting time on
things we new weren't going to make it. This required transparency and hard
decisions but that's part of the job, right?

* [0] CIM Namespace Metadata
* [1] Support download from and upload to Cinder volumes
* [2] Glance db purge utility
* [3] Deprecate Glance v3 API
* [4] Implement trusts for Glance
* [5] Migrate the HTTP Store to Use Requests
* [6] Glance Image Signing and Verification
* [7] Supporting OVF Single Disk Image Upload
* [8] Prevention of Unauthorized errors during upload/download in Swift driver
* [9] Add filters using an ‘in’ operator

[0] 
http://specs.openstack.org/openstack/glance-specs/specs/mitaka/implemented/cim-namespace-metadata-definitions.html
[1] 
http://specs.openstack.org/openstack/glance-specs/specs/mitaka/implemented/cinder-store-upload-download.html
[2] 
http://specs.openstack.org/openstack/glance-specs/specs/mitaka/implemented/database-purge.html
[3] 
http://specs.openstack.org/openstack/glance-specs/specs/mitaka/implemented/deprecate-v3-api.html
[4] 
http://specs.openstack.org/openstack/glance-specs/specs/mitaka/implemented/glance-trusts.html
[5] 
http://specs.openstack.org/openstack/glance-specs/specs/mitaka/implemented/http-store-on-requests.html
[6] 
http://specs.openstack.org/openstack/glance-specs/specs/mitaka/implemented/image-signing-and-verification-support.html
[7] 
http://specs.openstack.org/openstack/glance-specs/specs/mitaka/implemented/ovf-lite.html
[8] 
http://specs.openstack.org/openstack/glance-specs/specs/mitaka/implemented/prevention-of-401-in-swift-driver.html
[9] 
http://specs.openstack.org/openstack/glance-specs/specs/mitaka/implemented/v2-add-filters-with-in-operator.html

If the above doesn't sound impressive to you, let me fill you in with some extra
info about Glance's community.

Community
=

Glance's community currently has 12 core members, 3 of which joined during
Mitaka and 2 of those 3 members joined at the end of the cycle. That means the
team ran on 9 reviewers for most of the cycle except that out of those 9, 1 left
the team and joined later in the cycle and 3 folks weren't super active this
cycle. That left the team with 5 constant reviewers throughout the cycle.

Now, the above is *NOT* to say that the success of the cycle is thanks to those
5 constant reviewers. On the contrary, it's to say that we've managed to build a
community capable of working together with other non-core reviewers. This was a
key thing for this cycle.

I don't think it's a secret to anyone that, at the beginning of the cycle, the
community was fragile and somewhat split. There were different opinions on what
Glance should (or shouldn't) look like, what new features Glance should (or
shouldn't) have and where the project should be headed in the next 6 months.

The team sat down, the team talked and the team agreed on what the project
should be and that's what the team did in the Mitaka cycle. Sharing one message
with the rest of the OpenStack community (and especially new Glance
contributors) was a key for the community to become stronger.

What changed? What did the community do differently?

Priorities and Goals


Mitaka was the first