admin/milvus
1
0
Fork 0
mirror of https://gitee.com/milvus-io/milvus.git synced 2025-12-28 22:45:26 +08:00
Code Issues Packages Projects Releases Wiki Activity

[skip ci]Remove outdated files (#5885)

Browse Source 
Signed-off-by: Xiangyu Wang <xiangyu.wang@zilliz.com>
This commit is contained in:
Xiangyu Wang 2021-06-21 11:26:08 +08:00 committed by GitHub
parent d9b5c13e9c
commit e51bba5143
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
5 changed files with 0 additions and 167 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

99
COMMUNITY.md
View File

@ -1,99 +0,0 @@
# 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)

13
DESIGN.md
View File

@ -1,13 +0,0 @@
# 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)

24
NOTICE.md
View File

@ -1,24 +0,0 @@
| Name | License |
| ---------------- | -------------------------------------------------------------------------------------------------------------------------------|
| Boost | [Boost Software License](https://github.com/boostorg/boost/blob/master/LICENSE_1_0.txt) |
| FAISS | [MIT](https://github.com/facebookresearch/faiss/blob/master/LICENSE) |
| Gtest | [BSD 3-Clause](https://github.com/google/googletest/blob/master/LICENSE) |
| LAPACK | [LAPACK](https://github.com/Reference-LAPACK/lapack/blob/master/LICENSE) |
| MySQLPP | [LGPL 2.1](https://tangentsoft.com/mysqlpp/artifact/b128a66dab867923) |
| OpenBLAS | [BSD 3-Clause](https://github.com/xianyi/OpenBLAS/blob/develop/LICENSE) |
| Prometheus | [Apache 2.0](https://github.com/prometheus/prometheus/blob/master/LICENSE) |
| SQLite | [Public Domain](https://www.sqlite.org/copyright.html) |
| SQLite-ORM | [BSD 3-Clause](https://github.com/fnc12/sqlite_orm/blob/master/LICENSE) |
| yaml-cpp | [MIT](https://github.com/jbeder/yaml-cpp/blob/master/LICENSE) |
| ZLIB | [ZLIB](http://zlib.net/zlib_license.html) |
| libunwind | [MIT](https://github.com/libunwind/libunwind/blob/master/LICENSE) |
| gperftools | [BSD 3-Clause](https://github.com/gperftools/gperftools/blob/master/COPYING) |
| grpc | [Apache 2.0](https://github.com/grpc/grpc/blob/master/LICENSE) |
| EASYLOGGINGPP | [MIT](https://github.com/zuhd-org/easyloggingpp/blob/master/LICENSE) |
| Json | [MIT](https://github.com/nlohmann/json/blob/develop/LICENSE.MIT) |
| opentracing-cpp | [Apache 2.0](https://github.com/opentracing/opentracing-cpp/blob/master/LICENSE) |
| libfiu | [BOLA](https://github.com/albertito/libfiu/blob/master/LICENSE) |
| aws-sdk-cpp | [Apache 2.0](https://github.com/aws/aws-sdk-cpp/blob/master/LICENSE) |
| SPTAG | [MIT](https://github.com/microsoft/SPTAG/blob/master/LICENSE) |
| hnswlib | [Apache 2.0](https://github.com/nmslib/hnswlib/blob/master/LICENSE) |
| annoy | [Apache 2.0](https://github.com/spotify/annoy/blob/master/LICENSE) |

17
RELEASE.md
View File

@ -1,17 +0,0 @@
# Milvus Release Methodology and Criterias
## Release methodology
Milvus releases are packages that have been approved for general public release, with varying degrees of caveat regarding their perceived quality or potential for change.
They are stable releases intended for everyday usage by developers and non-developers.
Project versioning follows the specification of [Semantic Versioning 2.0.0](https://semver.org/).
## Release criteria
- Milvus core test code coverage must be at least 90%.
- Reported bugs should not have any critical issues.
- All bugs, new features, enhancements must be tested.
- All documents need to be reviewed with no broken link.
- Pressure testing, stability testing, accuracy testing and performance testing results should be evaluated.

14
SUPPORT.md
View File

@ -1,14 +0,0 @@
# Support for deploying and using Milvus
We use GitHub for tracking bugs and feature requests. If you need any support for using Milvus, please refer to the following resources below.
## Documentation
- [User Documentation](https://www.milvus.io/docs/install_milvus.md)
- [Troubleshooting Guide](https://www.milvus.io/docs/troubleshoot.md)
- [FAQ](https://www.milvus.io/docs/operational_faq.md)
## Real-time chat
[Slack](https://join.slack.com/t/milvusio/shared_invite/enQtNzY1OTQ0NDI3NjMzLWNmYmM1NmNjOTQ5MGI5NDhhYmRhMGU5M2NhNzhhMDMzY2MzNDdlYjM5ODQ5MmE3ODFlYzU3YjJkNmVlNDQ2ZTk): The #general channel is the place where people offer support.
## Other
[Bootcamp](https://github.com/milvus-io/bootcamp): It provides more scenario-based applications and demos of Milvus.