From 523c133bb65d139a02cf77e2746f7cc1addd6950 Mon Sep 17 00:00:00 2001 From: Andrey Miroshnikov Date: Fri, 22 Sep 2023 09:12:36 +0000 Subject: [PATCH] Moved info related to bug #1126 to new wiki page. --- HDL_workflow.mdwn | 44 --------------------------------- libresoc_bug_process.mdwn | 51 +++++++++++++++++++++++++++++++++++++++ 2 files changed, 51 insertions(+), 44 deletions(-) create mode 100644 libresoc_bug_process.mdwn diff --git a/HDL_workflow.mdwn b/HDL_workflow.mdwn index 6a2498356..9a358d365 100644 --- a/HDL_workflow.mdwn +++ b/HDL_workflow.mdwn @@ -135,50 +135,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. - -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. -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 [[HDL_workflow#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)* - -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), -and in the "Search by People" section, check "Bug Assignee" and "contains" -and write your nickname (i.e. andrey etc.). - ## ikiwiki Runs the main libre-soc.org site (including this page). effective, diff --git a/libresoc_bug_process.mdwn b/libresoc_bug_process.mdwn new file mode 100644 index 000000000..6c9f1a1dc --- /dev/null +++ b/libresoc_bug_process.mdwn @@ -0,0 +1,51 @@ +# LibreSOC Bug Process + +* [Bug #1126](https://bugs.libre-soc.org/show_bug.cgi?id=1126) + +This page describes in detail how to raise new tasks (bugs) and how to approach +development within the project in order to get appropriate amount of funding +for the tasks completed. + +# 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. + +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. +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 [[HDL_workflow#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)* + +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), +and in the "Search by People" section, check "Bug Assignee" and "contains" +and write your nickname (i.e. andrey etc.). \ No newline at end of file -- 2.30.2