On Mon, Feb 24, 2014 at 10:04:33PM +0100, Stephan Beal wrote: > On Mon, Feb 24, 2014 at 9:37 PM, Chad Perrin <c...@apotheon.net> wrote: > > > Is there some reason this kind of thing shouldn't be maintained in a > > Fossil wiki instead of Google docs? > > > > Yeah, i see the irony in it, but Fossil's just not the tool for what i want > in this case: simplicity and real-time collaboration[1]. i pdate docs with > uncommon frequency (you're just seeing the "public docs" there, not the > associated API docs and the related th1ish docs which get updated as i > find/fix bugs via libfossil), and i'd be firehosing my repos with doc > commits continually were they stored there.
Do you plan to move the stuff into a Fossil wiki, eventually? I find Google Docs problematic enough that I typically avoid them -- and, when there's nowhere else to get the information, I just make a local plaintext copy, so I don't have to deal with Google Docs any more than necessary. > > [1] after you've worked in GDocs for long enough you begin to feel that > others can watch everything you type, even outside of gdocs. I agree with Martin G.: that's scary. . . . and if you're using enough Google stuff, some people *are* probably "watching" everything you type (for some definition of "watching" that involves running keyword identifying and text pattern analysis routines). -- 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
