From 92f8c67aaddd24caade87433b75a279582cc6b8b Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Sat, 10 Mar 2018 12:28:14 -0400 Subject: add forum --- doc/index.mdwn | 1 + 1 file changed, 1 insertion(+) (limited to 'doc/index.mdwn') diff --git a/doc/index.mdwn b/doc/index.mdwn index 14fec93..16af569 100644 --- a/doc/index.mdwn +++ b/doc/index.mdwn @@ -4,6 +4,7 @@ * [[News]] * [[Bugs]] * [[Todo]] +* [[Forum]] * [[Protocol]] * [[Evidence]] * [[Servers]] -- cgit v1.2.3 From 3431a9757a5654fce1e472073a5bf97aa515553f Mon Sep 17 00:00:00 2001 From: spwhitton Date: Sun, 8 Jul 2018 20:17:00 +0000 Subject: add link to simon tatham essay --- doc/index.mdwn | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) (limited to 'doc/index.mdwn') diff --git a/doc/index.mdwn b/doc/index.mdwn index 16af569..7ea627d 100644 --- a/doc/index.mdwn +++ b/doc/index.mdwn @@ -16,7 +16,10 @@ Debugging a problem over email/irc/BTS is slow, tedious, and hard. The developer needs to see the your problem to understand it. Debug-me aims to make debugging fast, fun, and easy, by letting the developer access your computer remotely, so they can immediately see and interact with the -problem. Making your problem their problem gets it fixed fast. +problem. Making your problem their problem gets it fixed fast. As +Simon Tatham [[puts it|https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]], +"In a nutshell, the aim of a bug report is to enable the programmer to see the +program failing in front of them." debug-me does just that! A debug-me session is logged and signed with the developer's GnuPG key, producing a [[chain of evidence|evidence]] of what they saw and what they -- cgit v1.2.3