Azure / Azure/elastic-db-tools
Proposal: Transition to .NET Foundation
- Dominant language
- C#
- Stars
- 147
- Forks
- 108
- PR merge metrics
- No merged PRs in 30d
Description
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).
Contributor guide
No contributing guide indexed for this repository
Research direction
The proposal names no source files, tests, or entry points to inspect. Start by reviewing the repository status and the project's current stewardship information, then determine whether maintainers or the .NET Foundation have provided a decision; done would require an agreed transition plan, not a code change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100