NGI Assure call deadline 01/08/2022

Received today


Hi Loïc,

it has taken a while but we finally were able to resolve the issues raised by the external reviewers! The final conditions set by them are as follows:

"Standardising based on too limited an overview of the field can cause long term sustainability issues, and harm innovation. Project 2022-08-025 (Friendly Forge Format/F3) should make a thorough comparative analysis of solutions prior to standardising, along the approach of timesheets/apps-list.md at main · federatedbookkeeping/timesheets · GitHub

The project should build in adequate feedback from and collaboration with other forge maintainers, and recommend these request support from NLnet if necessary to have enough team resources to adequately participate in the process."

All in all, that seems quite doable. Do you think this is feasible? If so, we can move ahead…

[redacted]

Best,


Replied sent today:


Hi,

This is excellent news and I agree to the final conditions. Not only is it doable, it also makes perfect sense. F3 has matured in the past six months and it is in line with how it is being developed.

Cheers


Reply from NLnet received the same day.


Hi Loïc,

This is excellent news and I agree to the final conditions. Not only is it doable, it also makes perfect sense. F3 has matured in the past six months and it is in line with how it is being developed.

wonderful. In that case, please find the draft MoU attached.

You know how it works, we need to add the plan. Will you add other people to this MoU? Will you execute as Easter Eggs, or as individual? In that case, I need to send a slightly different variant.

Best,


My answer to NLnet. The draft MoU is not published here because it contains private data. The final MoU will be published with the private data redacted.


Hi,

Thanks for the quick turnaround. I’ll execute as an employee of Easter-Eggs will send you the draft workplan this week. The draft MoU looks good as it is.

Cheers