Hey guys,
could you pretty please take a look at PR #219 =) https://github.com/developer-portal/content/pull/219
I could use that live on Tuesday afternoon if it's possible. I will not be around to commit any fixes until Monday night though. Please, if there would be anything, email dotnet-sig@lists.fedoraproject.org (cc-ed, so a reply would suffice) and they could take a look at it.
Thanks, Radka
------------------------------ *Radka Janeková* .NET & OpenShift Engineer, Red Hat *radka.janek@redhat.com radka.janek@redhat.com* IRC: radka | Freenode: Rhea
+.NET Core is still work in progress. The download location below
contains packages that do not meet the official Fedora requirements yet (such as containing prebuilt binaries or bundled dependencies.) Please be patient, we should have reasonable packages within a few months.
I for one am excited that we have ongoing progress. What can I do to help?
I agree with the earlier comments on IRC that some of the sentences could be multiple sentences.
Sincerely,
* Kushal Dev kushaldeveloper@gmail.com [2017-07-27 19:46]:
I for one am excited that we have ongoing progress. What can I do to help?
We need to do a couple of things. The most significant is basically doing a review of .NET Core build as it stands right now, see how it compares with Fedora Packaging Guidelines, and try and fix all the issues.
Some issues that I am aware of include:
- Fixing licenses. Upstream distributes .NET Core under several licenses and the source license sometimes does not match the license generated by the build. We need to fix or remove the incorrect licenses.
- Find out which software is bundled/embedded in the current .NET Core source archive and fix that. AFAIK, only build tools are. But we need to find a way to build them separately and then fix .NET Core to build using those separately-packaged build dependencies.
Thanks, Omair
dotnet-sig@lists.fedoraproject.org