|Asciidoc||Website||Information about using Asciidocemail@example.com|
|Benchmark Links||Links||Links to existing benchmark firstname.lastname@example.org|
|Chairs Contact List||Document||List of all working groups, chairs/co-chairs, and email@example.com|
|Chair's Meeting Recordings||Document||These recordings are only available to those members of the tech-chairs firstname.lastname@example.org|
|Code of Conduct||Document||RISC-V Code of Conduct - please read email@example.com|
|Email groups - members||Portal||Member portal - working groups email server, hosted via Groups.firstname.lastname@example.org|
|Email groups - public||Portal||Public mailing lists (hosted on google groups) including ISA-DEV and SW-DEV, and other email@example.com|
|Extension Development Lifecycle||Document||Diagram of the lifecycle of milestones when developing a new firstname.lastname@example.org|
|Gaps||Document||Document identifying specification email@example.com|
|Document||How to work with the RISC-V technical firstname.lastname@example.org|
|GitHub||Link||A link to our GitHub email@example.com|
|Glossary||Document||Glossary of firstname.lastname@example.org|
|Information directory||Folder||has prior art, glossary, links, content, email@example.com|
|Information links||Document||docs, repos, videos, firstname.lastname@example.org|
|ISA specifications github||Links||get to ISA github repo directly|
|ISV list||Resources||List of ISVs within the RISC-V email@example.com|
|Opcode and Consistency Review Dashboard||Admin||Review of all proposals - must be completed prior to Freeze. Includes: a review of the specification for clarity and completeness, consistency with the RISC-V ISA and philosophy. Allocates opcodes and state (e.g., CSRs).||firstname.lastname@example.org|
|Other organizations||Links||other organizations that do work related to RISC-V or ecosystem technology that enables RISC-V members to develop and deploy email@example.com|
|Policies||Folder||Folder containing all working policies - approved, in process, and firstname.lastname@example.org|
|Prior Art Links||Links||Links to prior email@example.com|
|Shared Drive||Folder||Shared storage for the entire technical firstname.lastname@example.org|
|Slack space||Admin||Live messaging for the community - if you are new, add yourself with this email@example.com|
|Specifications||Links||Official links to approved firstname.lastname@example.org|
|Specification status||Document||All working specs and their email@example.com|
|Task and Interest Groups Github Links||Links||List of links to working group github repos (deprecated)||firstname.lastname@example.org|
|Tech Groups Calendar||Admin||hit + button on the bottom right to add to your google calendar. -- IF YOU NEED TO ADD EVENTS Contact email@example.com --||firstname.lastname@example.org|
|Tech Leader Calendar||Admin||hit + button on the bottom email@example.com|
|Tech Organizational Charts||Adminfirstname.lastname@example.org|
|TSC and Chairs minutes and status||Folder||Folder with minutes and status decks for TSC and email@example.com|
|Zoom Links||Admin||Links to zoom meetings (scroll to the right)||firstname.lastname@example.org|
This is guidance for tech chairs regarding Zoom and calendar entries.
ALL meetings should have someone with host privileges in control, and should be set to
When you use a RISC-V zoom account, the account will be zoom+xyz@riscv where xyz is one of the licenses we have allocated. You do NOT need to log in as this user. Instead, join the meeting, then click the Participants panel and in the lower right you should see [...]. Click this and choose CLAIM HOST. Enter the host code to become the host so you can moderate the meeting. Check your email from October 20, 2020 for the host code.
Due to a host of issues reported with the calendar system on the member portal (lists.riscv.org), we are working on migrating all calendar entries to the Tech Groups Google Calendar. If your group hasn't migrated yet, please add it to the calendar and then remove it from your group on the member portal. You can also send mail to email@example.com so Stephano or I can help you do it.
If someone in your group is unable to subscribe to this calendar for some reason, you can add them to the calendar entry directly. Each chair has write permission on that calendar. Just be aware that each invitation has a 200-person limit on direct invitees.
If you lose the link to the calendar, go to the wiki at https://wiki.riscv.org/display/TECH and look for the link to Tech Groups Calendar.
We have some new information that Outlook may not import the ICS link for this calendar properly - for some people it is being imported as a copy, rather than "subscribed". Microsoft provides some guidance on subscribing to ICS links using Outlook but if you still encounter this problem, let us know - at worst case, we may need to start maintaining multiple calendar entries.
Please also note that subscriptions to ICS links often take up to 24 hours to update, so do not count on them to propagate if you have a meeting change within 2 days of your meeting. Make the change on the invite, but be sure to send email to your group advising them of the change so no one gets lost. Unfortunately this is a limitation of the calendaring system, and it is not a bug we can fix.