In order for people to really make use of your project (in my case I'm planning on distributing a heavily modified fork under the MIT license), you really need to license it.
My personal preference is MIT, but you could go with another permissive license and be fine for most people.
This doesn't cover it? I mean, sounds pretty permissive to me.
"None" or "no license" is the same as "all rights reserved", which is about as strict as you can get.
If you need more info, Jeff has a nice write-up here: http://www.codinghorror.com/blog/2007/04/pick-a-license-any-license.html
I think what the author intends is to release the code into the public domain. But I agree with @petersondrew that it would be much better if that was clearly stated.
You need a license.
@johnpbloch I really don't mean to sound demanding, but for anyone to fork or use your work they need to be explicitly granted certain permissions, which are usually covered by standard open-source licenses. As I stated in a previous comment, the terms "none" or "no license" are actually the strictest forms of copyright. By stating "None" under license in the README, you have explicitly denied anyone else's legal right to use and/or modify your code, and it is therefore not open source.
Please, please consider checking out the super-simple MIT License and dropping that into your README or a LICENSE file. We all really appreciate the hard work you put into this project and it would be a shame for some of us to not be able to use it (in a corporate environment for instance) because it is not open source.
+1, please consider adding the MIT License
You might also want to use the WTFPL licence. Anything is better than this.
Sorry guys, I can't make any kind of legal claim until Microsoft clears up their own licensing: http://blog.reybango.com/2013/02/04/making-internet-explorer-testing-easier-with-new-ie-vms/comment-page-1/#comment-127129
As I read it currently, even using the modern.IE images as they are clearly intended by MS is not compatible with their own licensing. Until all of that gets sorted out, I can't license ievms in a traditional sense. I hope you understand.
@xdissent The license would cover the code in this repository; you're not redistributing the virtual pc images yourself and sub-licensing them. The person running the ievms script is responsible for abiding by Microsoft's terms when they download the images using ievms or manually from Microsoft's website.
You're clear to license the code with any standard OSS approved license.
That's a naive concept of software licensing and rarely ever true in practice. If I write something that in anyway interfaces with a GPL lib, my code is now GPL - unless it's a kernel module (which is literally an arbitrary distinction in the GPL made by Linus - because apparently that can happen without arbitration at any time). I can get away with it if it's LGPL code, but only sometimes (again, fairly arbitrary). What license does Virtualbox operate under? Would it matter? I'm in at least one literal sense "linking" to MS binaries. Does that count? Are you a cop?
All of that GPL gone viral bullshit originated from the OSS community. Imagine what kind of heinous licensing landmines the obviously better paid MS lawyers have laid!
I do not know anything about software licensing models except 3 things - they're designed to either make money or impede progress for market position, and they're written by people who spent more money on college than I did on my house. I'd like to have nothing to do with them, and as a human, who wrote a thing, I feel like I'm entitled to say "I don't know, and I don't really give a shit." Remember, "public domain" existed long before it needed fixing.
"Just use a MIT/BSD/Apache license and STF" they said. "Developers will be happy!" they said. Well sir, I don't know the distinction there either and I don't care to, and you're wrong. Developers will never be happy. It's part of the gig.
I want you to take my code, use it, add to it, delete it, modify it, sell it, claim you wrote it, buy drugs and ammunition with it - seriously, I don't care. If your corporate entity has a problem even fathoming the concept of "whatever" then I can only respond "whatever, man." And Morrissey is probably crying somewhere, but not because of you.
Sorry to have generalized - mad props to the intent of the MIT/BSD style licenses, but my point stands about the authors' tuition and the price of my house.
For what it's worth, it's a somewhat common practice for open source software to download binary distributions that are protected by copyright, much in the way that this project does.
One specific example is detailed here: https://blog.mozilla.org/blog/2013/10/30/video-interoperability-on-the-web-gets-a-boost-from-ciscos-h-264-codec/
Cisco is "opening" the H.264 codec by creating their own binaries and making the publicly available. Firefox will use these by downloading them via code, not anywhere in their software distribution. The license for Firefox isn't changing in any way because of this approach.
From what I can see, there's zero reason that their approach is any different from what you're doing. Microsoft is happily distributing these files for test purposes, and your code is simply grabbing their binary distribution.
Please consider this another for adding some sort of license. Something that says "The shell script in this distribution is public domain" even, in a license file, would make it a lot more comfortable for people to use this software.
It's not that you need to apply some sort of specific license (MIT or WTFPL or whatever), so much as there needs to be something clearly in the repo that indicates the intent of reuse, and that's commonly in a license file. The Jeff Atwood article above details why it's important.
Would you consider the unlicense?
This is free and unencumbered software released into the public domain.
Anyone is free to copy, modify, publish, use, compile, sell, or
distribute this software, either in source code form or as a compiled
binary, for any purpose, commercial or non-commercial, and by any
In jurisdictions that recognize copyright laws, the author or authors
of this software dedicate any and all copyright interest in the
software to the public domain. We make this dedication for the benefit
of the public at large and to the detriment of our heirs and
successors. We intend this dedication to be an overt act of
relinquishment in perpetuity of all present and future rights to this
software under copyright law.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS BE LIABLE FOR ANY CLAIM, DAMAGES OR
OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
OTHER DEALINGS IN THE SOFTWARE.
For more information, please refer to <http://unlicense.org/>
No license == no permission to download your code == can't use it.