Re: [fossil-users] Bikeshedding opportunity: back to the topic of libfossil's name
On Thu, Aug 22, 2013 at 4:34 AM, Chad Perrin c...@apotheon.net wrote:
http://chiselapp.com/user/cutterpillow/repository/fossil-iOS/
There's a libfossil.cpp in the src directory of the source tree
(requires anonymous login to view, naturally).
i'm not worried about collisions of individual files, just the overall
project name (but if they collide across namespaces that doesn't bother
me all that much). From what you and Brad have found, it seems like that's
of no real concern.
I'd say the name should just be set in stone as libfossil now, and a
i tend to agree. But then we'll have to find another bikeshedding topic ;).
(Oh, i've got plenty of them lined up...)
mirror should be set up on GitHub to boost its search engine ranking a
little bit (with a prominent mention of its canonical version control
repository being elsewhere using Fossil itself, of course). While
OMG! lol. It never occurred to me to do such a thing, but you're right, it
would probably be a good idea.
you're at it, if you're willing to bother, you could twit about it on
Twitter and/or homestead the @libfossil name there. I wouldn't go so
far as to recommend doing anything on Facebook, of course.
While i occasionally (or more often) act like one, i don't twit or FB, and
try to keep my G+ to a minimum. It's all too distracting for me - oh,
something shiny with moving parts...
That said, i do appreciate (==love/hate) the power of marketing and i would
be very appreciative if someone would take over such a role :). How does
the title of PR Manager sound to you :)?
I'll see if, at its current level of (in)completeness, it passes muster
for inclusion in some of the Copyfree Initiative's lists (like copyfree
licensed projects worthy of support or addition to the copyfree software
listing), if you want to finally declare an official name for it as
libfossil.
Don't bother at this point - it's alpha quality. The basics are in place
and working but there are months of work left in the lib-level SCM-related
components and about a thousand unit tests to write, and then several more
months for things like network sync. i also don't want to propagate the
home page link too much at this point because i will rename the repo as
soon as we decide to settle on the name libfossil ;). Last week i had the
advantage of having a week off of work, and got far more done on the code
than i had hoped to, but i won't have any more time off until probably
October, so i'm restricted to what i can get done in ~6 hours/night plus
weekends. The point being only that it's moving steadily but not quickly,
and is not something someone will be able to just sit down and use for at
least a few months (and at that point it'll almost certainly be limited to
local usage, but local app-embedded SCM is one of my primary goals here).
Thanks, {Ch,Br}ad!
--
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
___
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] Bikeshedding opportunity: back to the topic of libfossil's name
On Thu, Aug 22, 2013 at 7:30 PM, Chad Perrin c...@apotheon.net wrote: I'd like to be kept abreast of how you accomplish that in an automated manner. I too would like to do that with some projects of mine, but it's low enough on the priority list for my own stuff right now that I won't get to it for a while. If you end up doing the hard work of figuring out the best way to do it sooner than I'd get around to even starting, it could save me a lot of effort. It's all about me, after all. Right back at ya ;). That said, i do appreciate (==love/hate) the power of marketing and i would be very appreciative if someone would take over such a role :). How does the title of PR Manager sound to you :)? . . . kinda like that plea for assistance right there. i am by no means too proud to accept assistance, especially for areas i have little interest or skill in (PR being one of them - i value it but don't do it well). An acquaintance and I might be able to contribute to it in the meantime. We're interested in a C API for Fossil being available for production use some time in the next year or so, and as such might be motivated to hack on it. We'll have to discuss it and let you know if we're up for it, if you'd like to see some concerted contribution effort from us. The only requirement for code submissions is that a license/copyright waiver be on file with DRH, so that this code can be kept license-clean vis-a-vis fossil(1) (from which it borrows a huge (and growing) amount of code). Any sort of assistance, coding or not, is more than welcomed. As far as in the next year or so goes, my very rough guess is that it will take about until about the end of the year to get most of the fossil(1) functionality, minus the HTML and networking bits, working at a usable equivalent level. That might be pessimistic, though: as of a few moments ago, the formerly-missing low-level pieces of SCM machinery are in place and working in libfossil. The verify at commit bits were just added, which frees me up to experiment a bit more without concern about completely breaking my repo during experimentation/testing. Now it's mainly about tweaking those core APIs and adding the real functionality on top of that. e.g. you can save a wiki page _if_ you know how to brew the secret sauce (it's not hard, but it's a bit tedious), but the APIs for working with them at a higher level have yet to be developed (it's an ongoing process). If you decide you'd like to contribute code, the waiver can be found here: http://www.fossil-scm.org/index.html/doc/trunk/www/copyright-release.html and needs to be snail-mailed to DRH (address is in the form). -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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] Bikeshedding opportunity: back to the topic of libfossil's name
On Thu, Aug 22, 2013 at 08:46:43PM +0200, Stephan Beal wrote: On Thu, Aug 22, 2013 at 7:30 PM, Chad Perrin c...@apotheon.net wrote: An acquaintance and I might be able to contribute to it in the meantime. We're interested in a C API for Fossil being available for production use some time in the next year or so, and as such might be motivated to hack on it. We'll have to discuss it and let you know if we're up for it, if you'd like to see some concerted contribution effort from us. The only requirement for code submissions is that a license/copyright waiver be on file with DRH, so that this code can be kept license-clean vis-a-vis fossil(1) (from which it borrows a huge (and growing) amount of code). Any sort of assistance, coding or not, is more than welcomed. As far as in the next year or so goes, my very rough guess is that it will take about until about the end of the year to get most of the fossil(1) functionality, minus the HTML and networking bits, working at a usable equivalent level. That might be pessimistic, though: as of a few moments ago, the formerly-missing low-level pieces of SCM machinery are in place and working in libfossil. The verify at commit bits were just added, which frees me up to experiment a bit more without concern about completely breaking my repo during experimentation/testing. Now it's mainly about tweaking those core APIs and adding the real functionality on top of that. e.g. you can save a wiki page _if_ you know how to brew the secret sauce (it's not hard, but it's a bit tedious), but the APIs for working with them at a higher level have yet to be developed (it's an ongoing process). If you decide you'd like to contribute code, the waiver can be found here: http://www.fossil-scm.org/index.html/doc/trunk/www/copyright-release.html and needs to be snail-mailed to DRH (address is in the form). After discussing this with my collaborator, we'll send those off if we've decided to commit time to working on libfossil. Thanks. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.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] Bikeshedding opportunity: back to the topic of libfossil's name
On Thu, Aug 22, 2013 at 10:30 AM, Chad Perrin c...@apotheon.net wrote: On Thu, Aug 22, 2013 at 10:45:08AM +0200, Stephan Beal wrote: On Thu, Aug 22, 2013 at 4:34 AM, Chad Perrin c...@apotheon.net wrote: mirror should be set up on GitHub to boost its search engine ranking a little bit (with a prominent mention of its canonical version control repository being elsewhere using Fossil itself, of course). While OMG! lol. It never occurred to me to do such a thing, but you're right, it would probably be a good idea. I'd like to be kept abreast of how you accomplish that in an automated manner. I too would like to do that with some projects of mine, but it's low enough on the priority list for my own stuff right now that I won't get to it for a while. If you end up doing the hard work of figuring out the best way to do it sooner than I'd get around to even starting, it could save me a lot of effort. Did you say best way? I can't really help you there, but I do run the following script from time to time to keep 20+ fossil repos synced to private bitbucket repos. Github vs bitbucket should just be a matter of what the prefix portion of the remote path is -- it's all just git of course. https://gist.github.com/tifletcher/5399728 Caveats: - Everything is hard coded and is really just a rough draft / not intended for public consumption. - I'm calling 'tree' at the end because it helps me visualize / confirm what I just did. Please delete that line if 'which tree' returns nothing on your system. - You have to clean up the 'export' directory by hand at the moment (I don't personally like seeing rm -r in a script ... especially one that I run infrequently) On the other hand it has been working quite well for me with multiple pushes looking as expected on the remote for a while, so maybe it can be a starting point for you? And if you fix it please do fork and republish and let me know :) Best Regards, Themba ___ 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] Bikeshedding opportunity: back to the topic of libfossil's name
Mirroring of fossil to git ? I use http://core.tcl.tk/akupries/fossil2git/index On Thu, Aug 22, 2013 at 12:43 PM, Themba Fletcher themba.fletc...@gmail.com wrote: On Thu, Aug 22, 2013 at 10:30 AM, Chad Perrin c...@apotheon.net wrote: On Thu, Aug 22, 2013 at 10:45:08AM +0200, Stephan Beal wrote: On Thu, Aug 22, 2013 at 4:34 AM, Chad Perrin c...@apotheon.net wrote: mirror should be set up on GitHub to boost its search engine ranking a little bit (with a prominent mention of its canonical version control repository being elsewhere using Fossil itself, of course). While OMG! lol. It never occurred to me to do such a thing, but you're right, it would probably be a good idea. I'd like to be kept abreast of how you accomplish that in an automated manner. I too would like to do that with some projects of mine, but it's low enough on the priority list for my own stuff right now that I won't get to it for a while. If you end up doing the hard work of figuring out the best way to do it sooner than I'd get around to even starting, it could save me a lot of effort. Did you say best way? I can't really help you there, but I do run the following script from time to time to keep 20+ fossil repos synced to private bitbucket repos. Github vs bitbucket should just be a matter of what the prefix portion of the remote path is -- it's all just git of course. https://gist.github.com/tifletcher/5399728 Caveats: - Everything is hard coded and is really just a rough draft / not intended for public consumption. - I'm calling 'tree' at the end because it helps me visualize / confirm what I just did. Please delete that line if 'which tree' returns nothing on your system. - You have to clean up the 'export' directory by hand at the moment (I don't personally like seeing rm -r in a script ... especially one that I run infrequently) On the other hand it has been working quite well for me with multiple pushes looking as expected on the remote for a while, so maybe it can be a starting point for you? And if you fix it please do fork and republish and let me know :) Best Regards, Themba ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- 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 Tcl'2013, Sep 23-27, New Orleans, LA, USA @ http://www.tcl.tk/community/tcl2013/ EuroTcl'2013, July 6-7, Munich, GER ___ 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] Bikeshedding opportunity: back to the topic of libfossil's name
On Thu, Aug 22, 2013 at 9:50 PM, Andreas Kupries andre...@activestate.comwrote: Mirroring of fossil to git ? I use http://core.tcl.tk/akupries/fossil2git/index @Chad: Andreas wins :) i'll take a look at that when i'm feel snarky enough to export code from Fossil into the belly of my arch-nemesis. So far my own use of git has been limited to cloning from github and one brief project at work. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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] Bikeshedding opportunity: back to the topic of libfossil's name
On Thu, Aug 22, 2013 at 1:13 PM, Stephan Beal sgb...@googlemail.com wrote: On Thu, Aug 22, 2013 at 9:50 PM, Andreas Kupries andre...@activestate.com wrote: Mirroring of fossil to git ? I use http://core.tcl.tk/akupries/fossil2git/index @Chad: Andreas wins :) There was a competition ? Ah well. I will celebrate with a bit of chocolate ;) i'll take a look at that when i'm feel snarky enough to export code from Fossil into the belly of my arch-nemesis. So far my own use of git has been limited to cloning from github and one brief project at work. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- 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 Tcl'2013, Sep 23-27, New Orleans, LA, USA @ http://www.tcl.tk/community/tcl2013/ EuroTcl'2013, July 6-7, Munich, GER ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Bikeshedding opportunity: back to the topic of libfossil's name
Hi, all, The current list of upvoted names (no, Brad, urvogel's not one of them ;) for the on-going/up-coming library API includes (in my personal order of preference, but i'm not emotionally attached to these): - libfossil-scm and fossil(3) - libfossil - liblissof (fossil, backwards, because that's what this approach to Fossil is) i think that was about it? i _really_ liked the idea of the name (i've forgotten) which was a reference to a famously fake fossil, but i have been warned by one wiser than myself to avoid attempts at humorous names (his example being libiberty) and i tend to agree with him that such attempts eventually backfire in some way, shape, or form. (Side-note for history buffs: go look up the history of the mail reader Alpine's name, going all the way back to the first mail program (mail).) i'm still completely open for names but i keep finding myself writing libfossil and fossil(3) everywhere (i'm a doc fanatic), and would like to settle on one or the other relatively soon. Likewise, but of interest only to C coders, the main headers currently look like: #include fossil-scm/fossil.h // public API #include fossil-scm/fsl_internal.h // internal/pseudo-private API, will rename to fossil-internal.h eventually, for consistency If you C programmers feel strongly for some other convention, please speak up. You can peak at the code-related conventions here: http://fossil.wanderinghorse.net/repos/f2/doxygen/ (see the bottom half of that first page) and i am not emotionally attached to many of those, so feel free to suggest, e.g. better API name prefixes. The vast majority of things like that are trivial to refactor with a few lines of perl or sed (my main argument for keeping the repo db outside of the checkout dir, btw ;). Your opinions on the topic are much appreciated! -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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] Bikeshedding opportunity: back to the topic of libfossil's name
Ooh, I love bikeshedding. What about libfree as a portmanteau of lib, fossil, and three? I guess that crosses the line into humor a bit. More seriously though, fossil(3) is my favorite, but it does make it sound like it's an official part of the fossil project and actually implies, at least to me, that fossil(1) is built on top of it. Whether or not that implication is common and / or appropriate I'll leave to you to negotiate with Richard. On Wed, Aug 21, 2013 at 10:11 AM, Stephan Beal sgb...@googlemail.comwrote: Hi, all, The current list of upvoted names (no, Brad, urvogel's not one of them ;) for the on-going/up-coming library API includes (in my personal order of preference, but i'm not emotionally attached to these): - libfossil-scm and fossil(3) - libfossil - liblissof (fossil, backwards, because that's what this approach to Fossil is) i think that was about it? i _really_ liked the idea of the name (i've forgotten) which was a reference to a famously fake fossil, but i have been warned by one wiser than myself to avoid attempts at humorous names (his example being libiberty) and i tend to agree with him that such attempts eventually backfire in some way, shape, or form. (Side-note for history buffs: go look up the history of the mail reader Alpine's name, going all the way back to the first mail program (mail).) i'm still completely open for names but i keep finding myself writing libfossil and fossil(3) everywhere (i'm a doc fanatic), and would like to settle on one or the other relatively soon. Likewise, but of interest only to C coders, the main headers currently look like: #include fossil-scm/fossil.h // public API #include fossil-scm/fsl_internal.h // internal/pseudo-private API, will rename to fossil-internal.h eventually, for consistency If you C programmers feel strongly for some other convention, please speak up. You can peak at the code-related conventions here: http://fossil.wanderinghorse.net/repos/f2/doxygen/ (see the bottom half of that first page) and i am not emotionally attached to many of those, so feel free to suggest, e.g. better API name prefixes. The vast majority of things like that are trivial to refactor with a few lines of perl or sed (my main argument for keeping the repo db outside of the checkout dir, btw ;). Your opinions on the topic are much appreciated! -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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] Bikeshedding opportunity: back to the topic of libfossil's name
On Wed, Aug 21, 2013 at 7:30 PM, Themba Fletcher themba.fletc...@gmail.comwrote: What about libfree as a portmanteau of lib, fossil, and three? I guess that crosses the line into humor a bit. And sounds very GNU :/. More seriously though, fossil(3) is my favorite, but it does make it sound like it's an official part of the fossil project and actually implies, at least to me, that fossil(1) is built on top of it. Whether or not that implication is common and / or appropriate I'll leave to you to negotiate with Richard. It also has the drawback of basically prohibiting the name (eventually) fossil v3. i also can't write -lfossil(3) (thought it would be funny). So, yeah, fossil(3) is nice but too impractical. :( -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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] Bikeshedding opportunity: back to the topic of libfossil's name
On Wed, Aug 21, 2013 at 7:38 PM, Stephan Beal sgb...@googlemail.com wrote: On Wed, Aug 21, 2013 at 7:30 PM, Themba Fletcher themba.fletc...@gmail.com wrote: What about libfree as a portmanteau of lib, fossil, and three? I guess that crosses the line into humor a bit. And sounds very GNU :/. More seriously though, fossil(3) is my favorite, but it does make it sound like it's an official part of the fossil project and actually implies, at least to me, that fossil(1) is built on top of it. Whether or not that implication is common and / or appropriate I'll leave to you to negotiate with Richard. It also has the drawback of basically prohibiting the name (eventually) fossil v3. i also can't write -lfossil(3) (thought it would be funny). So, yeah, fossil(3) is nice but too impractical. :( -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users +1 for libfossil. I hate it when libraries have smart names requiring me to google for the package name to install. ___ 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] Bikeshedding opportunity: back to the topic of libfossil's name
On Wed, Aug 21, 2013 at 7:43 PM, Mark Janssen mpc.jans...@gmail.com wrote: +1 for libfossil. I hate it when libraries have smart names requiring me to google for the package name to install. BTW (should have noted this earlier): there is a filesystem called fossil, and while i have not found a libfossil naming conflict (==cursor googling), there might potentially be one, which is why i eventually tagged -scm to the name. But, again, i'm not emotionally attached to that. In fact, the name doesn't have to contain fossil, but i assume that'd be easier for everyone. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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] Bikeshedding opportunity: back to the topic of libfossil's name
On Wed, Aug 21, 2013 at 07:45:53PM +0200, Stephan Beal wrote: On Wed, Aug 21, 2013 at 7:43 PM, Mark Janssen mpc.jans...@gmail.com wrote: +1 for libfossil. I hate it when libraries have smart names requiring me to google for the package name to install. BTW (should have noted this earlier): there is a filesystem called fossil, and while i have not found a libfossil naming conflict (==cursor googling), there might potentially be one, which is why i eventually tagged -scm to the name. But, again, i'm not emotionally attached to that. In fact, the name doesn't have to contain fossil, but i assume that'd be easier for everyone. I definitely vote for the name libfossil. In fact, if you don't use it, I might have to encourage another Fossil library effort just so there's a libfossil that everyone will be able to find and remember. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.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] Bikeshedding opportunity: back to the topic of libfossil's name
Agreed. Hyphens in libnames don't look pleasing to my eye (fwiw), libfossilscm (cc ... -lfossilscm ...) might be next best to disambiguate from potential collision w/ another libfossil, though it too is pretty ugly looking. Brief search yields https://github.com/paulfitz/libfossil as second hit (after this very discussion). I also searched for libfsl, which appears to be claimed, I didn't look into what that project is. -bch On 8/21/13, Chad Perrin c...@apotheon.net wrote: On Wed, Aug 21, 2013 at 07:45:53PM +0200, Stephan Beal wrote: On Wed, Aug 21, 2013 at 7:43 PM, Mark Janssen mpc.jans...@gmail.com wrote: +1 for libfossil. I hate it when libraries have smart names requiring me to google for the package name to install. BTW (should have noted this earlier): there is a filesystem called fossil, and while i have not found a libfossil naming conflict (==cursor googling), there might potentially be one, which is why i eventually tagged -scm to the name. But, again, i'm not emotionally attached to that. In fact, the name doesn't have to contain fossil, but i assume that'd be easier for everyone. I definitely vote for the name libfossil. In fact, if you don't use it, I might have to encourage another Fossil library effort just so there's a libfossil that everyone will be able to find and remember. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- Brad Harder Method Logic Digital Consulting http://www.methodlogic.net/ http://twitter.com/bcharder ___ 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] Bikeshedding opportunity: back to the topic of libfossil's name
On Wed, Aug 21, 2013 at 06:03:50PM -0700, B Harder wrote: Agreed. Hyphens in libnames don't look pleasing to my eye (fwiw), libfossilscm (cc ... -lfossilscm ...) might be next best to disambiguate from potential collision w/ another libfossil, though it too is pretty ugly looking. Brief search yields https://github.com/paulfitz/libfossil as second hit (after this very discussion). I also searched for libfsl, which appears to be claimed, I didn't look into what that project is. As it happens, that GitHub hit appears to be someone's work on a library for Fossil SCM. Glancing across some of the code, it looks like it's a Ruby libfossil, so there'd be no practical namespace clash -- only a search engine namespace clash, which is a common case for libraries that do the same things in different languages anyway. I don't think that's much of an impediment. It currently has six commits, all from July, according to GitHub. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.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] Bikeshedding opportunity: back to the topic of libfossil's name
On Wed, Aug 21, 2013 at 08:05:58PM -0600, Chad Perrin wrote: On Wed, Aug 21, 2013 at 06:03:50PM -0700, B Harder wrote: Agreed. Hyphens in libnames don't look pleasing to my eye (fwiw), libfossilscm (cc ... -lfossilscm ...) might be next best to disambiguate from potential collision w/ another libfossil, though it too is pretty ugly looking. Brief search yields https://github.com/paulfitz/libfossil as second hit (after this very discussion). I also searched for libfsl, which appears to be claimed, I didn't look into what that project is. As it happens, that GitHub hit appears to be someone's work on a library for Fossil SCM. Glancing across some of the code, it looks like it's a Ruby libfossil, so there'd be no practical namespace clash -- only a search engine namespace clash, which is a common case for libraries that do the same things in different languages anyway. I don't think that's much of an impediment. It currently has six commits, all from July, according to GitHub. . . . and I found this on chisel: http://chiselapp.com/user/cutterpillow/repository/fossil-iOS/ There's a libfossil.cpp in the src directory of the source tree (requires anonymous login to view, naturally). That pretty much sums up my findings before web searches start devolving into stuff that doesn't really match, like ILU.lib - fossil-ice. It appears that all references to libfossil are, in fact, references to libraries related to Fossil SCM, specifically one for Ruby and one for iOS (unless my quick skim of each misinterpreted its purpose). I'd say the name should just be set in stone as libfossil now, and a mirror should be set up on GitHub to boost its search engine ranking a little bit (with a prominent mention of its canonical version control repository being elsewhere using Fossil itself, of course). While you're at it, if you're willing to bother, you could twit about it on Twitter and/or homestead the @libfossil name there. I wouldn't go so far as to recommend doing anything on Facebook, of course. That should about solve any potential namespace issues, by ensuring that other people checking to see if the name is taken will see your project and decide Yes, it does appear to be taken by an active project. I'll see if, at its current level of (in)completeness, it passes muster for inclusion in some of the Copyfree Initiative's lists (like copyfree licensed projects worthy of support or addition to the copyfree software listing), if you want to finally declare an official name for it as libfossil. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
