QuantumGrid OS is an OpenWrt-based networking operating system developed by NetCore Technologies.
The project focuses on high-performance networking, gaming optimization, Wi-Fi intelligence, security, 5G/cellular connectivity, telemetry, hardware acceleration, and a modern management experience.
We welcome contributions that improve QuantumGrid OS, whether they are code changes, packages, hardware support, documentation, testing, UI improvements, or bug fixes.
Before contributing:
- Fork the QuantumGrid OS repository.
- Clone your fork locally.
- Create a dedicated branch for your changes.
- Make your changes.
- Test your changes.
- Commit your work clearly.
- Push your branch.
- Open a Pull Request.
Example:
git clone https://github.com/NetCore-Technologies/QuantumGrid-OS.git
cd QuantumGrid-OS
git checkout -b feature/my-featureYou can contribute new or improved packages for:
- Networking
- Wi-Fi
- Gaming
- Security
- Monitoring
- 5G and cellular
- Hardware acceleration
- System management
- QuantumGrid-specific services
Make sure new packages are properly configured and tested before submitting them.
Performance improvements are an important part of QuantumGrid OS.
Contributions can include:
- Faster packet processing
- Reduced latency
- Improved CPU utilization
- Hardware acceleration
- NSS/EDMA improvements
- SQM and bufferbloat improvements
- Network throughput improvements
- Faster boot times
- Lower memory usage
If possible, include before-and-after benchmarks with your Pull Request.
Wi-Fi contributions can include:
- Driver improvements
- Channel management
- Wireless diagnostics
- Roaming improvements
- Multi-band optimization
- Wi-Fi telemetry
- 5 GHz / 6 GHz improvements
- Signal and interference monitoring
When submitting hardware-specific changes, clearly state the hardware that was tested.
QuantumGrid OS includes features designed to improve gaming and latency.
Contributions can include:
- QoS improvements
- SQM improvements
- Bufferbloat reduction
- Latency monitoring
- Traffic prioritization
- Gaming device detection
- Connection monitoring
- WAN optimization
Avoid claiming performance improvements without testing them.
Contributions for cellular networking are welcome.
Examples include:
- Modem support
- QMI/MBIM improvements
- APN management
- Signal monitoring
- Cellular diagnostics
- Automatic failover
- 4G/5G management
- Modem recovery
Include modem model, chipset, firmware version, and relevant configuration when submitting hardware-specific changes.
QuantumGrid OS aims to provide a modern networking interface.
UI contributions should maintain the QuantumGrid design direction and focus on:
- Clear navigation
- Responsive layouts
- Network telemetry
- Useful diagnostics
- Accessible controls
- Dark/light themes
- Consistent components
- Good performance
For UI Pull Requests, include screenshots when they help demonstrate the change.
Security improvements are encouraged.
Examples include:
- Firewall improvements
- Safer defaults
- Authentication improvements
- Security monitoring
- Permission fixes
- Vulnerability fixes
- Secure update mechanisms
Do not include passwords, private keys, tokens, or other sensitive information in commits or Pull Requests.
For security vulnerabilities, follow the repository's security reporting process instead of publicly posting sensitive exploit details.
When reporting a bug, provide as much useful information as possible.
Include:
- Device model
- SoC/platform
- QuantumGrid OS version
- OpenWrt version where relevant
- Installed packages
- Configuration
- Steps to reproduce
- Expected behavior
- Actual behavior
- Relevant logs
- Screenshots where useful
A good bug report should allow another developer to reproduce the problem.
When adding support for new hardware, provide:
Device:
SoC:
RAM:
Flash:
Ethernet:
Wi-Fi:
Modem:
OpenWrt Target:
OpenWrt Subtarget:
QuantumGrid Configuration:
Testing Performed:
Do not mark hardware as fully supported unless it has actually been tested.
Always test changes before opening a Pull Request.
At minimum, check:
git diff --check
git statusFor build changes, build the affected target or package.
For networking changes, test the relevant networking functionality.
For UI changes, test the affected pages and responsive layouts.
For hardware changes, test on the actual target hardware whenever possible.
Use descriptive branch names.
Examples:
feature/wifi-telemetry
feature/5g-failover
feature/gaming-qos
fix/wifi-crash
fix/modem-detection
perf/nss-networking
ui/dashboard-telemetry
docs/build-guide
Avoid working directly on the main branch.
Use clear commit messages that explain what changed.
Preferred formats:
feat: add 5G signal monitoring
fix: correct modem detection
perf: improve packet processing
wifi: improve channel scanning
security: harden firewall defaults
ui: improve network dashboard
docs: update build instructions
build: update firmware workflow
test: add Wi-Fi regression tests
refactor: simplify telemetry service
Keep commits focused on one logical change whenever possible.
Before opening a Pull Request:
- Make sure your branch is up to date.
- Test your changes.
- Check for unintended modifications.
- Run
git diff --check. - Write a clear Pull Request description.
- Include screenshots or benchmarks where useful.
A Pull Request should explain:
Describe the implementation.
Explain the problem being solved.
Explain what hardware, firmware, targets, or environments were tested.
Mention compatibility issues, limitations, dependencies, or anything maintainers should know.
Documentation improvements are always welcome.
You can contribute:
- Build guides
- Installation instructions
- Hardware documentation
- Troubleshooting guides
- Package documentation
- Configuration examples
- Developer documentation
- API documentation
Keep documentation accurate and avoid documenting features that have not been tested.
When adding dependencies:
- Prefer existing OpenWrt packages.
- Avoid unnecessary dependencies.
- Consider firmware size.
- Consider RAM and CPU requirements.
- Check upstream maintenance status.
- Verify licensing compatibility.
Never commit:
.env
private keys
passwords
API tokens
SSH keys
personal configuration
private certificates
user data
large generated build artifacts
Check your changes before pushing:
git status
git diffAll contributions must comply with the licenses used by QuantumGrid OS and its dependencies.
Do not submit code, images, documentation, or other assets that you do not have permission to redistribute.
For larger changes, discuss the idea before spending significant development time on it.
A typical contribution process is:
Idea
↓
Issue / Discussion
↓
Fork
↓
Feature Branch
↓
Development
↓
Testing
↓
Pull Request
↓
Review
↓
Changes / Approval
↓
Merge
Keep Pull Requests focused and make changes requested during review before asking for approval again.
Contributors are expected to communicate respectfully and constructively.
Technical disagreements are welcome, but discussions should remain focused on the project, implementation, and technical evidence.
Harassment, personal attacks, spam, and deliberately disruptive behavior are not acceptable.
We appreciate all feedback, bug reports, testing, ideas, documentation, and code contributions that help improve QuantumGrid OS.
Every contribution helps make QuantumGrid OS better.