Angyl
unread,Feb 13, 2019, 3:31:37 AM2/13/19Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Scott Alspach, Brad Bell, Annabelle Backman, Tara Gallagher, 43rd District Democrats Rules and Bylaws Committee
I haven’t double checked the current bylaws draft on this but I would think it should work much the same way. The order of operations that seems to make the most sense is :
- Somebody recruits
- forms submitted
- PCO committee does verification work and any vetting
- PCO committee recommends to membership one or more candidates for appointed via agenda
- epic rap battle if contested, membership votes or approves.
- LD Chair signs or rejects, if reject GOTO reject process
- if signed, papers to County
- County Chair signs, rejects, or times out, goto reject process.
- if CC approves, PCO or PCO committee may get the ack early, maybe they built a response channel or check the county page regularly, and whenever they do that person gets added to credentialed PCO voters in db. An optimal PCO committee would arguably be in contact with recruits throughout the process, but should hold explicit responsibility for tracking County signings at lest monthly to keep PCO credentials accurate and letting the PCOs know when their process is complete and getting their VB access up, or updating them if it moves to the neoActing approval process.
- In order to avoid a dead stop there, maybe there should be a more grassroots process for not-Acting-anymore, like nominating from the floor or something, so if somebody 45 day times out and there’s a total black hole they can still go straight to the body for approval of their desire for a PC role? Since it’s built as the body granting role and rights, that seems appropriate.
- Angyl
Sent from ProtonMail Mobile
To view this discussion on the web visit https://groups.google.com/d/msgid/43rd-bylaws/CA%2B7_OaidjcaofZeftyTG6UG2rnFawRfW15kZHgWiMBz%2BBH7ccQ%40mail.gmail.com.