=== modified file 'src/docbkx/en/dhis2_implementation_guide_support.xml'
--- src/docbkx/en/dhis2_implementation_guide_support.xml 2012-02-08 22:35:01 +0000
+++ src/docbkx/en/dhis2_implementation_guide_support.xml 2013-04-16 11:48:21 +0000
@@ -18,4 +18,51 @@
If you want to suggest new functionality to be implemented in DHIS 2 you can air your views on the developer mailing list and eventually write a specification, which is referred to as blueprints in Launchpad. The bueprint will be considered by the core development team and if accepted be assigned a developer, approver and release version. Blueprints can be browsed and added at http://blueprints.launchpad.net/dhis2
If you find a bug in DHIS 2 you can report it at Launchpad by navigating to http://bugs.launchpad.net/dhis2 Your bug report will be investigated by the developer team and be given a status. If valid it will also be assigned to a developer and approver and eventually be fixed. Note that bugfixes are incorporated into the trunk and latest release branch - so more testing and feedback to the developer teams leads to higher quality of your software.
+
+ Reporting a problem
+ If you encounter a problem with the DHIS 2 software you can ask for assistance on the
+ developer's mailing list at https://launchpad.net/~dhis2-devs. Before reporting, make sure that you
+ have:
+
+
+ Cleared the web browser cache (also called history or browsing data) completely
+ (select all options before clearing).
+
+
+ Cleared the DHIS 2 application cache: Go to Data administration -> Cache statistics
+ and click Clear cache.
+
+
+ For the developers to be able to help you need to provide as much useful information as
+ possible:
+
+
+ DHIS 2 version: Look in the Help -> About page inside DHIS 2 and provide the version
+ and build revision.
+
+
+ Web browser including version.
+
+
+ Operating system including version.
+
+
+ Servlet container / Tomcat log: Provide any output in the Tomcat log (typically
+ catalina.out) related to your problem.
+
+
+ Web browser console: In the Chrome web browser, click F12, then "Console", and look
+ for exceptions related to your problem.
+
+
+ Actions leading to the problem: Describe as clearly as possible which steps you take
+ leading to the problem or exception.
+
+
+ Problem description: Describe the problem clearly, why you think it is a problem and
+ which behavior you would expect from the system.
+
+
+