Re: [boost] Transfer of Maintenance Rights

Subject: Re: [boost] Transfer of Maintenance Rights
From: Stewart, Robert (Robert.Stewart_at_[hidden])
Date: 2010-03-25 12:20:31

Phil Endecott wrote:
> Stewart, Robert wrote:
> >
> > By submitting a library to Boost, you agree to put the
> > library and its
> > documentation under a Boost-compatible license, if it is accepted.
>
> I just wanted
> to point out that submissions really ought to be under the Boost
> license (and I guess not just 'a Boost-compatible license') when they

I'm not sure it is required that they use the Boost License, though perhaps we could phrase that as, "By submitting a library to Boost, you agree to put the library and its documentation under the Boost License, at least, if it is accepted."

> are submitted, not when they are accepted.  As far as I
> recall this has been what has happened in the past.

I wasn't sure I could say that.  What is an author to do if their library is rejected and they want to put it under a different license later?  Can they really rescind the freedom of the Boost License and replace it with another?  My guess is no.

> > we encourage you to make constant improvements.
>
> As someone else has pointed out, sometimes code can actually be
> declared "finished"!

I addressed that in another reply in this thread.

_____
Rob Stewart                           robert.stewart_at_[hidden]
Software Engineer, Core Software      using std::disclaimer;
Susquehanna International Group, LLP  http://www.sig.com

IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.