It's old school enterprise speak. When software-being-built consisted of a number of "Configuration Items" (CIs), such as .doc files, .xls files and of course heaps of .c files. There would be a dedicated "Configuration Manager" who's job it was to make sure that people wouldn't Visual SourceSafe their files over other people's files. He'd also write the batch files for the build server, assuming they had a build server.

They really do mean source control. Just that it doesn't have to be source code. It can be any "configuration item". Just like with git or svn or mercurial or zipping-directories-and-uploading-them-to-a-network-share.

Personally, I like "version control" for that reason. It just removes the subject of the operation from the name entirely.

Source code management is a subset of software configuration management ("configuration" here refers to the configuration of the build rather than the end program). https://en.wikipedia.org/wiki/Software_configuration_managem...

You are right, makes it seem like this is for storing config files. Source code management is not enough though since this has built in issue tracker and wiki.

Yeah that's really weird terminology for a VCS. I thought it was something like Puppet/Chef at first.

"SCM" can stand for different words, depending who's uttering it, but where fossil stands is this: it fills the same role as git or mercurial. Its a DSCM (which I read as "distributed source control management"). Fill out the acronym as you see fit.

Edit: typo, grammar

The title was changed to something less accurate than what I originally posted.

It is weird -- I think SCM should mean "source control management" NOT "software configuration management", but the latter is what the website has.