OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

xdi message

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

Subject: Re: [xdi] Re: Chet: creating an Editor's Subcommittee

Chet, thanks so much, I forgot to ask you about this when you joined our call today.

One question: we are not proposing that the Editor's SC have any deliverables of its own (with the possible exception of a Docbook template and a Glossary), simply that it be a collaboration group for the editors. The list of deliverables is still the responsibility of the overall TC.

So this is my strawman:
  1. Name of SC: XDI Editor's SC
  2. Statement of Purpose: To facilitate collaboration between the editors of XDI TC specifications.
  3. List of Deliverables: No formal deliverables, though the SC may produce a shared Docbook template and a Glossary.
  4. Chair: Peter Davis (see below)
Peter, you willing to chair this SC?

Chet: can you give us feedback on the above, and language on the motion we should pass to approve this?



On Fri, Apr 11, 2014 at 11:10 AM, Chet Ensign <chet.ensign@oasis-open.org> wrote:

Pretty easy really. Decide on the name, statement of purpose, list of deliverables and a chair. Put all those into a motion and pass it in a meeting. 

Then fill out -> https://www.oasis-open.org/resources/tc-admin-requests/subcommittee-creation-request 

I will get the SC set up and arrange for the email to be indexed by MarkMail. Once that is done I will update the TC webpages and let you know that the facility is set up. 



On Fri, Apr 11, 2014 at 1:45 PM, =Drummond Reed <drummond.reed@xdi.org> wrote:

The XDI TC wants to create an Editor's SC so we can have meetings and calls devoted just to editor's issues. I see the following description about an SC in the TC Process document, but how do we actually proceed to create an Editor's SC?



The TC may by Resolution create a Subcommittee (SC). The Resolution must be minuted, and must include the name, statement of purpose, list of deliverables, and name of the Chair of the SC. All of these items must fall within the Charter of the TC and conform to OASIS policy.

The deliverables of the SC are made only to the TC. Members of the SC must first be Members of the TC. Observers of a TC may be Observers of a SC, but may not become SC members without first becoming a Member of the TC. An SC member may resign from the SC and remain a Member of the TC.

The TC may close a Subcommittee (SC) by Resolution. The Resolution must be minuted, and must include the name of the Subcommittee.


Chet Ensign
Director of Standards Development and TC Administration 
OASIS: Advancing open standards for the information society

Primary: +1 973-996-2298
Mobile: +1 201-341-1393 

Check your work using the Support Request Submission Checklist at http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html 

TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin

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]