[Libre-soc-bugs] [Bug 961] NLnet 2022 Libre-SOC "ongoing" milestone 2022-08-107 (approved, MoU TBD)

[bugzilla-daemon at libre-soc.org]

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

--- Comment #7 from Andrey Miroshnikov <andrey at technepisteme.xyz> ---
[Part 2 of 2]
> - Task 999 is a bit vague (what does 'build' mean), where will these packages be delivered? I assume upstream Gentoo, Debian? Please make specific.

i did tell the team during the meeting precisely and exactly
that, that there has to be a *deliverable* that can be vetted
and audited.

they didn't take it on-board.

upstream debian and gentoo will require at least 2-3 years,
we cannot possibly wait that long.

i therefore requested that the "deliverable" be a set of
"reproducing instructions", and that all patches be included
in a git repository.

which i have already set up for gentoo, Sadoon, and you
still haven't pushed anything to it.
https://git.libre-soc.org/?p=portage.git;a=summary

and i recall you said "i made some random git repository"
on tuesday and i know for a fact that you did not ask me
for permission to use unauthorized external repositories:
the answer is and remains an automatic NO.

please push the work that you have done to date IMMEDIATELY
to public repositories and continue ONLY in public *LIBRESOC*
repositories. if you need more repositories raise it on the
bugreport and i will create them (and please remember that
binary files, log files, or anything autogeneratable is
PROHIBITED from being committed).

we DO NOT work out of gitlab or github, period.


team: welcome to the fact that this is a HUNDRED THOUSAND Euro
task, it is GUARANTEED 100% as a Condition of this Grant
that a EU Auditor, dedicated to this Grant, WILL go through
it with a fine-tooth comb.

Michiel and his team need ABSOLUTE CAST IRON CONFIDENCE that
they can answer any questions.  "the work got done somewhere,
just trust us and give us the money" is in NO WAY acceptable.


> - Task 1024,

not a wrapup. it's just genuinely that complex. it *might*
get subdivided into the usual "implementation tests docs"
which would give 3 subtasks but there will be no "wrapup".

> 1025,

i am leaving that to jacob to subdivide, as part of training
him to get his feet on the ground.  there will be no "wrapup",
the entire lot goes to connecting the IEEE754FPU work into
TestIssuer.  it's FIFTY instructions so no way we will get
all of it done but it will be a good start.

the rest of the team will be helping him to make the assessment.

> 1032,

again: not a wrapup, it really is that big.  i will attempt
to get the others to (again) think in terms of Project
Management and create the subtasks.

there will be no wrapup, there will only be subtasks.

> 1033: can "wrapup" be a bit more specific as well?

again: not a "wrapup". the task is relatively straightforward
and needs no subdivision into subtasks.

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