| <html> |
| <body> |
| <p>Mtg notes from CLARAty mtg with IP office</p> |
| <p>Mar 18 2003</p> |
| <p>Attendees: Issa Nesnas, Tara Estlin, Jennifer Schlickbernd, Grace Fisher-Adams, Carmen Lam</p> |
| <p>Topic: IP/ITAR issues for CLARAty repository</p> |
| <p>Explained general repository setup to Jennifer and Grace. Included discussion of university and other center partners.</p> |
| <p>Distinction between pure JPL vs. collaborative items</p> |
| <p>Who owns IP?</p> |
| <p>Depends on contract terms</p> |
| <p>University contract usually grants university rights</p> |
| <p>Get copies of CMU and Univ of Minnesota contract</p> |
| <p>Make sure statement of work mentions central repository</p> |
| <p>If not, may want to amend</p> |
| <p>Learned difference between subcontractors (CMU, Univ of Minn, Ames – under CLARAty task contract) and task plans (other tasks funded under MTP that will use CLARAty)</p> |
| <p>Extend contract for first and task plan for second if need to extend coverage or access to software</p> |
| <p>Remote access forms (for outside user accounts on our machines)</p> |
| <p>Goes through security</p> |
| <p>We sponsor them</p> |
| <p>Might need to do this for all outside user accounts</p> |
| <p>Check with Ed Momjian</p> |
| <p>EIS/ISIS has procedure, background forms</p> |
| <p>IP liability issues</p> |
| <p>Task plans (with universities) – other tasks through Mars Tech, not directly under CLARAty</p> |
| <p>Will need government use license for ASPEN/CASPER </p> |
| <p>Can coordinate with Jennifer Schlickbernd</p> |
| <p>Will need to work with PI or task plan manager (I believe they need to request it)</p> |
| <p>Task plan (with Ames)</p> |
| <p>IP and Export office would like everyone to be civil servants</p> |
| <p>Not an option – only Maria is a civil servant</p> |
| <p>If not, all software needs to be marked with statement of limited rights (?)</p> |
| <p>Issa suggested putting marking when checkout code (as opposed to marking every file)</p> |
| <p>In order to approve repository access, JPL will need Raj Shea (from Ames Export Administrator’s office) and Ames patent counsel (Raj Padea) to sign off on process and verify Ames list of personnel are </p> |
| <p>U.S. persons</p> |
| <p>Bound to confidentiality</p> |
| <p>Subcontractors (contracts directly under CLARAty)</p> |
| <p>As part of license, it covers our IP and export provisions</p> |
| <p>Need to verify</p> |
| <p>Go through procurement office / contract negotiator</p> |
| <p>List s/w: CLARAty, ASPEN, CASPER</p> |
| <p>License will be for Caltech s/w (pure JPL s/w)</p> |
| <p>Subsequent version can be specified in license for lifetime of task (e.g., now have version 1, later will have version 4, etc.)</p> |
| <p>If new technology added will need to resubmit for new NTR but won’t have to redo contracts/licenses</p> |
| <p>Remote access forms through security</p> |
| <p>Things are more complicated for mixed JPL/outside center s/w</p> |
| <p>Open source discussion</p> |
| <p>Jennifer: ASPEN/CASPER will likely not be approved for this since approved for commercial use by CalTech</p> |
| <p>Open source for rest</p> |
| <p>Several things need to happen:</p> |
| <p>ITAR/Export approved</p> |
| <p>Caltech IP office will have to say not interested or approve</p> |
| <p>Legal will have to look over issue</p> |
| <p>Rich Wolfe (associate director - Office of Tech Transfer) will need to sign off</p> |
| <p>will likely not want to sign off on mixed IP software</p> |
| <p>may not like signing off on technology not yet developed</p> |
| <p>Rights to derivatives</p> |
| <p>If CMU changes so many lines of code (of e.g., CASPER) we have rights to it</p> |
| <p>Should be in language for ASPEN/CASPER section for subcontracts and task plans</p> |
| <p>ASPEN/CASPER has been licensed for commercial use through CalTech</p> |
| <p>If we ever had university collaborator that wasn’t under contract then would need to go to CMU and write memorandum of understanding</p> |
| <p>Issa doesn’t think this would happen</p> |
| <p>Plan now is to go with public model (i.e., open source) first</p> |
| <p>Might be good for open source effort to put language to that effect in contracts now</p> |
| </body> |
| </html> |
|
|
