-
Notifications
You must be signed in to change notification settings - Fork 9
09.21.2023 SLIM TSC Meeting
John Engelke edited this page Nov 16, 2023
·
1 revision
- Welcome new SLIM team member Kyongsik Yun for FY'24
- SLIM Written Guides Standardization using Templates
- See: https://github.com/NASA-AMMOS/slim/issues/101
- Any additional feedback or are we ready to begin using this new template and rewriting all previous guides to use it?
- Leaderboard for SLIM infusion
- Unity project infusion (see board)
- NASA-AMMOS GitHub Org
- Inside JPL repositories
- 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
- Which one is canonical? How do we prevent divergence? Some ideas:
- Git modules
- Autogenerate / commit updates from slim repo to other repos
- Example: README.md template
- New ticket idea from @tariqksoliman regarding Communication Process for Cross-Customer Projects
- See: https://github.com/NASA-AMMOS/slim/issues/102
- Should we take this on? Technical ideas / feedback?
- Collaboration with InnerSource
- SLIM website has been forked inside JPL
- Potential collaboration opportunities to share code / developments with InnerSource and SLIM
- Shall we list out TSC members on the website?
- All of us should be utilizing DCO's - thoughts?
- Internship opportunities with https://www.outreachy.org
- Thoughts? Mentor volunteers?
- Dillon D. to join next SLIM TSC and present on CI/CD & metrics work he's been doing
- Greater emphasis in FY'24 on security scans for OSS projects - how can SLIM help?
- Existing ticket progress on A&A to follow-up on
- Action: include relevant people on this ticket thread
- We have existing guides that would be helpful to infuse further with projects
- Can we recommend a "checklist" for various application-development scenarios?
- Existing ticket progress on A&A to follow-up on
- For all new SLIM guides, please use the latest version of our in-progress template
- Current Unity leaderboard:
- Feedback: For other leaderboards, could potentially have checks be grouped instead of having each specific SLIM check
- Multiple copies of SLIM artifacts
- Feedback: consider having a canonical location and dependencies that "update" to the version
- Feedback: should we version control each one of our artifacts?
- Action: make ticket to address ideas on this ticket
- Recommendation: all TSC members should have a DCO in place for SLIM (or other repos!)
- https://nasa-ammos.github.io/slim/docs/guides/governance/contributions/developer-certificate-origin/
- Doing so helps streamline contributions from outside parties to projects (similar to contribution license agreements)