Be really clear about support guidelines, Daniel
diff --git a/doc/bugs.html b/doc/bugs.html
index 7bfc2df..7c987e7 100644
--- a/doc/bugs.html
+++ b/doc/bugs.html
@@ -122,9 +122,24 @@
attachment)</li>
</ul>
<p>Then send the bug with associated informations to reproduce it to the <a href="mailto:xml@gnome.org">xml@gnome.org</a> list; if it's really libxml
-related I will approve it.. Please do not send mail to me directly, it makes
+related I will approve it. Please do not send mail to me directly, it makes
things really hard to track and in some cases I am not the best person to
-answer a given question. Ask the list instead.</p>
+answer a given question, ask on the list.</p>
+<p>To <span style="color: #E50000">be really clear about support</span>:</p>
+<ul>
+<li>Support or help <span style="color: #E50000">request MUST be sent to
+ the list or on bugzilla</span> in case of problems, so that the Question
+ and Answers can be shared publicly. Failing to do so carries the implicit
+ message "I want free support but I don't want to share the benefits with
+ others" and is not welcome.</li>
+ <li>There is <span style="color: #E50000">no garantee for support</span>,
+ if your question remains unanswered after a week, repost it, making sure
+ you gave all the detail needed and the informations requested.</li>
+ <li>Failing to provide informations as requested or double checking first
+ for prior feedback also carries the implicit message "the time of the
+ library maintainers is less valuable than my time" and might not be
+ welcome.</li>
+</ul>
<p>Of course, bugs reported with a suggested patch for fixing them will
probably be processed faster than those without.</p>
<p>If you're looking for help, a quick look at <a href="http://mail.gnome.org/archives/xml/">the list archive</a> may actually