10.04.2023 SLIM TSC Meeting

Announcements

Multiple SLIM Best Practice Leaderboards: institutional, open source, project specific. Where shall we store the leaderboard + scripts?
Contributors / collaborators for Q4 tickets? https://github.com/orgs/NASA-AMMOS/projects/3
Multiple copies of SLIM artifacts
- Example: README.md template
  - Available in slim repo: https://github.com/NASA-AMMOS/slim/blob/main/docs/guides/documentation/readme/README.txt
  - Available in slim-starterkit repo: https://github.com/NASA-AMMOS/slim-starterkit/blob/main/README.md
  - Available in slim-python-starterkit repo: https://github.com/NASA-AMMOS/slim-starterkit-python/blob/main/README.md
- Use cases
  - Using SLIM artifacts manually for GitHub, GitLab, and other software repository projects
  - Using SLIM artifacts for open source or internal institutional projects
  - New projects / existing projects
- Which one is canonical? How do we prevent divergence?
  - @riverma Recommendation: keep GitHub.com/nasa-ammos/slim repository the canonical repository, and each time a release is made - notify downstream projects that use it (i.e. GitHub.com/nasa-ammos/slim-starterkit, institutional projects, other starter kits, etc.)
All of us should be utilizing DCO's - thoughts on requiring?
- See: https://nasa-ammos.github.io/slim/docs/guides/governance/contributions/developer-certificate-origin/

Best Practice Leaderboards:
- Keep code open source
- A: Keep leaderboards either institutionally internal (for internal repos) and private for external
DCO
- What happens if the GitHub Action finds non signed-off commits, do they have to amend commits? rebase?
- A: OSO check-in on this requirement and test out failure of GitHub Action
Dillion D. Presentation
- Apache DevLake
- DORA
- A: Work with Dillon to propose a SLIM ticket for a "metrics" best practice guide