SLIM Steering Meeting Notes

May 1st, 2024

Rishi will present SLIM to NASA SMD Software conference
KS will present to Might Devs community on continuous testing best practices (Thursday, May 16, 11:00 am – 12:00 pm PT)

Continuous Deployment discussion
- Context: SLIM has a goal to advise on best practices for CD - we're brainstorming what we should do to help with that goal
- Questions:
  - What is the problem with existing project deployments?
    - (time): "big" deliveries that take a long time to make and push out
    - (people): lot of people involved, hand-offs between delivery artifacts - can lead to mistakes
    - (security policies): permissions that make CD difficult to enact
  - What is "continuous deployment"?
    - Difference between "deployment" and "delivery": pushing to artifact repositories vs then pushing to production.
  - What is our vision?
    - Have ready-to-deliver artifacts that can be chosen when teams would like to deliver
    - Use containerization to reduce the complexity of a large single deployment
    - Use existing tooling that helps with CD
    - Offer rigor or comprehensive architecture that's consistent and well-tested
    - i.e. starter kits
OpenAI pilot activity
- New task to integrate ChatGPT-4 into infusion process: https://github.com/NASA-AMMOS/slim/issues/154
- New task to test ChatGPT-4 auto-code generation for continuous testing guide. See this part of the continuous testing guide.
AI and section 398 strategy
SLIM has a weekly developer meeting and a bi-weekly steering committee meeting. Can we bridge the information gap between the two? Shall we meet monthly or keep bi-weekly?