ACTION: commops New
members, make sure you introduce yourself on the CommOps mailing
list [ https://fedoraproject.org/wiki/CommOps/Join ](jflory7,
17:31:17)
Justin W. Flory; UTC+1; CommOps, Marketing,
Magazine, Diversity Team, Ambassadors, Join SIG, sysadmin-badges,
and more(jflory7,
17:31:46)
The submission window for Fedora 26 wallpapers
is now open. Contributors can submit wallpapers to be voted on for
the supplemental wallpaper package in Fedora 26.(jflory7,
17:40:44)
=== "Find Fedora at FOSDEM 2017!" ===(jflory7,
17:40:49)
This past weekend, Fedora participated with a
community stand at FOSDEM, one of the largest open source
conferences in Europe. Once we have some time, it would be helpful
to try to analyze our impact at this event, both from a statistic
point of view but also on feedback received.(jflory7,
17:41:05)
=== "Ambassadors LATAM: Year in Review"
===(jflory7,
17:41:12)
The Ambassadors of the LATAM region put
together a "Year in Review" post summarizing their past year and
identifying a few goals that they would like to continue focusing on
for 2017. You can read more on the Community Blog.(jflory7,
17:41:22)
=== Fedora 26 proposed changes close on Feb.
28th ===(jflory7,
17:41:29)
On February 28th, the window for proposed
changes to include in Fedora 26 closes. From there, we will have a
confirmed idea of what kind of new changes will be included in the
distribution. The Marketing team will work on identifying these
changes, breaking them down into talking points, and sharing them
with the project. CommOps will be able to assist by helping share
and communicate these changes with other groups in Fedora as
well.(jflory7,
17:41:35)
How This Works: We look at past #action items
from the last meeting for quick follow-up. If a task is completed,
we move on to the next one. If it isn't, we get an update and
re-action it if needed. If no status, we'll try to get a quick
update and move forward.(jflory7,
17:44:02)
=== [COMPLETE] jflory7 Work with Rhea on adding
her as a subreddit mod (due:2017-01-25) ===(jflory7,
17:44:08)
=== [COMPLETE] dhanesh95 Put a call out on the
devel mailing list asking for any Fedorans speaking at FOSDEM to
please check if their name is added to our list so that they are
covered in a later post on the Fedora Magazine (due: 2017-01-26/27)
===(jflory7,
17:44:29)
=== [COMPLETE] jflory7 Write article
introducing Fedora speakers at FOSDEM on Tue., Jan. 31, publish on
Wednesday or Thursday before FOSDEM (due: 2017-01-31) ===(jflory7,
17:44:38)
=== [COMPLETE] dhanesh95 File a new ticket in
the FESCo Trac/Pagure requesting more information to the wiki page
about their responsibilities and common tasks (bullet points are
great, but if they have time, longer descriptions would help too)
(due: 2017-01-29) ===(jflory7,
17:44:49)
=== [COMPLETE] cprofitt Work on pulling
feedback and ideas mentioned in Ticket #90 into smaller, more
achievable items, either as bullets in a ticket comment on #90 or as
new tickets (due: 2017-01-31) ===(jflory7,
17:44:59)
Past and current "election wranglers" of Fedora
identified that the nomination process sometimes faces issues. The
biggest problem was consistently communicating with the public and
also nominees. The public should know with enough time to cast
nominations for positions up for election. After, nominees receive
updates about the campaign process. This has always been done
manually.(jflory7,
17:50:37)
Additionally, another issue is finding out what
teams wish to hold elections. Normally it is consistent, but
sometimes, edge cases happen where a team that doesn't normally hold
elections decides to hold them. This happened recently with the
Fedora Ambassador Steering Committee holding their elections.(jflory7,
17:51:26)
IDEA: Filing upstream
tickets for long-term improvement to the voting application to
handle (1) nominations, and (2) questionnaire submissions(jflory7,
17:56:01)
IDEA: Maintaining the
communication bar we set for the last election: CommBlog / Magazine
posts, announcement mailing list posts for nomination and voting
process(jflory7,
18:06:28)
IDEA: Short-term,
trying to better communicate questionnaire as resource for people to
edit / add to for nominees to answer(jflory7,
18:06:54)
ACTION: jflory7 File
feature tickets in Election app for (1) nomination of candidates,
and (2) questionnaire question interaction (e.g. submitting new
questions)(jflory7,
18:10:45)
Voter participation has been a key focus point
of Fedora elections. In the past, we struggled to have significant
participation but it has gradually improved (with the last cycle
reaching the second highest record of voter participation for some
groups). For the past couple of election cycles, we have tried using
some of the following methods to better engage the voting
community:(jflory7,
18:14:31)
(1) Community Blog posts for candidate
interviews leading up to the election(jflory7,
18:14:52)
(2) Posts on the announce mailing list at the
start of the voting period, but also close to the end(jflory7,
18:15:08)
(3) Using social media to promote the election
window being open(jflory7,
18:15:20)
Some of the new ideas we have had to improve
voter participation are…(jflory7,
18:15:40)
(1) A single, general post on the Fedora
Magazine announcing the elections(jflory7,
18:16:05)
(2) Having a badge for voters to receive at the
end of the voting period (while keeping in mind potential privacy
issues that could arise from such a badge)(jflory7,
18:16:32)
(3) Having nominee AMAs (Ask Me Anything) hours
on the Fedora subreddit, /r/Fedora (or maybe another social media
platform of a candidate's choice)(jflory7,
18:17:06)
(4) Finding ways to build automated reports of
candidates for positions while keeping it general and fair to
participants - this idea should be approached with caution(jflory7,
18:17:40)
IDEA: Running data
analysis on past election participation data would be helpful to
understand our impact (cc: bee2502?)(jflory7,
18:25:05)
IDEA: Seriously
investigate the idea of having a badge for voter participation
(consider security concerns!)(jflory7,
18:27:28)
IDEA: Holding AMA on
IRC (a la freenode AMA style) and syncing traffic in IRC channels to
Telegram to promote participation and awareness of the election
process (needs discussion with jkurik)(jflory7,
18:28:13)
ACTION: jflory7
Summarize this discussion into the ticket, try to get opinion of
jkurik (and also bee2502 for metrics) in the ticket(jflory7,
18:29:11)
How This Works: There is a quick blast of
information about what was published in the past week with some
metrics, followed by posts that are being drafted. After the
information blast, the floor is opened for any Community
Blog-related discussion. Here we go!(jflory7,
18:31:06)
commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ]
jflory7 File feature tickets in Election app for (1) nomination of candidates, and (2) questionnaire question interaction (e.g. submitting new questions)
jflory7 Summarize this discussion into the ticket, try to get opinion of jkurik (and also bee2502 for metrics) in the ticket
Action items, by person
commops
commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ]
jflory7
jflory7 File feature tickets in Election app for (1) nomination of candidates, and (2) questionnaire question interaction (e.g. submitting new questions)
jflory7 Summarize this discussion into the ticket, try to get opinion of jkurik (and also bee2502 for metrics) in the ticket