ACTION: commops New
members, please introduce yourself on the CommOps Discourse [
https://discussion.fedoraproject.org/c/project/commops ](jwf,
17:01:12)
Justin W. Flory; UTC-5; CommOps, Diversity and
Inclusion Team, Fedora Badges(jwf,
17:01:28)
Alberto Rodriguez S; UTC-6;CommOps, Marketing,
Fedora-join, dotnet and more(bt0,
17:02:27)
John M. Harris, Jr.; UTC-5; CommOps (member),
Games (member), 3D Printing (member)(JohnMH,
17:05:54)
Find candidate interviews on the Community Blog
or linked from the voting app. Be sure to get your votes in before
the polls close on Thursday, Dec. 20th.(jwf,
17:06:09)
=== "Fedora's Strategic Direction: An Update
from the Council" ===(jwf,
17:06:24)
mattdm shares a vision of the future, as
discussed last week at the Fedora Council hackfest. The Council is
looking for feedback on the proposal.(jwf,
17:06:24)
You didn't even have to guess – bcotton has the
inside scoop of Fedora development in this week's report. Note the
major Red Hat Bugzilla upgrade and the cassandra package maintainers
looking for help.(jwf,
17:06:38)
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,
17:09:07)
=== [INCOMPLETE] "jwf Draft set of user testing
scenarios for contributing to docs, create new tickets for each test
scenario. Due: before 2019." ===(jwf,
17:09:19)
ACTION: jwf Draft set
of user testing scenarios for contributing to docs, create new
tickets for each test scenario, ask for Design Team feedback. Due:
before 2019(jwf,
17:09:25)
Note: Another action item to request Design
Team feedback is part of the required follow-up for this to be
complete. It is now included in this action item.(jwf,
17:09:25)
=== [COMPLETE] "jwf Start new Discourse thread
about the Dilemma of the Conflicting Meetings" ===(jwf,
17:09:31)
Choosing a new time for meetings in 2019.
Please review the suggested options and let us know your preference
if one time works better than another for you to join.(jwf,
17:09:39)
=== [INCOMPLETE] "jwf File new tickets to
discuss / plan out ideas from 2018-12-04 meeting further" ===(jwf,
17:09:49)
HELP: If some folks are
willing to help with this, it would help to distribute the ticket
filing. And then jwf doesn't have to re-explain the original ideas
that came from others last week. (this is on the agenda for tickets
— we will revisit soon!)(jwf,
17:09:58)
ACTION: bpabon Create
a flowchart based on 2018-12-04 meeting discussion (around
conventions / expectations for filing a CommOps ticket), ready for
review by Wed, Dec. 19th(jwf,
17:11:31)
=== [PARTIALLY COMPLETE] "jwf Post Discourse
summary / do ticket updates from meeting this week" ===(jwf,
17:11:38)
Next steps: This ticket is currently too big,
now that we had a chance to talk it through. We had several great
ideas from last week's meeting about how to divide this up. Let's
try to come up with how we want to break this up and file new
tickets for these ideas.(jwf,
17:12:26)
IDEA: Creating
“cheatsheet” of common Fedora tools, applications, and resources
used across project(jwf,
17:14:55)
IDEA: Find way to
better document group contacts for different SIGs /
sub-projects(jwf,
17:15:03)
IDEA: Curate list of
recurring “easyfix” tasks for CommOps(jwf,
17:15:11)
IDEA: Write a "Fedora
jargon cheatsheet"(jwf,
17:15:19)
IDEA: "Game-ifying" a
docs event, possibly having teams to compete for different goals
(e.g. "edit X number of pages", "create X number of new pages",
etc.)(jwf,
17:16:16)
IDEA: Offering prizes
for different categories, e.g. UnixStickers swag, gift cards,
etc.(jwf,
17:18:46)
ACTION: jwf File a
new ticket to better document and offer up recurring "easyfix" tasks
for CommOps by Wed, Dec. 19th(jwf,
17:29:17)
ACTION: bt0 File a
new ticket to create a "Fedora jargon" cheatsheet, to help explain
different terms and phrases often used in Fedora (but not obvious to
a newcomer or first-timer) by Wed, Dec. 19th(jwf,
17:30:34)
ACTION: JohnMH Fix
dead links in README of the fedora-commops repo by Wed, Dec.
19th(JohnMH,
17:31:03)
ACTION: bpabon File a
new ticket to better document procedure and best practices on
cross-team communication and collaboration by Wed, Dec. 19th (and
maybe add the flowchart from previous action there once it is
ready!)(jwf,
17:32:59)
ACTION: meskarune
File a new ticket for a "cheatsheet" to explain different Fedora
tools, apps, and resources and how they are used, by Wed, Dec.
19th(jwf,
17:37:04)
ACTION: meskarune
File a new ticket for brainstorming docs event "competition"
categories and possible prizes to go with them, by Wed, Dec.
19th(jwf,
17:37:33)
IDEA: Using Badges to
correspond with some of the competition categories? (e.g. "Most docs
edited in 2019 contribute-athon event", "Most new pages created in
2019 contribute-athon event", etc.)(jwf,
17:39:06)
IDEA: Using page views
/ metrics as an incentive for a "highest visibility" fix
category?(jwf,
17:42:34)
commops New members, please introduce yourself on the CommOps Discourse [ https://discussion.fedoraproject.org/c/project/commops ]
jwf Draft set of user testing scenarios for contributing to docs, create new tickets for each test scenario, ask for Design Team feedback. Due: before 2019
bpabon Create a flowchart based on 2018-12-04 meeting discussion (around conventions / expectations for filing a CommOps ticket), ready for review by Wed, Dec. 19th
jwf File a new ticket to better document and offer up recurring "easyfix" tasks for CommOps by Wed, Dec. 19th
bt0 File a new ticket to create a "Fedora jargon" cheatsheet, to help explain different terms and phrases often used in Fedora (but not obvious to a newcomer or first-timer) by Wed, Dec. 19th
JohnMH Fix dead links in README of the fedora-commops repo by Wed, Dec. 19th
bpabon File a new ticket to better document procedure and best practices on cross-team communication and collaboration by Wed, Dec. 19th (and maybe add the flowchart from previous action there once it is ready!)
meskarune File a new ticket for a "cheatsheet" to explain different Fedora tools, apps, and resources and how they are used, by Wed, Dec. 19th
meskarune File a new ticket for brainstorming docs event "competition" categories and possible prizes to go with them, by Wed, Dec. 19th
Action items, by person
bpabon
bpabon Create a flowchart based on 2018-12-04 meeting discussion (around conventions / expectations for filing a CommOps ticket), ready for review by Wed, Dec. 19th
bpabon File a new ticket to better document procedure and best practices on cross-team communication and collaboration by Wed, Dec. 19th (and maybe add the flowchart from previous action there once it is ready!)
bt0
bt0 File a new ticket to create a "Fedora jargon" cheatsheet, to help explain different terms and phrases often used in Fedora (but not obvious to a newcomer or first-timer) by Wed, Dec. 19th
commops
commops New members, please introduce yourself on the CommOps Discourse [ https://discussion.fedoraproject.org/c/project/commops ]
JohnMH Fix dead links in README of the fedora-commops repo by Wed, Dec. 19th
JohnMH
JohnMH Fix dead links in README of the fedora-commops repo by Wed, Dec. 19th
jwf
jwf Draft set of user testing scenarios for contributing to docs, create new tickets for each test scenario, ask for Design Team feedback. Due: before 2019
jwf File a new ticket to better document and offer up recurring "easyfix" tasks for CommOps by Wed, Dec. 19th
meskarune
meskarune File a new ticket for a "cheatsheet" to explain different Fedora tools, apps, and resources and how they are used, by Wed, Dec. 19th
meskarune File a new ticket for brainstorming docs event "competition" categories and possible prizes to go with them, by Wed, Dec. 19th