Our 2 year goal, by the end of AY 24-25, is to produce GAI-enabled course structure across the introductory STEM curriculum.
The tools should be agnostic to the textbook(s) used in the course, and should be implementable with a minimal time investment in courses nationwide.
Initial backend is likely to be ChatGPT, currently at version 4, but we should strive to build an architecture that can evolve and adapt to new and better and different tools. We need to have an overall architecture philosophy evolve with our development spirals.
...
| respondent | notes | |
|---|---|---|
| Carlos Argueles | carguelles@fas.harvard.edu | Hola Chris: Thanks for sending this email. I am very excited about this new technology. In fact, with Louis Deslauriers, we used some of it in my Physics 15B last semester. Carlos |
| David Malin | using it now in CS50 with custom interface | |
...
Decided to maintain a Table of Policy Questions GAI Policy questions that we can all edit as we go.
July 14 meeting
action items:
1. how do we provide licensing, and are there enterprise-level options (HUIT)
2. IF we decide to use a notebook interface, how does the use of API keys scale? One key per course? One key per person? (HUIT)
3. We should identify some undergraduates who can assist with developing course management tools (Brenner and Neeson)
4. Finalize FAQ document (Stubbs)
5. set up working session on notebook interface (Stubbs, in progress)
6. finalize date of STEM instruction session- proposed for 4-5 pm on Tuesday Aug 8. (Stubbs)
7. prep for STEM faculty instructional session (McCarty, Kestin, Neeson)
8. address issues that pertain to confidentiality and privacy of uploads. Enumerate the options (HUIT).