Are &quot;anti-exclusive&quot; contracts legal? Is it legal to have an &quot;anti-exclusive&quot; contract? By anti-exclusive, I mean a contract that says, for example: &quot;This software can be used on any platform EXCEPT for X&quot; For a real life example, would it be legal to create software and say it is available for any platform EXCEPT for, say, a specific Linux distribution? In a broader sense, can somebody sell a product/service to everybody except for a particular person/group of people? I'm thinking this would be illegal due to discrimination laws, so wouldn't this be the case for the above example too?
united-states Totally legal, as long as whatever you're forbidding isn't a protected class (race, gender, etc.—the details vary by jurisdiction), or, to some degree, a pretense for one. A real-life example comes via a feud between two artists: Stuart Semple and Anish Kapoor. For reasons that are not particularly relevant to this explanation (other than perhaps that they are unrelated to Kapoor's membership in any protected class), Semple strongly dislikes Kapoor, and has made one of his products available to purchase...as long as the purchaser agrees that they are not Anish Kapoor, that they are not an associate of Anish Kapoor, and that they do not have any reason to believe that the product they are purchasing will make its way to Anish Kapoor. The product page contains the following terms to accomplish this: Note: By adding this product to your cart you confirm that you are not Anish Kapoor, you are in no way affiliated to Anish Kapoor, you are not purchasing this item on behalf of Anish Kapoor or an associate of Anish Kapoor. To the best of your knowledge, information and belief this paint will not make its way into the hands of Anish Kapoor.
It may be discrimination; not all discrimination is illegal. Details vary by jurisdiction, for example discrimination on the following bases is illegal in Australia: race colour sex sexual preference age physical or mental disability marital status family or carer’s responsibilities pregnancy religion political opinion national extraction social origin Tobacco use or non-use doesn't make the list. That's the legal position; if you want advice on how to handle the workplace stuff post your question on the Workplace Stack Exchange.
This sounds a bit far-fetched. There are laws against circumventing copy protection measures (DRM) but not against aimbotting (to the best of my knowledge). Thus, you cannot reasonably believe that a click-assist functionality would be used to break laws. It could definitely be used to break private contracts such as an EULA, but you are not a party to that contract and are not bound by its terms. Of course, when you use such click-assist tech in an online game, you might be breaking your contract with the game vendor or server provider. But this doesn't imply that a click-assist would be forbidden outside of that context. Note that assistive technologies sometimes have exceptions from laws, e.g. a permission to circumvent DRM if necessary for accessibility. In the US, the Librarian of Congress adopts exceptions for a duration of three years. While none of the current exceptions match your specific scenario involving video-games, it can be permissible to break DRM on e-books or videos for certain accessibility enhancements.
Can anybody create their own license? That is to say, can I for example create my own license under which I can license software? Yep. It's just a contract granting rights to use a copyrighted work. You can write your own contracts, so you can write your own software license. It's just often recommended that you don't, because common licenses are more well-understood, and inexperienced drafters may make errors that could result in problems, such as unintended restrictions, failing to restrict things that were intended to be restricted, or creating provisions that aren't enforceable in some/all jurisdictions. Can you mandate how a software will be released? Yes. Many software licenses, including GPL, do. The restrictions you describe in your example sound similar to CC BY-NC-SA. Also, would the following clause even be legal? Using this software you agree that any work and intellectual property based on or created with this software will be under the [INSERT_NAME_LICENSE] license, even after any and all code from this software is removed in a future update, or even if the work is rebuilt from the ground up I'm not entirely certain, but &quot;even after any and all code from this software is removed in a future update, or even if the work is rebuilt from the ground up&quot; seems, in my opinion, unlikely to be enforceable—especially &quot;even if the work is rebuilt from the ground up.&quot; How would you differentiate a complete rebuild from a totally new piece of software? More broadly, once your copyrighted code is no longer in the product, there's nothing for them to license from you. It's hard to imagine how you'd be able to claim that you're harmed by someone releasing a new version of a product that used to contain your code under a different license. Without harm to you, there's nothing for a court to redress.
The companies really need to speak to an IP lawyer as this question is seeking specific advice which this site is loathe to give out for fear of compouding issues. The answer would depend on the license agreements and enforceability in various jurisdictions. According to https://social.msdn.microsoft.com/Forums/vstudio/en-US/0368d7ee-0eb3-4e3e-a143-4410969a15bb/eula-for-vs2010?forum=vssetup Microsoft says you cant rent out the software - but this applies to the "Pro" version - I could not find anything on the "Premium" version - so most likely Microsoft to have some clam. The flipside is how enforceable this EULA is - and this would probably vary from jurisdiction to jurisdiction. It would be a very, very good idea to speak to a lawyer before letting Microsoft come onto the premises - as "inviting them" to do this is almost certainly not going to improve the Asians company's case and will allow Microsoft to go fishing further and make it easier for them to expand on and collect evidence should they decide to pursue the matter.
This would be entirely dependant on the jurisdiction. The things that would need to be legal to make this transaction legal are: Is the sexual act legal? Is gambling legal? Ongoing consent by both parties To make this an enforceable contract, in addition you would need: Sexual acts to be valuable consideration, basically, is prostitution legal? The fundamentals of a binding contract: intention, legality of objects etc.
For the GPL &quot;family&quot; of open source licenses, the answer is no. The GPL FAQ answers a closely related question: I'd like to license my code under the GPL, but I'd also like to make it clear that it can't be used for military and/or commercial uses. Can I do this? (#NoMilitary) No, because those two goals contradict each other. The GNU GPL is designed specifically to prevent the addition of further restrictions. GPLv3 allows a very limited set of them, in section 7, but any other added restriction can be removed by the user. More generally, a license that limits who can use a program, or for what, is not a free software license. I'd also recommend looking into &quot;Why programs must not limit the freedom to run them&quot; (the page linked by the FAQ). Stallman there argues (among other lines) that copyright is about limiting, well, copies rather than running the program. Similar to limiting the production of copies of a book as opposed to restricting what you are allowed to do with the information contained in the book. (I may add: or restricting who is allowed to read it.) Also, &quot;Imagine selling pens with conditions about what you can write with them.&quot; (So this is basically the FSF's position) The OSI definition of what requirements a software license must meet in order to be considered open source by them has relevant clauses: Free Redistribution (though this says that anyone can distribute the software, it does not directly talk about restricting to whom the software may be given) No Discrimination Against Persons or Groups No Discrimination Against Fields of Endeavor The OSI has a newsletter post &quot;Open Source responds to the Russia-Ukraine war: First thoughts from the Executive Director&quot;, which links to a further discussion on the topic. This is more about politics and ethics than legal questions. However, I think it's relevant in 2 ways: For the situation at hand: They point out that while the open source definitions do not allow the license to have such restrictions, there is nothing that forces you (or a repository provider) to serve &quot;customers&quot; from all regions worldwide. I.e., geoblocking downloads is not prohibited by the FOSS licenses. It does show that there is a discussion on licenses that are somewhat more restrictive than the current open source definitions. As David Siegel points out, there's nothing to keep you from putting such restrictions into a proprietary license. And if there are sufficiently many people who want to do that, we may see &quot;more restricted open source&quot; licenses in the future. (IANAL, but I'd expect there may be limits to what can be restricted in a boilerplate license wrt. anti-discrimination laws.) Independently of what the license allows, people are anyways bound by general law, e.g. sanctions.
This can't be right. If I modify open source code as part of the work done, by nature of the open source license that code can not become intellectual property of the client. Certainly it can. That which is "developed or produced" would be the modifications to the pre-existing code, i.e the copyright on the derivative work so created. If the base code was under a share-alike or copy-left license, then the client can only distribute it under the same license (or a compatible one, perhaps). But nothing compels the client to distribute it, and for the client's use, the client owns the copyright, without fear of any future claims by the contractor. If I have my own code/scripts/settings/templates/etc that I use as a contractor, and I modify those in the interest of coding efficiency in the interest of serving the client, it hardly seems correct that these assets become property of the Client. Those are your work, and you can choose whether to sell the copyrights to the client or not. Again, only the work done for that client would be covered under the wording quoted above, unless there is another provision that grants the client a license to use the pre-existing work which you modified for the job, which there probably ought to be. Or I suppose the agreement could assign copyrights in pre-existing work to the client, but that seems an odd choice, and the language in the question would not do that. You and the client could agree on a different provision such as: The contractor grants to the client a fully-paid, non-exclusive permanent license to use all intellectual property developed under this agreement, and any pre-existing works that may be incorporated therein. The contractor warrants that s/he is entitled to grant such license, without infringing on the intellectual property of any other person or entity. That wording would have the contractor retain all copyrights and other IP, but provide a license to the client to use it without further payment or expiration. Many other ways to structure such a provision are possible, dividing the rights up however the contractor and client can agree. The price for the work might vary depending on what rights the client obtains. Both forms, and many others, are perfectly legal, it is just a question of what the contractor chooses to sell, and what th4e client chooses to buy.