[Libre-soc-bugs] [Bug 961] NLnet 2022 Libre-SOC "ongoing" milestone 2022-08-107 (approved, MoU TBD)

bugzilla-daemon at libre-soc.org bugzilla-daemon at libre-soc.org
Tue Aug 22 20:35:53 BST 2023


https://bugs.libre-soc.org/show_bug.cgi?id=961

--- Comment #6 from Andrey Miroshnikov <andrey at technepisteme.xyz> ---
Michiel responded with several questions.

Luke's response:
[Part 1 of 2]
On Thursday, August 17, 2023, <michiel at nlnet.nl> wrote:
> Hi Luke,
>
> please find the imported draft attached. Questions:

thx michiel, i will take a look.  i trust you did not
have to make any modifications to the task words? (that
defeats the object of autogenerating them!)


> - Task https://bugs.libre-soc.org/show_bug.cgi?id=1003
>
> "note this is a duplicate of bug #976 which has been marked as resolved/fixed, avoid "missing specifiers" (what bug #976 covered) under this task unless further work is needed"

ok, see comment 2
https://bugs.libre-soc.org/show_bug.cgi?id=1003#c2

and then observe in the child tasks that the entire budget
*has* already been allocated to subtasks.... *none of which*
overlap (or are a duplicate of) #972.

> The wording indicates dat this is work already done/double,

it was, 6 months ago. i spent several days going over ALL tasks
and eventually caught it. it was then changed but i did not
want to lose sight of the mistake made (i.e. looking
like i am hiding something, an Audit "no-no").

on reflection, strictly speaking, the "history of comment edits"
records that, for Audit purposes, but it is good to have the
up-front conversation with you, so that you fully understand
and are not caught off-guard if the Auditor queries it.

> while I gather from the context that this essentially builds on that work. In that case, let's make that explicit.

i leave it with the others to carry out that adjustment,
i have made a few minor adjustments.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the libre-soc-bugs mailing list