#2012 Election Interview Questions — FESCo (Dec 2018)
Closed: Accepted 7 months ago Opened 7 months ago by bcotton.

In order to move forward with the next election, we need to determine which three mandatory questions the FESCo would like to have asked.

The end result is that we need the FESCo to please identify the three questions before November 14, 2018 so we can properly communicate them to candidates and so they enough time to answer them.

The link to your current questionnaire is here:

https://fedoraproject.org/wiki/Elections/Questionnaire#FESCo_.28Engineering.29

In case the selection will not be done till November 14, then Election wrangler will use the same set of questions as the last election cycle (see FESCo ticket 1891).


I still think the questions we used the last two times are good - they are nice and general so they can have a wide variety of answers. I'd classify them as "timeless":

https://pagure.io/fesco/issue/1805#comment-484891

Agreed with bowlofeggs.

+1 to reusing the questions from last time.

For the next cycle, we could consider asking on fedora-devel for a new set, but we would need to do this two-three weeks before the deadline, to allow for enough discussion.

I'll proceed with the previous questions (included below for reference). I agree that starting the question process sooner makes sense. I'll adjust the F30 schedule accordingly.

  • Describe some of the important technical issues you foresee affecting the Fedora community. What insight do you bring to these issues?
  • What objectives or goals should FESCo focus on to help keep Fedora on the cutting edge of open source development?
  • What are the areas of the distribution and our processes that, in your opinion, need improvement the most? Do you have any ideas how FESCo would be able to help in those "trouble spots"?

+1 for the previous questions for the record.

+1 to reusing the last ones at this point...

I will mark this closed. I count +5 for reusing the last questions.

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

7 months ago

Login to comment on this ticket.

Metadata