Hi all! Today’s meeting happened earlier today. We split the discussion between two tickets: the WordCloudBot ticket and the Fedora Docs contribute-athon ticket. We walked through some first steps for how to move forward and assigned some action items to get momentum going.

Details and minutes are below. Thanks everyone who came out and participated today.

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:12:06)

Next steps: Need to find a willing volunteer to play with Python and
fedmsg. Some coding background is helpful, but it should not be
complex. If no volunteers in the meeting, let’s find a way to make
this task more visible in the Fedora community. Discourse? CommBlog?
Reddit…? We can be creative. (jwf, 17:15:10)

IDEA: Write up a CommBlog article (like a “CommOps winter 2018
easyfix newsletter”) and try sharing that more widely on social
media or user communities (jwf, 17:19:02)

Next steps: Identify barriers to contributing to docs as of today.
Start generating a list of pain points. How can CommOps help smooth
some of this points and make it easier for a first-time contributor
to land their contribution without too much fuss? Start here as our
base. (jwf, 17:25:58)