Quoting optimus <[EMAIL PROTECTED]>: > 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. > which is actually true. there are some programs and applications that have certain inate proprietariness. raymund mentions this point very clearly.
> 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? > there is generally the believe that architectural tools (compilers, Internet daemons and operating systems should be open source) while specialized tools (accouting, HR software) are better left proprietary. take the case of CRM, different companies will have different ways of implementing CRM and each implementation may not be relevant to other users. i believe this is probably one reason why GNUe is moving very slowly with regards to this. > 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)? > Google earns because it is popular. it is poplular because it uses bleeding eahc search enginer technology. if it open sourced the search enginer the would loose their competative advantage. therefore, google won't open source their enginer. (unless they probably invent a better algorithm or engine). > 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? > if you use open source tools like gcc, php and friend the products of theises tools need not be open sourced. take cisco for example, they use gcc to compile their IOS. but, they don't need to open source it. > 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? > > just make sure you read the licenses carefully.know the different between GPL and LGPL and BSD. raymund's catheral and bazaar actually answer all your questions. ----------------------------------------------- William Emmanuel S. Yu Ateneo Campus Network Group (AteneoCNG) email : wyu at ateneo dot edu web : http://CNG.ateneo.net/cng/wyu/ phone : +63(2)4266001-4186 GPG : http://CNG.ateneo.net/cng/wyu/wyy.pgp _ 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]
