Start with the help route published by the thing you are using. Product documentation and known issues may already contain the answer and remain available while every volunteer is asleep.

Packbase currently has no public status page, known-issues page, or account-support route in the web application. A signed-in person can open Help in the desktop rail to send product feedback. For a non-sensitive problem that cannot use that control, use the Wild HQ contact page, which opens ordinary email to Rek.

Volunteers use Discord for team coordination; a product may also publish a Discord help channel. Do not guess an invite, join an unrelated server, or direct-message a random volunteer for support.

Ask in the place that owns the problem

  • A usage question belongs in the product’s documented help space.
  • A reproducible public bug belongs in its public issue tracker when one is offered.
  • A contributor question belongs on the Wildbase Work task or the relevant Discord thread.
  • General account questions and non-sensitive notices about privacy, conduct, or security may use the contact route. It is ordinary email, not a confidential reporting channel.

If a conversation moves, leave a link or summary in the original place so the next person does not have to repeat the search.

Include enough to investigate

A useful report includes:

  • the product, page, or repository involved;
  • what you were trying to do;
  • the smallest reliable sequence that reproduces the problem;
  • what you expected and what happened instead;
  • the exact error wording, with secrets and personal data removed;
  • the browser, device, version, or environment when it changes the result;
  • whether the problem is still happening; and
  • a link to related tasks, pull requests, or status notices.

Screenshots can help with visual problems, but check them for names, email addresses, tokens, private messages, and other background information before sharing.

Keep private and dangerous details private

Never post passwords, session cookies, access tokens, private keys, recovery codes, unredacted customer information, or instructions that make an unfixed vulnerability easier to exploit.

Wild HQ does not currently have a secure channel and cannot safely accept secrets, private records, or exploitable vulnerability details. For a security problem, use the contact route only for a redacted notice that names the affected product and broadly describes the impact. A reply is still ordinary email and does not make the channel secure. If the problem cannot be described safely that way, do not send the detail through the current channels. If a credential is already exposed, revoke or rotate it first when you safely can.

Wild HQ also does not currently have a confidential or independent conduct-report process. The contact route sends ordinary email to Rek, Wild HQ’s founder and team lead. Use it only for a non-sensitive notice. If the concern is about Rek, Wild HQ has no conflict-free internal route; you may seek outside support or contact an appropriate authority without reporting to Wild HQ first.

The Wild HQ contact route is not an emergency service. If someone faces immediate danger, contact the appropriate local emergency service or authority first.

How reports are prioritised

Triage follows harm and reach:

  1. active security exposure, safety risk, privacy breach, or data loss;
  2. a widespread outage or a failure blocking access;
  3. an accessibility barrier or serious loss of core function;
  4. a reproducible defect with a workaround; and
  5. questions, improvements, and edge cases.

Donation status, subscription level, follower count, job title, repeated mentions, and personal access to a volunteer do not buy priority.

What a response means

Wild HQ is volunteer-run. Help is best effort and carries no default response-time promise. A reply may be a workaround, a request for detail, a link to an existing explanation, a candid “not now”, or a decision not to make the requested change.

No reply does not mean the problem is unimportant. It may mean nobody with the needed time or access is available. A respectful follow-up with new information is useful. Repeated messages across channels, pressure through private accounts, threats, and harassment are not.

When the team accepts work, the durable task should say so. Discord enthusiasm is not a delivery promise.

Volunteers responding to an active Packbase failure should use Incidents and maintenance.