10.26.2023 SLIM Developers Tag Up

Announcements

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?
  - Recommendation to follow best practice guide development: https://nasa-ammos.github.io/slim/docs/contribute/submit-best-practice
Continuous Testing ticket @yunks128: https://github.com/NASA-AMMOS/slim/issues/110
Infusion @jpl-jengelke