Design to last
Intranet wiki - pilot Print E-mail
Written by Daniel Leiderman-Gueller   
Wednesday, 19 November 2008 00:00
After preparing the short list as detailed in my previous post, we had a meeting for understanding the requirements for our organization. The result of this meeting was that although we have a basic idea of the requirements we need to get our hands dirty and try a wiki before we really understand the concepts.

The chosen pilot is a small marketing segment that has a need to publish small information snippets where each snippet is part of a larger information base, but each snippet has its own information. Additionally, the information is very structured and can be defined using a form so we can test the requirement of creating information from a form.

Last Updated on Saturday, 10 January 2009 13:52
Read more... [Intranet wiki - pilot]
 
Intranet wiki - searching for alternatives Print E-mail
Written by Daniel Leiderman-Gueller   
Sunday, 16 November 2008 00:00
Researching for wiki alternatives, as continuation of my previous post, I've gathered a short list of the possible alternatives. The main reasons for this list are to ease the selection process. There are many engines, with many capabilities so trying to compare all of them will take too long. The short list selects some of the top rated engines for CMS / wiki and tries to see how each one suits the requirements for my project.

The engines are:

  • Twiki
  • Tikiwiki
  • Bitweaver
  • Egroupware
Last Updated on Saturday, 10 January 2009 13:41
Read more... [Intranet wiki - searching for alternatives]
 
Intranet wiki Print E-mail
Written by Daniel Leiderman-Gueller   
Thursday, 13 November 2008 00:00
Just before starting the documentation of new development, I started to look for a more user friendly way of sharing information with other group in our company. The options available to me were:
  1. Word documents
  2. Wiki
  3. CMS
Read more... [Intranet wiki]
 
Open source vs commercial - support Print E-mail
Written by Daniel Leiderman-Gueller   
Sunday, 09 November 2008 00:00

In reply to this post on the quality of open source software, I received comments from a colleague that although the reasoning on software quality is valid, the main difference lays in the user perception of the software.

According to him, users perceive open source software of lower quality and commercial software of higher quality due to single factor - support. The reason most people will favor commercial software is the fact that there is a point for asking support and having a "back" for any kind of problem that might arise. Although I'm not the usual user, I can understand the presented argument but I disagree.

People use programs they are accustomed to, unless there is a reason for change. So most users will keep using whatever software they started to use up to the point where there is the possibility of change. Change can occur due to several factors:

  • Change in the company one is employed
  • Cost considerations
  • Experience in other open source software
  • Curiosity


Each one of those changes can occur in separate or combined. For example a company can switch to OpenOffice due to cost factors, and the employees can switch at home knowing the software and trying to reduce costs as well. So the perception of software is not limited to support, but also of actual exposure to the possible options.

Regarding support of commercial software vs. open source, there are commercial support solutions as well, like the consultants directory for OpenOffice. So having support is possible, its just a bit more complicated.

As you can see, there are several hurdles for open source software, but support isn't the major one.

Last Updated on Saturday, 08 August 2009 12:20
 
<< Start < Prev 11 12 13 14 15 16 17 18 19 Next > End >>

Page 14 of 19