Community
Welcome to the Arcan community. Whether you're deploying your first secret or building a custom plugin, we're here to help.
Get Help
GitHub Discussions (Q&A) — the best place to ask questions. Search existing answers first, then post your question with your Arcan version and platform.
Report a Bug
GitHub Issues — use the bug report template. Include arcan doctor output and the failing command with --debug.
Suggest a Feature
GitHub Discussions (Ideas) — describe what you'd like, why you need it, and any alternatives you've considered.
Share Your Setup
GitHub Discussions (Show and Tell) — share your Arcan deployment, custom plugins, or integrations with the community.
Contribute
We welcome contributions of all kinds — code, documentation, plugins, and bug reports.
How to contribute:
- Fork the repository
- Create a feature branch (
git checkout -b my-feature) - Write your code with tests (
go test ./...) - Format and vet (
go fmt ./... && go vet ./...) - Open a Pull Request with a clear description
What we look for:
- Tests for new functionality
slogfor logging (neverlog.Printf)- Error messages that answer: what failed, why, what now
- No unnecessary dependencies
See CONTRIBUTING.md for full guidelines.
Plugin Contributions
Built a custom plugin? We'd love to see it. Share it in Discussions (Show and Tell) or open a PR to add it to the official registry.
See the SDK Reference for plugin development documentation.
Response SLAs
We publish response commitments on every GitHub issue:
| Type | Response Time |
|---|---|
| Security vulnerabilities | 24 hours |
| Bug reports | 48 hours |
| Feature requests | 5 business days |
| Q&A discussions | Best effort (community + maintainers) |
Code of Conduct
We follow the Contributor Covenant v2.1. Be respectful, be constructive, focus on the technical problem. Report violations to [email protected].
Language
All issues, discussions, and contributions should be in English to ensure accessibility and effective moderation.