The Enterprise Committer: When Your Employee Develops Open-Source Code on the
Company Payroll
,----[ Quote ]
| This is not occurring in a bastion of open-source freedom; Marechal's
| company (which is a household word) has no open-source policy. Everything
| is proprietary. "As far as upper management knows, it's a 100 percent
| Microsoft shop (except for all the BSD and Linux boxes the geeks
| keep sneaking in through the back door). The decision to open source
| my application was purely a one-off. A fluke," says Marechal.
|
| It isn't a fluke for everyone. Some companies are actively
| participating in open-source projects, with some of their
| programming staff working part- or full-time on such software.
| The best known of these is perhaps IBM, which developed Eclipse,
| then successfully spun it off into an open-source project--yet has
| a significant number of developers working on the project.
`----
http://www.cio.com/technology/development/opensource/open_source_on_company_time.html?CID=28487
Related to:
Finding New Code
,----[ Quote ]
| "Too much time is wasted re-implementing code that someone else has
| already done, for the sole reason it's faster than finding the other
| code... This seems like just what we need to unify the open-source
| community, leading to an actual common repository of unique code,
| and ending the cycle of unnecessary reimplementing."
`----
http://developers.slashdot.org/article.pl?sid=07/02/05/1313253&from=rss
|
|
