kingchenc
d59cd44043
* docs: standardise language naming and add binding security sections Canonical binding list everywhere: Rust, Python, Node.js, WASM, C, C++, C#, Go, Java, R. Use C# (not .NET) as the language label, WASM (not WebAssembly) in prose, and frame the C ABI as a hub rather than a list item. - Bump stale indicator counts (200+ -> 514) and family count (sixteen -> twenty-four) in the Node/Python/WASM and docs READMEs. - Add a short Security section to all eight binding READMEs. - Relabel benchmark rows (C -> C / C++, C# / .NET -> C#). - Fix the 'language stecker' wording in the C#/Go/R API intros. - Documentation only; no code or public API changes. * release.yml: extend install snippets and expose version output Add the missing registry installs to the release body (dotnet, go, Gradle/ Maven Central, r-universe) alongside cargo/pip/npm, and expose a v-stripped 'version' output from the tag step for the Gradle coordinate. Also fix the C-ABI language order in the assets note (C# before Go). * release.yml: correct the release body (10 languages, all registries) Reframe the tagline to '10 languages' (native Rust/Python/Node.js/WASM + a C ABI hub for C, C++, C#, Go, Java, R) instead of '4 language registries', note that C#/Java/Go/R publish to NuGet/Maven/Go/r-universe via their own jobs, and tidy the Node.js label and the C-ABI hub list.
38 lines
1.3 KiB
Markdown
38 lines
1.3 KiB
Markdown
# Support
|
|
|
|
Thanks for using Wickra! Here is where to get help, depending on what you need.
|
|
|
|
## Documentation first
|
|
|
|
Most questions are answered in the documentation:
|
|
|
|
- **Docs site:** <https://docs.wickra.org> — quickstarts for Rust, Python,
|
|
Node.js, WASM, C, C++, C#, Go, Java and R, a per-indicator reference, warmup periods, the
|
|
data layer, and an FAQ.
|
|
- **README:** <https://github.com/wickra-lib/wickra#readme> — installation and a
|
|
quick overview.
|
|
- **API docs (Rust):** <https://docs.rs/wickra>.
|
|
|
|
## Questions and help
|
|
|
|
- Ask a question with the
|
|
[question issue template](.github/ISSUE_TEMPLATE/question.md).
|
|
- Browse [existing issues](https://github.com/wickra-lib/wickra/issues) — your
|
|
question may already be answered.
|
|
|
|
## Bugs and feature requests
|
|
|
|
- **Bugs:** use the bug-report issue template.
|
|
- **Feature requests / new indicators:** use the feature-request template.
|
|
|
|
## Security issues
|
|
|
|
Please do **not** report security vulnerabilities through public issues. Follow
|
|
the process in [`SECURITY.md`](SECURITY.md) (private GitHub advisory or email).
|
|
|
|
## Support expectations
|
|
|
|
Wickra is maintained by a single maintainer on a best-effort basis. Issues are
|
|
triaged and acknowledged as time allows; there is no commercial support or SLA.
|
|
Clear, reproducible reports get help fastest.
|