zsh-users
 help / color / mirror / code / Atom feed
From: "Daniel Shahaf" <d.s@daniel.shahaf.name>
To: "Ray Andrews" <rayandrews@eastlink.ca>, zsh-users@zsh.org
Subject: Re: Opensource.com Zsh article
Date: Thu, 19 Sep 2019 22:33:14 +0000	[thread overview]
Message-ID: <a93a6216-02f6-4051-8bb4-ed185a5e2024@www.fastmail.com> (raw)
In-Reply-To: <63509007-0773-58c7-7707-147b212ee459@eastlink.ca>

Ray Andrews wrote on Thu, 19 Sep 2019 19:40 +00:00:
> On 2019-09-19 11:04 a.m., Daniel Shahaf wrote:
> > Ray Andrews wrote on Thu, 19 Sep 2019 17:32 +00:00:
> >> On 2019-09-19 9:08 a.m., Daniel Shahaf wrote:
> >>>
> >>> What's your attacker model?  I.e., what do you fear Mallory¹ might do
> >>> without our consent, that we need to prepare to counter?
> 
> No attacker, I'm just curious as to how such a scenario would work out.  
> Were it the case that some commercial entity decided to take over a 
> project against the wishes of the traditional maintainers, how would it 
> be resolved?  I hardly expect this to happen with zsh but such a thing is
> conceivable.

As I said, the answer to your question depends on what your question
actually means to you.  What _exactly_ is it that you think the
commercial entity might do in order to "take over" a project?

For example, if your scenario is that Elvis would push commits to zsh's
repository without permission, the answer is that he can't.  He doesn't
have a username and password for that repository.  That's just like
saying he can't get to your living room because he doesn't have the key
to your front door.

If that's not the scenario you were concerned about, do clarify.

> I guess GPL makes it unlikely that an open source project could ever
> be privatized, still someone as big as Apple could be determined to
> have their way vis a vis some change or other.  Just curious.

First of all, zsh is not licensed under the GPL so the provisions of GPL
are irrelevant.

Second of all, GPL is a copyright license, not a system of governance.
It gives you some rights to the code, but doesn't determine how that
code is produced.  For example, it's perfectly possible for a GPL'd
project to be (or become) governed by a BDFL.

  reply	other threads:[~2019-09-19 22:34 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 [this message]
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

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=a93a6216-02f6-4051-8bb4-ed185a5e2024@www.fastmail.com \
    --to=d.s@daniel.shahaf.name \
    --cc=rayandrews@eastlink.ca \
    --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).