zsh-users
 help / color / mirror / code / Atom feed
From: "Daniel Shahaf" <d.s@daniel.shahaf.name>
To: "Bart Schaefer" <schaefer@brasslantern.com>
Cc: "TJ Luoma" <luomat@gmail.com>, "Zsh MailingList" <zsh-users@zsh.org>
Subject: Re: Opensource.com Zsh article
Date: Sat, 21 Sep 2019 08:21:55 +0000	[thread overview]
Message-ID: <e78e2d7f-214c-4d23-b791-e4502b78cd01@www.fastmail.com> (raw)
In-Reply-To: <CAH+w=7b__yBMOshFYm_Xm3GHumBYQgL3ZWLBoZ9FW6zxgHVQwQ@mail.gmail.com>

Bart Schaefer wrote on Fri, 20 Sep 2019 21:51 +00:00:
> On Fri, Sep 20, 2019 at 6:34 AM Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
> >
> > To elaborate on that: if Alice maintains an open source product and Bob
> > forks it, trademarks law requires that Bob rename the product before he
> > may distribute it.
> 
> That would be true if there were actually a trademark on "zsh", but there isn't.
> 

There isn't a _registered_ trademark, that is correct — but "zsh" is a
trademark nevertheless.

Trademarks are established through use in commerce.  So long as we
continue to offer a thing called "zsh" for download, "zsh" is our
trademark.  Registration can help but is not required.

> Copyright law might come into play because of the license terms, but
> because zsh assigns copyrights on the individual files to the
> individual contributors, it would be a serious headache to try to
> bring a coherent claim.

I'm not sure that is correct — but IANAL so I can't speak with any certainty.
What I can say is that copyright law and trademark law aren't the same thing,
and that zsh doesn't "assign" copyrights on individual files — it doesn't have
those rights to begin with.

> This is probably one of the factors behind other OSS projects deciding
> to join consortia like the Apache Foundation or Mozilla.

I can't speak of Mozilla, but the Apache Software Foundation doesn't
require copyright assignment; they only require a copyright _license_
(an ICLA [1]).  They do register trademarks for some of their project
names, but not all.

Cheers,

Daniel

[1] https://www.apache.org/dev/new-committers-guide.html#cla

      parent reply	other threads:[~2019-09-21  8:23 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-17 22:29 Bart Schaefer
2019-09-18  0:39 ` TJ Luoma
2019-09-18 16:06   ` Ray Andrews
2019-09-18 16:13     ` Jérémie Roquet
2019-09-18 16:37       ` Ray Andrews
2019-09-18 16:54         ` Daniel Shahaf
2019-09-18 17:05           ` Ray Andrews
2019-09-18 17:17         ` Roman Perepelitsa
2019-09-18 19:23           ` Ray Andrews
2019-09-18 22:37     ` Martijn Dekker
2019-09-19  1:43       ` Ray Andrews
2019-09-19 16:08         ` Daniel Shahaf
2019-09-19 17:32           ` Ray Andrews
2019-09-19 18:04             ` Daniel Shahaf
2019-09-19 19:40               ` Ray Andrews
2019-09-19 22:33                 ` Daniel Shahaf
2019-09-19 22:59                   ` Bart Schaefer
2019-09-20  0:06                     ` Ray Andrews
2019-09-20  1:01                       ` TJ Luoma
2019-09-20  3:51                         ` Ray Andrews
2019-09-20 13:33                         ` Daniel Shahaf
2019-09-20 13:51                           ` Ray Andrews
2019-09-20 21:51                           ` Bart Schaefer
2019-09-20 22:08                             ` Ray Andrews
2019-09-21  8:21                             ` Daniel Shahaf [this message]

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=e78e2d7f-214c-4d23-b791-e4502b78cd01@www.fastmail.com \
    --to=d.s@daniel.shahaf.name \
    --cc=luomat@gmail.com \
    --cc=schaefer@brasslantern.com \
    --cc=zsh-users@zsh.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).