Hi folks, regarding Personal Distributed Wiki - I’m syncing my JSPWiki contents over DropBox
Cheers, Siegfried Goeschl > On 12.02.2016, at 08:49, Derek Hohls <dho...@csir.co.za> wrote: > > Adrien > > Excellent points - but I still do not think a wiki is a tool that can/should > be installed locally for "casual" end-users (maybe my biases from 20+ years > in IT are showing here). Casual end users can - possibly - be trained to > contribute towards a shared wiki; but I am doubtful that they will really be > able to handle / manage / appreciate a locally installed version all on their > own. > > My own bias, because I work on multiple machines in different locations, all > with good network access, is towards hosted solutions; for example - > bitbucket repo can be used as just a wiki (with different syntax options if > desired) - public or private - with all of the revision options that that > entails (plus you can clone it to work locally & then push back changes if > really needed). > > We all have different needs - so I understand that in some situations a > "personal" wiki is desirable. > > Derek > >>>> Adrien Beau <adrienb...@gmail.com> 02/10/16 6:30 PM >>> > Derek Hohls wrote: >> >> I am very curious as to why people would even want to install a wiki on > their own machines (Windows or otherwise). > > You get a note-taking tool with text formatting, file attachments, > hyperlinks between notes, a full-text search engine, and no dependency on > network connectivity. You also get to keep past revisions, and can easily > backup the data (or even read it if the software fails): it's just > plain-text files. > > I've used JSPWiki this way for a few years (and was using MoinMoin in a > similar way before). Network connectivity was a major factor in choosing to > use a local instance: data connections in high-speed trains were quite > flaky, and clients often had restrictions on which web sites could be > accessed. Not storing client data on a remote server was also seen as a > bonus; the data is encrypted on my laptop. Network latency is also a bit > irritating when you've gotten used to a local server. > > The full-text search engine was not much of a criteria when I selected > JSPWiki, but it turned out to be much more useful than I envisioned, > especially on a local instance (no latency, very fast results). > > By the way, I selected JSPWiki based on its syntax. I wanted to use a wiki > that had a syntax close to what CollabNet TeamForge has, and it turns out > JSPWiki is the only one that matches (to the point that I wonder if > CollabNet forked JSPWiki a while ago). > > On Wed, Feb 10, 2016 at 1:26 PM, Derek Hohls <dho...@csir.co.za> wrote: > >> I am very curious as to why people would even want to install a wiki on >> their own machines (Windows or otherwise). >> >> To me, the main benefit of a wiki is that it is a shared repository of >> knowledge to which everyone has access. Such a wiki would be installed and >> maintained by the IT support team (or local guru, perhaps) on a server. >> Access is then as simple as "open your browser"! No barrier to entry at all. >> >> I think that for private note taking people are already using tools like >> Evernote or OneNote and I cannot see a "local" wiki replacing them. >> >>>>> Jason Morris <jason.mor...@sydney.edu.au> 02/08/16 10:22 AM >>> >> >> I tried (without success) to get people using JSPWiki internally in our >> faculty (Agriculture and Environment at the University of Sydney). At >> first, the majority were all gung-ho about using a wiki.. that was no >> problem. The barrier to entry was that they expected it to install like >> installing MS Word or something. Just a "one-shot and it just works" >> experience. As soon as I explained that they had to first install a servlet >> container (what's a servlet??!?!!) and fill out all this configuration >> stuff, they quickly lost interest. >> >> -- >> This message is subject to the CSIR's copyright terms and conditions, >> e-mail legal notice, and implemented Open Document Format (ODF) standard. >> The full disclaimer details can be found at >> http://www.csir.co.za/disclaimer.html. >> >> >> This message has been scanned for viruses and dangerous content by >> *MailScanner* <http://www.mailscanner.info/>, >> and is believed to be clean. >> >> >> Please consider the environment before printing this email. >> >> > > -- > This message is subject to the CSIR's copyright terms and conditions, e-mail > legal notice, and implemented Open Document Format (ODF) standard. > The full disclaimer details can be found at > http://www.csir.co.za/disclaimer.html. > > This message has been scanned for viruses and dangerous content by > MailScanner, > and is believed to be clean. > > Please consider the environment before printing this email. > > > -- > This message is subject to the CSIR's copyright terms and conditions, e-mail > legal notice, and implemented Open Document Format (ODF) standard. > The full disclaimer details can be found at > http://www.csir.co.za/disclaimer.html. > > This message has been scanned for viruses and dangerous content by > MailScanner, > and is believed to be clean. > > Please consider the environment before printing this email.
