Is it possible to have a software license that is free for people, but expensive for mega corporations? I've been searching for a software license that seems like it should exist. The fact that I'm not finding it anywhere makes me wonder if it's just not possible. This page has a pretty good list of licenses (https://choosealicense.com/licenses/) none of which achieve something that seems pretty obviously desirable: To have a software license where you can share your code, but you don't end up doing free labor for mega-corporations. I've heard from my non-profit friend that sliding-scale fees can be a bit of a legal hassle... so maybe that's why no such thing exists? Is it legally possible to have a software license which is in-effect open for individuals and small companies, without being free labor for large corporations?
It is possible if and only if you can say exactly what you mean, and what you mean isn't prohibited by law. Software licenses can have all sorts of conditions attached to them, such as use (commercial or not; educational) or a quasi-demographic (are a student at UX, are employed by Z; reside in Y). &quot;Mega-corporation&quot; is not at all defined, so you would need to specify what it means to be a &quot;mega-corporation&quot; (is it defined in terms of assets, or income, and what is the magic number that is not to be crossed). What do you mean by &quot;corporation&quot;? Your license might not achieve what you intended it to achieve, if you don't think about ways to legally get around the restriction (can a mega-corporation have an employee incorporate your code into a product, as an individual, and then sell the rights to the product to the mega-corporation for $1, or for $1,000,000? If not, what part of the license says you can't). Also bear in mind that a license might be for a fixed period (a nuisance), or perpetual (the usual case), but status as a &quot;mega-corporation&quot; is ever-changing (Microsoft was a garage operation a few years ago; Blockbuster was a mega-corporation a few years ago). Do you want people or companies to lose their license right once they make a certain salary / income? The license would be discriminatory, but not all forms of discrimination are illegal – I don't think this would actually run afoul of any anti-discrimination laws.
There are a tangle of issues going on in this question. First, distribution of hardware-related code in commerce might very well void any right you have to patent the software and might bring it into the public domain for purposes of patent law. Publicly disclosed inventions, even if protected by copyright, are part of the &quot;prior art&quot; and can't be protected by patents. Second, you have to disclose the material ideas in an invention in order to patent it, in your patent application. The bargain of a patent is that you get protection for about two decades in exchange for contributing your idea to the public domain when it expires. Third, usually people protect software with copyright rather than patent, although there are pros and cons to each approach. Fourth, if someone knows enough about your invention to subpoena the place where you store it, you have probably disclosed too much information pre-application to patent it. Fifth, usually the &quot;real&quot; target of a subpoena gets notice of it and an opportunity to defend against the subpoena (e.g. for improperly disclosing a trade secret) before it is carried out, but the same does not apply, for example, to National Security Letters under the Patriot Act (which are supposed to be used only in national security investigations or counter-terrrorism operations, but might be abused). Certainly, an ordinary person can't issue a National Security Letter for private commercial gain without corrupt government assistance. Sixth, to issue a subpoena, there must be some pending case to which someone can claim the subpoena is relevant. A random person can't just subpoena information because they want to. Seventh, even if a server host isn't based in the United States, that doesn't mean that there isn't some means by which a court might assert subpoena power over information on server host. There are many legal &quot;hooks&quot; that could apply. Eighth, defending an isolated subpoena isn't terribly expensive. Typically, you'd be looking at a legal fee in the $1000 to $5,000 (U.S.) range, which is much, much less than the dollar cost of patenting an invention in any country. In short, while there are pros and cons of using a U.S. based server host, people in the IT industry routinely attach far too much importance to this fact which is only very rarely an important one legally. There are many other issues which are much more important in this fact pattern to your ultimate goal.
You can license the use of your IP only for certain uses, for example (most commonly) &quot;non-commercial&quot;. The general template of permission is &quot;You have permission to ___ as long as you ___&quot;. What the user is permitted to do, in your scheme, is something along the lines of &quot;only distribute the output in this manner&quot;, or &quot;not distribute code developed with this tool anywhere else&quot;. It's up to you to prove that someone violated that condition, if they did.
Exactly the same way it works over all other content There are no special classes of copyright, there’s just copyright. What a user of a service may do with copyright materials will be spelled out in the licence. If there is no licence, then they are left with fair use/fair dealing.
Can the name of my LLC include the phrases "Software Engineer", "Software Engineering", or similar derivations thereof? No. Not based on what you've posted. Go to the definitions to see how engineer is defined. It may be they are talking about actual structural engineers or environmental engineers, where if you're wrong people die. But based on above, you can't use the word engineer unless you're licensed as such. Is there even a license for computer engineer? This seems more like it could be a term of use but not actually descriptive of what you're doing. IDK. You'd have to see the definitions and exceptions. Can my resume, curriculum vitae, or my advertising or promotional materials accurately report the subjects I studied in college as the subject matter of "Software Engineering", to the extent that this information is true and accurate? Yes, your CV is supposed to say what you have done, and learned and especially published (lest it's just a resume), but the answer as far as promotional materials, is NO. This, because you don't post your cv on your ad's and if you put that, you will likely be found to be trying to pose as a licensed professional based on a technicality. If that happens the licensing authority will probably censure you by disallowing a license when your qualify. If asked directly by a client, am I even allowed to divulge my area of study accurately,(of course, but you'd also have to divulge the fact that you are not licensed and cannot act in that capacity) Would it be a violation of the law to claim I had engineering knowledge since I have studied (and practiced) software engineering in the past (for instance, at previous places of work in states which did not have these kinds of limitations, or for corporations which did not offer my services to the general public)? It could be if the person reports that you are soliciting work as an engineer w/out a license. It's like a person who went to law school, passed the bar, but never got sworn in. They cannot solicit business as a lawyer. Unless there is a license for being a computer programer, there is nothing barring you from using that terminology. You could be, that if you look up the definition prior to the statue, that it says something like "for the purposes of this section the term engineer means…", In which case it doesn't even apply to you.
Strictly speaking, yes, Microsoft owns the copyright for all that stuff. But they grant users a license. So it's a matter of knowing what they let us do with it. I grabbed the EULA for Excel 2013. You'll want to check your version. My reading of this is that you can do the thing that you want to do. M. ADDITIONAL LICENSING REQUIREMENTS AND/OR USE RIGHTS ... Media Elements. Microsoft grants you a license to copy, distribute, perform and display media elements (images, clip art, animations, sounds, music, video clips, templates and other forms of content) included with the software in projects and documents, except that you may not: (i) sell, license or distribute copies of any media elements by themselves or as a product if the primary value of the product is the media elements; (ii) grant your customers rights to further license or distribute the media elements; (iii) license or distribute for commercial purposes media elements that include the representation of identifiable individuals, governments, logos, trademarks, or emblems or use these types of images in ways that could imply an endorsement or association with your product, entity or activity; or (iv) create obscene or scandalous works using the media elements. Other media elements, which are accessible on Office.com or on other websites through features of the software, are governed by the terms on those websites.
If you can accurately describe in one license what constitutes the conditions where you wish to let users freely copy the software, and forbid any other uses, then you can also offer a second license that allows specified commercial uses with a second license. Basically, it reduces to being clear (to yourself and to the world) on what you mean by &quot;service&quot;, and what you want to allow vs. prohibit. That SSPL has a section on &quot;Offering the program as a service&quot;, though it does not prohibit it, it just requires the user to make the source code available for free. You could rewrite that section, and then hire a lawyer to give an opinion as to whether your re-write does what you think it does. Pay attention to the fact that you are interested in restrictions on &quot;cloud servers&quot; but the SSPL permissions are broader.
You are correct that it is quite expensive to patent something in U.S. law. Under U.S. patent law, once an idea is publicly published, if no one else has a patent application for the same idea that is pending, the idea enters the public domain and no one can obtain a patent of that idea. The publication become "prior art" with respect to any future patent application which cannot be protected by patent law. Of course, if you publish an invention which you discovered independently, that someone else already has a patent application pending for that will be approved the following week, the fact that you published it after the patent was applied for doesn't prevent the person with the pending patent application from having it approved. The term "invention" rather than "idea" is what I will use for the remainder of this answer, because there are many ideas which may not be patented, while the lion's share of patentable ideas are appropriately described as "inventions." But, understand that as used in this answer, the term "invention" is being used to refer to the concepts and ideas necessary to make the invention, and not to a particular instance of a product made using those concepts and ideas. When an invention is in the public domain, anyone can utilize the invention free of charge without a license. People who use the invention are not even required to acknowledge that you invented or discovered it. An invention is also not eligible to be patented if more than a year has elapsed since the first sale of a product using it. But, in that case, the invention can still be protected as a trade secret until it is voluntarily disclosed in some fashion to someone who is not subject to a non-disclosure agreement. (I say voluntary, because the fact that, for example, an unauthorized corporate spy sees the trade secret doesn't end the status of the invention as a trade secret.) Some inventions, are effectively publicly disclosed and published the moment that anyone looks at it closely. The patentable element of other inventions are invisible to an end user, or to observer of an end user. For example, if the invention involves something in the interior of a device, or the invention involves something not visible to the naked eye (e.g. a process for synthesizing an industrial chemical from other chemicals where the chemical formula of the ingredients and end result can't be determined without a microscope or analytical chemistry tests), merely showing someone a product made using the invention will not put it in the public domain. It is generally legal to reverse engineer or independently come up with an invention which is merely a trade secret. It is not legal to use a patented invention or process, even if it is not directly copied and is instead reverse engineered or independently discovered, during the lifetime of the patent. There is no straightforward way to put an invention into the public domain while retaining any right to acknowledgement that you invented it or otherwise exercise control through a licensing agreement without patenting it.