$include_dir="/home/hyper-archives/boost/include"; include("$include_dir/msg-header.inc") ?>
From: Edward Diener (eldiener_at_[hidden])
Date: 2020-01-23 22:57:45
On 1/23/2020 2:29 PM, John Maddock via Boost wrote:
>
> On 23/01/2020 19:19, Rene Rivera via Boost wrote:
>> On Thu, Jan 23, 2020 at 1:13 PM Edward Diener via Boost <
>> boost_at_[hidden]> wrote:
>>
>>> If some compiler vendor takes a version of Boost and makes changes to
>>> that version of Boost to suit the particular compiler, while
>>> distributing that version with full source code as an optional part of
>>> some release of that compiler, does this mean that the code is now
>>> proprietary for that compiler vendor ? Or does the code still remain
>>> open source so that a programmer can use the changes made to update his
>>> own version of a Boost release or provide PRs to some later release of
>>> Boost based on the code in the compiler vendor's release ?
>>>
>> Depends entirely on what license they made the changes available as.
>
> Yup, if they don't copyright the changes, then it's still all BSL, but
> they are allowed to make their changes proprietary.
>
> If you're thinking of moving changes upstream into Boost, then I suggest
> you just drop them a line and see how they feel about that.
Where would I be expected to find some indication whether they have made
their changes proprietary ? Is it required to be in each source file, or
is it required to be in some other place related to the Boost
distribution they supply, and if so where ?
I have been in contact with one of their representatives, so I will ask
him point blank about it, but I did want to know in advance if there was
any requirement they specify their copyright changes in some particular
place related to their distribution of the source code.