Re: [boost] Legal problem with Stackoverflow contribution under the "Creative Commons Attribution Share Alike 3.0" license

Subject: Re: [boost] Legal problem with Stackoverflow contribution under the "Creative Commons Attribution Share Alike 3.0" license
From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2018-02-21 13:24:27

On Wed, Feb 21, 2018 at 4:13 AM, Paul A. Bristow via Boost <
boost_at_[hidden]> wrote:

> > -----Original Message-----
> > From: Boost [mailto:boost-bounces_at_[hidden]] On Behalf Of Nevin
> Liber via Boost
> > Sent: 20 February 2018 16:52
> > To: boost_at_[hidden]
> > Cc: Nevin Liber
> > Subject: Re: [boost] Legal problem with Stackoverflow contribution under
> the "Creative Commons Attribution Share Alike
> > 3.0" license
> >
> > On Tue, Feb 20, 2018 at 10:39 AM, Karen Shaeffer via Boost <
> > boost_at_[hidden]> wrote:
> >
> > > You obviously didn't act to obscure anything. But Dominique has said
> such
> > > software has flagged the code. Enough said. The rational path is to
> just
> > > rewrite the code and move on. Honest mistakes happen in code all the
> time.
> >
> > Most of us are not lawyers.  None of us are lawyers representing Boost
> as a
> > legal entity.
> >
> > The rationale path is to bring this up with the steering committee, who
> can
> > consult with Boost's legal representation if they deem it necessary, and
> > get back to us with what we should do now and in the future.
>
> +1
>
> Paul
>
> PS I think Niall is right on this, but it's a useful test case, and sets a
> precedent.
>

-1

My slack response about this:

"There’s no point in getting the BSC involved (unless you want to wait
around for some indefinite amount of time for an answer). Just contact the
SFC directly. The SFC’s lawyers are likely to tell you the same thing that
we already know. That’s it’s a possible concern. And that it’s up to you to
decide what to do given that there’s a concern, even if minor, because it’s
not their job to make your decision for you. Hence, it saves everyone time
and effort to just deal with it now."

Additionally there are at least two ways to deal with it: rewrite the code
in question with a new license, obtain permission to use the code with a
new license. Both of which naturally fell out of this conversation instead
of the likely conversation with the SFC. So.. good job everyone :-)

-- 
-- Rene Rivera
-- Grafik - Don't Assume Anything
-- Robot Dreams - http://robot-dreams.net