JuliaGraphs / JuliaGraphs/Graphs.jl
Move code from GraphFlows and GraphsMatching to GraphsOptim
Open
Nobody has claimed this yet.
enhancement
help wanted
- Dominant language
- Julia
- Stars
- 538
- Forks
- 128
- Avg merge
- 10h 25m
- Merged PRs (30d)
- 2
Description
As discussed on slack, it is annoying to have GraphFlows.jl and GraphsMatching.jl as separate packages. We should see what we can bring back to Graph.jl and maybe create a package with the more complex problems that need JuMP as a dependency.
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.
Research direction
Start by comparing the contents and APIs of GraphFlows.jl, GraphsMatching.jl, and Graph.jl, noting which functionality could return to Graph.jl and which complex problems require JuMP. The issue is done when the package split and destination of the relevant functionality are clearly decided and documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- data
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100