Skip to content

SLIM Steering Meeting Notes

Jump to bottom
Rishi Verma edited this page May 30, 2024 · 12 revisions

May 1st, 2024

Announcements

  • 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)

Table Topics

  • 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, reference architecture templates
  • OpenAI pilot activity
    • New task to integrate ChatGPT-4 into infusion process: https://github.com/NASA-AMMOS/slim/issues/154
      • How well does this scale to diversity of SLIM templates?
    • New task to test ChatGPT-4 auto-code generation for continuous testing guide. See this part of the continuous testing guide.
    • Discussion:
      • Suggestions on setting up AI tools for software developer use
  • AI and section 398 strategy
    • Skepticism on code quality?
    • Filling out documentation / auto-complete while coding
    • Skeleton code generation
    • Is industry going to solve this for us?
  • 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?

May 29th, 2024

Announcements

  • SLIM will make a v1.5.0 release in early June to publish the Continuous Testing guide
  • SLIM spoke with the NRSG community, and at least one follow-up with a project scheduled

Table Topics

  • Continuous Deployment discussion
    • Ticket created: DevOps Integration Process Improvement Guide
    • Discussion questions:
      • Idea of the above ticket is to have a top-level guide on "DevOps" that links to individual guides for CI, CD, CT. Is this hierarchy and organization appropriate?
      • Which tangible features within the ticket are "must haves" for CD?
  • Community Members
  • Best practice guide for project websites
    • Ticket: https://github.com/NASA-AMMOS/slim/issues/159
    • Discussion questions:
      • What are must haves for a given project website we should include in the template?
      • Deployment mechanism: deploy a working docusaurus build or fork the docusaurus repo?
Clone this wiki locally