settingsLogin | Registersettings

[openstack-dev] [tc][election] Question for the candidates

0 votes

In the past year or so, has there been anything that made you think “I wish the TC would do something about that!” ? If so, what was it, and what would you have wanted the TC to do about it?

-- Ed Leafe


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
asked Oct 13, 2017 in openstack-dev by Ed_Leafe (11,720 points)   1 3 6

27 Responses

0 votes

By being involved in training activities and on-boarding new contributors to our community I would like to join to Emilien on his point.

I think we have a great, open and welcoming community already, but we still have many areas to improve. Teaching the new community members the processes and tools is essential and also the easier part.

The difficulty starts when they start to actively contribute to a project and they need to understand the mission, scope, architecture and dynamics of it to become a team member longer term and take on responsibilities. With smaller projects it is usually easier, while the more complex projects can be challenging both for the new team members and the core team.

With smaller groups we get back to a discussion periodically about encouraging the teams to do more mentoring and also about mentoring the mentors as we have a few experienced people and teams with good examples already. In my view the TC can help with putting emphasis on encouraging this mentality and direction besides looking into metrics.

Thanks and Best Regards,
Ildikó
(IRC: ildikov)

On 2017. Oct 12., at 23:22, Emilien Macchi emilien@redhat.com wrote:

On Thu, Oct 12, 2017 at 11:38 AM, Ed Leafe ed@leafe.com wrote:

In the past year or so, has there been anything that made you think “I wish the TC would do something about that!” ? If so, what was it, and what would you have wanted the TC to do about it?

I've been part of the TC during the past year (first time) but I still
have an answer to that question.
There is one thing I wish the TC would do more is to encourage
projects to grow and empower trust in certain projects.
Beside technical things, we want an healthy community and grow
developer's knowledge so OpenStack can be a better place to
contribute. I think some projects are doing well but some of them
might need some mentoring on that front (maybe from some TC members).
For example, I'm thinking about the way some projects handle core
reviewers elections and their metrics used to do so. I think the TC
might ensure that healthy metrics and discussion happen, so projects
can scale.

I'm happy to answer questions on that topic.

Thanks Ed for this first question :-)
--
Emilien Macchi


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Oct 13, 2017 by Ildiko_Vancsa (2,220 points)   1 2
0 votes

On Thu, Oct 12, 2017 at 12:42 PM, Clay Gerrard clay.gerrard@gmail.com wrote:
[trim]

To candidates:

Would you please self select a change (or changes) from
https://github.com/openstack/governance/ in the past ~12 mo or so where they
thought the outcome or the discussion/process was particular good and
explain why you think so?

The one thing that really sticks out to me is the vision statement 1
by the TC.
Not just because such things are scary, but that the process to reach
a vision really
forces the entire group to reach a mutual understanding. I think that
the exercise of
writing the vision was worthwhile, largely because one can't see where
one is going,
without understanding where one is presently.


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Oct 13, 2017 by Julia_Kreger (1,460 points)   3
0 votes

On Thu, Oct 12, 2017 at 8:43 PM Clay Gerrard clay.gerrard@gmail.com wrote:

I like a representative democracy. It mostly means I get a say in which
other people I have to trust to think deeply about issues which effect me
and make decisions which I agree (more or less) are of benefit to the
social groups in which I participate. When I vote IRL I like to consider
voting records. Actions speak louder blah blah.

To candidates:

Would you please self select a change (or changes) from
https://github.com/openstack/governance/ in the past ~12 mo or so where
they thought the outcome or the discussion/process was particular good and
explain why you think so?

The TC proposes and votes governance patches; however its real power, or
better, responsibility, is to inspire, to provide guidance by building
trust first, to work in the community for the community.
I think the TC vision work [0] was a great example of all three. The draft
has been proposed by the TC. Is has been discussed with the community and
everyone had a chance to contribute to it.

I very much appreciated the work on the guiding principles [1] and on the
meetings [2] as well.
The vision was special in the way the community was even more involved than
in the others.

Faithfully,

Andrea Frittoli (andreaf)

[0]
https://governance.openstack.org/tc/resolutions/20170404-vision-2019.html
[1]
https://governance.openstack.org/tc/reference/principles.html#guiding-principles

[2]
https://governance.openstack.org/tc/resolutions/20170718-allow-scheduling-meetings-on-team-channels.html

It'd be super helpful to me, thanks!

-Clay


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Oct 13, 2017 by Andrea_Frittoli (5,920 points)   1 2 3
0 votes

On Thu, Oct 12, 2017 at 7:38 PM Ed Leafe ed@leafe.com wrote:

In the past year or so, has there been anything that made you think “I
wish the TC would do something about that!” ? If so, what was it, and what
would you have wanted the TC to do about it?

I really appreciate the work that the TC has done with the vision and the
community goals.
The TC is applying the ideas of servant leadership, which are a very good
fit with OpenStack guiding principles [0].

I wish the TC would be more proactive in propagating the ideas of servant
leadership and vision into the project teams - and help the PTLs be servant
leaders for their project teams.

Faithfully,

Andrea Frittoli (andreaf)

[0]
https://governance.openstack.org/tc/reference/principles.html#guiding-principles

-- Ed Leafe


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Oct 13, 2017 by Andrea_Frittoli (5,920 points)   1 2 3
0 votes

Clay,

Great question and one that made me think quite a bit. I believe that
while the commits in the Governance repo represent the visible actions
of the TC, the real leadership ability of the TC is often in the
actions that it inspires in people in the community. The TC is a body
that has to lead without any real authority over the individuals that
they lead, which makes it a very interesting form of leadership.

To the specific reviews, I'll pick three [1], [2] and [3]. Let me explain.

The first is a commit that I authored for the governance repository to
formalize the creation of the Stewardship Working Group (SWG). This
group then drove the discussions around the TC Vision which is the
subject of the third review. I'm very thankful for the leadership and
drive that Collette Alexander brought in getting a number of us
together in Detroit to meet and discuss where the TC was and where it
should be going. I was lucky to be one of the non-TC participants at
that meeting and worked with the group that later created the TC
vision which was also well discussed in the community.

The second is another review that I proposed that relates to the
maintenance-mode tag for projects to reflect (accurately) to deployers
and users (collectively to customers) the state of projects that are
not actively being developed.

You explicitly said that "actions speak louder ...", so let me
highlight that the reviews that I cite are ones that I either authored
or participated actively in.

Thanks for the question.

-amrith

[1] https://review.openstack.org/#/c/337895/
[2] https://review.openstack.org/#/c/449925/
[3] https://review.openstack.org/#/c/453262/

On Thu, Oct 12, 2017 at 3:42 PM, Clay Gerrard clay.gerrard@gmail.com wrote:
I like a representative democracy. It mostly means I get a say in which
other people I have to trust to think deeply about issues which effect me
and make decisions which I agree (more or less) are of benefit to the social
groups in which I participate. When I vote IRL I like to consider voting
records. Actions speak louder blah blah.

To candidates:

Would you please self select a change (or changes) from
https://github.com/openstack/governance/ in the past ~12 mo or so where they
thought the outcome or the discussion/process was particular good and
explain why you think so?

It'd be super helpful to me, thanks!

-Clay


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Oct 13, 2017 by amrith.kumar_at_gmai (3,580 points)   2 3
0 votes

Excerpts from Paul Belanger's message of 2017-10-12 23:13:11 -0400:

On Thu, Oct 12, 2017 at 12:42:46PM -0700, Clay Gerrard wrote:

I like a representative democracy. It mostly means I get a say in which
other people I have to trust to think deeply about issues which effect me
and make decisions which I agree (more or less) are of benefit to the
social groups in which I participate. When I vote IRL I like to consider
voting records. Actions speak louder blah blah.

To candidates:

Would you please self select a change (or changes) from
https://github.com/openstack/governance/ in the past ~12 mo or so where
they thought the outcome or the discussion/process was particular good and
explain why you think so?

It'd be super helpful to me, thanks!

-Clay

2017-05-30 Guidelines for Managing Releases of Binary Artifacts [1].

It would have to be 469265[2] that Doug Hellmann proposed after the OpenStack
Summit in Boston. There has been a lot of passionate people in the community
that have been asking for containers, specifically docker in this case.

Regardless of what side you are in the debate of container vs VM, together as a
community we had discussions on what the guideline would look like.
Individually, each project had a specific notion of what publishing containers
would look like, but the TC help navigate some of the technical issues around
binary vs source releasing, versioning and branding (to name a few).

While there is still work to be done on getting the publishing pipeline
finalized, I like to think the interested parties in binary artifacts are happy
we now have governance in place.

[1] http://git.openstack.org/cgit/openstack/governance/tree/resolutions/20170530-binary-artifacts.rst
[2] https://review.openstack.org/469265/

Thanks for highlighting that one, Paul. I agree that was a particularly
good outcome. Everyone involved listened to each other, came to a
common understanding of both the technical and social issues involved,
and worked on the resulting wording together. And it all happened
relatively quickly, too, given how contentious it seemed like it
was going to be at the outset.

Doug


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Oct 13, 2017 by Doug_Hellmann (87,520 points)   3 4 9
0 votes

Excerpts from Ed Leafe's message of 2017-10-12 13:38:03 -0500:

In the past year or so, has there been anything that made you think “I wish the TC would do something about that!” ? If so, what was it, and what would you have wanted the TC to do about it?

-- Ed Leafe

The main issue that I have that hasn't been fully addressed over
the last year is with driver teams. We're still working on how best
to address that situation, and I hope we'll have it resolved over the
next term.

Doug


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Oct 13, 2017 by Doug_Hellmann (87,520 points)   3 4 9
...