I am not 100% certain about this, but if we take Microsoft source code for example, they include a copyright notice in every file. In my spectulation, that would be the most important aspect, because you can have different licenses that apply to the same body of work and each license should be intended for the specific user. With the MIT license however, part of this License includes the words:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
Yeah, agreed. That page has more and makes a lot of sense given where Parallax is coming from. I did some looking and really don't know about just providing a link. I do see that done regularly. Probably the concern is that somebody not connected wouldn't know what the license really is. Hard to believe these days, but probably still valid.
After thinking about it some, I think this comes down to what you care about Rayman a lot more than it does others. If your intent is MIT, and you link, and the code ends up somewhere else, it's a worry if you think it is. Perhaps that is why people link.
Wow, I am a new guy here and reading this thread can be a little depressing.
I have tinkered with software for 30+ years and have made money off some of it but everything I have done has always been public domain because of the environment it was done in. Some of this software I created at the time was a decade ahead of its time but because I worked for a government as a direct employee and developed this software during working hours it was public domain software. At that time there was no MIT, GPL or such. It could only be considered public domain that could be used by anyone for any reason. I am sure this was one of the reasons many of the licensing terms came about.
I tell you that when your "free" software becomes the base for someone else to make millions you can look at it as a good thing or get ticked about it. But in the end it is what it is. I am currently a Software Engineering student looking to make my way through college. I will likely use the Software Engineering Degree as support for my Computer Security degree but still I want to be able to perform as a professional engineer. I have always been a hobbyist programmer since I was 14 programming basic on an Atari 8bit saving to Audio Tape...
I have very little hardware background so this is all a learning opportunity for me.
It is nice that this policy is clear because I am just starting out with stuff I will be making public eventually and I actually have yet to get my first Prop.
My intent is to use Props to help interface simple devices to ARM boards so I am sure I will be in need of much help.
Thanks for such a nice sharing.I do believe on clarity and try to fulfill all legal requirements.Thanks for stating this important things in a better way.
Comments
I am not 100% certain about this, but if we take Microsoft source code for example, they include a copyright notice in every file. In my spectulation, that would be the most important aspect, because you can have different licenses that apply to the same body of work and each license should be intended for the specific user. With the MIT license however, part of this License includes the words:
I'll go check his link...
It really a lot more than just the license itself.
So, that's not really what I'd like to link to in my codes...
I think I'd want just the license...
After thinking about it some, I think this comes down to what you care about Rayman a lot more than it does others. If your intent is MIT, and you link, and the code ends up somewhere else, it's a worry if you think it is. Perhaps that is why people link.
Yeah, that whole red/green thing now has you forever associated with these guys...
http://www.youtube.com/watch?v=JXkh6ho41-I
C.W.
Well you know what they say:
However, I would prefer that my true personality be associated this story and copyrighted song, (1,000,000 copies sold).
http://youtu.be/xhp96VWLEqA
I'm glad we have a million copies of that song and not a million Bruces... ;-)
That is a good song choice.
C.W.
A million Bruces, just think of the possibilities
Now, it appears that I should have done that first before commenting on this...
I have tinkered with software for 30+ years and have made money off some of it but everything I have done has always been public domain because of the environment it was done in. Some of this software I created at the time was a decade ahead of its time but because I worked for a government as a direct employee and developed this software during working hours it was public domain software. At that time there was no MIT, GPL or such. It could only be considered public domain that could be used by anyone for any reason. I am sure this was one of the reasons many of the licensing terms came about.
I tell you that when your "free" software becomes the base for someone else to make millions you can look at it as a good thing or get ticked about it. But in the end it is what it is. I am currently a Software Engineering student looking to make my way through college. I will likely use the Software Engineering Degree as support for my Computer Security degree but still I want to be able to perform as a professional engineer. I have always been a hobbyist programmer since I was 14 programming basic on an Atari 8bit saving to Audio Tape...
I have very little hardware background so this is all a learning opportunity for me.
It is nice that this policy is clear because I am just starting out with stuff I will be making public eventually and I actually have yet to get my first Prop.
My intent is to use Props to help interface simple devices to ARM boards so I am sure I will be in need of much help.
Rodney