[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [id-cloud] Why we were born
do not have issues in going to PR, for minor editorial changes. :)Standards Development is not a primary job of some people like me. Oasis rules should take into account, the changing world and the need to maintain the enthusiasm
of technical volunteers from companies. ;)I will put the latest editor's version for voting by the TC to send to 15 day PR, at the Monday's
meeting. On 03/15/2012 08:37 AM, Chet Ensign wrote:
Hmm - that complicates matters. Here's the thing: if you make any changes to a draft after a public review, even changes as minor as this, then the document has to be put out for another round of review before you can vote to move it from CND to Committee Note status. Discussions are underway about seeing if we can ease that requirement, however I have to manage to the rules as they stand and section 3.2, Public Review of a Committee Draft is unambiguous: "If any changes are made to the draft after the public review, whether as a result of public review comments or from TC Member input, then the TC must conduct another review cycle. The draft may not be considered for approval by the TC as a Committee Specification or Committee Note until it has undergone a review cycle during which it has received no comments that result in any changes." So the options are that the TC can approve the last publicly reviewed CND to be put up for ballot as a Committee Note or submit this version for another 15 day PR cycle. Also, just to help ensure things go as smoothly as possible, when you approve a draft for an action in your meeting, I need to have the link to the document in Kavi that the TC is approving in the minutes and that same link provided in the ticket to TC Admin requesting the support. That ensures that we can always connect the dots, should we be asked, between the artifact that the TC approved and the one that TC Admin formally publishes in the OASIS Library. Motion language like this: "Do the members of the TC approve ID-Cloud Use Cases WD02 (contained in http://www.oasis-open.org/apps/org/workgroup/id-cloud/document.php?document_id=45416) as a Committee Note Draft and further approve it be released for public review?" ... in your minutes suits the need just fine. If it would be helpful, I would be happy to dial in to one of your meetings or call you separately and walk through the process step by step. I realize that there is a learning curve here and I'd like to help get through it in any way I can. Let me know if you have any questions about this or want to talk about next steps further. Best, /chet On Wed, Mar 14, 2012 at 7:43 PM, Matt Rutkowski<mrutkows@us.ibm.com> wrote:Yes, we agreed as a TC to remove the work "normative" in all its forms and approved the changes by motion at last week's TC call. Since to section titles had "Normalize" in them the ToC had to be updated as well. Also, fixed 1 table where the header row broke across pages making the table unreadable. Kind regards, Matt From: Chet Ensign<chet.ensign@oasis-open.org> To: Matt Rutkowski/Austin/IBM@IBMUS Cc: Anil Saldhana<Anil.Saldhana@redhat.com>, "id-cloud@lists.oasis-open.org"<id-cloud@lists.oasis-open.org>, James Bryce Clark<jamie.clark@oasis-open.org>, Anthony Nadalin<tonynad@microsoft.com> Date: 03/14/2012 03:30 PM Subject: Re: [id-cloud] Why we were born Sent by:<id-cloud@lists.oasis-open.org> ________________________________ Matt, is this different from the version that went out for public review? Thx, /chet On Wed, Mar 14, 2012 at 4:00 PM, Matt Rutkowski<mrutkows@us.ibm.com> wrote:Anil, We will need to have Chet reference the version with the agreed (as per TC minutes) upon editorial changes for final posting. This is the location for that revision (which reflects the voted editorial changes): http://www.oasis-open.org/apps/org/workgroup/id-cloud/download.php/45416/id-cloud-usecases-v1.0-wd02a.doc Kind regards, Matt From: Chet Ensign<chet.ensign@oasis-open.org> To: Anil Saldhana<Anil.Saldhana@redhat.com> Cc: Anthony Nadalin<tonynad@microsoft.com>, "id-cloud@lists.oasis-open.org"<id-cloud@lists.oasis-open.org>, James Bryce Clark<jamie.clark@oasis-open.org> Date: 03/14/2012 12:43 PM Subject: Re: [id-cloud] Why we were born Sent by:<id-cloud@lists.oasis-open.org> ________________________________ Anil, please enter a ticket at http://www.oasis-open.org/resources/tc-admin-requests/committee-note-ballot-request with the requested information. That gets your request onto the TC Admin work queue. Thanks, /chet On Wed, Mar 14, 2012 at 1:23 PM, Anil Saldhana<Anil.Saldhana@redhat.com> wrote:Chet, the TC has voted at the last meeting. Once the minutes are ready, please create a ballot to move it from CND to CN. Regards, Anil On 03/13/2012 06:40 PM, Chet Ensign wrote:Hi Anil - Just a clarification on process. Not sure if I am understanding the below correctly, however the process for approving a CND as a CN (or CSD as a CS) is: - TC votes to request that TC Admin start a Special Majority Ballot for the TC to approve the CND as CN - Someone on the TC enters a Committee Note Ballot Request ticket to TC Admin at http://www.oasis-open.org/resources/tc-admin-requests/committee-note-ballot-request including a link to the minutes recording the above vote - TC Admin sets up the ballot and notifies the TC - Once the ballot period is closed, and assuming of course that it passes, TC Admin prepares the CN, loads it to docs.oasis-open.org and announces it to the TC, OASIS members and the world at large. Peter is correct too - I can provide you with the URIs to the Committee Note once the ballot is closed and we start work on the CN itself. Let me know if you have any questions on this. I generally get the ballot started same or next day. Best, /chet On Tue, Mar 13, 2012 at 4:59 PM, Anil Saldhana<Anil.Saldhana@redhat.com> wrote:At the last meeting, our Use Case Document has been voted into "Committee Note" Status. Now the editors/TCAdmin should work to put it on the Oasis site. On 03/13/2012 01:53 PM, Anthony Nadalin wrote: Time has come where other organizations are asking for our use case and gap analysis documents, in particular ITU-T SG17 Q8 is pulling together a set of use cases and this effort would be best informed by the work that this TC has done. So we need to make sure that the proposer procedures are in place to share these documents with other standards organizations, so maybe Jamie can give us the correct procedures to follow.--------------------------------------------------------------------- To unsubscribe, e-mail: id-cloud-unsubscribe@lists.oasis-open.org For additional commands, e-mail: id-cloud-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: id-cloud-unsubscribe@lists.oasis-open.org For additional commands, e-mail: id-cloud-help@lists.oasis-open.org-- /chet
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]