Proposal to mark etcd-io/dbtester as public archive

[jmhbnz]

Sub issue under etcd-io/etcd#16367.

This etcd sub-project has been inactive for a significant period, with the last meaningful activity occurring in 2018. Given the lack of recent contributions, I propose marking this repository as a public archive.

This action would clearly communicate to the community that the project is no longer actively maintained.

Reasoning:

1. Inactivity: The repository has not seen any substantial activity for the past five years.

2. Clarity: Marking the repository as a public archive would provide clarity to users and potential contributors. It indicates that the project is in a dormant state and that any forks or contributions would likely not be integrated.

3. Resource Allocation: Keeping inactive repositories in the active organization may create confusion and require unnecessary resource allocation responding to issues etc.

Next steps

I kindly request @etcd-io/maintainers-etcd and previous main subproject contributor @gyuho review the proposal and please provide feedback.

[serathius]

Here I'm on a fence, the repo is related to etcd-io/etcd#16467, a lost knowledge on how previous maintainers qualified previous releases. I could not reach out to @gyuho, but I expect could be one of the missing pieces. It would be great if we could evaluate this project as part of etcd-io/etcd#16467.

On the other hand, we can always archive it now, and unarchive it later.

[jmhbnz]

Here I'm on a fence, the repo is related to etcd-io/etcd#16467, a lost knowledge on how previous maintainers qualified previous releases. I could not reach out to @gyuho, but I expect could be one of the missing pieces. It would be great if we could evaluate this project as part of etcd-io/etcd#16467.

On the other hand, we can always archive it now, and unarchive it later.

Thanks @serathius, yes I was also of two minds for this repo which is why I took a few days longer to open this issue compared to the other archival proposals.

What it came down to for me is I believe we should be reviewing this code as part of what we develop for etcd-io/etcd#16467 but I was leaning towards our new solution living as part of our main etcd-io/etcd repo which would mean it is probably still reasonable to mark this as public archive.

Happy to change approach and just add the OWNERS file here instead of archiving if we think we will be putting our new benchmarking code here rather than in the main repo, curious to hear what everyone thinks 🙏🏻