Practical collaboration around real embedded work.
ForgeUI welcomes developers who enjoy embedded systems, UI tooling, hardware validation, technical writing and practical product development. Contribution starts through public GitHub collaboration.
Work Alongside RTech
Take on a focused issue, test hardware, improve documentation, propose a board port or develop a complete feature. This does not imply employment, payment or formal membership.
GitHub Issues
Coordinate publicly, document scope and attach reproducible evidence.
Pull Requests
Coordinate publicly, document scope and attach reproducible evidence.
Documentation improvements
Coordinate publicly, document scope and attach reproducible evidence.
Hardware testing
Coordinate publicly, document scope and attach reproducible evidence.
Board-port proposals
Coordinate publicly, document scope and attach reproducible evidence.
Example projects
Coordinate publicly, document scope and attach reproducible evidence.
Design reviews
Coordinate publicly, document scope and attach reproducible evidence.
Release testing
Coordinate publicly, document scope and attach reproducible evidence.
ForgeUI Open Development Review
A regular public development review is planned as the community grows. Timing and format will be announced through GitHub. It would cover releases, engineering work, hardware proof, contributions, proposals, board ports, documentation and next priorities.
Governance and support
Official
Reviewed, tested on named hardware and documented by the core project.
Community
Owned by named contributors, supported by evidence, with limitations documented.
Experimental
Useful for development and testing, incomplete and subject to breaking changes.
Bugs, ideas and collaboration currently use GitHub Issues. Code changes use Pull Requests. Discussions is not currently enabled.