OASIS XML Localisation Interchange File Format (XLIFF) TC

Re: [xliff] Draft Proposal Process for New TC Business

  • 1.  Re: [xliff] Draft Proposal Process for New TC Business

    Posted 03-15-2004 18:57
     MHonArc v2.5.0b2 -->
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    

    xliff message

    [Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


    Subject: Re: [xliff] Draft Proposal Process for New TC Business


    Very small correction (dates in example didn't match).

    We'll conduct a vote on this process at tomorrow's meeting.

    Regards,
    Tony

    Tony Jewtushenko wrote:
    All:

    Below is a Draft of the formal Proposal Process for New TC Business - I'd like to discuss this at tomorrow's TC teleconference.

    Regards,
    Tony

    Formal XLIFF Proposal Process:
    1. Submittor authors Proposal using the official XLIFF TC Proposal Form.
    2. TC member Submittor sends the Proposal to the TC using the xliff@lists.oasis-open.org
    3. Non-TC member Submittor sends the Proposal to the TC using the xliff-comment@lists.oasis-open.org
    4. "Proposal Review" action item will be added to the agenda of the next TC teleconference,  provided Proposal made 7 days in advance of the meeting date.  Any Proposal made within 7 or fewer days of XLIFF teleconference will be added to the following teleconference
    5. Review of the Proposal at TC teleconference will conssit of the following:
    • A unique Proposal ID will be assigned by TC based on the date the Proposal is first recieved by the TC ( the email timestamp in the )
      • The Proposal ID will take the form: "yymmdd".  Example "040214" indidates a Proposal was first made on 14 Feb 2004.
      • If more than one Proposal is recieved on the same date,  a suffix of "a" through "z" shall be applied to identify the Proposal.   The suffix shall be assigned based upon the order othat the Proposal arppears in the mailing list.   Example:  "040214a" and"040214b" represent two Proposals made on 14 Feb 2004.
    • The new Proposal will be added to an online report containing URL's to all Proposals recieved by TC.
    • Proposal will be reviewed by the TC,  and a "Next Step" shall be agreed to by usual TC consensus process:
    • The Next Step will be prose decribing in detail what if any ther next steps must be.
    • The Proposal will be assigned a "Status"
      • Approved:  Proposal was approved by TC.
      • Approved for <release/>:  Proposal was approved by TC for specific release number.
      • Need More Information:  Unable to make decision until reply to questions received from Submittor
      • Rejected:  No further consideration of Proposal.  A justificaiton will be provided.
      • To Subcommittee: Establish Subcommittee to return with analysis and/or recommendation.
      • Review in Progress: No determination on Proposal - review in progress
      • Deferred:  No action - defer decision to future unspecified date.
      • Deferred until <date/> - deferred until future specified date.
      • Deferred until <release/> - deferred until future release
      • Implemented: Approved Proposal was implemented by TC.
    1. At each TC teleconference,  agenda items shall be added for reviewing new,  and in progress Prposals.


    -- 
    Tony Jewtushenko		mailto:tony.jewtushenko@oracle.com
    Principal Product Manager	direct tel: +353.1.8039080
    Oracle Corporation, Ireland

    -- 
    Tony Jewtushenko		mailto:tony.jewtushenko@oracle.com
    Principal Product Manager	direct tel: +353.1.8039080
    Oracle Corporation, Ireland


    [Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]