[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [tag] I need the TC to remediate some problems with the CSD and CND requests
Hi Jacques, I see that the current ballot will close on Thursday. As you then have to ask me to hold another ballot to actually get the TC's approval, I can understand that you don't want to restart a whole new one. Let me follow on to your suggestion and recommend it this way: 1. As you suggest, open a new ballot asking 'Does the TC approve withdrawing Test Assertions Guidelines Version 1.0, CSPRD 03 (http://docs.oasis-open.org/tag/guidelines/v1.0/csprd03/testassertionsguidelines-csprd03.html ) from consideration as a CSD?" and put in the additional info that it is currently one of 3 CSDs being balloted in http://www.oasis-open.org/apps/org/workgroup/tag/ballot.php?id=2141. This accomplishes a clear followup record to the first ballot. 2. Before doing anything on on Test Assertions Guidelines, please request a CND template for it from http://www.oasis-open.org/resources/tc-admin-requests/work-product-registration-template-request (CND templates differ from CSD templates and Paul will turn it around for you asap). Cut & paste the guidelines content into that template to create a committee note working draft. 3. By meeting vote or ballot, approve that working draft for CND and for PR. Then enter the support ticket. 4. I will use Approved Work Products in Kavi to launch the public review meaning we will get the PR started within 3 days of your upload. It is a CND so it will be a 15 day public review. This keeps everything clean in terms of the various steps. TCA will handle the cover pages and such & all you will need to do is prep the working draft. This work ok for you? Thx - /chet On Fri, Nov 11, 2011 at 4:16 PM, Jacques Durand <JDurand@us.fujitsu.com> wrote: > So Dennis/Chet let me get that straight: > 1. CS specs: we do have currently a ballot open to approve both CSPRD specs (TA model, TA markup) for initiating a CS vote on them. We can keep this going (the ballot is also for submitting the TA Guidelines to CS vote, but we can cancel this by consulting the TC again at the end of this ballot). > 2. CN specs: we reposition TA Guidelines as a CND, as this was initially the intent (and is better in the long run to avoid confusion on what is normative, what not). That means we (TC admin?) change the front page, and initiate an e-ballot as follows: > "Do you approve canceling the submission to CS vote of third CSPRD work product (Test Assertions Guidelines Version 1.0 [URL]) mentioned in previous ballot (http://www.oasis-open.org/apps/org/workgroup/tag/ballot.php?id=2141) , and approving this work product as a CND, then as a PR candidate?" > If I don't hear otherwise, that is what I will initiate this Monday... > Thanks, > Jacques > > -----Original Message----- > From: tag@lists.oasis-open.org [mailto:tag@lists.oasis-open.org] On Behalf Of Dennis E. Hamilton > Sent: Friday, November 11, 2011 9:19 AM > To: 'Chet Ensign' > Cc: tag@lists.oasis-open.org; 'TCA'; 'Robin Cover'; 'Paul Knight'; 'Anne Hendry'; 'Greg Carpenter' > Subject: RE: [tag] I need the TC to remediate some problems with the CSD and CND requests > > Chet, That sounds like a great way to expedite this. > > The TAG TC will have to huddle to see whether we need to cancel and restart a current e-ballot and line up with your proposal. > > Then we could realign the Guidelines document as a CND (using the correct draft), and run the short PR on it. That should be no problem because more time is needed to take the two CS to COS anyhow. > > - Dennis > > -----Original Message----- > From: tag@lists.oasis-open.org [mailto:tag@lists.oasis-open.org] On Behalf Of Chet Ensign > Sent: Friday, November 11, 2011 06:53 > To: dennis.hamilton@acm.org > Cc: tag@lists.oasis-open.org; TCA; Robin Cover; Paul Knight; Anne Hendry; Greg Carpenter > Subject: Re: [tag] I need the TC to remediate some problems with the CSD and CND requests > > Dennis & members of the TAG TC, > > Apologies for the confusion. Here is the background on the situation > and a suggestion for going forward. > > Dennis, you are correct in nothing problems with the submissions. All > 3 documents were originally started as Committee Specifications. > During one of the rounds of preparation for public review, the motion > changed Test Assertions Guidelines from Committee Specification Draft > to Committee Note Draft. This posed a problem because the TC Process > does not allow for documents to change shape in mid-stream. It should > have been restarted as a Committee Note Draft. > > Because of the long delays with TC Admin requests at the time, I > simply moved all three forward to public review as Committee > Specifications. I dropped the ball on getting with Jacques to discuss > how to restart Guidelines as a Committee Note Draft. > > I suggest the best way to move forward is to: > > - Modify the ballot motion to approve the two Committee Spec Drafts as > Committee Specifications. > - Hold a different ballot (either electronic or as a motion in a > meeting) to approve Guidelines as a Committee Note Draft and to submit > it for 15-day public review. > > I will get the public review launched as soon as I have a request. > After the public review, assuming no comments that require changes, > the TC can move to approve Guidelines as a Committee Note and we'll > publish that way. > > My apologies for not getting this sorted out sooner and causing you > all delay. Please let me know if you want to discuss this further. > > /chet > > On Thu, Nov 10, 2011 at 8:23 PM, Dennis E. Hamilton > <dennis.hamilton@acm.org> wrote: >> I was rummaging through my mail folders to see if I zoned out on the change of Test Guidelines back to a CSD from a CND. >> >> I found this about how specific our motions must be and I realize that our last motion, to forward documents for balloting as 2x CS and 1x CN is also defective in the manner pointed out here. Our ballot motions do not include specific links to the authoritative (editable) versions that are to be carried forward. >> >> I confess that I did not give this enough attention to make sure the requisite vote statement was embedded in my DNA as TC Secretary. For that, I apologize. >> >> - Dennis >> >> -----Original Message----- >> From: Chet Ensign [mailto:chet.ensign@oasis-open.org] >> Sent: Sunday, July 24, 2011 15:12 >> To: Jacques Durand; tag@lists.oasis-open.org >> Cc: Robin Cover; Paul Knight; Scott McGrath >> Subject: [tag] I need the TC to remediate some problems with the CSD and CND requests >> >> Jacques & members of the Test Assertions Guidelines TC, >> >> We started work on TCADMIN-541, 542 and 543 and encountered problems >> with each submission that require me to ask for clarifying action from >> the TC before we proceed. I have listed the problems with each of the >> tickets below, why we have to ask for remedial action and described >> the actions I'm asking the TC to take to clear them up. I'm sorry that >> this adds further delays onto your committee drafts and public reviews >> but the TC Process rules are clear and we must follow them. >> >> >> - TCADMIN-541, CSD Creation / Upload Request for Test Assertions Model >> Version 1.0 (http://tools.oasis-open.org/issues/browse/TCADMIN-541) >> >> - The approval motions referenced in the meeting minutes provided do >> not contain the link to the Working Draft to be approved by the TC and >> the ballot referenced describes a PDF document, not editable source. >> In addition, the minutes are from May 24th, but the document URL in >> the ticket is to a file loaded on June 9th. >> >> The rules require that the motion to approve the CSD include the URL >> to the working draft being approved by the TC and the working draft >> must include editable source. The purpose of the rule is to ensure >> that the CSDs/CNDs created by TC Admin and loaded to the OASIS Library >> are created from the exact WD approved by the TC. Because we cannot >> make the connection between what was approved and what was submitted >> to us, we cannot proceed. >> >> - To remedy this, I ask that you hold another vote to approve the work >> product package that the TC wants promoted to CSD. Either a voice vote >> recorded in your meeting minutes or an electronic ballot will be fine. >> Motion language such as: >> >> Motion: That the OASIS Test Assertions Guidelines TC approve Test >> Assertions Model Version 1.0, Working Draft 04 (URI >> http://www.oasis-open.org/apps/org/workgroup/tag/document.php?document_id=42481) >> as Committee Specification Draft 04 and submit same to TC >> Administrator for use in ticket TCADMIN-541 >> (http://tools.oasis-open.org/issues/browse/TCADMIN-541)." >> >> will satisfy the requirement. (Obviously substitute whatever Working >> Draft URL links to the version that you want to approve.) When you >> have made and documented the vote, you can update the ticket directly >> with the link to the approving minutes and the link to the Working >> Draft or you can send them to me and I will update the ticket, >> whichever is more convenient. >> >> >> - TCADMIN-542, CND Creation / Upload Request for Test Assertions >> Guidelines Version 1.0 >> (http://tools.oasis-open.org/issues/browse/TCADMIN-542) >> >> - The approval motion in the meeting minutes does not include a URL to >> the Working Draft to be approved by the TC. The minutes simply say >> "2.2 TA GUIDELINES … Paul moved, Kevin seconded that the June 3 >> working draft be approved as CND03. The motion was approved by >> unanimous consent." In addition, the minutes are from June 7 but the >> document URL in the ticket is to a file loaded on June 14th. >> >> As above, we are unable to make the connection between the description >> in the meeting minutes and the document linked in the ticket >> >> - To remedy this, I ask that you hold another vote to approve the work >> product package that the TC wants promoted to CND. Either a voice vote >> recorded in your meeting minutes or an electronic ballot will be fine. >> Motion language such as: >> >> Motion: That the OASIS Test Assertions Guidelines TC approve Test >> Assertions Guidelines Version 1.0, Working Draft 03 (URI >> http://www.oasis-open.org/apps/org/workgroup/tag/document.php?document_id=42529) >> as Committee Note Draft 03 and submit same to TC Administrator for >> use in ticket TCADMIN-542 >> (http://tools.oasis-open.org/issues/browse/TCADMIN-542)." >> >> will satisfy the requirement. Again, you can update the ticket with >> the links to minutes and document or you can send to me. >> >> >> - TCADMIN-543, CSD Creation / Upload Request for Test Assertion Markup >> Language Version 1.0 >> >> - The approval motion in the meeting minutes does not include a URL to >> the Working Draft to be approved by the TC. The minutes simply say >> "2.1 TAML … Paul moved, Kevin seconded that the June 2 working draft, >> with the agreed change, be approved as CSD05. The motion was approved >> by unanimous consent." The minutes themselves are dated June 7 but the >> URL provided was loaded to Kavi on June 14 and there appear to be >> differences between the files dated June 2nd and the file in the >> provided URL. >> >> As above, we are unable to make the connection between the description >> in the meeting minutes and the document linked in the ticket. Also, we >> cannot accept motions to approve working drafts contingent on someone >> making changes after the approval. The motions must approve a complete >> and completed working draft. >> >> - To remedy this, I ask that you hold another vote to approve the work >> product package that the TC wants promoted to CSD. Either a voice vote >> recorded in your meeting minutes or an electronic ballot will be fine. >> Motion language such as: >> >> Motion: That the OASIS Test Assertions Guidelines TC approve Test >> Assertions Markup Language Version 1.0, Working Draft 05 (URI >> http://www.oasis-open.org/apps/org/workgroup/tag/document.php?document_id=42522 >> ) as Committee Note Draft 03 and submit same to TC Administrator for >> use in ticket TCADMIN-543 >> (http://tools.oasis-open.org/issues/browse/TCADMIN-543)." >> >> will satisfy the requirement. Again, you can update the ticket with >> the links to minutes and document or you can send to me. >> >> Again, I regret that this is further delaying work on your requests. >> We will hold the tickets in their current position in the queue and >> resume work on them as soon as you provide us with the TC approvals >> and URL's as described above. >> >> Please let me know if you have any questions or if I can be of help in >> expediting the resolution. >> >> -- >> >> /chet >> ---------------- >> Chet Ensign >> Director of Standards Development and TC Administration >> OASIS: Advancing open standards for the information society >> http://www.oasis-open.org >> >> Primary: +1 973-378-3472 >> Mobile: +1 201-341-1393 >> >> Follow OASIS on: >> LinkedIn: http://linkd.in/OASISopen >> Twitter: http://twitter.com/OASISopen >> Facebook: http://facebook.com/oasis.open >> >> --------------------------------------------------------------------- >> To unsubscribe from this mail list, you must leave the OASIS TC that >> generates this mail. Follow this link to all your TCs in OASIS at: >> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: tag-unsubscribe@lists.oasis-open.org >> For additional commands, e-mail: tag-help@lists.oasis-open.org >> >> > > > > -- > > /chet > ---------------- > Chet Ensign > Director of Standards Development and TC Administration > OASIS: Advancing open standards for the information society > http://www.oasis-open.org > > Primary: +1 973-378-3472 > Mobile: +1 201-341-1393 > > Follow OASIS on: > LinkedIn: http://linkd.in/OASISopen > Twitter: http://twitter.com/OASISopen > Facebook: http://facebook.com/oasis.open > > --------------------------------------------------------------------- > To unsubscribe, e-mail: tag-unsubscribe@lists.oasis-open.org > For additional commands, e-mail: tag-help@lists.oasis-open.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: tag-unsubscribe@lists.oasis-open.org > For additional commands, e-mail: tag-help@lists.oasis-open.org > > -- /chet ---------------- Chet Ensign Director of Standards Development and TC Administration OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-378-3472 Mobile: +1 201-341-1393 Follow OASIS on: LinkedIn: http://linkd.in/OASISopen Twitter: http://twitter.com/OASISopen Facebook: http://facebook.com/oasis.open
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]