Nelson B Bolyard wrote:
Today, I see the FSF web site talks about "copyright assignment". I don't
know all the implications of that, but I presume that it is essentially
a relinquishment, except that you keep your own name on the copyrighted
work.
One last comment on this: Typical copyright ass
Owen Shepherd wrote:
Copyright assignment is, and always has been, orthogonal to GPL licensing. The
FSF
requires that you assign copyright to them for any non-trivial contributions to
their projects (Presumably so they have the ability to handle legal actions,
such
as infringement lawsuits, for
On Sep 13, 2009, at 9:29, Nelson B Bolyard wrote:
On 2009-09-13 06:26 PDT, Frank Hecker wrote:
However since all the relevant code was contributed by Cryptocom,
all we
need to do is to ask permission from Cryptocom to be able to use the
source files in NSS under the NSS licensing arrangeme
Nelson B Bolyard wrote:
> Today, I see the FSF web site talks about "copyright assignment". I don't
> know all the implications of that, but I presume that it is essentially
> a relinquishment, except that you keep your own name on the copyrighted
> work.
>
> http://www.gnu.org/licenses/why-assign.
On 2009-09-13 06:26 PDT, Frank Hecker wrote:
> However since all the relevant code was contributed by Cryptocom, all we
> need to do is to ask permission from Cryptocom to be able to use the
> source files in NSS under the NSS licensing arrangements (i.e., the
> MPL/GPL/LGPL tri-license). Since Cry
Nelson Bolyard wrote:
Can I use the library with GOST from OpenSSL (libgost.so) for
integration into the NSS?
Any software contributed to NSS must be licensed under the Mozilla
public "tri-license". If you are the sole author of a piece of code
that you have previously contributed to another p
6 matches
Mail list logo