#203 Weekly to Mothly Meeting for the Join SiG
Closed: Fixed by nasirhm. Opened by nasirhm.

It's been quite some time we folks have had a Meeting on IRC and are using Needs Comment along with Future Meeting so people can asynchronously comment according to their timezones. Great Idea

I would like to suggest that there are some issues like deciding the flow for Fedora Classrooms that if discussed in a meeting would be really helpful. So rather than having meetings every week, we can set them up once or bi-monthly according to the number of tickets available for Future Meeting.

What do you guys think ?


I'm generally +1 to meetings, but they need to be limited to decision making. FESCo is an excellent example:
https://meetbot.fedoraproject.org/teams/fesco/fesco.2020-04-13-15.01.log.html

Meetings for any Fedora team always have the usual issues:

  • most of us work full time, and have families that we must commit our time to: so we're sometimes unable to commit time to meetings. With the lockdowns currently, more of us are working at home. Folks with kids are also looking after their children at home, which is already making working from home harder.

  • finding a time that works for us, in all our different time zones is always hard.

So, perhaps once a month maybe doable?

As far as discussion is concerned, we just have to be more active on Pagure here. The "needs-comment" tickets need to be looked at regularly. How we go about helping everyone do that is a different discussion in itself :(

Thoughts?

Agreed, How about setting up a meeting to get some active input on tickets marked as either Future Meeting or Next-Meeting and set a criteria for tickets that can be marked by those tickets, Tickets not meeting that criteria for Decision Making can be marked as Needs Comment.

For the time zones, we can fine some comfortable time between the time zones of the members joining.

After the meeting, if we wouldn't have many tickets marked as that, maybe we can extend the meeting to bimonthly too.

What do other members of the team think, Kindly share your thoughts.?

I'm generally +1 to meetings too,

Regards.,

@nasirhm : should we timebox this to a week? That's enough time for everyone to weigh in?

Please everyone comment before then :)

I've created a milestone so we have some "end date", please use it for other tasks. In the absence of bi-weekly meetings, milestones are a good way of adding some time limits to tasks.

Metadata Update from @ankursinha:
- Issue set to the milestone: 2020-05-10

@nasirhm : should we timebox this to a week? That's enough time for everyone to weigh in?
Please everyone comment before then :)

Sounds Good, Let's see what others think.

I've created a milestone so we have some "end date", please use it for other tasks. In the absence of bi-weekly meetings, milestones are a good way of adding some time limits to tasks.

Thank You, would use it from now onwards, It somehow resonates with the Monthly Classroom sessions thing.

I'm not against meetings, but personally I always have lack of time in following a meeting from the start to the end :-(

I think that's the common issue for all of us @alciregi :(

@nasirhm : what if we focus on a better asynchronous decision making process, like the "lazy approval" processes fesco and the council etc follow? That allow everyone to weigh in when they have time?

https://docs.fedoraproject.org/en-US/council/

Hmm, Lazy approval sounds good, how about time bounding the issues that needs comment like a Week or two ?

+1, every issue should be timeboxed (like this one).

Awesome, let's se if others have any constructive feedback and ideas to improve it :)

4 more days for this ticket, so let's keep that in mind :)

Asynchronous decision making process doesn't exclude meetings btw
We can try to organize a meeting just to take stock of the situation, to close old tickets, to introduce new members, etc.

Sounds Good, For now let's keep the decision making progress Asynchronous, If in any case some thing occurs which requires the need for a meeting. We can mark that ticket as Next meeting and then we can organize the meeting accordingly.

For now let's stick with Needs Comment :D

Good to Close ?

We're good to close as things are working fine without meetings and the topics set to next meeting are discussed generally on the Communication channels, If something of critical severity arises we can schedule a meeting to discuss it.

Metadata Update from @nasirhm:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Sounds good. +1 to close.

--
Thanks,

Ankur

(Sent from mobile device)

This ticket has been migrated to the forgejo instance. Please find the new ticket here
https://forge.fedoraproject.org/join/Fedora-Join//issues/203

Metadata