[Libre-soc-dev] Finishing off the grant: gigabit crypto router 2021-02-052

Luke Kenneth Casson Leighton lkcl at lkcl.net
Sun May 12 22:43:04 BST 2024


On Sunday, May 12, 2024, Cesar Strauss <cestrauss at gmail.com> wrote:
> Hello Jacob,
>
> At the last Tuesday meeting, Luke asked me to track down his current RFP
criteria, so you can work and submit RFPs. So here it is:
>
> Em 18/04/2024 14:33, Luke Kenneth Casson Leighton escreveu:
>>
>> jacob if you find any "admin" work (reporting, budget-sync)
>> i'm happy to do RFPs on that. documentation is out (because
>> it helps CALDERWOOD and LEWIS in their ongoing theft).
>> unit tests are out (likewise). finishing RFPs is ok,
>> writing existing RFPs is ok. developing *new material* to go
>> *into* RFPs is not ok. nmigen etc is ok.
>
> The one below is closed, but your RFP payment date is missing. Did you
submit it?
>
> * Bug 1044 - SVP64 implementation of pow(x,y,z)
> https://bugs.libre-soc.org/show_bug.cgi?id=1044
>
> As I understand it, one can finish tasks already in progress, so people
can be paid for the development work they did in the past:
>
> * Bug 1155 - O(n^2) multiplication REMAP mode(s)
>   https://bugs.libre-soc.org/show_bug.cgi?id=1155
>
> * Bug 1157 - Implement poly1305
>   https://bugs.libre-soc.org/show_bug.cgi?id=1157
>
> * Bug 1159 - poly1305 unit tests
>   https://bugs.libre-soc.org/show_bug.cgi?id=1159
>
> * Bug 1151 - Ed25519 demo
>   https://bugs.libre-soc.org/show_bug.cgi?id=1151

unfortuately all of these would increase the value of what
CALDERWOOD and LEWIS intend to seize control of, so
i do not want them completed.

> Those below don't seem to have started any development, so I guess are
outside Luke's current criteria:
>
> * Bug 1158 - poly1305 documentation
>   https://bugs.libre-soc.org/show_bug.cgi?id=1158
>
> * Bug 1166 - Ed25519 documentation.
>   https://bugs.libre-soc.org/show_bug.cgi?id=1166
>
> * Bug 1167 - Ed25519 unit tests
>   https://bugs.libre-soc.org/show_bug.cgi?id=1167

likewise

> * Bug 785 - Implement gfb* instructions for GF(2^n) instructions
>   https://bugs.libre-soc.org/show_bug.cgi?id=785

yes that would be obscure enough to not be high value

> * Bug 786 - Implement gfp* instructions for GF(p) instructions
>   https://bugs.libre-soc.org/show_bug.cgi?id=786

likewise

> I suppose these can be submitted later, once the situation improves and
we can lift Luke's current RfP criteria.

admin work - budget-sync - is fine. basically anything
that has a high value commercially if seized, re-branded
as proprietary and then sold, *has* to be frozen for our
own protection.

mundane non-essential work, such as finishing off of
OPF RFPs that are already mostly written, not a problem
precisely because they do not contain new additional
research or innovation.

l.


-- 
---
geometry: without it life is pointless
the fibonacci series: easy as 1 1 2 3


More information about the Libre-soc-dev mailing list