Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

reporting guidelines #958

Open
lsmith77 opened this issue May 29, 2021 · 3 comments
Open

reporting guidelines #958

lsmith77 opened this issue May 29, 2021 · 3 comments

Comments

@lsmith77
Copy link

semi-related to the topic of enforcement, I also wonder about the topic of reporting.

within the Symfony community we created this reporting guide which in turn was derived from those of the Stumptown Syndicate and the Django Software Foundation.

is the topic of reporting within the scope of 3.0?

(obviously in my dreams I would love to one day see Beacon as a way to partially enforce parts of these guidelines, especially about confidentiality, with a tool)

@CoralineAda
Copy link
Member

Totally agree that this is an area where we should provide guidance, and I've made an note of that for the CC 3.0 working group. Thanks so much Lukas.

@AevaOnline
Copy link

I'd like to add another endorsement of refactoring the CC to include a process guideline, and a point of comparison.

Within the Kubernetes community, we recently published our incident report handling process

@CoralineAda
Copy link
Member

@AevaOnline I like that a lot and will share it with the working group. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants
@CoralineAda @lsmith77 @AevaOnline and others