Friends, I am working on business solution implementation on open source product called Kaltura. Kaltura is a media management solution and has loads of features that compel any business to take a peek into it. More-over this is the only complete end-to-end open source software available to handle digital assets. But it comes with its own head ache.
Considering its open source, its understandable. I feel, handling these would ensure you the success in your open source product implementation.
1. In my opinion, before adopting any open source software, build the capability to deal with the inconsistency bundled in the open source software.
2. I would avoid involving external consultants for 2 reasons.
a. I am not sure, they would bring necessary expertise on to table
b. I fear that there would be little ownership, they will not see big picture of my business (neither I am interested to share it all)
3. Alternative to that is to build the team that is capable of debugging - This is very important, In my opinion its the key.
4. Use intelligent guess - like how do you implement given the scenario, this would take to find the problem
5. Also, I would advise to keep any customization minimum, keep the dependency on open source product to minimum, not that I dont like them, but it gives me the flexibility to adopt to new solution, when it arrives
6. If there is large chunk of functionality needed, then I would propose build it as an external module and integrate with open source product, rather than extending it.
7. Last but not least, not all requirements are the candidates for customization or development. This is where business analysis comes into picture. We need to model the business requirement in different or novel way understanding the constraints of the product in focus. This is another key to success.
The most annoying issue in open source implementation is not fixing, but in finding it. The community forums do their bit, but in case of Kaltura, hardly there is involvement from experts. Will keep updating ...
Take care.
Considering its open source, its understandable. I feel, handling these would ensure you the success in your open source product implementation.
1. In my opinion, before adopting any open source software, build the capability to deal with the inconsistency bundled in the open source software.
2. I would avoid involving external consultants for 2 reasons.
a. I am not sure, they would bring necessary expertise on to table
b. I fear that there would be little ownership, they will not see big picture of my business (neither I am interested to share it all)
3. Alternative to that is to build the team that is capable of debugging - This is very important, In my opinion its the key.
4. Use intelligent guess - like how do you implement given the scenario, this would take to find the problem
5. Also, I would advise to keep any customization minimum, keep the dependency on open source product to minimum, not that I dont like them, but it gives me the flexibility to adopt to new solution, when it arrives
6. If there is large chunk of functionality needed, then I would propose build it as an external module and integrate with open source product, rather than extending it.
7. Last but not least, not all requirements are the candidates for customization or development. This is where business analysis comes into picture. We need to model the business requirement in different or novel way understanding the constraints of the product in focus. This is another key to success.
The most annoying issue in open source implementation is not fixing, but in finding it. The community forums do their bit, but in case of Kaltura, hardly there is involvement from experts. Will keep updating ...
Take care.
Nice blog RP. Please keep updating it.
ReplyDeleteAs you know, we faced one major issue with kdp skin yesterday and because of it the player was not loading. We suspected the issue with cloud front url, but it actually got resolved when we reverted the skin file to the original one.
Not sure exactly the reason but suspecting it could be file corruption issue, but it took lot of time and team effort to find and fix it.
You helped us at the right time when we lost hope on the player.
Thanks
Shylesh