Proposal Process (Standing Rules for OASIS ODF TC)

The TC's standing rule for proposals is included on the TC'S home page.

How to Make an ODF New Proposal (Non-normative instructions/best practices for using the JIRA)

  1. For any substantive additions, deletions or changes to the ODF specification (proposal) an JIRA issue must be created if it does not exist already.

  2. A TC member who wishes to work on a proposal assigns the JIRA issue to herself/himself, and sets the "fix for" field to the target for which the proposal is aimed to be ready. The status of the issue is set to "Open".
  3. The details of the proposal are added to the JIRA issue, or where more appropriate, into a document in the TC's document repository that is linked from the JIRA issue. The ProposalTemplate provides guidance regarding the necessary information.

  4. If a proposal has enough details to be integrated into the specification document (as defined by the TC's standing rule), the status of the issue is changed to "resolved" by the issue owner.

  5. TC members then should review the proposal. They may state their agreement or objection to a proposal using Apache voting rules. The issue owner may revise the proposal based on comments from TC members.

  6. If a week after the proposal has been revised the last time no objections are stated in an issue, the TC editor may and should integrate it into the next working draft. If after a week objections still exist, the issue owner should decide and note in the issue whether she or her wants to revise the proposal. If not, the issue owner should ask for a formal TC ballot to integrate the proposal.
  7. The TC editor changes the status of integrated issues to "Applied" and adapts the "Fix for" field to the draft version into which the issue actually has been integrated.
  8. TC members at any time may request the discussion of an issue in a TC meeting by adding the component "needs discussion" to the "component field". When adding a "needs discussion", a comment describing the details that shall be discussed should be added.
  9. The TC may approve the integration of an issue even in case objections are stated in the JIRA issue by a TC formal ballot.
  10. For all status changes, votes and when a "needs discussion" is added to an issue, the TC member that modifies the issue should check whether a notification has been send to the TC mailing list. If not, she or he shall notify the TC mailing list manually.

Note: The "Fix for" field indicates the intention of the issue owner to have the issue resolved for a particular CSD. It does not indicate that a particular issue must be resolved for a particular CSD. In particular, if an issue is not resolved at the time by when issues have to be resolved according the the TC's CSD schedule, the CSD schedule will not be adapted, but the "fix for" field will be set to the next planned CSD.

Note: The integration of a proposal into the working draft (regardless whether a ballot has been conducted for this) in no way anticipates or replaces the approval of a working draft as Committee Specification draft. Integrated proposals may be amended or changed by subsequent proposals.

How_to_propose_a_change_or_addition_to_ODF (last edited 2011-02-11 14:09:49 by michael.brauer)