[Libre-soc-dev] first stage new grants "passed", planning needed for 2nd

[lkcl]

On Friday, February 23, 2024, Dmitry Selyutin <ghostmansd at gmail.com> wrote:
> On Fri, Feb 23, 2024 at 2:25 PM lkcl <luke.leighton at gmail.com> wrote:
>> i spoke with michiel directly by phone for 2 hours (2days ago),
>> and he sent me the signed MoU and the secret URL, after he
>> uploaded the JSON file (task list) for 2022-08-107 directly
>> into the RFP system right there right then.
>
> Is URL different for different members?

different per Grant. each RFP URL effectively contains a
password. if exposed then anyone could submit an RFP to
any bank account they chose.

>  If not, if you already have it
> means you can resend it to others, and they can submit RFPs.
>
>> no i need to check back with him, i got *some* emails from
>> him in real-time on the phone (he sent them, they arrived
>> immesiately) but others did not get through
>> (even now). very odd.
>
> This should be done fast.

i emailed michiel, he sent to my lkcl at lkcl.net address which
is still having problems [that i cannot resolve]

> It's been an awful lot of time since we went
> only for signature and an email.

that tells you how many projects they manage, now.
(they employed 2 more staff a few weeks ago)

> plan. I'd like to know that we have a backup plan, especially since
> NLnet is silent.

they're not. i am in touch with Michiel directly.

>> all of the NLnet Grants i have done that, so every Grant is
>> 2-way cross-referenced.
>
> Thanks! With this document I now introduced some sketch at
> https://bugs.libre-soc.org/show_bug.cgi?id=1212.

fantastic.

> I still have to think about the budget for each task. Meanwhile you
> can think about administrative and conference budgets and probably can
> add some tasks.

yes.

> The more I think about the task, the more challenging it seems;

well we do not have to do everything, it is R&D after all.
remember the rule that we work *towards* a goal, and can
apply for another grant.

> I
> tried to keep RISC-V support conservative and minimalistic so that we
> don't run out of time.
> That's why some tasks are explicitly labeled with PPC.

we can pick a simpler ISA if that helps?
or one you are familiar with?
x86 for example?

l.