#123 Fedora Diversity and Inclusion Advisor Elections 2020
Closed: complete 4 years ago by jflory7. Opened 5 years ago by amsharma.

Objective

Execute elections for Fedora Diversity and Inclusion Advisor Elections 2020. Thanks to @jonatoni who helped us do it till date. According to the process defined, we should be running these elections after every 2 Fedora release cycles but unfortunately, that did not happen as we all got busy. Better late than never, @bcotton can help us do it now.

Process

  • Get the team on-boarded for this by our next D&I meeting. We have +1s from members in ticket 89
  • Open new ticket to gather nominations for the seat. That will remain open for 2 weeks.
  • Send @bcotton mail with nominations and other info required.

Goal

To be regular with the process in future. It will be easier to do it if we get the experience now.


Metadata Update from @amsharma:
- Issue assigned to amsharma

5 years ago

Metadata Update from @amsharma:
- Issue priority set to: next meeting (was: awaiting triage)
- Issue tagged with: type - internal organization

5 years ago

Metadata Update from @jflory7:
- Issue tagged with: new change

5 years ago

If everyone in team is sync (As we got +1s in ticket#89), I would like to start the nomination gathering process. WDYT
@tatica @jonatoni @jflory7 @nikhilkathole @riecatnor

@amsharma That's why I assumed we opened the ticket :wink: Probably best to do a post to the mailing list and ping in #fedora-diversity. I don't think a CommBlog post is necessary, at least not since we are already on this.

Thanks for responses everyone. Here - https://docs.google.com/document/d/1kD14f5GkNshHpzE9ckgPmffk_evHE9TD_i7pQ52R30s/edit?usp=sharing is the draft post (short and precise ) which can be posted everywhere (ML, IRC, telegram) and any other channels , we would like to. Please check and revert. Last date for the feedback on post is 13th March, 2020. Thanks.
@tatica @jonatoni @jflory7 @nikhilkathole @riecatnor

Content of document

Today we are starting the Nomination & Campaign period during which we
accept nominations for Fedora D&I team representative.

This period is open until 2020-03-31 at 23:59:59 UTC.

Candidates may self-nominate. If you nominate someone else, please
check with them to ensure that they are willing to be nominated before
submitting their name.

Nominees submit their questionnaire answers via commenting on this
Pagure issue.

Please note that the interview is mandatory for all nominees. Nominees
not having their interview ready by end of the nomination period
(2020-03-31) will be disqualified and removed from the election.

As part of the election people may also ask questions to specific
candidates on the Pagure issue.

For more information about the elections process, roles and responsibilities
of the D&I team representative, please check this document.

Interview Questions:
What is your background in Fedora? What have you worked on and what are you doing now?
What are your future plans? Is there anything you can consider a "Fedora D&I Statement" as a candidate?
Please elaborate on the personal "Why" which motivates you to be a candidate for D&I.

Schedule
All the periods below start at (00:00:00UTC and end at 23:59:59UTC).
17 March – 31 March, 2020 - Nomination Period along with interview
31 March – 15 April, 2020 - Voting Period
16 April - 23 April, 2020 - Final evaluation by D&I team members
30 April, 2020 : Result Announcement

Thanks a lot for working on this Amita :blue_heart: I already gave my feedback on the document. :)

Thanks @amsharma. I left feedback on the doc too.

Great feedback @jflory7 and @jonatoni
I fixed the content according to the feedback. There are 2 pending questions on doc. Please have a look and help me resolve them. Thanks.

@bcotton do you want to check this out once from election process prospective and share your feedback please? - https://docs.google.com/document/d/1kD14f5GkNshHpzE9ckgPmffk_evHE9TD_i7pQ52R30s/edit?usp=sharing

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

5 years ago

Comments/responses provided in the doc

Thanks @bcotton

Now this seems to be good - https://docs.google.com/document/d/1kD14f5GkNshHpzE9ckgPmffk_evHE9TD_i7pQ52R30s/edit# :smile:

If no more comments or correction required. Let's put this in our docs?
@jflory7 can you please help me do that? Thanks.

I would like to suspend this work as of now. I suspect a very low participation because of the current unfortunate situation (COVID-19).

I will revisit this once the situation will be little better. Thanks.

Hi all! I would like to give some input here.

I have spoken to @amsharma @jonatoni @bee2502 @jflory7 about the D&I team at different points in the last year or so. There have been some issues with burnout and sustainability. I have been made aware that the team has a desire to pick things back up in a focused, strategic way to address those specific points. I think this is amazing, and I am here to support those efforts!!

Based on the fact that the team is currently at such a small size I propose that D&I drops this level of process for appointing an advisor/team lead. If, and when, the team reaches the size where it makes sense, that would be the time to implement. This is a unique case of scaling early ;)

Based on a conversation with @jflory7, I would like to nominate Justin as the adviser for the next release cycle. He has indicated he has the drive and cycles to help bring the team and the work/projects that are in place to a better place. I would ask that people add a +1 to the ticket if they agree.

+1. This would be for the F33 release cycle, so until about November 2020.

A massive +1 from my side.

+1 :100: :100:

+1 for @jflory7 to be the next adviser for the next Fedora release cycle.
Thanks a lot @jflory7 for taking up the responsibility during this difficult times. All the very best :)

We have 5 (+1) votes, so this ticket is approved :tada:

We just need to announce it on ML and update docs (D&I team and Council) - @jflory7 can you do that? :smile:

@bcotton can you please replace me with @jflory7 on Council? :pray:

Metadata Update from @jonatoni:
- Issue assigned to jflory7 (was: amsharma)

4 years ago

Metadata Update from @jflory7:
- Issue untagged with: needs feedback
- Issue priority set to: waiting on assignee (was: next meeting)

4 years ago

The Council logistics for this are done. I also made some minor changes to the Diversity Advisor page on the Council docs site.

I am closing this ticket as complete. Thanks again for your years of service as our Advisor, @jonatoni! :heart: :100: :heart:

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

4 years ago

Log in to comment on this ticket.

Metadata