Over the past twelve months, 482 developers contributed new code to salt. This is one of the largest open-source teams in the world, and is in the top 2% of all project teams on Ohloh.
For this measurement, Ohloh considers only recent changes to the code. Over the entire history of the project, 661 developers have contributed.
Over the last twelve months, salt has seen a substantial increase in activity. This may be a sign that interest in this project is rising, and that the open source community has embraced this project.
Ohloh makes this determination by comparing the total number of commits made by all developers during the most recent twelve months with the same figure for the prior twelve months. The number of developers and total lines of code are not considered.
salt is written mostly in Python.
Across all Python projects on Ohloh, 26% of all source code lines are comments. For salt, this figure is 31%.
This high number of comments puts salt among the highest one-third of all Python projects on Ohloh.
A high number of comments might indicate that the code is well-documented and organized, and could be a sign of a helpful and disciplined development team.
The first lines of source code were added to salt in February, 2011. If this young project has had recent activity, then it likely has passed its critical early start-up period, and has become established. The project still may be rapidly changing, innovative and exciting, and finding its focus.
As this project matures, a longer source control history in conjunction with recent activity might indicate that the project has enough merit to hold contributors interest for a long time. It might indicate a mature and relatively bug-free code base, and can be a sign of an organized, dedicated development team.
Note: The source code for salt might actually be older than the source control history can reveal. Many new projects begin by incorporating a large amount of source code from existing, older projects. You might be able to tell whether this is the case by looking for a rapid rise in the amount of code early in the project's history.