fedora-commops

Community Operations, a.k.a. CommOps, addresss community infrastructure by providing tools, resources, and utilities for different sub-projects to improve communication across Fedora  |  https://fedoraproject.org/wiki/CommOps

#107 Automated Fedocal reminders to send to all mailing lists for upcoming Elections

Created a year ago by bee2502
Modified 4 months ago

In CommOps issue #19 it was mentioned that some work could be done to help improve communication about the entire Elections process, from nominations to interviews to voting. One immediate way we could do this is by having Automated Fedocal reminders to send to mailing lists for Elections

Timeline for the reminders

  • One week before the nomination period begins
  • Start of Nomination Period
  • 24 hours before end of Nomination Period
  • End of Nomination Period and start of Campaign Period
  • 24 hours before end of Campaign Period
  • End of Campaign period and start of Voting Period
  • 24 hours before end of Voting Period
  • End of Voting Period (with details on the dates when results will be announced)
  • One week after voting period [thanking community for participating]

The messages for all the reminders should also have appropriate links to Election pages for community to check out information. Also, messages during Campaign and Voting Period should have a note asking community to check out candidate interviews on Community Blog.

The message one week before start of Elections should inform that next Fedora election is about to start and that detailed information about number of seats for election will be sent by Fedora Election Manager soon.

a year ago

Metadata Update from @bee2502:
- Issue priority set to: minor (3-4 weeks)
- Issue set to the milestone: Future releases
- Issue tagged with: easyfix, elections

a year ago

Metadata Update from @bee2502:
- Issue set to the milestone: Fedora 26 (was: Future releases)

@jkurik Would love your feedback on this. If this is a +1, we can work on this for the upcoming elections.

a year ago

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

a year ago

Metadata Update from @bee2502:
- Issue tagged with: blocked

a year ago

Metadata Update from @bee2502:
- Issue untagged with: blocked

Hi guys!
I was reading fedocal source code, cool project :)
I know this issue is waiting some feedback first but I'm available for help.
@bee2502 are there any mailing templates regarding the election process and such? is there any process in order to create the reminders in fedocal? (maybe we could design a new specific interface to integrate election events with fedocal :D)
Tks

Can we get some details on which mailing lists are being proposed here? The title implies it will be all Fedora mailing lists which is a non-starter for me as I don't want so many copies of the same email.

a year ago

Metadata Update from @bex:
- Issue set to the milestone: None (was: Fedora 26)

a year ago

Metadata Update from @jflory7:
- Issue set to the milestone: Fedora 26 (to June 2017)

@bex Ideally, this should be the most relevant mailing lists. For all election communication or inter-project communication, the logistics mailing list serves this purpose. However, for specific elections, I would suggest these lists:

  • Fedora Council:
    • announce
    • announce-devel
    • council-discuss
  • FAmSCo:
    • ambassadors
    • announce
    • announce-devel
  • FESCo:
    • announce
    • announce-devel
    • devel
    • Maybe a FESCo list? Not sure if this exists or if it's public or not?
10 months ago

Metadata Update from @bee2502:
- Issue tagged with: meeting

I am +1 to these lists.

We need feedback from @jkurik before we go ahead on setting automated reminders in Fedocal.

Edited 10 months ago by bee2502

This could also be a task for anyone interested in coding and CommOps to integrate this functionality in Elections app.

10 months ago

Metadata Update from @bee2502:
- Issue untagged with: easyfix
- Issue tagged with: help wanted

10 months ago

Metadata Update from @bee2502:
- Issue set to the milestone: Fedora 27 (to Nov. 2017) (was: Fedora 26 (to June 2017))

I am OK with @jflory7 's proposal with one exception. I would avoid the announce@ mailing list for most of the events described above and use it just for result announcement.

I would also like to mention that the flow of the Election periods has changed. See https://pagure.io/Fedora-Council/tickets/issue/135#comment-467523 for more information.

Discussed in 2017-10-30 meeting.

Setting up Fedocal announcements

@x3mboy volunteered to create new Fedocal events for this upcoming election during the meeting. These events can be created in the CommOps calendar and sent to the mailing lists discussed above. Also note the updated election cycle per @jkurik's comment above.

@x3mboy will close this ticket once he adds the events to Fedocal. This is due for completion by our next meeting on Monday, Nov. 6th.

10 months ago

Metadata Update from @jflory7:
- Issue untagged with: help wanted, meeting, needs feedback
- Issue assigned to x3mboy
- Issue priority set to: critical (next week) (was: minor (3-4 weeks))

I can't update the Elections calendar:

You are not one of the editors of this calendar, or one of its admins, you are not allowed to add new meetings.

Can I set this in the CommOps Calendar?

@x3mboy and I discussed this in IRC, and with the help of Fedora Infrastructure team, the CommOps FAS group now has admin privileges on the Elections calendar.

Fedocal is ready for next elections :D

5 months ago

Metadata Update from @jflory7:
- Issue priority set to: no deadline (was: critical (next week))
- Issue set to the milestone: Future releases (was: Fedora 27 (to Nov. 2017))

Policy changes were made to the elections in January 2018. #118 is now closed and complete, now that our team documentation better explains our role and engagement with the election process.

Since @x3mboy set up the calendar notifications for the last election towards the end of 2017, I am closing this ticket as complete. We can start fresh with new work for the elections at the start of the next cycle.

4 months ago

Metadata Update from @jflory7:
- Issue close_status updated to: Complete
- Issue set to the milestone: Fedora 27 (to Nov. 2017) (was: Future releases)
- Issue status updated to: Closed (was: Open)

Login to comment on this ticket.