From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4603 invoked by alias); 21 Apr 2013 11:56:01 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 31312 Received: (qmail 10278 invoked from network); 21 Apr 2013 11:55:58 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE, SPF_HELO_PASS autolearn=ham version=3.3.2 Received-SPF: none (ns1.primenet.com.au: domain at bewatermyfriend.org does not designate permitted sender hosts) From: Frank Terbeck To: Ramkumar Ramachandra Cc: ZSH Workers Subject: Re: Out-of-date mirror on GitHub In-Reply-To: (Ramkumar Ramachandra's message of "Sun, 21 Apr 2013 16:44:22 +0530") References: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) Date: Sun, 21 Apr 2013 13:54:18 +0200 Message-ID: <87ehe45cb9.fsf@ft.bewatermyfriend.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Df-Sender: [pbs]MDExNTM1 Ramkumar Ramachandra wrote: > I think it's nice for every project to have an up-to-date mirror on > GitHub, so contributors can maintain a fork and regularly send patches > upstream (via email in this case). [...] I always thought that the nice thing about decentralised systems like git was that they allowed contributors to keep forks even without a central place like github. Github is only useful if you want visibility for your changes and even then you can just publish a repo with your own account. On github, bitbucket or $yourserviceproviderhere, it doesn't matter. I actually think having more than one canonical source (and one that might be out of date as we can see) would actually hurt. Personally, I do have a mirror of the code repository on my account. But I don't want to see push requests or forks or any of that. I won't promise, that it's up-to-date. I won't even promise, that it's there tomorrow... I only use it to, from time to time, show someone something I've worked on. Since any real changes have to go through the mailing lists to pick up X-Seq: header numbers=C2=B9 for later reference anyway, I think everyone is better off working on a clone (which already _is_ a fork) of the canonical zsh code repository at sourceforge, and using git's excellent mail-workflow related tools (like "git format-patch", "git send-email" and "git am"). Regards, Frank =C2=B9 If you wonder what those are, you might want to take a look at the README of https://github.com/ft/zsh-am, which explains zsh's traditional development style and a way to cope with it with the minimal amount of pain from an integrator's point of view.