Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[New Topic] Current state of development tools #3446

Closed
ShalokShalom opened this issue Oct 17, 2017 · 13 comments
Closed

[New Topic] Current state of development tools #3446

ShalokShalom opened this issue Oct 17, 2017 · 13 comments
Labels
discussion Indicates issues that are being discussed Pri3 support-request Support-style question;customer needs help solving a problem [org][type][category] won't fix Issues that were closed as part of automated backlog grooming
Milestone

Comments

@ShalokShalom
Copy link
Contributor

ShalokShalom commented Oct 17, 2017

[Idea] A sheet which shows all the available compilers, runtimes and frameworks including the support for the different languages and platforms, including notation of the licenses, maintainers and blocking issues.

[Edit] So, something like this:

screenshot_20171018_140341

I think this is important to get a simple overview.

@enricosada
Copy link
Contributor

enricosada commented Oct 18, 2017

So, you pratically want the link to github projects for each component? there you can see releases, notes, issue open and closed, docs, etc

=> https://github.com/dotnet/core/blob/master/Documentation/core-repos.md

and https://github.com/dotnet/core/blob/master/release-notes/download-archive.md

You can start navigate docs from the readme of https://github.com/dotnet/core

@charlesroddie
Copy link

I think this is a good idea. Suggest putting an .md file similar to what you have a screenshot of on your own github where people can submit changes. Here it would require some group to approve it.

@hsorbo
Copy link

hsorbo commented Oct 18, 2017

Its a good mixture of different stuff in that list. Perhaps it would be clearer if you further group them into Runtimes, Compilers, Frameworks etc?

@ShalokShalom
Copy link
Contributor Author

Perhaps it would be clearer if you further group them into Runtimes, Compilers, Frameworks etc?

Yes, exactly this is my plan. To be honest: I am fresh to this whole infrastructure, so my information is based on a lot of opinions and some kind of half official statements.

This is why I hope for some contributions by deeply involved community members.

Suggest putting an .md file similar to what you have a screenshot of on your own github where people can submit changes. Here it would require some group to approve it.

I like to get it on the official documentation anyway. Currently, this is a .ods and I can port it to something compatible. Is there a template for something?

@BillWagner BillWagner added discussion Indicates issues that are being discussed question labels Oct 23, 2017
@BillWagner
Copy link
Member

I'm waiting to assign this to a milestone for a couple reasons.

First, this is a great discussion, and I want to coalesce around what information should be in this topic.

Second, do you expect version information here as well? And, if so, to what detail (major version, minor version, build)?

@ShalokShalom
Copy link
Contributor Author

ShalokShalom commented Oct 24, 2017

Well, I think one fundamental question is, how we like to maintain this table.

Which is why I left 'current blockers' and such stuff out for now.
I also like to include links to the roadmap and active communitys.

So a full overview over the complete ecosystem.

To be honest:

This is something important in my sense while I see this as the job of somebody who is deeply involved.

So, two solutions:

a) Somebody maintains all this mutable stuff.
b) This list stays immutable.

Of course is it nice to present the whole thing in a manner that is super helpful.

@ShalokShalom
Copy link
Contributor Author

ShalokShalom commented Oct 24, 2017

@enricosada

I do not see the whole range of available products in Github.
To start with, since they are spread on several repos.

I do not see the current usability state of these products on Github.

I also cant see, which of the other products are working well with specific products.
So .NET Native is running usable on C# while not yet on F#, yes?

How to see this on Github?

@mairaw
Copy link
Contributor

mairaw commented Nov 7, 2017

@richlander any thoughts on this?

@mairaw mairaw added this to the Backlog milestone Nov 7, 2017
@ShalokShalom
Copy link
Contributor Author

ShalokShalom commented Nov 24, 2017

I will upload the file for now:

ComparsionSheetMSdevtools.xlsx

@ShalokShalom
Copy link
Contributor Author

Who feels responsible here?

@ShalokShalom
Copy link
Contributor Author

@ShalokShalom
Copy link
Contributor Author

Why is it impossible to one of the largest companies in the world, to implement such a fundamental thing, while there is even an open source contribution which simply can get adopted?

@Thraka Thraka added support-request Support-style question;customer needs help solving a problem [org][type][category] and removed support-request Support-style question;customer needs help solving a problem [org][type][category] question labels Jun 10, 2019
@dotnet-bot dotnet-bot added the won't fix Issues that were closed as part of automated backlog grooming label Jan 25, 2021
@dotnet-bot
Copy link
Contributor

This issue has been closed as part of the issue backlog grooming process outlined in #22351.

That automated process may have closed some issues that should be addressed. If you think this is one of them, reopen it with a comment explaining why. Tag the @dotnet/docs team for visibility.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion Indicates issues that are being discussed Pri3 support-request Support-style question;customer needs help solving a problem [org][type][category] won't fix Issues that were closed as part of automated backlog grooming
Projects
None yet
Development

No branches or pull requests

9 participants