Pages

Saturday, August 7, 2010

OTRS – Release of 3.0 Beta version

Recently, came across this announcement from the OTRS team for the beta release of OTRS 3.0.

With a new Ajax-powered interface, OTRS claims to improve its tickets dispatch performance by as much as 30%. Amongst other things, the new user-centered design features an enhanced New Ticket dashboard, a dynamic Ticket Zoom view, enhanced search, an interactive Global Ticket overview, ticket archiving, and accessibility compliance.

In the past, I have been involved in multiple installations of OTRS at major client enterprises and some of the very useful OTRS features were:
  • Multiple methods of ticket generation like web-based, email and phone
  • Auto-routing of tickets (especially of email tickets) to concerned organizational departments for resolution
  • Escalation mechanisms to handle ticket resolution delays; we extended this feature to multiple level of escalations and associated management reports
  • Definition of work-time schedules for the organizational staff to care of shift schedules, holidays etc.
  • Bulk action methods to respond in case of emergencies
  • Maintenance of detailed audit trail of every customer interaction
  • Comprehensive Knowledge Base which grows with regular usage (FAQs section)
  • Quick response templates to improve productivity; most useful for auto-notifications
  • Best-in-class reporting mechanisms to generate planned as well as on-demand reports
And of course, we had great fun integrating OTRS with SugarCRM!!

Hope to see the GA version of OTRS 3.0 soon; meanwhile enjoy this Youtube file on the beta version:



P.S. If you are looking to install OTRS on windows then, here's a very useful reference on youtube

Thursday, August 5, 2010

Business Primer on Open Source Licensing

The world of open source licensing can get pretty complex for the uninitiated. Similar products can be using different licenses and thus, can have different implications around its usage. However, at the heart of the various open source licenses are two concerns -
  1. Specifying the rights of the users to use and modify the software
  2. Detailing how the modified works of the software can be distributed
Before, we go into discussion of some of the most popular open source licenses; there are three basic license templates which drive the subsequent definitions:
  1. Copyright License - This is as we understand in everyday usage, is designed to restrict the use of the particular product unless authorized in some manner. Typical example include most of the commercial software like Windows etc
  2. Copyleft License - This is an exact opposite of Copyright - in the sense that Copyleft promotes active use of the product by others with no restrictions on sharing and modifying; but with the condition that any modifications to the product are also distributed under the same license.
  3. Non-Copyleft License - This is very similar to the Copyleft license except for the condition where the users can modify the software and re-distribute under any license of their own choice.
Let us start with the dominant copyleft licenses. The most common license here is the GPL (GNU General Public License). According to Black Duck Software tracking of FOSS Licenses, GPL under all its variations account for nearly 64% of the market share. The most commonly accepted form is GPL2 with close to 48% market share.

The origins of GPL are closely rooted in the Copyleft principle, thus all derivative products need to be compulsorily GPLed. This makes GPL as a complex license to interpret. For example, you download a product with license under GPL, make certain changes to it like may be adding new modules and would like to re-distribute it. Sure, you can do that but all of your changes / additions to the earlier product now needs to follow the same license i.e. GPL. The philosophy behind GPL is to keep Open Source software ‘Open’.
However, for ease of understanding, some rules of thumb when using GPL are (as referenced here):
  1. You can charge as much as you want for distributing, supporting, or documenting the software, but you cannot sell the software itself.
  2. The rule-of-thumb states that if GPL source is required for a program to compile, the program must be under the GPL. Linking statically to a GPL library requires a program to be under the GPL.
  3. The GPL requires that any patents associated with GPLed software must be licensed for everyone's free use.
  4. Simply aggregating software together, as when multiple programs are put on one disk, does not count as including GPLed programs in non-GPLed programs.
  5. Output of a program does not count as a derivative work. This enables the gcc compiler to be used in commercial environments without legal problems.
  6. Since the Linux kernel is under the GPL, any code statically linked with the Linux kernel must be GPLed. This requirement can be circumvented by dynamically linking loadable kernel modules. This permits companies to distribute binary drivers, but often has the disadvantage that they will only work for particular versions of the Linux kernel.
The last point above required that anything that statically links to GPL, must also be GPLed. However, this made the implementation of Proprietary applications on Linux difficult and was partly the driver behind the origins of the LGPL (Lesser GPL) license. LGPL differs from the GPL in that it allows the linking of software licensed under it to non-GPL software. Originally designed for use with programming libraries, the LGPL is also a popular choice for dual-licensed software by commercial companies.

Another recent extension of GPL is the GNU Affero General Public License (AGPL). AGPL extends the condition for source code provision for even the Softwares which are offered 'As a Service' using cloud computing.

At the other end of the spectrum are the Non-Copyleft licenses with complete freedom around the licensing for derived works. The most common form of this kind is the BSD-style licenses. Per BSD site, a BSD style license is a good choice for long duration research or other projects that need a development environment that:
  1. Has near zero cost
  2. Will evolve over a long period of time
  3. Permits anyone to retain the option of commercializing final results with minimal legal issues.
Somewhere in-between these two ends lie the other licenses; one of the most popular being the Apache 2.0 license. In fact Google has chosen Apache 2.0 as the default for all the software it open-sources. Although Apache 2.0 is permissive like BSD, but (unlike BSD) actually happens to mention the rights under copyright law and gives a license under those rights.

Over a period of time, with the increase in the number of open source licenses, multiple efforts have been made to standardize the various licenses by introducing specific buckets for the same. Open Source Initiative has come out with the following categories:
  1. Licenses that are popular and widely used or with strong communities (9)
  2. Special purpose licenses (3)
  3. Licenses that are redundant with more popular licenses (9)
  4. Non-reusable licenses (24)
  5. Other/Miscellaneous licenses (5)
The discussion around the above groups and their constituents is available here

With the increasing acceptance of Open Source in the Enterprise business community, it is imperative that we have better awareness around the various Open Sources licenses and more importantly, the knowledge to make an informed decision in choosing a particular license when needed.

References:

Wednesday, August 4, 2010

Sugar 6 Release - And the debate around being Open Source

Recently, SugarCRM announced the release of Sugar 6 version for its popular CRM application. However, the release has also seen significant amount of debate around the actual meaning of 'Open Source' and if Sugar is truly Open or just a commercial model with some 'Open' inclinations. Firstly, here's the announcement as covered by eCRM guide.

One of the main features of the new release is a revamped user interface which is made available only to the paid users of SugarCRM i.e. under the Professional and Enterprise licenses. The open source version i.e. the 'Community' version does not benefit with this new interface although it gets some parts of the other 'new' features.

Per Slashdot reports, Martin Schneider, senior director of communications at SugarCRM, said:

"Open source doesn't mean free and was never really meant to mean free. Open source runs through everything we do, it enables us to be transparent and gives customers more power. We are an open source company and it's why we're better than proprietary companies."

This triggered a string of coverage around the Sugar 6 release and SugarCRM's 'Open Source' claim, notably -

  1. http://news.slashdot.org/story/10/07/13/2358224/SugarCRM-6-Released-But-Is-It-Open-Source
  2. http://www.zdnet.com/blog/open-source/sugarcrm-6-community-and-commercial-diverge/6850
  3. http://ostatic.com/blog/has-sugarcrm-violated-open-source-principles
  4. http://www.readwriteweb.com/enterprise/2010/07/sugarcrm-releases-new-version.php

And finally, the official company response from the CEO of SugarCRM, Larry Augustin:

http://www.crmoutsiders.com/2010/07/15/some-thoughts-on-open-from-sugarcrm-ceo-larry-augustin/

As an active user of the SugarCRM community edition for close to 3 years, I do agree with most of the difficulties faced by the community version users like

  1. No Access to some of the most useful modules like Reports, Forecasts etc.
  2. Problems in upgrading to higher versions with custom modules
  3. No dedicated support from SugarCRM for community version

Although time, we did benefit from the partner network of SugarCRM where, we could easily locate vendors / publishers of third-party plug-ins to meet most of our requirements.

But at the very broad level, I would tend to agree with Larry's comments about his views around the 'Open' culture. The fact that SugarCRM provides complete source code to all its paid customers with freedom to deploy and modify as needed...is a very important consideration in its claim of being 'Open'. Also, Open Source is about better software development by sharing source code with your customers and/or with the wider community. However, it doesn’t stop you from charging for your work.

At the same time, am very certain that this will not be the end of the discussion around the real meaning and application of Open Source...