Update the README file with bugs, questions, and contribution
sections and fix the format for readability.

Signed-off-by: Lisa Nguyen <lisa.ngu...@linaro.org>
---
 README |   46 +++++++++++++++++++++++++++++++++++++++-------
 1 file changed, 39 insertions(+), 7 deletions(-)

diff --git a/README b/README
index 2eef1c4..5da4485 100644
--- a/README
+++ b/README
@@ -1,5 +1,5 @@
-General Info
-============
+Commands
+========
 - In order to run the tests, invoke as root:
 
        make check
@@ -12,20 +12,52 @@ General Info
 
        make -C cpufreq check
 
-- The test specifications can be found at
+
+Test Specifications
+===================
+The test specifications can be found at:
 
 
https://wiki.linaro.org/WorkingGroups/PowerManagement/Resources/TestSuite/PmQaSpecification
 
-Other info
-==========
+
+Bugs
+====
+If you believe that you have encountered a bug, please file a bug report on
+Linaro Bugzilla at https://bugs.linaro.org. Once you log in, click on
+"New" --> "Power Management" --> "PM-QA" as the component. Then fill
+in the form.
+
+Helpful tips for filing a bug report:
+    1. Provide logs, be verbose as possible
+    2. Outline steps to reproduce the bug
+    3. Describe the environment you are running PM-QA on (e.g. Android,
+        OpenEmbedded, Ubuntu, etc.)
+    4. What Linux device(s) you're using
+
+Questions/Comments
+==================
+Please submit questions and comments to the linaro-dev mailing list at
+linaro-dev@lists.linaro.org with "PM-QA" as part of the subject.
+
+Contributions
+=============
+If you wish to submit patches to improve PM-QA, please send them to
+the linaro-dev mailing list at linaro-dev@lists.linaro.org with
+"PATCH PM-QA" as the subject prefix.
+
+All scripts in PM-QA must be POSIX-compliant and cannot use any
+bashisms. At a minimum, they must run in Android and Ubuntu
+environment and have text files that include their descriptions.
+
+Additional Notes
+================
 - PM-QA is one of the tools in the external opensource modules in the external
   path of android. For building on android, the makefile Android.mk is used to
   build the testsuite with a makefile for each subtest.
-- Incase you are extending a subtest, say a new script which will test a
+- In case you are extending a subtest, say a new script which will test a
   feature. Add the test number in the Android.mk, in addition to this if its
   using a source file (say .c), add the source file in the Android.mk so that
   it gets built.
 - LAVA scripts are used to trigger the pm-qa tests.
 - Similarly for non-android adding a script and txt (test description) pair is
   needed to extent the suite.
-=======
-- 
1.7.9.5

_______________________________________________
linaro-dev mailing list
linaro-dev@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-dev

Reply via email to