What happens if open source software infringes existing patent? What happens if an open source software is released globally and it violates a patent? I found an interesting answer on MetaFilter and would like to know if it is considered to be correct by local community. The answer says in short that theoretically a patent infringement exists but in reality the open source project won't be sued for various reasons at least as long as no commercial entity uses the software to make profit from it. Can a distribution and usage model be found that "works around" current patent legislature for example by making the developers anonymous or by using largely anonymous distribution channel (for example P2P sharing - like bittorrent). I know nothing can really be 100% anonymous and for example the music industry is able to take legal action against torrent trackers (have them shut down), but it probably goes back to how strong is the patent holder and if there is an asset to be gained from a possible judgment. An example case for such patent violation may be writing software that works as a driver assist the same way as is already patented. By a work around I mean a form of distribution what the end user would play a large role since the end user crowd is probably the hardest to sue by the patent holder. The end user would download the software to the car by him/herself.
Software doesn't infringe any patents. Creating a product that includes the software may infringe the patent, and may infringe that patent because the software is included, but the software itself doesn't. Software on its own doesn't have any effect that could be patented, only as part of some machine. On the other hand, if you want to distribute software that is under the GPL v3.0 license, then a requirement is that you give everyone a patent license for all patents that would be infringed by using the software (as part of some machine), and if you are not the patent holder, then in practice that means you are not allowed to distribute the software. With your grand plan that you write software and then let the end users do the patent infringement, that will backfire in two ways: First, you'd be likely sued for contributory patent infringment, because it is you who enables the patent infringemnt. Second, you can be sued for copyright infringement because you have no license that allows you distribution of the software, depending on the Open Source license used.
Yes That is very simple - copyright is an exclusive right that starts automatically with the creation of a copyrightable work. The default situation is that the author has an exclusive rights to make copies of the work and derivative works. If the code is published somewhere by the author but the author has not said anything about its licence or copyrights, then the default situation applies - you need permission and you don't have it, so it's not legal for you to distribute their copyrighted works. They have the right to just publish it somewhere, others don't. If you try to contact the author and they don't say anything and ignore you, then the default situation applies - you need permission and you don't have it, so it's not legal for you to distribute their copyrighted works. If it's impossible to find the author (e.g. I have certain cases with literary works where it's not clear who inherited the rights after the author died), then the default situation applies - you need permission and you don't have it, so it's not legal for you to distribute their copyrighted works. That being said, certain forms of reuse (recreating ideas, learning from them, etc) would not be a copyright violation. But in general the situation with the author not saying anything is almost the same as the author explicitly stating "all rights reserved, you're not allowed to do anything, violators will be shot" - some specific uses are allowed even against author's wishes (e.g. 'fair use' clauses) but everything that needs their permission really does need their explicit permission.
It's legal to sell your program if it doesn't infringe any law or anyone else's intellectual property. Examples of things that can get you into trouble: statutes: Some countries have export laws that forbid you to distribute certain types of encryption without proper export controls. patents: If you use a design or invention that is under patent protection you could be liable for infringing patent rights. trademark: If you improperly use a trademarked name you could be subject to damages. licensing: If you violate a license to which you have agreed you can be sued for damages. copyright: If you appear to have copied something without license you can be liable for damages. Just because: If someone wants to sue you, they can. Since there's no way to guarantee your business won't run into liability from infringement &ndash; or from some other failure &ndash; people normally conduct business through entities like LLCs that shield them from personal liability. Depending on their concerns and finances, they may also: Buy liability insurance Consult professionals like IP lawyers to: review their business and products in advance to look for and address glaring infringements, and/or correctly protect their IP using the tools mentioned above.
could this mean my employer owns the idea and anything I develop --since I would use the same technology for my idea that I do at work? No, unless by &quot;technology&quot; you mean the employer's materials or resources (see condition 3 of the clause). Your remark that &quot;this is completely and utterly unrelated to [employer's] business model&quot; survives items 1 and 2. Likewise, working on your idea outside hours survives the corresponding part of item 3. Would this also mean that any open-source software I develop outside of work automatically belongs to my employer? No, unless the software you develop is &quot;based on [your] knowledge [etc.] of (COMPANY)&quot;.
In the most likely case No, but you can make it happen! First - almost every patent is rejected - at first. Then you respond to the office action rejection by arguing and/or amending and - guess what - you are likely to get a final rejection. That means the rejection is final until you pay them more money to file a Request for Continued Examination and get two more go-arounds with them. Can you keep doing this? Yes. A previous director of the USPTO tried to make a rule that limited the number of RCEs - the courts knocked it down. If you give up and let it go abandoned by not responding to an office action within the statutory limit (6 months) then the process of that application is over. If you have not filed a co-pending application before the initial application went abandoned then you are really starting over if you file a new application. The original application can be used against any new application on a similar subject matter if it has been published. But it might not have published. The law (35 USC 102) contains - (a) NOVELTY; PRIOR ART.—A person shall be entitled to a patent unless— (1) the claimed invention was patented, described in a printed publication, or in public use, on sale, or otherwise available to the public before the effective filing date of the claimed invention; or (2) the claimed invention was described in a patent issued under section 151 , or in an application for &gt;patent published or deemed published under section 122(b) , in which the patent or application, as the case may be, names another inventor and was effectively filed before the effective filing date of the claimed invention. Your application may or may not have been published. Then it is neither published or issued and does not fall under prior art under 102 or 103. Applications are automatically published by the USPTO at the 18 month point unless you requested non-publication. In that case if your application never issues it is never public and can't be used against you or anyone else as prior art. You could even decide to keep it a trade secret. Before the publication process came into being as part of TRIPS, an applicant could wait until they saw the claims that had been allowed and the patent was ready to go. If they didn't feel the claims were valuable enough they can chose to explicitly abandon and keep it secret.
That depends on how you get the ingredient list. If the list is published and not protected by a patent, then anyone is free to use it in making the same or a similar product. If the product is patented and the ingredient list is covered by the patent, and the patent is currently in force, then making a similar product would probably be patent infringement, and the patent holder could sue and collect damages. If the list is secret, and has been protected as a Trade Secret, and if the would-be imitator gets the formula improperly, then the owner of the formula would have valid grounds for a trade secret lawsuit and to collect damages in that suit. Improper means would include breaking into the owner's files, or inducing an employee or contractor to violate a confidentiality agreement. But analyzing the product and figuring out its composition, a form of reverse engineering would be perfectly proper, and would give the formula owner no claim. Similarly, if the owner was careless and allowed the formula to be disclosed, the imitator would have done nothing improper. So the outcome depends on the details of facts not stated in the question.
The title of your question suggests that a patent is involved, but it isn't clear from the rest of your question if that is really the case. Simply seeing a product on the internet does not mean that there are any patent rights attached to it. If a patent does exist, then that patent's protection is defined by its claims. In the US, if you make or use an object that includes all the elements of the claims of a granted patent, then you are infringing that patent. It does not matter whether you share the object or attempt to make money from it—simply making or using it is enough to qualify as infringement. That said, based on your intended use, the patent owner is highly unlikely to ever find out about your infringement. Further, even if they did, enforcing patent rights in court is incredibly expensive (typically involving multi-million dollar legal budgets), and they wouldn't stand to recover much from you, so it is even less likely that they would sue you for the infringement.
How can you get in trouble? If they see any code you wrote for them show up in your open source project. They own the code you write on company time. Even if your code goes into an open source project owned by the company, you still don't own that code. The only way you can own it is if they directly tell you that you may put it into your open source project. If you make your open source project private so nobody else can see the source code, but they see your side business has the same features you wrote for them. You can try to get around problem #1 by hiding your open source project. But if they see the same features in it that they told you to write for them, they can become suspicious. They might force you to reveal the source to them in court. If you don't want them to see it, they may force you to share it with a third party who is bound by an NDA. The third party can compare your code to theirs and report if you copied any code. Even if your work is not directly related to the company products, your work for them can be a company secret. You reveal that, and you are in trouble. You say your work improves internal procedures, but is not directly related the company products. If a company can reduce its cost, it can lower its prices and still make more money than their competition. That gives them a competitive edge over other businesses. By revealing how your employer does its internal work, you give that competitive edge to their competition. Although you say your open source project does not violate rule #4 - "does not reveal company secrets" - all three explanations mentioned above say it does. What can you do? Quit and start your own company based on your open source project. If you quit, you should do it before you write any code related to your project for your employer. Ask your company to fund your project. Talk to your boss and anybody else there who might be a stakeholder. Tell them what you can do. Make a deal with them that you get to work on your project during work hours. Maybe they could turn it into an additional source of revenue for the company. That changes you from a potential loss into a valuable asset. Their competitors might end up buying products based on your code. Many companies would love for their competition to pay them. Ask your employer to allow you to turn your work into your open source project. Some companies require employees who work on open source projects to give their employers a royalty-free license to use and modify the work as they wish. Ask your employer if they would use a product based on your project. You can start a side business (with your employer's blessing), and turn them into your first customer. They get access to a beta product before their competitors do. Promise them they get it free or at a hefty discount for a year or two before the competition even knows what you have. The first option is win/lose. You win and your employer loses. The other three options are win/win. Good luck!