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.Continue reading
CategoryFree and open source software (FOSS)
All articles related to free and open source software (FOSS) are here. Topics include my favorite software, thoughts on contributing to open source communities, some experiences in the Fedora and MetaBrainz communities, my thoughts on issues in the world of FOSS, and more.
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
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
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.
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.
One of the most unusual but wonderful experiences happened to me on a return trip from Europe to the United States.
A series of heavy noreasters hit the US east coast over the last couple weeks. This coincided with my travel dates back to Rochester, NY. While we didn’t have flooding, we had a lot of snow. A lot of snow means canceled flights.
As I made my way through border control in Dublin, Ireland on March 7, I discovered my connection to New York City would likely be canceled. A meander from baggage claim to the check-in desk confirmed this. Fortunately, Aer Lingus had no issue putting me up in a hotel overnight with dinner and breakfast to catch the next flight to New York the next day.
While waiting in airport queues, a friend happened to retweet a local event happening in Dublin the next day.
For International Women's Day on Thursday, we'll be celebrating Female Firsts in medicine with @RCSILibrary https://t.co/RvIHtwAhys
Saturday, we have our @artandfeminism event in @UCC, celebrating our Irish and local female artists from 12-3pm https://t.co/ZMpKQOSR3q pic.twitter.com/0G7Kn3zpS6
— Wikimedia Ireland (@WikimediaIE) March 5, 2018
The event was a local Wikimedia meet-up to celebrate International Women’s Day. Participants would create and edit Wikipedia pages for influential women in the history of the Royal College of Surgeons in Ireland. After digging deeper, I found out the event was 30 minutes away from my hotel from 09:30 to 12:30. My flight was at 16:10.
I put in my RSVP.
In December, I received the happy news of an offer for a internship position at UNICEF in the Office of Innovation. The Office of Innovation drives rapid technological innovation by rapid prototyping of new ideas and building full-stack products to make a positive impact in the lives of children. This is a simple answer, but a more detailed description is on our website.
My internship at UNICEF is unique: I support open source community engagement and research as my primary task for the MagicBox project. For years, I’ve done this in open source communities in my free time (namely SpigotMC and Fedora), but never in a professional role. As I navigate my way through this exciting opportunity, I plan to document some of the experience as I go through blogging. My intent is that my observations and notes will be useful to someone else in the humanitarian open source space (or maybe to a future me).
But first, what does “open source community engagement and research” really mean?