www-legal-discuss mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Roman Shaposhnik <ro...@shaposhnik.org>
Subject Re: Is GitHub forking subject to clause 4b?
Date Wed, 04 Jan 2017 00:05:39 GMT
On Mon, Jan 2, 2017 at 6:07 PM, Roy T. Fielding <fielding@gbiv.com> wrote:
> No, no, no, no, ...
>
> -1
>
> First, this public discussion list is not where we decide to make changes to
> our legal FAQ.  We have an internal list for that, managed by our VP, and
> checked by our lawyers.
>
> Second, that answer is wrong in almost all cases (e.g., the vast majority of
> changes to existing files are not sufficient to attain a separate copyright,
> meaning that suggested addition of a new copyright notice is dubious at best).
> We certainly don't want to recommend the addition of copyright notices
> when we are making significant efforts to exclude them from contributions.
>
> Third, the license already says what needs to be said.  We don't define
> what a prominent notice "is", exactly, because it will depend on the nature of
> the change.  For example, a simple one-liner might have a one-line comment
> next to it indicating why it was changed. We didn't want to define (limit)
> that phrase in the license when it was written, and still don't want to now.
> It is a notice that happens to be prominent.  It's purpose is to alert readers.
> That's all. It can even be accomplished external to the file itself (and note
> that we don't define what "file" means either).
>
> Finally, enough with the Github nonsense. When people fork our products they
> have to do a lot of things to avoid infringing our trademarks and avoid
> confusing downstream recipients of that software.  We are not going to list
> them because it will depend as much on the person's intent and context as it
> does on the extent of changes in relation to the specific product in question.

Thank you! That was my point all along when this thread got started:
intent/context
is everything here.

Thanks,
Roman.

---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org


Mime
View raw message