-
-
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
[lesson program] Accepting new lessons to Software Carpentry #6
Comments
Thanks for contributing these important topics, Tony! We'll have to see what the members think about adding this to the agenda for our first meeting, but at a minimum we can start the discussion here on Github. In addition, I think several of the other potential agenda items are at least related to the questions that you've posed. My current understanding is that non-members may attend CAC meetings (perhaps @ErinBecker can verify this). If you'd like to join us to hear the discussion and perhaps to briefly introduce this topic, I think that would be valuable. |
I am planning to attend the meeting next week, as liaison from the Core Team. I'll be delighted to provide more context and detail then, if you want to discuss it further this time. |
Adding a link to the planned Lesson Program Governance Committees, since they're clearly relevant to this discussion. |
As Core Team liaison to the committee, an agenda item I would like to see the CAC discuss this year is about the potential for new lessons to be added to the Software Carpentry fold (in our official jargon, to be added to the lesson collection of the Software Carpentry Lesson Program). I am interested in helping you make some decisions on this, particularly in relation to lessons under development in The Carpentries Incubator. Specific questions would be:
These are quite "big" questions and I would absolutely understand if you prefer not to address them in your first meeting this year. But I will be very keen to hear your thoughts when you are ready to begin this discussion.
The text was updated successfully, but these errors were encountered: