Claromentis Intranet Software Blog

As being a provider of an intranet software and its side solutions; we develop, deploy and deliver.. an intranet software… Recently one of our clients requested a quotation for an enhanced social networking platform to enable a possible collaboration of their consumers and staff under a single social networking platform. Personally, I think this is a great idea! Specially in an internet age, I can not think of any better solution to improve your public face than this. But there is one small problem… Our software was not developed while keeping the social networking platforms in mind. In other words, we are not the providers of a social networking platform. So how should we answer the client?

To find an answer to this, we did have an internal meeting today to narrow down our solutions and decided the following options:

1. Find a reliable third party social networking platform software, buy the software, customize it for the client and resell it.
2. Create a partnership with a third party company delivering social networking platforms and work on their software together with the owner of the software and deliver the result to the client. Consider the possibilities of learning the social networking platform development and combine it with our own product.
3. Develop our own bespoke social networking platform and deliver it to the client.
4. Say no.

The first three options have their pros and cons, while the 4th option is something we don’t like to go for, therefore I am going to focus on the first 3 options.

We found a perfect software delivering exactly what the client has asked for. It ticks almost every boxes based on the client’s requirements sheet. The software is open source and can be acquired with different pricing structures; starting from free up to good amount of money; depending on the package. In my opinion, the most expensive package, which is still relatively cheap based on its functionalities, is the one we should go for. The main reason behind my defence for this software is it works perfectly, delivers exactly what the client is asking for, the software itself is open source so we can modify it the way we want it, customize it to suit the client’s needs and deliver it to the client. The client gets what they want which works and we are happy to exceed the client’s expectations.

However there were several concerns about this option. The main concern, which is the main reason I am writing this article for is the software is actually an open source software. Some of our team members considered this as a negative point, because you may not get any support for the software. However what was forgotten in this concern was actually the provider of the software is releasing the core code of the software and any additional plug-ins (which we will need all of them) costs money. What took my attention was the word ‘open source’ made them think that this software may be unstable or developed by a student in couple of nights for fun and may well be forgotten by its provider. What I find strange is this thought would have never come to mind if the software was released by companies like Apple, Google, Sun or even Facebook or Digg team, just because they are a well known company and/or charging millions for it… For example, Mozilla may well stop supporting Firefox if it was not financially possible for them to keep the development of it.

But there were some other points which I found logical. Up-to-date, we delivered our own software which we know inside out. We are able to answer every question about it because we developed, deployed and delivered it. We are responsible to support our clients for the software they bought from us. What if something goes wrong with this third party software? OK, we have our own developers who can fix many problems, but to address a problem may take 5 minutes if the problem is occured on our software whereas it may well take 5 hours to address the same problem on some other software, if you are not familiar with it, and we are not talking about couple of hundred lines of code. This third party software is huge, so its’ codebase.

The other unspoken concern, which again I agree with, was the feeling we will have from the result. If the client loves this third party solution and sends their greetings to us, we would not feel the same level of satisfaction and proud as much as if they did the same for our intranet software, because simply what we delivered is NOT ours. We may have done a good job on finding the correct solution, customizing it and deploying it, but these are not actually what the client is requesting. These are expected standard results whereas the capabilities of the software are the requirement itself.

The second option is creating a partnership with a local social networking software developer and work on the actual software itself together. By doing this, there will be a mutual level of knowledge sharing. On our side, we will be learning how to deal with social networking management and implementation of these kind of platforms on corporate environments. And so many other stuff that I am not able to share with you for the moment. Because this will be a partnership, the provider will be reachable, therefore it will be possible for us to mash both of our solutions on one platform. Our client is already using our intranet solution and they are happy with it. Rather than giving them a complete new solution, which does not have the same look and feel as our own software, may be seen confusing to them (which is what may happen with the first solution, but again it is an open source software, so we should be able to customize it).

There is already one company we are considering to have a partnership for this project and we are in talks with them. I can not give you more details about this for the moment.

The third solution is a less likely to achive in a timescale given by the client. Our own software has years of experience and development history and as I said at the beginning of my article, it was not developed as a social networking platform. The strange thing is our software can do many of the client’s requirements on an individual basis, but was not designed to use these features on a public website with social networking ideas in mind.

You are probably asking “So, which option did you go for?“, well, we are still considering these and other  options and there are no decisions as of now. What I wanted to share with this article was what may be thought when we hear the word “open source“.

Can/should open source be considered as professional? How far professional and successful it can go? Can commercial products be open source and if they are open source, are they still commercial? Is open source turning out to be a marketing term because of the success of Mozilla Firefox?

Probably harder questions to answer than the meaning of life.

Clients, Communities and Case studies, Intranet Development and API, Open Source Intranets open source, Open Source Intranets, Social, Social Networking

For those of you that don’t already know, LAMP is an acronym for Linux - Apache – MySQL - PHP. It’s a collection of software that can be used to run servers and dynamic websites. It’s one of the most popular alternatives to Microsoft, and according to statistics provided by netcraft.com not only is Apache holding around 60% market share in the delivery/presentation of websites, but it’s thriving on the open source platforms and continuing to grow and compete (successfully) against Microsoft. It doesn’t take a genius to work out that any piece of software that can even compete (let alone lead) in its market against a super company like Microsoft has to have something special about it. Well, it’s no secret why the LAMP solution is so popular, it just works, it works well, it’s reliable, it’s robust, it’s resilient, and it’s free.

Without going into all of the nitty-gritty debates about why you should and shouldn’t base a corporate solution on an open source platform (there are enough of these debates on the Internet already), it’s not hard to realize why Claromentis run all of their development on the LAMP platform. The LAMP platform allows the development team to manage all aspects of their programming environment without relying on Microsoft to ensure the stability of that environment. Depending on who you talk to, avoiding Microsoft can be complete suicide, or a dream come true. Personally, I’m a believer in the statistics, and if 60% of the websites are running on Apache, my money is on that platform to deliver the best of everything. And I’ve never met a PHP developer who programs on anything else.

However, Claromentis doesn’t believe in limitations, so we let you decide which platform you wish to run the applications on. The Claromentis framework is compatible with LAMP, Windows, and ORACLE, so it works the way you do, integrating easily with your existing IT infrastructure.

For more information about Claromentis and the platforms it can run on, please contact sales@claromentis.com or call us on 01273 666 355

Open Source Intranets, Services, Technical Support, intranet applications apache, LAMP, Linux, mysql, open source, php, platform, windows

Designers are independent. In work, mindset and lifestyle. Yet in this Web age aren’t we losing independence? For most designers the first tool to start designing from is the Adobe suite, a quite impressive set of tools that help us to make our work easier. But don’t we rely too much on Adobe? For years people have been watching how Microsoft dominated the market. We lament that its applications are bloated and criticize its efforts to wipe away competitors. But instead of taking a stand, we continue to buy its products and we continue to moan.

We always have options. And in the design process we have them too. At the moment we don’t really know to what level open source applications can compete with Adobe. But with support, with independent minds and strong community involvement, the open source movement can grow. Competition is a part of the progress and so is the choice. We need to maintain a competitive arena in design. And we need good open source alternatives for the tools we use. Independent start-ups are the lifeblood of the industry and the breath of fresh air we all need.

But apart from Microsoft, Adobe and the latest computer system to run these applications, you may have problems setting up a professional open source environment which would perfectly meet your needs. We need better open source applications for designers. And we need to work together to produce them and then use them. Just think for a second: how many young designers can afford Adobe anyway? Do we not need a platform that supports us while we support it? Doesn’t open source represent the true spirit of design?

Nick Pretorius,
[Source]

General Intranet Posts, Visual Interface Adobe, Design, Microsoft, open source

I today read with real interest what apparently is the first of a total of 3 articles on intranet journal by Paul Chin. I encourage you to take a look.

The theme is choosing between Open Source and Commercial intranets. He discusses the ideas that we have reviewed for such a long time when developing Claromentis, a commercially available and supported intranet system that is developed on LAMP, coded entirely in PHP, is completely customizable and has a comprehensive API for external PHP developers to extend our systems to meet the needs of their clients.

We are currently working with 2 major corporations, one in the USA and one in the UK, where open source developers are working with our own core team to provide significant functionality on top of our framework.

I will be very interested to read Paul’s conclusion - and to see if we at Claromentis really do suppply, as we have alwasy argued - a third way.

General Intranet Posts, Open Source Intranets commercial, intranets, open source