Is it legal to use leaked documents for open source development? Lets say a specific data structure is only documented in a confidential document, which can not be found over the official websites. If a developer can find a copy of this document via Google (on an indexed server), is it legally allowed to implement the data structure in open source projects (and make it public with that)? I am wondering because technically, the developer using this data structure and document has never signed a NDA with the owner of this document. But has simply found it online via Google. So the document was not even obtained by &quot;breaking&quot; or hacking into any systems. Besides, is there a difference with which country the developer works?
Such use might well be illegal, and subject the user to tort liability, or possibly even criminal liability. Parties For this discussion let us call the person or company that developed and wants to protect the information D, the person or company that downloaded and wants to use the information U, and the person who placed the information on the server P. Trade Secret One possible source of liability is if D considers the information to be a trade-secret. The law on trade secrets varies to some extent in different countries, although there is a general similarity. Since no jurisdiction is specified in the question, I am going to look at the united-states law. Definition The LII page on &quot;Trade Secrets defines a trade secret under the US Uniform Trade Secrets Act (&quot;UTSA&quot;) as: &quot;information, including a formula, pattern, compilation, program, device, method, technique, or process that: Derives independent economic value, actual or potential, from not being generally known to, and not being readily ascertainable by proper means by, other persons who can obtain economic value from its disclosure or use; and Is the subject of efforts that are reasonable under the circumstances to maintain its secrecy. A similar definition is given by the USPTO page on &quot;trade secret policy&quot;. Prior to the USTA, and still in those US states that have not adopted the USTA, trade secrets were/are protected under the common law. The LII page lists the common law factors, as given by the Restatement of Torts (1939) § 757, comment b: The extent to which the information is known outside the claimant's business The extent to which it is known by employees and others involved in the business The extent of measures taken by the claimant to guard the secrecy of the information The value of the information to the business and its competitors The amount of effort or money expended by the business in developing the information The ease or difficulty with which the information could be properly acquired or duplicated by others These factors may apply in other common-law countries. In either case, one must consider how the would-be user came to acquire the information, and thus how it came to be on the server from which it was downloaded. One must also consider whether it was the subject of &quot;reasonable efforts&quot; to protect its secrecy, under the circumstances. Circumstances If P was violating an obligation of confidentiality, such as an NDA or a duty as part of an employment relationship, then the placement of the info on the server was improper. In such a case its acquisition by another, such as U might constitute misappropriation. The same would be true if a person under an obligation of confidentiality arranged for the server to be indexed by a search engine, when it should not have been. The case for misappropriation would be stronger if U knew that the information was considered confidential by D, and also if P had informed U about where to find the info, or what search terms would uncover it. If P was acting with the permission of D, and P or someone else at D simply failed to realize that the server was, or might become, indexed, then the question is whether the steps taken by D to keep the info secret were reasonable. If this a case of &quot;inadvertent disclosure resulting from the trade secret holder's failure to take reasonable protective measures&quot; then there is no misappropriation, and the actions of U are lawful. That will depend of a judgement of whether D's actions were reasonable in light of the value of the info and the overall circumstances. If the placement of the info on the server is considered to constitute &quot;general publication&quot; of the info, so that it is no longer secret in any meaningful sense, then D may have a claim against P, but not against U unless U acted in collaboration with P. Copyright Law The documents downloaded from the4 server are almost surely protected by copyright. Directly incorporating them into an open source project without permission from the copyright holder would be copyright infringement, and would subject U to a suit for infringement. However, copyright does not protect ideas, methods, or facts. If U learns a method or idea from the document, and uses that knowledge without directly copying or closely paraphrasing the document, there is no copyright infringement and no claim under copyright law. Patent Law The question does not mention any patents. It is possible that D has patented the method describe in the downloaded documents. If so, and if the patent is valid, any use by U would be patent infringement, and the question of how U learned the info becomes irrelevant. However, most software developments such as data structures are not patented, so this is a somewhat unlikely, albeit possible, case. Notre that if the information is covered by a patent is is by definition not secret, as all patents must be openly disclosed. But they may not be widely publicized, and if U does not make a patent search, U may not realize that the document includes patented technology. This possibility is largely incompatible with the trade secret possibility, althogh it is possible to use trade secrets in connection with patented tech. Conclusion In short whether U may lawfully use then info, or is subject to a tort claim by D, or even criminal action, depend on the details of the overall facts. U would do well to take legal advice on the matter before proceeding to use the info.
If you are worried that some secret will become public, you should find and meet with an attorney, not a financial adviser or other nonlawyer. Your attorney is able to shield your secret information from disclosure in ways other professionals cannot. Raise any credit score issues you're concerned about. In general, the public has a right to access judicial records. See Nixon v. Warner Communications, Inc., 435 US 589, 597 (1978) (noting that the right is rarely litigated and not clearly defined). That right is not absolute; some records can be sealed, which means that the public can't read them. Local rules govern when that happens. I don't think the existence of a civil lawsuit could be made secretly except in special circumstances. Likewise, the plaintiff usually must identify herself, except in special circumstances. A plaintiff should assume that everything about the lawsuit--who filed it, against whom, what evidence arises, the trial, and who wins and loses--will be public.
Just assuming for the sake of this particular answer that everything happens in the U.S.: I'm not sure about the particular example of Open ZFS. The registration in the USPTO Records is in Oracle's name. Using OpenZFS for distributing the same kind of software as the now closed-source ZFS would seem to be infringing to me absent a license. Maybe Oracle just tolerates the use of the "ZFS" component by third-parties since they decided at some point to license the software under an open source license. In that case, they may have a dilution (http://www.inta.org/TrademarkBasics/FactSheets/Pages/TrademarkDilution.aspx) problem and the mark may be invalid. If the mark is invalid, anybody can pretty much do whatever they want with it. That said, assuming for sake of discussion that the mark is valid, there is indeed such a thing that is similar to the copyright fair use in trademarks (in the U.S. at least). It's called "nominative fair use". You can read more about it here: http://www.inta.org/TrademarkBasics/FactSheets/Pages/FairUse.aspx Bottom line is that under the nominative fair use doctrine it's generally ok for party A to use party B's trademark to refer to whatever party B is doing, even to sell products and services related to whatever party B is doing. As per the INTA document I just linked above, its for example ok to "use “iPhone” in non-stylized form on packaging for phone cases to indicate that it is usable with iPhone 6." Having a website (even with third-party ads) that discuss ZFS-related matters is similar to the iPhone example in my mind. Having a domain name that contains the mark seems riskier, but it's not necessarily downright forbidden. See: http://itlaw.wikia.com/wiki/Toyota_Motor_Sales,_U.S.A._v._Tabari
If you aren't including those libraries, then yes because it's entirely your own work. If you are publishing those libraries, then no because their licenses will limit how you can do that. GPL's and MIT's main features are restricting how you can distribute software that includes the licensed code, and they don't allow the &quot;do whatever you want&quot; of public domain.
No. The GPL does not say 'pretend to make source code available'. The means by which the source code is made available must be equivalent to the means by which the compiled program is made available. Relevant clauses include (in version 3 of the GPL) clause 6, which says: You may [distribute your program in object form] provided that you also convey the machine-readable Corresponding Source under the terms of this License... The conveyance of source code must be in one of the prescribed ways. The one most relevant to the question (and which is illustrative of the issue at hand) is that in clause 6(d): [You may convey] the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements. The phrase 'equivalent access' means that, if you are only prepared to provide source code in an arbitrarily padded format over a very slow network link, then that is the only form in which you can provide the object code. So you will have no customers. Where you convey your software via other means such as on disk (the other subclauses of clause 6) there are similar requirements for equivalency.
Anything that helps you with your business and that you keep secret is a trade secret. The "keeping it secret" is an important part. Competitors are free to discover the same information themselves and use it, but stealing it from you is illegal. If a contractor needs to learn this information to do their job, you make them sign a non-disclosure agreement or confidentiality agreement which forbids them to pass that information on. That way, it remains a trade secret. If the contractor gives your trade secrets away, that is breach of contract and you can sue for damages. If a competitor pays your contractor to give them your trade secrets, that's not just illegal, it's criminal. On the other hand, if the contractor puts the information on his blog for example where everyone can read it, without having been enticed by someone to do this, then I believe your trade secret is gone and competitors can use it. Same as if you left documents on a park bench and your competitor finds them and reads them. You have to keep a trade secret a secret; if you fail to do so you lose. Asked about patents: If there is a non-disclosure or confidentiality agreement in place, then nobody can apply for a patent. The whole idea of a patent is that you get legal protection in exchange for disclosing your invention. Applying for a patent would mean violation of the non-disclosure agreement.
germany I am reasonably sure that works like this would be Public Domain, i.e. not copyrighted in the first place. In Germany, copyright (or more precisely, Author's Right) can only be held by a natural person, which is a legal term of art that essentially means &quot;human being&quot;. There are two groups of natural persons involved here: the programmers and the creators of the works which are part of the training set. However, I can't see how either group could have a reasonable claim of copyright. Note: there have been similar discussions about GitHub Copilot, an AI that writes code for you. It is my understanding that the process used by GitHub Copilot is roughly comparable to the process used here. With GitHub Copilot, there have been instances where significant snippets which are part of the training set have appeared in the output with only minor alterations. In this case, it is likely that the original author will have copyright over that portion of the output. However, IFF a human being were actually involved in selecting specific works, then there is probably a copyright based on the creative decision of selecting this particular work and rejecting all the others. This is similar to the classic textbook example of a driftwood sculpture: the creative process here is not creating the sculpture but choosing to pick up this particular piece of driftwood instead of the hundreds of others on the beach. So, if you simply generate these works and publish all of them, there is no copyright. If you generate a large batch and then select a certain number, then the person who made the selection might hold a copyright.
One big hole in any scheme that relies on copyright is that it could not preclude people talking about the previous content or talking about you. This is well established First Amendment law. For example, see Near v. Minnesota 283 U.S. 697 (1931), which holds that except in rare judicially established exceptions (relating to military information, obscenity, and inciting acts of violence), government censorship is unconstitutional. Thus, no statutory scheme could be used to prevent third parties who happened to have seen the material while it was freely available from re-iterating what they had seen, or talking about it, or talking about the author (you). People could even reproduce portions of the published content. Some types of reproduction would be protected as fair use in the US, especially if the reproduction is for the purpose of criticism. (17 USC 107, and this previous Law.SE answer) The closest approach would be to protect your work as trade secret, making sure that anyone that you share it with agrees to non-disclosure. But, if you "publish unique content under this pseudonym" there is no way to "arbitrarily or wholly revoke discussion about that content". If the cat gets out of the bag, while you may have remedies against the person who violated the non-disclosure agreement, you would not be able to prevent third-party discussion or reproduction.