-
Notifications
You must be signed in to change notification settings - Fork 197
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MuseScore must open source their mobile app #29
Comments
I can prove this, even without the need to reverse-engineer the app. These following simple bash commands can reveal the nature of using libmscore in the mobile app. (Think it another way. Will the MuseScore team write code from zero to process MSCZ files?) # first download apk from apkpure or somewhere else
# extract the `so` file we need from the `apk` file (every apk is a zip file)
unzip -j MuseScore-v2.6.11.apk lib/arm64-v8a/libXtzAndroid.so
# extract printable strings in that file
strings libXtzAndroid.so | grep MuseScore Results
Where did the strings come from?
|
More example strings libXtzAndroid.so | grep Score
Search the code where those strings locate at using https://github.com/musescore/MuseScore/search |
This proves once again, that MuseScore does not give a single damn about their code contributers. |
I have something in mind. Since Musescore is released with the GNU license, why don't we contact GNU for license violations? |
While I applaud your efforts and persistence, you should at least direct some of that effort to getting your facts straight. |
The readme and the LICENSE file both state that there is only GPL
@jeetee Where can I find it? sign it since 20 years ago? |
musescore.org/cla |
And indeed, everyone since the public launch in 2008 has signed it |
The internet has memory: https://web.archive.org/web/20120426185810/musescore.org/cla |
Correct, and it shows you the previous version of the CLA; your point being? |
since 2008? Where is missing 3 years? |
Before github there was sourceforge and a lot smaller team of contributors; all of which have signed the CLA when it came into existence. |
I mean the starting year of the CLA. And the readme and the LICENSE file both state that there is only GPL, nothing states that it is dual licensed. |
Of course, because the version made public is the GPL licensed version of the code.. That is how dual licensing works.. |
And all of this thus brings me again to my opening statement. You love telling that MuseScore isn't doing their research on what they can legally enforce of you. But at the same time you fail to do the same research.. |
How many? Who are they? |
There is no version prior to 1.0 (nor were there mobile apps). Contributions made before that however are all covered by it when those contributors signed the v1.0 version. And all contributors that signed it are listed there, right on that CLA page. |
Why wouldn't they? |
Why would any company share their closed source software with a random person? |
Because the software uses code from a GPL licensed library. it's a requirement per GPL license. They must distribute the source code under the same license. |
Oh please do me the curtesy of at least reading my responses; the closed source applications do not use any GPL licensed code. It just so happens that the company that owns that closed source code (via the CLA) also chose to provide an open source GPL licensed version of it; and that open source version may or may not be identical to the close source version they use and own. |
Although I agree in spirit, they should opensource the mobile app, they are truly not legally obliged to do so. The reason is the CLA -- which is precisely why there was so much backlash against Audacity receiving a CLA as well. The CLA was signed by all people who ever contributed to code to the current state of MuseScore. The CLA says that the ownership of the code is signed over the Muse Group which then can shell out as many differently licensed versions of the program as they please, since they own the Copyright. The Copyright is a the legal privilege of being able to say who is allowed to use your software, including putting a license on the code for everyone to use. But you are still able to give a different license to those who ask, since you own the Copyright. |
The point is, I don't believe the statement that all people who ever contributed signed the CLA is true. |
Fair enough, then you need to find a contributor who hasn't signed it. |
Then prove it; you have been given all the required information to do so. This is exactly my point about calling them out on not doing their copyright research and then doing exactly the same. Don't accuse based on your belief, accuse based on proof. |
But how do you know that everyone has signed it? Are you an employee?
|
I am not an employee. I have occasionally contributed to MuseScore and my first PR remained not accepted until I agreed to the CLA. I completely fail to understand how this is a "god exists argument"; the case in point here is that you claim not everyone that contributed to the current codebase has signed the CLA; all information for you to back up that claim is available (in contrast to god-like discussions). It would suit you to not deflect the discussion into something else, but use your persistence to actually do you research. This is a discussion about facts; nothing more nothing less. |
Then, I've collected all users who has PR accepted through If any of them (especially who contributed before 2019 where the PR template was not there) answers no, then yours is absolutely a pointless false claim. However, there is a chance that people left out CLA are in the group of unknown addresses or refuse to answer. |
"god exists argument" means you can't prove all have signed CLA, but I can't effectively show if there is only and only one case who left out the CLA. |
I apologize for my proofless claim about the CLA. However, your argument is only based on your personal experience, no close to the fact either. |
Why not just run a git blame on the current sources (as you were advised)? Way less work and actually gives you to overview of everyone that contributed to the current state of the code.
But you can. You have git blame and the CLA available. No need to go into contacting everyone personally (but knock yourself out if you so choose).
You are again sidestepping the actual argument I had and are deflecting it to my personal experience. My argument wasn't that you have no right to claim this, but that you should do your due diligence before making such a claim. |
I am trying to know whether the CLA is required to get a pull request accepted.
You are the one claiming that the code is covered by the CLA. Shouldn't you prove that?
|
Straight from the CLA page:
|
As for
I linked you to the actual CLA and keep pointing you to it multiple times. It exists, you can read it. It's existence is the proof that it.. well.. exists. |
Or another one, here's a link to the git workflow document on their developers handbook: https://musescore.org/en/handbook/developers-handbook/finding-your-way-around/git-workflow#Make_a_Pull_Request_to_send_your_changes_to_MuseScore Check the Important note at the end of the "Make a Pull Request" chapter (but since you keep showing a lack for following links, I'll quote it here for you):
|
All of these can be easily found in about 30 mins of browsing the contributor documentation; so again, do your research, get the facts, then come with proof. |
If you just want to teach me how to prove my claims, then thank you for all endless effort in begging me to pick up your statements. |
So, who are you?
|
Your only source of proof is the scrappy descriptions on that tiny documentation. Is that verifiable? |
As you said, don't rely on a single claim, come with proof. |
With regards to my involvement with MuseScore, I'm an active forum member of .org and an occasional contributor. In that role I've had the opportunity to meet the original team during FOSDEM a couple of times and can call them my friends. It is through that friendship that I've gained more information about the history of MuseScore. What I also am is someone who cares about correct licensing of source code; so if there is a GPL violation ongoing it should be addressed. Then again, my person is still quite irrelevant to the discussion at hand and the facts to back up a claim of violation.
Yes, the CLA is a legally binding document and the documentation refer to it; what more do you expect? Is it verifiable that all the current active code was committed by people that have signed the CLA? YES; again, take the blame of the full sources and compare it with the CLA list So no, my point is not about a single tiny description (since when does size has a correlation with importance?). It is about all those things combined: the CLA document, the list of those who signed it, the instructions for new developers on how to get their PR accepted, the actual rejection of some PRs due to the author not signing it and the git blame. It's all of those sources combined.
Again, if you choose this more intensive route of proof, by all means go ahead. But as an aside information: me, being a contributor with active code inside MuseScore at least have not received your email inquiry yet. |
Please show me the list of people who signed the CLA. It's not on https://musescore.org/en/cla
Show me some.
because I know you are here. By the way, the CLA says the company can do anything on the code. They did -- release it under GPL. Where did the dual-licence come from? Any indication? |
It is, if you're logged in with a free account. But since you once again fail to do research yourself:
If you consult that list on the CLA page itself you have the advantage of being able to click through on each on of them, leading straight to their .org profile. If they've not explicitly disabled it in their account preferences, then you'll also find a "contact me" button on there that allows you to send them a message.
There aren't that many because well, most people sign the CLA instead. But once again this is something you ought to find out in 1 or 2 hrs of work. Perhaps start from https://github.com/musescore/MuseScore/pulls?page=1&q=is%3Apr+is%3Aclosed+is%3Aunmerged+CLA+in%3Acomments which lists all non-merged PRs where the CLA is mentioned in the comments. You'll easily notice that in most cases this mention is a reviewer asking for signing it, after which in nearly all cases the author did so.
The fact that they have an app in the iOS App Store is that indication, as the ToS from the App Store are not compatible with GPL. See for example the VLC article on ZDNet from already quite some time ago and/or this stackoverflow thread discussing the same. Also note the reply you've been given by @ljrk0 above:
And yet once again, finding all of the above took me about 40 minutes, and it's been almost 7 months since you've been aware of the dual licensing possibility (if you weren't yet before I posted here). |
There's a whole thread on the sourceforge mailing list about the CLA (and when it came into existence): https://sourceforge.net/p/mscore/mailman/mscore-developer/thread/[email protected]/#msg27295415 Just to quote one of the many relevant replies (which in itself is already a quote from the Linux User & Developer Magazine Issue 97), part of a reply given by Werner:
|
@Xmader the only way you can get anything out of this, if you find the one person who hasn't signed the CLA and haid their code accepted under GPL, and had that person sue for violations of GPL (cause everything after that is a derivative work). Without that one copyright holder who's being harmed, you dont really have a way into the courtroom. |
So... I'm guessing you couldn't find a non-signing contributor? |
The MuseScore mobile app uses code (at least libmscore) from the MuseScore desktop software, which is open source under GPL.
Therefore, the MuseScore team (or UltimateGuitar, or wsmgroup.ru actually) must open source it under the same licence as per the requirements of GPL. @danieljray
Although the MuseScore desktop software is under the MuseScore name. You can't just change its licence and use the code into a proprietary app.
It's not your code. It is the result of community contribution.
The company does not care about open source and the community at all.
The text was updated successfully, but these errors were encountered: