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 16:08:39 +0000	[thread overview]
Message-ID: <740d5b56-50df-4eb7-afa7-dc0d73000817@www.fastmail.com> (raw)
In-Reply-To: <5349aa4a-299f-76dd-01a1-a4e9e99d7191@eastlink.ca>

Ray Andrews wrote on Thu, 19 Sep 2019 01:43 +00:00:
> On 2019-09-18 3:37 p.m., Martijn Dekker wrote:
> > Apple has plenty of in-house manpower and expertise to take over zsh 
> > development if the need should ever arise. 
> 
> How would that work in practice?  I mean a 'takeover' wouldn't seem to 
> be desirable but a contribution of resources  might be. Who has the last 
> word in these things?

Anyone can send patches.  If someone from Apple starts sending many
good patches, they'll get commit access in the ordinary way.

Taking over the project would require the consent of the existing
maintainers.  However, anyone can fork the project at any time for any
reason, provided they rebrand their fork (= not call it "zsh").

Apple can also help in other ways, for example, by assigning someone
to monitor zsh-users@ and answer questions there, to help with the
increased workload once their users are on zsh.

Cheers,

Daniel

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

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=740d5b56-50df-4eb7-afa7-dc0d73000817@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).