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.
Automation to check for additional information in GitHub infrastructure like tickets and discussion boards would be useful here. Beyond the capabilities of our guide on checking for sensitive information.
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.