ACTION: commops New
members, make sure you introduce yourself on the CommOps mailing
list [ https://fedoraproject.org/wiki/CommOps/Join ](jwf,
14:31:47)
Justin W. Flory; UTC-4; CommOps, D&I,
Mindshare, Fedora Badges(jwf,
14:32:12)
algogator, bt0, and meskarune also here!(jwf,
14:37:43)
The Fedora Internationalization (i18n) Team is
testing internationalization features every day this week. See the
post for how you can get involved and help.(jwf,
14:38:44)
New thread by riecatnor about deciding new
policy for Fedora Badges used at events, to help better support
people using badges at events with their requests and the Design
Team taking on new work(jwf,
14:40:43)
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 if needed. If no status, we'll try to get a quick update
and move forward.(jwf,
14:42:22)
Metrics discussion was quick check-in on status
of GrimoireLabs + fedmsg integration. Since Grimoire is still
blocked, we drove the discussion about answering data questions now
with the tools we have available today.(jwf,
15:08:38)
Through an interactive activity, we came to two
final questions we wanted to begin exploring and felt like we could
answer with current fedmsg tools (with the help of a fedmsg
developer who happened to be in the room!).(jwf,
15:09:24)
Q1. Do we have many contributors in specific,
narrow places versus contributors working in many different areas?
If so, could we better connect the narrow places to other parts of
the community that find their input valuable? Example of connecting
a group to something like the Fedora Magazine or CommBlog.(jwf,
15:10:55)
Q2. Do we have many activities that are small
in time needed to contribute but generate high levels of activity by
drive-by contributors? Can we get more visibility of some of these
high-interest places across the wider community?(jwf,
15:12:12)
IDEA: Two main efforts
in 2019 could be to (1) answer some of the metrics questions above,
and (2) begin writing this guide for publication(jwf,
15:17:29)
ACTION: jwf Update
Pagure tickets with new comments from Flock discussion / session by
Monday, October 10(jwf,
15:18:33)
ACTION: jwf If
possible, a CommBlog article summarizing CommOps @ Flock by Monday,
October 17(jwf,
15:19:20)
HELP: Looking for help
of someone to write new documentation on Google Summer of Code
mentor / student best practices from past mentor feedback:
https://pagure.io/fedora-commops/issue/133#comment-529325(jwf,
15:24:50)
AGREED: Will keep
ticket open for one more week to look for someone interested in
leading work. Otherwise, we will close it and point to the upstream
ticket in mentored-projects(jwf,
15:25:32)