On 2 April 2018 at 19:40, Rick O'Connor <ric...@riscv.org> wrote:
> Yes - The process is detailed in the Bylaws and we’ll have it posted on the
> main site as well as the public Tech Committee page in workspace.
> We settled on the description text last week.
> Is there something specific you’re looking for Alex?
Thanks for the response Rick. In one of my previous emails I outlined
how I currently believe things work, based on statements made on this
list and the bylaws. I'd appreciate comments on that and
clarifications on the points labeled with a question mark - especially
the role of the technical committee:
>>>> The lifecycle as I understand it currently:
>>>> * RISC-V board establishes a taskgroup (or is it the technical
>>>> committee - if so, where do these discussions take place?)
>>>> * A taskgroup has a chair and vice-chair, and through a series of
>>>> meetings develops a proposed specification or specification
>>>> * Once the taskgroup is ready, it releases the specification for
>>>> public review for at least a 45 day period. This might be the first
>>>> time it is released publicly, but taskgroups could opt to release
>>>> earlier versions or public status updates.
>>>> * (?) After this review period, the committee will collate feedback
>>>> and submit to the technical committee for approval? Is there a TC
>>>> meeting? Or is this just a vote on Kavi? How long after the 45-day
>>>> review period does this take place?
>>>> * (?) Things then go up to the RISC-V board for final approval?
>>>> Again, how long is this expected to take?
>>>> I'd really appreciate any clarification here. It seems especially
>>>> important given that this is going to be the first time changes to
>>>> the specification are proposed and (hopefully) enacted through the
>>>> RISC-V Foundation.