It is my personal belief that OASIS as a member run organization should allow and provide a vehicle to enable the members of the organization to help create and develop the best current practice documents that they may want to use in their individual TCs.
Having a TC adopt any best current practice or claim conformance to any best current practice document is NO different than a TC creating and establishing their own standing rules from their own best current practices that they created in their TC.
Further, as is stated in the proposed charter, "All BCPs that are created must comply with OASIS Policy and must not encourage practices that violate OASIS Policy.â To this end OASIS policies, IMHO, should be very high level and ensure compliance with ANSI, ISO, and other SSOs / SDOs that we get our certifications from. OASIS Policies and ByLaws should not focus on day-2-day and should change very little over the years. On the other hand, best current practices can changes as technology changes.
In addition, the day-2-day best current practices, IMHO, should not be done by the board, board process sub-committee of the board, or TAB. Best current practice documents should be done in the open and through a vehicle that allows everyone in the membership to contribute. I am sure there is a wealth of knowledge in our community that can help produce great best current practice documents.
As a member of the board of directors at OASIS, I fully support trying to help OASIS become better, easier to work with, and more prestigious in the market. I also full support trying to make things easier for the members and their TCs to do their work and work more efficiently in our massively distributed and technologically diverse world. This is why I have proposed the creation of this technical committee. However, if the membership-at-large does not want this, then that is okay. Because that is the will of the membership and we are a consensus based organization. But to date, I have only heard one person that has a concern with this. So if you have a concern or you are supportive of this work, please speak up.
Martin - I believe you lead the process committee at the board level. If the process was working well then there would be no need for this TC.
Seems like there is disconnect somewhere between what is working and folks working in TCs trying to make the rules work to get stuff done.
I personally donât find getting too fixated on the label of a rule vs best practice very helpful. I focus on enabling progress and effective use of time. This is a volunteer organization and as such everyoneâs time is limited.
Imo the board and all other leadership roles in the tcs should care about that as an important objective and if a best practice tc can help make things faster and more efficient then they should embrace that. Not defend rules because theyâre the rules.
So we can debate rules vs best practice all day long but the net result will be that we will still be in the exact same place as we started. Zero progress or improvement.
The main motivation for my comments is on determining the scope of this proposed TC and the boundary with existing policies, guidelines etc. that have been developed over the years by the Board, Staff and TAB . The charter, as I read it, proposes to develop voluntary practices that do not yet exist within OASIS, though your email below talks about fixing ârulesâ that are âout of dateâ, âdonât make senseâ, âa burdenâ or âirrelevantâ. Which is it, as these are two very different prospects?
Martin & other board members â Iâve been fairly active in the OASIS TC process for a few years now. I was encouraged by Bret taking an active measure to help document some of the âbest practicesâ because it has been my experience that the OASIS documents and guidelines were either out of date or just didnât make any sense to active work that Iâve seen or been involved in. Personally, Iâve worked in standards across IEEE, IETF and OASIS so I feel that I have some experience to draw from.
I get why a standards organization needs rules. But when those ârulesâ become a burden or irrelevant then I think the board should consider what is motivating this new âbest practicesâ TC to form in the first place.
So instead of trying to undermine its work (by some of the comments provided) maybe it would be good to consider that the folks in this new proposed TC are trying to make things *better* at OASIS and make it easier for everyone working in various TCs to learn from otherâs experiences while writing standards.
The board should not see this TC as a threat to the rules of OASIS but rather embrace the fact that a *member-driven* organization has members that wish to improve the organization.
Oh and just to be clear, while I disagree with most of these comments from Martin, OASIS is a member run consensus based organization. So I am more than happy to tweak the charter, if needed, to be inline with the majority.
Please find my comments and suggestions on the proposed charter in the attached redline.
To OASIS Members:
A draft TC charter has been submitted to establish the OASIS Best Current Practices Technical Committee. In accordance with the OASIS TC Process Policy section 2.2: (https://www.oasis-open.org/policies-guidelines/tc-process#formation) the proposed charter is hereby submitted for comment. The comment period shall remain open until 23:59 GMT on 11 November 2019.
OASIS maintains a mailing list for the purpose of submitting comments on proposed charters. Any OASIS member may post to this list by sending email to: firstname.lastname@example.org. All messages will be publicly archived at: http://lists.oasis-open.org/archives/oasis-charter-discuss/. Members who wish to receive emails must join the group by selecting "join group" on the group home page: http://www.oasis-open.org/apps/org/workgroup/oasis-charter-discuss/. Employees of organizational members do not require primary representative approval to subscribe to the oasis-charter-discuss e-mail.
This call for comment is also available as a Google Doc. See https://docs.google.com/document/d/1AfMM2Hoyu5fsVJ8VUhZf8uwTTq-cK_1YAX0qcqOGQDc/. Comments and suggestions may be left on that document.
Comments received will be reviewed by the proposers and a log of the comments and their resolution will be posted to oasis-charter-discuss mailing list before the telephone call with the convener.
A telephone conference will be held among the Convener, the OASIS TC Administrator, and those proposers who wish to attend no more than four days after the comment period closes. The announcement and call-in information will be noted on the OASIS Charter Discuss Group Calendar.
We encourage member comment and ask that you note the name of the proposed TC (BCP) in the subject line of your email message. Comments received will be reviewed by the proposers and a log of the comments and their resolution will be posted to oasis-charter-discuss mailing list before the telephone call with the convener.
If you wish to be listed as a co-proposer in the Call for Participation, please contact the convener Bret Jordan, email@example.com, Symantec Corporation. For representatives of OASIS organizational members, a statement of support from their Primary Representative will be required.
Section 1: TC Charter
(1)(a) Name of the TC
OASIS Best Current Practices (BCP) Technical Committee
(1)(b) Statement of Purpose
This technical committee will produce best current practice (BCP) documents to help with all aspects of managing and maintaining technical committees and their work products inside and outside of OASIS.
These documents will not be defined as OASIS Policy documents, but rather as best practices that a TC may voluntarily elect to adopt and may voluntarily then claim conformance to.
As these documents will be produced by a TC in OASIS, they can be referenced and used by other organizations outside of OASIS.
Organizations join standards developing organizations (SDOs) like OASIS and participate in the development of open standards to solve business problems. When SDOs lack sufficient best practices, organizations can potentially waste a lot of time trying to address overhead efficiencies, rather than spending the time doing the work that solves their target business problems.
The OASIS standards development organization has defined high level policy documents that govern how technical committees should work. However, these documents do not define or explain many of the day-to-day details that most TC need. As such most technical committees in OASIS are required to figure out day-to-day operations themselves. This leads to variability between technical committees and proves to waste a lot of time. In some cases this also includes different TCs creating similar but different best practices. For example, TCs often create and circulate their minutes differently, making it difficult for users to find minutes for each TC following a consistent search approach.
The idea behind this technical committee is to enable the members of the OASIS community to define and produce best practices that others in OASIS can use.
Historically some of this was written by the OASIS TAB, however, it is felt that as a member run organization the members should have a direct say in the best practices that are created, and have the opportunity to create those documents. By providing the recommended procedures for how to do specific tasks, these documents would help get new TCs operating efficiently faster and help them avoid common pitfalls. One example of a BCP that could help new TCs is "roster maintenance".
This technical committee will produce best current practice documents to help with all aspects of managing and maintaining a technical committee and its work products.
This TC will limit its scope to proposals addressing gaps identified in the TC Process and addressing tasks not covered by the TC Process. Some BCPs may be submitted to the Board Process Committee for formal adoption as policy.
The BCPs that this TC will create can help ensure that technical committees and their work products are managed and maintained in a consistent manner.
All BCPs that are created must comply with OASIS Policy and must not encourage practices that violate OASIS Policy.
It is possible that that this TC may produce multiple different BCPs for a single topic. Obviously the goal is to produce a single best practice document, however, we understand early on that some TCs may have radically different sets of requirements. Even if there are multiple BCPs for a single topic, at least they would all be documented in a single repository and could be easily referenced.
This technical committee will produce best current practice documents to help with all aspects of managing and maintaining a technical committee and its work products. This can include, but is not limited to, the following initial list of potential BCPs:
* How to manage voting rights across multiple meeting due to time zones
* Guidance for holding Face-to-Face Meetings
* Guidance for holding a plugfest or hackathon
* How to conduct OASIS business exclusively over email
* Accepting and tracking new work items
* Using Google Docs for document collaboration
* Using Git for document collaboration
* Using Markdown for document content regardless of collaboration tool
* Responsibilities of a TC or Subcommittee Chair
* Responsibilities of an Editor
* Gaining consensus and dealing with contentious issues
* Distributing leadership responsibilities and holding reelections
* Writing a conformance section
* Writing a security considerations section
* Writing a privacy considerations section
(1)(e) IPR Mode
All members of the OASIS community including contributors, editors, chairs, OASIS TAB members, OASIS staff, and OASIS Board members that are interested in helping improve the operational aspects of all technical committees at OASIS.
(Optional References for Section 1)
Section 2: Additional Information
(2)(a) Identification of Similar Work
Many SDOs have or produce best current practice documents. Some of these documents may be referenced or used as a baseline.
(2)(b) First TC Meeting
The first meeting will be held by teleconference on Wednesday, 17 December 2019, at 11:00 AM US Eastern. Symantec Corporation will host the call.
(2)(c) Ongoing Meeting Schedule
Other than a kick off meeting (meeting #2 that will be one month after the formation meeting), this technical committee may hold quarterly meetings as needed, to review contributions that can not be reviewed over email. It is expected that all work will be done electronically over email.
(2)(d) TC Proposers
* Duncan Sparrell, firstname.lastname@example.org, sFractal Consulting, LLC.
* Bret Jordan, email@example.com, Symantec Corporation.
* Jane Ginn, firstname.lastname@example.org, Cyber Threat Intelligence Network, Inc.
* Ryan Hohimer. email@example.com, DarkLight
* Justin Stewart, firstname.lastname@example.org, LookingGlass Cyber Solutions, Inc.
(2)(e) Primary Representatives' Support
I, Duncan Sparrell (email@example.com) as sFractal Consultingâs Primary Representative to OASIS, confirm our support for the OASIS Best Current Practices Technical Committee (BCP TC) charter and my participation.
I, Bret Jordan (firstname.lastname@example.org) as Symantec Corporation's Primary Representative to OASIS, confirm our support for the OASIS Best Current Practices Technical Committee (BCP TC) charter and our participation.
I, Jane Ginn (email@example.com) as Cyber Threat Intelligence Networkâs Primary Representative to OASIS, confirm our support for the OASIS Best Current Practices Technical Committee (BCP TC) charter and our participation.
I, Ryan Hohimer (firstname.lastname@example.org) as DarkLightâs Primary Representative to OASIS, confirm our support for the OASIS Best Current Practices Technical Committee (BCP TC) charter and our participation.
I, Allan Thomson (email@example.com) as a LookingGlass Cyber Solutions, Inc. Primary Representative to OASIS, confirm our support for the OASIS Best Current Practices Technical Committee (BCP TC) charter and our participation.
(2)(f) TC Convener
Bret Jordan, firstname.lastname@example.org, Symantec Corporation.
(2)(g) Anticipated Contributions
(2)(h) FAQ Document
(2)(i) Work Product Titles and Acronyms
Chief Technical Community Steward
OASIS: Advancing open source & open standards for the information society