Subject: Ballot on Feature Approval Procedure, XLIFF 2.0 program Charter Draft v0.4 committed to SVN
Features not listed here:
will not be considered at all for inclusion in any XLIFF 2.x spec.
The feature tracking wiki comprises three sections. 1. Approved, 2. Under Consideration, 3. Discarded.
Section 2. Features under consideration is the default section: http://wiki.oasis-open.org/xliff/XLIFF2.0/FeatureTracking#Featuresunderconsideration.28notyetevaluatedbyTC.29
Any TC member can record a feature in Section 2., preferably following an e-mail or meeting discussion.
Features can be moved into section 1. or 3. only following a formal TC ballot.
Features can be proposed for ballot in a regular TC meeting by the listed Owner (Champion) or the TC Chair.
Owners must demonstrate to the TC not only the technical appropriateness of the feature but also explain what resources and timeframe is needed for elaboration and if those resources are available.
TC Chair can suggest moving a feature from Section 1. to section 2. Or even 3. if it does not show reasonable progress close to XLIFF 2.x spec release deadline.
Only the Owner can suggest reconsideration of an item in section 3.
[Alternative additional conditions for reconsideration of items in section 3:]
1. Not sooner than 4 months after the item was placed in Section 3.
2. Majority of *all* voting members needed (via kavi to all eligible, or also possible if the meeting majority is at the same time the majority of all current voting members).
3. No additional conditions.
Only features in the Section 1. Approved Features can be proposed for XLIFF 2.x Core.
This is recorded as “Core Status: [YES/NO/TBD]”
[This needs to be implemented into wiki template – if approved]
Otherwise the procedure is the same as feature approval.
A feature moving away from Section 1. gets its core status set to “NO”
“TBD” is being used as initial value only, all subsequent changes are between “YES” and “NO” only.