Revised Proposed standing rules for creating New Proposals

[robert_weir@us.ibm.com]

Item #4 on Monday's TC meeting agenda (http://lists.oasis-open.org/archives/office/200807/msg00174.html)
calls for a vote on the approval of a new standing rule for the ODF TC.
 The agenda points to the text on the wiki here:  http://wiki.oasis-open.org/office/How_to_propose_a_change_or_addition_to_ODF

Since that was sent out, I received feedback and suggestions
on the that text in several areas:

1) Recommendation to state what occurs if a TC member
requests a discussion or vote on an item, but the agenda cannot accommodate
that request for lack for time.

2) Recommendation to make it clear that this rule
is only for substantive changes.  Editorial changes are not required
to use this process.

3) Consistent use of gender inclusive "his or
her" rather than "his".

4) General suggestions on how to tighten the language

The net result in the revised text which I am attaching.
 On Monday I will move that we replace the existing proposed text
with this revised text.  If the TC agrees to make this substitution,
then we can vote on whether to accept the revised text as a standing rule.

Regards,

-Rob

------------------------------------------------------------------

1. Any TC member may propose a substantive addition,
deletion or change to the current working draft of the ODF specification
by submitting a Proposal.  This standing rule does not apply to editorial
changes.

2. A TC member wishing to make a Proposal (the Proposer) should first announce
their intention to make a Proposal on the ODF TC's mailing list. Detail
is not needed at this point, but such notification is recommended in order
to let other interested TC members know that someone is working in this
area and to prevent duplication of effort.

3. The Proposer then must fill out the New Proposal
Form on the ODF TC's wiki, with details of the Proposal.

4. When the Proposal is ready for broader discussion within the TC, the
Proposer must post a link to it to the TC's mailing list to solicit feedback.

5. The Proposer controls the content of the Proposal and the pace at which
the Proposal advances towards approval. As it is discussed on the mailing
list, TC members may propose changes to the Proposal. However, only the
Proposer, and those whom he or she designates, may edit the proposal.

6. When the Proposer wishes for the Proposal to be discussed in a TC meeting,
he or she must notify the TC mailing list of this intent by the Wednesday
prior to the Monday TC meeting in which he or she wishes to discuss the
Proposal. If the agenda cannot accommodate this discussion during the next
TC meeting, the Chair(s) should ensure that the discussion is scheduled
for the next available TC meeting, with no new notification by the Proposer
needed. A Proposal may be discussed in multiple TC meetings.

7. When the Proposer wishes to request a vote to accept his or her Proposal,
he or she must notify the TC mailing list of this intent by the Wednesday
prior to the Monday TC meeting in which he or she wishes to have the vote.
 If the agenda cannot accommodate this vote during the next TC meeting,
the Chair(s) should ensure that the vote is scheduled for the next available
TC meeting, with no new notification by the Proposer needed. No Proposal
shall be voted on unless it formally meets the definition of "contribution"
as defined by OASIS IPR Policy. No Proposal shall be voted on unless it
has already been discussed in a previous TC meeting. Simple Majority Vote
shall determine whether a Proposal is approved or not.

8. The TC Chairs shall be responsible for maintaining a record in the Proposal
form, of when the proposal was initiated, at which TC meetings it was discussed,
when a vote was requested, when the vote was held, and the outcome of the
vote.