Update README

CODE_OF_CONDUCT.md

@@ -0,0 +1,48 @@
+# Milvus Code of Conduct
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+-   Using welcoming and inclusive language.
+-   Being respectful of differing viewpoints and experiences.
+-   Gracefully accepting constructive criticism.
+-   Focusing on what is best for the community.
+-   Showing empathy towards other community members.
+
+Examples of unacceptable behavior by participants include:
+
+-   The use of sexualized language or imagery and unwelcome sexual attention or advances.
+-   Trolling, insulting/derogatory comments, and personal or political attacks.
+-   Public or private harassment.
+-   Publishing others' private information, such as a physical or electronic address, without explicit permission.
+-   Conduct which could reasonably be considered inappropriate for the forum in which it occurs.
+
+All Milvus forums and spaces are meant for professional interactions, and any behavior which could reasonably be considered inappropriate in a professional setting is unacceptable.
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers 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, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies to all content on milvus.io, Milvus’s GitHub organization, or any other official Milvus web presence allowing for community interactions, as well as at all official Milvus events, whether offline or online.
+
+The Code of Conduct also applies within all project spaces and in public spaces whenever an individual is representing Milvus or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed or de facto representative at an online or offline event. Representation of Milvus may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [email protected]. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org/), version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+For answers to common questions about this code of conduct, see https://www.contributor-covenant.org/faq
+

COMMUNITY.md

@@ -0,0 +1,99 @@
+# Community Roles
+
+<!-- TOC -->
+
+-   [TSC Members](#tsc-members)
+-   [Committers](#committers)
+-   [Reviewers](#reviewers)
+-   [Contributors](#contributors)
+
+<!-- /TOC -->
+
+## TSC Members
+
+The Technical Steering Committee (TSC) functions as the core management team that oversees the Milvus community. The TSC decides the roadmap of the project and makes major decisions related to the community.
+
+TSC members have the following responsibilities:
+
+-   Coordinate the technical direction of the project.
+-   Approve project or system proposals.
+-   Decide on formal releases of the project's software.
+-   Organize and remove sub-projects.
+-   Coordinate any marketing, events, or communications regarding the project.
+
+To become a TSC member, a committer must be sponsored by a TSC member and the sponsorship must be approved by 2/3 of all TSC members.
+
+The TSC members are listed below:
+
+-   [cxie](https://github.com/cxie)
+-   [JinHai-CN](https://github.com/JinHai-CN)
+
+## Committers
+
+Committers lead project feature discussions and oversee the overall project quality.
+
+Committers have the following responsibilities:
+
+-   Lead feature design discussions and implementation.
+-   Ensure the overall project quality and approve PRs.
+-   Participate in product release, feature planning, and roadmap design.
+-   Have a constructive and friendly attitude in all community interactions.
+-   Mentor reviewers and contributors.
+
+To become a committer, a reviewer must have contributed broadly throughout the Milvus project. A reviewer must also be sponsored by a committer and the sponsorship must be approved by the TSC.
+
+The committers are listed below:
+
+-   [JinHai-CN](https://github.com/JinHai-CN)
+
+## Reviewers
+
+Reviewers review new code contributions and ensure the quality of existing code.
+
+Reviewers have the following responsibilities:
+
+-   Participate in feature design discussion and implementation.
+-   Ensure the quality of owned code modules.
+-   Ensure the technical accuracy of documentation.
+-   Quickly respond to issues and PRs and conduct code reviews.
+
+To become a reviewer, a contributor must have provided continued and quality contribution to the Milvus project for at least 6 months and have contributed at least one major component where the contributor has taken an ownership role.
+
+The reviewers are listed below:
+
+-   [XuPeng-SH](https://github.com/XuPeng-SH)
+-   [yhmo](https://github.com/yhmo)
+-   [scsven](https://github.com/scsven)
+-   [cydrain](https://github.com/cydrain)
+-   [shengjun1985](https://github.com/shengjun1985)
+
+## Contributors
+
+Contributors can be anyone who has successfully submitted at least one PR to the Milvus project.
+
+The contributors are listed below:
+
+-   [ZhifengZhang-CN](https://github.com/ZhifengZhang-CN)
+-   [tinkerlin](https://github.com/tinkerlin)
+-   [youny626](https://github.com/youny626)
+-   [fishpenguin](https://github.com/fishpenguin)
+-   [BossZou](https://github.com/BossZou)
+-   [del-zhenwu](https://github.com/del-zhenwu)
+-   [jielinxu](https://github.com/jielinxu)
+-   [yamasite](https://github.com/yamasite)
+-   [Yukikaze-CZR](https://github.com/Yukikaze-CZR)
+-   [Heisenberg-Y](https://github.com/Heisenberg-Y)
+-   [sahuang](https://github.com/sahuang)
+-   [op-hunter](https://github.com/op-hunter)
+-   [GuanyunFeng](https://github.com/GuanyunFeng)
+-   [thywdy](https://github.com/thywdy)
+-   [erdustiggen](https://github.com/erdustiggen)
+-   [akihoni](https://github.com/akihoni)
+-   [shiyu22](https://github.com/shiyu22)
+-   [shengjh](https://github.com/shengjh)
+-   [dvzubarev](https://github.com/dvzubarev)
+-   [aaronjin2010](https://github.com/aaronjin2010)
+-   [ReigenAraka](https://github.com/ReigenAraka)
+-   [JackLCL](https://github.com/JackLCL)
+-   [Bennu-Li](https://github.com/Bennu-Li)
+-   [ABNER-1](https://github.com/ABNER-1)

CONTRIBUTING.md

@@ -0,0 +1,128 @@
+# Contributing to Milvus
+
+Contributions to Milvus are welcome from everyone. We strive to make the contribution process simple and straightforward. Up-to-date information can be found at [milvus.io](https://milvus.io/).
+
+The following are a set of guidelines for contributing to Milvus. Following these guidelines makes contributing to this project easy and transparent. These are mostly guidelines, not rules. Use your best judgment, and feel free to propose changes to this document in a pull request.
+
+As for everything else in the project, the contributions to Milvus are governed by our [Code of Conduct](CODE_OF_CONDUCT.md).
+
+
+## What contributions can I make?
+
+Contributions to Milvus fall into the following categories.
+
+1.  To report a bug or a problem with documentation, please file an [issue](https://github.com/milvus-io/milvus/issues/new/choose) providing the details of the problem. If you believe that the issue needs priority attention, please comment on the issue to notify the team.
+2.  To propose a new feature, please file a new feature request [issue](https://github.com/milvus-io/milvus/issues/new/choose). Describe the intended feature and discuss the design and implementation with the team and community. Once the team agrees on the plan, you can follow the [Contributing code](CONTRIBUTING.md#contributing-code) to implement it.
+3.  To implement a feature or bug-fix for an existing outstanding issue, follow the [Contributing code](CONTRIBUTING.md#contributing-code). If you need more context on a particular issue, comment on the issue to let people know.
+
+## How can I contribute?
+
+### Contributing code
+
+If you have improvements to Milvus, send us your pull requests! For those just getting started, see [GitHub workflow](#github-workflow). Make sure to refer to the related issue in the ccomment of your pull request and update [CHANGELOG.md](CHANGELOG.md).
+
+All submissions will be reviewed as quickly as possible. Once it is accepted, the status of the project to which it is associated will be changed to **Reviewer approved**. This means we are working on submitting your pull request to the internal repository. After the change has been submitted internally, your pull request will be merged automatically on GitHub.
+
+### GitHub workflow
+
+Generally, we follow the "fork-and-pull" Git workflow.
+
+1.  [Fork](https://docs.github.com/en/github/getting-started-with-github/fork-a-repo) the repository on GitHub.
+2.  Clone your fork to your local machine with `git clone [email protected]:<yourname>/milvus.git`.
+3.  Create a branch with `git checkout -b my-topic-branch`.
+4.  [Commit](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork) changes to your own branch, then push to to GitHub with `git push --set-upstream origin my-topic-branch`. You must record your changes in [CHANGELOG.md](CHANGELOG.md) with issue numbers and descriptions.
+5.  Submit a [pull request](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/about-pull-requests) so that we can review your changes.
+
+Remember to [sync your forked repository](https://docs.github.com/en/github/getting-started-with-github/fork-a-repo#keep-your-fork-synced) *before* submitting proposed changes upstream. If you have an existing local repository, please update it before you start, to minimize the chance of merge conflicts.
+
+```shell
+git remote add upstream [email protected]:milvus-io/milvus.git
+git checkout master
+git pull upstream master
+git checkout -b my-topic-branch
+```
+
+### General guidelines
+
+Before submitting your pull requests for review, make sure that your changes are consistent with the [coding style](CONTRIBUTING.md#coding-style), and run [unit tests](CONTRIBUTING.md#run-unit-test-with-code-coverage) to check your code coverage rate.
+
+-   Include unit tests when you contribute new features, as they help to prove that your code works correctly, and also guard against future breaking changes to lower the maintenance cost.
+-   Bug fixes also require unit tests, because the presence of bugs usually indicates insufficient test coverage.
+-   Keep API compatibility in mind when you change code in Milvus. Reviewers of your pull request will comment on any API compatibility issues.
+-   When you contribute a new feature to Milvus, the maintenance burden is (by default) transferred to the Milvus team. This means that the benefit of the contribution must be compared against the cost of maintaining the feature.
+
+### Developer Certificate of Origin (DCO)
+
+All contributions to this project must be accompanied by acknowledgment of, and agreement to, the [Developer Certificate of Origin](https://developercertificate.org/). Acknowledgment of and agreement to the Developer Certificate of Origin _must_ be included in the comment section of each contribution and _must_ take the form of `Signed-off-by: {{Full Name}} <{{email address}}>` (without the `{}`). Contributions without this acknowledgment will be required to add it before being accepted. If contributors are unable or unwilling to agree to the Developer Certificate of Origin, their contribution will not be included.
+
+Contributors sign-off that they adhere to DCO by adding the following Signed-off-by line to commit messages:
+
+```text
+This is my commit message
+
+Signed-off-by: Random J Developer <[email protected]>
+```
+
+Git also has a `-s` command line option to append this automatically to your commit message:
+
+```shell
+$ git commit -s -m 'This is my commit message'
+```
+
+## Coding Style
+The coding style used in Milvus generally follow [Google C++ Style Guide](https://google.github.io/styleguide/cppguide.html).
+And we made the following changes based on the guide:
+
+-   4 spaces for indentation
+-   Adopt .cpp file extension instead of .cc extension
+-   120-character line length
+-   Camel-Cased file names
+
+### Format code
+
+Install clang-format
+```shell
+$ sudo apt-get install clang-format
+$ rm cmake_build/CMakeCache.txt
+```
+Check code style
+```shell
+$ ./build.sh -l
+```
+To format the code
+```shell
+$ cd cmake_build
+$ make clang-format
+```
+
+## Run unit test with code coverage
+
+Before submitting your Pull Request, make sure you have run unit test, and your code coverage rate is >= 90%.
+
+Install lcov
+```shell
+$ sudo apt-get install lcov
+```
+Run unit test and generate code for code coverage check
+```shell 
+$ ./build.sh -u -c
+```
+
+Run MySQL docker
+```shell 
+docker pull mysql:latest
+docker run -p 3306:3306 -e MYSQL_ROOT_PASSWORD=123456 -d mysql:latest
+```
+
+Run code coverage
+
+```shell  
+$ ./coverage.sh -u root -p 123456 -t 127.0.0.1
+```
+
+Or start your own MySQL server, and then run code coverage
+
+```shell
+$ ./coverage.sh -u ${MYSQL_USERNAME} -p ${MYSQL_PASSWORD} -t ${MYSQL_SERVER_IP}
+```
+

DESIGN.md

@@ -0,0 +1,13 @@
+# Milvus Design Documents
+
+If you would like to propose a new feature for Milvus, it is recommended that you submit a design document following the [design document template](https://docs.google.com/document/d/1KhWs9b53K6WQUZ_FGWhIaeTraaSqsLQF7v2v68sAh_c/edit?usp=sharing).
+
+The following list contains existing design documents for Milvus.
+
+-   [Support DSL interface](https://docs.google.com/document/d/1U83LY36TyaG3WD67Q9HWg9saD3qQcz9BfMcEScgwQPM/edit?usp=sharing)
+-   [Support delete/search by ID, attribute filtering, ID de-duplication](https://docs.google.com/document/d/1CDKdTj_DnE90YaZrPgsMaphqOTkMdbKETNrsFKj_Bco/edit?usp=sharing)
+-   [Support write-ahead logging](https://docs.google.com/document/d/12N8RC_wJb2dvEKY9jrlh8hU_eH8jxQVBewoPuHNqcXE/edit?usp=sharing)
+-   [Support in-service config modification](https://docs.google.com/document/d/1pK1joWJgAHM5nVp3q005iLbLqU5bn9InWeBy0mRAoSg/edit?usp=sharing)
+-   [Support Multi-Storage](https://docs.google.com/document/d/1iwwLH4Jtm3OXIVb7jFYsfmcbOyX6AWZKaNJAaXC7-cw/edit?usp=sharing)
+-   [Support AVX-512](https://docs.google.com/document/d/1do6_JgRCYdcV95sTPE6rLoiBK8wAcZki5Ypp7jbgqK0/edit?usp=sharing)
+-   [Refactor Knowhere](https://docs.google.com/document/d/1HY27EXV4UjJhDEmJ9t4Rjh7I1sB8iJHvqvliM6HHLS8/edit?usp=sharing)