Hello pluggers! Is open-sourcing a software really the way to go in the future? I've read Eric Raymond's musings on this topic, and he seems to believe that there are different opportunities where both open-source and proprietary apps can thrive and coexist.
a. What apps should remain proprietary? b. What apps should be open-sourced? c. Any rule-of-thumb, considerations, and criteria to use in deciding whether to open-source or not? d. Should all proprietary apps gradually be open-sourced? Here are some scenarios that's been bugging my mind: 1. I've read that the code behind Google's search engine is proprietary. Is this an advantage? Should Google open-source this in the future? Is the proprietary nature of the search engine an advantage for Google as a business entity? Is the proprietary nature of Google's search engine a disadvantage to users? Can Google capitalize on this proprietary software to establish a monopoly and lock-in clients who advertise in Google (via sponsored links)? 2. A consulting firm develops software for a business entity using open-source tools. Should the code be open-sourced? If the code is open-sourced, who should own the code, the consulting firm or the business entity? 3. Is there any distinction between using open-source "tools" (eg. Gtk, GPL Qt) and open-source software (eg. KDE or Gnome libraries) by a consulting firm who plans to develop apps for a business entity? Regards, mikol _ Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph To leave: send "unsubscribe" in the body to [EMAIL PROTECTED] Fully Searchable Archives With Friendly Web Interface at http://marc.free.net.ph To subscribe to the Linux Newbies' List: send "subscribe" in the body to [EMAIL PROTECTED]
