MQTT-Explorer
MQTT-Explorer copied to clipboard
looking for maintainer
With a time consuming job and family, coding in the off-hours is not as easy as it was before.
This project could use some help to stay running and even improve.
Thanks for @bj00rn who already put in some work to get the ball rolling again.
Have you considered possibly reverting the project back to AGPL so that others can fork it and move forward? It seems like that would solve the problem.
Thanks @thomasnordquist for coming back for an update! While I can't help on the programming side of things (being no programmer) sure I can help spread the word.
Have you considered possibly reverting the project back to AGPL so that others can fork it and move forward? It seems like that would solve the problem.
Yeah I agree with this. It’s a bit funny to ask for help but still keep a license that says “look but don’t touch.” I think people would like to help, but with that kind of restriction, it’s not really possible to do much. Opening things up is pretty much necessary if the goal is to get people involved.
Have you considered possibly reverting the project back to AGPL so that others can fork it and move forward? It seems like that would solve the problem.
While the current licence is not as restrictive as it appears, at this point it also won't the project.
The issue is with that is that appearance's are everything,
What are your main objections to switching it back to AGPL?
If I wanted to make a fork of this project legally I can't. And this means that any forks in order to submit pull requests are technically illegal. I can't actually contribute to the project. It's a bit of a catch-22 scenario.
If I wanted to make a fork of this project legally I can't.
I believe you can fork it and edit your fork, but you cannot distribute your edits. It's the ND part of the license that halts all progress on this project.
I hate to be a lawyer, because I am not a proffesional pedant but wouldnt distrubution also just include having that fork public on github? It is an absolutely bizzare choice of a License. that has totally stunted basically the only avalible Free (as in money) Open Source, MQTT Viewer/Diagnoser.
I currently can't get this working natively on arm without it crashing, a problem someone would have sorted if Deliveratives allowed.
wouldnt distrubution also just include having that fork public on github?
You are correct, your fork must remain private to avoid violating the license.
Still actively trying to let others know about your search for maintainers. To everyone interested in the future of MQTT Explorer: please help spread the word!
While the current licence is not as restrictive as it appears, at this point it also won't the project.
Sorry @thomasnordquist , but this answer is a bit cryptic to me.. what do you mean by that? Can you clarify please? Also, the dev OpenMQTTGateway also has doubts about the possibility of helping given the current licence: https://community.openmqttgateway.com/t/a-little-ot-but-please-read-mqtt-explorer-is-seeking-for-a-maintainer/4233
Possibly the licence is really a key factor in preventing external help after all?
@thomasnordquist : I would gladly try to help, but it's actually quite difficult to get in touch with you. Can you contact me privately, if github issues isn't the right way? :)
Possibly the licence is really a key factor in preventing external help after all?
I maintain some of my own small patches for issues but the license makes upstreaming them a non-starter.
While the current licence is not as restrictive as it appears
Creative Commons themselves don't recommend the license to be used for software due to how restrictive it is. There is no way to contribute to the project without violating the terms and the project is also likely violating the licenses of many of it's dependencies.
https://creativecommons.org/faq/#can-i-apply-a-creative-commons-license-to-software
@thomasnordquist : we're trying to follow to your request for supporters.. as a kind request, could you please try every now and then to follow this thread? Many thanks as always!
Happy to oblige, creating forks is covered by the GitHub TOS and stands apart from the ND.
The intend of the license is to prevent commercial distribution.
So please create a pr with a proper new license, an let's continue from there.
P.S. at this point every new license may be fine
I'll be happy to make a PR for that. Any reason not to go with CC by-nc?
Ok. Thank you very much.
Saygılarımla. / Sincerely yours. / Mit freundlichen Grüßen. Halil Satilusagi
scubanarc @.***>, 21 Ağu 2025 Per, 06:52 tarihinde şunu yazdı:
scubanarc left a comment (thomasnordquist/MQTT-Explorer#885) https://github.com/thomasnordquist/MQTT-Explorer/issues/885#issuecomment-3208901224
I'll be happy to make a PR for that. Any reason not to go with AGPL?
— Reply to this email directly, view it on GitHub https://github.com/thomasnordquist/MQTT-Explorer/issues/885#issuecomment-3208901224, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD3K5HITGYGTEFOQEEOKIRL3OU67LAVCNFSM6AAAAAB2W6EDI6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEMBYHEYDCMRSGQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>
PR created, updating the license to Creative Commons Attribution-NonCommercial 4.0 International. This should allow development to continue but prevent commercial use.
https://github.com/thomasnordquist/MQTT-Explorer/pull/897
Just merged the licence PR
Thanks for the quick merge. Looks like you added me as a colab, which is great. If you don't mind, I'll start merging some of the backlog of PR's now. I can at least work through the basic ones pretty fast.
I think this post, along with the updated licensing, should gain more visibility. I've personally tried to let other MQTT-Focused communities informed about the news, but every help counts. I'm not a programmer, but I'm willing to help in any way I can (spreading the news, coordinating the effort, and such) Please do write me if needed, or reply in this thread!
I think this post, along with the updated licensing, should gain more visibility. I've personally tried to let other MQTT-Focused communities informed about the news, but every help counts.
Mentioned it here: https://community.victronenergy.com/t/mqtt-explorer-restart/47571?u=blue_cat
This makes me very sad :( I've been running this for years, and it has worked great for me until Tahoe. To see this project die due to licensing seems a shame. I guess I will keep hunting for a replacement.
This makes me very sad :( I've been running this for years, and it has worked great for me until Tahoe. To see this project die due to licensing seems a shame. I guess I will keep hunting for a replacement.
I think you misundestood the situation: the project is not abandoned, and the licensing issue has been solved (the author changed the license to a more permissive one), so now the only problem is finding volounteers to either help in maintaining the project OR spread the word, so others can get to know the current status. (thanks @Greentreegarden btw!) @danielgoepp : Since you enjoyed MQTTExplorer over the years, please help! it's our turn to give back, for all the effort Thomas has dedicated to us and to keep enjoying MQTT Explorer
I think you misundestood the situation: the project is not abandoned, and the licensing issue has been solved (the author changed the license to a more permissive one), so now the only problem is finding volounteers to either help in maintaining the project OR spread the word, so others can get to know the current status. (thanks @Greentreegarden btw!) @danielgoepp : Since you enjoyed MQTTExplorer over the years, please help! it's our turn to give back, for all the effort Thomas has dedicated to us and to keep enjoying MQTT Explorer
I'd be happy to, but there is probably little I can do. I don't have the time right now or skills to be able to do the coding changes necessary. I'd be happy to beta test and provide feedback though. I am glad to hear things got sorted out with the license.
I'd be happy to, but there is probably little I can do. I don't have the time right now or skills to be able to do the coding changes necessary. I'd be happy to beta test and provide feedback though. I am glad to hear things got sorted out with the license.
Don't worry if your're not a coder: you can still help, by spreading the word!