Roadmap

[ghuntley]

overview

We are in the early days of forming a community and consensus of what should (could) be worked on. Please come join the discussions at https://aka.ms/dotnet-discord (in #opendotnet). Collective ownership and the ability to change / improve anything in the .NET tooling and developer experience ala to Own Your Own Future when it comes to your toolchain is a potential central northstar.

See also #47

The pinned items on top of the GitHub repository are a suggested starting position and if you desire to help out then starting to obtaining domain knowledge needed to achieve tasks such as #45 helps so much.

discussions

From Ani:

I think that the central Truism to focus around is, "What is getting in the way of writing production-scale .NET apps using solely open-source tools". Like, having a forked build of every .NET package seems like it is a V2 Thing
So toward that end, I would say your list is, in order of priority:

1. Build an open source debugger for dotnet.
2. Improve omnisharp/C# in vscode experience
   ....
3. Maybe replace NuGet?

tbh I'd put that last one low on my list, because like, what you really want out of this initiative is the ability to change / improve anything about your tooling and developer experience - to Own Your Own Future when it comes to your toolchain, and NuGet from a developer perspective is really just like a fancy S3 bucket. Yeah, it's owned by someone else but like who cares

From Yair Halberstadt

Can I make a suggestion?

At the moment I feel like you're doing a lot of things and are very vague about your plans for all of them. At the moment you have a lot of community interest and attention, but that going to wane soon. You're very excited about this project, and that's great but if you want to keep it going for the long term you have to focus all this passion and attention to something concrete.

So I would advise picking one thing, and doing it really well. If that works you can branch out from there. So for example pick one of these, and focus almost entirely on it:

1. Have a community built version of the dotnet sdk with key differentiator (e.g. telemitry disabled), and automatically in sync with core dotnet.
2. Improve omnisharp/C# in vscode experience.
3. Build an open source debugger for dotnet.
4. Experiments with replacing MSBuild
5. Experiments with replacing Nuget

But pick one and stick to it, and for now don't even mention any of the others - they're just a distraction. Or simply act as a Community advocacy organization for dotnet, where you don't build anything at all, but act as whistleblowers for things you feel MS is doing wrong, and provide assistance to people trying to change things in dotnet, or simply help drive forward community contributers.