Create additional docs (documentdb#290)

Additional docs needed for:

Governance
Project Maintainers
Update CONTRIBUTING guidelines
Updated Security
Update Code of Conduct

Author: abinav2307

CODE_OF_CONDUCT.md

@@ -1,9 +1,48 @@
-# Microsoft Open Source Code of Conduct
+# Code of Conduct
 
-This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).
+**Effective: September 14, 2017**
 
-Resources:
+LF Projects, LLC ("LF Projects") supports and hosts open source and open standards projects (each a "Project") and undertakes such other activities as approved by The Linux Foundation. LF Projects, LLC is a Delaware series limited liability company. Projects of LF Projects are formed as separate series of LF Projects (each, a "Series"). References to "Projects" within this Policy include the applicable Series for each Project.
 
-- [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/)
-- [Microsoft Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/)
-- Contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with questions or concerns
+## Our Pledge
+
+LF Projects hosts communities where participants choose to work together, and in that process experience differences in language, location, nationality, and experience. In such a diverse environment, misunderstandings and disagreements happen, which in most cases can be resolved informally. In rare cases, however, behavior can intimidate, harass, or otherwise disrupt one or more people in the community, which LF Projects will not tolerate.
+
+A Code of Conduct ("Code") is useful to define accepted and acceptable behaviors and to promote high standards of professional practice. It also provides a benchmark for self-evaluation and acts as a vehicle for better identity of the organization.
+
+## Scope
+
+This Code applies to any participant of any Project – including without limitation developers, participants in meetings, teleconferences, mailing lists, conferences or functions, and contributors. Note that this Code complements rather than replaces legal rights and obligations pertaining to any particular situation.
+
+In addition, with the approval of LF Projects, Projects are free to adopt their own code of conduct in place of the Code.
+
+## Our Standards
+
+LF Projects is committed to maintain a positive, professional work environment. This commitment calls for workplaces where participants at all levels behave according to the rules of the following code. A foundational concept of this code is that we all share responsibility for our work environment.
+
+**We expect participants to:**
+
+- Treat each other with respect, professionalism, fairness, and sensitivity to our many differences and strengths, including in situations of high pressure and urgency.
+- Never engage in any form of harassment, including but not limited to:
+  - **Harassment** is any conduct, verbal or physical, that has the intent or effect of interfering with an individual, or that creates an intimidating, hostile, or offensive environment.
+  - **Sexual harassment** includes visual displays of degrading sexual images, sexually suggestive conduct, offensive remarks of a sexual nature, requests for sexual favors, unwelcome physical contact, and sexual assault.
+
+## Who This Applies To
+
+Anyone from the Public partaking in the LF Projects work environment (e.g. contribute code, comment on our code or specs, email us, attend our conferences, functions, etc.)
+
+## Our Commitment
+
+**Respect** is the genuine consideration you have for someone (if only because of their status as participant in LF Projects, like yourself), and that you show by treating them in a polite and kind way.
+
+**Summary:** if you are unsure whether something might be welcome or unwelcome, don't do it.
+
+## Reporting
+
+To report incidents or to appeal reports of incidents, send email to the Manager of LF Projects, Mike Dolan ([manager@lfprojects.org](mailto:manager@lfprojects.org)). Please include any available relevant information, including links to any publicly accessible material relating to the matter.
+
+Every effort will be taken to ensure a safe and collegial environment in which to collaborate on matters relating to the Project. In order to protect the community, the Project reserves the right to take appropriate action, potentially including the removal of an individual from any and all participation in the project. The Project will work towards an equitable resolution in the event of a misunderstanding.
+
+## Attribution
+
+This code is based on the W3C's Code of Ethics and Professional Conduct with some additions from the Cloud Foundry's Code of Conduct and the Hyperledger Project Code of Conduct.

CONTRIBUTING.md

@@ -4,7 +4,7 @@ Thank you for your interest in contributing to DocumentDB. There are several way
 
 ## Asking Questions
 
-[Join us on Discord](https://discord.gg/WXUrVbnt4n) to engage directly with our team and the community with any questions you may have. Our channel inside the Microsoft OSS server is not only a place for immediate assistance but also a hub for discussing project updates, upcoming features, and technical challenges. We host regular meetings where team members and contributors can interact directly to ask questions, share feedback, and discuss their ideas in real time.
+[Join us on Discord](https://discord.gg/vH7bYu524D) to engage directly with our team and the community with any questions you may have. Our channel is not only a place for immediate assistance but also a hub for discussing project updates, upcoming features, and technical challenges. We host regular meetings where TSC members and contributors can interact directly to ask questions, share feedback, and discuss their ideas in real time.
 
 ## Reporting Issues
 
@@ -21,42 +21,33 @@ The more descriptive the issue is and the more information that can be provided,
 For each issue created, please include: 
 
 - A brief description of the suggestion or issue.
-
 - Relevant details such as the operating system you were using, if applicable.
-
 - Clear, step-by-step instructions or context that describe how the issue occurred or how the feature would function.
-  
 - The expected outcome versus the actual result or behavior observed, if relevant.
 
 ### Code Contributions
 
 For those looking to contribute code, whether for bug fixes or new features, please ensure your issues and pull requests include the following:
 
 - A code snippet that reliably reproduces the issue or demonstrates the new feature.
-
 - An accessible repository link that can be cloned, built, and run, providing a complete environment for testing and verifying the issue or feature.
-
 - Clear documentation or comments in the code explaining the changes made and their purpose.
 
 ## Pull Requests
 
-Before a pull request is accepted, you will need to sign a [Contributor License Agreement (CLA)](https://cla.opensource.microsoft.com/), an automated process that is triggered by a bot and only needed once. If you have previously signed the CLA, the status check turns green instantly. If you are yet to sign the CLA, a comment is added with more information and instructions on how to sign the CLA.
-
-For the smoothest and fastest turnaround time, we request that a single pull request be created along with a link to a previously created issue describing the bug or feature request.
-
-Wherever applicable, pull requests should contain tests.
+We want to ensure all contributions made by the developer community are correctly licensed. To achieve this, DocumentDB uses a Developer Certificate of Origin (DCO). The DCO is a declaration attached to each commit to the project. A message that simply adds a Signed-off-by statement to every commit to DocumentDB is all that is needed and this confirms that the committer agrees to the DCO, which can be located at https://developercertificate.org/.
 
-## Suggestions
+DocumentDB requires every contribution to be signed with a DCO through a known identity. Anonymous names or pseudonyms cannot be used. An example of a DCO signed commit message is:
 
-We’re keen to hear your feedback on the future of DocumentDB. Feature Requests can be submitted through the issue tracker. To ensure suggestions are reviewed faster, we do request that the following information be provided for each suggestion:
+Signed-off-by: John Doe <john.doe@email.com>
 
-- Purpose/Motivation for the feature
+git commit --signoff can also be used to automatically add the Signed-off-by message to the end of a commit message if git configs have been set to include user.name and user.email.
 
-- Description of the problem space that will be solved or addressed by this feature
+Commits of any form require a DCO, including revert commits.
 
-- Description of a few scenarios that will help test and validate this feature
+## Technical Steering Committee and Maintainers
 
-For even quicker engagement and real-time discussions about your feature ideas, join our [Discord channel](https://discord.gg/WXUrVbnt4n). Our team and community members are actively available to provide feedback, answer questions, and collaborate on refining your suggestions before they are formally submitted through the issue tracker.
+DocumentDB is governed by the Technical Steering Committee, where all decisions are conducted in the open, documented, and voted upon. All code that is checked in is managed by the Maintainers. The list of TSC members and the project's maintainers are listed in the [MAINTAINERS.md](./MAINTAINERS.md) file. 
 
 ## Discussion Etiquette