Triaging bugs is a necessary skill for any open source maintainers, whether they're working on a newly-minted library or helping out with a 10-year-old framework.
Explore these four excellent open source options for keeping track of bugs and issues, for software developers and anyone who needs to manage a complex project.
Six non-code opportunities for contributing to open source software code and communities.
Katrina Hayes shares her debugging process and gives a sneak preview of her upcoming SCaLE 14x talk.
Why open source code is not enough, but it's the right place to start as we move to more interconnected systems.
I do a lot of work on open source, but my most valuable contributions haven't been code. Writing a patch is the easiest part of open source. The truly hard stuff is all of the rest: bug trackers, mailing lists, documentation, and other management tasks. Here's some things I've learned along the way...
I recently announced a call to action for GNOME 3.10 Test Day for Fedora 20 on Facebook and I got a response that caused me to think about how everyone from the general public to developers submit and fix bugs for an open source project. This was the interaction:
After 'version 1.0' of the US Constitution was released to the public on Sept 17, 1787 there was remaining discontent among several states regarding the powers assigned to the new Federal government and a lack of protections for fundamental individual freedoms and civil rights. To fix this bug, the... Read more
With almost 30 years of active development under its belt, BRL-CAD is believed to be the second oldest open source codebase in the world that’s still under active development (VistA, the EHR of the Veterans Administration being the oldest). It has also been the primary tri-service solid modeling... Read more
They're not our favorite movie quotes but I've caught myself saying some of the more popular open source phrases more than once. It might be an analogy that we use to describe what open source is or perhaps a conversation starter.