Re: [fossil-users] managing documentation in Fossil?
[Drifting (even further) off topic here...] On Fri, 20 Apr 2012 14:25:59 -0400 Miles Fidelman mfidel...@meetinghouse.net wrote: Mike Meyer wrote: On Fri, 20 Apr 2012 10:26:26 -0700 Andreas Kupriesandre...@activestate.com wrote: On 4/20/2012 7:34 AM, Mike Meyer wrote: ... Things like architectural diagrams wind up there, and ... I like to program my diagrams, instead of drawing them. Easier to change, and the code (aka text) is nicer to version than some binary blob. If I don't need to work on such collaboratively, I'll use graphviz for the same reasons. But google docs is easier to get other people to contribute to. Don't know about google docs - no real version control. Unusable for anything serious, like a multi-author paper or proposal. I always end up sharing Word Documents, with change tracking, via email. Gets ugly with more than a few people. I'm still exploring how google docs fits into a small team. So far, I've just used it for one-page diagrams, and it's worked well there. Word, on the other hand - never again. The differences between implementations - different programs, different versions of the same program, the same version on different platforms - is just to painful. In one case, I saw word documents that would cause some *machines* to crash when opened. Other machines (presumably using the same version of word) would open them just fine. Saving the doc unaltered on those machines created a doc that didn't cause other machines to crash. have you tried MSFT's answer to google docs (SkyDrive + Office Apps)? I've used it myself (I live in the win ecosystem) for on-the-go Word, PowerPoint, and OneNote editing and it works great as a replacement. Tomek ___ 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] managing documentation in Fossil?
On Fri, 20 Apr 2012 09:50:02 -0400 Miles Fidelman mfidel...@meetinghouse.net wrote: Just started using Fossil for a new project - it just seems so much easier than git, and the integrated wiki and ticketing system just simplifies things a lot. Yup. A question to the group: To what extent are any of you using Fossil for managing documentation associated with projects - any or all of developer, user, administrator, sys admin (configuration files, configuration notes, shell scripts, cfengine/puppet/chef recipes, tickets, checklists, procedures, user account info, logbooks), etc.? I use the wiki for developer docs for clients that don't already have a preferred tool for those, or a preferred SCM other than fossil. Docs for the users/admins wind up stored in fossil, but normally aren't done in the wiki. There's a tension here in that I also use Google Docs for writing documentation. Things like architectural diagrams wind up there, and get links in the wiki. If the client has a google id, I'll give them write access to such, so there's a pull to keep everything there. I'm still working that division out. mike -- Mike Meyer m...@mired.org http://www.mired.org/ Independent Software developer/SCM consultant, email for more information. O ascii ribbon campaign - stop html mail - www.asciiribbon.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] managing documentation in Fossil?
Thanks to all who wrote! Gour.. the asciidoc pointer, and asciidoc-fossil glue are awesome! Stephan, Stephan Beal wrote: Sorry for the brevity - my hand is broken and i can't type worth a damn... Been there. Sucks big time. You have my sympathies. Sorry to ask Recently i started moving my wikis to dedicated wiki repos - a custom front-end served by a fossil back-end using the JSON API: http://fossil.wanderinghorse.net/wikis/ Those wikis could just as easily be hosted in their main source repos (also fossil), but because i use a custom wiki grammar (Google Code) which is rendered client-side and does not render properly when used via the native fossil UI, i prefer to keep the pages in their own repos (which i then hide behind my own UI), That front-end is nice. I don't suppose the code is available for perusal/use? Welcome aboard, Thanks! And, after choosing a less-than-mainstream tool, it sure is reassuring to find out how active, welcoming, and responsive the Fossil community seems to be! (Including a shoutout from someone I haven't seen in years!) Best, Miles -- - 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 -- In theory, there is no difference between theory and practice. In practice, there is. Yogi Berra ___ 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] managing documentation in Fossil?
On 4/20/2012 9:50 AM, Michael L. Barrow wrote: On 04/20/2012 09:32 AM, Stephan Beal wrote: i'm normally thrilled to get suggestions and whatnot, but i can't type well enough to program for a while (probably still several weeks). Nonetheless, if you'd like to contribute, that can of course be arranged. Maybe you can get a typist like Richard Stallman... http://en.wikipedia.org/wiki/Speech_recognition_in_Linux -- Andreas Kupries Senior Tcl Developer Code to Cloud: Smarter, Safer, Faster™ P: 778.786.1122 F: 778.786.1133 andre...@activestate.com http://www.activestate.com Learn about Stackato for Private PaaS: http://www.activestate.com/stackato http://www.eurotcl.tcl3d.org/ - EuroTcl 2012, July 7-8 , Munich, Germany. http://www.tcl.tk/community/tcl2012/ - Tcl'2012, Nov 12-16, Chicago, IL, USA. ___ 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] managing documentation in Fossil?
On Fri, 20 Apr 2012 10:26:26 -0700 Andreas Kupries andre...@activestate.com wrote: On 4/20/2012 7:34 AM, Mike Meyer wrote: ... Things like architectural diagrams wind up there, and ... I like to program my diagrams, instead of drawing them. Easier to change, and the code (aka text) is nicer to version than some binary blob. If I don't need to work on such collaboratively, I'll use graphviz for the same reasons. But google docs is easier to get other people to contribute to. mike -- Mike Meyer m...@mired.org http://www.mired.org/ Independent Software developer/SCM consultant, email for more information. O ascii ribbon campaign - stop html mail - www.asciiribbon.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] managing documentation in Fossil?
On 4/20/2012 10:34 AM, Mike Meyer wrote: On Fri, 20 Apr 2012 10:26:26 -0700 Andreas Kupriesandre...@activestate.com wrote: On 4/20/2012 7:34 AM, Mike Meyer wrote: ... Things like architectural diagrams wind up there, and ... I like to program my diagrams, instead of drawing them. Easier to change, and the code (aka text) is nicer to version than some binary blob. If I don't need to work on such collaboratively, I'll use graphviz for the same reasons. Ah, even higher level. With automatic layouting. But google docs is easier to get other people to contribute to. Fair point. -- Andreas Kupries Senior Tcl Developer Code to Cloud: Smarter, Safer, Faster™ P: 778.786.1122 F: 778.786.1133 andre...@activestate.com http://www.activestate.com Learn about Stackato for Private PaaS: http://www.activestate.com/stackato http://www.eurotcl.tcl3d.org/ - EuroTcl 2012, July 7-8 , Munich, Germany. http://www.tcl.tk/community/tcl2012/ - Tcl'2012, Nov 12-16, Chicago, IL, USA. ___ 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] managing documentation in Fossil?
Mike Meyer wrote: On Fri, 20 Apr 2012 10:26:26 -0700 Andreas Kupriesandre...@activestate.com wrote: On 4/20/2012 7:34 AM, Mike Meyer wrote: ... Things like architectural diagrams wind up there, and ... I like to program my diagrams, instead of drawing them. Easier to change, and the code (aka text) is nicer to version than some binary blob. If I don't need to work on such collaboratively, I'll use graphviz for the same reasons. But google docs is easier to get other people to contribute to. Don't know about google docs - no real version control. Unusable for anything serious, like a multi-author paper or proposal. I always end up sharing Word Documents, with change tracking, via email. Gets ugly with more than a few people. Right now, the WikiPedia (or more accurately, MediaWiki) model seems to be really effective - what with support for multiple authors, change tracking, discussions, etc. Starts to fall down if you want to manage a structured document or generate printed versions as an output. Miles -- In theory, there is no difference between theory and practice. In practice, there is. Yogi Berra ___ 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] managing documentation in Fossil?
[Drifting off topic here...] On Fri, 20 Apr 2012 14:25:59 -0400 Miles Fidelman mfidel...@meetinghouse.net wrote: Mike Meyer wrote: On Fri, 20 Apr 2012 10:26:26 -0700 Andreas Kupriesandre...@activestate.com wrote: On 4/20/2012 7:34 AM, Mike Meyer wrote: ... Things like architectural diagrams wind up there, and ... I like to program my diagrams, instead of drawing them. Easier to change, and the code (aka text) is nicer to version than some binary blob. If I don't need to work on such collaboratively, I'll use graphviz for the same reasons. But google docs is easier to get other people to contribute to. Don't know about google docs - no real version control. Unusable for anything serious, like a multi-author paper or proposal. I always end up sharing Word Documents, with change tracking, via email. Gets ugly with more than a few people. I'm still exploring how google docs fits into a small team. So far, I've just used it for one-page diagrams, and it's worked well there. Word, on the other hand - never again. The differences between implementations - different programs, different versions of the same program, the same version on different platforms - is just to painful. In one case, I saw word documents that would cause some *machines* to crash when opened. Other machines (presumably using the same version of word) would open them just fine. Saving the doc unaltered on those machines created a doc that didn't cause other machines to crash. Right now, the WikiPedia (or more accurately, MediaWiki) model seems to be really effective - what with support for multiple authors, change tracking, discussions, etc. Starts to fall down if you want to manage a structured document or generate printed versions as an output. It's certainly proved itself in the real world. mike -- Mike Meyer m...@mired.org http://www.mired.org/ Independent Software developer/SCM consultant, email for more information. O ascii ribbon campaign - stop html mail - www.asciiribbon.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
