 |
 |
If you work for an employer under a contract in which all intellectual property created during employment belongs to your employer, put in your employer's name. If you retain the IP rights, put in your name. If other contribute to a file, it depends on the size of their contribution whether it warrants a sharing of the copyright. As copyright holder, you retain important rights, including the right to license the same code under a different license, including a non-open source license, in the future. Projects such as GNU projects put in their organization, but developers are typically required to submit copyright assignment forms in which they declare that the copyright of their contributions goes to the foundation. - Godmar On 9/14/06, William Denton <[log in to unmask]> wrote: > What do ad hoc software projects do about naming a copyright holder when > putting their work under a free software license? The licenses I've > looked at have "insert copyright holder here," but what's the best thing > to put there when it's a few people hacking something informally? Apache > and Perl and the BSDs, for example, have formal organizations, but I > don't. If someone wants to put out FooMumble under an MIT license, in the > hopes other people will be interested, what's the best source for advice > about what to put in the copyright statement? > > Thanks, > > Bill > -- > William Denton : Toronto, Canada : www.miskatonic.org : www.frbr.org >