From f342206988072d0077316bfbbe14de7dc97ea287 Mon Sep 17 00:00:00 2001
From: Xin LI <delphij@FreeBSD.org>
Date: Sat, 17 Mar 2007 08:48:46 +0000
Subject: [PATCH] New SoC idea: automated kernel crash reporting.

---
 en/projects/ideas/ideas.xml | 36 +++++++++++++++++++++++++++++++++++-
 1 file changed, 35 insertions(+), 1 deletion(-)

diff --git a/en/projects/ideas/ideas.xml b/en/projects/ideas/ideas.xml
index 4f5dc91552..8e0cdcf93c 100644
--- a/en/projects/ideas/ideas.xml
+++ b/en/projects/ideas/ideas.xml
@@ -15,7 +15,7 @@ Ideas//EN"
 <ideas>
   <cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0">
     <cvs:keyword name="freebsd">
-      $FreeBSD: www/en/projects/ideas/ideas.xml,v 1.11 2007/03/16 16:49:17 murray Exp $
+      $FreeBSD: www/en/projects/ideas/ideas.xml,v 1.12 2007/03/16 17:59:05 dds Exp $
     </cvs:keyword>
   </cvs:keywords>
 
@@ -121,6 +121,40 @@ Ideas//EN"
   <category>
     <title>Kernel</title>
 
+    <idea id="autoreport" class="soc">
+      <title>Automated kernel crash reporting system</title>
+
+      <desc>
+<p><strong>Technical contact</strong>: <a href="mailto:delphij@FreeBSD.org">Xin LI</a>, <a
+  href="mailto:howard0su@gmail.com">Howard SU</a></p>
+
+<p>In some recent operating systems, it is common that crashes are
+  automatically reported to its vendor, which is very helpful for
+  finding hidden problems that can not be easily triggered by usual
+  test cases.  Newer GNOME applications also has similar functionalities.</p>
+
+<p>This project would consist two parts.  One is some improvements over
+  the current savecore rc.d script to teach it how to collect necessary
+  information (of course, automatic reporting has to be explicitly enabled
+  by individual system administrators, and should have at least three
+  options: not to send out anything at all as a default, send out after
+  administrator confirmation, and automatically send all necessary information)</p>
+
+<p>Another part is the server side one, which will keep a database of backtraces
+  where similar (call stack minus addresses) reports are kept together and be
+  considered as a "vote", to make it possible for developers and release engineers
+  to focus on the most commonly triggered issues.</p>
+
+<p><strong>Requirements</strong>:</p>
+<ul>
+  <li>Strong knowledge of C.</li>
+  <li>Understanding of kernel debugging.</li>
+  <li>Knowledge about web application as well as database.</li>
+  <li>Understanding of user privacy protection.</li>
+</ul>
+      </desc>
+    </idea>
+
     <idea id="setproctitle" class="soc">
       <title>Avoiding syscall overhead</title>