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.

Check your spam folder if you don't see messages.

WG mailing lists are meant to help coordinate the WG's operation without polluting the main RISE TSC list. Usual topics are RISE project prioritization, RISE project scoping, tracking and long term planning. The lists are not meant specifically as an additional place for technical discussions, where these would duplicating existing resources available to upstream projects.

Participation should be limited to RISE members.

Work Group Meetings

Meetings and their cadence is at the discretion of each Work Group and its lead. Check the individual WG page for more info.

Also see TSC Meetings for some helpful info on getting access to recordings, resending invites, etc.

Work Group Leads

Leads are responsible for:

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

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.

Work Group Project Prioritization

Projects selected by Work Groups meet the following criteria:

1. In alignment with the upstream project roadmap, goal, etc.
2. Are either:
   1. Already contributed to by a RISE member and require additional resources (developers, reviewers, testers)
   2. Gaps that need a level of investment (e.g. into design/implementation), where a concrete focused effort by strongly-interacting (WG) participants would be more efficient than some eventual convergence by a group of weak-interacting (upstream project mailing list)
   3. Proof of Concepts (e.g. from RVI spec work) that need to be matured into upstream.
   4. Projects that are necessary to unblock RISE efforts in other area.

Algorithm of prioritizing projects is at the discretion of the WG, but all choices are reviewed and confirmed by the TSC, and subject to the Board's approval. Projects currently appear to be chosen by impact (which somewhat correlates to member interest in the project proposal).