I helped found what became one of the most widely used open-source help desk and ticketing systems in the world. Yet most people who know osTicket do not know it began with a Kenyan student who had never used a computer before college.

For more than two decades, that part of the story remained mostly out of view. Only recently did a longtime forum member share The osTicket Origin Story.

That distance was not entirely accidental. Some of it comes from being naturally introverted, and some from an upbringing that taught me not to boast. I wrote about that silence in The Musings I Kept Putting Off. It has taken me time to understand that telling the fuller story is not the same as making myself its hero.

My route into computing was similarly quiet. I did not enter through a computer of my own. The machines I could reach belonged to the engineering school.

The lab stayed open later than the other computer labs, and its Unix and Solaris workstations became my classroom after hours. Later, I learned Linux partly because it was available to me and partly because I could not afford a Windows license. I could study the system, experiment, make mistakes, and return the next night without owning the machine on which I was learning.

I eventually went dumpster diving for my first computer, but that is a story for another day.

Open source made sense to me before I had a philosophy for it. Someone had made knowledge reachable. The door into technology was not easy, but it was open.

Years later, I recognized something familiar inside that experience. It carried the Harambee spirit I grew up with.

Pulling together is practical

Harambee is often translated as “all pull together.” In Kenya, it names an instinct that communities can gather effort, knowledge, and resources to do something no person could complete alone.

It is not an abstract celebration of togetherness. It is practical. A classroom has to be built. A student needs a path forward. A family has work that cannot wait for ideal conditions. People bring what they can, and the contribution becomes more useful because it joins the contributions of others.

The connection between African communal traditions and open-source software is also visible in Ubuntu, the Linux distribution with South African roots. Its name comes from a southern African philosophy often summarized as “I am because we are.” Ubuntu and Harambee are not the same idea, but they rhyme. One emphasizes personhood through others; the other calls people into collective action. Both resist the myth that meaningful work is ever entirely solitary.

Open source carries a similar possibility into software. One person reports a problem. Another understands the part of the system where it lives. Someone else writes documentation, translates an interface, tests a fix, or explains the answer patiently enough for a newcomer to continue.

The contribution may be small. The circle it joins can be enormous.

The value does not belong only to the person who began the code. It grows through people willing to carry it.

Access is only the first door

Open code can travel farther than the institutions where it began. A student in Eldoret can study the same foundations as a developer in San Francisco. A small organization can use a tool without waiting for the budget of a large one. A person can learn not only what a program does, but how someone made it work.

This matters because talent is widely distributed while access is not.

Still, availability alone does not close the digital divide. A repository can be public and remain difficult to enter. Documentation may assume knowledge a beginner has never been given. A community can say everyone is welcome while rewarding only those who already understand its customs.

The work is to move from access toward agency:

  • Can a person understand how to begin?
  • Can they run the software with the equipment they have?
  • Can they question a decision instead of treating the product as a sealed box?
  • Can they adapt it to the language and conditions of their community?
  • Can today’s learner become tomorrow’s contributor and teacher?

Curiosity should not have to wait for ownership. Access becomes meaningful when someone can use it to build capacity of their own.

Local knowledge should shape the tool

Technology often travels with assumptions about where expertise lives. The product is designed in one place, then delivered to another place whose people are treated as users rather than authors.

Open source can interrupt that direction of travel. When code is inspectable and adaptable, communities can bring their own constraints, languages, workflows, and priorities into the product. The people closest to a problem gain more power to shape its solution.

This is not only generosity from the original builder. The original work becomes better because it encounters knowledge it did not contain.

Open code makes room for local wisdom to become technical direction.

The connection should run in both directions. Kenya does not simply receive technology from the West. Its leadership in mobile money and everyday financial technology has lessons for places that still imagine innovation moving along one familiar route. Participation changes who is allowed to teach.

Community creates responsibility

Open source is sometimes described as giving software away. That description misses the relationship created when other people begin to depend on it.

osTicket grew because people installed it, found it useful, reported problems, contributed improvements, translated it, and carried it into organizations I would never have reached alone. The community extended the life of the project. It also made our responsibility larger.

Building in the open means being accountable to uses you did not predict. It means maintaining trust after the original excitement fades. It means accepting that criticism often contains knowledge about the real conditions where the software lives.

Harambee is not a way to avoid ownership. It is a way to understand that ownership can include obligations to the people pulling with you.

Leave the door wider

Someone else’s openness made room for me. I feel an obligation not simply to publish code, but to make the route clearer for the next person.

That can mean better documentation, patient mentorship, sensible defaults, or software that can run without expensive infrastructure. It can mean recognizing contributions that do not arrive as code. It can mean trusting people from outside the familiar centers of technology with consequential work.

It also means stepping out from behind the work. Speaking at schools, conferences, and community gatherings does not come naturally to someone who would rather listen from the edge of the room. I do it because visibility can make a path imaginable. I want young people to see that technology is not reserved for those who started early, owned the right equipment, or came from the places the industry expects.

The measure is not that someone else can repeat my path. It is that they can begin with less friction, bring more of their own context, and open a route I could not have imagined.

Open source made room for me.

The work now is to leave the door wider.