|Asciidoctor APIs||documentation||Website||APIs for automating aspects of the doc email@example.com|
|Asciidoc Writers' Guide||documentation||Website||Introduction to Asciidocfirstname.lastname@example.org|
|Benchmark Links||links||Links||Links to existing benchmark email@example.com|
|Calendars for tech group meetings (ics file)||calendar||Admin||hit + button on the bottom right to add to your google calendar. -- IF YOU NEED TO ADD EVENTS Contact firstname.lastname@example.org --||email@example.com|
|Chairs Contact List||contacts||Document||List of all working groups, chairs/co-chairs, and firstname.lastname@example.org|
|Chair's Meeting Recordings||meetings||Document||These recordings are only available to those members of the tech-chairs email@example.com|
|Code of Conduct||etiquette||Document||RISC-V Code of Conduct - please read firstname.lastname@example.org|
|Content Requests||requests||Link||Send email to RISC-V Content team for web content, collaborative PR, blog posts, email@example.com|
|Email groups - members||subscribe||Portal||Member portal - working groups email server, hosted via Groups.firstname.lastname@example.org|
|Email groups - public||subscribe||Portal||Public mailing lists (hosted on google groups) including ISA-DEV and SW-DEV, and other email@example.com|
|Extension Development Lifecycle||extensions||Document||Diagram of the lifecycle of milestones when developing a new firstname.lastname@example.org|
|intro||Document||How to work with the RISC-V technical email@example.com|
|GitHub||repo||Link||A link to our GitHub organization. which will hve links to the other groups of firstname.lastname@example.org|
|Github: groups and committees||repo||Link||charters, agendas, minutes, etc. that are independent of a specification (remember a group may be working on more than one spec)||email@example.com|
|Github: ISA specifications (link tbd)||repo||Link||ISA specifications, issues, email, etc. (something that creates new instructions and/or state)||firstname.lastname@example.org|
|Github: non-ISA specifications (link tbd)||repo||Link||non-ISA specifications, issues, email, etc. (things like ABIs or guides)||email@example.com|
|Github: upstream software (link tbd)||repo||Link||temp location to stage upstream software. eventually goes away when firstname.lastname@example.org|
|Github: RISC-V software (link tbd)||repo||Link||Software developed specifically for RISC-V and not an upstream email@example.com|
|Github: other (link tbd)||repo||Link||random other documents that need github but don't belong in the other firstname.lastname@example.org|
|Glossary||documentation||Document||Glossary of email@example.com|
|Information directory||repo||Folder||has prior art, glossary, links, content, firstname.lastname@example.org|
|Information links||URLs||Document||docs, repos, videos, email@example.com|
|ISV list||ISVs||Resources||List of ISVs within the RISC-V firstname.lastname@example.org|
|Jira||bug reporting||Admin||Issue tracking for RISC-V International issues - use Github Issues for extension-specific email@example.com|
|Opcode and Consistency Review Dashboard||oversight||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|
|Organizational Charts for technical groups||organization||Adminemail@example.com|
|Other organizations||links||Links||other organizations that do work related to RISC-V or ecosystem technology that enables RISC-V members to develop and deploy firstname.lastname@example.org|
|Policies||policies||Folder||Folder containing all working policies - approved, in process, and email@example.com|
|Prior Art Links||legal||Links||Links to prior firstname.lastname@example.org|
|Shared Drive||repo||Folder||Shared storage for the entire technical email@example.com|
|Slack space||messaging||Admin||Live messaging for the community - if you are new, add yourself with this firstname.lastname@example.org|
|Specifications||extensions||Links||Official links to approved email@example.com|
|Specification status||status||Document||All working specs and their firstname.lastname@example.org|
|TSC and Chairs minutes and status||status||Folder||Folder with minutes and status decks for TSC and email@example.com|
|Zoom Links||video conferencing||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.