Hi,
I'm reviewing the license of the Nettle manual, which has been
somewhat unclear (in some places it was stated that the manual was
GPL:ed, while copyright notices in the manual said something
differently or were simply missing).
This is related to Pike, because some paragraphs of the Nettle manual
are copied to pike's module reference doc, e.g.,
http://pike.ida.liu.se/generated/manual/modref/ex/predef_3A_3A/Crypto/AES.h….
The corresponding Pike source file
(http://pike.ida.liu.se/…
[View More]development/cvs/view.xml?module=Pike&file=7.8/lib/mo…),
but I guess the intention is that it's licensed under the usual
GPL/LGPL/MPL dual (or "threeal") license as the rest of Pike.
I'd like to make clear that such copying and remixing is allowed,
question is how. I could use the GNU FDL (no invariant sections), and
try to come up with an exception covering remixing of the manual into
documentation for crypto modules that reuse nettle code and/or
interfacecs. Or I could make the entire manual public domain. Or in
between, I could try to use something along the lines of
CC-attribution or CC-sharealike.
If possible, I'd prefer to retain some kind of copyleft, i.e, it
should not be allowed to remix the manual and then require a per-copy
licensing fee for the result, or apply drm-madness, and things like
that.
Suggestions?
PS. Whatever I decide for the main text, I'm going to add some
disclaimer saying that code examples are in the public domain.
PPS. At least I think the copying is from the Nettle manual to Pike
module documentation. If anybody thinks the copying is in the
other direction, please correct me.
[View Less]
3
4
%4H broken
by Henrik Grubbstr�m (Lysator) @ Pike (-) developers forum
18 May '09
18 May '09
New fix in CVS.
1
0
nabble.com
by Martin Stjernholm, Roxen IS @ Pike developers forum
28 Apr '09
It's time to package the accumulated 7.8 fixes. Let me know if you
have anything outstanding in 7.8 right now that needs to be fixed, or
I will try to package and ship whats in CVS ASAP.
1
0
get_dir() problem
by Henrik Grubbstr�m (Lysator) @ Pike (-) developers forum
21 Apr '09
hi,
i am reviewing the pike entry on wikipedia and noticed that the logo
image lacks clear license information. while trying to find out what the
actual license is i found that there is no clear information on the pike
website either.
i think it would be helpful if http://pike.ida.liu.se/about/pike/
contained a phrase like: the pike name and logo are registered
trademarks of IDA.
i would also like to clarify the license of the logo images on
http://pike.ida.liu.se/download/logotype/
i …
[View More]believe there is no problem with making them gpl or mpl since they
are protected by a trademark anyways.
are there any issues with adding these clarifications on the pike site?
greetings, martin.
[View Less]
I'm giving OpenID a try and need to get the big endian two's complement
of a large (if not) number (a/the default Diffie-Hellman 'p' value) how
do I do that in Pike? I've tried to figure it out myself, but I get a
bit lost between all the definitions.
Thanks in advance!
Coen
__________________________________________________________
Deze e-mail en de inhoud is vertrouwelijk en uitsluitend bestemd voor de geadresseerde(n). Indien u niet de geadresseerde bent van deze e-mail verzoeken wij u …
[View More]dit direct door te geven aan de verzender door middel van een reply e-mail en de ontvangen e-mail uit uw systemen te verwijderen. Als u geen geadresseerde bent, is het niet toegestaan om kennis te nemen van de inhoud, deze te kopieren, te verspreiden, bekend te maken aan derden noch anderszins te gebruiken.
The information contained in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Please notify us immediately if you have received it in error by reply e-mail and then delete this message from your system.
__________________________________________________________
[View Less]