add stub meeting page, TODO

[libreriscv.git] / HDL_workflow.mdwn

diff --git a/HDL_workflow.mdwn b/HDL_workflow.mdwn
index 38bd6f0f619b6d7262e1f1b60c77ac5c19bbe453..d9e570ba4ddd899fc9b11a8b425a8222f0e2a2e1 100644 (file)
--- a/HDL_workflow.mdwn
+++ b/HDL_workflow.mdwn
@@ -126,6 +126,8 @@ send this to Spam" option.
 
 ## Bugtracker
 
+* **LibreSOC bug/task process**: [[libresoc_bug_process]]
+
 bugzilla. old and highly effective. sign up in the usual way. any
 problems, ask on the list.
 
@@ -135,27 +137,6 @@ lions are getting wind and gout from overfeeding on that one.
 
 one.
 
-### Why raise issues
-
-* [Bug #1126](https://bugs.libre-soc.org/show_bug.cgi?id=1126)
-
-If you have discovered a problem in Libre-SOC (software, hardware, etc.),
-please raise a bug report!
-Bug reports allow tracking of issues, both to make the developers lives easier,
-as well as for tracking completed grant-funded work.
-
-####How to raise issues
-
-1. Create a bug report.
-2. Add in any links from the mailing list or IRC logs to the bug report for back tracking
-  (this is mandatory). Also fill in the URL field if there is a relevant wiki page.
-3. CC in relevant team members
-4. make absolutely sure to fill in "blocks", "depends on" or "see also" so that the
-   bug is not isolated (otherwise bugs are too hard to find if isolated from everything else)
-5. Ping on IRC to say a bug has been created
-6. Unless you know exactly which milestone to use, leave blank initially. This also applies when editing milestone, budget parent/child, toml fields. See section [[WikiLink#Task management guidelines]] further down.
-7. After setting the milestone, it is **absolutely required** to run [budget-sync](https://git.libre-soc.org/?p=utils.git;a=blob;f=README.txt;hb=HEAD), as it will point out any discrepancies. The budget allocations will be used for 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)*
-
 ## ikiwiki
 
 Runs the main libre-soc.org site (including this page). effective,
@@ -436,6 +417,7 @@ In the meantime, sfpy can be built as follows:
 
     git clone --recursive https://github.com/billzorn/sfpy.git
     cd sfpy
+    git apply /path/to/ieee754fpu/sfpy.patch
     cd SoftPosit
     git apply ../softposit_sfpy_build.patch
     git apply /path/to/ieee754fpu/SoftPosit.patch