chore: restore CLA/Contributing/code-of-conduct docs (#1520)

We missed adding these back with the new repo.

CLA.md

@@ -0,0 +1,27 @@
+
+# ElectricSQL Contributor License Agreement
+
+## Definitions
+
+- **Contributions**: software, bug fixes, configuration changes, documentation, or any other materials
+- **Project**: [github.com/electric-sql](https://github.com/electric-sql)
+- **ElectricSQL**: [Electric DB Limited](https://find-and-update.company-information.service.gov.uk/company/13573370)
+- **You**: the copyright owner or legal entity authorized by the copyright owner
+
+## Preamble
+
+The agreement clarifies the terms under which You may make Contributions to the Project. It protects You, ElectricSQL and licensees. It does not change your rights to use your own contributions for any other purpose.
+
+## Agreement
+
+You and ElectricSQL agree that:
+
+1. You grant to ElectricSQL a non-exclusive, irrevocable, worldwide, royalty-free, sublicenseable, relicenseable, transferable license under all of Your relevant intellectual property rights, to use, copy, prepare derivative works of, distribute and publicly perform and display the Contributions on any licensing terms, including without limitation: (a) open source licenses like the [Apache-2.0 License](https://www.apache.org/licenses/LICENSE-2.0); and (b) binary, proprietary, or commercial licenses. Except for the licenses granted herein, You reserve all right, title, and interest in and to the Contributions.
+2. You grant to ElectricSQL a non-exclusive, irrevocable (except as stated in this section), worldwide, royalty-free, sublicenseable, transferable patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Project, where such license applies only to those patent claims licensable by You that are necessarily infringed by Your Contribution(s) alone or by combination of Your Contribution(s) with the Project to which such Contribution(s) was submitted. If any entity institutes patent litigation against You or any other entity (including a cross-claim or counterclaim in a lawsuit) alleging that your Contribution, or the Project to which you have contributed, constitutes direct or contributory patent infringement, then any patent licenses granted to that entity under this Agreement for that Contribution or Work shall terminate as of the date such litigation is filed.
+3. You are able to grant us these rights. You represent that You are legally entitled to grant the above license(s). If Your employer has rights to intellectual property that You create, You represent that You have received permission to make the Contributions on behalf of that employer, or that Your employer has waived such rights for the Contributions.
+4. the Contributions are your original work. You represent that the Contributions are Your original works of authorship, and to Your knowledge, no other person claims, or has the right to claim, any right in any invention or patent related to the Contributions. You also represent that You are not legally obligated, whether by entering into an agreement or otherwise, in any way that conflicts with the terms of this license. For example, if you have signed an agreement requiring you to assign the intellectual property rights in the Contributions to an employer or customer, that would conflict with the terms of this license.
+5. We, as authoritative representatives of ElectricSQL determine the code that is in the Project. You understand that the decision to include Your Contribution(s) in any project or source repository is entirely that of ElectricSQL, and this agreement does not guarantee that the Contributions will be included in any product.
+
+### No Implied Warranties
+
+ElectricSQL acknowledges that, except as explicitly described in this Agreement, the Contribution is provided on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.

CODE_OF_CONDUCT.md

@@ -0,0 +1,126 @@
+
+# ElectricSQL Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+[[email protected]](mailto:[email protected]). All complaints
+will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.

CONTRIBUTING.md

@@ -0,0 +1,52 @@
+
+# Contributing to ElectricSQL
+
+Welcome to the ElectricSQL developer community. Thanks for taking the time to contribute!
+
+This guide covers two main topics:
+
+1. the [legal terms](#legal-terms) under which you contribute to the project
+2. the [guidelines](#contributor-guidelines) for how to contribute to the project
+
+## Legal terms
+
+ElectricSQL operates under the
+[default GitHub terms](https://help.github.com/en/articles/github-terms-of-service#6-contributions-under-repository-license),
+where your contributions are licensed under the terms of our
+contributor license agreement. The
+[ElectricSQL Contributor License Agreement](https://github.com/electric-sql/meta/blob/master/CLA.md) ("CLA") is a legal agreement that essentially assigns the IP in your contributions to the ElectricSQL project.
+
+### How do I accept the CLA?
+
+The **ElectricSQL repositories** are defined as any repository hosted on the GitHub platform within the [electric-sql](https://github.com/electric-sql) organisation. By contributing code to any of the ElectricSQL repositories, for example by pushing commits to GitHub and / or by raising a Pull Request, you indicate your acceptance of the CLA.
+
+<blockquote>
+  :warning: Do not contribute code to any of the ElectricSQL repositories unless you accept the ElectricSQL Contributor License Agreement. Contributing code to the ElectricSQL repositories indicates your acceptance of the terms.
+</blockquote>
+
+## Contributor Guidelines
+
+Please read the guideance below about what to do if you:
+
+- [found a bug](#did-you-find-a-bug)
+- [fixed a bug](#did-you-write-a-patch-that-fixes-a-bug)
+- [want to add a new feature or change an existing one](#do-you-intend-to-add-a-new-feature-or-change-an-existing-one)
+
+### Did you find a bug?
+
+* ensure that the bug was not already reported by searching on GitHub under the relevant issue tracker
+* if you're unable to find an open issue addressing the problem, open a new one
+
+Be sure to include a title and clear description, as much relevant information as possible, and a **code sample** or an **executable test case** demonstrating the expected behavior that is not occurring.
+
+### Did you write a patch that fixes a bug?
+
+* open a new GitHub pull request with the patch
+* ensure the PR description clearly describes the problem and solution. Include the relevant issue number if applicable
+
+### Do you intend to add a new feature or change an existing one?
+
+* say hello and suggest your change on the discussion channels for the [ElectricSQL community](https://electric-sql.com/about/community)
+* assuming you get positive feedback, raise a Pull Request against your fork/branch to track the development of the feature and discuss the implementation
+
+Then write some code ;) We welcome contributions and encourage you to pitch in :)