In today’s meeting, CommOps discussed three goals we want to accomplish and focus our efforts on in the Fedora 30 release cycle. We want wider feedback and opinions on some of these ideas – feel free to leave any thoughts or opinions here in this thread.
Since Fedora Appreciation Week recently came to an end, we finished our biggest undertaking since we held our in-person 2018 team sprint. Now, we wanted to figure out what undertakings we wanted to explore next. The hope is to have one code / metrics ticket and one non-code ticket.
Non-code: Virtual Fedora Docs contribute-athon
We want to move forward with our plans to organize a virtual Fedora Docs contribute-athon focused on the quick-docs. These quick docs are topic-based documentation for doing specific tasks or things in Fedora. We want to engage active user communities as much as possible, to give experienced users a chance to share some of their knowledge into official project documentation. The subtle goal here is to try and have better documentation to help user’s needs, and one of the best people to ask what user’s needs are is to get the people who are answering questions and helping users solve problems in support groups.
Next steps for this include coming up with a structure and looking at on-boarding resources. Most of the planning for this will likely focus on lowering the barrier to contribution as low as possible.
@x3mboy volunteered to help lead on this task, with support of the CommOps team.
Code: Run a word-cloud bot on Twitter
Based off of fedora-commops#186.
An older CommOps project, wordcloudbot, takes Fedora meeting minutes, generates a word cloud from most-used words in a meeting, and automatically posts the results to a Twitter account. It would be cool to get this working again and set up on the
@fedoracommunity Twitter account.
Next steps likely include a revisit to the original code (some modernization might be needed), testing it out with existing Fedora meetings locally, and then getting it running on a server so the tweets happen automatically.
We’ll begin exploring this at the next CommOps meeting. Maybe @siddharthvipul, Sumantro, or Anna could help get this added to GCI 2018.
Finding a way forward: WordPress fedmsg metrics
Based off of fedora-commops#108.
@dhanesh95 raised this topic in the meeting. This is currently our oldest ticket. @kevin left helpful feedback two months ago that needs more consideration before we move forward. For Fedora 30, we didn’t think we could accomplish this completely, but we agreed to narrow our options and make a commitment to a single option by the end of the release cycle.
Personally, the OpenShift idea mentioned by @kevin in the ticket was interesting to me.
We’ll also revisit this one at the next meeting.
We wanted to post this thread on Discourse to get feedback from other team members who couldn’t make the meeting as well as anyone else in the wider Fedora community. This is what we are thinking of working on for the next six to seven months until May 2019, when Fedora 30 releases.