diff --git a/JspChat/contributors.md b/JspChat/contributors.md
new file mode 100644
index 0000000..d668e34
--- /dev/null
+++ b/JspChat/contributors.md
@@ -0,0 +1,44 @@
+Note that individual Jackson projects have different maintainers; see the individual project
+README for the list of maintainers of that module.
+## "New Contributor Friendly" issues
+A new (as of October 2019) effort is to try to collect issues that might be particularly good for
+new contributors:
+[Issues for New Contributors](https://github.com/FasterXML/jackson/wiki/Issues-For-New-Contributors) (Added for Hacktoberfest 2019)
+## Branches
+Jackson projects maintain a few branches:
+* `master` for developing the still-far-off 3.0.0 release
+* `2.12` the next minor version in development
+* `2.11` the current stable release
+* `2.10` the previous stable branch, for which patch releases are still made
+* `2.9` inactive branch that may receive micro-patches for urgent security issues (usually only [`jackson-databind`](https://github.com/FasterXML/jackson-databind))
+Most pull requests should be made against the current stable branch, `2.11`.  Pull requests for
+major new functionality or that significantly alter internals, but which is backwards-compatible
+with existing behavior should be made against the next minor version branch (`2.12`).  If
+Jackson's functionality or default behavior is to be altered, `master` is the correct branch, but
+discussion is probably in order.
+## Backwards Compatibility
+When submitting a pull request, your choice of a base branch should take into account backwards
+compatibility.
+The Jackson project follows [Apache versioning](https://apr.apache.org/versioning.html).  Patch
+versions maintain source and binary compatibility; functionality may be added, but existing code
+that depends upon Jackson must continue to function properly without alteration.  Minor versions
+add functionality, may deprecate existing functionality, and may remove functionality that has
+been deprecated for at least two minor versions.  Any changes that require breaking existing
+functionality must be part of a major version release.
+See [Jackson Releases on the wiki](https://github.com/FasterXML/jackson/wiki/Jackson-Releases)
+for more information.
+
+## Testing
+
+TODO
+Jackson's functionality is vast and is used widely, so automated testing for any changes is
+important for preventing accidental breakage in the future.  Tests also document and demonstrate
+the bounds of functionality, showing the author's intent to others working on the code in the
+future.
+
+## Paperwork
+
+* Contributor License Agreement, needed by core team to accept contributions. There are 2 options:
+    * Standard Jackson [Contributor License Agreement](../../blob/master/contributor-agreement.pdf) (CLA) is a one-page document we need from every contributor of code (we will request it for pull requests), used mostly by individual contributors
+    * [Corporate CLA](../../blob/master/contributor-agreement-corporate.txt) is used by Corporations to avoid individual employees from having to send separate CLAs; it is also favored by corporate IP lawyers.
+Note that the first option is available for corporations as well, but most companies have opted to use the second option instead. Core team has no preference over which one gets used; both work; we care more about actual contributions.