- Caucus FORUM pages
- Provide a FORUM for each of the state caucuses.
- Limit access to each state caucus forum to delegates from that state, and other selected delegates as appropriate.
- FORUM page will provide:
- A list of links to existing TOPICS pages including information on any MOTIONS pending for each TOPIC.
- Opening new TOPICS. If a NEW TOPIC is created, send email notification and invitation to comment, to every caucus member.
- TOPICS pages
- At the top of the page:
- Display a form for caucus members to SUBMIT MOTIONS for consideration by the caucus. Include fields for the title of the MOTION and the text of the MOTION.
- For any PENDING MOTION, display the title, text and current state of the MOTION
- If no one has moved to CLOSE DEBATE, display a link to the MOTIONS page.
- If someone has moved to CLOSE DEBATE, display a link to the VOTE page.
- Allow caucus member to post COMMENTS to a TOPIC. When a COMMENT is posted, send email notification to members who have previously commented on that topic
- At the top of the page:
- MOTIONS Page
- Display the title, text and current state of the MOTION.
- Provide the ability to manage MOTIONS.
- If no one has moved to CLOSE DEBATE
- Display form for delegates to post COMMENTS on the MOTION. If delegate SUBMITS a COMMENT, send email notification to all members of the caucus.
- If the delegate has not submitted a comment, display a button to CLOSE DEBATE
- If a delegate has clicked to CLOSE DEBATE, send email notification to every delegate giving them 72 hours to vote on CLOSURE.
- If no one has moved to CLOSE DEBATE
- Display all COMMENTS for the MOTION
- VOTE page.
- Display
- The title, text and current state of the MOTION.
- A digital CLOCK showing how much time remains for voting.
- If the delegate has not already voted, and:
- the vote is on CLOSURE, display "DO YOU FAVOR CLOSING DEBATE ON THIS MOTION?" and a form for voting YES or NO.
- the vote is on passage of the MOTION, display "DO YOU FAVOR PASSAGE OF THIS MOTION?" and a form for voting YES or NO.
- A list of all delegates who have voted, whether they voted YES or NO, with totals at the bottom.
- A list of all delegates who have commented of the MOTION, with their COMMENT.
- If, at the end of the time for voting,
- there are more YES than NO votes
- if the VOTE is on CLOSURE, debate is closed and the CLOSURE VOTE page is replaced by a PASSAGE VOTE page
- if the VOTE is on PASSAGE debate is closed and the MOTION is PASSED
- there are more NO than YES votes
- if the VOTE is on CLOSURE, debate is closed and page reverts to the PENDING MOTION page
- if the VOTE is on PASSAGE debate is closed and the MOTION is FAILS
- there are more YES than NO votes
- Display
If a vote for CLOSURE failed and the MOTION reverted to PENDING, the FORUM would remain closed and the only possibility would be to comment and vote on the MOTION again. So that debate could continue and so that a PENDING MOTION would not close the FORUM in one case but would in another, the outline does not indicate closing the FORUM when a motion is initially submitted.
Reverting a MOTION to a PENDING MOTION on a failed CLOSURE MOTION indicates that the original MOTION should remain for consideration, but I was not sure if more than one PENDING MOTION was permissible. The logic of this outline permits multiple PENDING MOTIONS.
Observed Differences in State Caucus Designs:
ReplyDeleteThe aim here is to outline observed differences between the State Caucus design described by Judge Brennan on February 19th and this outline intended to express these designs created by Delegate Tape.
State Caucuses
State Caucuses, Continued
If Judge Brennan accepts this as an acceptable interpretation of his vision, I will close the posts started by him, and redirect this topic to this thread.
I will be expressing my personal opinions in a separate comment.
Construct Hierarchy:
The Brennan hierarchy implies a STATE CAUCUS construct, and has FORUM and MOTION constructs directly subsidiary to the STATE CAUCUS construct. A TOPIC construct is defined subsidiary to the FORUM construct.
The Tape hierarchy unifies the STATE CAUCUS and FORUM construct, and makes the MOTION construct subsidiary to the TOPIC construct.
FORUM and TOPIC Constructs:
The FORUM and TOPIC constructs of the two proposals are identical when available. The Brennan design closes these constructs when any MOTION is open, while the Tape design keeps these constructs available regardless of the state of any MOTION construct.
MOTION Construct
The processes for closing debate and voting differ only in the organization of the presentation, using a 72 hour voting period and a majority to close debate on a motion.
Conclusion
The only significant difference is that the Tape design allows for discussion of multiple MOTIONS at any given time, while the Brennan design allows an open MOTION to prempt all other Caucus business.
The outline by Delegate Tape allows for the consideration of multiple topics in parallel, which I support. I do think that only one motion per topic should be allowed at any given time.
ReplyDeleteI reiterate my primary concerns regarding this outline, as I presented them in the original post by Judge Brennan.
The most significant issues I have with this proposal is the lack of a need for a second, and the lack of an ability for the State Caucus Captain, or other officer created by the State Caucus to serve in their absence, to rule a motion out of order.
This should be a question for the Rules Committee to decide, ideally after an Advisory Committee of the Whole is formed to discusses the idea at the existing Delegate Forum, to form a basis for the Rules Committee to gauge the various views of the Delegates.
I note that, for the short term, these processes can be managed manually by the administrators of the Forum, which is presently under construction. The guidelines on the test state caucus are intended to allow for a manually managed protocol that addresses the concerns I outline.
http://forum.conventionusa.org/forumdisplay.php?fid=22
This is designed to empower state caucus captains to manage their own state caucus forum, while making the internet committee available where states caucus captains are unable to regularly manage the caucus.
As I understand, the question of state caucus business and deliberation is fully at the discretion of the caucus. Why would the Rules Committee be involved?
DeleteRegarding a Captain delegating authority, I agree.
Regarding the seconding of motions, I would suggest that this be an option determined by the caucus and configurable by the caucus Captain.
The state caucuses should be able to override any default parameters that are established.
DeleteIs it more proper for the Internet Committee or Rules Committee to establish the default rules for the State Caucuses? In the absence of such guidance, however, the Internet Committee should be expected to establish guidelines typical of existing well managed forums.
I would certainly entertain discussion on whether the default behavior should be related to Caucus size. I would offer ten delegates as the threshold where a second is required to open a motion.
If we decide to allow multiple motions to be open at once, I would also suggest that multiple seconds may be appropriate if a caucus grows to where more than three motions are regularly open at once.