docs: better docs, mv doxygen to sphinx

[vpp.git] / docs / contributing / reportingissues / reportingissues.rst

diff --git a/docs/troubleshooting/reportingissues/reportingissues.rst b/docs/contributing/reportingissues/reportingissues.rst
similarity index 91%
rename from docs/troubleshooting/reportingissues/reportingissues.rst
rename to docs/contributing/reportingissues/reportingissues.rst
index 3ccd494..970f340 100644 (file)
--- a/docs/troubleshooting/reportingissues/reportingissues.rst
+++ b/docs/contributing/reportingissues/reportingissues.rst
@@ -2,24 +2,6 @@
 
 .. toctree::
 
-Reporting Bugs
-==============
-
-Although every situation is different, this section describes how to
-collect data which will help make efficient use of everyone's time
-when dealing with vpp bugs.
-
-Before you press the Jira button to create a bug report - or email
-vpp-dev@lists.fd.io - please ask yourself whether there's enough
-information for someone else to understand and to reproduce the issue
-given a reasonable amount of effort. **Unicast emails to maintainers,
-committers, and the project PTL are strongly discouraged.**
-
-A good strategy for clear-cut bugs: file a detailed Jira ticket, and
-then send a short description of the issue to vpp-dev@lists.fd.io,
-perhaps from the Jira ticket description. It's fine to send email to
-vpp-dev@lists.fd.io to ask a few questions **before** filing Jira tickets.
-
 Data to include in bug reports
 ==============================