Hi Francesco,
On Mon, Jan 09, 2012 at 07:39:36AM -, Francesco Namuri wrote:
I hope this is the right place to ask for a advice.
I have become DD in last days, in all my NM process, and in all my debian
work I used only my first and last name, my doubt is related to my second
name. I use
Thank you very much Steve,
I think that I follow your advices, in any case I've posted the question
on debian-devel too.
Cheers,
francesco
Il Lun, 9 Gennaio 2012 8:16, Steve Langasek ha scritto:
Hi Francesco,
On Mon, Jan 09, 2012 at 07:39:36AM -, Francesco Namuri wrote:
I hope this is
On Sun, 8 Jan 2012 22:23:57 +0100 Stefano Zacchiroli wrote:
On Sun, Jan 08, 2012 at 10:05:00PM +0100, Francesco Poli wrote:
Good point, but where does it claim so?
In the footer of every page. My quote:
Copyright © 1997-2011 SPI and others; See license terms
can be found in the
On Mon, 9 Jan 2012 00:17:39 +0100 chrysn wrote:
[...]
On Sun, Jan 08, 2012 at 10:22:39PM +0100, Francesco Poli wrote:
Have you tried to persuade libcgal copyright holder(s) to re-license
libcgal under the GNU GPL v2 or later, or under the GNU LGPL v2.1, or,
at least, to dual-license it
On Sun, 8 Jan 2012 23:17:02 +0100 Stefano Zacchiroli wrote:
On Sun, Jan 08, 2012 at 10:40:35PM +0100, Francesco Poli wrote:
I think that this is exactly what people opposing to copyright
assignment want to avoid: giving permission to re-license under yet
unknown terms.
I don't think you
/lurker surfacing
Working on a new project with a collaboration team. They are throwing
around GPLv3, Apache, and zlib.
An argument sprang up, which makes me concerned about DFSG-ness of the GPLv3.
The GPLv3 allows for modifications per the license itself. This is
apparent in statements by
On Mon, Jan 9, 2012, at 07:41 PM, Felyza Wishbringer wrote:
My biggest concern is that since it allows for small modifications,
what would protect us, as the original authors, from someone taking
our source, modifying a single line, then re-releasing under a
modified GPLv3 that says that
Apache License v2.0 section 4.4 also allows somebody to make a trivial
change to the covered source code and require notice wherever such
third-party notices normally appear; You may add Your own attribution
notices within Derivative Works that You distribute, alongside or as an
addendum to the
8 matches
Mail list logo
