<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Thanks, Flavio. You did a great job. Many thanks for all your hard
work to make those happen.<br>
<br>
<div class="moz-cite-prefix">On 11/09/15 23:51, Flavio Percoco
wrote:<br>
</div>
<blockquote cite="mid:20150911115103.GA8182@redhat.com" type="cite">Greetings,
<br>
<br>
I'm sending this email to announce that I wont be running for
Zaqar's
<br>
PTL position this cycle.
<br>
<br>
I've been Zaqar's PTL for two cycles and I believe it is time for
me
<br>
to move on. More importantly, I believe it's time for this great,
<br>
still small, project to be led by someone else. The reasons behind
<br>
this belief have nothing to do with neither the previous state of
the
<br>
project or even its current success story. If anything, my current
<br>
decision of not running has everything to do with the project's
<br>
current growth.
<br>
<br>
As many of you know, Zaqar (formerly known as Marconi) went
through
<br>
many ups and downs. From great discussions and growth attempts to
<br>
almost being shutdown[0]. This has taugh me a lot but more
<br>
importantly, it's made the team stronger and it's cleared the
team's
<br>
goals and path. And to prove that, let me share some of the
success
<br>
stories the team has had since Vancouver:
<br>
<br>
3 great milestones
<br>
==================
<br>
<br>
Let me start by sharing the progress the project has made
code-wise.
<br>
While it may not be the most important for many people, I believe
it's
<br>
extremly valuable for the project. The reason for this being that
<br>
every single member of this team is not a full-time Zaqar
developer.
<br>
That means, every single member of this team has a different
full-time
<br>
responsibility and every contribution made to the project has been
<br>
made in their spare working (or free) time. From amazing Outreachy
<br>
mentees (we've mentored participants of the Outrechy program since
<br>
cycle 1) to great contributors from other projects in OpenStack.
<br>
<br>
In milestone #1[1], we closed several bugs while we discussed the
<br>
features that we wanted to work on during Liberty. In milestone
#2[1],
<br>
some of the features we wanted to have in Liberty started to land
and
<br>
several bugs were fixed as well. In milestone #3, many bugs were
fixed
<br>
due to a heavy testing session. But it doesn't end there. In
RC1[4], 3
<br>
FFE were granted - not carelessly, FWIW - to complete all the work
<br>
we've planned for Liberty and, of course, more bug fixes.
<br>
<br>
We now even have a websocket example in the code base... ZOMG!
<br>
<br>
In addition to the above, the client library has kept moving
forward
<br>
and it's being aligned with the current, maintained, API. This
<br>
progress just makes me happy and happier. Keep reading and you'll
know
<br>
why.
<br>
<br>
Adoption by other projects
<br>
==========================
<br>
<br>
If you read the call for adoption thread[0], you probably know how
<br>
important that was for the project to move forward. After many
<br>
discussions in Vancouver, on IRC, conferences, mailing lists,
pigeons,
<br>
telegrams, etc. projects started to see[5] the different use-cases
for
<br>
Zaqar and we started talking about implementations and steps
forward.
<br>
One good example of this is Heat's use of Zaqar for
<br>
software-config[6], which was worked on and implemented.
<br>
<br>
Things didn't stop there on this front. Other projects, like
Sahara,
<br>
are also considering using Zaqar to communicate with guests
agents.
<br>
While this is under discussion on Sahara's side, the required
features
<br>
for it to happen and be more secure have been implemented in
Zaqar[7].
<br>
Other interesting discussions are also on-going that might help
with
<br>
Zaqar's adoption[8].
<br>
<br>
That said, I believe one of the works I'm most excited about right
now
<br>
is the puppet-zaqar project, which will make it simpler for
<br>
deployments based on puppet to, well, deploy zaqar[9].
<br>
<br>
Community Growth
<br>
================
<br>
<br>
None of the above would have been possible without a great
community
<br>
and especially without growing it. I'm not talking about the core
<br>
reviewers team growth - although we did have an addition[10] - but
the
<br>
growth of the community accross OpenStack. Folks from other teams
-
<br>
OpenStack Puppet, Sahara, Heat, Trove, cross-project efforts -
have
<br>
joined the efforts of pushing Zaqar forward in different ways
(like
<br>
the ones I've mentioned before).
<br>
<br>
Therefore, I owe a huge THANK YOU to each and one of these people
that
<br>
helped making this progress possible.
<br>
<br>
Oh God, please, stop talking
<br>
============================
<br>
<br>
Sure, fine! But before I do that, let me share why I've said all
the
<br>
above.
<br>
<br>
The above is not to show off what the team has accomplished. It's
<br>
definitely not to take any credits whatsoever. It's to show
exactly
<br>
why the team needs a new PTL.
<br>
<br>
I believe PTLs should rotate every 2 cycles (if not every cycle).
I've
<br>
been the PTL for 2 cycles (or probably even more) and it's time
for
<br>
the vision and efforts of other folks to jump in. It's time for
folks
<br>
with more OPs knowledge than me to help making Zaqar more
<br>
"maintainable". It's time for new technical issues to come up and
for
<br>
us as a community to work together on achieving those. More
<br>
cross-project collaboration, more APIs improvement, more user
stories
<br>
is what Zaqar needs right now and I believe there are very capable
<br>
folks in Zaqar's team that would be perfect for this task.
<br>
<br>
One thing I'd like the whole team to put some efforts on,
regardless
<br>
what technical decisions will be taken, is on increasing the
diversity
<br>
of the project. Zaqar is not as diverse[11] (company wise) as I'd
like
<br>
that worries me A LOT. Growth will, hopefully, bring more people
and
<br>
reaching out to other communities remain something important.
<br>
<br>
It's been an honor to serve as Zaqar's PTL and it'll be an honor
for
<br>
me to contribute to the next PTL's future plans and leads.
<br>
<br>
Sincerely,
<br>
Flavio
<br>
<br>
P.S: #openstack-zaqar remains the funiest channel ever, just
sayin'.
<br>
<br>
[0]
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/pipermail/openstack-dev/2015-April/061967.html">http://lists.openstack.org/pipermail/openstack-dev/2015-April/061967.html</a><br>
[1] <a class="moz-txt-link-freetext" href="https://launchpad.net/zaqar/+milestone/liberty-1">https://launchpad.net/zaqar/+milestone/liberty-1</a>
<br>
[2] <a class="moz-txt-link-freetext" href="https://launchpad.net/zaqar/+milestone/liberty-2">https://launchpad.net/zaqar/+milestone/liberty-2</a>
<br>
[3] <a class="moz-txt-link-freetext" href="https://launchpad.net/zaqar/+milestone/liberty-3">https://launchpad.net/zaqar/+milestone/liberty-3</a>
<br>
[4] <a class="moz-txt-link-freetext" href="https://launchpad.net/zaqar/+milestone/liberty-rc1">https://launchpad.net/zaqar/+milestone/liberty-rc1</a>
<br>
[5]
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/pipermail/openstack-dev/2015-May/064739.html">http://lists.openstack.org/pipermail/openstack-dev/2015-May/064739.html</a>
<br>
[6]
<a class="moz-txt-link-freetext" href="https://github.com/openstack/heat-specs/blob/master/specs/kilo/software-config-zaqar.rst">https://github.com/openstack/heat-specs/blob/master/specs/kilo/software-config-zaqar.rst</a><br>
[7]
<a class="moz-txt-link-freetext" href="http://specs.openstack.org/openstack/zaqar-specs/specs/liberty/pre-signed-url.html">http://specs.openstack.org/openstack/zaqar-specs/specs/liberty/pre-signed-url.html</a><br>
[8] <a class="moz-txt-link-freetext" href="https://review.openstack.org/#/c/185822/">https://review.openstack.org/#/c/185822/</a>
<br>
[9] <a class="moz-txt-link-freetext" href="https://github.com/openstack/puppet-zaqar">https://github.com/openstack/puppet-zaqar</a>
<br>
[10]
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/pipermail/openstack-dev/2015-August/072191.html">http://lists.openstack.org/pipermail/openstack-dev/2015-August/072191.html</a><br>
[11] <a class="moz-txt-link-freetext" href="http://stackalytics.com/?module=zaqar-group">http://stackalytics.com/?module=zaqar-group</a>
<br>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Cheers & Best regards,
Fei Long Wang (王飞龙)
--------------------------------------------------------------------------
Senior Cloud Software Engineer
Tel: +64-48032246
Email: <a class="moz-txt-link-abbreviated" href="mailto:flwang@catalyst.net.nz">flwang@catalyst.net.nz</a>
Catalyst IT Limited
Level 6, Catalyst House, 150 Willis Street, Wellington
-------------------------------------------------------------------------- </pre>
</body>
</html>