We need to clean up and reboot the workgroups. Since subworkgroups were an informal concept that is not reflected in our bylaws/charter, let's skip them (SystemVerilog, RISC-V DV) for now so that they don't clutter up the WG list page. We could reboot them as e.g. SIGs. The meetings of the Subgroups could be listed in the metadata of their parent group.
We should also remove groups that are currently not meeting (Cores, Interconnects) to also reflect the state of affairs better, as well as describe new ones, such as Caliptra.
This data should be presented in the form of MD files with YAML frontmatter. The YAML will be used to render "standard" stuff like WG name, leader, mailing list or meetings (probably should be a list in case a WG has more meetings re: different matters) - and the MD will contain a broader WG description to be pasted as-is. Of course this is just my idea, I welcome criticism especially if trying to implement things this way results in something that's bonkers.
So we need to have:
Chisel
F4PGA
Tools
Caliptra
Analog
Rocket (does this operately from Chisel? need to figure out)
mgielda
commented
1 year ago
We need to clean up and reboot the workgroups. Since subworkgroups were an informal concept that is not reflected in our bylaws/charter, let's skip them (SystemVerilog, RISC-V DV) for now so that they don't clutter up the WG list page. We could reboot them as e.g. SIGs. The meetings of the Subgroups could be listed in the metadata of their parent group.
We should also remove groups that are currently not meeting (Cores, Interconnects) to also reflect the state of affairs better, as well as describe new ones, such as Caliptra.
This data should be presented in the form of MD files with YAML frontmatter. The YAML will be used to render "standard" stuff like WG name, leader, mailing list or meetings (probably should be a list in case a WG has more meetings re: different matters) - and the MD will contain a broader WG description to be pasted as-is. Of course this is just my idea, I welcome criticism especially if trying to implement things this way results in something that's bonkers.
So we need to have: