enable discussions for dev-sec org

[deric4]

Description

When reading through issues/PRs, I sometimes find there are references/cross links to provide to other issues/PRs in dev-sec projects to provide context/reason/implementation details i.e.:

• tcp Timestamp comment is wrong, value can also be improved in some cases. puppet-os-hardening#275
• Support for validation of cpu vulnerabilities (#114) needs further consideration... linux-baseline#140
• 30 instead of 30s in sshd-18 ssh-baseline#148
• why keep_logs? linux-baseline#171

Other times I may notice a difference in how the same task is implemented between Project-A and Project-B and curious about pros/cons and would like to ask a question. Maintainers of Project-A might not be the same maintainers of Project-B, which leaves me unsure of what the most "polite" thing to do is. Opening issues in both projects with same question to increase visibility feels a bit "rude" and noisy...

Enabling discussion for the Org would also allow for migrating any existing Team Discussions which were deprecated May 8, 2023

https://github.blog/changelog/2023-02-08-sunset-notice-team-discussions/

Solution

Enable organization discussions and encourage users to label questions with related projects/standards/etc

examples labels:

• ansible-collection-hardening
• puppet-os-hardening
• CIS
• networking
• logging

Alternatives

keep status quo

Additional information

...

[rndmh3ro]

Good idea! Done -> #21