Revised 3/27/03: Bob Ross Revised 6/2/98: Bob Ross Revised 4/26/08 Bob Ross - substituted Michael Mirmak for Stephen Peters Revised 12/22/09 Bob Ross - developed the TSIRD Form Revised 6/21/2015 Mike LaBonte - New email addresses. ----------------------------------------------------------------------------- (edited for TSIRD instead of BIRD) Howdy, 9/15/93 The following is your key to getting issues resolved in the IBIS Open Forum. It's called a "Touchstone Issue Resolution Document" or "TSIRD". Issues must be well thought out and clearly documented using this template to be placed on the agenda of a future IBIS Open Forum. Here's how the process works. Write up your issue and submit it to the IBIS Open Forum Chair (currently Bob Ross at bob@teraspeedlabs.com) or ibis-info@freelists.org. The Chair will do a preliminary check for completeness and (potentially) send your BIRD back to you. If not, the Chair will post the issue to the reflector. Each issue must be out for review for two weeks before the Open Forum will vote on it. During that time, you will be expected to answer questions related to your TSIRD. In each meeting announcement, the Chair will list those TSIRDs that are ready for a vote at that meeting. { New statement } A TSIRD will be accepted if the meeting has a quorum and the majority of voting members vote in favor of it. The IBIS Open Forum strives to reach a consensus or near consensus of all members in preparation for future public review. So normally the IBIS Open Forum will defer a formal vote until all concerns expressed by members are discussed and resolved. { This sentence is deleted } A TSIRD will be accepted if EVERYONE at the meeting agrees with it. Please note that Open Forum time will not be used for detailed TSIRD review, but rather for confirming consensus. Detailed review MUST ensue during the two-week review cycle via emails. Dissenters should not wait until the Open Forum to express their opinions. So far the group has been exceedingly cooperative, achieving a 2.0 spec in only a couple of months. Hopefully this process will allow us to use time more efficiently, while maintaining the same flavor in the larger group setting. Regards, Don Telian NOTE: All text in french brackets is for explanation only and should be deleted. ---------------------------- cut here --------------------------------- Touchstone Issue Resolution Document (TSIRD) TSIRD ID#: {don't fill in, will be filled in by IBIS Chair for Tracking} ISSUE TITLE: {one line description of your issue} REQUESTOR: {your name and company} DATE SUBMITTED: {date you sent to IBIS Chair} [ DATE REVISED: {revision date} ] NOT USED DATE ACCEPTED BY IBIS OPEN FORUM: {status or date TSIRD accepted} **************************************************************************** **************************************************************************** STATEMENT OF THE ISSUE: {Place a short description of your issue here. People should be able tell by reading this if they care about this in less than 1 minute.} **************************************************************************** STATEMENT OF THE RESOLVED SPECIFICATIONS: {For new keywords, write the text EXACTLY AS IT SHOULD APPEAR in a future IBIS specification. If this is a change, state the old text and the new text again EXACTLY AS IT SHOULD APPEAR. Be sure to give intended location in the specification.} **************************************************************************** ANALYSIS PATH/DATA THAT LED TO SPECIFICATION: {There are many "experts" reviewing this document. Your reasons, analysis, and justifications must be precise and well documented, or your TSIRD will be sent back to you. Use this section to show that you've done your homework, and answer all questions that will undoubtedly be asked. If your issue is a change instead of an enhancement, document how backward compatibility is to be addressed.} **************************************************************************** ANY OTHER BACKGROUND INFORMATION: {These documents will be archived, so use this section to carry any detail that is not essential to the previous section, but should not be lost.} ****************************************************************************