Re: [fossil-users] Git-v-Fossil. Was: Google code shutting down
On Fri, Mar 13, 2015 at 8:26 PM, Richard Hipp d...@sqlite.org wrote: Fossil was created to support the development of SQLite. All other use (and there is more and more of that lately) is just gravy. They all start somewhere. :) Git Hg were both written to solve the Linux kernel's BitKeeper conundrum. Both grew to be larger than just a solution for the initial need. It could happen for Fossil too. -J ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Git-v-Fossil. Was: Google code shutting down
On Mar 16, 2015 9:44 AM, James Moger james.mo...@gmail.com wrote: On Fri, Mar 13, 2015 at 8:26 PM, Richard Hipp d...@sqlite.org wrote: Fossil was created to support the development of SQLite. All other use (and there is more and more of that lately) is just gravy. They all start somewhere. :) Git Hg were both written to solve the Linux kernel's BitKeeper conundrum. Both grew to be larger than just a solution for the initial need. It could happen for Fossil too. It has happened for fossil. Just to a different magnitude. :) SDR ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Git-v-Fossil. Was: Google code shutting down
On Fri, Mar 13, 2015 at 8:46 PM, Timothy Beyer bey...@fastmail.net wrote: At Fri, 13 Mar 2015 20:23:51 -0400, James Moger wrote: You have a great solution. If not then... 5. Corporate users/teams need hooks to integrate with CI notification systems. Partial check. I see there are per-repository hook points, but they seem undeveloped. 6. Corporate users/teams need active notifications: mail, Slack, HipChat, Glip, etc Semi-existing with external tools. See http://core.tcl.tk/akupries/fx/index At least in my view, the ticketing system would be more useful with more hooks for ticket editing and submission. I wrote a vastly more powerful interface to the ticketing system that we use internally, Are the sources of this interface openly visible somewhere, i.e. OSS ? -- Andreas Kupries Senior Tcl Developer Code to Cloud: Smarter, Safer, Faster™ F: 778.786.1133 andre...@activestate.com, http://www.activestate.com Learn about Stackato for Private PaaS: http://www.activestate.com/stackato ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Git-v-Fossil. Was: Google code shutting down
At Sat, 14 Mar 2015 13:33:31 -0700, Andreas Kupries wrote: On Fri, Mar 13, 2015 at 8:46 PM, Timothy Beyer bey...@fastmail.net wrote: At Fri, 13 Mar 2015 20:23:51 -0400, James Moger wrote: You have a great solution. If not then... 5. Corporate users/teams need hooks to integrate with CI notification systems. Partial check. I see there are per-repository hook points, but they seem undeveloped. 6. Corporate users/teams need active notifications: mail, Slack, HipChat, Glip, etc Semi-existing with external tools. See http://core.tcl.tk/akupries/fx/index At least in my view, the ticketing system would be more useful with more hooks for ticket editing and submission. I wrote a vastly more powerful interface to the ticketing system that we use internally, Are the sources of this interface openly visible somewhere, i.e. OSS ? Unfortunately, not yet. At some point I am going to try to persuade my boss of the merits of releasing the source code, particularly to the ticket search capabilities. Tim ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Git-v-Fossil. Was: Google code shutting down
Tim wrote: At Sat, 14 Mar 2015 13:33:31 -0700, Andreas Kupries wrote: On Fri, Mar 13, 2015 at 8:46 PM, Timothy Beyer bey...@fastmail.net wrote: At least in my view, the ticketing system would be more useful with more hooks for ticket editing and submission. I wrote a vastly more powerful interface to the ticketing system that we use internally, Are the sources of this interface openly visible somewhere, i.e. OSS ? Unfortunately, not yet. Sorry to hear that. At some point I am going to try to persuade my boss of the merits of releasing the source code, particularly to the ticket search capabilities. IIRC Richard is experimenting with general searching of fossil repos via the sqlite FTS, i.e. commits, wiki pages, tickets, etc. -- So long, Andreas Kupries akupr...@shaw.ca http://www.purl.org/NET/akupries/ Developer @ http://www.activestate.com/ EuroTcl 2015, June 20-21, Colgne/DE, http://www.eurotcl.tcl3d.org/ 22'nd Tcl/Tk Conference: Oct 19-23, Manassas, VA, USA --- ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Git-v-Fossil. Was: Google code shutting down
On 3/13/15, James Moger james.mo...@gmail.com wrote: What exists in the Git world to compare to Fossil as a private, self-contained, all-in-one service? Feature-for-feature: GitLab If you can live with less: Gitblit, Gerrit, RhodeCode, GitBucket, Stash Which if these (if any) is used by http://repo.or.cz/git-browser/by-commit.html?r=sqlite.git to mirror the SQLite repo (compare: https://www.sqlite.org/src/timeline?y=ci) and are some of the others any better? -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Git-v-Fossil. Was: Google code shutting down
At Fri, 13 Mar 2015 20:23:51 -0400, James Moger wrote: You have a great solution. If not then... 1. Corporate users/teams need client/server with a centralized/canonical repo. Check. 2. Corporate users/teams need multiple-repositories. Check, although configuration consistency/maintenance scales linearly with the number of repos. There appears to be shared authentication, so that is good. But authorization must be maintained for each repo. 3. Corporate users/teams need to be able to manage repo lifecycle (create/delete). Missing. 4. Corporate users/teams like to have overviews/dashboards of multiple repositorires - repository groups are a crowd favorite. Graphs are pretty. Missing. For the extent of my own open source projects, I would like a dashboard to promote awareness of my other (often related) open source projects. 5. Corporate users/teams need hooks to integrate with CI notification systems. Partial check. I see there are per-repository hook points, but they seem undeveloped. 6. Corporate users/teams need active notifications: mail, Slack, HipChat, Glip, etc 7. Corporate users/teams need LDAP/PAM/Windows authentication - especially LDAP. We use fossil extensively where I work, for almost any imaginable use, and LDAP authentication would be hugely beneficial. The other changes that you mentioned sound quite useful as well. At least in my view, the ticketing system would be more useful with more hooks for ticket editing and submission. I wrote a vastly more powerful interface to the ticketing system that we use internally, and as far as that is concerned, I don't know of a way allow inline editing of tickets on the ticket list view, at least not without using the edit page as a ticket listing page. If the JSON API supports such hooks in the future, that would be amazing. This is a non-trivial list and maybe it's beyond the scope of the intentions of Fossil. Or maybe not. Perhaps if a large company starts using fossil, then they would finance some or all of these features. Regards, Tim ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Git-v-Fossil. Was: Google code shutting down
The SQLite mirror is GitWeb which is a Perl script that ships with Git. I didn't name it because it is not a server like Fossil, Gitblit, Gerrit, etc. It is usually paired with Apache system-level SSH access. I rarely see it anymore as there are more competent alternatives for plain viewing, like cGit[1]. Absolutely, some are better than others. Some are of those are commercial (Stash), some are hybrid-commercial (RhodeCode, Gitlab), and some are pure FOSS (Gitblit, Gerrit). All the ones I mentioned 1. serve repos over http ssh (some do native, unauthenticated git:// protocol too) 2. offer multiple authentication mechanisms and authorization schemes 3. allow sharing/collaboration via branch/multi-repo mechanisms (not all follow the Github repo-fork design) 4. have rich hook integrations (mail, ci, realtime hosted chat ala Slack, Hipchat, etc) And then there are many rich GUI clients for the major platforms... SourceTree, SmartGit, Tower, Github for Mac/Windows, Eclipse EGit, etc. Not too mention major corporate funding. Git and it's ecosystem are a juggernaut. When Fossil is compared to Git, the comparison is of course going to extend beyond core Git and core Fossil to include clients servers integrations. Rather than using our tape measures to see who is awesome at X and who is lousy at Y, I would just consider what the needs of Fossil users are: I don't know who the intended audience of Fossil is, but I will assume that it includes FOSS projects and corporations. If that is not the intended audience, then I think you are done. You have a great solution. If not then... 1. Corporate users/teams need client/server with a centralized/canonical repo. Check. 2. Corporate users/teams need multiple-repositories. Check, although configuration consistency/maintenance scales linearly with the number of repos. There appears to be shared authentication, so that is good. But authorization must be maintained for each repo. 3. Corporate users/teams need to be able to manage repo lifecycle (create/delete). Missing. 4. Corporate users/teams like to have overviews/dashboards of multiple repositorires - repository groups are a crowd favorite. Graphs are pretty. Missing. 5. Corporate users/teams need hooks to integrate with CI notification systems. Partial check. I see there are per-repository hook points, but they seem undeveloped. 6. Corporate users/teams need active notifications: mail, Slack, HipChat, Glip, etc 7. Corporate users/teams need LDAP/PAM/Windows authentication - especially LDAP. This is a non-trivial list and maybe it's beyond the scope of the intentions of Fossil. Or maybe not. Has integrating/promoting ChiselApp for on-premise installs been entertained? I haven't tried it yet, but on it's face it seems to address some of the above list. -J [1]: http://git.zx2c4.com/cgit On Fri, Mar 13, 2015 at 5:46 PM, Richard Hipp d...@sqlite.org wrote: On 3/13/15, James Moger james.mo...@gmail.com wrote: What exists in the Git world to compare to Fossil as a private, self-contained, all-in-one service? Feature-for-feature: GitLab If you can live with less: Gitblit, Gerrit, RhodeCode, GitBucket, Stash Which if these (if any) is used by http://repo.or.cz/git-browser/by-commit.html?r=sqlite.git to mirror the SQLite repo (compare: https://www.sqlite.org/src/timeline?y=ci) and are some of the others any better? -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Git-v-Fossil. Was: Google code shutting down
On 3/13/15, James Moger james.mo...@gmail.com wrote: I don't know who the intended audience of Fossil is... Fossil was created to support the development of SQLite. All other use (and there is more and more of that lately) is just gravy. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
