[Libre-soc-bugs] [Bug 1126] How to document new bugs/issues

[bugzilla-daemon at libre-soc.org]

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

--- Comment #27 from Andrey Miroshnikov <andrey at technepisteme.xyz> ---
(In reply to Jacob Lifshay from comment #26)
> Apologies, luke and andrey, I got distracted with other things and didn't
> get around to doing that task.

That's fine, but please do remember to focus on the tasks for cryptorouter and
cavatools grants that need to be done (unless that's what you were distracted
by). The sooner we get those done, the sooner we'll be able to apply for new
grants (with potentially very interesting work).


On another note, I need to add the point of having a summary comment in a
completed bug (to make a clear declaration that budget is justified, and make
the job easier for any potential auditors):
https://lists.libre-soc.org/pipermail/libre-soc-dev/2023-October/005730.html

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