[openstack-ansible] Evaluating meeting schedule + method
Hey everyone: Over the past few weeks, the OpenStack Ansible meetings have had increasingly less attendance. In addition, the engagement seems to be decreased as well. I think IRC meetings are generally awful and it's really hard to come up with a proper engagement, because you get pulled into 60 other things and the meeting gets forgotten. I'd like to suggest a few things: - Look into a voice-based meeting system which is recorded + notes: This will help with engagement and discussion, we'll actually be able to get things done. - Change meeting topics: perhaps people don't care about what we discuss? - Change meetings to once every 2 weeks or month (or even cancel them). I'm sending this to the community to hear what they have to say about this. Thanks, Mohammed -- Mohammed Naser — vexxhost ----------------------------------------------------- D. 514-316-8872 D. 800-910-1726 ext. 200 E. mnaser@vexxhost.com W. http://vexxhost.com
On Tuesday, 27 November 2018 17:50:12 CET Mohammed Naser wrote:
Hey everyone:
Over the past few weeks, the OpenStack Ansible meetings have had increasingly less attendance. In addition, the engagement seems to be decreased as well.
I think IRC meetings are generally awful and it's really hard to come up with a proper engagement, because you get pulled into 60 other things and the meeting gets forgotten. I'd like to suggest a few things:
- Look into a voice-based meeting system which is recorded + notes: This will help with engagement and discussion, we'll actually be able to get things done. - Change meeting topics: perhaps people don't care about what we discuss? - Change meetings to once every 2 weeks or month (or even cancel them).
Did you try to check what are the people the attended before and are not attending anymore? In the last weeks there was also the summit and few vacations in the Europe and in the US. Yes, a chat system allows you to multitask and do other things, but, personally speaking, when I hear about a voice-based meeting, I think I would not join at all (while I can quickly skim through the chat logs meeting). -- Luigi
Yes, a chat system allows you to multitask and do other things, but,
I think the problem IS multitasking. It can become a really frustrating experience for meeting chair tbh. We have faced this fluctuating attendance in the past. I proposed to change meeting time, change of topics, and change of frequency. All of the above lead to a temporary increase in the meeting attendance for a week or two, followed by a return to the status quo. We can replace the status update of last week/focus of the week by a regular mail to the ML. That could be the equivalent of the WHOA (What's happening in OpenStack-Ansible, featuring Keanu Reeves' memes) Major wrote in the past. Open Discussion is something we achieve generally in our channel outside meetings. Having an office hour there could ensure people could come to a certain time and we'd be there. Attendance would be identitical though, but it's not really an issue to me. Only one section remains, bug triage. Bug triage had not only a goal of triaging bugs, but we also actively engage with people to get contributions. I am not sure how this can be adapted, as we need people actively working together at the same time. Maybe organising more regular bug smashes instead? Regards, Jean-Philippe Evrard (evrardjp)
On Wed, Nov 28, 2018 at 4:49 AM Jean-Philippe Evrard <jean-philippe@evrard.me> wrote:
Having an office hour there could ensure people could come to a certain time and we'd be there. Attendance would be identitical though, but it's not really an issue to me.
just wanted to add another data point here. the API-SIG recently migrated from regular meeting times to office hours. one of the big reasons for this was that our regular weekly meeting attendance had dropped to minimal levels. so far we've found that the office hours have lessened the strain on the chairs and organizers while still giving us a few very visible times for the community to interact with us. the API-SIG isn't quite the same as a code central project, but i think the pattern of meeting migration is more general in nature. hope this helps =) peace o/
On Wed, Nov 28, 2018 at 10:55 AM Michael McCune <msm@redhat.com> wrote:
On Wed, Nov 28, 2018 at 4:49 AM Jean-Philippe Evrard <jean-philippe@evrard.me> wrote:
Having an office hour there could ensure people could come to a certain time and we'd be there. Attendance would be identitical though, but it's not really an issue to me.
just wanted to add another data point here. the API-SIG recently migrated from regular meeting times to office hours. one of the big reasons for this was that our regular weekly meeting attendance had dropped to minimal levels. so far we've found that the office hours have lessened the strain on the chairs and organizers while still giving us a few very visible times for the community to interact with us.
the API-SIG isn't quite the same as a code central project, but i think the pattern of meeting migration is more general in nature. hope this helps =)
peace o/
Unfortunately, I haven't heard a lot of the OpenStack Ansible side of things however I'm very happy to hear about what's going on with other projects and how to pick ways to manage our meetings. The first step that I'd like to maybe suggest is going to an office hours model? I'm still not sure how that will increase our engagement in meetings. -- Mohammed Naser — vexxhost ----------------------------------------------------- D. 514-316-8872 D. 800-910-1726 ext. 200 E. mnaser@vexxhost.com W. http://vexxhost.com
participants (4)
-
Jean-Philippe Evrard
-
Luigi Toscano
-
Michael McCune
-
Mohammed Naser