Please throw in ideas of what do you think that should be on the C# page https://developer.fedoraproject.org/tech/languages/csharp/mono-installation.html
One option is to have generic C# page, which will talk about different IDEs, and then branch out to .net core and mono resources / sub-pages, my proposed structure:
Anything else, any other ideas? Containers/openshift stuff maybe, can anyone explore this topic?
Metadata Update from @rhea: - Issue assigned to rhea
Metadata Update from @rhea: - Issue tagged with: meeting
Metadata Update from @rhea: - Issue tagged with: admin
What about running behind Docker/Kubernetes ?
@amitosh , What is exactly the idea? generate a image or a Dockerfile + instructions?
The mono page could use a little bit more info about actual usage, very basic xbuild and mono usage, reference, etc... I've added .net framework api reference links.
xbuild
mono
GitHub fork Please if you have any changes, commit to our github fork, so we don't PR multiple times. I'll PR it when the time comes. https://github.com/Fedora-dotnet/developer-portal-content
Copr repos related to mono stack.
A bit of a philosophical question: should developer.fedoraproject.org recommend projects that are:
I took a quick look at most of the pages under https://developer.fedoraproject.org/tech.html. Every single tool I saw being used/recommended was part of Fedora. Some language pages explained how to fetch upstream libraries, but that was only so users could use them for building their applications. I guess the equivalent for us would be showing examples of nuget packages. The Java page doesn't mention Intellij IDEA, for example. I did see mongodb pages point to a non-Fedora repository, but it contains packages licensed under AGPL.
Should we point users to non-Fedora and/or proprietary tools such as Visual Studio Code (https://code.visualstudio.com/License/) or .NET Core releases (https://www.microsoft.com/net/dotnet_library_license.htm) or Rider?
A bit of a philosophical question: should developer.fedoraproject.org recommend projects that are: Not part of Fedora Not Open Source
A bit of a philosophical answer: Yes it should, by all means, give people all the options with disclaimers and let them choose.
Realistic answer: I've no idea if it's allowed to do "by fedora." If it's not, I'll fite 'em This is very new project and it's work in progress, I'm gonna hope that we will be able to shove as much of it into fedora repos as possible (of course doesn't apply to rider)
Metadata Update from @rhea: - Issue untagged with: meeting
I've written a dotnet-usage doc containing the commonly used commands of dotnet core, their syntaxes, and the arguments that each command takes.
The developer portal is in good state now, but improvements can be made.
WIP most of this is nicely done, but we could still come up with something about ASP.NET Core
Metadata Update from @rhea: - Issue assigned to rhea - Issue tagged with: admin
Log in to comment on this ticket.