[Soc-2005-dev] Copyright stuff
Jiří Hnídek
jiri.hnidek at vslib.cz
Thu Jul 28 15:38:59 CEST 2005
Hi,
I created wiki page with .c .h and .py templates. Feel free to add some
c&c ;-)
http://wiki.blender.org/bin/view.pl/Blenderdev/SourceFileTemplates
Best regards
Jiri
> Hi,
>
> A proper new header could look like this;
>
> /*
> * ***** BEGIN GPL LICENSE BLOCK *****
> *
> * This program is free software; you can redistribute it and/or
> * modify it under the terms of the GNU General Public License
> * as published by the Free Software Foundation; either version 2
> * of the License, or (at your option) any later version.
> *
> * This program is distributed in the hope that it will be useful,
> * but WITHOUT ANY WARRANTY; without even the implied warranty of
> * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
> * GNU General Public License for more details.
> *
> * You should have received a copy of the GNU General Public License
> * along with this program; if not, write to the Free Software Foundation,
> * Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
> *
> * The Original Code is Copyright (C) 2005 by xxxxxxxxxxxxxx
> * All rights reserved.
> *
> * The Original Code is: all of this file.
> *
> * Contributor(s): none yet.
> *
> * ***** END GPL LICENSE BLOCK *****
> *
> */
>
> At choice you can assign (c) to yourself or to the Blender Foundation.
> My preference is to assign it to the BF, that will enable us to better
> protect the code in case of abuse, it will also free you from
> liability, if anyone ever thinks you violated copyright or a patent.
>
> Also note that the BL exception was removed from the license text.
>
> -Ton-
>
> On 27 Jul, 2005, at 23:48, Pablo Diaz-Gutierrez wrote:
>
>> Hi guys,
>>
>> I was just creating a new file, using an old one as a template, and I
>> came across the copyright notice in the file header. It says
>> something like "Original code copyright (2001-2002) by NaN blah blah.
>> Original code is: all the file. Contributors: None".
>>
>> So I got a bit curious about what's the right thing to do here for us
>> summer coders. If it's modifying an existing file, it should
>> obviously be enough with adding our name to the list of contributors.
>> But what shall we do with new files? I didn't find any related
>> information in the website. Is there a policy for this, or does
>> everyone choose what to write?
More information about the Soc-2005-dev
mailing list