Bug reports allow tracking of issues, both to make the developers lives easier,
as well as for tracking completed grant-funded work.
+It is **extremely** important to link the new bug to previous ones. As Luke
+mentioned on [this bug](https://bugs.libre-soc.org/show_bug.cgi?id=1139#c3),
+"it is a mandatory project requirement that the graph from any bug
+contain all other bugs (one "Group")".
+
+The primary reason for this is to ensure bugs don't get buried and lost,
+and will aid those tackling similar problems at a later time.
+
+Also, for project management and financing purposes, it helps developers
+to keep an up-to-date list of their tasks.
+
####How to raise issues
1. Create a bug report.
accounting purposes and **MUST** be correct. *Note you can only get paid for
stuff done **after the nlnet grant is approved** (before the MOU is signed)*
-It is **extremely** important to link the new bug to previous ones. As Luke
-mentioned on [this bug](https://bugs.libre-soc.org/show_bug.cgi?id=1139#c3),
-"it is a mandatory project requirement that the graph from any bug
-contain all other bugs (one "Group")".
-
-The primary reason for this is to ensure bugs don't get buried and lost,
-and will aid those tackling similar problems at a later time.
-
-Also, for project management and financing purposes, it helps developers
-to keep an up-to-date list of their tasks.
-
If a developer ever needs to check which bugs are assigned to them, go to the
Libre-SOC bug tracker
[advanced search page](https://bugs.libre-soc.org/query.cgi?format=advanced),