On Fri, Nov 26, 2010 at 11:20:36AM +0100, Mounir IDRASSI wrote:
> Contribution are usually done by sending a patch to r...@openssl.org. The
> subject of the email must start with "[PATCH]".
> The patch should be against the latest stable sources or CVS head of the
> branch/branches you are targeting (0.9.8x, 1.0.0x or 1.0.1x).
> I hope this will help you enrich OpenSSL with this interesting engine.
A comment on code contributions. The pace at which OpenSSL's code has
evolved has far outstipped the evolution of the documentation. I think
this needs to stop.
Therefore, in my humble view, contributions that introduce new public
interfaces, or features should not be adopted into the OpenSSL code-base
as a matter of policy unless said contributions include documentation
contributions that fully describe the new interfaces or features.
There should also be some effort to organically fill in the documentation
gaps for past interfaces and features, but the starting point is to
ensure that no new gaps are introduced. So I hope that the OpenCL
engine contribution includes appropropriate documentation both public
and internal.
I have to reason to assume one way or the other, but *if* the
software is not sufficiently documented I propose that it not be
adopted unless someone on the OpenSSL team decides that the code is
sufficiently compelling for him or her to take ownership and complete
the documentation.
--
Viktor.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager majord...@openssl.org
