Don't ask to ask, just ask | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
My main point was that many times issues of training, maintenance and feature enhancements aren't considered when you look at a problem and say, "That's not so hard." I know I've been guilty of that false hubris in the past. Whether open source is appropriate in this case is another issue. If you're creating a framework that provides some basic functionality that others can customize (like a specialized application server), then open source can be a good idea. (IME open source software works best when it's infrastructure.) This is particularly true for attracting VARs. The permanent availability of the framework can be a strong argument for a VAR to invest the time and resources necessary to learn the framework and possibly adapt existing software to fit in or use it. Regarding installation keys: beats me, although I doubt people will miss them :-) Chris In reply to Re: open source, training/maintenance
by lachoy
|
|