Kyongsik Yun

Here are some additional suggestions on software repository hygiene (I believe that several of those were already addressed in the other issue tickets.): **Continuous Integration and Testing:** - Integrate automated...

@yunks128 Next steps: 1. Finalize Repository and Naming Conventions - Several repository and naming conventions are outlined (e.g., PyPI, DockerHub, Maven). - Confirm and document the agreed-upon repository choices, especially...

I updated CHANGELOG.md focusing on high-level changes for end users and pointing to the release link (following the option 2): https://github.com/NASA-AMMOS/slim/pull/174 @hookhua Do you have any preference between options 1...

Updated the metrics readme by adding a simple metrics gathering: https://github.com/yunks128/slim/tree/yunks128-issue-160-metrics/docs/guides/software-lifecycle/metrics

Great discussions! I would like to start a document that describes what we have discussed. The title and scope are to be updated (code of conduct, expectations, acknowledgments, etc.) https://github.com/yunks128/slim/blob/main/docs/guides/governance/contributions/code-of-conduct/EXPECTATIONS.md

> We discussed this ticket during our SLIM community meeting today and @yunks128 is going to open an issue on the TOPS side to see if we can broaden the...

@c-h-david Thanks for the update! I think it makes sense to have "Collaborative Expectations" under "Research Integrity and Collaborative Working". The European Code of Research Integrity emphasizes principles of reliability,...

Pull request has been submitted to close the loop: https://github.com/NASA-AMMOS/slim/pull/187

Things to consider: 1. API integration: GitLab and Bitbucket REST and GraphQL APIs 2. CI/CD pipelines need to be compatible with GitLab and Bitbucket

@riverma I took another pass and resolved the conflict in registry.json. It should be all set for your review now—thanks!