ReadySetGit/Legal.md
William Sandner fb3100a5fc GFM changes
2018-08-14 19:54:11 +02:00

7.0 KiB

<html> <head> </head> Overview Project Plan Workflows Current <!-- Markdown content here --> <h1 id="user-content-legal-issues" dir="auto">Legal Issues</h1> <hr> <h5 id="user-content-project" dir="auto">Project:</h5> <p dir="auto">::<a href="/Suborbital-Systems/ReadySetGit/src/commit/24b358f205606dd7bf7922e3cbf0b88a4314dde1/Home">PROJECTNAME</a></p> <h5 id="user-content-internal-release-number" dir="auto">Internal Release Number:</h5> <p dir="auto">::X.Y.Z</p> <h5 id="user-content-release-audience" dir="auto">Release Audience:</h5> <ul dir="auto"> <li>::General availability release ||</li> <li>::Customer-specific release: CUSTOMER(S) ||</li> <li>::Developer release (Internal usage only) ||</li> <li>::Early access release (Controlled external access)</li> </ul> <h5 id="user-content-intended-product-license" dir="auto">Intended Product License:</h5> <p dir="auto">::Commercial license</p> <h5 id="user-content-related-documents" dir="auto">Related Documents:</h5> <ul dir="auto"> <li><a href="/Suborbital-Systems/ReadySetGit/src/commit/24b358f205606dd7bf7922e3cbf0b88a4314dde1/Proposal">Project proposal</a> &gt; <a href="/Suborbital-Systems/ReadySetGit/src/commit/24b358f205606dd7bf7922e3cbf0b88a4314dde1/Target-and-Benefits">Target audience and benefits</a></li> <li><a href="/Suborbital-Systems/ReadySetGit/src/commit/24b358f205606dd7bf7922e3cbf0b88a4314dde1/plan">Plan</a> &gt; <a href="/Suborbital-Systems/ReadySetGit/src/commit/24b358f205606dd7bf7922e3cbf0b88a4314dde1/Resource-Needs">Resource needs</a></li> <li><a href="/Suborbital-Systems/ReadySetGit/src/commit/24b358f205606dd7bf7922e3cbf0b88a4314dde1/Glossary">Glossary</a></li> </ul> <hr> <p dir="auto"><strong>Process impact:</strong> This document outlines legal issues that may affect this release. Failure to carefully consider these issues may put the development organization at risk for legal action.</p> <p dir="auto"><em>TODO: Fill in the information above and below. Add or remove rows as needed. Use the worksheet to help identify legal issues. Seek professional counsel for review as needed.</em></p> <h3 id="user-content-ownership-of-intellectual-property" dir="auto">Ownership of Intellectual Property</h3> <table> <thead> <tr> <th>Component</th> <th>Owner</th> <th>License</th> <th>Status</th> <th>Comments</th> </tr> </thead> <tbody> <tr> <td>::Product name</td> <td>::Us</td> <td>::Trademark</td> <td>::Registration pending</td> <td>::We must use &quot;(TM)&quot;, not &quot;(R)&quot;</td> </tr> <tr> <td>::Database</td> <td>::VENDOR</td> <td>::Commercial license</td> <td>::In compliance, paid normal fee</td> <td>::Limits us to 2 CPUs/server</td> </tr> <tr> <td>::Encryption library</td> <td>::VENDOR</td> <td>::Commercial license</td> <td>::In compliance, signed partnership agreement</td> <td></td> </tr> <tr> <td>::Clip-art graphics</td> <td>::None</td> <td>::Public Domain</td> <td>::In compliance</td> <td></td> </tr> <tr> <td>::Sound driver library</td> <td>::OS Project</td> <td>::BSD</td> <td>::In compliance</td> <td></td> </tr> <tr> <td>::Search engine indexer</td> <td>::OS Project</td> <td>::GPL</td> <td>::In compliance</td> <td>::Indexer runs in separate process, does not make our code GPL</td> </tr> <tr> <td>::Other library</td> <td>::OS Project</td> <td>::BSD</td> <td>::In compliance</td> <td></td> </tr> <tr> <td>::Other data</td> <td>::Us</td> <td>::Copyrighted</td> <td>::In compliance</td> <td></td> </tr> <tr> <td>::Special algorithm patent</td> <td>::Us</td> <td>::Patent pending</td> <td>::In compliance</td> <td>::Patent search done, patent application submitted</td> </tr> </tbody> </table> <h3 id="user-content-regulatory-compliance" dir="auto">Regulatory Compliance</h3> <table> <thead> <tr> <th>Type</th> <th>Regulation</th> <th>Status</th> <th>Comments</th> </tr> </thead> <tbody> <tr> <td>::Export</td> <td>::Strong encryption exports must be declared</td> <td>::In compliance</td> <td>::We will not distribute out of country</td> </tr> <tr> <td>::Privacy</td> <td>::Cannot collect personal information from minors</td> <td>::In compliance</td> <td>::We ask for user age before asking for other information</td> </tr> <tr> <td>::Industry certification</td> <td>::Game industry rating</td> <td>::In compliance</td> <td>::We follow guidelines for &quot;Everyone&quot; rating</td> </tr> </tbody> </table> <h5 id="user-content-possible-status-values" dir="auto">Possible Status Values</h5> <ul dir="auto"> <li>In compliance: we are OK to go ahead with this release</li> <li>Waived: we decided not to consider this aspect for this release</li> <li>Violated: we are not conforming. Comment should describe impact.</li> </ul> <h3 id="user-content-legal-issues-checklist" dir="auto">Legal Issues Checklist</h3> <p dir="auto">The goal of this checklist is to help expose legal issues that might otherwise be missed. It does not help with the actual management of legal issues.</p> <p dir="auto"><em>TODO: Answer the questions below. If multiple sample answers are provided, delete the ones that do not apply. Edit any provided answers as needed.</em></p> <h4 id="user-content-does-the-development-organization-hold-trademarks-on-the-product-name-and-any-other-names-used-in-marketing-the-product" dir="auto">Does the development organization hold trademarks on the product name and any other names used in marketing the product?</h4> <p dir="auto">::Yes. Make sure to defend your ownership.</p> <p dir="auto">::No. Make sure not to impinge on the trademarks of others.</p> <h4 id="user-content-does-the-development-organization-hold-or-license-patents-on-intellectual-property-that-is-used-in-the-product" dir="auto">Does the development organization hold or license patents on intellectual property that is used in the product?</h4> <p dir="auto">::Yes. Make sure to defend your ownership.</p> <p dir="auto">::No. Make sure not to impinge on the patents of others.</p> <h4 id="user-content-does-the-development-organization-hold-or-license-copyrights-on-source-code-that-is-used-in-the-product" dir="auto">Does the development organization hold or license copyrights on source code that is used in the product?</h4> <p dir="auto">::Yes. Make sure to defend your ownership.</p> <p dir="auto">::No. Make sure not to impinge on the patents of others.</p> <h4 id="user-content-for-each-component-in-the-product-is-that-component-being-used-in-a-way-that-complies-with-its-license" dir="auto">For each component in the product, is that component being used in a way that complies with its license?</h4> <p dir="auto">::Fill in details in table above.</p> <h4 id="user-content-for-each-piece-of-copyrighted-data-in-the-product-is-that-data-being-used-in-a-way-that-complies-with-its-license" dir="auto">For each piece of copyrighted data in the product, is that data being used in a way that complies with its license?</h4> <p dir="auto">::Fill in details in table above.</p> <h4 id="user-content-was-any-component-or-data-produced-by-another-organization-under-contract" dir="auto">Was any component or data produced by another organization under contract?</h4> <p dir="auto">::Yes. Review the contract details for ownership and licensing.</p> <p dir="auto">::No. No action required.</p> <h4 id="user-content-does-the-product-use-technologies-that-are-under-export-control" dir="auto">Does the product use technologies that are under export control?</h4> <p dir="auto">::Yes. But, we have no plans to export.</p> <p dir="auto">::Yes. Take steps to obtain needed export permissions.</p> <p dir="auto">::No. No action required.</p> <h4 id="user-content-does-the-product-need-to-meet-industry-specific-regulations" dir="auto">Does the product need to meet industry-specific regulations?</h4> <p dir="auto">::Yes. Take steps to meet them. Specifically...</p> <p dir="auto">::No. No action needed.</p> <h4 id="user-content-does-the-product-satisfy-corporate-policies-eg-on-privacy-and-security" dir="auto">Does the product satisfy corporate policies (e.g., on privacy and security)?</h4> <p dir="auto">::Yes. Describe how each policy is satisfied..</p> <p dir="auto">::No. Describe steps to bring the product into compliance.</p> <p dir="auto">::No. No policies apply.</p> <!-- End Markdown content -->
</html>