ACTION: commops New
members, make sure you introduce yourself on the CommOps mailing
list [ https://fedoraproject.org/wiki/CommOps/Join ](jflory7,
16:31:15)
Justin W. Flory; UTC-4; CommOps, Magazine,
Marketing, Ambassadors, Diversity Team, sysadmin-badges, and
more(jflory7,
16:31:36)
Alberto Rodriguez; UTC-5;Commops,Stats,
Education, and more(bt0,
16:32:11)
mailga; timezone Europe/Rome; mktg/ambassadors
and some others(mailga,
16:32:47)
FUDCon LATAM ended last week. Fedora
contributors from all around the globe flocked to Puno, Perú for
speaker talks, workshops, and collaboration to advance Fedora and
its Four Foundations. You can read more in the Community Blog post,
and there should be event reports popping up soon.(jflory7,
16:39:26)
Fedora 25 supplementary wallpaper elections are
open! If you are CLA+1 in the Fedora Account System, you can
participate in the election and vote for your favorite wallpapers to
be included in the upcoming Fedora 25 release.(jflory7,
16:39:43)
=== In the news: "Fedora 25 Beta Resets the
Linux Performance Bar" ===(jflory7,
16:39:58)
LinuxInsider covers some of the latest features
and changes in the Fedora 25 Beta, and includes comments and a brief
interview from mattdm. This article highlights many of the talking
points generated in the past few weeks. It's clear they're making it
easy for everyone to talk about what's new in Fedora 25!(jflory7,
16:40:13)
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,
16:44:27)
=== [COMPLETE] jflory7 Promote Outreachy
article on social media channels for final week of applications
===(jflory7,
16:44:34)
=== skamath Follow up with Infrastructure team
on fas=>bz email lookup rules and whether a fix can be made to
gracefully handle failed lookups ===(jflory7,
16:44:42)
skamath not present, will follow up next
week(jflory7,
16:45:03)
ACTION: skamath
Follow up with Infrastructure team on fas=>bz email lookup rules
and whether a fix can be made to gracefully handle failed
lookups(jflory7,
16:45:11)
=== [INCOMPLETE] jflory7 File ticket for
looking into centralizing / making more clear what a member of
Council or FESCo does, what their responsibilities are, and
centralize the info in a wiki page or CommBlog article ===(jflory7,
16:45:21)
ACTION: jflory7 File
ticket for looking into centralizing / making more clear what a
member of Council or FESCo does, what their responsibilities are,
and centralize the info in a wiki page or CommBlog article(jflory7,
16:45:33)
ACTION: jflory7 Reach
out to skamath about Infrastructure / Bugzilla+FAS lookup
rules(jflory7,
16:46:06)
=== [INCOMPLETE] jflory7 Begin drafting a
Community Blog post for Fedora Appreciation Day ===(jflory7,
16:46:17)
ACTION: jflory7 Begin
drafting a Community Blog post for Fedora Appreciation Day(jflory7,
16:46:25)
=== [INCOMPLETE] jflory7 Post to the mailing
list about selecting a new sub-project to work with on the
on-boarding process ===(jflory7,
16:46:31)
ACTION: jflory7 Post
to the mailing list about selecting a new sub-project to work with
on the on-boarding process(jflory7,
16:46:37)
=== [INCOMPLETE] jflory7 Open up discussion
about Fedora Appreciation Day date on the mailing list ===(jflory7,
16:46:44)
ACTION: jflory7 Open
up discussion about Fedora Appreciation Day date on the mailing
list(jflory7,
16:46:50)
=== [COMPLETE] jflory7 Create initial wiki page
for EDU talking points, share in ticket ===(jflory7,
16:46:58)
=== Problems / issues within Marketing
===(jflory7,
16:59:00)
IDEA: It is unclear
what kind of tasks Marketing is working on during a release cycle
and how to participate. They are not clearly defined in many places
(and some places that have info are outdated).(jflory7,
16:59:32)
IDEA: The tasks that
are highly visible can be intimidating to a new contributor (e.g.
contributing to the release announcement or creating talking points
for editions and spins of Fedora, which requires a lot of cross-list
communication and knowledge of where to go to find people in
Fedora).(jflory7,
17:00:20)
IDEA: Many of the types
of contributors in marketing come by in cycles. Some people will
contribute for one, maybe two releases, and then they might drop
off. Retainment is an issue, both with membership and
leadership.(jflory7,
17:01:15)
IDEA: The actual
on-boarding steps are simple and don't provide much of a chance for
engagement. The on-boarding steps have someone introduce themselves
on the mailing list, say hello in a meeting, and then that's it. It
would be helpful to have more opportunities to engage new members
with "easyfix" types of tasks. Or low-hanging fruit, whichever you
prefer.(jflory7,
17:02:51)
IDEA: Because of the
difficulty of engaging new members, it's difficult for Marketing to
focus on non-essential tasks other than release announcements and
talking points. If there were more communication about to contribute
ideas, marketing could push to be more innovative to work with
different media or campaigns to engage with new waves of
users.(jflory7,
17:03:47)
=== Brainstorming ways to help resolve these
problems ===(jflory7,
17:05:02)
IDEA: Working more
closely with other groups like Join SIG to engage newcomers in
Marketing with other areas in the project to see if there are other
areas they might be interested in (community, development,
etc.)(jflory7,
17:24:42)
IDEA: Each subproject
could have a month to highlight awesome things they do (meskarune) -
example tasks could be reaching out to project leads to gather those
points and write an article(jflory7,
17:25:12)
IDEA: Improvements to
the on-boarding process beyond an introduction on the mailing list
and meeting(jflory7,
17:27:31)
IDEA: Better
communicating existing contacts in media and how to convey Fedora
news to them in a professional but curt way (as a newcomer or
intermediate task??)(jflory7,
17:28:33)
IDEA: Better ways to
communicate our social media presence to engage newcomers to then
engage with us on social platforms?(jflory7,
17:31:18)
IDEA: Breaking down the
"Tasks and roles" wiki page into better communicated roles and
smaller tasks (low-hanging fruit) to engage new contributors(jflory7,
17:32:17)
IDEA: "How I use
Fedora" talking points / articles... make them into videos,
interviews, footage, example work that people could share on their
channels or platforms(jflory7,
17:35:18)
IDEA: Eventually create
a badge for members of the FAS group(jflory7,
17:36:11)
IDEA: Podcasting as a
maybe lower barrier way of doing things like interviews (see: Chris
Ward's interviews with Fedora contributors on SoundCloud)(jflory7,
17:41:35)
ACTION: jflory7 Take
the discussion points from today's meeting, lay out the earlier
problems, expand on solutions, and try to offer mock implementations
in the Marketing ticket(jflory7,
17:42:34)
Out of time for covering more tickets, but
today's discussion was deep and for the longer-term analysis for
growth and retainment strategies of the Marketing sub-project(jflory7,
17:46:26)
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,
17:46:53)
commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ]
skamath Follow up with Infrastructure team on fas=>bz email lookup rules and whether a fix can be made to gracefully handle failed lookups
jflory7 File ticket for looking into centralizing / making more clear what a member of Council or FESCo does, what their responsibilities are, and centralize the info in a wiki page or CommBlog article
jflory7 Reach out to skamath about Infrastructure / Bugzilla+FAS lookup rules
jflory7 Begin drafting a Community Blog post for Fedora Appreciation Day
jflory7 Post to the mailing list about selecting a new sub-project to work with on the on-boarding process
jflory7 Open up discussion about Fedora Appreciation Day date on the mailing list
jflory7 Take the discussion points from today's meeting, lay out the earlier problems, expand on solutions, and try to offer mock implementations in the Marketing ticket
jflory7 Process and review pending Community Blog articles for publishing
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 ticket for looking into centralizing / making more clear what a member of Council or FESCo does, what their responsibilities are, and centralize the info in a wiki page or CommBlog article
jflory7 Reach out to skamath about Infrastructure / Bugzilla+FAS lookup rules
jflory7 Begin drafting a Community Blog post for Fedora Appreciation Day
jflory7 Post to the mailing list about selecting a new sub-project to work with on the on-boarding process
jflory7 Open up discussion about Fedora Appreciation Day date on the mailing list
jflory7 Take the discussion points from today's meeting, lay out the earlier problems, expand on solutions, and try to offer mock implementations in the Marketing ticket
jflory7 Process and review pending Community Blog articles for publishing
skamath
skamath Follow up with Infrastructure team on fas=>bz email lookup rules and whether a fix can be made to gracefully handle failed lookups
jflory7 Reach out to skamath about Infrastructure / Bugzilla+FAS lookup rules