Importing NanoBlogger post "Email interface to bugs everywhere"
authorW. Trevor King <wking@drexel.edu>
Sun, 19 Jul 2009 01:25:18 +0000 (01:25 +0000)
committerW. Trevor King <wking@drexel.edu>
Sun, 19 Jul 2009 01:25:18 +0000 (01:25 +0000)
posts/Email_interface_to_bugs_everywhere.mdwn [new file with mode: 0644]

diff --git a/posts/Email_interface_to_bugs_everywhere.mdwn b/posts/Email_interface_to_bugs_everywhere.mdwn
new file mode 100644 (file)
index 0000000..cd25ad3
--- /dev/null
@@ -0,0 +1,42 @@
+[[!meta  title="Email interface to bugs everywhere"]]
+[[!meta  date="2009-07-18 21:25:18"]]
+I've been amusing myself over the past few days working up an email
+interface for the distributed ugtracker [Bugs
+Everywhere](http://bugseverywhere.org).  One of the things we've been
+struggling with with BE is how end users should submit
+bugs/comments/etc, since
+
+    $ apt-get install bzr
+    $ bzr branch http://whatever/remote/repo local_repo
+    $ cd local_repo
+    $ be new "The demuxulizer is broken"
+    Created bug with ID 48f
+    $ be comment 48f
+    <Describe bug>
+    $ bzr send --mail-to "whatever-dev@fancyprojects.com"
+
+mostly just raises eyebrows among non-devs ;).  My interface replaces
+it with
+
+    $ cat | mail -s "[be-bug] new" "whatever-dev@fancyprojects.com"
+    The demuxulizer is broken
+
+    <describe bug>
+    ^D
+
+Which will hopefully be more user friendly.  Of course, most non-devs
+I know (and some devs) avoid the command line like the plague, so we
+will still want a web-frontend.  Luckily, web frontends seem popular
+with other devs, so I don't have to bother with that ;).
+
+Curious parties can branch my public repo:
+
+    $ bzr branch http://www.physics.drexel.edu/~wking/code/bzr/be-email be.email
+
+As a nice side effect of this little project, my
+[`send_pgp_mime`](/~wking/code/python/send_pgp_mime) is now much more
+elegant.
+
+[[!tag  linux]]
+[[!tag  programming]]
+[[!tag  fun]]