On Tue, Mar 10, 2015 at 1:58 PM, jungle Boogie <[email protected]> wrote:
> BTW, referring link was this: > http://www.omiyagames.com/farewell-fossil-version-control/ > > Author's main complaints about Fossil were: > ... > -Author thought you had to run sql each time to list tickets. > Many issue tracking systems have a GUI, "point and click" query builder/editor. So, SQL use can be mostly avoided. Creating such a query builder (probably in Javascript) for Fossil might be a good idea. The project managers I work with want one. Even some of my developer colleagues complain about needing to learn SQL. (Not as much as a few years ago when we doing a lot of defining and refining of the reports and queries.) > -also isn’t a single-button way to switch the default settings of > permissions to the repository from open-source (default) to private, > corporate use. (No idea what this means) > I'm thinking he wants 2 sets of default settings: The existing one (which he perceives as being open source oriented) and another set that are more appropriate for use by software teams within a "corporate environment". > -Complains about cloning > > I know there's been discussion regarding the last one to make cloning > and creating the repo slightly faster by cutting down mkdir. Seems to me that he doesn't realize that Fossil separates the repository from the "working copy". He's expecting "fossil clone" to work like Git or Hg where the working copy is automatically created.
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
