laurent22/joplin
Joplin - the privacy-focused note taking app with sync capabilities for Windows, macOS, Linux, Android and iOS.
In plain words
Outside PRs: 4 in 10 merged. First reply usually within 14 h. Replies slowed down this month.
Outside PRs merged
39%
42 merged, 67 closed, 1 still open
Higher than 7% of 565 other measured repositories
First human reply
14 h
median of 110 outside PRs, 28 unanswered
Time to merge
Not enough data
42 of 110 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 README
No contributing guide was found, so the README is where setup is explained.
Open the README - 2
Find something small
No first issue is free right now. Look for a typo, a missing test or an unclear error message, or ask where help is wanted.
Browse open issues - 3
Know where to ask
Questions go to the project's discord, 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 14 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 outsiders110100%
- Got a human reply8275%
- Merged4238%
Time to first reply
After 2 days, 60% of outside PRs had a reply from a person. After a week, 73%. Bots do not count.
The last 52 weeks
Slowed down. Median first reply was 6 h over the last four weeks (49 PRs) and 3 h over the four before (39 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.
No open issue carries a beginner label.
Issue replies: first human reply in Not enough data (median of 297 issues).
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 19:00 and 22:00 (India time).
Show as table
| Hour (India time) | Replies, all weekdays |
|---|---|
| 00:00 | 44 |
| 01:00 | 40 |
| 02:00 | 44 |
| 03:00 | 43 |
| 04:00 | 37 |
| 05:00 | 37 |
| 06:00 | 32 |
| 07:00 | 18 |
| 08:00 | 8 |
| 09:00 | 2 |
| 10:00 | 1 |
| 11:00 | 2 |
| 12:00 | 6 |
| 13:00 | 13 |
| 14:00 | 25 |
| 15:00 | 39 |
| 16:00 | 49 |
| 17:00 | 40 |
| 18:00 | 31 |
| 19:00 | 44 |
| 20:00 | 49 |
| 21:00 | 43 |
| 22:00 | 40 |
| 23:00 | 45 |
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/laurent22/joplin)[](https://contributable.vercel.app/repo/laurent22/joplin)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/laurent22/joplinFor developers: every figure on this page as JSON at /api/v1/repos/laurent22/joplin.
Similar repositories
Same main language (TypeScript), most shared frameworks and topics first, then the faster reply.
Fast, developer-friendly JS/TS dependency vulnerability scanner with local lockfile scanning, OSV matching, direct vs transitive visibility,
- First reply
