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

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
responded Oct 12, 2017 by Clay_Gerrard (5,800 points)   1 2 2
0 votes

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
responded Oct 12, 2017 by emilien_at_redhat.co (36,940 points)   2 6 9
0 votes

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

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!

The vision exercise was, in my opinion, one of the more exciting
things we have done in 2017.
It's not an easy thing to do because of our diverses opinions, but
together we managed to write something down, propose it to the
community in the open and make it better afterward (of course this
will never finish).

Outcome related, I loved the fact we're thinking outside of the
OpenStack community and see how we can make OpenStack projects usable
in environments without all the ecosystem. I also like to see our
strong efforts to increase diversity in all sorts and our work to
improve community health.

Beside the outcome, I loved to see all TC members able to work
together on this Vision in the open, I hope we can do more of that in
the future, even outside of the TC (in teams). (ex: doc team had a PTG
session about visioning as well).
I hope I answered the question, please let me know if that's not the
case if you want more details.
--
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
responded Oct 12, 2017 by emilien_at_redhat.co (36,940 points)   2 6 9
0 votes

On Thu, Oct 12, 2017 at 2:48 PM, Emilien Macchi emilien@redhat.com wrote:

The vision exercise was, in my opinion, one of the more exciting
things we have done in 2017.

Yeah for sure, that was a big goings-on.

It's not an easy thing to do because of our diverses opinions, but
together we managed to write something down, propose it to the
community in the open and make it better afterward (of course this
will never finish).

Outcome related, I loved the fact we're thinking outside of the
OpenStack community and see how we can make OpenStack projects usable
in environments without all the ecosystem. I also like to see our
strong efforts to increase diversity in all sorts and our work to
improve community health.

Beside the outcome, I loved to see all TC members able to work
together on this Vision in the open, I hope we can do more of that in
the future, even outside of the TC (in teams). (ex: doc team had a PTG
session about visioning as well).
I hope I answered the question,

Yup. Unifying and disseminating an acceptable future state of an
organization is definitely one important job of "leadership".

please let me know if that's not the
case if you want more details.
--
Emilien Macchi

Thanks!


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 12, 2017 by Clay_Gerrard (5,800 points)   1 2 2
0 votes

I ment to include reference back to (what I believe) was the original work:

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

On Thu, Oct 12, 2017 at 2:48 PM, Emilien Macchi emilien@redhat.com
wrote:

The vision exercise was, in my opinion, one of the more exciting
things we have done in 2017.

Yeah for sure, that was a big goings-on.

It's not an easy thing to do because of our diverses opinions, but

together we managed to write something down, propose it to the
community in the open and make it better afterward (of course this
will never finish).

Outcome related, I loved the fact we're thinking outside of the
OpenStack community and see how we can make OpenStack projects usable
in environments without all the ecosystem. I also like to see our
strong efforts to increase diversity in all sorts and our work to
improve community health.

Beside the outcome, I loved to see all TC members able to work
together on this Vision in the open, I hope we can do more of that in
the future, even outside of the TC (in teams). (ex: doc team had a PTG
session about visioning as well).
I hope I answered the question,

Yup. Unifying and disseminating an acceptable future state of an
organization is definitely one important job of "leadership".

please let me know if that's not the
case if you want more details.
--
Emilien Macchi

Thanks!


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 12, 2017 by Clay_Gerrard (5,800 points)   1 2 2
0 votes

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

I ment to include reference back to (what I believe) was the original work:

https://review.openstack.org/#/c/453262/


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 12, 2017 by Clay_Gerrard (5,800 points)   1 2 2
0 votes

On Thu, Oct 12, 2017 at 5:48 PM, Emilien Macchi emilien@redhat.com wrote:
On Thu, Oct 12, 2017 at 12:42 PM, Clay Gerrard clay.gerrard@gmail.com wrote:
[...]

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!

The vision exercise was, in my opinion, one of the more exciting
things we have done in 2017.
It's not an easy thing to do because of our diverses opinions, but
together we managed to write something down, propose it to the
community in the open and make it better afterward (of course this
will never finish).

Outcome related, I loved the fact we're thinking outside of the
OpenStack community and see how we can make OpenStack projects usable
in environments without all the ecosystem. I also like to see our
strong efforts to increase diversity in all sorts and our work to
improve community health.

Beside the outcome, I loved to see all TC members able to work
together on this Vision in the open, I hope we can do more of that in
the future, even outside of the TC (in teams). (ex: doc team had a PTG
session about visioning as well).
I hope I answered the question, please let me know if that's not the
case if you want more details.

I think Emilien here covers a lot of what I personally agreed with,
however, I'd like to add more about the cloud application mission:

https://github.com/openstack/governance/blob/master/resolutions/20170317-cloud-applications-mission.rst

As we are delivering fundamental building blocks for applications, we
need to make sure that provide open standards which put into place
best practices in order to consume those resources. In that
resolution, it introduces some concepts which are quite prevalent in
many other infrastructure cloud components (which generally are not
self-hosted) that are not yet very strong inside OpenStack.

For example, using domains for specific applications, improving policy
support for a more predictable set of ACLs which allows developers to
be more productive and empower them more to automate their
infrastructure

The good thing is quite a few good things have come out of this:

  • The OpenStack provider for Kubernetes is getting stronger than even
    (and will soon hopefully get gating to improve stability)
  • Policy in code has made great process over the past few cycles
    (great stepping stone towards more predictable ACLs)

However, I think that we still have quite a bits way to make things
more standardized on this side of things, some projects use
"ResellerAdmin", others picked "Member", some went with "member",
others have ACLs that use "creator", some projects have
project-specific role names. I think that the next step would be to
unify all of those, so that at least the (base) roles are predictable
across clouds.

--
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

--
Mohammed Naser — vexxhost


D. 514-316-8872
D. 800-910-1726 ext. 200
E. mnaser@vexxhost.com
W. http://vexxhost.com


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 Mohammed_Naser (3,860 points)   1 3
0 votes

On Thu, Oct 12, 2017 at 2: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?

This is great and the timing of this question is more important than ever.

I think that the OpenStack infrastructure team is doing a wonderful
job at keeping such a huge CI system working to the best of their
effort, however, I think that there needs to be a stronger
relationship between projects and the infrastructure team in order for
us to help alleviate some of the load that is on them. There are a lot
of moving components from dealing with multiple cloud infrastructure
donors, operating two flavours of clouds internally, maintaining the
codebase of Zuul and other system administration related tasks.

I do think that just like how projects have a release liaison, bug
czar, there should be a notion of a infrastructure team liaison.
Often, there are a lot of things going on in the infrastructure side
of things, jobs might be breaking (for infra related and unrelated
reasons), and keeping up with what's going on on the infrastructure
team to report to the project team.

This would help the infrastructure team tremendously by allowing a
much easier communication channel, as well as assist the team in
avoiding being behind on infrastructure updates and suddenly finding
themselves in the red for a while.

-- 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 Mohammed_Naser (3,860 points)   1 3
0 votes

One thing I wish the TC could do in the past years or so is using their
"power" to help to push a more integrated/collaborative OpenStack.
Though some(all) TC members may think they don't have the power.

On 13/10/17 07:38, Ed Leafe 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?

-- 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

--
Cheers & Best regards,
Feilong Wang (王飞龙)


Senior Cloud Software Engineer
Tel: +64-48032246
Email: flwang@catalyst.net.nz
Catalyst IT Limited
Level 6, Catalyst House, 150 Willis Street, Wellington


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 Fei_Long_Wang (4,460 points)   3 3
0 votes

On Oct 12, 2017, at 8:10 PM, Mohammed Naser mnaser@vexxhost.com wrote:

I think that the OpenStack infrastructure team is doing a wonderful
job at keeping such a huge CI system working to the best of their
effort, however, I think that there needs to be a stronger
relationship between projects and the infrastructure team in order for
us to help alleviate some of the load that is on them. There are a lot
of moving components from dealing with multiple cloud infrastructure
donors, operating two flavours of clouds internally, maintaining the
codebase of Zuul and other system administration related tasks.

Thanks for the answer, and I definitely agree. But I don't feel that you answered the important part: what would you have wanted the TC to do about this?

-- 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

responded Oct 13, 2017 by Ed_Leafe (11,720 points)   1 3 6
...