Suggestion to slightly improve Julia development

Community
80

After reading Julia has an issue… blogpost, I’ve added few updates to initial report.

  1. “State of the first PR of new authors” - what is usually happening with the first PR? Well, it is a good thing, that over the years acceptance rate is more or less constant, though in recent years PRs more often left in open state instead of rejected (I am not sure that this is the correct word, it means that PR was closed without being merged). So, yes, combining it with the fact that more then half of new authors produces only single PR it looks like from their perspective their PRs are left in limbo.

  2. More interesting section is “Core and non-core developers”. It shows amount of PRs produced by core developers (well, they also were called mergers and maintainers, sorry for this terminology shifting). One can see that over the years PRs from non core team is growing almost linearly which is really good, and currently 40% of all PRs is from non-core contributors. On the other hand, waiting times for core and non-core team are significantly different, especially it shows in 2019. Only half of PRs in 2019 were closed in 215 hours (~9 days), other half waited longer than that.

Now, these numbers should be considered carefully, because there are multiple reasons why non-core PR wait longer - they may lack proper documentation, testing or some other important things, so this difference is natural, but of course it would be better if waiting times can be made smaller.

  1. I’ve added a couple other repositories for comparison. There was no particular strategy, choice is more or less random. Full list is

    Julia: ⚡ Pluto.jl ⚡
    Rust: ⚡ Pluto.jl ⚡
    Chapel: ⚡ Pluto.jl ⚡
    Nim: ⚡ Pluto.jl ⚡

Rust report is partially broken, due to their maintenance bot.

7 Likes