Date: Mon, 22 Sep 2014 10:35:14 -0700
From: "W. Trevor King" <wking@tremily.us>
To: notmuch@notmuchmail.org
Subject: Re: [announce] nmhive v0.1.0, a bookmarklet/server for nmbug tags
Message-ID: <20140922173514.GK20827@odin.tremily.us>
References: <20140922171935.GJ20827@odin.tremily.us>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="9RxwyT9MtfFuvYYZ"
Content-Disposition: inline
In-Reply-To: <20140922171935.GJ20827@odin.tremily.us>
OpenPGP: id=39A2F3FA2AB17E5D8764F388FC29BDCDF15F5BE8;
	url=http://tremily.us/pubkey.txt
User-Agent: Mutt/1.5.23 (2014-03-12)
Precedence: list


--9RxwyT9MtfFuvYYZ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Sep 22, 2014 at 10:19:35AM -0700, W. Trevor King wrote:
> I like nmbug's distributed tag maintenance, but not everyone has
> notmuch/nmbug installed locally (yet ;).  However, everyone that I
> know does have a browser and a mail client.  They can submit
> messages with their mail client already, but we've been missing a
> way for them to help tag messages.

Ah, and the other piece to this workflow is the existing nmbug-status,
which collects the results of canned searches so folks without a local
notmuch can use the tags [1].  Folks using a local nmhive will
probably want to run their own status-genertion via a post-commit hook
in their nmhive repository.  Then their users will have their
search-results updated after each web-initiated change.  If you also
wanted them to see updates from changes to tethera's nmbug repository,
you'd probably also want a cron job that tried to fetch and merge
tethera's changes with the nmhive changes:

  -o---o---o----o  tethera/master
    \            \
     \            o  nmhive/status  (auto-generated merge for nmbug-status)
      \          /
       o---o----o   nmhive/master (with web-initiated changes)

You'd want to resolve conflicts somehow, but any resolution strategy
is probably fine, since it's unlikely that we get conflicts very
often.

Cheers,
Trevor

[1]: http://nmbug.tethera.net/status/

--=20
This email may be signed or encrypted with GnuPG (http://www.gnupg.org).
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy

--9RxwyT9MtfFuvYYZ
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBAgAGBQJUIF3RAAoJEG8/JgBt8ol8q4wP/3fMDQejeHW54Br4EmgJuNuN
jUtBJLX7SRUWt3zCJzgDw5LmpNaviczAaP4qxOQKOlibaNKeD6tZj18k9R7oUtx9
qArCumvYC4o43rohgNeo8eBeG1R6wJPDqGScyeNZPext4J0LUmyw12xdWzP2OVtv
BMv2hPvypxn8tmTYVsOq2ITxvmkiXAt1Q7GKrRRuGwU/vZ3675e8iDPHn9fMxj4w
l/kBUzH0/WebHb7FVaJ6rxD5puuOorv4Adoh5wzsJT7KhvnrskyrcCBypjCixEhZ
abzxF9ktjpHA5NIuYhnOUmMzdndAG3A59dTrUu5sqkHsJJeNBh5gcuKq/p2L7Mzu
Y6eMNTBqn6IzahNs8anE60qg3hoTW2Y0q6L4nVWn2NWdGP+eT/1wXLuXG051XGm9
LiP+Wc+WfJdJRlnKrrgne6KpjCn189qQRNC+WjDRe6sRuQ3Gb3DDclrZB5mRbQ/E
zp3emXmtFxzs8llXLV02hOaGujLG1W7tmA/tOybsq9tIs/yg+0QINjsCfMRJ24K/
R1v2y2zmKuDg9Hi2fuVodmUApR1RUlOuroFwLAv8i1d/SKTP8IR/2jmW/i52WD27
8xXNiKugEXQOc1eXQNdAlMcDMcvxkldQ8wiBXR/UFb3QGgvHUMW1+AiLExfIbR/R
K2wKxKY5qvsR+vosfysy
=Wnyz
-----END PGP SIGNATURE-----

--9RxwyT9MtfFuvYYZ--