chore: native repository conversion — remove FreeCAD/GitHub artifacts (#367)
All checks were successful
Build and Test / build (pull_request) Successful in 29m36s
All checks were successful
Build and Test / build (pull_request) Successful in 29m36s
- Delete .github/ directory (60 files, ~4600 lines of unused GitHub Actions workflows, FreeCAD-branded issue/PR templates, problem matchers, scripts, and images) - Delete .packit.yaml (Fedora COPR packaging, unused) - Delete SECURITY.md (FreeCAD-specific security policy) - Update .pre-commit-config.yaml to remove .github file pattern - Update .gitignore to remove .github/ whitelist - Rewrite CODE_OF_CONDUCT.md for Kindred Create community - Rewrite PRIVACY_POLICY.md covering Silo integration, update checker, origin system, and local storage Gitea equivalents (.gitea/workflows/, .gitea/ISSUE_TEMPLATE/, .gitea/pull_request_template.md) are already in place. Closes #367
This commit is contained in:
@@ -1,8 +1,8 @@
|
||||
# FreeCAD Project Code of Conduct
|
||||
# Kindred Create Code of Conduct
|
||||
|
||||
## Statement
|
||||
|
||||
The FreeCAD Project community covers people from a wide variety of countries,
|
||||
The Kindred Create community includes people from a wide variety of countries,
|
||||
backgrounds and positions. This global diversity is a great strength of the
|
||||
project, but can also lead to communication issues, which may in turn cause
|
||||
unhappiness. To maximise happiness of the project community taken as a whole,
|
||||
@@ -55,12 +55,13 @@ further defined and clarified by project maintainers.
|
||||
## Enforcement
|
||||
|
||||
Instances of abusive, harassing, or otherwise unacceptable behavior may be
|
||||
reported by contacting any of the community admins or moderators at
|
||||
https://forum.freecad.org/memberlist.php?mode=team . All
|
||||
complaints will be reviewed and investigated and will result in a response that
|
||||
is deemed necessary and appropriate to the circumstances. The project team is
|
||||
obligated to maintain confidentiality with regard to the reporter of an incident.
|
||||
Further details of specific enforcement policies may be posted separately.
|
||||
reported by opening an issue at
|
||||
https://git.kindred-systems.com/kindred/create/issues or by contacting the
|
||||
Kindred Systems project maintainers directly. All complaints will be reviewed
|
||||
and investigated and will result in a response that is deemed necessary and
|
||||
appropriate to the circumstances. The project team is obligated to maintain
|
||||
confidentiality with regard to the reporter of an incident. Further details
|
||||
of specific enforcement policies may be posted separately.
|
||||
|
||||
Project maintainers who do not follow or enforce the Code of Conduct in good
|
||||
faith may face temporary or permanent repercussions as determined by other
|
||||
|
||||
Reference in New Issue
Block a user