> Right. It’s a careful balance of what to include and what not to include. (A long-time fossil dev here...) The single most important criteria for new featur

> Right. It’s a careful balance of what to include and what not to include. (A long-time fossil dev here...) The single most important criteria for new features in fossil is, quite simply, "is it useful to fossil's own developers?" Countless times, Richard (the project lead) has found a personal SCM itch in the sqlite project and, a few hours later, committed a feature to fossil to handle that. Fossil is, and always has been, first and foremost, a tool to manage the sqlite project's source code, and sqlite's development is still a primary driver for new features in fossil. None of the features are sqlite-project-specific, but many of the derive from the needs of that project.