JonKazama-Hellion
1b63765caa
Closes the remaining gaps in GitHub's community-standards check, adds explicit privacy and dependency documentation matching the plugin's "DSGVO-by-design" claim, and removes the stale upstream Crowdin artefact so the repo no longer suggests it ships its own translation pipeline. New community-health files: - CODE_OF_CONDUCT.md: project-specific, short and direct, single reporting path to kontakt@hellion-media.de - CONTRIBUTING.md: scope, accepted vs declined contributions, build and test instructions, EUPL-1.2 contribution terms, translation policy split between Hellion-specific (here) and upstream strings (Chat 2 repo) - SUPPORT.md: routing for bugs, security, privacy and casual feedback - .github/PULL_REQUEST_TEMPLATE.md: summary, change-type checklist, testing notes, compatibility notes for migrations and manifest fields, contribution checklist - .github/FUNDING.yml: comments-only file, no platforms enabled, points donors at the upstream Chat 2 maintainers' Ko-fi pages New privacy and compliance documentation: - PRIVACY.md: what the plugin stores locally (config, SQLite, EmoteCacheV1), retention defaults, the two outbound network calls (BetterTTV API+CDN with ShowEmotes opt-out, Square Enix Lodestone font once-off), explicit no-telemetry statement, GDPR Art. 15/17/18/20/21 rights mapped to plugin features, third-party privacy-policy links - THIRD_PARTY_NOTICES.md: direct NuGet dependencies with versions pinned to v0.5.4 (MessagePack, Microsoft.Data.Sqlite, morelinq, Pidgin, SixLabors.ImageSharp under Six Labors Split License 1.0), Dalamud SDK and .NET tooling, bundled Exo 2 font (OFL-1.1) and plugin icon, network-touch status per component, re-audit commands Crowdin cleanup: - crowdin.yml deleted (was upstream Chat 2's project_id 663694, pointed at /ChatTwo/Resources/Language.resx, never wired to HellionChat strings) - README, CONTRIBUTING and CODE_OF_CONDUCT no longer suggest HellionChat operates a Crowdin project; remaining mentions are explicitly framed as upstream Chat 2's workflow Contact and version consistency: - Maintainer email switched from maintainer@hellion-media.de to kontakt@hellion-media.de in SECURITY.md and NOTICE.md - README version references updated to 0.5.4 (header, project status block) and the update-tag pattern generalised from v0.1.x to v0.X.Y - bug_report.yml version placeholder bumped to 0.5.4 - Project-documents table added to README footer linking all health and reference files in one place Release-body automation: - .github/workflows/release.yml now extracts the matching version block from ChatTwo/HellionChat.yaml's changelog and combines it with a static install / docs footer (custom-repo URL, project document links, licence) before passing the result to softprops/action-gh-release@v3 via body_path - Workflow fails fast if no changelog block exists for the tagged version, automating the existing "yaml + repo.json + release body kept in sync" rule - Tag value passed via env: TAG_NAME with strict ^v\d+\.\d+\.\d+$ validation before any string concatenation, so the tag input cannot break out into shell evaluation
51 lines
1.7 KiB
Markdown
51 lines
1.7 KiB
Markdown
# Support
|
|
|
|
HellionChat is a small hobby project maintained by one person. There
|
|
are a few different paths depending on what you need; please pick the
|
|
one that matches.
|
|
|
|
## Bugs and feature requests
|
|
|
|
GitHub issues, using the templates:
|
|
|
|
- [Bug report](https://github.com/JonKazama-Hellion/HellionChat/issues/new?template=bug_report.yml)
|
|
- [Feature request](https://github.com/JonKazama-Hellion/HellionChat/issues/new?template=feature_request.yml)
|
|
|
|
Please search [existing issues](https://github.com/JonKazama-Hellion/HellionChat/issues?q=is%3Aissue)
|
|
first. Duplicates get closed and pointed at the original.
|
|
|
|
## Security
|
|
|
|
Do **not** open a public issue for security-relevant findings. Use
|
|
the private advisory route described in [SECURITY.md](SECURITY.md):
|
|
|
|
- [Private vulnerability advisory](https://github.com/JonKazama-Hellion/HellionChat/security/advisories/new)
|
|
- Email `kontakt@hellion-media.de`
|
|
|
|
## Privacy questions
|
|
|
|
Specific questions about what HellionChat does or does not store and
|
|
send are covered in [PRIVACY.md](PRIVACY.md). For follow-ups beyond
|
|
that document:
|
|
|
|
- Email `kontakt@hellion-media.de`
|
|
|
|
## Quick questions and casual feedback
|
|
|
|
Discord DM `@j.j_kazama`. Bug reports still go through the issue
|
|
tracker so they can be tracked, but a quick "is this a bug or am I
|
|
holding it wrong" message is fine.
|
|
|
|
## Upstream Chat 2 issues
|
|
|
|
If the issue exists in upstream Chat 2 too, please report it at
|
|
[Infiziert90/ChatTwo](https://github.com/Infiziert90/ChatTwo/issues).
|
|
That keeps the original maintainers in the loop and helps everyone
|
|
who uses Chat 2 directly.
|
|
|
|
## Response times
|
|
|
|
Weekdays during European business hours. Weekends and FFXIV patch
|
|
days, replies will be slower. A few days of silence on a non-urgent
|
|
issue is normal; pinging once after a week is fine.
|