Sounds good to me.  Thanks for chasing up existing style authors for
re-licensing.

Regards,
Rob.

On 3 January 2012 23:55, Charles Parnot <[email protected]> wrote:
> I am all for it. It seems very reasonable, and while it may keep a few styles 
> out (?), it makes it much easier to use those styles without extra friction.
>
> charles
>
> On Jan 3, 2012, at 3:20 PM, Rintze Zelle wrote:
>
>> Dear all,
>>
>> As of this moment, all the CSL styles in the style repository at 
>> https://github.com/citation-style-language/styles are registered under a 
>> single license, using the exact string "This work is licensed under a 
>> Creative Commons Attribution-Share Alike 3.0 License: 
>> http://creativecommons.org/licenses/by-sa/3.0/";.
>>
>> I added the license to styles that did not carry one, updated older versions 
>> of the license, and replaced ported variants by the unported version. I got 
>> permission of the style authors who had released their styles under by-nc-sa 
>> licenses to switch to by-sa.
>>
>> Going forward I would like to require that any new style added to the 
>> repository should use Creative Commons Attribution-Share Alike (I already 
>> included this in our requirements: 
>> https://github.com/citation-style-language/styles/wiki/Style-Requirements ).
>>
>> If anybody has an issue with any of these changes, please let me know,
>>
>> Rintze
>>
>> On Tue, May 31, 2011 at 8:25 AM, Rintze Zelle <[email protected]> wrote:
>> On Mon, May 30, 2011 at 8:01 PM, Bruce D'Arcus <[email protected]> wrote:
>> > The main question is whether CC-licenses are applicable at all to 
>> > something like
>> > CSL styles, or whether we should pick a software license. If everybody is
>> > comfortable with CC-BY-SA, it'd like to make it the requirement for styles 
>> > hosted
>> > in the github repo.
>> >
>> > We touched on this before, but we never came to a clear conclusion. We 
>> > could really
>> > use some advice from somebody legally schooled.
>>
>> Yes; and preferably someone with experience with these specific
>> licenses, and understanding of copyright law.
>>
>> I just came across this: 
>> http://discovery.ac.uk/files/pdf/Licensing_Open_Data_A_Practical_Guide.pdf 
>> (via http://twitter.com/#!/ostephens/statuses/75466458326511616 )
>>
>> The JISC people are obviously interested in scientific publishing, so they 
>> might not mind giving some advice.
>> ------------------------------------------------------------------------------
>> Write once. Port to many.
>> Get the SDK and tools to simplify cross-platform app development. Create
>> new or port existing apps to sell to consumers worldwide. Explore the
>> Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
>> http://p.sf.net/sfu/intel-appdev_______________________________________________
>> xbiblio-devel mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
>
> --
> Charles Parnot
> [email protected]
> twitter: @cparnot
> http://mekentosj.com
>
>
>
> ------------------------------------------------------------------------------
> Write once. Port to many.
> Get the SDK and tools to simplify cross-platform app development. Create
> new or port existing apps to sell to consumers worldwide. Explore the
> Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
> http://p.sf.net/sfu/intel-appdev
> _______________________________________________
> xbiblio-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/xbiblio-devel

------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual 
desktops for less than the cost of PCs and save 60% on VDI infrastructure 
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
_______________________________________________
xbiblio-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xbiblio-devel

Reply via email to