From: Jameson Graef Rollins <jrollins@finestructure.net>
To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
Subject: Re: Experimental Tag Sharing
In-Reply-To: <1319906707-10141-1-git-send-email-david@tethera.net>
References: <1319857491-12298-5-git-send-email-david@tethera.net>
	<1319906707-10141-1-git-send-email-david@tethera.net>
User-Agent: Notmuch/0.9-24-g2fd0ca5 (http://notmuchmail.org) Emacs/23.3.1
	(x86_64-pc-linux-gnu)
Date: Sat, 29 Oct 2011 17:44:56 -0700
Message-ID: <87lis3tiif.fsf@servo.finestructure.net>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha256; protocol="application/pgp-signature"
Precedence: list

--=-=-=
Content-Transfer-Encoding: quoted-printable

On Sat, 29 Oct 2011 13:45:06 -0300, David Bremner <david@tethera.net> wrote:
> OK, here is my rough and ready attempt at tag sharing.  I figure we
> can smooth out the rough edges if/when we agree on a set of tags and
> preferably on an on-disk format.

Great!  Thank you so much for working on this, David.  This is very
exciting work.

Comments below.

> How to play?
>=20
> - - Apply all the patches in this thread (starting
>   id:"1319383133-11006-1-git-send-email-david@tethera.net")

These patches did not apply cleanly for me from the list.  I was able to
get them from bremner's "nmbug" branch [0], though.

[0] git://pivot.cs.unb.ca/git/notmuch

> $ nmbug dump
> $ cd $HOME/.nmbug && git add tags && git commit

This last command seems to be included in nmbug as "commit".  Fwiw, I
don't like having to do two separate operations for dump and commit.
Could they be merged into a single operation?

> now you have to get the changes into the "master" repo.  I think
> hosting this on git.notmuchmail.org in a seperate repo will make
> sense, but for now, if you want to participate in the experiment, send
> me your public key (ideally in a gpg signed mail, but if not, oh well),=20
> and you can push to my repo at
>=20
>     git@pivot.cs.unb.ca:pub/nmbug

While I think having a central shared tag repo is ok to get started, I
would really like to see this work in a distributed way.  I don't think
it's impossible to extend this model you have here to work in a
distributed way, though, so that will be something good to work on down
the line.

> Probably the most crucial thing is that we agree on some set of tags.
> Here is the set of tags I am working with (output from=20
>      notmuch search --output=3Dtags "*" | grep ^notmuch::=20
> )
>=20
> notmuch::bug   		     is a bug report
> notmuch::feature	     provides a new feature
> notmuch::fix		     fixes a bug
> notmuch::obsolete	     replaced by some other patch
> notmuch::patch=09=09=20=20=20=20=20
> notmuch::portability	     improves portability
> notmuch::pushed		     is pushed to master
> notmuch::review		     is a review
> notmuch::reviewed	     has been (well reviewed)
> notmuch::test		     provides a new test/or improves testing
>=20
> The prefix "notmuch::" is hardcoded into the script, but everything
> else is easy to change with the usual notmuch operations.  Of course
> we can change the prefix too. I decided on :: because it needed less
> escaping.

I think these are a fine set to start with.

It might be nice to let the user configure what prefix they use
(ie. what goes before the "::" (currently "notmuch")).

Does this system support the removing of tags?  I guess I need to see
the documentation for the restore --match option...

It's too bad there's not a way to do scoped tag searches in notmuch
(ie. notmuch search tag:"notmuch::*").  Any idea how hard it would be to
support something like that?

> On think I'm not sure about is how to handle ideas like "voting", and
> "signing off" with tags. I suspect we can come up with some
> conventions like "notmuch::review1", or
> "notmuch::vote1".."notmuch::vote5". But maybe people have less kludgy
> ideas.

What issue are you trying to solve here?  Whatever it is, I don't think
I like enumerating tags as the solution.

Again, thanks so much for working on this, David.  This is going to be
very cool.  I really look forward to fleshing it out, and using it!

jamie.

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAEBCAAGBQJOrJ4IAAoJEO00zqvie6q80S0P/RDECS7Ji8nf3bMA41HJ1OL7
rk8spKV6sHs0aClXYqaG3JTOWcj9iEVEcHNjPw/S3O9fowksn8YFRwx+0HresyNn
aCuLC/2Np385i24S4MpoTGTqfDTMD/fUX/BFbdQUUFs0Nq9o5RuxH9nyzGbuHQo1
A6vFfkxNlnYRN5QF9QdXKNWa9nLY9DQ9rTd8GhHfUxNLAfpF8t7O2a0ML0W2B7hH
xa+5vJ3+mbiqMQglYbRSOwabRnlT6tEBL2uKyAB++i6WDONWL1zdV6Nqa4NRogVQ
TBPwYtEUPZ3b5DJ/0MG+KzSnRRV2enB1ydhAb4afBPCKnc4kvl2ucNoDYjZu1WPP
3CsCqJkGpjSWccofwDTWgBIRmP25ME2zuqF+RfDddBP80x5MBxKY1pM8LpcClaRM
4HzBm3h7AlRrmqxHD9iI08/YqpMA1qvAiDFxfWB4CyYD8DS9OZK1q6FIFrj0SAbo
rngAfFVbq6tAOTODQtIyWv/169V7KTHnNQlqtMm62Q6JxQVOdLGGCP2+1eYZViPB
NWqihDL0zN1fZzb+xB3R3pPxYi4ffTxtjgul2PSyp10Kh9pjVqQkgGcJn2vJxyzh
c2K90wz3yqbB/LzxIkt52UT/7mD8LbKau4gF/FDK7DYGU7yO2gnU2NcbTcDWS9px
JfKNHWkNU17Zb95SNhh5
=jh2K
-----END PGP SIGNATURE-----
--=-=-=--