|
Boost : |
From: Andrey Semashev (andrey.semashev_at_[hidden])
Date: 2024-07-18 22:52:34
On 7/19/24 01:45, René Ferdinand Rivera Morell wrote:
> On Thu, Jul 18, 2024 at 5:41â¯PM Andrey Semashev via Boost
> <boost_at_[hidden]> wrote:
>>
>> On 7/19/24 01:40, René Ferdinand Rivera Morell wrote:
>>> On Thu, Jul 18, 2024 at 5:34â¯PM Andrey Semashev via Boost
>>> <boost_at_[hidden]> wrote:
>>>>
>>>> On 7/19/24 01:24, René Ferdinand Rivera Morell wrote:
>>>>> On Thu, Jul 18, 2024 at 5:18â¯PM Andrey Semashev via Boost
>>>>> <boost_at_[hidden]> wrote:
>>>>>>
>>>>>> Or just reject the new logo along with its terms of use and stick with
>>>>>> the current one.
>>>>>
>>>>> I'm confused. How does the current logo not have the same, or worse,
>>>>> re-use license problems in your oppinion?
>>>>
>>>> I'm assuming, Boost is in its rights to distribute the current logo
>>>> under BSL. Because that is what's being communicated to users on every
>>>> page that says it's distributed under BSL. Let alone the official Boost
>>>> packages themselves, which contain the license text and the logo. And
>>>> it's been this way for decades.
>>>>
>>>> If this is not the case then we have a major legal issue and should
>>>> obtain the license ASAP or remove the logo. In which case, my stance
>>>> wrt. the current logo is pretty much the same as what I said about the
>>>> proposed new logo.
>>>
>>> We've had "a major legal issue" for 18 years with regards to the logo.
>>
>> Replacing one legal issue with another is not the solution.
>
> True. But we can resolve the issue more readily with a new logo.
> Because we don't have to fix 18 years worth of misuse with a new one.
I asked before whether there were attempts to fix the legal issue with
the current logo, and got no reply. So I'm assuming one of the three:
- There is no issue
- Noone was aware of the issue
- Noone bothered to fix the issue
The 18 year delay has no bearing in either of these cases. So we could
fix this as readily as with the new logo. Or at least try.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk