#120 Elect a CommOps Mindshare representative
Closed: Complete 3 years ago Opened 3 years ago by jflory7.

Summary

@robyduck asked CommOps to choose a representative for the Mindshare Committee by the next election (December 5) (see: email).

Background

Mindshare is a new committee that will replace the Fedora Ambassador Steering Committee (FAmSCo). The purpose of this is to encourage regular communication between all sub-projects, so the project moves forward in step together (instead of moving forward without understanding where the rest of Fedora is).

The wiki page explains more, although it is currently marked as a draft and may change.

Detail

CommOps is allocated one seat on the new Mindshare Committee. CommOps must choose how our representative is selected (i.e. it is not a seat up for general election). Other than selecting a candidate for the upcoming election, we need to establish a procedure for this as well.

This is a high-priority topic to be discussed at our next meeting. A candidate needs to be put forward by December 5th, which is when nominations open for the general election.

Action

We need to…

  • Establish a process for selecting the Mindshare representative
    • Idea: Take names, vote among team members, serve a period of two releases before cycling the seat back up for election?
  • Select a candidate for the next election

Metadata Update from @jflory7:
- Issue assigned to jflory7
- Issue priority set to: critical (next week)
- Issue set to the milestone: Fedora 27 (to Nov. 2017)
- Issue tagged with: Mindshare, internal operations, meeting

3 years ago

Detail
CommOps is allocated one seat on the new Mindshare Committee. CommOps must choose how our representative is selected (i.e. it is not a seat up for general election). Other than selecting a candidate for the upcoming election, we need to establish a procedure for this as well.
This is a high-priority topic to be discussed at our next meeting. A candidate needs to be put forward by November 7th, which is when nominations open for the general election.

It is high priority, but the deadline is not November 7th, which would be a very very late request.
You don't need to nominate a candidate for the upcoming elections (anyone who wnats can run for Mindshare, we have two seats to fill through normal elections). What I am asking for is to appoint your CommOps representative who will fill the CommOps seat in Mindshare. This way each outreach team will have at least one seat and voice within Mindshare.
It is up to each team how you want to choose your representative, but you should appoint him by the end of the election period, when results are published and which will be likely in December.

Thanks for taking this request as high priority.

  • Establish a process for selecting the Mindshare representative
    • Idea: Take names, vote among team members, serve a period of two releases before cycling the seat back up for election?

+1, I can't really think of anything better for a small team (of < 10 people)

However, I think that there is a question of who is the member - i.e. who is to vote. FAS membership is irrelevant. How do you rate activity? All the questions we struggle to answer in other areas of the project.

@robyduck said…
It is high priority, but the deadline is not November 7th, which would be a very very late request.

Ah okay, this is good to know. Looking at the elections schedule, this date is December 5th. This gives us a little bit of time to formalize a process, which is helpful. I'll update the original date in the ticket after posting this.

@robyduck said…
What I am asking for is to appoint your CommOps representative who will fill the CommOps seat in Mindshare. This way each outreach team will have at least one seat and voice within Mindshare.

Oops, I knew this for CommOps, but used the wrong words. Thanks for the clarification. :smile:

@rhea said…
However, I think that there is a question of who is the member - i.e. who is to vote. FAS membership is irrelevant. How do you rate activity? All the questions we struggle to answer in other areas of the project.

I think it might be time to visit our FAS group members. I think for the size of our team, the FAS group is an effective way of getting this count. But we need to clean up inactive / old members who are no longer involved with the team. Since our FAS group is barely 30 people, it won't be hard, but it's just time-consuming work. I should file a new ticket for this one too.

I think it might be time to visit our FAS group members. I think for the size of our team, the FAS group is an effective way of getting this count. But we need to clean up inactive / old members who are no longer involved with the team. Since our FAS group is barely 30 people, it won't be hard, but it's just time-consuming work. I should file a new ticket for this one too.

I want this can help u @jflory7 .It's a list of the commops members with FAS "last seen" > 06/01/17 (MM/DD/YY) . This only says they was active recently but not if they work on CommOps related things :pensive:

FedoraCommops.csv

Discussed in 2017-10-30 meeting.

We divided the work for this ticket into three pieces.

Updating active members in FAS

If we want to make a voting requirement based on FAS group membership, we need to establish rules to maintain membership and also remove contributors who are no longer active in Fedora. I always like to send a personal email with guidance on how to get started again.

I plan to review the list provided by @bt0dotninja over the weekend, send emails to inactive accounts, and remove them from the group. I hope to have more to say by the next meeting on Nov. 6th.

Establishing a selection process

Since we're a small team, I believe it's better to have a simple process. Here's some of the basic requirements for the CommOps seat as I see it:

  • Representative serves for two releases (e.g. Fedora 27, Fedora 28)
  • Any sponsored member of FAS group eligible to run
    • Could add another requirement, e.g. X number of CommBlog posts published, assigned and completed X number of tickets, etc.
  • Sponsored members of group vote in ticket / meeting if multiple candidates
    • If privacy a concern, we could use the election app
  • If two candidates for seat, and one has just served for two terms, the incumbent is not eligible to run again
    • Curious for feedback on this one; I thought this would be good to encourage fresh voices / perspective on the seat and to try to actively involve others in Mindshare, helping represent the team there

Selecting a candidate for F27-F28

Once we establish a process, we can put it into process for this upcoming term.

Metadata Update from @jflory7:
- Issue tagged with: needs feedback

3 years ago

Discussed in 2017-11-06 meeting.

FAS group membership

This is a task I'm working to complete in the next 24 hours.

Selection process

In the meeting, we finalized the selection process and dropped the last requirement. As of now, this is our process.

  • Representative serves for two releases before opportunity to re-confirm commitment (e.g. Fedora 27, Fedora 28)
  • Any sponsored member of FAS group eligible to run
  • Sponsored members of group vote in ticket / meeting if multiple candidates

Candidates

We put out a tentative call for candidates. I was interested in filling this role, but we're keeping this ticket open for the next week to let anyone else throw their hat in the ring. I'd be very interested in supporting someone else in this position too, if there is interest. :smile:

Discussed in 2017-11-20 meeting.

Not much else to cover. I am announcing the availability of the seat on our mailing list, and then removing the ticket from the meeting agenda. On Dec. 4th, we will review our final nomination list and get a candidate to @robyduck at the end of the meeting.

Anyone who wishes to enter a nomination should add a new comment to this ticket.

As mentioned earlier, I self-nominated myself for this position.

Metadata Update from @jflory7:
- Issue untagged with: meeting
- Issue set to the milestone: Fedora 28 (to May 2018) (was: Fedora 27 (to Nov. 2017))

3 years ago

Metadata Update from @jflory7:
- Issue untagged with: needs feedback
- Issue tagged with: blocked

3 years ago

Metadata Update from @jflory7:
- Issue priority set to: normal (1-2 weeks) (was: critical (next week))

3 years ago

Metadata Update from @jflory7:
- Issue untagged with: blocked
- Issue priority set to: critical (next week) (was: normal (1-2 weeks))
- Issue tagged with: meeting

3 years ago

Discussed in 2017-12-04 meeting.

Ticket complete

I am the only candidate for CommOps. As we discussed two weeks ago, I added myself to the Mindshare members page. Closing this ticket as complete.

Metadata Update from @jflory7:
- Issue untagged with: meeting

3 years ago

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

3 years ago

Login to comment on this ticket.

Metadata
Attachments 1
Attached 3 years ago View Comment