Introduce repo-metadata.toml as single source of truth for repo identity (org slug, maintainer email, canonical URLs) and add sync-metadata.yml workflow with a Python audit script that fails CI if any tracked file drifts back to pre-migration values. Bulk-replace across 24 tracked files: - kingchenc/wickra -> wickra-lib/wickra (URL segment) - kingchencp@gmail.com -> wickra.lib@gmail.com (maintainer email) - @kingchenc -> @wickra-lib (CODEOWNERS mention only) Person-name credits are preserved: LICENSE copyright holder, Cargo.toml authors handle, and CHANGELOG historical @kingchenc reference all remain unchanged. Crate / PyPI / npm package names also untouched. Merge this PR only after the kingchenc/wickra -> wickra-lib/wickra org transfer has happened on the GitHub side, otherwise all badges and repository links 404 until the transfer is performed.
1.6 KiB
Code of Conduct
Our pledge
We as members, contributors, and maintainers pledge to make participation in the Wickra project a respectful and welcoming experience for everyone, regardless of background or identity.
Our standards
Behaviour that helps build a positive community includes:
- Showing empathy and kindness toward others.
- Respecting differing opinions, viewpoints, and experiences.
- Giving and gracefully accepting constructive feedback.
- Taking responsibility for mistakes and learning from them.
- Focusing on what is best for the project and the community.
Behaviour that is not acceptable includes:
- Personal attacks, insults, or derogatory comments.
- Harassment of any kind, public or private.
- Publishing others' private information without explicit permission.
- Other conduct that would reasonably be considered inappropriate in a professional setting.
Scope
This Code of Conduct applies in all project spaces — the repository, issues, pull requests, and discussions — and when an individual is representing the project in public spaces.
Enforcement
Instances of unacceptable behaviour may be reported to the project maintainer at wickra.lib@gmail.com. All reports will be reviewed and investigated promptly and fairly, and the maintainer will respect the privacy and security of the reporter.
Maintainers may take any action they deem appropriate, including warnings, temporary bans, or permanent removal from the project, for behaviour that violates this Code of Conduct.
Attribution
This Code of Conduct is adapted from the Contributor Covenant, version 2.1.