Members of the SARIF TC, Again, congratulations on getting the TC off to a successful start. Here are some pointers to resources that may be useful to you as you move your work forward. - TC-specific resources 1) Your Charter Your charter is the document that governs the work of your TC. In particular, it spells out what is in and out of scope and the essential objectives that you have set out to address.
https://www.oasis-open.org/committees/sarif/charter.php 2) Your public and internal TC Home Page - the public page is the web page visitors to
www.oasis-open.org see. The internal page is where you can manage your roster, start electronic ballots, store working documents, etc. Public page:
https://www.oasis-open.org/committees/sarif/ TC member web page:
https://www.oasis-open.org/apps/org/workgroup/sarif/ 3) Your TC email list and comment lists - the comment list is the only allowed channel for non-OASIS member comments to the TC. You must subscribe to the comment list explicitly by sending a blank email to
sarif-comment-subscribe@lists.oasis-open.org . We recommend that the Chair assign a member of the TC to explicitly be responsible for monitoring the comment list.
https://lists.oasis-open.org/archives/sarif/ https://lists.oasis-open.org/archives/sarif-comment/ 4) TC chat room - you can use this chat room to support the running of your meetings.
http://webconf.soaphub.org/conf/room/sarif 5) TC Document Repository - this is where you can store your meeting minutes, working drafts, etc.
https://www.oasis-open.org/apps/org/workgroup/sarif/documents.php Other facilities you can request include: 6) OASIS Open Repositories, providing the ability to launch one or more TC-affiliated open source projects. See
https://www.oasis-open.org/resources/open-repositories for more information. To request that an Open Repository, use this support ticket:
https://www.oasis-open.org/resources/tc-admin-requests/open-repository-request 7) GitHub Repositories for TC's work, providing the ability to perform version control with GitHub for the TC. See
https://www.oasis-open.org/resources/tcadmin/github-repositories-for-oasis-tc-members-chartered-work for more information. To request that a TC Github be set up, use this support ticket:
https://www.oasis-open.org/resources/tc-admin-requests/request-a-tc-github-version-control-instance-be-created - General OASIS policies and guidelines 1) The OASIS TC Administration How-to Guide provides specifics on how the TC Process policies are put into practice. You can access it at httpss://
www.oasis-open.org/resources/tcadmin/tc-process-how-to-guide-introduction 2) The OASIS Naming Directives document - This document spells out the rules governing filenames and URIs for Technical Committee Work Products.
https://docs.oasis-open.org/specGuidelines/ndr/namingDirectives.html 3) The OASIS Liaison Policy - this is the policy that governs relationships between OASIS and other organizations and may be of interest if the TC is considering submitting work to other organizations in the future.
https://www.oasis-open.org/policies-guidelines/liaison 4) Other OASIS policies and guidelines - the full list of OASIS policy and guidelines documents can be found at
https://www.oasis-open.org/policies-guidelines See in particular the OASIS Technical Committee Process and Intellectual Property Rights policy documents - these are two of the primary documents that govern work at OASIS. The IPR documentation may be relevant if a TC member intends to contribute a particular work to the TC.
https://www.oasis-open.org/policies-guidelines/tc-process https://www.oasis-open.org/policies-guidelines/ipr - Best practices and guidance from the OASIS Technical Advisory Board (TAB) The OASIS TAB is a group of elected representatives from the membership preparing best practices documents to help TCs produce high-quality work under the OASIS procedures, including: 1) "Checklist for Verifying the Editorial Quality of OASIS Specifications" -
https://www.oasis-open.org/committees/document.php?document_id=54999 2) "Guidelines to Writing Conformance Clauses for OASIS Specifications" -
http://docs.oasis-open.org/templates/TCHandbook/ConformanceGuidelines.html 3) "OASIS Keyword Guidelines" -
https://www.oasis-open.org/policies-guidelines/keyword-guidelines 4) "Conformance, Interoperability and Portability Testing: Procedures and Practices" -
https://wiki.oasis-open.org/tab/TestingPolicy 5) "Testability Guidelines" -
https://wiki.oasis-open.org/tab/TestabilityGuide - Other sources of helpful information 1) Help with Kavi - on the main page of your internal TC web page you will find a link to the Kavi Group help manual. This link will take you directly to that page.
https://www.oasis-open.org/khelp/phpgroups/user_help/html/home_group.html 2) TC Admin support request forms - These are the tickets you use to request working draft templates, ballots, public reviews, etc. These forms formally create the tickets used by TC Admin to manage its work. TC Admin will not take requests for support for these routine activities by email. The forms can also be found under the Resources tab on the OASIS home page
https://www.oasis-open.org/resources/tc-admin-requests 3) The OASIS Library -- this is where approved Work Products (Committee Specification Drafts, etc.) of your TC will be published. The top level directory will be created when your first approved work product is ready.
https://docs.oasis-open.org/sarif/ In addition to these, you can be set up to use the OASIS wiki, JIRA issues tracking tool, SVN version-control tool and web conferencing chat room. Let me know if and when you are interested in using any of these tools. -- /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-996-2298 Mobile: +1 201-341-1393