Skip to content

CoC draft #3264

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.

Sign up for GitHub

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

Draft
elarlang wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

CoC draft #3264

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 25 additions & 0 deletions CODE_OF_CONDUCT.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
# Code of Conduct
Copy link

@ajayojha ajayojha Oct 31, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's good to follow opensource CoC document structure and writing content style, Here sharing the few links for reference only


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/>)
Copy link

@ajayojha ajayojha Oct 31, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"issuer"
Is it the person opening a GitHub issue, a project maintainer, or someone else? This term is not standard term.

Copy link

@ajayojha ajayojha Oct 31, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"knows"
How is "knowing" measured? This is a vague expectation and unclear.


A contributor needs to be polite in words and in actions.

Tone of contributions:
Copy link

@ajayojha ajayojha Oct 31, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Clarifies tone, it should be in two sections - Expected Behavior and Unacceptable Behavior

* Contributions must be politely worded and have a calm and professional tone.
* At the same time, when reading someone else's contributions, please assume positive intent, as not everyone’s first language is English.
* Contributions must not contain personal attacks.
* Please do not respond to contributions that violate this code of conduct, but rather report them. <!-- needs some instruction here -->

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.
Copy link

@ajayojha ajayojha Oct 31, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Efficiency is sometimes misused to exclude newcomers or non-native speakers.


* Do your best to search the issues list for previous discussions on the topic before opening a new issue, and investigate the previous issue when you are asked to do so.
* 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.
Copy link

@ajayojha ajayojha Oct 31, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

* If longer text is quoted, please provide your own summary and key points, and why the content was provided. That especially applies to AI-generated responses.
* If quoting previous comments, it must be done in a way that it contains the context (e.g., avoid a partial quote that may change the meaning when used out of context)