Hi Mikael,
...
> 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.
I understand. I would have been happy in the past when a client had as much
knowledge and structure than we already have. Under "Project goal" we now have
about 300 words. So we could add more. What do you have in mind? Like adding
more bullet points to each item in the form of:
- rebase existing implementation to current master
- identify missing requirements
- add tests for missing requirements
- implement missing requirements to pass tests.
...
Or are your targeting a more time based approach like:
Milestone 1: shared mem coarrays merge to master in week 2 of project
Milestone 2: finish research on general way for doing remote coarray access
in alien structures to finish in week 1 of project
...
Take the above as examples please, not as proposals.
In the meantime I have added something to the "Who section":
---
- Who (maintainer, contributor, organization) would be most qualified to
implement this work/receive the support and why?
Maurice Ulrich @ Badger Systems GmbH -- Project management
Dr. Andre Vehreschild @ Badger Systems GmbH -- Contributed to distributed
memory coarray, teams and failed images support. Has also worked on the
associate command and several other standard compliance issues.
Mikael Morin @ ??? -- Maintained/Contributed to the scalarizer. Experienced in
gfortran development and component dependencies.
Nicolas König @ ETH Zürich -- Implemented the first steps of the process-based
shared memory coarray approach.
---
Our project manager is mostly there as a counting head. He will not do much, if
not asked explicitly, but I learned that it is good to have some one named.
I am curious to hear your input.
Regards,
Andre
--
Andre Vehreschild * Email: vehre ad gmx dot de
