Interpress/Xerox/2.1 fjXEROXXC1-1-1TERMINAL kjv;XEROXXC1-1-1MODERN g 1;3v'XEROXXC1-1-1LOGOTYPES-XEROX nnjXEROXk%v'XEROXXC1-1-1MODERN{%v'Lv'Lv'njROOMS USERS' RULESkZ v'3uxj3u?Z u?kZ u?Z uZ u.7nxj.7oBF2oB-kF2oBF2nF2n.7nLxj.7n]F2n]kF2n]F2nLF2nL1kXEROXXC1-1-1 MODERN-Bold njROOMS USERS' RULESkBk.7ixj.7iҙF2iҗkF2iҊF2iF2i.7hxj.7hF2h-kF2hF2hF2h3g>3g>˝ 3dNvnj\This document describes the rules and procedures for "Rooms Users" modules. This document iskZ d3ctDunjSmainly for Rooms Users' module writers, but users should also understand the rules.kPct3`XEROXXC1-1-1 MODERN-Bold g )nj!DEVELOPING A ROOMS USERS' MODULEk5w`3^~NqnjXA Rooms Users' module is a useful program made available to the general Rooms community.kZ ^~n@3\N{nj[Neither the author nor the custodian of Rooms Users' imputes any warranty of suitability orkZ \3[vnjresponsibility for errors.k*[[vN ! 3XNtnj[Rooms Users' modules should be easily distinguishable from released library and Lisp Users'kZ X{3WwNynj^modules. In particular, this means that a Rooms Users' module may not have the same name as akZ Wwr3UNynjaLibrary or Lisp Users' module and should be visibly different. Rooms Users' modules derived fromkZ UUU@3ToNwnjUreleased software should be announced to the public only after communicating with thekZ To3R0nj4organization responsible for that released software.kmail or on akZ :@39mNsnj[floppy. External users should make sure that they include all relevant information, such askZ 9m37EnjVdocumentation containing an e!>mail or US mail address where he/she can be reached.kQl735n'nj SUBMITTING FILES TO ROOMS USERS'k3R5ni32N{njfAs with released software, it is important to submit not just the resulting product, but all the fileskZ 231o2nj3needed to build and maintain a Rooms Users' module:k=1o3.,nj3 1. the file to load ( .LCOM or .dfasl or .SUITE)k8!.3,y?njM 2. documentation describing it, following the formatting rules (see below)kK7,y3)-Tnj3 3. a source file that can be released (optional)k8)3'nj 4. data files, if neededk*'o3%NwnjXModules submitted once are released once. Do not assume that a module submitted for onekZ %3#6Inj>release will be automatically released in subsequent releases.kA#3! nj DOCUMENTATIONk''! kjv;XEROXXC1-1-1MODERN g 2;3v'XEROXXC1-1-1LOGOTYPES-XEROX nnjXEROXk%v'XEROXXC1-1-1MODERN{%v'Lv'Lv'njROOMS USERS' RULESkZ v'3uxj3u?Z u?kZ u?Z uZ ua@3nxNrnjVNo modules will be released without documentation. Documentation can be as simple as akZ nxV3lN|nj[paragraph describing what the module does and how to use it, or it can be as extensive as akZ lꎩ3kpNxnj`dozen!>page user manual. All modules should have a file with a .TEDIT extension. FormattingkZ kp;3iN{nj\should be done according to the rules outlined in the Rooms Users' Template, included on thekZ i3hhNsnj`Rooms Users floppy as EASYTEMPLATE.TEDIT. All users, external users included, should follow thekZ hhk3fNvnj]Rooms Users' Template rules. If the documentation is large and formatting time consuming, youkZ f\/@3e`Nqnjfcan also produce an interpress file (with the .ip extension), as well as submitting a .TEdit file. (BekZ e`u%@3c܊NsnjZsure to update the interpress file if you update the documentation!) Documentation shouldkZ c܊3bX)Znj*include the full address of the submitter.k4bX3_݊XEROXXC1-1-1 MODERN-Bold g  njCOMPATIBILITY k%_݊L0@3]bNynj`Any submitted Rooms Users' files should be compilable in a "vanilla" Rooms environment. The filekZ ]b3[ފ4nj;itself should load in any auxiliary modules when necessary.k@U[ފ3Yc"njThanks for your cooperation.k-Yckg