[Libre-soc-bugs] [Bug 939] NLnet 2021 cavatools proposal 2021-08-071

bugzilla-daemon at libre-soc.org bugzilla-daemon at libre-soc.org
Mon Dec 12 18:50:10 GMT 2022


--- Comment #14 from Dmitry Selyutin <ghostmansd at gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #13)
> (In reply to Dmitry Selyutin from comment #11)
> > Updated the milestones for the subtasks. What should be the next step?
> i thought it might be sensible to put a "management" budget on here,
> part for you writing the mou, part for me, and part for future
> updates to budget-sync and other odds.

Fair enough, I agree, but with a remark below.

> my feeling is that cavatools eabi is going to be near-trivial,
> it can come down to EUR 4000.  management can be EUR 3000, that
> leaves EUR 1000 which can go into one or more other tasks which
> are abit low. #976 and #958?

I also have a strange feeling that works around integration will need more
resources, too. I'm not the one to judge, since I haven't checked this part
yet, but I'd be really surprised if integrating cavatools to our testing API
would be trivial. But I'm afraid this is to be discovered yet. I'm unlikely to
do it due to time constraints, but others will almost certainly handle it. How
about the scheme below?

1. Cut ABI tasks to 4500 EUR each (#981, #982).
2. Since we now have 5000 EUR, we can assign 3000 EUR to management, 500 EUR to
#976, 500 EUR to #958, and 1000 EUR for wrapup which can migrate to #985 if

Or we can assign 1000 EUR #985 immediately if you can confirm this is a
difficult one. I'm not sure of the level of gdb support we have now.

If OK, I will raise the management task with 3000 EUR, will assign 500 EUR to
each #976 and #958, and will move the 1000 EUR to either wrapup or #985,
depending on our conclusions.

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

More information about the libre-soc-bugs mailing list