- Discussed a bit the risks of five ~modest proposals in close alignment with current projects, but all agreed there is no sense in trying to pre-empt the SC’s reaction to this yet.
- No idea what the SC’s reaction will be and how feedback will come (end of May is late for us, given the June Workshop) - anything is possible.
- G&J will report to the group immediately after the meeting.
- We will make the point about the workshop being critical to us and that the time to organise it is short.
- Applying a standard formatting in Word, we set a work count limit of 600 per proposal
- We will shorten the Reco proposal by condensing the final list to a few sentences.
- Please finalise changes by 10h tomorrow morning, so that G&J can prepare the actual submission.
- The minimum effort for each proposal should be 1 fellow plus 1 student. For Reconstruction it should be 2. (Thus 6 in total for software.) Explicitly adding the word “minimum" is recommended, to underline these projects could all benefit from more effort.
- We will broaden the base of each proposal where one person was primarily involved up to now to have further convenors; this is to help cover work needed for the workshop organisation.
- By the workshop there should be a draft plan with milestones, etc. That will need to be explicit to the SC for the second round of submissions at the end of June (the workshop helps clarify and ratify the plans).
- We will hold off organising the workshop until next Wednesday, so at least we have some feedback from the SC.
- But after that we will need to move quickly - anticipate a planning meeting shortly after (end of next week, or w/b 28 May)
There are minutes attached to this event.
Show them.