I’ve implemented a project that allows people to self-report which parts of Django they are using in their project. The purpose here is to help Fellows, Steering Councils and contributors make better decisions about the project.
Currently, when we discuss a particular API, setting, or patterns, one approach is to search GitHub for those usages. However, that’s a very small subset of projects. This seeks to increase the amount of projects that the community has some insight into. Any reports from this should be taken with a grain of salt, it’s only projects that can/are willing to share that can be reported on. However, like the Django survey, it is information that can help us moving forward.
- Site: https://djangoprobe.org
- Stats: Stats | Django Probe
- Repo: GitHub - tim-schilling/django-probe: Django Probe allows you to share how your project uses Django. This package counts how often specific code patterns appear in your Django project and shares the aggregated information with the community. · GitHub
Ideally, I’ll pass this off to the DSF to manage in the future. However, I don’t want to add to our burden without providing a value, so until we get some value out of it, I’m happy to spend the time maintaining/operating it.
There are several ways this can be iterated on to improve the community such as a sponsors integration to allows their usages to be highlighted for Fellows / the Steering Council, the ability for other Django & Python packages to upload their own API vocabularies to allow users who opt-into reporting on their packages to share info, or more generally becoming a way for us to see how well we communicate API changes to the community watching usages change over time.