Conversation
|
What is the driver for this and why is are reviewers excluded [from the CoC]? |
|
|
||
| The Code of Conduct applies to the content since the 1st of October, 2025. | ||
|
|
||
| The "issuer" knows what the ASVS is about, e.g., is familiar with the content of the "What is the ASVS" (<https://asvs.dev/v5.0.0/What-is-the-ASVS/>) |
There was a problem hiding this comment.
"issuer"
Is it the person opening a GitHub issue, a project maintainer, or someone else? This term is not standard term.
|
|
||
| The Code of Conduct applies to the content since the 1st of October, 2025. | ||
|
|
||
| The "issuer" knows what the ASVS is about, e.g., is familiar with the content of the "What is the ASVS" (<https://asvs.dev/v5.0.0/What-is-the-ASVS/>) |
There was a problem hiding this comment.
"knows"
How is "knowing" measured? This is a vague expectation and unclear.
| * In case the issue is about existing content - quote the requirement or part of the document from the bleeding edge version from markdown | ||
| * In the discussed issue, read and analyze in detail what is written before to avoid situations like "it was already answered 2 comments before" - it causes useless content, wastes everyone's time, and makes issues complicated to follow and analyze later | ||
| * If the issue is about the requirement, the discussion must focus precisely on that requirement. If there is a side-topic evolving, it should be moved to a separate issue. | ||
| * If quoting something, please provide a source. If AI-generated content is used, it must be stated so. |
There was a problem hiding this comment.
This should be under separate title, like below copied from Microsoft Opensource CoC
Responsible Use of AI-Generated Content
We are excited about the innovation and the opportunities that generative AI tools like GitHub Copilot bring to our community. It's essential to use these technologies thoughtfully and in alignment with our shared values of integrity, respect, and authenticity.
When using generative AI to contribute to the community:
- Take ownership of your contributions. You are responsible for the content you share.
- Review and revise AI-generated responses before posting. Ensure they reflect your own understanding and voice.
- Apply your expertise to validate that the information is accurate, relevant, and helpful.
These practices support a community built on trust, collaboration, and mutual respect. Misuse of AI-generated content may be considered a violation of our Code of Conduct. Please refer to the enforcement section for more details.
|
|
||
| A contributor needs to be polite in words and in actions. | ||
|
|
||
| Tone of contributions: |
There was a problem hiding this comment.
Clarifies tone, it should be in two sections - Expected Behavior and Unacceptable Behavior
|
|
||
| The main goal for issues is that all changes to requirements are public information, and it is possible to go back to the discussion and re-investigate the arguments. | ||
|
|
||
| Additionally, as the ASVS is based on volunteer work, the most valuable resource is volunteers' time. That means communication on issues requires efficiency. |
There was a problem hiding this comment.
Efficiency is sometimes misused to exclude newcomers or non-native speakers.
| @@ -0,0 +1,25 @@ | |||
| # Code of Conduct | |||
There was a problem hiding this comment.
It's good to follow opensource CoC document structure and writing content style, Here sharing the few links for reference only
This Pull Request relates to issue -