ODF proposal standing rule

Dear TC members,

we currently have a standing rule which covers how we work on feature
proposals.

http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office

We approved this standing rule before we had JIRA, and it is tailored
to the Wiki based work flow we had in place before we had JIRA.

Since we agreed to use JIRA to work on feature proposal, it seems
appropriate to amend the standing rule. A proposal is below:

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 or by adding a comment to a JIRA issue. 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. The proposer must assign
the issue to herself/himself, and must set the "fix for" field to the
target for which the proposal is aimed to be ready. The proposal will
only be considered for that target if it contains enough information
for the TC editors to integrate it into the specifications, and if no
unresolved objections are raised in the JIRA issue.

3. For all proposals, a JIRA issue must exist. If such an issue is
not existing at the time a proposal is made, the proposer must create
an issue. The Proposer then must add the information requested
in the New Proposal Form on the ODF TC's wiki to the JIRA issue,
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, or add an appropriate comment to the JIRA issue. TC
members can raise objections to a proposal by a "-1" comment, or
agreement by a "+1" comment.

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 or within the JIRA issue, 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, or by adding an appropriate comment to the
JIRA issue. 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 completion of  a proposal has been announced, when the
proposal is detailed enough to be integrated into the specification,
and when no objections are raised in the issue within one week, the TC
editors may integrate the proposal. Already integrated proposals may be
revised or amended by subsequent proposals. No Proposal shall be voted
on unless it formally meets the definition of "contribution" as defined
by OASIS IPR Policy.

8. When objections are raised to a proposal, the
Proposer may 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. Simple Majority Vote shall determine whether a Proposal is
approved or not.

9. When notifications mentions in this standing rule are made using
JIRA, the TC member that notifies should ensure that JIRA sends a copy
of the notification to the TC mailing. In doubt, a notifications should
be made on the TC mailing list.

Best regards

Michael

-- 

Michael Brauer | Oracle Office Development

Phone: +49 40 23646 500 

Oracle Office Global Business Unit

ORACLE Deutschland B.V. & Co. KG | Nagelsweg 55 | 20097 Hamburg

ORACLE Deutschland B.V. & Co. KG

Hauptverwaltung: Riesstr. 25, D-80992 München

Registergericht: Amtsgericht München, HRA 95603

Komplementärin: ORACLE Deutschland Verwaltung B.V.

Rijnzathe 6, 3454PV De Meern, Niederlande

Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697

Geschäftsführer: Jürgen Kunz, Marcel van de Molen, Alexander van der Ven

Oracle is committed to developing practices and products that
help protect the environment