Hey everyone!

I'm a table tennis player and hobby developer from Serbia. Since having a full-time job, playing table tennis, maintaining servers and occasionally pretending to have a social life apparently wasn't enough, I decided to start a few free and open-source projects.

Over the past few months, I've been working on three of them:

  • LibreTT (https://librett.org/) — a free and open-source desktop application for organizing table tennis tournaments. Runs on Linux, Windows and macOS. Somehow. The goal is to provide a genuinely free alternative to proprietary tournament management software.
  • stoni.rs (https://stoni.rs/) — an independent table tennis player and club registry for Serbia, currently containing around 5,000 players, 217 clubs and over 11,000 historical registrations. Because apparently having this information scattered across hundreds of PDF documents was too convenient. Note: The database is temporarily unavailable to the public while I clarify some legal questions regarding player profiles and personal data protection. I've contacted digital rights organizations for guidance. I'd rather sort that out before publishing thousands of profiles and accidentally creating a fourth project called Legal Defense Fund.
  • Velmoža (https://velmoza.rs/) — a volunteer initiative to help table tennis clubs get their own websites using free software. The idea is simple: clubs should own their websites and data instead of depending on proprietary platforms. Naturally, I decided to volunteer myself for even more work.

All three projects are currently developed and maintained by a highly professional team consisting of me, myself and I. Our meetings are extremely productive, although employee satisfaction is at an all-time low.

So, I'm looking for contributors!

Developers, designers, testers, translators, documentation writers, or anyone who finds these projects interesting. You don't even need to know anything about table tennis, although knowing which end of the racket to hold would be appreciated.

Everything is non-commercial, and contributions are entirely voluntary. There's no funding, no salaries, and unfortunately no free pizza. What I can offer is GitHub commits, occasional existential crises, and the satisfaction of contributing to something that anyone can use, study, modify and share.

I'm also considering eventually establishing a nonprofit organization to support free software and open digital infrastructure for table tennis, including projects developed by other people. But that's a longer-term idea. For now, I'd be happy just to have someone else to blame when something breaks.

There's no need for a long-term commitment. Even a small contribution, bug report, code review or suggestion would mean a lot.

P.S. In the interest of transparency, a significant portion of the code is AI-assisted or, as the kids call it, vibe coded. I've been responsible for the architecture, functionality, testing and the questionable decision to start all of this in the first place. So if you open the repositories and discover something horrifying, please remember that the code is free software. You're legally allowed to fix it. :)

Anyway, if any of this sounds interesting, feel free to reach out. If not, I completely understand. I'm also questioning my life choices.

Free software, free knowledge, and apparently free labor. 🏓

all 5 comments

sorted by: hot top controversial new old
[–] 9 points 2 days ago (3 children)

It’s unfortunate that this is vibe coded because these sound like they could’ve been interesting and useful projects.

  • source
  • hideshow 3 child comments
  • [–] [S] -5 points 2 days ago (2 children)

    Thanks for the constructive feedback! If you happen to find any actual issues with the code, feel free to open an issue or submit a PR. That's the beauty of open-source software. :)

  • source
  • parent
  • hideshow 2 child comments
  • [–] 12 points 2 days ago

    To me it seems unlikely people that know what they’re doing (the ones you’re likely looking for) will bother contributing to vibe coded projects. You’ll probably end up with other developers that write slop, if any at all.

  • source
  • parent
  • [–] 0 points 2 days ago

    The code could be perfect. Doesn't matter; it's slop.

    Every line could be immaculate, idiomatic code. It's slop.

    This could cure cancer and it would still be slop.

    There is nothing you could do to make these projects anything other than slop. Absolutely nothing can be done. They are ontologically slop.

    And by extension so are you.

  • source
  • parent
  • [–] 2 points 2 days ago

    Well, þis is a new approach.

  • source