LoopX Community Support: Channels, Guidelines, and Best Practices

LoopX provides best-effort community support through GitHub Issues for bugs, GitHub Discussions for usage questions, Discord for informal peer help, and private security advisories, with no guaranteed response time or commercial SLA.

LoopX is an open-source, community-driven project hosted at huangruiteng/loopx. Understanding the LoopX community support structure is essential for getting timely help with bugs, configuration questions, or contribution guidance. The project maintains explicit documentation in SUPPORT.md and CONTRIBUTING.md that defines how users should interact with maintainers and other contributors across different channels.

Official Support Channels

Bug Reports and Feature Requests via GitHub Issues

For reproducible bugs or installation failures, use GitHub Issues at https://github.com/huangruiteng/loopx/issues/new/choose. The repository provides issue templates that prompt for environment details and reproduction steps. Feature requests should include a concrete problem statement, desired outcome, and the smallest useful change. The maintainers triage these publicly, though there is no guaranteed timeline for resolution.

Usage Questions and Design Discussion via GitHub Discussions

For configuration help, workflow design questions, or general "how-to" queries that are not confirmed bugs, use GitHub Discussions in the Q&A category at https://github.com/huangruiteng/loopx/discussions/categories/q-a. This keeps the issue tracker focused on actionable defects while allowing the community to explore implementation strategies collaboratively.

Security Vulnerability Reporting

Suspected unpatched vulnerabilities must be reported through Private Vulnerability Reporting at https://github.com/huangruiteng/loopx/security/advisories/new. Do not post security issues publicly in Issues or Discord. The repository's SECURITY.md defines the disclosure process and embargo policies.

Informal Community Chat on Discord

For on-boarding assistance, workflow comparison, or community conversation, join the Discord server at https://discord.gg/XmGgQyCFZd. This channel is not an authoritative support record and operates on a best-effort basis; critical bugs should still be filed in GitHub Issues for tracking.

How to File an Effective Support Request

According to SUPPORT.md, effective requests must include:

• LoopX version (or commit SHA) and the execution surface (host/runtime, command, workflow).
• Expected versus actual behavior.
• The smallest reproducible, public-safe test case.

Before posting, sanitize all content by removing credentials, private repository content, raw agent sessions, internal links, and sensitive logs. If material cannot be made public-safe, do not upload it to public channels.

Contributing to the Community

The LoopX community coordinates work through the Contributor Task Board documented in CONTRIBUTOR_TASKS.md. This public board lists work items that newcomers can claim. All pull requests must follow the guidelines in CONTRIBUTING.md, including code style, testing requirements, and commit message conventions.

Community Interaction Workflow

The project follows a standard four-step workflow:

1. Search first – Check existing issues or discussions for duplicates.
2. Post – Use the appropriate channel with a clear, concise description.
3. Iterate – Respond to maintainer requests for smaller reproductions or accept redirection to better channels.
4. Follow-up – Track fixes via linked issues or PRs; note that there is no guarantee of a fix or specific timeline.

Example: Creating an Issue via GitHub API

When automating issue creation, ensure your payload matches the repository's template expectations:

POST https://api.github.com/repos/huangruiteng/loopx/issues
Authorization: token <YOUR_PERSONAL_TOKEN>
Content-Type: application/json

{
  "title": "Bug: loopx doctor fails on macOS 14",
  "body": "## Environment\n- LoopX version: 0.9.3 (commit a1b2c3d)\n- macOS 14.0.1\n- Python 3.11.5\n\n## Steps to reproduce\n1. Run loopx doctor\n2. Observe traceback ...\n\n## Expected behavior\nloopx doctor should complete without error.\n\n## Additional context\n[Link to minimal reproducible example](https://gist.github.com/…)",

  "labels": ["bug"]
}

Example: Posting to Discussions via cURL

For programmatic interaction with the Q&A board:

curl -X POST \
  -H "Authorization: token <YOUR_TOKEN>" \
  -H "Accept: application/vnd.github.v3+json" \
  https://api.github.com/repos/huangruiteng/loopx/discussions/123/comments \
  -d '{"body":"I am seeing this same issue on Ubuntu 22.04. Here is a minimal script that reproduces it..."}'

Summary

• LoopX provides best-effort community support with no commercial SLA or guaranteed response time.
• GitHub Issues handle bugs and feature requests; GitHub Discussions handle usage questions.
• Security vulnerabilities must be reported privately via GitHub Security Advisories, not public channels.
• Discord serves informal peer support but is not authoritative.
• Contributors should consult CONTRIBUTOR_TASKS.md for available work items and CONTRIBUTING.md for submission guidelines.
• All support requests must be sanitized to remove credentials and sensitive data before posting publicly.

Frequently Asked Questions

Is there commercial support available for LoopX?

No. According to the repository's SUPPORT.md, LoopX is an open-source project that provides support on a best-effort basis only. There is no paid support tier, service-level agreement, or guaranteed response time. Enterprises requiring dedicated support must rely on community channels or engage independent contractors familiar with the codebase.

What is the expected response time for GitHub Issues?

There is no guaranteed response time. The community triages issues based on severity, clarity of the reproduction steps, and maintainer availability. Issues with minimal reproducible examples and clear environment details in SUPPORT.md format typically receive faster attention. Contributors can track progress via linked pull requests, but no timeline commitments are made.

Where should I report a security vulnerability in LoopX?

Report suspected unpatched vulnerabilities through GitHub's Private Vulnerability Reporting at https://github.com/huangruiteng/loopx/security/advisories/new. The SECURITY.md file defines the full disclosure process. Do not post security concerns in public Issues, Discussions, or Discord, as this could expose users to risk before a patch is available.

How can I find tasks to contribute to LoopX?

New contributors should consult the Contributor Task Board in CONTRIBUTOR_TASKS.md at the repository root. This file lists community-visible work items, their difficulty levels, and claim status. Once you identify a task, follow the workflow in CONTRIBUTING.md to submit a pull request, ensuring you reference the task number in your commit messages.

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