3 ms·
What are you trying to achieve by releasing the source code? Improved quality, by having it scrutinized by lots of other coders/hackers/devs (if you are lucky
by flashgordon 19y ago
What are you trying to achieve by releasing the source code? Improved quality, by having it scrutinized by lots of other coders/hackers/devs (if you are lucky and release it under GPL).
Good will and Trust?
Perception of "more for the buck"?
- hbien 19y agoThe web language/framework I would like to use (Python/Django) doesn't have any sort of source code protection for it. There's no compiled byte code or source code encoder product. But if it's an advantage to release the source code, that shouldn't matter. If it's a mistake to release the source code, I would probably use PHP (I'm still comfortable programming with PHP from my day job, but I'd be happier with Python).
- flashgordon 19y agoActually another startup patient/kind enough to talk to me (:D) is in a very similar predicament to yours. They are infact building a CMS by aggregating several open source tools (eg word-press and so on). Their main reason for open-sourcing their CMS itself was so the increased scrutiny. However the main concern is how reproducible is your idea? If you are still at the very young stage, and your main strength really is in your IP. But having said that, if your customer base is such that they would be happy to fix problems themselves given the source, that could save you a lot in support-mullah. But that may depend on the kind of license you release your source code under. What do you folks think? or am I thinking about it the wrong way?