On Thursday, February 8, 2018 at 7:46:17 PM UTC, Niall Douglas wrote:
>
> On Thursday, February 8, 2018 at 4:32:25 PM UTC, [email protected] wrote:
>>
>> Hi,
>> In Boost 1.62.0 we saw in the following header file : 
>> boost/thread/win32/thread_primitives.hpp
>> that the function inline ticks_type __stdcall GetTickCount64emulation()
>> is a contribution coming from 
>> https://stackoverflow.com/questions/8211820/userland-interrupt-timer-access-such-as-via-kequeryinterrupttime-or-similar
>>
>
> That code was borrowed by me.
>  
>
>>
>> This causes legal problem as Stackoverflow contributiona are under the 
>> "Creative Commons Attribution Share Alike 3.0" license which is not 
>> permissive.
>>
>> Is someone aware about that?
>> Is there any remedy planned?
>>
>  
> Explanatory text is under the CCA, but code snippets are under MIT which 
> is a licence compatible with Boost. See 
> https://meta.stackexchange.com/questions/271114/code-licensing-change-for-all-se-sites
>

Looking at this again, it looks like the linked borrowed code predates the 
StackOverflow licence change.

The link back to the relevant SO page complies with the CC-BY-SA 
attribution clause. In most jurisdictions such a small snippet would be 
either uncopyrightable, or fall under fair use, so the copyleft requirement 
would not apply. But IANAL.

BTW this is hardly the only instance of code borrowed from StackOverflow in 
Boost. There are many instances, some without the attribution.

Niall

-- 
The Boost Steering Committee webpage: 
https://sites.google.com/a/boost.org/steering/
--- 
You received this message because you are subscribed to the Google Groups 
"Boost Steering Committee" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/boost-steering.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/boost-steering/d7f743fd-19c0-48d9-887c-624cbb35fc02%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to