From: Sam Halliday Date: Sun, 27 Apr 2014 18:53:33 +0000 (+0100) Subject: [Sam Halliday] Re: github mirror X-Git-Url: http://git.tremily.us/?a=commitdiff_plain;h=1fa1c24159b47c56f719afff3bfd49fac7902a4f;p=notmuch-archives.git [Sam Halliday] Re: github mirror --- diff --git a/9c/5f0c9d5aa3faddd38738aa5c3df88dd48a9ef6 b/9c/5f0c9d5aa3faddd38738aa5c3df88dd48a9ef6 new file mode 100644 index 000000000..29fc4a1d6 --- /dev/null +++ b/9c/5f0c9d5aa3faddd38738aa5c3df88dd48a9ef6 @@ -0,0 +1,201 @@ +Return-Path: +X-Original-To: notmuch@notmuchmail.org +Delivered-To: notmuch@notmuchmail.org +Received: from localhost (localhost [127.0.0.1]) + by olra.theworths.org (Postfix) with ESMTP id 1E2F7431FBD + for ; Sun, 27 Apr 2014 11:53:34 -0700 (PDT) +X-Virus-Scanned: Debian amavisd-new at olra.theworths.org +X-Spam-Flag: NO +X-Spam-Score: 2.6 +X-Spam-Level: ** +X-Spam-Status: No, score=2.6 tagged_above=-999 required=5 + tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, + FREEMAIL_FROM=0.001, RCVD_ILLEGAL_IP=3.399, RCVD_IN_DNSWL_LOW=-0.7] + autolearn=disabled +Received: from olra.theworths.org ([127.0.0.1]) + by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) + with ESMTP id NjxvyIQ6yn+m for ; + Sun, 27 Apr 2014 11:53:26 -0700 (PDT) +Received: from mail-we0-f179.google.com (mail-we0-f179.google.com + [74.125.82.179]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) + (No client certificate requested) + by olra.theworths.org (Postfix) with ESMTPS id B4A27431FBC + for ; Sun, 27 Apr 2014 11:53:25 -0700 (PDT) +Received: by mail-we0-f179.google.com with SMTP id x48so5582004wes.10 + for ; Sun, 27 Apr 2014 11:53:22 -0700 (PDT) +DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; + h=from:to:subject:user-agent:date:message-id:mime-version + :content-type; bh=gLI15lkW+YMj2etC+XrkK9EqfFvUUN9XP/bnRJEIDM8=; + b=KZELlBKKAxCCqprIw4pdaD8zUCvtURwcaSoe0J9+/QZ6vTBKgxguMrM9kztL9EajIz + h8ziI2aJT0Y8i3jFViU/CPeU3yJiznyWr8N1JTzMlSg9HkGEEcxV38I3B0HPmOomBvv+ + EJYH1m8BceNFc0JU2xgv4J1crhYehWX9UYnaclIu7iCaZRDP0AVKfavbyltckB+KD/rk + RCGzrPkwECaFKwCKyoLeK5Dyn3k7CkZVhcE/ovFcW//hJJQ0nFX8MYQfRutbJn+N5LJo + gMNUlBLrcSgGWXUSBsrJT+QPhftV+7HHxQsrJceuWfqxtuud7ObnlAVxdf++IC2QmPqI + K0ig== +X-Received: by 10.180.189.65 with SMTP id gg1mr12178432wic.56.1398624802148; + Sun, 27 Apr 2014 11:53:22 -0700 (PDT) +Received: from Samskara.home (host5-81-31-114.range5-81.btcentralplus.com. + [5.81.31.114]) by mx.google.com with ESMTPSA id + km2sm22236586wjb.13.2014.04.27.11.53.15 for + (version=TLSv1.2 cipher=RC4-SHA bits=128/128); + Sun, 27 Apr 2014 11:53:15 -0700 (PDT) +From: Sam Halliday +To: notmuch@notmuchmail.org +Subject: [Sam Halliday] Re: github mirror +User-Agent: Notmuch/0.17 (http://notmuchmail.org) Emacs/24.3.1 + (x86_64-unknown-linux-gnu) +Date: Sun, 27 Apr 2014 19:53:33 +0100 +Message-ID: <87mwf6txhu.fsf@Samskara.home> +MIME-Version: 1.0 +Content-Type: multipart/mixed; boundary="==-=-=" +X-Mailman-Approved-At: Sun, 27 Apr 2014 12:28:04 -0700 +X-BeenThere: notmuch@notmuchmail.org +X-Mailman-Version: 2.1.13 +Precedence: list +List-Id: "Use and development of the notmuch mail system." + +List-Unsubscribe: , + +List-Archive: +List-Post: +List-Help: +List-Subscribe: , + +X-List-Received-Date: Sun, 27 Apr 2014 18:53:34 -0000 + +--==-=-= +Content-Type: text/plain + +Sorry, I replied to jani and not the list... + + +--==-=-= +Content-Type: message/rfc822 +Content-Disposition: inline +Content-Transfer-Encoding: 8bit + +Return-Path: +Received: from Samskara.home (host5-81-31-114.range5-81.btcentralplus.com. + [5.81.31.114]) by mx.google.com with ESMTPSA id + gc19sm12258278wic.5.2014.04.27.10.57.25 for + (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Sun, 27 Apr 2014 + 10:57:25 -0700 (PDT) +From: Sam Halliday +To: Jani Nikula +Subject: Re: github mirror +In-Reply-To: <8761lu928m.fsf@nikula.org> +References: <87bnvn111h.fsf@Samskara.home> <8761lu928m.fsf@nikula.org> +User-Agent: Notmuch/0.17 (http://notmuchmail.org) Emacs/24.3.1 + (x86_64-unknown-linux-gnu) +Date: Sun, 27 Apr 2014 18:57:47 +0100 +Message-ID: <87sioyu02s.fsf@Samskara.home> +MIME-Version: 1.0 +Content-Type: multipart/signed; boundary="=-=-="; + micalg=pgp-sha1; protocol="application/pgp-signature" + +--=-=-= +Content-Type: text/plain + +Jani Nikula writes: +> We also maintain fairly high standards for the contributions we +> accept, so the review has a significant role in the process. + +In my experience the github pull review process is by far superior to +any other solution. If you've never done a github review, I would +strongly recommend doing one just for fun to see what you think of +it. You can basically add line comments in the code and have a +discussion on the finer points of commits. And then, to address those +comments, it's as simple as the contributor pushing to their repo again +and the review is updated. Repeat until the "merge" button is pressed +(or the equivalent git commands, of course). + +But you are correct, it would be a big change from your current +setup. + +>> Would it be possible to have a github project for notmuch? I'm certain +>> the git repositories could be synchronised easily. +> +> This part is trivial, but on its own it doesn't provide any obvious +> benefits. + +The benefit would be - perhaps - an increase in the number of patches +for you to review :-). Plus, free hosting, and easier to track down who +aims to contribute to the project. It would also expose you to a larger +audience. I find a lot of cool projects just by jumping around +interesting developers on github. + +I can only cite my own experience, but I have received a lot more +contributions (out of the blue) since moving to github than I did when I +was running repositories on savannah, sourceforge or google code. It's +just so much easier to click the "fork" button, then make some commits, +and click the "pull request" button. If I were contributing to you, it +requires having to learn your process, create diffs and then attach +them, and then after a review it means tracking down the bits of the +code you're referring to and manually reconciling that with my repo and +sending you more diffs. Using github, it's like all open source +developers agree on a basic set of common processes. + + +>> A bridge between github's issue tracker and notmuch would be entirely +>> possible: they have an API that would allow addition and removal of +>> tags, as well as editing tickets. Actually, I would probably use such a +>> thing :-) +> +> I'm sure all of this would be entirely possible; I'm not so sure it +> would be worth the effort. But hey, if someone is willing to do the +> work, patches are welcome. By email. ;) + +Heh, well I might just end up doing something like that because the more +I use notmuch, the more I think it could be used for other parts of my +workflow. For example, I wrote https://github.com/fommil/zibaldone a +couple of years ago for a friend but I never quite got it to a stage +where I would use it myself. If I could use notmuch to manage a large +collection of notes, that would be interesting, and would mean I could +drop to the zibaldone visual (auto-cluster) mode and use a touchscreen +to move the ideas around and find new connections. I'm using Lucene in +that project, but I could rewrite the backend to use notmuch (or xapian +directly). There are a few tickets on that project I'd love to implement +(on the machine learning side) but on their own are not convincing +enough for me to start using it. + +That said, Zibaldone and note organisation is low priority. If I were to +do anything with notmuch it would be improving syncing with gmail (so a +tag in notmuch equates to a label in their interface) or at the very +least sharing the same tag structure across multiple notmuch +machines. Being able to see the same thing on multiple machines using +one canonical data source is really important for me. + + +--=-=-= +Content-Type: application/pgp-signature + +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.12 (GNU/Linux) + +iEYEARECAAYFAlNdRRsACgkQh5Q4qVL9G8l9cgCfRExczj9MnYktYpDdja+ErRfF +grMAnjUxY0GaQ58fu7dZspCMBhMAoO2n +=cmex +-----END PGP SIGNATURE----- +--=-=-=-- + +--==-=-= +Content-Type: multipart/signed; boundary="===-=-="; + micalg=pgp-sha1; protocol="application/pgp-signature" + +--===-=-= +Content-Type: text/plain + + +--===-=-= +Content-Type: application/pgp-signature + +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.12 (GNU/Linux) + +iEYEARECAAYFAlNdUi0ACgkQh5Q4qVL9G8kAFQCbBML9n0EX+3TRkV+t+SzPZhcw +hr0An1WfuwGvMVDM3d04NyL33pYBoVwP +=fOxR +-----END PGP SIGNATURE----- +--===-=-=-- + +--==-=-=--