[tei-council] Fwd: [tei-board] licensing issues

[Piotr Bański]

In general, I believe that a single license for code, schemas and their
documentation would be a real blunder. Documentation under LGPL? Please...

I attempted to present my reasoning in this e-mail:

http://lists.village.virginia.edu/pipermail/tei-council/2011/013670.html

It may be stupid, of course, but I'd rather shove it in front of your
eyes now and wait to be told so than have a feeling that we may be
missing something important.

best,

  P.

On 28/09/11 15:34, Laurent Romary wrote:
> You guys are always so quick.... I was stuck in the middle of the river not understanding why CC-By, which is what is aimed at with BSD is incompatible with GPL (in a context where we seem not to care about GPL). Should not we make a recommendation along principles and make explicit that CC-BY and BSD are two options, and let the board finalize. Or should we vote on one or the other?
> 
> 
> Le 28 sept. 2011 à 14:55, Martin Holmes a écrit :
> 
>> So this is the proposal:
>>
>> The TEI Guidelines, including schemas or documentation generated from 
>> them, associated processing tools and stylesheets, exemplars, and test 
>> files, should be released under a 2-clause BSD license.
>>
>> (The 2-clause license is the "Simplified BSD License" or "FreeBSD License".)
>>
>> I vote in favour.
>>
>> Cheers,
>> Martin
>>
>> On 11-09-28 05:25 AM, Sebastian Rahtz wrote:
>>>
>>> On 28 Sep 2011, at 13:12, Lou Burnard wrote:
>>>>> so which of you three were going to convey this to Council, I wonder? never mind.
>>>>
>>>> I'm not sure who "you three" are, but I'm guessing it's Laurent's job
>>>> formally to convey Board decisions to the Council
>>>
>>> the chair of the Board also sits, ex officio, on the Council.
>>>
>>>> "all TEI stuff which the Consortium produces" is a rather vague concept.
>>>
>>> it is. sorry
>>>
>>>> In particular it cannot apply prospectively surely? If (perhaps as a
>>>> result of the ongoing futures debate) the Consortium gets into some
>>>> other line of business -- say developing courseware -- it might want to
>>>> licence such activities differently.
>>> true.
>>>
>>> s/TEI stuff/The TEI Guidelines, including schemas or documentation generated from them, associated processing tools and stylesheets, exemplars, and test files/
>>>
>>>>
>>>> I think the proposal needs to be rather more precisely formulated before
>>>> it can be voted on,
>>>>
>>>
>>> see above. is there a category you have in mind to _exclude_, apart from courseware?
>>>
>>> --
>>> Stormageddon Rahtz
>>> Head of Information and Support Group
>>> Oxford University Computing Services
>>> 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431
>>>
>>> Sólo le pido a Dios
>>> que el futuro no me sea indiferente
>>>
>>> _______________________________________________
>>> tei-council mailing list
>>> tei-council at lists.village.Virginia.EDU
>>> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
>>>
>>> PLEASE NOTE: postings to this list are publicly archived
>> _______________________________________________
>> tei-council mailing list
>> tei-council at lists.village.Virginia.EDU
>> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
>>
>> PLEASE NOTE: postings to this list are publicly archived
> 
> Laurent Romary
> INRIA & HUB-IDSL
> laurent.romary at inria.fr
> 
> 
> 
> _______________________________________________
> tei-council mailing list
> tei-council at lists.village.Virginia.EDU
> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
> 
> PLEASE NOTE: postings to this list are publicly archived
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4054 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.village.Virginia.EDU/pipermail/tei-council/attachments/20110928/ccdac992/attachment.bin