Issue Tracker
GitHub Issues
All bug reports, feature requests, and questions are tracked via GitHub Issues at:
Repository: https://github.com/ifmprotocol/ifm/issues
Issue Labels
The project uses the following label categories to organize issues:
| Label | Color | Description |
|---|---|---|
bug | #e11d21 | Confirmed bug or crash |
feature | #e1e4e8 | New feature or enhancement |
question | #f6e05e | Usage question or how-to |
documentation | #e11d21 | Docs improvements or clarifications |
good first issue | #7058ff | Welcome contribution for newcomers |
help wanted | #a24661 | Maintainer assistance needed |
invalid | #cfd3d7 | Issue not reproducible or out of scope |
wont fix | #e11d21 | Issue will not be addressed |
Issue Templates
The repository includes standardized issue templates to ensure all necessary information is provided:
Bug Report
---
name: Bug Report
about: Report a bug with IFM
title: ''
labels: ['bug']
assignees: ''
---
**Environment**
- IFM Version: `0.3.0-alpha`
- OS: (e.g., macOS 13, Windows 11, Ubuntu 22.04)
- Browser: (e.g., Chrome 115, Safari 17)
**Steps to Reproduce**
1.
2.
3.
**Expected Behavior**
...
**Actual Behavior**
...
**Additional Context**
- Log output (use `ifm logs --follow`)
- Screenshots/videos if applicableFeature Request
---
name: Feature Request
about: Suggest a new feature for IFM
title: ''
labels: ['feature']
assignees: ''
---
**Problem Statement**
...
**Proposed Solution**
...
**Alternatives Considered**
...
**Additional Context**Issue Workflow
- Open: Issue is created and labeled
- Triage: Maintainers review and assign priority
- Discussion: Community and maintainers discuss solution
- Implementation: Developer works on the fix/feature
- Review: Pull request reviewed and merged
- Close: Issue closed with resolution
Getting Help
- For questions: Use the
questionlabel or visit#ifm-protocolon Slack - For discussions: Join the
#ifm-devchannel on Slack - For urgent bugs: Tag
@ifm/protocol-maintainersin the issue
Reporting Security Issues
Security issues should be reported privately via email to security@ifm.sh rather than via public GitHub Issues. The security team will coordinate a responsible disclosure process.
Known Issues
| Issue | Status | Workaround |
|---|---|---|
Choppy audio on wireless | Being investigated | Increase jitter buffer |
Protected frequency access | Being investigated | Use correct access code format |
Rendezvous connection failed | Being investigated | Check NAT/firewall settings |