vigouredelaruse
commented
1 year ago a worthy suggestion given the timeseries datapoints pertinent to this repo
however i believe you may want to consult the link below and make a case to the provided email directly https://opensource.microsoft.com/codeofconduct/faq/
as not your attourney i suggest
- that the mitigation you suggest adds another bureaucracy with potentially debilitative decision execution times to the nominal critical path
- that this client library is associated with closed source infrastructure whose owers retain freedom to make opaque and arbitrary decisions regarding the entire software stack and the associated infrastructure, and are evidently doing so now
- the conduct of the repo's contributors may well be in line with the aforementioned arbitrary opacity
best regards
I'd like to propose that this project joins the .NET Foundation and is transitioned to community stewardship. The reason for asking that is many out there still use this library and would like to see it gently advanced, like Microsoft.Data.SqlClient or .NET 6.0 - no major feature work is expected, just an active community that fixes the odd bug going forward.
As is, this repo is dead. In a bad way. By not telling anyone its status, not allowing a clear way forward (except the odd fork that itself dies off, just like https://www.nuget.org/packages/ElasticScaleCore.Client).