Which license can protect a project&#39;s owner and give him ownership over volunteer contributions? I am the owner of a private GitHub repo for a game project. We are a team of 5, I wrote 98% of the code and made several commits, other users have also added their own code to the project and its been merged into the main branch. Parts of the project might be released commercially at a later date (not sure yet), maybe on Steam. There is no license, which means it's under All Rights Reserved (according to Github). Does that mean that everyone still &quot;owns&quot; their own code? Since I am the owner of the repo, what rights do I have over the contributions of code of others? Or is all the code others wrote still theirs under &quot;All Rights Reserved&quot;? That's in case of code, what about when a team member contributes models, audio files, etc? I dont want to get sued by someone because I used their proprietary code. So I think I need a license that gives me ownership over the contributions of others. In this case all team members are inexperienced and have agreed to work as volunteers, with full accreditation if the project is ever published. So what would be the de facto best license for me to use here? Appreciate any help. I looked all over Stack/Quora and forums, but couldn't find any conclusive answer.
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.
While the Commons Clause is not an Open Source license, the BSD license allows you to do this. To be clear, you cannot change the license of other people's code. You can however add your own code and license it under whatever terms you want. The resulting code then consists of your modifications, under whatever license you want parts of the original code, under BSD-3-clause Since you are a license-taker for the BSD-3-clause material, you must still comply with its license such as providing any recipients with the copyright + license notice. When people receive the software with your modifications, they must comply with both your chosen license terms for your modifications, and with the BSD-3-clause license for the other parts. For example, you can use the Commons Clause to prevent certain competing uses of the software as a whole. But since you will presumably provide the source code of the software, other people are free to use the BSD-3-clause code under the terms of that license, ignoring your restrictions. If you provide binaries then the resulting binary would not be covered by the BSD-3-clause license, but you would still have to provide the copyright and license notice for the original code as a kind of attribution.
The Organization Does Not Own the Copyright As you were clearly not an employee of the organization, and did not have a specific contract with them, this was not a &quot;work-made-for-hire&quot; (WFH). Therefore, the copyright initially belonged to the author, in this case the programmer, that is you. That being so, it would require a written document to transfer the copyright to another during your lifetime. In future there should be a written agreement in such a case, spelling out just what rights are to be retained by whom. It can save lots of trouble. The organization would have an implied license to use the software. The terms of this would be defined by the conduct of the parties, and might be a matter of dispute. Probably there would be a non-exclusive license without any fee or ending date. Probably there would be no license to distribute to others unless you explicitly grant one. Specific US Laws 17 USC 101 defines a WFH: 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. (emphasis added) 17 USC 201 provides that: (a) Initial Ownership. — Copyright in a work protected under this title vests initially in the author or authors of the work. The authors of a joint work are coowners of copyright in the work. (b) Works Made for Hire. — In the case of a work made for hire, the employer or other person for whom the work was prepared is considered the author for purposes of this title, and, unless the parties have expressly agreed otherwise in a written instrument signed by them, owns all of the rights comprised in the copyright. ... (d) Transfer of Ownership.— (d) (1) The ownership of a copyright may be transferred in whole or in part by any means of conveyance or by operation of law, and may be bequeathed by will or pass as personal property by the applicable laws of intestate succession. (d) (2) Any of the exclusive rights comprised in a copyright, including any subdivision of any of the rights specified by section 106, may be transferred as provided by clause (1) and owned separately. The owner of any particular exclusive right is entitled, to the extent of that right, to all of the protection and remedies accorded to the copyright owner by this title. 17 USC 204 provides that: (a) A transfer of copyright ownership, other than by operation of law, is not valid unless an instrument of conveyance, or a note or memorandum of the transfer, is in writing and signed by the owner of the rights conveyed or such owner’s duly authorized agent.
A document can be distributed under more than one license. Just because it has been made available under a CC license for free, doesn't mean that IEEE can't negotiate a different license with different terms that allow them to sell the content. (This is similar to the way that a software library can be available for free under a license that permits non-commercial use, but also be made available for a fee for commercial use.) If you want to know whether IEEE is legally selling Aaron Swartz's manuscript, you can contact Morgan &amp; Claypool, the publisher that owns the copyright, and ask them whether this use by IEEE has been authorized by them. For the other documents you mention, contact MIT Press. Etc.
Generally, as the copyright holder, you can grant anyone a license to any or all of the copyright rights you have over your work (copying, distribution, derivative works, etc.). If you want to articulate unambiguously exactly what rights you are licensing, and optionally require attribution, you could use one of the Creative Commons licenses, which are designed for creative works. Some that would likely be a good fit for you are: Creative Commons Attribution license (CC BY) - Grants full rights to any recipient to use, modify, and distribute. Requires that all reuse mentions you somewhere in the work's credits. Creative Commons Attribution-ShareAlike license (CC BY-SA) - Grants the same full rights as the CC BY license except that any new derivative work made by a recipient must also be licensed under the CC BY-SA license. With the CC BY license, another person's modifications could be under a different license; under CC BY-SA, all modifications must be licensed under CC BY-SA when distributed, so the work and all its future transformations must be shared under the CC BY-SA license, forever (until your copyright expires, of course). This falls under the broad umbrella of copyleft licenses. CC0 - Functionally places your work in the public domain where it can be used by anyone with no restrictions (other than moral rights). CC0 allows you to renounce all claim to copyright on your work (to whatever extent possible in your jurisdiction), and/or freely license all the rights you hold in your work to the maximum extent possible (for jurisdictions where renouncing your copyright is not possible). There are also Creative Commons licenses that disallow commercial use and disallow the creation of derivative works, but you are probably not interested in those, since you want to grant full rights. One other factor to consider is whether you want to license the musical work itself or only the sound recording. By default, you might only be licensing the recording, which means other people cannot record a new cover of your music. (See Does a Creative Commons license allow me to record a cover of a song recording?) If you want to allow that, simply make a separate declaration when you license the work, saying something like, "In addition to the sound recording(s), I also license the underlying musical work under identical terms, to allow recipients to record their own covers based on this song."
Unless you have a legally valid IP right related to the specification that statement is meaningless. When a software license is granted it is based on the copyright of the code. The copyright of the spec. just stops people from copying the spec - it does not protect the information in it. You can restrict copying of the spec. under copyright, you can make up a name for the spec (like USB or Bluetooth) and get a trademark and only allow the trademark use in limited cases(doesn’t stop implementation of the spec), or get a patent that would be necessarily infringed if something complying with the spec was created and used, sold, made, etc. or you can keep it secret and only show it to people who contractually agreed with your terms.
You'll want to read the actual licenses yourself and understand what is required. If you don't understand, then you'll want to consult an attorney. But neither of these licenses are all that complex in my opinion. MIT: Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the &quot;Software&quot;), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. Apache 2.0: Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a &quot;NOTICE&quot; text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. Nowhere does either license require you to publish your application's source code, even if your application is directly based on the original code.
Written down computer code is subject to copyright. If you do not have the permission of the owner to copy it you are breaching their copyright unless your use constitutes fair use/dealing.