You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To ensure that all repositories have equitable opportunity to own and lead Y3 Plan tasks and deliverables Co-Chairs are asking that PIs take a look at the GREI Y3 Deliverables- Champions and nominate “Y3 Champion(s)” from their repository.
Tasks
@kristiholmes to update the format to capture the areas of interest
@lekshmi-sheelakumari to send a reminder to team to nominate GREI Champions before 15th May
Discussed and added leads and co-leads to Task Groups- to be confirmed with the nominees by individuals mentioned in comments. (ACTION)- By June 14
Create a timeline based view of the Task Groups, with a heat map for prioritizing the Task Groups, and Co-chairs mapped to these task groups - TG timing/dependencies
Community Engagement Task Groups to be updated, OSF nominations to be added. (Lekshmi to complete)
GitHub Issues related to the Task Groups to be linked in the Champions Nominees list
@sbarbosadataverse to assign the Task Group leads to Task Group GitHub Issues to update the details
Decided that Co-Chairs should review all related documents and define the purpose of each, eliminate duplications, link all, and then update names to match purpose - to add this as a new issue
The call for Task Group Champions were made and we have identified the Task Group Leads, Contributors and those who want to keep awareness. We have also identified the estimated timeline for the task groups. Deliverable updated in the description
##Deliverable
GREI Y3 Task Groups & Deliverables
Objective
To ensure that all repositories have equitable opportunity to own and lead Y3 Plan tasks and deliverables Co-Chairs are asking that PIs take a look at the GREI Y3 Deliverables- Champions and nominate “Y3 Champion(s)” from their repository.
Tasks
Deliverables
Resources
Related Issues
The text was updated successfully, but these errors were encountered: