On 10/24/2016 03:07 PM, Warren Young wrote: > I don’t know that Fossil is all that close to any other software > system you’ve likely used before.
Isn't it a file (version) management system based on an embedded database? On 10/23/2016 06:13 PM, Scott Doctor wrote: > My current workflow uses a database (was filemaker but switched to > sqlite a while ago) like a library card catalog with notes and status > fields. It sounds like you rolled your own file management system; the difference being that, with Fossil, the managed files are stored *in* the database. For a while I imagined it would be useful if the Fossil file management system were also capable of tracking and referencing files that are not stored in the database. But after thinking more about the requirements and use-cases, Fossil is probably in a funky territory of being too light-weight in its capabilities to be the solution, and too monolithic to be incorporated into a solution. It has however attracted/inspired several people from the research/experimentation arena (to the mailing list) who need a tool-suite that supports modern [science][1] with software engineering and data analysis methods. Again, I don't think Fossil is the solution to this open problem. [1]: By "science" I mean knowledge engineering informed by epistemological sophistication and a high traction with reality. _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
