[Improve Existing Best Practice Guide]: Contributing guide should outline guidance for gov't folks on posting public content
Open
@riverma is already working on this.
Since Jul 19, 2022.
governance
low complexity
requested
- Dominant language
- JavaScript
- Stars
- 36
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
Checked for duplicates
Yes - I've already checked
Best Practice Guide
Documentation
Best Practice Guide Sections
Starter Kits
Describe the improvement
We've received questions and passed out guidance on how to converse in open source tickets / discussion boards when some of the operational software systems are not publicly accessible. We've noticed sometimes that SLIM community members post internal intra-net hyperlinks (only accessible to their institution) or snippets that include sensitive info like IPs. Guidance here would help serve as a reference for all.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.