These ideas sound pretty reasonable to me :). On Wed, Dec 16, 2015 at 08:03:47PM +0100, Lars Wirzenius wrote: > * All discussion is over email, to avoid making people have to sign > up to a website…
Like notmuch does [1] (see “Bug and patch tracking”)? And I have some work on ssoma-archiving outlined in [2], but that's low priority and extremely alpha. > * Having at least a read-only view of the system via a static > rendering of the ticket system data is crucial. A more interactive > one would be nice, of course. Notmuch has a read-only status page built from its tags [3]. It links to Gmane for each tagged message, but you could easily point it at any archive server that supports Message-ID URLs. And yeah, a more interactive system would be nice ;). I've mocked up nmhive for tagging while browsing Gmane [4], but it's low priority and extremely alpha. > * All ticketing system data is stored in git, and normal git > operations are used for syncing. The data is stored in a way that > makes merging unlikely to cause conflicts. The notmuch folks do this with nmbug [5], which would work well for any system that wanted to distribute per-Message-ID tags. If any of that sounds interesting, help is welcome :). Cheers, Trevor [1]: https://notmuchmail.org/bugs/ [2]: http://thread.gmane.org/gmane.mail.notmuch.general/19673 [3]: http://nmbug.notmuchmail.org/status/ [4]: https://github.com/wking/nmhive [5]: https://notmuchmail.org/nmbug/ -- 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
signature.asc
Description: OpenPGP digital signature
_______________________________________________ dist-bugs mailing list [email protected] http://kitenet.net/cgi-bin/mailman/listinfo/dist-bugs
