Tag: IRC

Friday’s Fedora Facts: 2021-21

Here’s your weekly Fedora report. Read what happened this week and what’s coming up. Your contributions are welcome (see the end of the post)! Elections voting is open through 3 June.

I have weekly office hours on Wednesdays in the morning and afternoon (US/Eastern time) in #fedora-meeting-1. Drop by if you have any questions or comments about the schedule, Changes, elections, or anything else. See the upcoming meetings for more information.

Continue reading

IRC Announcement

Since its beginnings, the Fedora Project has used the freenode IRC network for our project communications. Due to a variety of recent changes to that network, the Fedora Project is moving our IRC communications to Libera.Chat.

If you are a current IRC user, please go and register your nick(s) on Libera.Chat ( https://libera.chat/guides/registration#registering ) and rejoin the #fedora related channels you wish to. You can take this opportunity to choose a new secure password and make sure you are connecting via SSL. There is good documentation about choosing an IRC client at https://libera.chat/guides/clients

If you are a Matrix user, we ask for your patience as we get bridges setup on the new network. If you were joined to rooms via the generic freenode bridge, you will need to leave them and rejoin the fedora rooms in matrix (which will be plumbed with the Libera channels)

As of 2021-05-28 our official IRC presence is on irc.libera.chat.

Many Fedora channels have moved over and are ready on Libera.Chat. However, less-used channels have not be automatically setup. If you need a specific #fedora-* IRC channel setup, please file a ticket at https://pagure.io/irc requesting the channel.

New channels should have the same name as they did on freenode. For example: #fedora, #fedora-admin, #fedora-devel, and #fedora-join.

If you would like a fedora IRC ‘cloak’ you can request it at:
(an IRC cloak obfuscates your client host address and shows ‘fedora’ instead). Please note that cloaks are not foolproof, there are ways for people to still get your IP, but they do make it more difficult for people to obtain your IP.

Also, look for upcoming exciting announcements around Fedora’s Matrix presence.

Fedora Council November 2020 meeting

As usual, the Fedora Council held an annual strategy meeting last month. And as usual for 2020, we had to conduct it virtually. Instead of meeting somewhere in person for a few packed days, we decided to split it into several half days over a few weeks.  Ben Cotton, the apparently untiring Fedora Program Manager (FPgM), already published the minutes through Zodbot. In this post, I’ll cover some of the discussion in more detail.

Continue reading

Fedora meetup at Pune – March 2018

Long time we did not had any meetup at Pune, Maharashtra, India, so we decided to get started again.  Details about this meetup are available at Fedora Wiki page.

Planning for meetup started 1 month before. Initially Ompragash proposed to have meetup.com account for Fedora Pune to get more awareness. Later dropped this plan, since this is not only Fedora Pune level topic but applicable for all Fedora events.

Event started well in time.

  • 15 Attendees were present including college students.
  • Ompragash welcomed all the attendees and had a short introduction from everyone. He delivered his first talk “Telling the Fedora Story”, in this he explained how Fedora project started.
  • Parag explained different ways to contribute in Fedora in his talk. He kept on answering queries in between, it was engaging session.

Continue reading

Celebrating Fedora 25 with freenode

This post was originally published on the freenode website.

On November 22nd, 2016, the Fedora Project released Fedora 25, the latest and greatest version of our Linux-based operating system. For over thirteen years, the Fedora community has worked to bring the leading edge of open source development to the world. Fedora’s focus is guided by its Four Foundations: Freedom, Friends, Features, First. Freedom is representative of Fedora’s commitment to championing free and open source software and contributing back to upstream projects for the benefit of the open source community. Features stands for Fedora’s commitment to driving some of the newest features First. Some of these examples include the Wayland display server, systemd, and GNOME 3. Perhaps most importantly, Friends are for the friendships made by contributors from around the world who help make every release of Fedora possible. Part of why Friends is an important part of the Four Foundations is communication. Fedora community members come from all over the planet, including six out of seven continents. The tools we use to communicate help us collaborate, solve problems, and build friendships. IRC and freenode are an important part of how we communicate. Fedora registered our first channel on freenode on December 29, 2002. As we celebrate thirteen years of open source collaboration and the newest release of Fedora 25, the Fedora community wanted to reflect on our longstanding relationship with freenode.

Continue reading

Meetbot Data Analytics – A peek into Fedora IRC meetings

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.

Screenshot from 2015-10-23 21:47:06

Constructing Queries

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.

Starting and Completing Meetings

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).

mcomplete mstart

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?).

dcomplete dstart

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:

Updating Meeting Topics

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.

Calls for Help in Meetings

meetbot.meeting.item.helpMessages 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.

Linking to More Info

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.

Attendees and Chairs

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.

Other Questions to Ask

  1. Are there any specific time periods in a day when IRC meetings generally occur?
  2. Are any channels specifically used? Especially what percent of meetings are conducted on channels like #fedora-meeting, #fedora-meeting-1, #fedora-meeting-2? Is the distribution of meetings across channels equal?
  3. Are item.link messages generated equivalently by both chairs and non-chairs, or is the message generation partial?
  4. Are 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 © 2024 Fedora Community Blog

Creative Commons License
This work is licensed under a Creative Commons Attribution 4.0 International License.

Theme by Anders NorenUp ↑