[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
Sat Sep 2 02:00:29 BST 2023
https://bugs.libre-soc.org/show_bug.cgi?id=961
--- Comment #25 from Jacob Lifshay <programmerjake at gmail.com> ---
discussion with luke on irc:
https://libre-soc.org/irclog/%23libre-soc.2023-09-01.log.html#t2023-09-01T21:54:33
ok, for figuring out the exact list of subtasks for bug #1025, I'm not sure
what you meant by "documentation budget":
1. if you meant under a different grant, then that doesn't change what we need
to do before the MOU is signed and we can figure it out later.
2. If you meant it should come out of this grant, then, reading through the
top-level subtasks' descriptions and not spotting anything mentioning
documentation, I think the best place to get that budget from is actually bug
#1025, because an intrinsic part of completing bug #1025 is figuring out the
exact list of subtasks of bug #1025.
Likewise, adding FP/FPSCR registers to TestIssuer and stuff is also an
intrinsic part of bug #1025, so I think the budget should come out of #1025.
All of the other things I recall you mentioning are also subtasks of bug #1025.
Since all of the above tasks are then subtasks of bug #1025 or in a completely
different grant and we do not need to flesh out bug #1025's subtasks in order
to sign the MOU because bug #1025 has enough tasks that we will need to remove
a lot of them to fit in the allocated budget, I think we should leave all of
the above tasks till after we sign the MOU.
Therefore, I think we should move the excess EUR 4000 from bug #1035 (which is
almost completely done already, so the currently assigned budgets are
sufficient) to bug #1025 where we need it.
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the libre-soc-bugs
mailing list