The Fedora Council stuck around Brno the day after DevConf.CZ to have a day-long working session. This is part of our newly-adopted regular cadence of in-person meetings. We mostly used this day to follow up on some items from the November meeting, including the vision statement.
Continue readingHere’s your report of what has happened in Fedora this week. The Beta Freeze is underway.
I have weekly office hours in #fedora-meeting-1. Drop by if you have any questions or comments about the schedule, Changes, elections, or anything else.
Continue readingIf you’ve attended a Release Readiness Meeting in the last few years, you’ve noticed that there’s a lot of me asking for an update from a team and getting no response. This makes the meeting a lot less valuable for the project and for the people who attend. And because the Release Readiness Meeting is held after the first Go/No-Go meeting, there’s not much chance to fix unready issues. Let’s make this better.
Continue readingThis is part two of a four-part series recapping the Fedora Council’s face-to-face meeting in November 2019.
In addition to the big topic of the Fedora Project Vision, we used the opportunity to cover some other Fedora Council business. Because it’s a lot, we’re breaking the reporting on this into two posts, kind of arbitrarily — here’s the first of those.
Continue readingToday is Day 4 of Fedora Appreciation Week. To help celebrate the Fedora Project, our fifteen-year anniversary, and the community of people that make Fedora what it is, the Community Operations team collected Contributor Stories from the community to feature here every day of Appreciation Week.
Have someone you want to thank? Do you want to share your appreciation with Fedora? See how you can celebrate 15 years of Fedora and participate in Fedora Appreciation Week over on the Fedora Magazine.
Today’s Contributor Stories come from three people: Chhavi Shrivastava (chhavi), Eduard Lucena (x3mboy), and Alberto Rodríguez Sánchez (bt0 / bt0dotninja).
Continue reading Many Fedora projects and groups use IRC channels on freenode for their regular meetings. Generally, meetings take place in one of the three #fedora-meeting channels (#fedora-meeting, #fedora-meeting-1 and #fedora-meeting-2). However, there is no requirement that a meeting take place in only these channels. Many ad-hoc or one-time meetings take place in other channels. Such meetings in IRC channels are normally logged. There is a Meetbot IRC bot in every channel to assist with running meetings and publishing meeting summaries and logs. To help meeting attendees, Meetbot provides a set of commands like #startmeeting, #endmeeting, #info, #help, #link, and more.
With an aim to gather information about Fedora IRC meetings and especially understand how Fedora contributors interact in these meetings, I turn towards Datagrepper. Datagrepper is a JSON API that lets you query the history of the Fedora Message bus (or fedmsg) for corresponding data. Here is a quick look of the raw feed of Datagrepper from the fedmsg bus with messages for topics like buildsys.rpm.sign and buildsys.task.state.change.
fedmsg has a few Meetbot-related topics corresponding to Meetbot commands which I gathered daily, weekly, and monthly IRC meeting data from. You can construct queries for a time period by specifying the start and end parameters for the query. Using count variables from JSON data dump, I found the total number of messages pertaining to our query. You can also use Datagrepper Charts API for some basic visualizations.
meetbot.meeting.start: Messages on this topic are published when an IRC meeting starts (using #startmeeting Meetbot command).
meetbot.meeting.complete: Messages on this topic are published when an IRC meeting ends (using #endmeeting Meetbot command).
On average, 99 IRC meetings take place every month across different channels (the mean monthly IRC meetings started is 98 while mean monthly IRC meetings completed is 100). During December to February, this value dropped considerably. After looking at the number of weekly IRC meetings started as well as completed, we see that the drop in IRC meetings in December can be attributed to the two weeks during the Christmas season (IRC meetings started dropping approximately the week before Christmas and continued until after New Years).
The weekly mean for IRC meetings started is 23.05 (median 26, highest 33) while for completed IRC meetings is 23.51 (median 27, highest 35). Also, IRC meetings are particularly low (mostly zero IRC meetings started/completed per day) during March 11th to 18th, 2015, January 28th to February 1st, and February 7th to 15th, 2015 (bot outage?).
On a normal weekday, generally 3 to 4 meetings are started/completed. Saturdays have lower values(~1-2) and no meetings are generally held on Sundays (the average IRC meetings per day started is 3 while that of IRC meetings completed is 3.3, and the median for both is 4). The highest value of IRC meetings started as well as completed across different channels occurred on 23rd March 2015 (started 11, completed 14) to Monday (next working day) after a week with particularly low IRC meetings. (March 11th to 18th 2015).
Using daywise percentage-stacked representation, we see that IRC meetings started and completed is generally the same (started and completed have equal percentages), thus allowing us to conclude that meetings are generally of short duration (less than 24 hours). The small delta in IRC meetings started and completed can be attributed to the IRC meetings overlapping between two periods. Also, the deviations are during the weeks where IRC meetings started/completed is very low and hence the large percentage value (i.e. March 11th to 18th IRC meetings started are 1, but meetings completed are 0, hence 100% of total is due to meetings started – the complete blue streak in the graph for such a case).
For visualizations generated using Datagrepper Charts API:
meetbot.meeting.topic.update: Messages on this topic are published when meeting topic is updated (using #topic command).
This correlates with IRC meetings with very low values in the December to March period and in the weeks where IRC meetings (started/completed) is particularly low. The monthly average for topic update messages generated during IRC meetings is 556.16 (median value is 618 and highest number of topic.update messages in a month is 708). The weekly mean is 130 messages (median value is 143 and highest number of topic.update messages in a week is 202).
On average, 18 topic.update messages are published per day (median value 20) with highest messages published on July 19, 2015 (56 messages). Plotting the daywise average topic.update messages per IRC meeting (we consider topic.update messages/IRC meetings started as meeting duration is generally less than a day), we can see that generally meeting topics are updated 4-5 times per meeting (mean 4.07, median 4.71), but there have also been 11-12 average topic updates per IRC meeting.
You can also find visualizations generated using Datagrepper Charts API for meetbot.meeting.topic.update here.
meetbot.meeting.item.help: Messages on this topic are published when attendees call for help on items (using #help Meetbot command). This topic was introduced at the end of March, therefore previous values are not available.
The #help command, as shown by the graphs, is rarely used by IRC meeting attendees, only being used once per month in the past two months.
For visualizations generated using Datagrepper Charts API for meetbot.meeting.item.help, click here.
meetbot.meeting.item.link: Messages on this topic are published when attendees link information to an item (using #link Meetbot command). This command was introduced at the end of March, therefore previous values are not available.
The monthly average number of items linked was 404 (median 465) and the highest number of items linked in the past year was 567. The weekly average number of items linked was 104.25 (median 109) and the highest number of items linked in the past year was 183.
On average, 14 items are linked in IRC meetings in a day, with the highest being 61 item links within a single day. Also, in an IRC meeting, generally 3 to 4 items are linked to, with 14 being the highest number of items linked to in an IRC meeting.
For visualizations generated using Datagrepper Charts API for meetbot.meeting.item.link, click here.
To get an overview of statistics related to the Fedora contributers attending IRC meetings (both attendees and chairs), I used the meetbot.meeting.complete messages (meetbot.meeting.start messages only show the initial attendees). I used the data for the past three months (August to October 2015).
During the past 3 months, 337 IRC meetings have taken place. On average, 10 people attended an IRC meeting, including the chairs, and the mean size of chairs was 4.67 for an IRC meeting (mean 4.67, median 5). Also, the largest meeting in the past three months comprised of 27 attendees and the largest group of chairs included 10 Fedora contributors.
#fedora-meeting, #fedora-meeting-1, #fedora-meeting-2? Is the distribution of meetings across channels equal?item.link messages generated equivalently by both chairs and non-chairs, or is the message generation partial?topic.help messages generated in the past only due to a specific set of users using this command?Check out threebean’s blog posts on Datagrepper here. He is one of the super awesome people behind fedmsg and Datagrepper.
Here is a fun word cloud visualization of IRC meeting attendees over the past three months (Fedora CommOps seems to be very active – you can see a lot of CommOps members here: decause, threebean, mattdm, lmacken, jflory7 and mailga too!! Yayy!!)
Copyright © 2020 Fedora Community Blog
This work is licensed under a Creative Commons Attribution 4.0 International License.
Theme by Anders Noren — Up ↑
Recent Comments