I am good with this approach the only thing (which I am tired of repeating and now feel sad to state it again), we need to consider other time zones as well while running such meetings. People are really motivated from this part of the globe as well to participate but the current meeting time does not suit and fit in their schedule. Even-if they try, they tend to miss it.

I know we can not solve TZ (time zone) issue, but being diversity team, we need to find some middle ground in order to be inclusive and to give everyone a fair chance to participate.

+1 for reserving the last ten minutes of each weekly meeting before open floor for this. Shall we note down status somewhere? This will helpful for us to know what we achieved every week.

I am good with this approach the only thing (which I am tired of repeating and now feel sad to state it again), we need to consider other time zones as well while running such meetings. People are really motivated from this part of the globe as well to participate but the current meeting time does not suit and fit in their schedule. Even-if they try, they tend to miss it.
I know we can not solve TZ (time zone) issue, but being diversity team, we need to find some middle ground in order to be inclusive and to give everyone a fair chance to participate.

yea, it will be great if we can change the current meeting time slightly (before 1-2 hours).

I am good with this approach the only thing (which I am tired of repeating and now feel sad to state it again), we need to consider other time zones as well while running such meetings. People are really motivated from this part of the globe as well to participate but the current meeting time does not suit and fit in their schedule. Even-if they try, they tend to miss it.
I know we can not solve TZ (time zone) issue, but being diversity team, we need to find some middle ground in order to be inclusive and to give everyone a fair chance to participate.

+1 for considering other time zones also, as it will help us to get more participation.

+1 for your suggestion Justin, this way it will be easier for the D&I Representative (me for now, until we have the next elections) to send the most important updates to Council. But also I agree with Amita regarding the timezones - maybe weekend would be easier to dedicate just one hour to the meeting without the work time restrictions. Thoughts?

@amsharma:
I know we can not solve TZ (time zone) issue, but being diversity team, we need to find some middle ground in order to be inclusive and to give everyone a fair chance to participate.

Previously we discussed alternating between NA-friendly and APAC-friendly meeting times each week. @amsharma Were you able to put together the WhenIsGood poll for an APAC-friendly meeting time?

I liked the weekend suggestion.
No I did not do the WIG for apac as people wants to have a common meeting, not separate.

I wrote a status update for D&I team, and you can find it here: https://pagure.io/Fedora-Council/status_reports/pull-request/3

If I forgot something, I can add it at the next report that I will write. We need to provide reports every week.

Every week will be too much. This should be atleast bi-weekly. @jonatoni ?

We need to do this every week, but bi-weekly updates should be fine as well.

Hi @jonatoni are we doing it at present as well? How often we submit reports. Can we view those reports somewhere please? Thanks,

The status reports are not designed to fit the workflow of our team; I think we should push back to find a way to make this successful or abolish these so we stop feeling guilty for work we are not equipped to do.

The status updates are published in the Fedora Council docs. The source is maintained in a Pagure repo maintained by @bcotton. The last update from the D&I Team was August 20th, 2019.

Every week is too much for our team when we are holding meetings maybe once a month. If that. If someone's paid responsibility included Fedora D&I, maybe every week would be possible. But we are all volunteers trying to balance Fedora in our busy lives. We don't have updates every week and it is unrealistic to expect us to have updates every week.

One possible way to adjust this an update once a Fedora release. Fedora release schedule is not relevant to our team, but it fits the planning model that the rest of the development-focused parts of Fedora already use. It might be a path of least resistance.

Alternatively, we could abolish these reports. But if we are going to continue feeling guilty about not publishing anything, we need to figure out something that does work.

cc: @mattdm @riecatnor

One of the outcomes from the November Council meeting was for me to work with the people representing each team to determine an update cadence that works for them. It's on my list, hopefully very soon, because I'd like to start getting status reports from teams again.

See the CommBlog post for more info.

I like way you challenge the existing workflows @jflory7 :laughing:
But honestly, the points and reasoning you have put on the table are very valid. Thanks.

We need to ask council what is the need and how they can help us fulfil the status requirement as we are not currently fully equipped with right resources. We also need to set the right expectations as a team of volunteers, what we can achieve and what not.

For now, I see we have two options for this -
Either council should help us get a full time paid position for our team. This person can help us achieve much more than just regular weekly/bi-weekly status reports but also in many different brilliant ideas execution at Fedora community.
OR leave it to the team to decide how frequent these status reports can be provided.

cc: @mattdm @riecatnor @bcotton

I've emailed @jonatoni to discuss frequency. This ticket can either be closed or reassigned to her.

@bcotton is going to provide training on how to do this! See Fedora-Council/tickets#318.

@bcotton passed info to me on the updates. We are moving to a four-week cadence for D&I updates on the status dashboard. I have made a few PRs already to the dashboard.

Closing this ticket as complete! :clapper: