From: Walter Bright <walter@digitalmars.com>
To: Iain Buclaw <ibuclaw@gdcproject.org>
Cc: Jeff Law <law@redhat.com>, gcc-patches <gcc-patches@gcc.gnu.org>,
Joseph Myers <joseph@codesourcery.com>,
Walter Bright <walter@walterbright.com>,
Andrei Alexandrescu <andrei@erdani.com>
Subject: Re: [PATCH v3 1/14] D: The front-end (DMD) language implementation and license.
Date: Fri, 06 Oct 2017 08:44:00 -0000 [thread overview]
Message-ID: <e7d00208-e3c4-a39a-af1d-2ad91c23c157@digitalmars.com> (raw)
In-Reply-To: <CABOHX+eMYv-ekdNcpmzK53z86DCT0NBVA7onBMxDtXatxjioLA@mail.gmail.com>
On 10/6/2017 1:34 AM, Iain Buclaw wrote:
> On 6 October 2017 at 02:57, Walter Bright <walter@digitalmars.com> wrote:
>>
>>
>> On 10/5/2017 3:59 AM, Iain Buclaw wrote:
>>>
>>> On 3 October 2017 at 23:36, Joseph Myers <joseph@codesourcery.com> wrote:
>>>>
>>>> On Tue, 3 Oct 2017, Jeff Law wrote:
>>>>
>>>>> /* Copyright (c) 2010-2014 by Digital Mars
>>>>> * All Rights Reserved, written by Walter Bright
>>>>> * http://www.digitalmars.com
>>>>> * Distributed under the Boost Software License, Version 1.0.
>>>>> * (See accompanying file LICENSE or copy at
>>>>> http://www.boost.org/LICENSE_1_0.txt)
>>>>>
>>>>> If the code was assigned to the FSF in 2011, then the FSF would have
>>>>> ownership of the code. And the FSF would be the only entity that could
>>>>> change the license (which according to your message changed to Boost in
>>>>> 2014). So something seems wrong here.
>>>>
>>>>
>>>> The standard FSF assignment would allow the contributor to distribute
>>>> their own code under such terms as they see fit.
>>>>
>>>
>>> Walter, would you mind clarifying details of your assignment? Was it a
>>> standard assignment? Did you request for any amendments?
>>
>>
>> I'm good with FSF owning their copy and it being under the GPL and Digital
>> Mars owning our copy and it being Boost licensed.
>>
>
> Out of curiosity, I did have a look at some of the tops of gofrontend
> sources this morning. They are all copyright the Go Authors, and are
> licensed as BSD. So I'm not sure if having copyright FSF and
> distributing under GPL is strictly required. And from a maintenance
> point of view, it would be easier to merge in upstream changes as-is
> without some diff/merging tool.
>
> Regards,
> Iain.
That certainly seems like a more convenient solution.
next prev parent reply other threads:[~2017-10-06 8:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-02 8:45 Iain Buclaw
2017-10-03 19:59 ` Jeff Law
2017-10-03 21:36 ` Joseph Myers
2017-10-05 10:59 ` Iain Buclaw
2017-10-06 0:57 ` Walter Bright
2017-10-06 8:34 ` Iain Buclaw
2017-10-06 8:44 ` Walter Bright [this message]
2017-10-06 12:51 ` Ian Lance Taylor
2017-10-06 12:52 ` Andrei Alexandrescu
2017-10-18 7:35 ` Iain Buclaw
2017-10-25 1:26 ` Jeff Law
2017-10-25 20:27 ` Iain Buclaw
2017-11-06 18:49 ` Iain Buclaw
2017-11-13 7:42 ` Andrei Alexandrescu
2017-11-21 9:02 ` Iain Buclaw
2018-02-17 15:08 ` Iain Buclaw
2017-10-25 0:27 ` Jeff Law
2017-11-04 19:52 ` Walter Bright
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e7d00208-e3c4-a39a-af1d-2ad91c23c157@digitalmars.com \
--to=walter@digitalmars.com \
--cc=andrei@erdani.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=ibuclaw@gdcproject.org \
--cc=joseph@codesourcery.com \
--cc=law@redhat.com \
--cc=walter@walterbright.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).