Skip to content

CODE_OF_CONDUCT.md

Latest commit

 

History

History
34 lines (24 loc) · 2.21 KB

CODE_OF_CONDUCT.md

File metadata and controls

34 lines (24 loc) · 2.21 KB
Raw

ARSAS Community Conduct

ARSAS welcomes professional, evidence-based collaboration from substation engineers, protection and control specialists, software developers, testers, educators, researchers, and users.

Expected conduct

Participants should:

  • communicate respectfully and keep discussion focused on the engineering problem;
  • distinguish observed evidence from assumptions, estimates, or marketing claims;
  • provide reproducible steps and synthetic examples where possible;
  • respect customer, employer, contributor, and third-party confidentiality;
  • avoid sharing credentials, restricted network details, personal information, or proprietary material;
  • acknowledge operational-technology risk and never pressure others to bypass site authority, isolation, cybersecurity, or test procedures;
  • accept review of licensing, provenance, safety wording, protocol behavior, and the ARSAS/ARIEC61850 boundary as part of technical quality;
  • state clearly when a feature is available, preview, planned, or unverified.

Unacceptable conduct

The project does not accept:

  • harassment, personal attacks, discriminatory language, intimidation, or retaliation;
  • knowingly false claims about certification, affiliation, interoperability, safety, or test evidence;
  • publication of confidential project data, security-sensitive information, relay settings, or restricted captures;
  • instructions to operate equipment without the required authority and approved procedure;
  • copied proprietary source, documentation, UI assets, screenshots, tests, or restricted engineering material;
  • attempts to hide negative protocol evidence, unsafe behavior, provenance concerns, or licensing conflicts;
  • repeated disruption of issues or reviews after a decision and its engineering basis have been explained.

Enforcement

Maintainers may edit, hide, lock, or remove content; close issues or pull requests; or restrict participation when necessary to protect contributors, users, project integrity, legal provenance, confidential data, cybersecurity, or operational safety.

For sensitive conduct or security concerns, use GitHub private vulnerability reporting when appropriate, or request a private contact channel without publishing confidential details.