August, 2004归档文章

开放知识管理:从开源运动所学到的

由 徐永久 发表于 2004年08月25日 13:32。

在美国信息科学技术学会杂志第11期上,Yukika Awazu 和 Kevin C. Desouza 发表了该论文,网上只有摘要。

人们或许可以说知识工作的未来已经在开源运动的工作方式中得到展示。由德鲁克[1968],达文波特,Thomas , Cantrell[2002] 以及其他人讨论的结果,知识工作的定义是一群通过交换经验和技巧的专家们来开发产品和服务。而这恰恰是开源社区的工作方式。本文通过对开源社区的观察,洞察到了提高组织中的知识管理实践的一些方法。
目的是诱使组织内部的专家把封闭的知识管理议程转换为开源运动的代表。

恐翻译不好,提供原文如下:

“One might argue that the future of knowledge work is manifested in how open-source communities work. Knowledge work, as argued by Drucker ([1968]); Davenport, Thomas, and Cantrell ([2002]); and others, is comprised of specialists who collaborate via exchange of know-how and skills to develop products and services. This is exactly what an open-source community does. To this end, in this brief communication we conduct an examination of open-source communities and generate insights on how to augment current knowledge management practices in organizations. The goal is to entice scholars to transform closed knowledge management agendas that exist in organizations to ones that are representative of the open-source revolution.”

Source: Journal of the American Society for Information Science and Technology, 55, 11 (2004) pp. 1016-1019

领导力神话:成功知识管理的秘密

由 徐永久 发表于 2004年08月13日 17:28。

“The Myth of Leadership ” 的作者 Jeff Nielsen 认为传统的等级式的组织架构扼杀了知识管理,要让员工和部门之间无缝的信息共享,是一个立志成为真正的知识管理组织的最大挑战。然而, Jeff Nielsen 认为这种说法只不过是知识管理的一种娇艳的打扮而已。

他提出一种新的管理模式,就是基于个体点的思考。在他的以个体点为基础的世界里,信息共享和决策制定都是开放的,透明的过程。

(more…)

开源软件的10个特点

由 徐永久 发表于 2004年08月10日 11:24。

Organizations are now starting to embrace open source solutions as a cost-effective alternative to these closed source products. Open source solutions differ from closed source in many ways, one of which is cost. Open source solutions are typically free of charge, although some companies such as IBM, Oracle and Hewlett Packard (HP) often sell versions of open source software with related maintenance. The following 10 features distinguish open source:

来源: http://www.report.cpr.ca.gov/cprrpt/issrec/stops/it/so10.htm

  1. Free Redistribution: The software can be given as part of a package with other applications;
  2. Source Code: The code must either be distributed with the software or easily accessible;
  3. Derived Works: The code can be altered and distributed by the new author under the same license conditions as the product on which it is based;
  4. Integrity of the author’s source code: Derived works must not interfere with the original author’s intent or work;
  5. No discrimination against persons or groups;
  6. No discrimination against fields of endeavor: Distributed software cannot be restricted in who can use it based on their intent;
  7. Distribution of license: The rights of the program must apply to all to whom the program is re-distributed without need for an additional license;
  8. License must not be specific to a product; Meaning that an operating system product cannot be restricted to be free only if used with another specific product;
  9. License must not contaminate other software; and License must be technology-neutral.[1]
  10. Open source software is developed with the source code freely available; anyone can use the software, and make changes to it as necessary. Typically changes are then made available back to the open source community using a common methodology for change control. In contrast to open source, most software development companies sell their products at a specific cost, but do not allow the user to see or modify the source code.

The advent and acceptance of open source software represents a significant shift in the software development and procurement cycle. It is sometimes difficult to think of downloading a free version of software from the Internet and then using it in a mission-critical environment rather than buying software from a major software vendor. There are arguments to be made that open source can be a better choice for some mission-critical implementations than closed source. The following are some potential reasons for choosing open source:

More secure due to the extreme scrutiny of the source code before being deployed;
Can be run in multiple environments (i.e. Unix, Linux and Microsoft);
May be less expensive to manage (no maintenance contracts or upgrade costs); and Often less vulnerable to viruses.[2]

Endnotes
[1] Bruce Perens, “The Open Source Definition,” http://www.opensource.org/docs/definition.php (last visited March 8, 2004).
[2] David A. Wheeler, “Secure Programming for Linux and UNIX HOWTO,” Chapter 2.4 “Is Open Source Good for Security?” http://www.dwheeler.com/secure-programs/Secure-Programs-HOWTO.html (last visited June 2, 2004).
[3] C/Net, “How Linux Saved Amazon Millions,” http://news.com.com/2100-1001-275155.html?legacy=cnet (last visited June 14, 2004).
[4] David A. Wheeler, “Why Open Source Software/Free Software (OSS/FS)? Look at the Numbers!” (June 8, 2004), http://www.dwheeler.com/oss_fs_why.html (last visited June 14, 2004).
[5] Bill Welty, chief information officer, California Air Resources Board, “Air Resources Board Open Source Software Initiatives,” http://www.arb.ca.gov/oss/oss.htm (last visited June 14, 2004).
[6] Interview with Allen Lung, systems architect, California Franchise Tax Board, Sacramento, California (May 3, 2004).
[7] Interview with Troy Kallas, account executive, Novell Corporation, Sacramento, California (June 15, 2004).
[8] Oracle Corporation, “Oracle on Linux,” http://www.oracle.com/technologies/linux/ (last visited June 2, 2004); and IBM, “Linux at IBM,” http://www-1.ibm.com/linux/ (last visited June 14, 2004).
[9] David A. Wheeler, “Why Open Source Software /Free Software (OSS/FS)? Look at the Numbers!”