-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RP Meeting - 4/5 #85
Comments
2021-05 MinutesAttendees:@MarkLieffering; @LouisAK; @hol353; ; @peter-devoil; @yashvirchauhan; @sarahcleary; @jbrider; @HamishBrownPFR; @hut104; @sarchontoulis; @sno036 @junqi108; @Keith-Pembleton @EnliWang; Apologies/Not in attendance:Tuesday 4th May 2021 - 9:30 am AESTMeeting recorded – which can be accessed on Teams link for meeting attendees. Discussion with group on modelRecording from 52min to 1:20 min. Work required for Model to be accepted into Release** Preamble require a bit more information with cautions/caveats for new users Debrief discussion from 1:20-endKey Points for Future Review Meetings Outcomes from meeting: Comments on new process: |
Note additional comments on APSIMInitiative/ApsimX#1822 |
@sarahcleary, @HamishBrownPFR and I were chatting ... this review worked because Junqi was presenting and fielding questions while Hamish was taking notes and moderating. This was more of a happy accident but something we should make sure happens consistently for future reviews. Particularly so when the presenter is not one of the RP members probably. |
I agree, the meeting went very smoothly. I don't believe this was by accident and noted that @HamishBrownPFR had worked closely with @junqi108 in preparation for this meeting. I also understand @hut104 had provided @junqi108 with feedback prior to the meeting. It might be a good idea for a RP rep (or someone close to the RP) reviews and/or assists with preparation for the meeting. |
I agree it went well. My only comment is that the presentation went a little long. Would be good to suggest that presenters have 30 minutes. What do you think? |
My two-cents on duration is that we need to be flexible. For the grape model I thought the issue was more that we scheduled too short a time slot than that the presentation itself was too long. They had a lot to cover (the new geometry as well as multi-year phenology and then the model and data). Other presentations may well be much simpler with fewer concepts to introduce and may well only need 30 min. If the 'oral examination' method is going to be effective then we do have to allow time for discussion and questions and then the list of items to be completed before release. |
A shorter time for pedestrian subjects (eg another annual field crop) could be possible. But this exercise had several major new pieces of functionality which were only briefly discussed. I'd leave any decision on amount of time required to the facilitators |
Yep ok. My real issue was the too short a time slot and someone else put a meeting into my calendar immediately following the RP meeting. I missed the important discussion. I'll talk to Neil and get an update. |
@hol353 - the recording is on the teams link - let me know if you can't access it. Main discussion from 52 min point to 1:20 if you would like to listen to it |
@JulianneLilley, @kchenu - recording is available if you would like to listen. Any issues accessing it, please give me a call |
@sarahcleary I can't see a recording of the previous meeting. |
@hol353 - sent by email |
Grape Vine Model Review
9:30-10:30 AEST
@junqi108 to present to the RP
Questions:
@HamishBrownPFR - will this be sufficient time? do we need to extend this meeting?
@APSIMInitiative/reference-panel - who else needs to be invited to this review?
@junqi108; @HamishBrownPFR - any instructions for the @APSIMInitiative/reference-panel prior to this meeting? Anything they should do to prepare?
The text was updated successfully, but these errors were encountered: