Re: Windows Cryptography API - Public Key Authentication extensions

[Andreas Schneider <asn@xxxxxxxxxxxxxx>]

On Friday, June 10, 2011 17:33:22 you wrote:
> Hi Gearoid,
> 
> First thank you for going into the process of publishing changes
> upstream, we really appreciate it. Token support is also very
> appreciated, since it's a hot topic right now. We are working to
> implement PKCS#11 tokens, and having support for native windows API is
> complementary.
> 
> We do not have very strict guidelines or rules on the code inclusion, we
> can say that empirically they are the following:
> 
> - Copyright is kept by the committer, at least for nontrivial (more than
> a few lines) changes. Here it would be HP or yourself, depending on your
> guidelines

Hi Gearoid,

we setup a copyright policy for libssh and we're asking for contributions to 
be made under the personal copyright of the contributor, instead of a 
corporate copyright.

There are some reasons for the establishment of this policy:

Individual copyrights make copyright registration in the US a simpler process.

If libssh is copyrighted by individuals rather than corporations, decisions 
regarding enforcement and protection of copyright will, more likely, be made 
in the interests of the project, and not in the interests of any corporation’s 
shareholders.

If we ever need to relicense a portion of the code contacting individuals for 
permission to do so is much easier than contacting a company.


Let me know if you have further questions and if we can hope with your 
internal process.


Cheers,


	-- andreas