TREK Community Forums and Support Channels: Where to Get Help

The TREK project provides official support through a Discord server for real-time chat, GitHub Issues for bug tracking, and a public Kanban roadmap for project visibility.

The TREK repository (mauriceboe/TREK) maintains several dedicated community hubs designed to streamline user support and contributor collaboration. Whether you are troubleshooting an installation, requesting a new feature, or planning to submit code, knowing which channel to use ensures faster resolution and keeps the project organized. This guide maps every official support avenue directly to its source in the repository files.

Discord Server: Real-Time Community Support

The Discord server serves as the primary real-time communication hub for the TREK community. According to CONTRIBUTING.md at line 7, contributors should ask questions in Discord before opening a pull request, reinforcing its role as the first line of support.

• Purpose: Instant troubleshooting, feature brainstorming, and maintainer coordination.
• Access: Join via the invite badge embedded in README.md at line 25: https://discord.gg/NhZBDSd4qW.
• Additional locations: The same link appears in wiki/_Footer.md and is referenced in wiki/Notifications.md for webhook integrations.

When you need immediate clarification on configuration or usage, search the Discord channels first—the community typically resolves common questions within minutes.

GitHub Issues: Formal Bug Reports and Feature Requests

For structured bug reports or concrete feature proposals, use GitHub Issues. This channel creates a permanent, searchable public record tracked directly in the repository.

• Location: https://github.com/mauriceboe/TREK/issues (linked from README.md line 21).
• Templates: The repository provides structured templates via .github/ISSUE_TEMPLATE/bug_report.yml, ensuring you include necessary environment details and reproduction steps.
• Security: Sensitive security disclosures should also route through GitHub Issues to maintain accountability.

Use Issues when you have identified a reproducible bug or can articulate a specific feature requirement with clear acceptance criteria.

GitHub Discussions: Community Q&A

When your topic is broader than a bug report but requires community input, GitHub Discussions offers a forum-style format for Q&A and idea exchange. This channel is ideal for architecture questions, usage patterns, or exploratory feature conversations that do not yet warrant a formal issue.

• Access: Visit https://github.com/mauriceboe/TREK/discussions.
• Note: Availability depends on repository settings, but when enabled, it serves as the middle ground between informal Discord chat and formal Issues.

Public Kanban Roadmap

The public Kanban board provides transparency into the project's development pipeline. Monitor this board to see what features are planned, in progress, or under review before submitting duplicate requests.

• URL: https://kanban.pakulat.org/shared/I4wxF6inOOMB0C6hH6kQm3efyNxFjwyI (referenced in README.md at line 27).
• Use case: Check here before opening feature requests to see if the functionality is already on the maintainers' radar.

Recommended Support Workflow

Based on the repository's documentation structure, follow this hierarchy when seeking help:

1. Search Discord – Check existing channels for similar questions.
2. Open a GitHub Issue – Use the issue templates for verified bugs or specific feature requests.
3. Post in GitHub Discussions – For open-ended questions or design debates.
4. Check the Kanban Roadmap – Verify existing plans before proposing new work.

Embedding Support Links in Documentation

When creating your own documentation or issue comments, use these markdown snippets derived from the repository's official badges:

<!-- Discord invite badge -->
[![Discord](https://img.shields.io/badge/Discord-join-5865F2?style=for-the-badge)](https://discord.gg/NhZBDSd4qW)

<!-- Link to open a new GitHub issue -->
[Report a bug or request a feature](https://github.com/mauriceboe/TREK/issues/new/choose)

<!-- Link to the public roadmap kanban -->
[View the public roadmap](https://kanban.pakulat.org/shared/I4wxF6inOOMB0C6hH6kQm3efyNxFjwyI)

Summary

• Discord (https://discord.gg/NhZBDSd4qW) is the primary real-time support channel, referenced in README.md, CONTRIBUTING.md, and the wiki footer.
• GitHub Issues provide formal bug tracking with templates located in .github/ISSUE_TEMPLATE/bug_report.yml.
• GitHub Discussions host community Q&A when enabled.
• Kanban Roadmap (kanban.pakulat.org) displays current development priorities.
• Always consult Discord before opening pull requests, as mandated in CONTRIBUTING.md.

Frequently Asked Questions

How do I join the TREK Discord server?

Access the permanent invite link at https://discord.gg/NhZBDSd4qW. This link appears as a badge in README.md at line 25 and in wiki/_Footer.md, providing immediate access to the real-time community chat.

Should I open a GitHub Issue or ask in Discord first?

Ask in Discord first for troubleshooting and quick questions. Open a GitHub Issue only when you have confirmed a bug or have a specific feature request, using the templates provided in .github/ISSUE_TEMPLATE/bug_report.yml to ensure complete information.

Where can I see what features are currently being developed?

View the public Kanban roadmap at https://kanban.pakulat.org/shared/I4wxF6inOOMB0C6hH6kQm3efyNxFjwyI, linked from README.md at line 27. This board displays planned and in-progress work, helping you avoid submitting duplicate feature requests.

Is there a specific process for contributing code to TREK?

Yes. According to CONTRIBUTING.md at line 7, you must ask in Discord before opening a pull request. This policy ensures coordination with maintainers and prevents duplicate or conflicting work before you invest development effort.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}