MeshMC: Regarding the KDE Incubation request and the need for a sponsor.

[M.samet Duman]

Hello, esteemed KDE developers, sponsors, and administrators,

I am writing to you regarding a sponsorship request for MeshMC and to address some
concerns about the necessary next steps. I began the MeshMC journey on March 25, 2026,
building upon a MultiMC patch that had last been updated on June 24, 2022. Exactly seven
months have passed since then. I dedicated a great deal of effort to the project—developing
new features, refactoring code, fixing bugs, and migrating to Qt6 (while dropping Qt5 support).
However, I eventually restored and expanded Qt5 support—partly due to the extreme stability
requirements of projects like Debian—established a governance structure, and even moved
development to my own server for a time before ultimately returning to GitHub. While it may
not be a vast span of time in the grand scheme of things, it has been quite a journey for me.
However, as I have been working on MeshMC alone and wish to grow its user base, I have
been looking for an umbrella organization to join for quite some time. MeshMC didn't actually
start on March 25th; I took my first steps into development with "ProjT Launcher"—a fork of
PrismLauncher—back in October 2025. I later abandoned ProjT Launcher due to issues like
code complexity and licensing, continuing instead with MeshMC, which I derived from MultiMC.
As you know, the "Mesh" in MeshMC represents modularity. True to this concept, I developed
a plugin system for it called MMCO—standing for MeshMC Module Component Object. The
reason for my email today is to propose that MeshMC continue as a KDE project. It is a launcher
with minimal dependencies and is released under the Apache-2.0 free software license. I
conducted some preliminary research before sending this email. Apache-2.0 is not viewed very
favorably—specifically regarding the codebase, or the application itself. That is not an issue; the
contributions are mine, so I can relicense the project. I am rejecting the QML contribution from my
friend, and the branch currently on GitHub will not be included in Invent. In short, I am willing to
relicense the project. Furthermore, I am ready and willing to explicitly transfer the naming rights for
MeshMC, Project Tick, and Project Tick HQ, as well as the domain names projecttick.org, projecttick.net,
and projecttick.com, to the KDE Foundation. However, I do not have a sponsor; therefore, I am in need
of sponsorship. I respectfully request that the necessary steps be taken as a matter of urgency.

To rectify any minor misunderstandings, I can relicense my own contributions; the existing
contributions to MultiMC will remain under the Apache license, and proper attribution is
already in place. This is the proper procedure to follow. I have a few more questions. I currently
provide official distributions of MeshMC for Windows and macOS; it is essential that we do not
discontinue these. While I believe it shouldn't be limited to Linux, I am asking this because I am
not entirely certain. Also, since I will be moving to Invent, manual updates will be required, which
is not an issue. My general user base uses Flathub; I anticipate a potential issue regarding the
AppID change there, though to my knowledge, it shouldn't cause a problem. I hope Flathub
has taken measures to handle this. Thanks!

Best regards,
Mehmet Samet Duman
Project Tick HQ
https://projecttick.org