Role w.r.t. Member Companies

• Work Groups prioritize and prefer RISE members to external parties.

Role w.r.t. External Parties

External parties include all relevant non-RISE stakeholders for the WG's work. This includes non-RISE members, OSS communities and projects, external tasks groups.

• 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.
• 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)

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.
• 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.
• 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.

Each WG generally commit ~2-4 hours per week, probably averaging to 2hr or less. The goal here is to provide an organizational backbone for the WG, not be a proxy for every activity, so the effort is not supposed to balloon with the amount of participants, projects, etc.

...