Contributions to our twice-monthly tech newsletter are strongly encouraged by chairs and vice-chairs of HCs, ICs, TGs, SIGs, and RISC-V staff.
To submit a new entry for the newsletter, ensure you are part of the "riscv-members" at GitHub. You can easily verify if you are part of that by clicking here (select GitHub, type your GitHub user and press Search).
Considering our diverse audience, which includes both technical and non-technical individuals, all content should be concisely explained and, if appropriate, include a reference to where more information can be found. This ensures that the newsletter remains both accessible and valuable to all.
In other words, submissions should be crafted in a clear and concise manner, including links to external sources for additional context or in-depth understanding. A 300-character limit is recommended and might look like this:
Example Submissions for All
For the transactional security extension, two alternative proposals were introduced, one of which is closer to existing industry architectures while the other has a more novel architecture but might offer better future scalability. See lively discussion of the pros and cons of the two alternatives on the email thread here: …
Agreement was reached on the final set of extensions to include in the matrix crypto extension ratification package. See updated spec at Git Hub:...
The rotate-up instruction was removed from the draft nibble-manipulation extension as it was found to almost entirely duplicate existing functionality, and the few cases that were novel were not deemed important enough to justify inclusion. Thread at:...
A backward-incompatible change to machine-mode register misa was proposed for priv 1.23. The change is considered unlikely to affect implementations or software but discussion is continuing at: thread…
Example Submissions for Specification Owners
Please note that the RISC-V Staff will be ensuring that following events are submitted and included, space permitting:
Submit your entries during the open-submission phase in the first week of each bi-weekly cycle. Ensure your contributions align with the twice-monthly publication schedule of the newsletter.
Topics can vary widely, from key and/or contentious technical discussions and conclusions, to major specification releases, hot topics, notable updates, notable upcoming discussion topics, and AR reviews. These serve to keep our community updated on a range of relevant issues. These should not include mundane status updates or minutia.
The technical topics will be grouped by the relevant HC/IC committee to help readers find relevant material.
The entries will be moderated by the appropriate HC/IC committee chairs and RISC-V staff.