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

[M.samet Duman]

Hi Albert,

Thank you for your candid feedback regarding MeshMC.

I understand that you are not currently convinced MeshMC is a suitable candidate for the KDE incubation process, and I respect your decision not to sponsor the project.

However, I would greatly appreciate it if you could explain which aspects of the project—or the proposal I submitted—raised concerns for you.

What would I need to change, improve, or demonstrate for you to consider sponsoring MeshMC in the future? Do your concerns relate to the project's technical aspects, governance structure, licensing, long-term maintenance, or its alignment with the KDE ecosystem?

I am open to considering constructive feedback and making necessary improvements wherever possible. Understanding your concerns more clearly will help me determine the appropriate next steps.

Thank you for your time.

Best regards,
Mehmet Samet Duman

> Albert Astals Cid <aacid at kde.org> şunları yazdı (8 Eki 2026 01:12):
> 
> El dimarts, 6 d’octubre del 2026, a les 7:25:48 (Hora d’estiu d’Europa
> central), M.samet Duman va escriure:
>> Hello Mr. Albert,
>> 
>> My motivation for getting involved with KDE stems from MeshMC’s fully
>> modular nature, philosophical alignment, and the desire for better
>> integration with the KDE ecosystem.
>> 
>> My project introduces a plugin system called "MeshMC Modular Component
>> Object" to KDE. I believe the "Games" category is missing a Minecraft
>> launcher; after all, many people play Minecraft, and having access to such
>> a launcher is essential for users installing KDE.
>> 
>> The reason I forked MultiMC lies in issues regarding branding rights and
>> redistribution; the original maintainers are not only heavily involved in
>> distribution but also frown upon the addition of new features. My goal is
>> to add new features while preserving the extensive support base. I am of
>> the opinion that changes can be made without breaking things.
> 
> Thanks for answering my questions.
> 
> I’m not convinced that this project is a good fit for incubation into KDE, so
> I won’t be sponsoring it.
> 
> Of course, don’t take my answer as me blocking the incubation if someone else
> is willing to sponsor it.
> 
> Best Regards,
>  Albert
> 
>> 
>> Kind regards,
>> Mehmet Samet Duman
>> Project Tick
>> 
>>> Albert Astals Cid <aacid at kde.org> şunları yazdı (6 Eki 2026 00:48):
>>> El dijous, 1 d’octubre del 2026, a les 18:41:07 (Hora d’estiu d’Europa
>>> 
>>> central), M.samet Duman va escriure:
>>>> 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!
>>> 
>>> Please next time write more paragraphs. Reading such a huge block of text
>>> was hard.
>>> 
>>> What is your motivation for becoming part of KDE?
>>> 
>>> What does your project bring into KDE?
>>> 
>>> Why fork MultiMC? It seems quite actively maintained?
>>> 
>>> Cheers,
>>> 
>>> Albert
>>> 
>>>> Best regards,
>>>> Mehmet Samet Duman
>>>> Project Tick HQ
>>>> https://projecttick.org
> 
> 
>