> > > My comment was not about discussing the pros and cons of closed versus > open source software. My concerns are more about reliability. > For me it's totally Ok to use git for versioning IF the tools are there. > Squak and Pharo have decent versioning systems that suit their internal > needs. There is room for improvements, that's for sure. > For me Smalltalk is a system and not a simple language with some arbitrary > tools that can be replaced easily. > > The problem is whether the tools you choose for "commoditized" tasks (e.g. SCM) limit the amount of manpower that could contribute to your open source project.
Forks and pull-requests are the way most open source projects fix bugs and integrates enhancements. You can't do branching with current tooling (read: Monticello) without suffering proportional to its complexity. No one said tools can be replaced easily, and that's the reason we still use Monticello, some of us backed by old mcz files, others already using some git behind it. Regards,
