Skip to content

10.26.2023 SLIM Developers Tag Up

Rishi Verma edited this page Oct 26, 2023 · 7 revisions

Announcements

  • November meetings
  • @ddalton212 contributions

Agenda / Notes

  • Metrics ticket issue-117
    • Key steps:
      • Which metrics to capture? As a community-initiative, which metrics are important to capture for SLIM related projects
        • DORA metrics: an effort led by Google to pinpoint useful metrics
        • Topics
          • Deployment Frequency—How often an organization successfully releases to production
          • Lead Time for Changes—The amount of time it takes a commit to get into production
          • Change Failure Rate—The percentage of deployments causing a failure in production
          • Time to Restore Service—How long it takes an organization to recover from a failure in production
        • **A: add comment in issue-117 with list of proposed metrics that satisfy initial discussion as well as experience gained deploying sample tools like DevLake, etc. **
      • How to capture?
        • ApacheDevLake
        • (project that measures open source community health) @riverma
        • May make sense to do a trade-study as well as get feedback from other developers
      • How to make it easy to do this for projects?
        • Imagine having a "best practice" guide for metrics:
          • Would it have starter kits? templates? automation? If so what?
          • Could it be as easy as a GitHub Action
          • Customized Docker image?
          • SLIM verifies infusion of SLIM recommendations via repository signatures or files or configuration - can we "verify" that a particular project is using metrics?
        • Answer the questions clearly: why is this important, for given use cases?
          • Maybe multiple metric dashboards can be offered for different use cases
      • Recommendation to follow best practice guide development: https://nasa-ammos.github.io/slim/docs/contribute/submit-best-practice
    • Use cases
      • NISAR - action on metrics is a challenge, typically more value to projects in early-stage development
      • Potential use cases:
        • SRL
        • Unity
        • SLIM projects
  • Continuous Testing ticket @yunks128: https://github.com/NASA-AMMOS/slim/issues/110
    • Forked SLIM repo and currently working on the draft template
    • Tool identification
      • Survey for community
      • Q/A with developers
    • @yunks128 has a PR listing a set of CT tools ready for review
    • Next steps
      • See task list above
      • Share a milestones / set of dates for Q1 with community and @riverma
  • Infusion @jpl-jengelke
    • Seeking to fully infuse SLIM deliverables (issue templates, LICENSE, code of conduct, contributing guide) for IDS projects by end of Oct
    • READMEs are more challenging but will be the next aim
    • Goal for Q1 is to "infuse" existing SLIM deliverables to IDS / NASA-AMMOS projects fully