[sword-devel] Creative Commons - updating the verbatim requirements for DistributionLicense values in module .conf files

[David Haslam]

Hi DM,

I think you misunderstood me. I never said we have no existing modules with a CC license. It's quite clear that we do.
I said "It's not about existing modules."
i.e. We don't have to change any released modules just because new CC licenses have since appeared.

What I'm after is to clarify how we word the DL for any new module for which a CC license should apply.
Our instructions state that the DL should be one of the listed items verbatim.
We merely need to change the verbatim wordings to match each of the latest CC licenses. It's not a difficult tehcnical task.

However, the reason I'm not updating the table "on my own bat" is precisely because I'm not a copyright lawyer.
i.e. I do not wish to expose CrossWire to legal risk, were I to get things wrong on this score.
Maybe Troy can advise? After all, any possible future disputes about breach of DL would have to be referred to him.

Best regards,

David

Sent with [ProtonMail](https://protonmail.com) Secure Email.

> -------- Original Message --------
> Subject: Re: [sword-devel] Creative Commons - updating the verbatim requirements for DistributionLicense values in module .conf files
> Local Time: 29 December 2017 4:54 PM
> UTC Time: 29 December 2017 16:54
> From: dmsmith at crosswire.org
> To: David Haslam <dfhdfh at protonmail.com>
>
> Then if we have no CC modules, just remove the references to them as supported entries.
>
>> On Dec 29, 2017, at 11:48 AM, David Haslam <dfhdfh at protonmail.com> wrote:
>>
>> This is not about existing released modules.
>>
>> It's about updating our advice/instructions for anyone making a new or updated module.
>>
>> We should update the details in our wiki page without waiting for any other activity.
>>
>> Best regards,
>>
>> David
>>
>> Sent with [ProtonMail](https://protonmail.com/) Secure Email.
>>
>>> -------- Original Message --------
>>> Subject: Re: [sword-devel] Creative Commons - updating the verbatim requirements for DistributionLicense values in module .conf files
>>> Local Time: 29 December 2017 4:33 PM
>>> UTC Time: 29 December 2017 16:33
>>> From: dmsmith at crosswire.org
>>> To: David Haslam <dfhdfh at protonmail.com>, SWORD Developers' Collaboration Forum <sword-devel at crosswire.org>
>>>
>>> Have any modules been released with CC? Chris added these licenses as “supported.” I don’t see the point in updating the list to support what isn’t reality. When we negotiate new content that has a particular license, we should update it then.
>>>
>>> DM
>>>
>>>> On Dec 29, 2017, at 10:02 AM, David Haslam <dfhdfh at protonmail.com> wrote:
>>>>
>>>> Dear all,
>>>>
>>>> It's imperative that we provide accurate advice to SWORD module makers.
>>>>
>>>> Please visit https://crosswire.org/wiki/DevTools:conf_Files#Copyright_.26_Licensing_related_elements
>>>>
>>>> Since this table was constructed a long time ago, there have been several new versions released for all the Creative Commons licenses.
>>>>
>>>> Please visit http://creativecommons.org/ for details.
>>>>
>>>> Our verbatim strings for CC licenses are no longer adequate. They need to be updated to match the latest license versions.
>>>>
>>>> Please would someone in CrossWire that "knows the ins and outs" please attend to this urgent task.
>>>>
>>>> Best regards,
>>>>
>>>> David
>>>>
>>>> PS. This is not the first time that I have made such a request.
>>>>
>>>> Sent with [ProtonMail](https://protonmail.com/) Secure Email.
>>>>
>>>> _______________________________________________
>>>> sword-devel mailing list: sword-devel at crosswire.org
>>>> http://www.crosswire.org/mailman/listinfo/sword-devel
>>>> Instructions to unsubscribe/change your settings at above page
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.crosswire.org/pipermail/sword-devel/attachments/20171229/0952cbf9/attachment-0001.html>