License in new files

[Simo Sorce]

On Tue, 2020-04-14 at 18:35 +0100, Alexey Melnikov wrote:
> Hi Simo,
> 
> On 13/04/2020 15:18, Simo Sorce wrote:
> 
> > Hello,
> > In https://github.com/cyrusimap/cyrus-sasl/pull/598 I asked a question
> > given I forgot to fix (C) in files we recently merged.
> > 
> > The question is simply: what license needs to be set on files?
> > I personally prefer to give a very liberal license like 2 clause BSD,
> > when a non-copyleft work is involved. Generally that license is
> > compatible with anything else already on the work and won't conflict.
> > 
> > Is there any rule on (C) on net new files in cyrus-sasl ?
> 
> I would just cut & paste license from something like plugins/scam.c (and 
> update appropriately):

Unfortunately the text you pasted below is like the original 3-clause
bsd + advertising clause which is a bit obnoxious.

Plus it list the (C) holder as CMU, which is clearly not the case for
software I've written.

I could replace the (C) line with my authorship, but still clause 4
would be clumsy in that case, why would I require people to advertise
CMU as the author for software that was not authored by CMU ?

It'd be much easier if a revised 2 or less clauses BSD was used w/o
advertising and (C) was that of the actual authors.

If I am allowed to do that for the files *I* contribute I'd be all set.

If not it would be nice to have a clear idea of what are the (C) rules
for contributions to cyrus-sasl...

> /*
>   * Copyright (c) 2009-2016 Carnegie Mellon University.  All rights 
> reserved.
>   *
>   * Redistribution and use in source and binary forms, with or without
>   * modification, are permitted provided that the following conditions
>   * are met:
>   *
>   * 1. Redistributions of source code must retain the above copyright
>   *    notice, this list of conditions and the following disclaimer.
>   *
>   * 2. Redistributions in binary form must reproduce the above copyright
>   *    notice, this list of conditions and the following disclaimer in
>   *    the documentation and/or other materials provided with the
>   *    distribution.
>   *
>   * 3. The name "Carnegie Mellon University" must not be used to
>   *    endorse or promote products derived from this software without
>   *    prior written permission. For permission or any other legal
>   *    details, please contact
>   *      Carnegie Mellon University
>   *      Center for Technology Transfer and Enterprise Creation
>   *      4615 Forbes Avenue
>   *      Suite 302
>   *      Pittsburgh, PA  15213
>   *      (412) 268-7393, fax: (412) 268-7395
>   *      innovation at andrew.cmu.edu
>   *
>   * 4. Redistributions of any form whatsoever must retain the following
>   *    acknowledgment:
>   *    "This product includes software developed by Computing Services
>   *     at Carnegie Mellon University (http://www.cmu.edu/computing/)."
>   *
>   * CARNEGIE MELLON UNIVERSITY DISCLAIMS ALL WARRANTIES WITH REGARD TO
>   * THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
>   * AND FITNESS, IN NO EVENT SHALL CARNEGIE MELLON UNIVERSITY BE LIABLE
>   * FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
>   * WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN
>   * AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING
>   * OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
>   */
> 
> I think it is 2 clause BSD.
> 
> Best Regards,
> 
> Alexey
> 
> 

-- 
Simo Sorce
RHEL Crypto Team
Red Hat, Inc