...
- RISE is a tool for efficient execution within OSS communities and projects, focusing on:
- Commerical-grade RISC-V support.
- Self-sustaining support for RISC-V within upstream projects as a long term goal.
- No posturing - RISE represents individual interests of RISE members.
- RISE is complementary, not duplicative. WGs do not duplicate existing project/community infrastructure (including "RISE forks", "RISE releases", additional discussion lists/forums)
- WG embrace transparency, building bridges with all stakeholders. This includes active sharing of RISE priorities/status in a manner that is usual for the upstream project.
- WGs do not silo themselves off and are responsible for tracking their ecosystems (being aware of what is being done, why, what blockers/challenges exist).
Confluence
Confluence is the main way WGs interact with internal and external parties. The WG pages are used to report updates for the TSC meetings, and every RISE-funded/prioritized project must have an up-to-date page listing that helps answer what is being done, why it's important, how is it going to be done and when it will be complete:
- Clear definition of work being done
- Timelines
- Components, repositories, stakeholders
- Measure of success
- Requirements from RISE (if any)
- Dependencies, including any RVI specification dependencies.
- Periodic Updates, including:
- Relevant technical decisions that are impacting the project
- Delays
- Links to important technical discussions (on upstream channels, of course)
- References to patches.
Confluence is viewed as the single source of truth. No entries == no progress. Anyone should be able to view the page and get at least a rough sense of what's going on. This has implications on the quality of how the information is presented.
Confluence is not an engineering log or an attic for obsolete information. Pages need to be maintained and revised to reflect reality. All in all, this enables passive updates of RISE progress to all interested parties.
Work Group Mailing Lists
Everything is done through https://groups.io/groups. In fact, you can even read and post message through the web interface if you don't want to see it in your regular inbox.
...
- Identifying and prioritizing projects, by de-duplicating and analyzing input from all WG participants.
- Lead necessary project scoping activities, where this helps RISE to appropriately staff/fund projects.
- Leading WG participants in maintaining project info on the RISE wiki (not doing all the work themselves).
- Leading WG participants to track ecosystem, build bridges with relevant upstream and external communities.
- Regularly collect and report to the TSC project status, progress and challenges on a monthly basis. Don't assume WG members to be proactive.
- Helping direct new member engineers who wish to participate in these areas to the appropriate project leads.
- Helping build consensus around implementation approaches when possible.
- Working with other WG leads where dependencies or commonalities exist.
...