Hello,

is this “improvement” now concluded-à-la-consensus?

If it is not concluded yet, which conditions shall be met in order to
have a decision?

Greetings
  Дилян

On Thu, 2020-12-10 at 14:02 -0800, Quanah Gibson-Mount wrote:
> Here's a draft of an IPR notice for Cyrus SASL as we discussed in the
> last 
> meeting and I assume it could be used similarly with Cyrus IMAPD:
> 
> ---------------------------------------------------------------------
> Files containing patches representing significant blocks of new code
> (10 
> lines or greater) must include a notice of origin:
> 
>     The attached patch file is derived from Cyrus SASL Software. All
> of the 
> modifications to Cyrus SASL Software represented in the following
> patch(es) 
> were developed by <YOUR NAME> <YOUR-EMAIL-ADDRESS>. I have not
> assigned 
> rights and/or interest in this work to any party.
> 
> This notice must be followed by an appropriate rights statement.
> 
> description of these others works. The description should include
> specific 
> references to the location where these works can be obtained, such as
> URL 
> to their location on the Internet.
> 
> If you have assigned rights and/or interest in this work to another
> party, 
> such as your employer (possibly through your employment agreement),
> you 
> must state which rights you have assigned and to whom. For instance,
> "By 
> virtue of my employment agreement with EMPLOYER-NAME, I have assigned
> my 
> rights and interest in this work to EMPLOYER-NAME."
> 
> Below is an example notice for someone making a contribution on
> behalf of 
> your employer:
> 
> modifications to Cyrus SASL Software represented in the following
> patch(es) 
> were developed by <YOUR-EMPLOYER>. <YOUR-EMPLOYER> has not assigned
> rights 
> and/or interest in this work to any party. I, <YOUR-NAME> am
> authorized by 
> <YOUR-EMPLOYER>, my employer, to release this work under the
> following 
> terms.
> 
> This notice must be followed by an appropriate rights statement.
> 
> For small modifications (bug fixes, minor enhancements, etc.), we
> suggest 
> the modifications be placed into the public domain so that they can
> be 
> freely incorporated into Cyrus SASL Software (as well as other
> works).
> 
>     I, <YOUR NAME>, hereby place the following modifications to Cyrus
> SASL 
> Software (and only these modifications) into the public domain.
> Hence, 
> these modifications may be freely used and/or redistributed for any
> purpose 
> with or without attribution and/or other notice.
> 
> A corporate example:
> 
>     <YOUR-EMPLOYER> hereby place the following modifications to Cyrus
> SASL 
> Software (and only these modifications) into the public domain.
> Hence, 
> these modifications may be freely used and/or redistributed for any
> purpose 
> with or without attribution and/or other notice.
> 
> While you may use the above for large modifications as well, you may
> desire 
> to maintain rights in your modifications. However, to ensure license 
> compatibility, we require all contributions (your modifications) to
> be 
> provided under compatible terms. Hence, we suggest the following
> statement 
> be used:
> 
>     The attached modifications to Cyrus SASL Software are subject to
> the 
> following notice:
> 
>     Copyright <YEAR> <YOUR NAME>
>     Redistribution and use in source and binary forms, with or
> without 
> modification, are permitted only as authorized by the Cyrus SASL
> Software 
> license.
> 
> By making this statement, you are allowing redistribution and use of
> your 
> modifications under the same terms as Cyrus SASL Software itself.
> 
> Alternative rights statements will not generally be accepted.
> ---------------------------------------------------------------------
> 
> Regards,
> Quanah
> 
> --
> 
> Quanah Gibson-Mount
> Product Architect
> Symas Corporation
> Packaged, certified, and supported LDAP solutions powered by
> OpenLDAP:
> <http://www.symas.com>
> 
> ------------------------------------------
> Cyrus: Devel
> Permalink:
> https://cyrus.topicbox.com/groups/devel/T9066d56fe70247f8-M01950c8eec6b4cea8b9a13f5
> Delivery options:
> https://cyrus.topicbox.com/groups/devel/subscription



------------------------------------------
Cyrus: Devel
Permalink: 
https://cyrus.topicbox.com/groups/devel/T9066d56fe70247f8-M2ce253aeae25cbf9f20ed910
Delivery options: https://cyrus.topicbox.com/groups/devel/subscription

Reply via email to