gnu-crypto-discuss
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [GNU Crypto] Upcoming 2.0 release


From: Ryan Senior
Subject: Re: [GNU Crypto] Upcoming 2.0 release
Date: 17 Dec 2003 07:50:58 -0600

Well, I would like to help out with the project.

> Also note that if you are thinking of contributing anything major we
> need a copyright assignment, 

Do you mean signing over the copyright to the FSF?  Not a problem.  I
have read RMS's reasoning for that and I think he has some good points.


On Tue, 2003-12-16 at 23:50, Casey Marshall wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> >>>>> "Ryan" == r senior <address@hidden> writes:
> 
> Ryan> Sorry Casey..I should have CC'd the list- I have read through
> Ryan> about half of it and have noticed some typos etc (is the Texinfo
> Ryan> source somewhere?).  Is there a list of things somewhere of
> Ryan> things that need be added?  Also has there been any thought
> Ryan> given to a more tutorial type of manual, or changing the current
> Ryan> one to allow for more examples and explanations?
> 
> The Texinfo source is in CVS, but that is still down/untrustworthy due
> to the recent compromise of Savannah (although I doubt someone would
> put trojans into documentation, unless it was a virulent meme). If you
> want a recent copy I can mail you one.
> 
> We'd like to fix typos. Yes, yes indeed ;)
> 
> There were some messages here a while ago about how the examples were
> somewhat confusing, because many of them go for brevity rather than
> absolute correctness. I don't like having confusing documentation, so
> if you have suggestions about how to make the documentation clearer
> please mention them. My original intention was to structure the manual
> by primitive -- ciphers, hashes, etc. -- with a brief outline of what
> you needed to know to use each, and to let the JavaDocs handle the
> minutiae of the API. Popular opinion seems to indicate that it doesn't
> work that well, however.
> 
> A tutorial would be a great idea, but I still very much want a basic,
> English overview of the library.
> 
> Also note that if you are thinking of contributing anything major we
> need a copyright assignment, unless the rules are different for
> documentation. But don't let that stop you from publishing anything on
> your own.
> 
> Cheers,
> 
> - -- 
> Casey Marshall || address@hidden
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.3 (GNU/Linux)
> Comment: Processed by Mailcrypt 3.5.7 <http://mailcrypt.sourceforge.net/>
> 
> iD8DBQE/3+6QgAuWMgRGsWsRArx7AJ9uLzsqh/xJOPHeltpWzsvJu0DP/gCeOvMf
> 8ExAcl8jBMwzvDMd21lyUT8=
> =N2Ob
> -----END PGP SIGNATURE-----





reply via email to

[Prev in Thread] Current Thread [Next in Thread]