Le 05/06/2023 à 10:08, Andre Vehreschild a écrit :
Regarding the time estimates, it's a bit difficult as we can't foresee
at this stage the amount of regressions that will need to be fixed, and
how difficult they will be. I'm not even sure that the process of
picking one regression and fixing it will eventually converge to a
zero-regression state. It doesn't mean much, but I expect to spend
between 3 and 6 months on every item I have proposed. But I expected
those items to be discussed, prioritized, and either acknowledged or
refused by the contributors before.
You mean, you will 3 to 6 month full-time for the scalarizer rework, the API
thingys and so on? Or is the estimate on how long it will take you to do the
things in total, i.e. not working full-time on them?
The latter, 3-6 months delivery time each item at 60% working time.
I am asking that specifically because we need to estimate the person days they
pay for and time boundary up to when the project will be done.
Yes, I don't like it but I understand the need for estimating.
I have looked at the evaluation criteria at [1]. There is among other
things:
Furthermore, we look at how well the planning for the project is laid out. Are
the activities well-structured, appropriate and feasible?
I think we are far from having a "well laid out planning". Even if it's
difficult to estimate the amount of days of work, we should probably at
least try to decompose the project into milestones, that is (small)
steps proving progress toward the target.
[1] https://sovereigntechfund.de/en/applications/
