authored by Ludovic Henry, Qualcomm
Each RISE Working Group (WG) now tracks its project work directly on GitHub, instead of on Confluence. If you’re following, or want to start following, what a WG is doing, GitHub is now the place to look.
What’s changed
Every WG has its own public GitHub repository under the riseproject-dev organization, paired with a GitHub Projects board. The individual work items that used to live as pages in the RISE wiki have been migrated into GitHub issues, carrying over their status, upstream links, dependencies, and history.
The full list of Working Groups and their respective repositories and project boards is maintained at github.com/riseproject-dev#working-groups:
| Working Group | Repository | Links |
|---|---|---|
| Enablement and Optimization | System Libraries | project board |
| Compilers & Toolchains | project board | |
| Language Runtimes | project board | |
| Developer Tooling | Developer Infrastructure | project board |
| Simulator / Emulator | project board | |
| Platform | Firmware | project board |
| Distro Integration | project board | |
| Kernel & Virtualization | project board | |
| Security Software | project board | |
| AI/ML | AI/ML | project board |
| Microcontroller Software | Microcontroller Software | project board |
All of these repositories are public, so anyone (RISE member or not) can browse the work each WG is tracking, see what’s in progress, and follow along without needing access to Confluence.
Where to find things now
- Project status and open work items live as issues in each WG’s repository, e.g. system-libraries-wg/issues.
- A birds-eye view of progress for each WG is available on its GitHub Projects board, linked from that WG’s repository README.
- Supporting documentation – things like meeting notes, developer environment setup, and background material that doesn’t map to a single tracked work item – lives as markdown files under each repository’s docs/ folder, or directly in the README.
- Old wiki pages that were migrated now simply point to their new home on GitHub, so any link you may have bookmarked from before will redirect you to the right place.
What stays on the RISE wiki
This migration covers Working Group content only. TSC, Project, Governing Board, and other RISE content is unaffected and remains on the RISE wiki as before.
How to interact with a Working Group’s repository going forward
- Propose work, report a gap, or ask a question by filing an issue in the relevant WG repository.
- Track progress using that WG’s GitHub Projects board.
- Each WG is free to use whatever GitHub features fit how it works – issues, pull requests, actions, releases, packages, and so on.
- Repositories are expected to be kept up to date, so that the state of a repository reflects the actual state of the work. This is what makes it possible for anyone, inside or outside RISE, to passively track how a project is progressing without having to ask around.
- As a reminder: work that isn’t written up isn’t a RISE project. Documenting it – on GitHub now – is what enables collaboration and avoids duplicated effort across companies.
If you’ve contributed to a WG before, the best place to start is the repository and Projects board for your area of interest, linked in the table above.
