Is it enforceable to restrict publication of work created with my tool I created a software compiler, that produces some object code from original source code, and designed processes around it such as documentation and pre-processing. I plan to sell this tool providing monthly subscription fees of X amount, given that software compiled with my tool will be published only on my registry (there are other registries). Is it enforceable to restrict people to publication of their software compiled with my tool only on my registry and no other registries? I'd like to build my own ecosystem and lead in my own way, so ideally I want to include a clause in EULA, saying that you cannot publish your software compiled with my tool online, however I don't think this is enforceable therefore will have no effect. I know I can use marketing to make people want only to publish on my registry, but my registry costs money whereas another one is free, and I don't want code compiled with my tool to be published on a free registry, but it doesn't contain any of my code. Maybe if I include the smallest bit of algorithm to the output of the compiler, under a license that prevents redistribution on other platforms, I can enforce it? heh I think that's what I'm going to do. But then people can remove it manually by modifying the object code, so another question is if I can prevent people from modifying the output my compiler? I know it sounds like drastic measures but I really want to gain my own user base. It is because another registry is my competition and they didn't create a compiler so why should people use my compiler to publish there?
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.
Yes, a work with no license is All Rights Reserved, reserved meaning the creator of the work. Who is the creator of the work ? Everyone who contributed it, unanimously. Yes. If people contributed any copyrightable part of your work, in theory you cannot add any license or grant any right to use/reproduce/whatever the work without their unanimous agreement. That's very cumbersome, and almost nobody really does that, but it's what the law is. Big serious companies and repos require contributors to waive their rights on the code they contribute, by agreeing to a contributor's agreement. For example, python/cpython requires you to give your contribs a license allowing the python org to do essentially what they want with it, even though you retain copyright over them. If your project is not so serious, I suggest it should be enough to make the license clear, and that by contributing people are agreeing to place their contribution's code under the license. If it's a free license, that's all you need.
The software is "work for hire" and the copyright is owned by the client, not you. This is the default rule when copyrightable work is done on this basis in the absence of an agreement to the contrary. To not be "work for hire" you would have had to have a written agreement to the contrary or would have had to written the software before you were engaged by the client and then sold it to the client as an off the shelf finished product. [After further research I have determined that the language above is not accurate.] While you didn't have a written agreement, you did have an agreement reached without committing it to a final written form signed by both parties that is sufficient to cover all of the material terms of the contract and that is a binding and fully performed agreement. UPDATE: The "work for hire" issue is a bit more complex than I initially stated. Here is an American Bar Association summary of the issue in the independent contractor context (there is also a plausible argument that while the parties characterized you as an independent contractor for tax purposes that you were in fact of de facto temporary employee in which case it would automatically be work for hire, but I'll put that issue aside and take it at face value): Under the Copyright Act (17 U.S.C. §§ 101 et seq.), a work is a “work made for hire” only if: (1) it is prepared by an employee within the scope of his employment; or (2) it is specially ordered or commissioned from an independent contractor pursuant to a written agreement and the work falls within one of nine statutorily defined categories. . . . For works created by independent contractors, only the following types of works are eligible to be “works made for hire”: a contribution to a “collective work” (a work, such as a periodical issue, anthology, or encyclopedia, in which a number of contributions, constituting separate and independent works in themselves, are assembled into a collective whole); a part of a motion picture or other audiovisual work; a translation; a “supplementary work” (a work prepared for publication as a secondary adjunct to a work by another author for the purpose of introducing, concluding, illustrating, explaining, revising, commenting upon, or assisting in the use of the other work, such as forewords, afterwords, pictorial illustrations, maps, charts, tables, editorial notes, musical arrangements, answer material for tests, bibliographies, appendixes, and indexes); a “compilation” (a work formed by the collection and assembling of preexisting materials or of data that are selected, coordinated, or arranged in such a way that the resulting work as a whole constitutes an original work of authorship); an “instructional text” (a literary, pictorial, or graphic work prepared for publication and with the purpose of use in systematic instructional activities); a test; answer material for a test; or an atlas. This software is clearly specially ordered or commissioned from an independent contractor. I suspect that if you looked at the course of dealings including the client's specification of what work needed to be done (probably in part by email or in some other written form) that it would meet the requirement of a written agreement even though there wasn't a document called a contract signed by both parties. But, this still begs the question of whether it falls in one of the nine statutory categories. This American Bar Association source says that custom software doesn't qualify. The list above does not include many types of works that businesses frequently hire outside personnel to create, such as websites, logos, advertisements, photography, and custom software. For works that do fall within the defined categories, the business must have a written agreement from the author expressly stating that the work is made for hire for it to qualify as such. Although the agreement and course of dealings between a business and an independent contractor may give rise to an implied license for the business to use the works created by the contractor, it is highly preferable to avoid relying on an implied license. Any business that engages a non-employee to create a work and intends to own the copyright to such work should have a written agreement with the author expressly stating that the work is made for hire (if it falls within one of the eligible categories). If the work is not eligible to be a work made for hire, and for good measure even if it is, the written agreement should include a provision assigning the copyrights to the business. An example of such a provision is: “To the extent that the Work Product is not recognized as a ‘work made for hire’ as a matter of law, the Contractor hereby assigns to the Company any and all copyrights in and to the Work Product.” By including such a copyright assignment clause, a business will be able to obtain the copyrights it expects, even if the work does not qualify as a “work made for hire.” The copyright office's official publication on the subject provides a statutory citation (17 USC 101), and doesn't contradict the ABA presentation, although it is less detailed and specific on the legal issues. This section of the United States Code is a series of definitions. The relevant one states: A “work made for hire” is— (1) a work prepared by an employee within the scope of his or her employment; or (2) a work specially ordered or commissioned for use as a contribution to a collective work, as a part of a motion picture or other audiovisual work, as a translation, as a supplementary work, as a compilation, as an instructional text, as a test, as answer material for a test, or as an atlas, if the parties expressly agree in a written instrument signed by them that the work shall be considered a work made for hire. For the purpose of the foregoing sentence, a “supplementary work” is a work prepared for publication as a secondary adjunct to a work by another author for the purpose of introducing, concluding, illustrating, explaining, revising, commenting upon, or assisting in the use of the other work, such as forewords, afterwords, pictorial illustrations, maps, charts, tables, editorial notes, musical arrangements, answer material for tests, bibliographies, appendixes, and indexes, and an “instructional text” is a literary, pictorial, or graphic work prepared for publication and with the purpose of use in systematic instructional activities. In determining whether any work is eligible to be considered a work made for hire under paragraph (2), neither the amendment contained in section 1011(d) of the Intellectual Property and Communications Omnibus Reform Act of 1999, as enacted by section 1000(a)(9) of Public Law 106-113, nor the deletion of the words added by that amendment— (A) shall be considered or otherwise given any legal significance, or (B) shall be interpreted to indicate congressional approval or disapproval of, or acquiescence in, any judicial determination, by the courts or the Copyright Office. Paragraph (2) shall be interpreted as if both section 2(a)(1) of the Work Made for Hire and Copyright Corrections Act of 2000 and section 1011(d) of the Intellectual Property and Communications Omnibus Reform Act of 1999, as enacted by section 1000(a)(9) of Public Law 106-113, were never enacted, and without regard to any inaction or awareness by the Congress at any time of any judicial determinations.
My understanding is that here "derived from the program" means "created by modifying the source code of the program" and not "created by running the program". Certainly that is the way all users that I have heard of treat the matter. Note that a commercial program, such as a word processor, will be fully protected by copyright, but the maker does not claim to have any rights over documents written using it. "Derived" here seems pretty clearly to mean "derivative work" in the sense in which that term is used in copyright law. In copyright law "derived work" is a term of art with a definition specific to that field.
Is it illegal to ask a company for money in exchange for information on a bug in their software/website? That in itself is legal. Indeed, the company would incur unjust enrichment if it coerced you to disclose your discovery for free. Only if you threatened the company to divulge to others your discovery unless the company pays you, it would be illegal and trigger charges such as extortion (likewise, legislations outlaw the unjustified delivery of programs or instructions for hacking a software/network/etc., although this goes beyond your actual question). Can the company take legal action against me? That seems doubtful, futile, and it could backfire (please note I have not done any research on legal precedents about this). Although the terms and conditions of the website or the End User License Agreement (EULA) of software might prohibit you to reverse engineer (RE)/decompile/etc. the application, anti-RE clauses are unenforceable and the remedies therefor are indeterminate because the sole act of conducting reverse engineering does not subject the company (or third parties) to any losses. The company's decision to take legal action for your discovery could backfire from two standpoints. First, it calls attention to the fact that the software at issue is defective and unsafe. And second, the bug is likely to be detected by someone else anyway, thereby potentially compromising customers' systems.
All the CC licenses permit anyone to use the licensed content, and to make copies of it for others. Some of them permit using it for commercial purposes, others (the ones including the -NC- clause) do not. Some CC licenses permit creating modified versions of the original work (derivative works), others (the ones including the -ND- clause) do not. I do not know of any standard license which allows users to create and distribute derivative works, but not to distribute the original. The license used by Project Gutenberg permits re-use and re-distribution, but if a fee is charged beyond recouping expenses requires the removal of the PG name and logo. One problem is that if derivative works are allowed, this would include works which are only trivial modifications to the original, which would have the effect of allowing distribution of the original. If the main concern is about commercial sales, possibly a CC-NC-SA license would effectively serve the purpose? That allows redistribution, including of derivative works, but forbids commercial reuse or distribution without separate permission, and requires all redistribution to be under the same license. Otherwise a new license for this situation might have to be created. It is often a good idea to have the assistance of a lawyer with IP expertise in creating a new license, or the wording chosen may have unexpected effects or include unintended contradictions. Or one could simply place a basic copyright notice along with text such as "Modified versions may be created only with permission from the author. Request permission at work-permisisons@example.com". However, if the work proves popular, there might be a large volume of requests.
In the EU, software license resale is legal, even if explicitly forbidden by terms of any EULA or other contract imposed upon the parties. To quote the European Court of Justice's press release on its ruling in a case in Germany between Oracle and a German reseller, An author of software cannot oppose the resale of his `used' licences allowing the use of his programs downloaded from the internet. [...] The principle of exhaustion of the distribution right applies not only where the copyright holder markets copies of his software on a material medium (CD-ROM or DVD) but also where he distributes them by means of downloads from his website. Where the copyright holder makes available to his customer a copy – tangible or intangible – and at the same time concludes, in return form payment of a fee, a licence agreement granting the customer the right to use that copy for an unlimited period, that rightholder sells the copy to the customer and thus exhausts his exclusive distribution right. Such a transaction involves a transfer of the right of ownership of the copy. Therefore, even if the license agreement prohibits a further transfer, the rightholder can no longer oppose the resale of that copy. There are many such companies in the EU who resell software legally, including used OEM Windows licenses that are far cheaper than retail copies. This is, in my opinion, a fantastic thing -- but undoubtedly has been behind the trend towards time-limited licenses rather than perpetual ones, which we all arguably suffer from today.
Assuming Chegg own the copyright, then they can restrict the activities that copyright protects The statement you quote is no more or less than the rights granted to them by copyright law. Basically, it's their stuff, they get to decide how you can use it. However, that does not necessarily mean that the uses that you have nominated are prohibited. For that, we would have to look at the specific fair use or fair dealing exemptions to copyright protection where you are. It's likely that both of your usage scenarios would meet fair use and probably fair dealing (which is harder to meet). You may also find that, buried somewhere in those massive terms of use, is something that deals with this directly.