================================================================= Rice University Center for Research on Parallel Computation Software Distribution Center (SDC) Software Submission Form (This file: SUBMIT) --------------------------------------------------------------- This form should be filled out and forwarded to the SDC to submit software for distribution by the SDC. Forms for PD and IU software can be submitted via EMAIL. A hard copy of the form must be signed by at least the person completing the form. In the case of multiple developers, signatures of each of the developers are preferred, but not required, unless royalties to the developers are involved. i.e. If more than nominal fees are to be charged for the software, and if royalties are then to be disbursed to the software developer(s), then signatures of each of the developers of the software are required. Hard copies of this form for CM software MUST be signed by each of the listed developers before the software can be included in the Catalogue. An initial EMAIL submission, however, will allow the SDC to begin its review of the information provided. Electronic submissions can be made to (sdc@cs.rice.edu). Hard copies can be mailed to: Rice University SDC 6100 S. Main MS #41 Houston, Texas 77005 (713) 527-6077 Please answer the questions below as fully as possible. Part of the purpose of these questions is to identify potential problem areas (e.g., areas where legal liability might be a possibility); complete answers will aid this process. For more information on the SDC software distribution program, see the file INFO. ================================================================= 1. INFORMATION ABOUT THE SOFTWARE 1.0 SDC Catalogue number (if known at this time): ____________ 1.1 (a) Short title of software (for use in the SDC catalog): ___ ____________________________________________________________ (b) Please provide a full-path specification or list of the files that comprise the software as it is to be distributed: ____________________________________________________________ 1.2 Has any associated research been published (or is publica- tion planned)? If so, please provide citation(s) for pos- sible inclusion in the SDC software catalog (optional): _______ ____________________________________________________________ 1.3 Distribution should be (check one; see the file INFO for more details on the various options): ___ PD: Public domain ___ IU: Non-commercial internal use, free (electonic) or nominal fee, no author/contributor royalties (w/o royalties) ___ IU2: Non-commercial internal use, significant license fee, author/contributor royalties (with royalties) ___ CM: Commercial development license, negotiated on an individual basis with each licensee. 1.4 Please provide an abstract, in as much detail as desired, of the software's capabilities (for possible inclusion in the SDC catalog): ___________________________________________ 1.5 Please describe the hardware platform and/or associated software support that is necessary to use the software (e.g., VAX running Ultrix to run software as-is, but can be adapted and recompiled for any Unix platform; etc.): _____ __________________________________________________________ 1.6 Please speculate about what kinds of users might be inter- ested in the software (e.g., oil exploration companies, au- tomobile manufacturers, defense contractors, computer de- signers, academic researchers in particular fields, etc.). Feel free to let your imagination run a little wild here, but please be as precise as possible about who the possible "market" might be: _______________________________________ __________________________________________________________ 1.7 What is the "competition" for this software? What other technologies are available to achieve analogous results? ___________________________________________________________ 1.8 The SDC's catalog description should state that the software as distributed includes (please check all applicable): ___ source code ___ relocatable object ___ executable ___ electronic copy of documentation file(s) ___ electronic copy of paper(s) associated with software (please ensure that citations are provided above; for published papers, be careful about journal copyrights) 1.9 Likely preferred format for physical distribution, when required (e.g., 9-track tape, 5.25" PC floppy disk, etc.): ______________________ 1.10 Please provide any other information that you think would be useful in the SDC's catalog description: ____________________ ================================================================= 2. INFORMATION ABOUT CONTRIBUTORS The identity of the developers of and other contributors to the software is needed to identify potential co-owners (in the legal sense) of the rights in the software. The law in this area is not fully developed; if any doubt exists whether someone might be a contributor, please provide the requested information about them (even if you're not sure about the matter) for possible further investigation. CAUTION: In responding to the questions below, please provide any **factual** information (even hearsay or rumor) that you have. * If you don't have first-hand knowledge, please distinguish between what you know and what you've heard. * If other persons might have more or better information about a particular matter, please identify them and indicate how they can be contacted. * When in doubt, indicate that a question exists and that further investigation may be warranted. * Please **don't** offer your opinions (e.g. "John Doe couldn't possibly have made any significant contributions to this code because he's not capable of a significant contribution"), suppositions, or surmises ("just the facts, ma'am") -- doing so could create a document that might be subject to misinterpretation or quotation out of context by an adversary some day. 2.1 Please provide: * The names of **all** individuals who contributed **in any way** to the creative parts of the development of the software or its underlying "technology," including development of theory, clever implementation details, library files and the like. "Routine coders" need not be identified, but when in doubt, identify a potential contributor for futher investigation; * The affiliation of each individual (e.g., Rice computer science professor, Rice electrical engineering graduate student, ABC Corporation researcher); and * A brief description of the contribution made by each such person as you understand it. EXAMPLE: "John Jones, Rice computer science associate professor: wrote entire source code and developed underlying algorithm while at Rice" (Please use additional space/sheets as necessary) Individual #1:____________________________________________________ Individual #2:____________________________________________________ Individual #3:____________________________________________________ ... 2.2 Were any of the above-named individuals employed (full- time, ** or ** part-time in areas relating to the software, e.g., as consultants) by corporations or other businesses, or by government agencies or departments, when they made their contributions to the software? If so, the "employer" conceivably may have some claim to rights in the software. Please explain briefly (see the caution above): __________________________________________________________ EXAMPLE: "Jane Doe, who developed the user interface, previously did consulting work for ABC Corporation that may have been in the same general area of technology as the software." 2.3 Was any state- or federal-government funding, or any corp- orate or other business-related funding, used in developing the software **or** in developing any part of the technology underlying the software? If so, please explain briefly (see the caution above): _____________________________________ Grant number: _____________________ 2.4 Were any previously-existing software pieces (e.g., library files, linkable modules, etc.) used in building the software **or** its documentation? If so, please explain briefly (see the caution above): _________________________________ 2.5 Was any part of the software written with the intent of performing the same functions as a commercial software package of any kind (e.g. to write a cheaper work-alike of a commercial package)? __________________________________________________ ================================================================= 3. PROPRIETARY RIGHTS 3.1 Copyrights: Has anyone registered the copyright in the software, or any part of it, yet? _______________________ 3.2 Are there any known unauthorized users of the software? If so, please explain briefly (see the caution above): ______ __________________________________________________________ 3.3 Patents: If you are interested in seeking patent protection for your software, see the file PATENTS for more information. Are you interested in investigating this possibility? _______ Note: In the U.S., a patent application must be filed no later than **one year** after the earliest of the first pub- lication, the first "offer" for sale (this is a buzz word), or the first "public" use (this is another buzz word; even use in secret for gain can be "public" use, but "experi- mental" use may not be), among other things. 3.4 To your knowledge, might any third party's rights be in- fringed by the SDC's distribution of the software, or a licen- see's use thereof, or any part thereof? (This question is intended to identify potential problems in this area for further investigation.) If your answer is "No", proceed. If your answer is "yes" or "maybe," skip to the next question; DO NOT WRITE ANY KIND OF "YES" OR "MAYBE" ANSWER, AND DO NOT PROVIDE ANY EXPLANATION HERE. You should discuss the matter only by telephone or in person with the SDC and its counsel to preserve any applicable attorney-client privilege and to avoid inadvertently creating documents that might be quoted out of context by an adversary. _____ No _____ Need more information; please contact me about this. I certify that the foregoing statements are true to the best of my knowledge, and that I have read and agree with the terms and conditions in the file ROYALTY maintained on-line by the SDC, concerning royalty payments and related matters. Pursuant to those terms and conditions: (1) Nonexclusive License for PD Software: If the software described in section 1 above (which for purposes of this authorization includes with limitation any documentation and/or data files associated with the computer programs) is PD software as indicated by me in section 1.3, I hereby grant Rice University a perpetual, irrevocable, royalty-free, world-wide nonexclusive license (a) to make and distribute copies of the software, (b) to create derivative works based on all or any part or parts of the software, (c) to make and distribute copies of any such derivative works, (d) to practice any patentable or unpatentable inventions embodied in the software, (e) without limiting the foregoing, generally to do any or all things with the software that may require my consent, and (f) to authorize others to do any of the foregoing things upon such terms as Rice University may deem appropriate in its discretion; (2) Assignment of All Rights in IU or CM Software: If the software described in section 1 above (which for purposes of this authorization includes without limitation any documentation and/or data files associated with the computer programs) is IU or CM software as indicated by me in section 1.3, I hereby assign to Rice University all right, title, and interest in and to the software, under any law governing patents, copyrights, trade secrets, and the like in any and all countries, together with the right to apply for patents, copyright registrations, and the like and the right to sue for present and/or past infringement, throughout the world. I agree to cooperate fully and promptly with Rice University, at its request and its expense, in filing patent applications, copyright registration applications, assignment documents, and the like in any and all countries for the purpose of perfecting Rice University's rights in the software. _________________________________ Signature of date person submitting this form _________________________________ Printed name and title Signatures (dated) of other developers: __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________ __________________________________________________________________________