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"
+
+# Adding sub-tasks to tasks under existing milestone
+
+* notify Michiel and the relevant NNNN-NN@nlnet.nl team of
+ advance notice of intent to add new sub-tasks, cc'ing bob
+ goudriaan
+ - confirm with them that this is NOT a change in the AGREED
+ MILESTONE BUDGETs, because it is just sub-task allocation.
+ - confirm that they are happy to add the sub-tasks to the MoU
+ (this needs approval of bob goudriaan)
+* *re-generate* the JSON file
+* make a DIFF against the *PREVIOUS* JSON file
+* create a MANUAL report/summary of "changes" that
+ NLnet may easily action
+ - "add the following task X to parent Y of amount W",
+ - and if any: "change parent Z available amount to V as a WRAPUP")
+ (this latter is because occasionally there are subtasks **not**
+ totalling the full parent amount, usually because a summary
+ report is needed. Michiel and I privately agreed to call
+ this "wrapup")
+* obtain a confirmation that this has been actioned
+* **double-check** that the RFP database correctly matches the new
+ bugzilla status.
+
+PLEASE NOTE: YOU CANNOT ACTION THE ABOVE UNDER THE FOLLOWING CIRCUMSTANCES
+
+1. to make a change to the actual budgetary amounts of the
+ Grant Milestones, without written authorization from Bob
+ and Michiel. a DIFFERENT PROCEDURE is needed.
+ this is because NLnet had to go through a 3rd party Verification
+ Process with the European Union: changing the amounts without
+ consent is therefore tantamount to fraud.
+
+2. if there has been an RFP already submitted under a given Milestone,
+ it becomes NO LONGER POSSIBLE to change the JSON file in NLnet's
+ system because it is too complex.
+
+ there is one Grant in this complex situation: bug #690, the crypto
+ grant. it is made much more complex because it *pre-dates* NLnet's
+ current RFP system, where RFPs were submitted by EMAIL and there
+ are manual records not fully integrated into the database.
+
+also note: as the addition of sub-tasks *requires a change to the MOU*
+it should NOT be taken lightly, i.e. should not be arbitrarily done
+one by one, but only in "batches".
+
+considerable care therefore has to be taken to ensure that NLnet are
+not overloaded, nor that the EU Auditor is given grounds to become
+"suspicious" because of a dozen or more alterations to the MOU.
and write your nickname (i.e. andrey etc.).
\ No newline at end of file