Expectations for Open Science

[yunks128]

We are cross-posting this issue from NASA-AMMOS/slim Issue #173 to broaden the conversation and gather feedback from the TOPS community.

We believe this is a great opportunity to expand the conversation regarding expectations around open research and collaborative contributions.

Specifically, we are proposing to either create a new document or integrate it into the existing Code of Conduct to outline expectations for open, collaborative research practices, including:

• Best practices for contributing and collaborating in open-source projects.
• Guidelines for research integrity and transparency.
• Approaches for feedback, authorship, and sharing research outputs. The current draft is here: https://github.com/yunks128/slim/blob/main/docs/guides/governance/contributions/code-of-conduct/EXPECTATIONS.md

We welcome feedback from the TOPS community on how to best structure and implement these expectations. Should we integrate this into the Code of Conduct or create a new standalone document? Your insights and suggestions will be valuable in shaping this initiative.

Thanks in advance for your contributions!

[c-h-david]

@yunks128, thank you so much for cross-pollinating and for building on the initial draft. I think what you're proposing here is an excellent start and I look forward to community feedback!

[bressler95tops]

Thanks for asking this question @yunks128. I have not been able to pin point a NASA standard for code of conduct files. The way that I am using to handling this type of file in the root directory of the repository as we have here. And the advantage of doing this is a nice shortcut appears when people land on your repository, and you also have everything consolidated to one file.

Our code of conduct has not been updated for some time and I will make sure to let everyone on this thread know when we have done so. I do like the approach that you have taken, framing it as "Yes do this" instead of "no don't do this". One piece of critical feedback is your metrics of success, I feel like this would best fit wherever you talk about the bottom line of your project, where the code of conduct should be dedicated to expectations of how people interact on your repository including the manner in which they contribute to the repository.