Hi Ron, On 10 March 2015 at 12:15, Ron W <[email protected]> wrote: > 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.)
Not diminishing your recommendation at all because it probably would be helpful, but because there's not a builder in place, it enables so much more than whoever creates the builder would image that's necessary. It's kinda like the Unix way where if you're root, you can do something incredibly stupid. I'm sure if a builder is created, though, the user will still be able to enter their own parameters for tickets. Since there is no builder, that means thought needs to be put into creating the queries to get it to show you what you want. Perhaps a happy medium for now is a wiki/document on sample queries for tickets. > >> >> -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". > To me open source means available on internet and corp environment means behind a firewall restricting who can view/clone/etc. >> >> -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. > > Yes, exactly. It's a couple extra steps to open it up. If he's willing to leave Fossil because of that, oh well! ------- inum: 883510009027723 sip: [email protected] xmpp: [email protected] _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
