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
Thread to discuss prioritizing the agenda for our upcoming meeting scheduled for 2023-01-23 at 15:00 UTC (convert to your time-zone).
Please take a look at open issues (or submit new ones if something's missing), and comment here with the ones you'd like to prioritize and how much time they should get.
For "news" topics (describing something that has already happened, or where a CAC decision is not currently needed) 10 minutes out of our 60 minute meeting should be enough. For broader thematic discussions or those requiring a decision, 20 minutes will be necessary. We'll also reserve 10 minutes at the beginning and 10 minutes at the end for introductions and wrap-up, respectively.
The text was updated successfully, but these errors were encountered:
(10 minutes) Sign-on, workflow discussion
(10 minutes) Prioritization of content / episodes (#3)
(10 minutes) Accepting new lessons to Software Carpentry (#6)
(10 minutes) Replacing the default lesson ("Planets") with an alternative story (#5)
(10 minutes) Potential survey of community members about lessons (#2)
(10 minutes) Wrap up
Thread to discuss prioritizing the agenda for our upcoming meeting scheduled for 2023-01-23 at 15:00 UTC (convert to your time-zone).
Please take a look at open issues (or submit new ones if something's missing), and comment here with the ones you'd like to prioritize and how much time they should get.
For "news" topics (describing something that has already happened, or where a CAC decision is not currently needed) 10 minutes out of our 60 minute meeting should be enough. For broader thematic discussions or those requiring a decision, 20 minutes will be necessary. We'll also reserve 10 minutes at the beginning and 10 minutes at the end for introductions and wrap-up, respectively.
The text was updated successfully, but these errors were encountered: