JuliaLang/julia
The Julia Programming Language
In plain words
Outside PRs: 6 in 10 merged. First reply usually within 16 h. 2 starter issues are available now. Replies got faster this month.
Outside PRs merged
64%
49 merged, 28 closed, 43 still open
Higher than 19% of 565 other measured repositories
First human reply
16 h
median of 120 outside PRs, 20 unanswered
Time to merge
Not enough data
49 of 120 outside PRs merged
Outside PRs opened 30 to 120 days ago, so each has had time to be answered. A figure needs at least 5 pull requests, otherwise it reads "Not enough data". How this is calculated · A number looks wrong?
Your first steps here
If you have never contributed to this project, do these in order.
- 1
Read the contributing guide
It says how to set the project up and what the maintainers expect in a pull request.
Open the guide - 2
Take this free issue
Core.bitcast to LLVMPtr from Float64 generates invalid inttoptr, aborts compilation
Open issue #63218 - 3
Know where to ask
Questions go to the project's zulip, or on the issue itself. Not in private messages.
Open it - 4
Open a small pull request
Link the issue in it. A first reply here usually takes 16 h; until then, silence is normal.
What happens to an outside pull request
Every pull request opened by someone outside the core team, 30 to 120 days ago.
- Opened by outsiders120100%
- Got a human reply10083%
- Merged4941%
Time to first reply
After 2 days, 57% of outside PRs had a reply from a person. After a week, 62%. Bots do not count.
The last 52 weeks
Got faster. Median first reply was 7 h over the last four weeks (65 PRs) and 19 h over the four before (48 PRs).
Starter issues
Issues labelled for beginners, with their real state. Available means open, unassigned, no linked pull request, nobody has claimed it in the last 14 days, and it was updated in the last 60 days.
- Available
- 2
- Claimed
- 1
- Has a pull request
- 30
- Stale
- 21
- AvailableCore.bitcast to LLVMPtr from Float64 generates invalid inttoptr, aborts compilation#63218
- Has a pull request"@inferred requires a call expression" for do notation#59114
- Has a pull request`EACCES` when checking `islink` for symbolic link on Windows#58870
When replies arrive
All maintainers counted together. Shown only when at least 3 people replied in the last 90 days, so it never describes one person.
Replies are most likely between 00:00 and 03:00 (India time).
Show as table
| Hour (India time) | Replies, all weekdays |
|---|---|
| 00:00 | 134 |
| 01:00 | 163 |
| 02:00 | 148 |
| 03:00 | 102 |
| 04:00 | 64 |
| 05:00 | 72 |
| 06:00 | 77 |
| 07:00 | 59 |
| 08:00 | 54 |
| 09:00 | 38 |
| 10:00 | 31 |
| 11:00 | 36 |
| 12:00 | 42 |
| 13:00 | 45 |
| 14:00 | 48 |
| 15:00 | 61 |
| 16:00 | 80 |
| 17:00 | 93 |
| 18:00 | 115 |
| 19:00 | 138 |
| 20:00 | 138 |
| 21:00 | 136 |
| 22:00 | 139 |
| 23:00 | 128 |
How to start
Stack
Badge and feed
Two ways to use these figures outside this page.
For maintainers: a README badge
Shows newcomers how quickly this project answers and how often it merges. Paste the line into your README; the badge updates with the index.
[](https://contributable.vercel.app/repo/JuliaLang/julia)[](https://contributable.vercel.app/repo/JuliaLang/julia)For contributors: follow new issues
Add the feed to a feed reader (Feedly, Inoreader, Thunderbird) and you hear about new free starter issues here without checking the site.
https://contributable.vercel.app/feed/repo/JuliaLang/juliaFor developers: every figure on this page as JSON at /api/v1/repos/JuliaLang/julia.
Similar repositories
Same main language (Julia), most shared frameworks and topics first, then the faster reply.
A data structure for mathematical optimization problems
- First reply
- 4 h
