-
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
Paper on GitHub process and RP meeting structure and changes #10
Comments
@APSIMInitiative/reference-panel - please send any comments to @Keith-Pembleton |
Also note that an action from the AI SC meeting was "RP to involve/notify/incorporate home organisation key personnel into the new GitHub process". |
@APSIMInitiative/reference-panel - please forward any comments to @Keith-Pembleton prior to AI SC on Friday. |
Reopen issue - action from August AI SC Meeting - RP to provide report on GitHub processes at next SC meeting |
Reminder: @APSIMInitiative/reference-panel to provide feedback to @Keith-Pembleton via email, phone etc.. |
@sarahcleary - apologies for denseness. Feedback on what? |
@APSIMInitiative/reference-panel - AI SC are interested in an update on how the 'new' RP processes/structure are working, in particular, the utilisation of GitHub. Please feed any comments (positive and negative) to @Keith-Pembleton. Sorry @sno036 for missing your message |
Ongoing Action. |
agree to be a verbal update. @APSIMInitiative/reference-panel to provide @peter-devoil with comments/input |
I feel that current processes/structure are working well. The utilisation of GitHub helped tracking issues and communications in RP |
@APSIMInitiative/reference-panel - please note any issues/suggestions |
Request for update of GitHub process and RP Meeting structure/changes
ACTION @Keith-Pembleton and @sarahcleary to commence work on paper
The text was updated successfully, but these errors were encountered: