As of right now, #ArchCom-RFCs are frequently be assigned to person writing the RFC. As we try out the Rust
model (per T123606), and as we try to increase the speed by which RFCs move though the process, we intend to assign RFCs to shepherds on the ArchCom.
T123606 describes the shepherd role:
** Makes sure that stakeholders are informed.
** Guides the discussion.
** Once the discussion plateaus or stalls & in coordination with the RFC
author(s), announces and widely publicizes a "Final Comment Period",
which is one week.
What this means from a practical perspective is that the shepherd is responsible for ensuring that an RFC is in the proper column on the #ArchCom workboard, and is responsible for nominating that RFC to be highlighted in an RFC meeting if/when the time is appropriate. Non-ArchCom members who file RFCs will have an assigned liaison who can keep them apprised of the status of their RFC.
See also my wikitech-l mail: "[Using assignees for RFC shepherd](http://thread.gmane.org/gmane.science.linguistics.wikipedia.technical/85616)"