Please at least read this, or at least the section that describes controls, or DO NOT download Mugician. Contact me if you like Mugician, b...
Wednesday, March 2, 2011
hwado's Musician vs my Mugician
"WTF is this?" - A quote from somebody that helped work on Mugician with me, after seeing this image on his iPad.
I made Mugician open source a few weeks ago. I got asked by a lot of people to add features that I didn't want, so I figured that making the project open source was a reasonable thing to do. So I put it here.
In the README file that shows up on this page, it merely states some simple conditions in the license. They are all aimed at just making sure that I don't end up getting emails about the Malware version of Mugician, or confusing my users.
If you buy "Musician" just note that it's a blind re-compile of the Mugician project in its latest state, with a few bug fixes that are not yet in the official Mugician, and a stupid splash screen banner added.
I really dislike this sort of developer, and these guys were the only thing that gave me pause to making Mugician open source. But whatever, some developer that wants to really add something, like make an ergonomically workable iPhone Mugician or add MIDI support... be my guest. Just credit the project, and I will endorse your work enthusiastically, and ask you to submit your changes into a branch. If I trust you enough, I will write an exception to the request to submit changes into a branch that I can compile too.
Pythagoras won't be open source because of this sort of thing though. It would be a better candidate because the source is smaller and cleaner, and there is a good possibility of the whole sound engine being in libpd. I might have to share it on a peer-to-peer basis with specific collaborators just to shut out the compiletards that just take people's stuff and try to re-brand it as their own.
If you don't understand why that irritates me about a free app, keep in mind that I am not the only person that sunk time into Mugician's design. Jordan Rudess is an example of somebody who spent time on it. Hiding "Musician"'s origins as "Mugician" hides the credit that Jordan Rudess deserves. In this case, calling it "Musician" is clearly an attempt to confuse my users as well. I just did a gig with Mugician the other night, and I am sure that people will be sending email to HWADO thinking that it's me, and that I don't respond to emails.
It hides the credit to all of my many testers, and people who got up on stage and risked their gig with my instrument.
I hope that Apple tires of these sorts of developers and starts revoking their certificates en-masse. There is always talk about it, and at some point Apple will have to step in and do it. hwado's business will be gone overnight when it does. Apple even noted quite explicitly in the developers agreement that they don't need more fart apps, so they don't just blindly allow junk because it's not violating an explicit rule. Musician is a good app because it's Mugician, but it's definitely an underhanded way to avoid the obligation to contribute something or to write your own code.
Note that I wrote the license myself in plain english, and I did not pick some legally binding GPL. The reality is that the legal mumbo-jumbo is unreadable because it's not really in English, and it only works in the case of enforcing it against a large company - but that would still require lawyers to challenge it anyway. So I am relying on people to simply point out what these people are doing in the app comments.
Maybe "Musician" will be a runaway hit for some strange reason. I guess that's ok as long as everybody follows links back to Mugician to see who actually did the work on it, because it still validates what I am trying to do. My main concern is that I never want to have to deal with a malware version of my app floating around, especially one that *does* credit Mugician.