In community/issues/118, @tison requested to reduce the entropy of TiKV community governance by associate every repository with one and only one project. For one project, there are many repositories, for example, the repositories in TiKV project are:
tikv client-c client-py client-go client-java client-rust client-cpp agatedb async-speed-limit bytes client-validator copr-test crc64fast crossbeam fail-rs grpc-rs importer jemalloc jemallocator minitrace-go minitrace-rust minstant mock-tikv mur3 pprof-rs procinfo-rs protobuf-build raft-engine rocksdb rusoto rust-prometheus rust-rocksdb sig-transaction sysinfo terraform-tikv-bench tikv-operator tikv.github.io titan tlaplus-specs website yatp
At present, every repository has its own place to track issues in their github repository, for example:
- client-java: https://github.com/tikv/client-java/issues
- client-rust: https://github.com/tikv/client-rust/issues
- client-cpp: https://github.com/tikv/client-cpp/issues
It’s too hard for us to maintain all these issues in so many individual repositories. I propose to close all issue functions on these repositories and only allow to open issues on the tikv repository.