TagFedora Planet

This tag is used for articles that are intended to be published via Fedora Planet.

TeleIRC v1.3.1 released with quality-of-life improvements

On April 20th, 2019, the TeleIRC development team released TeleIRC v1.3.1, the latest version after the final development sprint for the university semester. This release introduces minor improvements in order to accommodate heavier work-balance loads on our volunteer contributors. However, it gave us an opportunity to reduce technical debt. This blog post explains what’s new in TeleIRC v1.3.1 and also offers a retrospective into how this last sprint went.

Special thanks and appreciation goes to Tim Zabel and Nic Hartley for their contributions this release cycle.

Continue reading

Roadmap for TeleIRC v1.4

The RITlug TeleIRC developer team celebrated the v1.3 release on March 3rd, 2019. Looking ahead, the team is mapping out next steps for quality-of-life improvements in v1.4.

What’s coming in TeleIRC v1.4

TeleIRC v1.4 is the next feature release of TeleIRC. The targeted release date for v1.4 is by the end of April 2019 (i.e. the end of the academic semester for students involved with the project). Following v1.4, the project will likely enter brief hibernation until Fall 2019 when the RIT academic semester begins again.

At the developer meeting on March 23rd, we discussed the scope of this sprint and what we felt is realistic for project maintainers to work on:

Continue reading

TeleIRC v1.3: Developers map out next release

On Saturday, February 2nd, 2019, the TeleIRC community in Rochester, NY held the first developers’ meeting. Starting this month, weekly meetings are held to discuss blocking issues and plan ahead for the future of the project. Current project lead Justin W. Flory met with Tim Zabel and Nic Hartley to finish planning the v1.3 milestone for TeleIRC. Notably, this marks the next feature-release of TeleIRC since v1.2 in October 2018.

Read on to learn more about what’s coming in TeleIRC v1.3.

Continue reading

Why did Fedora Modularity fail in 2017? A brief reflection

For the ISTE-430 Information Requirements Modelling course at the Rochester Institute of Technology, students are asked to analyze an example of a failed software project and write a short summary on why it failed. For the assignment, I evaluated the December 2017 announcement on Fedora Modularity. I thought it was an interesting example of a project that experienced initial difficulty but re-calibrated and succeeded in the end. And it is a project I am biased towards, as a Fedora user and sysadmin.

I thought sharing it on my blog might be interesting for others. Don’t read into this too much – it was a quick analysis from a single primary source and a few secondary references.

Continue reading

Sphinx docs authors: Meet an opinionated quickstart

Do you write documentation with the Sphinx tool chain? Do you want to encourage more people to write Sphinx documentation in a distributed organization, but worry about maintaining compatible workflows? Introducing sphinx-docs-opinionated-quickstart, a template repository with an opinionated configuration of ReStructuredText documentation with Travis CI testing and readthedocs.org publishing.

Continue reading

Sustain OSS 2018: quick rewind

This year, I attended the second edition of the Sustain Open Source Summit (a.k.a. Sustain OSS) on October 25th, 2018 in London. Sustain OSS is a one-day discussion on various topics about sustainability in open source ecosystems. It’s also a collection of diverse roles across the world of open source. From small project maintainers to open source program managers at the largest tech companies in the world, designers to government employees, there is a mix of backgrounds in the room. Yet there is a shared context around the most systemic problems faced by open source projects, communities, and people around the world.

The shared context is the most valuable piece of the conference. As a first-time attendee, I was blown away by the depth and range of topics covered by attendees. This blog post covers a narrow perspective of Sustain OSS through the sessions I participated and co-facilitated in.

Continue reading

Fedora Appreciation Week: Tribute to a legacy

I was reviewing one of my old journals this morning and re-read an early entry from when I was studying abroad in Dubrovnik, Croatia. The entry was a time when I learned more about a man named Seth Vidal by chance. Reading this entry again the week before Fedora Appreciation Week motivated me to share it and add to the stream of stories surrounding his life and passing.

The entry is lifted out of my journal with minimum edits. I thought about fully revising it or updating it before publishing. Many parts I would write in a different way now, but I decided to let it be. It reflects my perspective at that particular moment and time at 19 years old. It is more personal than other posts I’ve published and maybe it’s a little uncomfortable for me to share, but I felt like it was worth doing anyways.

entry002: 2017-02-12

Continue reading

How five Queen songs went mainstream in totally different ways

Originally published on the MusicBrainz blog.


Making graphs is easy. Making intuitive, easy-to-understand graphs? It’s harder than most people think. At the Rochester Institute of Technology, the ISTE-260 (Designing the User Experience) course teaches the language of design to IT students. For an introductory exercise in the class, students are tasked to visualize any set of data they desire. Students David Kim, Jathan Anandham, Justin W. Flory, and Scott Tinker used the MusicBrainz database to look at how five different Queen songs went mainstream in different ways.

Continue reading

How to fix missing Python for Ansible in Fedora Vagrant

Recently, I started to use Vagrant to test Ansible playbooks on Fedora machines. I’m using the Fedora 28 cloud base image. However, when I tried to provision my Vagrant box, I was warned the Python binary is missing.

$ vagrant provision
==> default: Running provisioner: ansible...
    default: Running ansible-playbook...

PLAY [all] *********************************************************************

TASK [Gathering Facts] *********************************************************
fatal: [default]: FAILED! => {"changed": false, "module_stderr": "Shared connection to 192.168.121.3 closed.\r\n", "module_stdout": "\r\n/bin/sh: /usr/bin/python: No such file or directory\r\n", "msg": "MODULE FAILURE", "rc": 127}
	to retry, use: --limit @playbook.retry
Continue reading

Keep your open source project organized with GitHub project boards

This article was originally published on Opensource.com.


Managing an open source project is challenging work. The challenge grows as a project grows. Eventually, a project may need to meet different requirements and span across multiple repositories. These problems aren’t technical, but are important to solve to scale a technical project. Business process management methodologies such as agile and kanban bring a method to the madness. Developers and managers can make realistic decisions for estimating deadlines and team bandwidth with organized development focus.

At the UNICEF Office of Innovation, we use GitHub projects boards to organize development on the MagicBox project. MagicBox is a full-stack application to serve and visualize data for decision-making in humanitarian crises and emergencies. The project spans multiple GitHub repositories and works with multiple developers. With GitHub project boards, we organized our work across multiple repositories to better understand development focus and team bandwidth.

Here’s three tips from the UNICEF Office of Innovation on how to organize your open source GitHub projects with the built-in project boards on GitHub.

Continue reading