In our Mindshare Committee meeting today, the issue of re-election and policy regarding seats was brought up. There are a few points that need discussion and a couple tasks to be done.
Re-election policy needs to be put onto docs Mindshare page
How to handle unresponsive members of the committee? - how do we define unresponsive (i.e. someone says they want to be involved, but do not show up to meetings)
What are expectations around the amount of activity a member should be doing?
Need to confirm each team represented has a re-appointment process and have an understanding of how those processes work.
Please provide some feedback. Thanks!
How to handle unresponsive members of the committee? - how do we define unresponsive (i.e. someone says they want to be involved, but do not show up to meetings) What are expectations around the amount of activity a member should be doing?
The principal object is, we need commitment...
For example:
A same initiative comes from Neuro Fedora GROUP, the TEAM open a ticket in Fedora Community Operations (CommOps) to provide a script to manage a similar situation, I think we can have benefit from it, here is the ticket open there:
https://pagure.io/fedora-commops/issue/204
and then take action....
Regards.,.
I'm updating the commops script but by now I can upload some data here. the mindshare.ods file shows the current members of the mindshare FAS group. So we need to add @hhlp in the mindshare group.
+1 to using the script to gather some data on activity. We agreed to the following metrics to measure: Participation in meetings Activity on pagure
@bt0dotninja really cool, thanks for the update! Next mindshare meeting we will begin to brainstorm ways we want to use this.
Metadata Update from @bt0dotninja: - Issue close_status updated to: Moved - Issue status updated to: Closed (was: Open)