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

Re: libssh patch


Hi,

    Ok, I will suppress the brackets in config.c file.

My intention is colaborate with the community to improve the library, if you think is better, I could do the patch again, and send a mail, without any reference to Telefonica. I didn´t try use the patch to add a new Telefonica copyright.

    I wait your response and thanks for your time.

Regards.

El 06/04/2010 21:23, Aris Adamantiadis escribió:
Hi Andreas,

As told on IRC, I think that his patches are to small to be eligible to
the statute of copywritable work.
Rubben, this is of course not in the intention of minimizing your work.
What you did is cool but in my opinion not worth adding your name to
the copyright file.
I think our copyright policy against corporations is relevant anyway,
in case you'd do some other development for libssh for your company.

Do you agree that we commit your patch in these conditions ? your name
and email address would appear in the git logs.

Regards,

Aris

Andreas Schneider a écrit :
On Tuesday 06 April 2010 20:26:05 you wrote:
Hi,
Hi Rubben,

    A new feature patch.

    This has two files because I forgot one file in the first patch, sorry
if it is a problem.
that's no problem. The commit message states:

	Ruben Garcia Azuara, a Telefonica I+D SAU worker, deliver a patch to
	add OpenSSH parameters to libssh.

We have a copyright policy:

The developers of libssh have a policy of 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

http://www.libssh.org/development/

So I have to ask if you contribute this personally, else we can't accept the
patch.


	-- andreas




Follow-Ups:
Re: libssh patchAris Adamantiadis <aris@xxxxxxxxxxxx>
References:
libssh patchRuben Garcia Azuara <rubenga@xxxxxx>
Re: libssh patchAndreas Schneider <mail@xxxxxxxxxxxx>
RE: libssh patchRUBEN GARCIA AZUARA <rubenga@xxxxxx>
Re: libssh patchAndreas Schneider <mail@xxxxxxxxxxxx>
Re: libssh patchAris Adamantiadis <aris@xxxxxxxxxxxx>
Archive administrator: postmaster@lists.cynapses.org