1. 13
  1. 1

    wow, this is fascinating and a little sad, and makes me feel guilty for never getting involved with Django! the only thing I’d say (on a first reading of the article only) is I wonder if the problem of cachet associated with “committers” vs just releasers/mergers wouldn’t simply reappear over time with the latter anyway. Interesting to see where its gone, having followed (and used) the project since about 1.1 (!).

    1. 2

      I’ve sent a couple commits to Django, more as drive-by fixes and improvements than having much involvement in django-developers

      My interactions ended up mostly being with Tim Graham (I think a Fellow? handling PRs and bug triage), and it’s a pretty well-set up process. The round tripping a couple times for things can take time, but it’s mostly because of high baseline of the codebase.

      The rough reality is that the DSF doesn’t have nearly the funds of other communities. Millions of users of Django, but there are almost no full-time paid contributors. Compared to what you see in something like Rails, it makes it really hard to have the resources to move forward. I don’t really know the right way forward, though.