In our upcoming 1.1.0 release, you will be able to use new features that will differentiate PolyMC from MultiMC. In the end, we concluded that we will be moving on from our origins as a packaging-friendly fork of MultiMC. This has sparked many internal discussions both at PolyMC as well as MultiMC. Sadly, our request was dismissed, and most of our team members were banned from the official MultiMC Discord server for being associated with PolyMC. In an effort to prepare for our upcoming 1.1.0 release, we wanted to contact the MultiMC maintainer to see, if they want to be credited in our documentation. This was manifested after access to the metadata service, provided by MultiMC, was blocked for all PolyMC users.Īll versions prior to 1.0.6 do not work anymore, as they try to reach MultiMC servers instead of our own. The founders have decided to sublicense PolyMC under the terms of the GNU General Public License 3 (GPL-3), which made it impossible for MultiMC to take contributions, without re-licensing to GPL-3 as well.Īs a result the MultiMC team have decided to burn bridges with PolyMC. PolyMC's inception is very controversial by its very nature. Please refrain from brigading other communities. These disagreements were turned into a takeover of packaging on Arch Linux by the PolyMC founders, something that, understandably, the MultiMC maintainers took as sabotage.Īfter MultiMC dropped support for third-party packaging, the seeds for PolyMC were laid.Īs a side note, we want to mention that we do not approve the actions of community members that used these controversies as a basis to harass MultiMC developers. In short, the original founders of PolyMC had disagreements with the maintainer of MultiMC and the project's direction. PolyMC emerged out of frustration with the MultiMC project and therefore brought controversy with it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |