After 2,5 years with MPA2 we came to realize which parts of the program a program owner should have open source to to do their own customization needs. So in MPA3 we opened up the most requested ones that would not directly interfer with the main source that protects vital functionalities of the program.
This now seems to have been a smart move. Customers can customize the things needed to do regular "business changes" when needed, and when special customization is needed they ask for a quote, get it, and we do it within the specified timeframe given. Works like a charm.
The DANGER of giving out the source code to "anyone" is that when something happens that needs attention in the form of support, WE, the creators of the software have no way of knowing what was done to the source by the customer, hence creating a confusion whereas to who is to "blame" or who is to "fix what was broken". It is a very cheap insurance and a way to create a comfort level that both sides can accept the terms of.
This is how we can be so damn good at support, having a MPA3 uptime that is unheard of in our industry, and custom work done that is unsurpassed by anyone.
PS. Check out the custom work we just did for
www.adultlounge.com v4.0 !
