zsh-users
 help / color / mirror / code / Atom feed
From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: Opensource.com Zsh article
Date: Thu, 19 Sep 2019 17:06:47 -0700	[thread overview]
Message-ID: <00dc62c7-81f0-636d-5373-40138c3befa6@eastlink.ca> (raw)
In-Reply-To: <CAH+w=7aDAMBLFawbretdKMpY=5LFdozHAc6AjHLL=H8Pq7MM=g@mail.gmail.com>

On 2019-09-19 3:59 p.m., Bart Schaefer wrote:
> On Thu, Sep 19, 2019 at 3:34 PM Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
>> 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?
That's exactly what I'm asking.
> I believe Ray means that Apple copies the code and begins publishing
> it as "zsh", using their size and influence to declare that theirs is
> now "the" authoritative version of the shell.
Yes, some scenario like that.  Anyway it was only the most general 
question, I hadn't meant to dive into some hard situation.   But as an 
example, you can see that if  Apple did decide that zsh would become an 
essential component of their universe, that they'd want complete control 
of it, and thus be tempted to more or less brush you and the crew 
aside.  No malice it's just that you can't imagine Tim Cook asking you 
guys for permission to change something.  I wonder how that would play 
out.  Meanwhile bash rests on a single pair of shoulders; good health to 
Chet ;-)


  reply	other threads:[~2019-09-20  0:07 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 [this message]
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=00dc62c7-81f0-636d-5373-40138c3befa6@eastlink.ca \
    --to=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).