[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Savannah-hackers-public] Assigning a 'co-copyright' to the FSF?
From: |
Stephan Peijnik |
Subject: |
[Savannah-hackers-public] Assigning a 'co-copyright' to the FSF? |
Date: |
Fri, 15 Sep 2006 23:28:53 +0200 |
User-agent: |
Mutt/1.5.13 (2006-08-11) |
Hi eval-team,
I'm in need of some help from you. I've 'stumbled' accross a project submission
on Savannah where someone proposed assigning the FSF a 'co-copyright' on his
project. He asked on information about whether that is possible at all
and I can't come up with an answer myself. Further more I don't even want to
give a straight answer myself as I simply don't know and don't feel like being
the right person to do so.
The point for doing something like that is, as the submitter proposes, that the
FSF could change the license (that's at least what I think he means),
if the need to do so arises.
More information on the issue can be found at [0], comment #2, fourth point.
As I said, I simply don't know which answer would be right there and if
there even is a simple answer. Thus I'd really like you to have a quick
look into the problem and maybe provide me with some information.
Thanks in advance,
Stephan
[0] https://savannah.gnu.org/task/?5863
signature.asc
Description: Digital signature
- [Savannah-hackers-public] Assigning a 'co-copyright' to the FSF?,
Stephan Peijnik <=