1 Return-Path: <madduck@lapse.rw.madduck.net>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by olra.theworths.org (Postfix) with ESMTP id 4DFE9431FBF
\r
6 for <notmuch@notmuchmail.org>; Mon, 1 Feb 2010 14:32:11 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=-0.483 tagged_above=-999 required=5 tests=[AWL=2.116,
\r
12 BAYES_00=-2.599] autolearn=ham
\r
13 Received: from olra.theworths.org ([127.0.0.1])
\r
14 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
15 with ESMTP id RbbCzSMPYlpD for <notmuch@notmuchmail.org>;
\r
16 Mon, 1 Feb 2010 14:32:09 -0800 (PST)
\r
17 Received: from clegg.madduck.net (clegg.madduck.net [193.242.105.96])
\r
18 by olra.theworths.org (Postfix) with ESMTP id E07C4431FBD
\r
19 for <notmuch@notmuchmail.org>; Mon, 1 Feb 2010 14:32:08 -0800 (PST)
\r
20 Received: from lapse.rw.madduck.net (lapse.nz.madduck.net
\r
21 [IPv6:2001:4428:234::1])
\r
22 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
\r
23 (Client CN "lapse.rw.madduck.net",
\r
24 Issuer "CAcert Class 3 Root" (verified OK))
\r
25 by clegg.madduck.net (postfix) with ESMTPS id AA1101D409D
\r
26 for <notmuch@notmuchmail.org>; Mon, 1 Feb 2010 23:32:03 +0100 (CET)
\r
27 Received: by lapse.rw.madduck.net (Postfix, from userid 1000)
\r
28 id B471EFF; Tue, 2 Feb 2010 11:31:12 +1300 (NZDT)
\r
29 Date: Tue, 2 Feb 2010 11:31:12 +1300
\r
30 From: martin f krafft <madduck@madduck.net>
\r
31 To: notmuch@notmuchmail.org
\r
32 Message-ID: <20100201223112.GA20288@lapse.rw.madduck.net>
\r
33 Mail-Followup-To: notmuch@notmuchmail.org
\r
34 References: <87my083mgh.fsf@SSpaeth.de> <87d4148s2c.fsf@lillypad.riseup.net>
\r
35 <4B595D3A.1030901@SSpaeth.de> <87636u34lw.fsf@SSpaeth.de>
\r
36 <87d411zvz8.fsf@yoom.home.cworth.org>
\r
37 <20100125213231.GB15987@lapse.rw.madduck.net>
\r
38 <960df8f6a8a08f2ca3aceef5a216d691.squirrel@webmail.sspaeth.de>
\r
39 <87wrz4fqsw.fsf@lillypad.riseup.net>
\r
40 <20100127194149.GA23034@lapse.rw.madduck.net>
\r
41 <20100128070522.GA18649@ukfsn.org>
\r
43 Content-Type: multipart/signed; micalg=pgp-ripemd160;
\r
44 protocol="application/pgp-signature"; boundary="LZvS9be/3tNcYl/X"
\r
45 Content-Disposition: inline
\r
46 In-Reply-To: <20100128070522.GA18649@ukfsn.org>
\r
47 X-Motto: Keep the good times rollin'
\r
48 X-OS: Debian GNU/Linux squeeze/sid kernel 2.6.32-trunk-686 i686
\r
49 X-Spamtrap: madduck.bogus@madduck.net
\r
50 X-Subliminal-Message: debian/rules!
\r
51 User-Agent: Mutt/1.5.20 (2009-06-14)
\r
52 X-Virus-Scanned: clamav-milter 0.95.3 at clegg
\r
53 X-Virus-Status: Clean
\r
54 Subject: [notmuch] patchwork test instance (was: Git feature branch)
\r
55 X-BeenThere: notmuch@notmuchmail.org
\r
56 X-Mailman-Version: 2.1.13
\r
58 List-Id: "Use and development of the notmuch mail system."
\r
59 <notmuch.notmuchmail.org>
\r
60 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
61 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
62 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
63 List-Post: <mailto:notmuch@notmuchmail.org>
\r
64 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
65 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
66 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
67 X-List-Received-Date: Mon, 01 Feb 2010 22:32:11 -0000
\r
71 Content-Type: text/plain; charset=utf-8
\r
72 Content-Disposition: inline
\r
73 Content-Transfer-Encoding: quoted-printable
\r
75 I investigated some patch/issue trackers over the weekend. Here's my
\r
78 The executive summary is that
\r
79 http://patchwork.madduck.net/project/notmuch/list/ now exists.
\r
80 I have not really used it for anything real, so if some of you feel
\r
81 inclined to give it a shot, sign up and triage away! Feedback
\r
84 also sprach James Rowe <jnrowe@gmail.com> [2010.01.28.2005 +1300]:
\r
85 > Roundup has command line and email interfaces. The email interface is
\r
86 > quite similar to debian's. I've never used a launchpad hosted project
\r
87 > so I can't compare it.
\r
89 Roundup is an issue tracker, while Patchwork is a patch tracker.
\r
90 They are fundamentally distinct, but there are overlaps. What led me
\r
91 to go the Patchwork-path is that projects like the kernel and Git
\r
92 don't use issue trackers but work entirely patch-based.
\r
94 I don't know if that is the right way to do things, but having an
\r
95 issue tracker that fills up with bugs and wishlist items lacking
\r
96 patches is no better in the long run than not having an issue
\r
99 Arguably, being patch-centric means that a project has a higher
\r
100 barrier of entry, but it also means that if someone wants something,
\r
101 they know that they'll have to somehow end up with a patch. The way
\r
102 this happens on Git is that you either write it yourself and bring
\r
103 it up to discussion (which is what patchwork facilitates), or
\r
104 constructively theorise the functionality until someone else
\r
107 > Google's codereview tool has a nice interface for collecting and
\r
108 > commenting on patches, but I suspect that suggestion will also meet with
\r
109 > a degree of friction. To me codereview feels like patchwork with
\r
112 Maybe you could take some ideas from codereview and inform the
\r
113 patchwork people about them?
\r
115 > Both gitorious and github have commenting functionality built in.
\r
116 > Commenting on commits in a fork is as easy as opening the commit in
\r
117 > a browser. I use something along the lines of the following script to
\r
118 > open commits on github:
\r
121 > BASE=3D$(git config remote.${2:-origin}.url | sed 's,git\(@\|://\)\([=
\r
122 ^:/]*\)[:/]\(.*\).git,http://\2/\3/commit,')
\r
123 > COMMIT=3D$(git rev-parse ${1:-HEAD})
\r
124 > sensible-browser ${BASE}/${COMMIT}
\r
126 > Using github or gitorious you can easily find and track forks from one
\r
127 > place as well, which makes discovering new work much easier. Github
\r
128 > even provides a pretty single page interface to the work going on in
\r
129 > other forks, gitorious requires a little more leg work to do the same
\r
132 Git now has commit notes, but it doesn't seem like that's integrated
\r
133 with Github/Gitorious.
\r
135 Mind you, patchwork isn't integrated at all with Git. It should be
\r
136 possible to set it up to automatically flag patches that are
\r
137 accepted into mainline, next, or pu.
\r
139 The benefit of patchwork is that discussion isn't moved to the web,
\r
140 but patchwork hooks into the mailing list, so discussion can stay
\r
141 where it should IMHO be.
\r
143 > For a couple of hosted projects we use at the office we email the
\r
144 > individual entries from http://github.com/$user/$project/comments.atom
\r
145 > to the mailing list so they're /forcibly/ seen by everybody :)
\r
147 Right, but replying requires them to open a browser and be online at
\r
152 Anyway, I suggest we give patchwork a try. It occurs to me that
\r
153 notmuch can pretty much do all of what patchwork is doing =E2=80=94 after
\r
154 all, it's just tagging patches/threads, but until we have
\r
155 synchronisable tags and a mailing list archive based on notmuch
\r
156 (which could then replace patchwork), I think we'll need to employ
\r
160 martin | http://madduck.net/ | http://two.sentenc.es/
\r
162 "what's your conceptual continuity? --
\r
163 well, it should be easy to see:
\r
164 the crux of the bisquit is the apopstrophe!"
\r
167 spamtraps: madduck.bogus@madduck.net
\r
170 Content-Type: application/pgp-signature; name="digital_signature_gpg.asc"
\r
171 Content-Description: Digital signature (see http://martin-krafft.net/gpg/)
\r
172 Content-Disposition: inline
\r
174 -----BEGIN PGP SIGNATURE-----
\r
175 Version: GnuPG v1.4.10 (GNU/Linux)
\r
177 iEYEAREDAAYFAktnVi0ACgkQIgvIgzMMSnVpmQCeNAE//qcT8J5I7s7f/3BbLFxB
\r
178 3TIAn2Ha7h9pacquF0AmIljRHclIgiIo
\r
180 -----END PGP SIGNATURE-----
\r
182 --LZvS9be/3tNcYl/X--
\r
projects / notmuch-archives.git / blob