It's not clear what type of project the OP is trying to setup, whether it's a programming-related project, or general document-repo type.
>From personal experience, I once was facing the same question to assess Fossil "general" viability. For this almost abstract task, Jim Schimpf's pdf book [http://www.fossil-scm.org/schimpf-book/home] was of great help. It also helped to focus our intended use of Fossil with our projects. Back then we concluded that Fossil was best fit for development-type project, as developers had no issues with command-line interactions, and were familiar with VCS concepts and tools. QA team could also use Fossil tickets through web-UI. However non-developer users would be simply unproductive trying to learn the Fossil command-line for document management, thus we chose a different approach for the document-flow project types. Fast-forward to present, as mentioned before, with Fuel the document-flow gets somewhat more office-friendly. Additionally, with the use of plugins, the developer interaction also gets somewhat more linear, concealing the command-line for the routine tasks. Here are a few Fossil plugins: - Fossil plugin for IDEA-based IDEs [ https://plugins.jetbrains.com/plugin/7479] - Fossil plugin for Qt Creator IDE, C/C++ [ https://github.com/nomadbyte/qtcreator-plugin-fossil] Hope this helps.
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
