Closed GoogleCodeExporter closed 9 years ago
Did you decide which license is being used yet?
Original comment by Tim.Henigan
on 24 Jan 2008 at 3:46
The project is under GPL V3. This is stated on the home page for the project.
Original comment by matt.van...@gmail.com
on 24 Jan 2008 at 4:22
Now, if you mention the license and you provide a link or address at which to
obtain
the license, do you need to paraphrase the license in each product header?
Also, what is the stuff at the bottom of this Perl script? (below the functions)
Original comment by Daniel.S...@gmail.com
on 24 Jan 2008 at 1:26
Also - do you 'own' this issue Tim? If not, you should change the Status from
'Accepted' to 'New'. As per the status descriptions, if an issue is 'new' it's
basically up for grabs until it becomes 'Accepted'.
Original comment by Daniel.S...@gmail.com
on 24 Jan 2008 at 1:27
The stuff at the bottom of the perl script is POD (perl documentation markup.
Its
kind of like Doxygen for perl. Been around forever and is part of the standard
distribution.
Original comment by Tim.Henigan
on 24 Jan 2008 at 1:53
From "How to use the GNU licenses for your own software"
http://www.fsf.org/licensing/licenses/gpl-howto.html
"Whichever license you plan to use, the process involves adding two elements to
each
source file of your program: a copyright notice (such as “Copyright 1999
Terry
Jones”), and a statement of copying permission, saying that the program is
distributed under the terms of the GNU General Public License (or the Lesser
GPL).
The copyright notice should include the year in which you finished preparing
the
release (so if you finished it in 1998 but didn't post it until 1999, use
1998). You
should add the proper year for each release: for example, "Copyright 1998, 1999
Terry Jones" if some versions were finished in 1998 and some were finished in
1999.
If several people have helped write the code, use all their names.
Always use the English word “Copyright”; by international convention, this
is used
worldwide, even for material in other languages. The copyright symbol “©”
can be
included if you wish (and your character set supports it), but it's not
necessary.
There is no legal significance to using the three-character sequence “(C)”,
although
it does no harm.
You should also include a copy of the license itself somewhere in the
distribution
of your program. All programs, whether they are released under the GPL or LGPL,
should include the text version of the GPL. In GNU programs the license is
usually
in a file called COPYING."
Original comment by Tim.Henigan
on 24 Jan 2008 at 1:54
I can work on this, but it should wait until you finish the work you are doing
on
the branch.
Part of this task should be the creation of a standard file header for
inclusion in
the style guidelines.
Original comment by Tim.Henigan
on 24 Jan 2008 at 2:16
License information was added to all files currently in the project. A standard
GPL
v3 licensing phrase was added to cover the entire Fin-ally project. In the file
header, everything below 'Version History' should be copied to new file headers.
This issue will move to Pending once the fileCheck branch is merged back to the
trunk.
Original comment by Daniel.S...@gmail.com
on 26 Jan 2008 at 9:13
The license files should really be placed at the root of the project and named
LICENSE.txt or COPYING.txt.
Other than that, is there are reason this one is still open?
Original comment by Tim.Henigan
on 20 Jul 2010 at 1:37
negative - license files can be moved and this can be closed!
Original comment by Daniel.S...@gmail.com
on 20 Jul 2010 at 1:50
done
The license file is now at $ROOT/LICENSE.txt
Original comment by Tim.Henigan
on 20 Jul 2010 at 1:57
Original issue reported on code.google.com by
Tim.Henigan
on 24 Jan 2008 at 3:36Attachments: