wagtail/wagtail
A Django content management system focused on flexibility and user experience
In plain words
Outside PRs: 3 in 10 merged. First reply usually within 41 h. 1 starter issue is available now. Replies slowed down this month.
Outside PRs merged
30%
25 merged, 59 closed, 18 still open
Higher than 4% of 559 other measured repositories
First human reply
41 h
median of 102 outside PRs, 24 unanswered
Time to merge
Not enough data
25 of 102 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
No GSoC on Wagtail core in 2027
Open issue #14705 - 3
Know where to ask
No chat was found. Ask on the issue you are working on; that is where maintainers look.
- 4
Open a small pull request
Link the issue in it. A first reply here usually takes 41 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 outsiders102100%
- Got a human reply7876%
- Merged2525%
Time to first reply
After 2 days, 51% of outside PRs had a reply from a person. After a week, 62%. Bots do not count.
The last 52 weeks
Slowed down. Median first reply was 6 h over the last four weeks (53 PRs) and 2 h over the four before (43 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
- 1
- Claimed
- 0
- Has a pull request
- 0
- Stale
- 0
- AvailableNo GSoC on Wagtail core in 2027#14705
Issue replies: first human reply in 5 days (median of 88 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 13:00 and 16:00 (India time).
Show as table
| Hour (India time) | Replies, all weekdays |
|---|---|
| 00:00 | 1 |
| 01:00 | 2 |
| 02:00 | 1 |
| 03:00 | 0 |
| 04:00 | 0 |
| 05:00 | 1 |
| 06:00 | 1 |
| 07:00 | 0 |
| 08:00 | 0 |
| 09:00 | 0 |
| 10:00 | 3 |
| 11:00 | 8 |
| 12:00 | 10 |
| 13:00 | 22 |
| 14:00 | 32 |
| 15:00 | 27 |
| 16:00 | 21 |
| 17:00 | 14 |
| 18:00 | 13 |
| 19:00 | 22 |
| 20:00 | 24 |
| 21:00 | 20 |
| 22:00 | 13 |
| 23:00 | 2 |
How to start
- Contributing guidefound
- Code of conductfound
- Issue templatesfound
- Dev container for one-step setupnot found
- No CLA or sign-off requirement was found.
Where the project talks
No chat or mailing list link was found in the README or contributing guide.
Activity
- Commits, 90 days
- 534
- Releases, 12 months
- 30
- Active maintainers
- 13
- Last push
- 9 Oct 2026
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/wagtail/wagtail)[](https://contributable.vercel.app/repo/wagtail/wagtail)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/wagtail/wagtailFor developers: every figure on this page as JSON at /api/v1/repos/wagtail/wagtail.
Similar repositories
Same main language (Python), most shared frameworks and topics first, then the faster reply.
An open database of prices 🧾💸💰🏷️🤑🍽️
- First reply
- 2.9 days
