Re: [fossil-users] Introducing Lagerstatte, an open-source hosting service for Fossil repositories
On 30 March 2015 at 17:39, j. van den hoff veedeeh...@googlemail.com wrote: a marginal point, but in case you care: the german word for repository/deposit actually is Lagerstätte where the diacritical mark over the `a' really matters. but Lagerstatte sounds really awful (since the a is pronounced like the u in the English word `up', while the ä is similarly pronounced to English a in action). and it simply looks misspelled ;-). it also seems not to belong to the words having been assimilated into english after spelling changes (such as iceberg) as far as I know. to make german users a bit more happy you might call it lagerstaette where the `ae' is a widely used ASCII approximation of the ä (in germany, anyway). also note, that Lagerstatt (the singular form of Lagerstätten (with final n)) is an exalted way of denoting a bed (and not a place were to store fossils (or beer ;-)). overall, I'm not sure whether the name choice was a lucky one... Regarding name: What we have considered so far: * Germans prefer to transliterate ä to ae. * Google tries to correct lagerstaette to lagerstatte. * Google includes results for lagerstätte when searching for lagerstatte (but not with lagerstaette). * https://ssl.icu-project.org/icu-bin/translit transliterates ä to a (use Latin - ASCII settings). * This Rails method does the same - ä to a- http://api.rubyonrails.org/classes/ActiveSupport/Inflector.html#method-i-transliterate * German borrowed words in English usually do not use the e form. Like Über to Uber, Flügelhorn to Flugelhorn, Lämmergeier to Lammergeier, https://en.wiktionary.org/wiki/Frau from Fräulein, Grossencharakter from Größencharakter. * There are a few counter examples though - Fuehrer from Führer, Muesli from Müsli, Loess from Löß, Foehn from Föhn. * 29,400 Google search results for lagerstatte (with quotes) vs 8990 for lagerstaette (with quotes). (for completeness, 3,89,000 results for lagerstätte (with quotes)). * Almost all search results for lagerstaette are in German, and in English for lagerstatte. * Our conclusion: lagerstaette when transliterating in German, lagerstatte when transliterating in English. * I'm still not 100% sure. Maybe I should roll with Lagerstätte as project's name, but we still need the ASCII approximation to use in code. regards/joerg On Mon, 30 Mar 2015 12:50:54 +0200, Vikrant Chaudhary vikr...@webstream.io wrote: Hello everyone, I've been working on a project named Lagerstatte, a front-end for Fossil repositories. The browser facing part is written in Ember.js, while server runs a Ruby on Rails application which acts as a JSON endpoint. Access to Fossil database is provided by Stephan's excellent libfossil library. I'd also like to emphasise that this a very early announcement. The project is far from even a beta stage. With this email, my sole intention is to make Fossil community aware of the project. Lagerstatte is a work-in-progress and may do anything it likes up to and including eating your laundry. Features that you can evaluate today: * Navigating through files. * Viewing latest revision of wiki pages. * Access the Fossil repositories through Git protocol (readonly). Planned features: * Installation instructions documentations. * on-premise behind-firewall installations. * Fully featured code, wiki, and issues management. * Email notifications. * LDAP / OpenID Connect authentication. * Searching across multiple repositories. * Basic elements of social networking project discovery. * Unified login across all repositories. * One-click repository setup. * Fault-tolerant and high-availability storage of Fossil repositories. * Cheap forking (I have some ideas on how to achieve this in Fossil/libfossil). * Cross-fork merge-requests. * API, Notifications, Webhooks, OAuth for integration with third-parties. * Graphs Statistics. A preview of Lagerstatte-in-action is available at https://codeflow.io/ Lagerstatte: Web/Fossil: https://codeflow.io/lagerstatte/lagerstatte Git: http://git.codeflow.io/lagerstatte/lagerstatte fossil_ruby: (a Ruby wrapper for libfossil) Web/Fossil: https://codeflow.io/lagerstatte/fossil_ruby Git: http://git.codeflow.io/lagerstatte/fossil_ruby libfossil: Web/Fossil: https://codeflow.io/libfossil/libfossil Git: http://git.codeflow.io/libfossil/libfossil Fossil: Web: https://codeflow.io/fossil/fossil Git/Fossil: Too awesome to handle by currently inefficient git conversion code. I've some ideas on improving this, which I'm working on. I'll be adding more repositories soon to the list (SQLite3, SQLite4, Tcl, Tk, and more). If you'd like to see your repository at Codeflow, let me know. Subscribe to mailing-list for discussions and development updates! https://groups.google.com/forum/#!forum/lagerstatte Feedback, suggestions, and contributions are welcome. About name: A Lagerstätte is a sedimentary deposit that exhibits extraordinary fossils with exceptional
Re: [fossil-users] New timeline display options
Richard Hipp wrote: James Moger's circular timeline nodes and colored timeline graphs are easily selectable skin options available to skin designers. For a comparison: http://www.fossil-scm.org/fossil/timeline?y=ci http://www2.fossil-scm.org/fossil/timeline?y=ci I hope you aren't too attached to this. I finally got some time to experiment with making it possible to style the various graph elements in just about any way that CSS allows. This will give skin authors a lot more flexibility without requiring Fossil devs to add support for each desired customization. I should have gone to bed a long time ago. I'll have a branch (probably called graph-css) for review/fixes/improvement up by Tuesday night at the latest. ___ 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] Introducing Lagerstatte, an open-source hosting service for Fossil repositories
On Mon, Mar 30, 2015 at 10:57 PM, Vikrant Chaudhary vikr...@webstream.io wrote: fossil clone --cheap file:///path/to/upstream.fossil new-project.fossil +1 I think I would use this feature should it ever come available. I have 500M+ repos where a cheap clone would be quite nice to have. I assume the feature would work whether the upstream fossil was read only or not. The benefit would be a clone that takes a few seconds rather than several minutes. ___ 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] Introducing Lagerstatte, an open-source hosting service for Fossil repositories
On 3/31/2015 11:18 PM, Matt Welland wrote: On Mon, Mar 30, 2015 at 10:57 PM, Vikrant Chaudhary vikr...@webstream.io wrote: fossil clone --cheap file:///path/to/upstream.fossil new-project.fossil +1 I think I would use this feature should it ever come available. I have 500M+ repos where a cheap clone would be quite nice to have. I assume the feature would work whether the upstream fossil was read only or not. The benefit would be a clone that takes a few seconds rather than several minutes. I'm thinking about how this could be used at my workplace. On some projects we have shared computers called viewservers (view being a ClearCase term) on which we create our sandboxes (again, CC term). Switching to Fossil would mean each user getting his or her own copy of the full repository which synchronizes with the master. Furthermore, each user would need a separate copy for each viewserver because it's best not to share SQLite databases through NFS. This will eat a LOT of disk space. If users could somehow share repositories without copying them in full, that would help a lot. A simple test showing how Fossil repositories cannot be shared is to attempt running two [fossil open] commands simultaneously. With small projects this is hard to do, but you can just hit Ctrl-Z during the first to make it take as long as you want. With projects such as those I work on, [fossil open] takes a few minutes because (1) there's gigabytes of stuff being written out, and (2) we're always stuck with obsolete computers. So sharing any given repository file is clearly out of the question. -- Andy Goth | andrew.m.goth/at/gmail/dot/com signature.asc Description: OpenPGP digital signature ___ 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] New timeline display options
On Tue, Mar 31, 2015 at 5:48 PM, bch brad.har...@gmail.com wrote: Hi Matt. Would picking the branch you care about (like this: http://fossil-scm.org/index.html/timeline?r=skin-xekrindc=2015-03-25+21%3A52%3A07n=200 ) suit your workflow ? Hi Brad, Yes, I often narrow to the branch like that but that hides the context of activity on other branches I might be interested in. When scrolling down through a busy timeline the visual clue of which line belongs to which branch would be useful to me. I have one section on a timeline with 16 parallel lines and no visual hint as to which is which branch. Just my $0.02 ... -bch On 3/31/15, Matt Welland mattrwell...@gmail.com wrote: On Tue, Mar 31, 2015 at 9:20 AM, Andy Bradford amb-fos...@bradfords.org wrote: Thus said Matt Welland on Mon, 30 Mar 2015 21:08:49 -0700: +1 circular nodes, +1 colored lines, seemed to make visually tracking the branch easier to my eyes. but as Brad said, a matter of style. Definitely a matter of style. While I think both are pretty, I prefer black edges (the nodes are already colored and align nicely with the commit messages, and I find the colored lines distracting), and square nodes. :-) There is one pragmatic factor. I quite often find myself tracing timelines back over multiple screens and having different colored lines would really help. I'd be cool if this was an option for those who like it. Andy -- TAI64 timestamp: 4000551ac96a ___ 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 ___ 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] New timeline display options
On Mar 31, 2015 8:26 PM, Matt Welland mattrwell...@gmail.com wrote: On Tue, Mar 31, 2015 at 5:48 PM, bch brad.har...@gmail.com wrote: Hi Matt. Would picking the branch you care about (like this: http://fossil-scm.org/index.html/timeline?r=skin-xekrindc=2015-03-25+21%3A52%3A07n=200 ) suit your workflow ? Hi Brad, Yes, I often narrow to the branch like that but that hides the context of activity on other branches I might be interested in. When scrolling down through a busy timeline the visual clue of which line belongs to which branch would be useful to me. I have one section on a timeline with 16 parallel lines and no visual hint as to which is which branch. Just my $0.02 ... That sounds like a valid $0.02 to me. JS/CSS experts: is there such tech that we could somehow select a vertical graph/branch indicator and have it highlighted somehow? -bch On 3/31/15, Matt Welland mattrwell...@gmail.com wrote: On Tue, Mar 31, 2015 at 9:20 AM, Andy Bradford amb-fos...@bradfords.org wrote: Thus said Matt Welland on Mon, 30 Mar 2015 21:08:49 -0700: +1 circular nodes, +1 colored lines, seemed to make visually tracking the branch easier to my eyes. but as Brad said, a matter of style. Definitely a matter of style. While I think both are pretty, I prefer black edges (the nodes are already colored and align nicely with the commit messages, and I find the colored lines distracting), and square nodes. :-) There is one pragmatic factor. I quite often find myself tracing timelines back over multiple screens and having different colored lines would really help. I'd be cool if this was an option for those who like it. Andy -- TAI64 timestamp: 4000551ac96a ___ 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 ___ 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] using fossil server --repolist behind nginx proxy
From: Dewey Hylton dewey.hyl...@gmail.com To: Fossil SCM user's discussion fossil-users@lists.fossil-scm.org Sent: Sunday, March 29, 2015 11:07:31 AM Subject: Re: [fossil-users] using fossil server --repolist behind nginx proxy From: David Macek david.mace...@gmail.com Sent: Sunday, March 29, 2015 10:56:07 AM On 29. 3. 2015 16:55, Andy Bradford wrote: Given that you're using nginx as a proxy, perhaps you need to add --baseurl to the fossil server options? OP mentioned that he tried it. yeah ... that feature seems to be relevant only when one is *not* serving a directory. at least that's what my testing has shown. and for what it's worth, i'm working with: $ fossil version This is fossil version 1.32 [6c40678e91] 2015-03-14 13:20:34 UTC ... any other suggestions? i really prefer to stay away from cgi and making my own index page ... ___ 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] Introducing Lagerstatte, an open-source hosting service for Fossil repositories
Vikrant Chaudhary wrote: On 30 March 2015 at 17:39, j. van den hoff veedeeh...@googlemail.com wrote: a marginal point, but in case you care: the german word for repository/deposit actually is Lagerstätte where the diacritical mark over the `a' really matters. but Lagerstatte sounds really awful (since the a is pronounced like the u in the English word `up', while the ä is similarly pronounced to English a in action). and it simply looks misspelled ;-). it also seems not to belong to the words having been assimilated into english after spelling changes (such as iceberg) as far as I know. to make german users a bit more happy you might call it lagerstaette where the `ae' is a widely used ASCII approximation of the ä (in germany, anyway). also note, that Lagerstatt (the singular form of Lagerstätten (with final n)) is an exalted way of denoting a bed (and not a place were to store fossils (or beer ;-)). overall, I'm not sure whether the name choice was a lucky one... Regarding name: What we have considered so far: * Germans prefer to transliterate ä to ae. * Google tries to correct lagerstaette to lagerstatte. * Google includes results for lagerstätte when searching for lagerstatte (but not with lagerstaette). * https://ssl.icu-project.org/icu-bin/translit transliterates ä to a (use Latin - ASCII settings). * This Rails method does the same - ä to a- http://api.rubyonrails.org/classes/ActiveSupport/Inflector.html#method-i-transliterate * German borrowed words in English usually do not use the e form. Like Über to Uber, Flügelhorn to Flugelhorn, Lämmergeier to Lammergeier, https://en.wiktionary.org/wiki/Frau from Fräulein, Grossencharakter from Größencharakter. * There are a few counter examples though - Fuehrer from Führer, Muesli from Müsli, Loess from Löß, Foehn from Föhn. * 29,400 Google search results for lagerstatte (with quotes) vs 8990 for lagerstaette (with quotes). (for completeness, 3,89,000 results for lagerstätte (with quotes)). * Almost all search results for lagerstaette are in German, and in English for lagerstatte. * Our conclusion: lagerstaette when transliterating in German, lagerstatte when transliterating in English. * I'm still not 100% sure. Maybe I should roll with Lagerstätte as project's name, but we still need the ASCII approximation to use in code. I'm not a German speaker, and I don't know if you care, but I would vote with Joerg to use ae rather than just a. (Simply ignoring the umlaut seem just wrong - regardless of Google.) FWIW, the two dots in ä and ö derive historically from a small e placed above the letters a and o. Also, German proper names that contained an umlaut are regularly spelled with the e (at least in the mid-western US). -- Will ___ 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] file-filter branch plead
Hi Steve, On 30 March 2015 at 15:53, Steve Stefanovich s...@stef.rs wrote: Yes, I find file filtering useful too. Even better, it should be incorporated in search drop-down list. FWIW, I manage now by ' f sett manifest on' and grepping the manifest file. You do this from the cli only, correct? http://www.mail-archive.com/fossil-users%40lists.fossil-scm.org/msg19455.html Good points in article and hopefully we'll see some happen. Since the file filter already exists, it's the easiest to implement but I suppose there's not much of a draw for it and that's why it's not in Fossil. -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info xmpp: jungle-boo...@jit.si ___ 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] New timeline display options
+1 -Original Message- From: Andy Bradford Sent: Tuesday, March 31, 2015 7:20 PM To: Matt Welland Cc: Fossil SCM user's discussion Subject: Re: [fossil-users] New timeline display options Thus said Matt Welland on Mon, 30 Mar 2015 21:08:49 -0700: +1 circular nodes, +1 colored lines, seemed to make visually tracking the branch easier to my eyes. but as Brad said, a matter of style. Definitely a matter of style. While I think both are pretty, I prefer black edges (the nodes are already colored and align nicely with the commit messages, and I find the colored lines distracting), and square nodes. :-) Andy -- TAI64 timestamp: 4000551ac96a ___ 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] New timeline display options
Thus said Matt Welland on Mon, 30 Mar 2015 21:08:49 -0700: +1 circular nodes, +1 colored lines, seemed to make visually tracking the branch easier to my eyes. but as Brad said, a matter of style. Definitely a matter of style. While I think both are pretty, I prefer black edges (the nodes are already colored and align nicely with the commit messages, and I find the colored lines distracting), and square nodes. :-) Andy -- TAI64 timestamp: 4000551ac96a ___ 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] Introducing Lagerstatte, an open-source hosting service for Fossil repositories
On Tue, Mar 31, 2015 at 2:16 AM, Vikrant Chaudhary vikr...@webstream.io wrote: Maybe I should roll with Lagerstätte as project's name, but we still need the ASCII approximation to use in code. In the actual code or in string constants? If in string constants, why not use the ISO-8859-1 encoding? Or even Unicode? As long as your software sets the character set parameter in the HTTP header, this should display correctly. Example: Content-Type: text/html; charset=iso-8859-1 or: Content-Type: text/html; charset=utf-8 ___ 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] New timeline display options
On Tue, Mar 31, 2015 at 9:20 AM, Andy Bradford amb-fos...@bradfords.org wrote: Thus said Matt Welland on Mon, 30 Mar 2015 21:08:49 -0700: +1 circular nodes, +1 colored lines, seemed to make visually tracking the branch easier to my eyes. but as Brad said, a matter of style. Definitely a matter of style. While I think both are pretty, I prefer black edges (the nodes are already colored and align nicely with the commit messages, and I find the colored lines distracting), and square nodes. :-) There is one pragmatic factor. I quite often find myself tracing timelines back over multiple screens and having different colored lines would really help. I'd be cool if this was an option for those who like it. Andy -- TAI64 timestamp: 4000551ac96a ___ 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] file-filter branch plead
Yes, from the shell command line. S. Original Message From: jungle Boogie Sent: Wednesday, 1 April 2015 01:18 To: Fossil SCM user's discussion Reply To: Fossil SCM user's discussion Subject: Re: [fossil-users] file-filter branch plead Hi Steve, On 30 March 2015 at 15:53, Steve Stefanovich s...@stef.rs wrote: Yes, I find file filtering useful too. Even better, it should be incorporated in search drop-down list. FWIW, I manage now by ' f sett manifest on' and grepping the manifest file. You do this from the cli only, correct? http://www.mail-archive.com/fossil-users%40lists.fossil-scm.org/msg19455.html Good points in article and hopefully we'll see some happen. Since the file filter already exists, it's the easiest to implement but I suppose there's not much of a draw for it and that's why it's not in Fossil. -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info xmpp: jungle-boo...@jit.si ___ 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] New timeline display options
Hi Matt. Would picking the branch you care about (like this: http://fossil-scm.org/index.html/timeline?r=skin-xekrindc=2015-03-25+21%3A52%3A07n=200) suit your workflow ? -bch On 3/31/15, Matt Welland mattrwell...@gmail.com wrote: On Tue, Mar 31, 2015 at 9:20 AM, Andy Bradford amb-fos...@bradfords.org wrote: Thus said Matt Welland on Mon, 30 Mar 2015 21:08:49 -0700: +1 circular nodes, +1 colored lines, seemed to make visually tracking the branch easier to my eyes. but as Brad said, a matter of style. Definitely a matter of style. While I think both are pretty, I prefer black edges (the nodes are already colored and align nicely with the commit messages, and I find the colored lines distracting), and square nodes. :-) There is one pragmatic factor. I quite often find myself tracing timelines back over multiple screens and having different colored lines would really help. I'd be cool if this was an option for those who like it. Andy -- TAI64 timestamp: 4000551ac96a ___ 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
