#18 Nominating a team lead
Closed: Complete Opened by jflory7.

Summary

The Diversity Adviser role is currently unfilled, but we need someone to help organize and drive Diversity and Inclusion efforts in Fedora. This ticket summarizes what we need and intends to open the floor for someone to volunteer in a leadership capacity.

Background

One of the repeating themes from our discussions in the past few weeks is how to enable ourselves to be the most productive in our limited time as volunteers. Currently, there are some organizational challenges limiting us from using some of our time together most effectively. Resolving these challenges will move us towards maximizing our time together and working through tasks at a more expedient rate. One of the things that will help us accomplish this is choosing someone to help drive and lead some of the efforts that we are working on. Having someone in this leadership role would help us take down some of these blockers and help us make progress quicker than we have been.

Responsibilities

Some of the responsibilities of what this would look like are outlined below. This list is not exhaustive.

  • Chairing meetings
    • Would chair IRC / video meetings and help organize the team meeting structure to maximize the most effective use of our time
    • Responsible for creating agenda before meeting as a rough outline of what to cover
  • Identify core short-term and long-term tasks
    • Recognize existing tasks, identify new tasks, and prioritize based on team bandwidth and expertise
      • New tasks to focus on how to have a larger impact on Fedora and community
    • Strategize how we proceed together as a team to accomplish these tasks
  • Helping break down and delegate tasks
    • Some of our tasks are very big and need to be broken into smaller pieces with timelines for completion to be realistic
    • Spend time looking at existing tickets, help envision the goals, and form a path forward from current position
    • Collaborate with others to help envision the goals and work with team members to build realistic timelines on what they can include
    • Delegate action items with realistic check-ups when possible
  • Coordination and representation with the Fedora Council
    • As with the Diversity Adviser role, attend Council meetings and serve as the Diversity and Inclusion representative where possible
    • Represent needs and vision of D&I efforts and act as a liason between Council and Diversity WG
  • Ticket / wiki gardening
    • Keep ticket metadata updated and current with tags, priorities, milestones
    • When necessary, help garden the wiki with accurate / current information

Length of leadership

Since this is a volunteer position, it is difficult to pin this onto someone as a permanent role. As a suggested way of maintaining this in the long run, we could have the team lead follow the Fedora release cycles, and at the beginning of every release, the team lead would have a chance to renew their leadership role. If someone else wanted to help lead the team, they would also have a chance to self-nominate. This could become integrated into the Fedora Elections cycle for a community election (but for the immediate sense, this is something we should endeavor to self-nominate as soon as possible).

Nominations

If the above sounds reasonable, I propose that we begin collecting nominations for anyone who would to take the helm in this leadership capacity. We should endeavor to move this seat to an electable role by F27.


Metadata Update from @bee2502:
- Issue tagged with: internal operations, meeting

Metadata Update from @jflory7:
- Issue priority set to: urgent (1-2 weeks)
- Issue set to the milestone: Fedora 26

Metadata Update from @amsharma:
- Issue priority set to: normal (3 -4 weeks) (was: urgent (1-2 weeks))

I don't think this is something which can be achieved with quality process within 2 weeks. I have been there and did it for the first diversity adviser role selection, it took a lots of good efforts and thoughts to process applications. I suggest to reuse the already happened successful process, so that we can save some time and energy here.

Metadata Update from @amsharma:
- Issue assigned to amsharma

@amsharma What do you mean by reusing the past process ? Do you mean the selection/interview process ? How do you exactly propose we reuse it - do a community call for volunteers again ? Can you elaborate a bit more ?

Also, if it is okay with you , I would like to leave out assigning this issue to any particular Diversity team member. This is something we want as a team and will work on as a team and hence, assigning it to one person doesn't seem appropriate.

@bee2502 leaving any ticket unassigned too seems not a good thing, we need some ownership for the tasks, while we are going to have discussions on every ticket in open with everyone.

Here are some pointers to the last process (I am not sure why/how you are not aware of these) -
https://fedoramagazine.org/help-fedora-find-a-diversity-adviser/
https://fedoramagazine.org/call-for-applications-for-fedora-diversity-adviser-a-volunteer-position/
http://piratepad.net/Diversity-MOM

I can explain more in meeting.

This ticket is not about electing a new Fedora Diversity Advisor, but just a team lead for Diversity team. Since the Diversity Adviser role is currently unfilled, we need someone to help organize and drive Diversity team tasks as we are facing some organizational issues.

We aim to have a decision by next meeting.

Agree with you Bee. Let's discuss about this during our next meeting.

Metadata Update from @amsharma:
- Assignee reset

This ticket is discussed in meeting today. And team feels that we don't need to comeup with one Team lead and we can go ahead with co-ordination among team mebers.
For council meetings, we can rotate the duty between team members.

I am closing the ticket on the same notes.

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

Metadata