Modernize torchsharp infrastructure
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- csharp
- Domain
- build-system, ci-cd, release
Research direction
Start with the linked pkg/pack.proj and review the existing YML, local build scripts, CProj, nupkgproj, and SLN setup. Compare the build and packaging structure with the listed Arcade, Microsoft.Build.NoTargets, and dotnet/runtime conventions. Done means the checklist is addressed across the build, project, package, and readme configuration.
Written by the indexing model from the issue text.
Description
In looking at Torchsharp's build I had a few thoughts for improvement.
- Evaluate using arcade and provided build templates.
- Remove as much as possible from the YML and have it be part of the local build scripts so that it's easier to repro things that are hit by the official build.
- Remove use of the
nupkgprojand instead pack from the CProj projects where possible - For the remaining
nupkgprojhave them use the Microsf.Build.NoTargets SDK to avoid C# specific targets. - Add all projects to the SLN, and control the pack behavior with
IsPackableconditions rather than conditions in a project https://github.com/dotnet/TorchSharp/blob/077780db89bfc7671af6262ed817e30cb14cf4d3/pkg/pack.proj#L4 - Adopt package readme's following a similar convention to dotnet\runtime.
- Dominant language
- C#
- Stars
- 1.9k
- Forks
- 228
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dotnet/TorchSharp
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 56/100
dotnet/TorchSharp#1574 ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
dotnet/TorchSharp#1567 ·
-
question
Difficulty 5/5 Over a week Newbie friendliness 25/100
dotnet/TorchSharp#1557 ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 45/100
dotnet/TorchSharp#1545 · 1 reaction ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 42/100
dotnet/TorchSharp#1541 ·
All issues in dotnet/TorchSharp
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
t/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
ci-failure-cause test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:auth FE mvp P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
klasolsson81/jobbliggaren#1788 ·