Illustration for hierarchy of TuringLang repos
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 238
- Forks
- 107
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 2
Description
In the TuringLang organisation we have lots of repos.
Which of them depend on which of them?
It would be nice to have an illustrated dependency graph that shows how they are all related, e.g.
Turing ──────┐
│ │ │
│ │ │
MCMCChains ◄────┘ │ │
▲ │ │
│ │ │
│ ▼ │
└─ext──DynamicPPL │
│ │ │
│ │ │
│ │ ▼
│ └───────► AbstractMCMC
▼
Bijectors
I think fundamentally this would boil down to parsing TOML files, although this might is a bit tricky to get right since we also have package extensions which would probably require a different type of arrow.
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
Begin by inventorying the TuringLang repositories and the TOML files that describe their dependencies. Determine how package extensions should be represented, then produce an illustrated graph showing repository relationships and distinguishing extension arrows.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- data-visualization, documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100