The static file format that we've held for a while fails to scale
at some point, as run out of ways to split data. This patch
converts it all into a YAML file.
Change-Id: I4264c663d82077940873e2d3a1564b4e232daa9e
I would like to nominate myself to serve as the chair of the TC
for the upcoming session.
First of all, I'd like to thank Doug for his service as the chair
for the past few periods of time. He has been instrumental in
helping our TC, provided a lot of leadership and guidance and
he was very instrumental in helping me understand this role by
helping him as vice-chair.
We have a lot to work on as a team and I would like to explore
more and new options to communicate more often and follow-up on
our projects within the TC. As time goes by, the role of the TC
to validate new projects seems to have decreased, and it seems
that the community would like a more "hands-on" involvement with
actionable 'artifacts' that come out of the TC.
That's not to say that we haven't built any of that over the past
few months, we've come up with a lot of very important documents
to help define a lot of things, but I'd like us to focus on working
with our teams to help push OpenStack with our community in the
best and most succcesful path possible.
We have a community of long term contirbutors that we trust to know
the best decision to take, however, there is still a lot of doubt
from our new-comers and perhaps a lot of questions on "how should
we deal with this?" -- as a technical committee, we need to be there
for our developers to help steer them in the best direction.
With the changes within the OSF, it's also more important than ever
to be aware of what is happening on the foundation level on how it
affects us, as well as working with other foundation-level projects
to find value that benefits all of us (which we already do, in the
case of Zuul).
Thank you for your consideration.
Change-Id: I92c867c7237295bc6fea731b656d5d2c69e01926
Mohammed has agreed to serve as vice chair again this term.
Change-Id: I1ba63b4e2f72ccfd9876f646212acae8479eb5b5
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
I would be happy to serve as chair this term to continue the work we
started last term.
Change-Id: Ic2caa463f3b08637f81e913ccc168512b14b8fb9
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
I have asked Mohammed to serve as vice chair, and he has agreed.
Change-Id: Ifdc2cf103330bb4539910975bcb725adb09af1c4
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Track each current TC member's E-mail address next to their name and
IRC nick in the members roster and include it in the rendering on
the governance site, to make them easier for community members to
figure out how to contact in private when needed. We've included TC
candidate contact E-mail addresses in the elections repository for
many cycles, but not recorded them in governance once elected. The
addresses themselves are far from secret and are already "published"
in our election results records, so there's little to be gained by
omitting them from governance.
Change-Id: If7c22f056d33e874b606c48d86d1e4236eae8a99
I would be honored to serve as chair for the TC for this session.
With Thierry stepping down as chair, this session will be the first
time the TC as it stands today is chaired by someone from outside of
the Foundation staff. This is an important step for us, to show not
only that our principle of Changes in Leadership are Good applies to
the TC, but that our leaders can and will place the needs of the
community first. Over the 6 years I have been contributing to
OpenStack and the 4+ years I have served on the TC, I have been
employed by 3 separate companies. I hope my history of service within
the community reassures everyone of my continued impartiality.
The nature of the TC and the issues it has had to address have changed
in significant ways several times while I have been involved.
When the TC addressed fundamental questions about what types of
projects should be included in the community, and OpenStack expanded
from a simple IaaS project to our current mission of producing the
ubiquitous Open Source Cloud Computing platform, I helped navigate
that change, first as a member of the Ceilometer team (one of the
first teams to be added to OpenStack without being spawned from an
existing project), and later as a TC member drafting early versions of
the Big Tent resolution.
When our community went through a period of intensive growth, as
companies joined and brought new features and formed new projects, I
helped organize the Oslo and release teams to cope with that growth by
implementing the liaison system and driving more use of automation.
More recently, as we have seen some leveling off, or even reduction,
of contributors, I worked with the documentation and requirements
teams to accommodate the contraction by shifting documentation from a
central location into team-owned repositories and by simplifying the
way we manage dependency settings in each project. These changes
reduced the friction for contributors to those projects.
Those experiences have prepared me to help us through this next
transition, as well.
My goals for this session are to have a smooth transition and to help
the TC work together as a team to achieve our shared objectives. I
have a few things I would like to change about the way we organize
ourselves based on patterns we have seen work well elsewhere,
including using sub-teams of TC members to manage our recurring
responsibilities more actively.
I look forward to talking with you about the future of the TC over the
next few weeks.
Change-Id: I35a4b1501b0019e79b34cc92f83af38ea4a41c26
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Given that Sean took over ReleaseManagement PTLship this cycle
I'm fine with continuing with the TC chair duties and producing
regular status reports for the TC.
If you are interested in taking over, please post a similar patch.
Change-Id: I1fc172a540a27a42fca0eea02282a1c9673f0b3f
Hi! Despite being away for the first meeting of the new
membership, I'd like to propose myself to continue chairing
the OpenStack Technical Committee in the coming 6 months.
We need to go through a number of significant changes, to
adapt OpenStack to the new challenges created by this
post-hype phase we are currently in. That will likely involve
an increase in the number of janitorial tasks which traditionally
fell on the Technical Committee chair. As part of my job at the
OpenStack Foundation, I'm able to continue dedicating substantial
time tracking efforts and pushing for their completion. I hope
you will trust me to help us all through those needed changes.
Note: Other candidates should propose alternate patches to this
one, and we can use Gerrit votes to select the winner.
Change-Id: I8b6464ca96f5c04e76794aee05edacaaf4404cfd
I'd like to nominate myself to be the chair of the
Technical Committee for yet one more round. Since Doug
is still holding the PTLship for release management,
I have extra time to dedicate to the Technical Committee,
which comes handy to navigate the complex issues we need
to tackle in the near future.
Change-Id: I4bd9db2153e2ccd4873554508399fd2a02be889e
The chair is responsible for making sure meetings are held
according to the rules described in our charter, and for
communicating the decisions taken during those meetings to the
Board of Directors and the OpenStack community at large.
If you'll have me, I'll be happy to serve again this cycle.
If you'd like to submit your own candidacy, please propose
an alternate patch. We'll vote on this at the next meeting.
Change-Id: I23f8953f510b2ec8bf4ab9def49891e2ebc2cc1e
The chair is responsible for making sure meetings are held
according to the rules described in our charter, and for
communicating the decisions taken during those meetings to the
Board of Directors and the OpenStack community at large.
Change-Id: I8cf96ee2928f99e3fea8ff4e8a66f26fc8bcd16c
I'll be happy to serve again as TC chair for this cycle, unless
someone really wants it (in which case, that person should file a
competing proposal like this one).
Change-Id: Iac3ac1180e1ba6faf0a5bf62beed1eee2b5ba6f1
Create initial repository structure and add the following
reference documents:
- charter: The authoritative copy of the TC charter (copied from wiki)
- members: Current TC members with election expiration
- programs.yaml: List of official programs including PTLs, codenames,
mission statements...
- extra-atcs: List of people being granted an ATC exception
Change-Id: Ia2df3bf0808af8cfa306092442160d5ecb14dfb0