Merge pull request #1 from virtix/master

Add licensing template files

Author: virtix

CHANGELOG.md

@@ -0,0 +1,3 @@
+
+
+

CONTRIBUTING.md

@@ -0,0 +1,45 @@
+# Guidance on how to contribute
+
+> All contributions to this project will be released under the CC0
+> dedication. By submitting a pull request, or filing a bug, issue, or 
+> feature-request you are agreeing to comply with this waiver of copyright interest.
+> Details can be found in our [TERMS](TERMS.md) and [LICENCE](LICENSE).
+
+
+There are two primary ways to help: 
+ - Using the issue tracker, and 
+ - Changing the code-base.
+
+
+## Using the issue tracker
+
+Use the issue tracker to suggest feature requests, report bugs, and ask questions. 
+This is also a great way to connect with the developers of the project as well
+as others who are interested in this solution.  
+
+Use the issue tracker to find ways to contribute. Find a bug or a feature, mention in
+the issue that you will take on that effort, then follow the _Changing the code-base_ 
+guidance below.
+
+
+## Changing the code-base
+
+Generally speaking, you should fork this repository, make changes in your
+own fork, and then submit a pull-request.  All new code should have associated unit
+tests that validate implemented features and the presence or lack of defects. 
+Additionally, the code should follow any stylistic and architectural guidelines 
+prescribed by the project. In the absence of such guidelines, mimic the styles
+and patterns in the existing code-base.
+
+----
+
+## Public domain
+
+The project is in the public domain within the United States, and
+copyright and related rights in the work worldwide are waived through
+the [CC0 1.0 Universal public domain dedication][CC0].
+
+
+[CC0]: http://creativecommons.org/publicdomain/zero/1.0/
+
+

README.md

@@ -1,4 +1,64 @@
-open-source-project-template
-============================
+#### CFPB Open Source Project Template Instructions
+
+1. Create a new project
+2. Copy these files into the new project
+3. Update the README, replacing the contents below as prescribed
+4. Add any libraries, assets, or hard dependencies to the _Exceptions_ section in the [TERMS](TERMS.md)
+5. Delete these instructions and everything up to the _Project Title_ from the README
+6. Write some great software and tell people about it
+
+> Keep the README fresh! It's the first thing people see and will make the initial impression.
+
+----
+
+# Project Title
+
+**Description**:  Put a meaningful, short, plain-language description of what 
+this project is trying to accomplish and why it matters. 
+
+Other things to include:
+
+  - **Status**:  Alpha, Beta, 1.1, etc. It's OK to write a sentence, too.  The goal is to let interested people know where this project is at. This is also a good place to link to the [CHANGELOG](CHANGELOG.md)
+  - **Links to production or demo instances**
+  - Describe what sets this apart from related-projects. Again, a link to another doc is OK if this can't be expressed in a sentence or two
+
+
+**Screenshot**: If the software has visual components, place a screenshot after the description; e.g.—
+
+![](https://raw.githubusercontent.com/virtix/open-source-project-template/master/screenshot.png)
+
+
+## How to get this running or how to use it
+
+Detailed instructions on how to install, configure, and get the project running.
+This should be frequently tested to ensure reliability. Alternatively, a link to 
+another page is fine, but it's important that this works.
+
+
+## Getting involved
+
+This section should detail why people should get involved and describe key areas you are
+currently focusing on; e.g., trying to get feedback on features, fixing certain bugs, building
+important pieces, etc.  
+
+General instructions on _how_ to contribute should be stated with a link(CONTRIBUTING.md) 
+
+
+____
+
+## Open Source Licensing Info
+1. [License](LICENSE)
+2. [TERMS](TERMS.md)
+3. [CFPB Source Code Policy](http://github.com/cfpb/source-code-policy/)
+
+
+----
+
+### Credits and References
+
+1. Projects that inspired you
+2. Related projects
+3. Book, papers, or other writings that
+
+
 
-A project template containing default open source files for new projects

TERMS.md

@@ -0,0 +1,55 @@
+As a work of the United States Government, this package (excluding the
+exceptions below) is in the public domain within the United States.
+Additionally, we waive copyright and related rights in the work worldwide
+through the CC0 1.0 Universal public domain dedication.
+
+Software source code previously released under an open source license and then
+modified by CFPB staff or its contractors is considered a "joint work" (see 17 USC § 101); 
+it is partially copyrighted, partially public domain, and as a whole is protected by
+the copyrights of the non-government authors and must be released according to
+the terms of the original open-source license.
+
+For further details, please see the CFPB [Source Code Policy][policy].
+
+
+## CC0 1.0 Universal Summary
+
+This is a human-readable summary of the [Legal Code (read the full text)][CC0].
+
+### No Copyright
+
+The person who associated a work with this deed has dedicated the work to
+the public domain by waiving all of his or her rights to the work worldwide
+under copyright law, including all related and neighboring rights, to the
+extent allowed by law.
+
+You can copy, modify, distribute and perform the work, even for commercial 
+purposes, all without asking permission. See Other Information below.
+
+### Other Information
+
+In no way are the patent or trademark rights of any person affected by CC0,
+nor are the rights that other persons may have in the work or in how the
+work is used, such as publicity or privacy rights.
+
+Unless expressly stated otherwise, the person who associated a work with
+this deed makes no warranties about the work, and disclaims liability for
+all uses of the work, to the fullest extent permitted by applicable law.
+When using or citing the work, you should not imply endorsement by the
+author or the affirmer.
+
+[policy]: http://github.com/cfpb/source-code-policy/
+[CC0]: http://creativecommons.org/publicdomain/zero/1.0/legalcode
+
+
+## Exceptions
+
+_:Source code or other assets that are excluded from the TERMS should be listed
+here. These may include dependencies that may be licensed differently or are
+not in the public domain._
+
+
+
+
+
+