[openstack-dev] [openstack-ansible] Implement rotations for meetings handling

[Jean-Philippe Evrard]

Hello everyone,

Now that we are all part-time, I'd like to toy with a new idea,
proposed in the past by Jesse, to rotate the duties with people who
are involved in OSA, or want to get involved more (it's not restricted
to core developers!).

One of the first duties to be handled this way could be the weekly meeting.

Handling the meeting is not that hard, it just takes time to prepare,
and to facilitate.

I think everyone should step into this, not only core developers, but
core developers are now expected to run the meetings when their turn
comes.


What are the actions to take:
- Prepare the triage. Generate the list of the bugs for the week.
- Ping people with the triage links around 1h before the weekly
meeting. It would give them time to get prepared for meeting,
eventually updating the agenda, and read the current bugs
- Ping people at the beginning of the meeting
- Chair the meeting: The structure of the meeting is now always
the same, a recap of the week, and handling the bug triage.
- After the meeting we would ask who is volunteer to run next
meeting, and if none, a meeting char will be selected amongst core
contributors at random.

Thank you for your understanding.

Jean-Philippe Evrard (evrardjp)

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-***@lists.openstack.org?subject:unsubscribe
http://lists.openstac

[Mohammed Naser]

On Wed, May 2, 2018 at 11:14 AM, Jean-Philippe Evrard

Post by Jean-Philippe Evrard
Hello everyone,
Now that we are all part-time, I'd like to toy with a new idea,
proposed in the past by Jesse, to rotate the duties with people who
are involved in OSA, or want to get involved more (it's not restricted
to core developers!).
One of the first duties to be handled this way could be the weekly meeting.

+1

I think that's something that we can share amongst us as a responsibility and
take turns doing.

Post by Jean-Philippe Evrard
Handling the meeting is not that hard, it just takes time to prepare,
and to facilitate.
I think everyone should step into this, not only core developers, but
core developers are now expected to run the meetings when their turn
comes.
- Prepare the triage. Generate the list of the bugs for the week.
- Ping people with the triage links around 1h before the weekly
meeting. It would give them time to get prepared for meeting,
eventually updating the agenda, and read the current bugs
- Ping people at the beginning of the meeting
- Chair the meeting: The structure of the meeting is now always
the same, a recap of the week, and handling the bug triage.
- After the meeting we would ask who is volunteer to run next
meeting, and if none, a meeting char will be selected amongst core
contributors at random.
Thank you for your understanding.
Jean-Philippe Evrard (evrardjp)
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[David Wilde]

I am definitely +1 on this, I think it's a great idea.

Thanks,

Dave Wilde (d34dh0r53)

Post by Mohammed Naser
On Wed, May 2, 2018 at 11:14 AM, Jean-Philippe Evrard

Post by Jean-Philippe Evrard
Hello everyone,
Now that we are all part-time, I'd like to toy with a new idea,
proposed in the past by Jesse, to rotate the duties with people who
are involved in OSA, or want to get involved more (it's not restricted
to core developers!).
One of the first duties to be handled this way could be the weekly

meeting.
+1
I think that's something that we can share amongst us as a responsibility and
take turns doing.

Post by Jean-Philippe Evrard
Handling the meeting is not that hard, it just takes time to prepare,
and to facilitate.
I think everyone should step into this, not only core developers, but
core developers are now expected to run the meetings when their turn
comes.
- Prepare the triage. Generate the list of the bugs for the week.
- Ping people with the triage links around 1h before the weekly
meeting. It would give them time to get prepared for meeting,
eventually updating the agenda, and read the current bugs
- Ping people at the beginning of the meeting
- Chair the meeting: The structure of the meeting is now always
the same, a recap of the week, and handling the bug triage.
- After the meeting we would ask who is volunteer to run next
meeting, and if none, a meeting char will be selected amongst core
contributors at random.
Thank you for your understanding.
Jean-Philippe Evrard (evrardjp)

__________________________________________________________________________

Post by Jean-Philippe Evrard
OpenStack Development Mailing List (not for usage questions)
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[Amy Marrich]

+1, leading meetings is a great way to get folks involved in the Community
and gives them some 'ownership' within the project.

Amy (spotz)

On Wed, May 2, 2018 at 10:14 AM, Jean-Philippe Evrard <

Post by Jean-Philippe Evrard
Hello everyone,
Now that we are all part-time, I'd like to toy with a new idea,
proposed in the past by Jesse, to rotate the duties with people who
are involved in OSA, or want to get involved more (it's not restricted
to core developers!).
One of the first duties to be handled this way could be the weekly meeting.
Handling the meeting is not that hard, it just takes time to prepare,
and to facilitate.
I think everyone should step into this, not only core developers, but
core developers are now expected to run the meetings when their turn
comes.
- Prepare the triage. Generate the list of the bugs for the week.
- Ping people with the triage links around 1h before the weekly
meeting. It would give them time to get prepared for meeting,
eventually updating the agenda, and read the current bugs
- Ping people at the beginning of the meeting
- Chair the meeting: The structure of the meeting is now always
the same, a recap of the week, and handling the bug triage.
- After the meeting we would ask who is volunteer to run next
meeting, and if none, a meeting char will be selected amongst core
contributors at random.
Thank you for your understanding.
Jean-Philippe Evrard (evrardjp)
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[Jimmy McCrory]

+1 good idea

Post by Amy Marrich
+1, leading meetings is a great way to get folks involved in the Community
and gives them some 'ownership' within the project.
Amy (spotz)
On Wed, May 2, 2018 at 10:14 AM, Jean-Philippe Evrard <

Post by Jean-Philippe Evrard
Hello everyone,
Now that we are all part-time, I'd like to toy with a new idea,
proposed in the past by Jesse, to rotate the duties with people who
are involved in OSA, or want to get involved more (it's not restricted
to core developers!).
One of the first duties to be handled this way could be the weekly meeting.
Handling the meeting is not that hard, it just takes time to prepare,
and to facilitate.
I think everyone should step into this, not only core developers, but
core developers are now expected to run the meetings when their turn
comes.
- Prepare the triage. Generate the list of the bugs for the week.
- Ping people with the triage links around 1h before the weekly
meeting. It would give them time to get prepared for meeting,
eventually updating the agenda, and read the current bugs
- Ping people at the beginning of the meeting
- Chair the meeting: The structure of the meeting is now always
the same, a recap of the week, and handling the bug triage.
- After the meeting we would ask who is volunteer to run next
meeting, and if none, a meeting char will be selected amongst core
contributors at random.
Thank you for your understanding.
Jean-Philippe Evrard (evrardjp)
____________________________________________________________
______________
OpenStack Development Mailing List (not for usage questions)
e
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[Doug Hellmann]

Post by Jean-Philippe Evrard
Hello everyone,
Now that we are all part-time, I'd like to toy with a new idea,
proposed in the past by Jesse, to rotate the duties with people who
are involved in OSA, or want to get involved more (it's not restricted
to core developers!).
One of the first duties to be handled this way could be the weekly meeting.
Handling the meeting is not that hard, it just takes time to prepare,
and to facilitate.
I think everyone should step into this, not only core developers, but
core developers are now expected to run the meetings when their turn
comes.
- Prepare the triage. Generate the list of the bugs for the week.
- Ping people with the triage links around 1h before the weekly
meeting. It would give them time to get prepared for meeting,
eventually updating the agenda, and read the current bugs
- Ping people at the beginning of the meeting
- Chair the meeting: The structure of the meeting is now always
the same, a recap of the week, and handling the bug triage.
- After the meeting we would ask who is volunteer to run next
meeting, and if none, a meeting char will be selected amongst core
contributors at random.
Thank you for your understanding.
Jean-Philippe Evrard (evrardjp)

This is a great idea for sharing the load of organizing the team!

Doug

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

[Marc Gariepy]

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

[Andy McCrae]

Post by Jean-Philippe Evrard
Now that we are all part-time, I'd like to toy with a new idea,
proposed in the past by Jesse, to rotate the duties with people who
are involved in OSA, or want to get involved more (it's not restricted
to core developers!).
One of the first duties to be handled this way could be the weekly meeting.
Handling the meeting is not that hard, it just takes time to prepare,
and to facilitate.
I think everyone should step into this, not only core developers, but
core developers are now expected to run the meetings when their turn
comes.
- Prepare the triage. Generate the list of the bugs for the week.
- Ping people with the triage links around 1h before the weekly
meeting. It would give them time to get prepared for meeting,
eventually updating the agenda, and read the current bugs
- Ping people at the beginning of the meeting
- Chair the meeting: The structure of the meeting is now always
the same, a recap of the week, and handling the bug triage.
- After the meeting we would ask who is volunteer to run next
meeting, and if none, a meeting char will be selected amongst core
contributors at random.
Thank you for your understanding.
Jean-Philippe Evrard (evrardjp)

I will gladly pick up my well-used meeting chair hat.
It's a great idea, I think it would help make our meetings more productive.
Once you've been chair you have a different view of how the meetings work.

Andy

[Mike Carden]

Hi OSA peeps.

I apologise in advance for what may seem like an impertinent question. And
for those playing along at home, I was just getting the hang of
contributing to OSA when last year my employer decided that some of us were
no longer needed, and OpenStack lost quite a few full time employed
contributors.

So my question is... what is the health status of OSA? Is there still a
core of committed contributors? I only check in on OSA code reviews rarely
now, but activity seems a lot less than it was.

Before you answer, imagine that I now work for a moderately large,
potential consumer of OSA.

Is OSA the future, or have other deployment projects made it less relevant?
--
MC

Post by Andy McCrae

Post by Jean-Philippe Evrard
Now that we are all part-time, I'd like to toy with a new idea,
proposed in the past by Jesse, to rotate the duties with people who
are involved in OSA, or want to get involved more (it's not restricted
to core developers!).
One of the first duties to be handled this way could be the weekly meeting.
Handling the meeting is not that hard, it just takes time to prepare,
and to facilitate.
I think everyone should step into this, not only core developers, but
core developers are now expected to run the meetings when their turn
comes.
- Prepare the triage. Generate the list of the bugs for the week.
- Ping people with the triage links around 1h before the weekly
meeting. It would give them time to get prepared for meeting,
eventually updating the agenda, and read the current bugs
- Ping people at the beginning of the meeting
- Chair the meeting: The structure of the meeting is now always
the same, a recap of the week, and handling the bug triage.
- After the meeting we would ask who is volunteer to run next
meeting, and if none, a meeting char will be selected amongst core
contributors at random.
Thank you for your understanding.
Jean-Philippe Evrard (evrardjp)

I will gladly pick up my well-used meeting chair hat.
It's a great idea, I think it would help make our meetings more productive.
Once you've been chair you have a different view of how the meetings work.
Andy
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[Jesse Pretorius]

Hi Mike – please see my responses in-line.

From: Mike Carden <***@gmail.com>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-***@lists.openstack.org>
Date: Thursday, May 3, 2018 at 9:42 AM
To: "OpenStack Development Mailing List (not for usage questions)" <openstack-***@lists.openstack.org>
Subject: Re: [openstack-dev] [openstack-ansible] Implement rotations for meetings handling


* So my question is... what is the health status of OSA? Is there still a core of committed contributors? I only check in on OSA code reviews rarely now, but activity seems a lot less than it was.

I’m not sure how to answer this, really. OSA is used by a variety of organizations, and contributed to by a number of organizations. The health of the project depends on the contributions of those who consume it. A quick review of Stackalytics shows that OSA has multiple contributing stakeholders, which means that the risk of project failure is managed. See http://stackalytics.com/?metric=commits&module=openstack-ansible / http://stackalytics.com/?metric=person-day&module=openstack-ansible for Rocky stats, and you can look back in history using the ‘Release’ drop-down box on the left.


* Before you answer, imagine that I now work for a moderately large, potential consumer of OSA.

OK, you’d be in good company if you check the contributing companies in Stackalytics.


* Is OSA the future, or have other deployment projects made it less relevant?

OSA is one of many deployment projects. Each has their own style. Pick the one that suits your needs best.

________________________________
Rackspace Limited is a company registered in England & Wales (company registered number 03897010) whose registered office is at 5 Millington Road, Hyde Park Hayes, Middlesex UB3 4AZ. Rackspace Limited privacy policy can be viewed at www.rackspace.co.uk/legal/privacy-policy - This e-mail message may contain confidential or privileged information intended for the recipient. Any dissemination, distribution or copying of the enclosed material is prohibited. If you receive this transmission in error, please notify us immediately by e-mail at ***@rackspace.com and delete the original message. Your cooperation is appreciated.

[Jean-Philippe Evrard]

I think Jesse sumarized things elegantly.

Here is an analogy for you, to complement the answer with more
background. Let me compare our state with a new company,
as this is a a notion people many people can relate to.

Initially we were a startup. Only a few people were working on OSA on
its creation. And they were busy doing everything.
But then we grew, and we continue to grow. At some point, those few
people doing everything didn't (or don't) have the time to do
everything anymore (because of the growing nature). So OSA, like any
business, needs to learn how to grow bigger.

One of the way is to distribute work as much as we can into the more
appropriate persons.
We started doing that by distributing core duties for roles.
We are now adding the meeting organisation.
I have a few other ideas where shared ownership will help the project
mature and allow more growth in the future, but one step at a time :)

Best regards,
Jean-Philippe Evrard (evrardjp)

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-***@lists.openstack.org?subject:unsubscribe
http://lists.open