The Tao of Open Source: Minimum Action for Maximum Gain

This study is an examination of features of the four most popular digital library open source software packages against a set of predetermined criteria that is deemed to be essential for the development of a digital library. While analysing and identifying the similarities, differences, strengths, and weakness of the open source software packages, it is indicated that open source digital library software still lacks certain functionalities that are perceived to be important. Each software package has its own individual strengths and weaknesses that will appeal to organizations and stakeholders with different needs. The study is expected to help those library professionals, seriously interested in implementing a digital library by providing a checklist to evaluate how well a particular software fits into their specific implementation requirements. Certain good features of the four open source software packages have also been pointed out via a comparison analysis.

In this paper, we study oligopolistic competition between closed and open source softwares. By intersecting existing economic contributions on open source, we propose a two stage game with perfect information and product di¤eretiation in which producers firstly set softwares quality, then they determine prices (constrained at zero for open source programs). In doing this, we explicitly model lock-in e¤ects, network externality components of software quality as well as knowledge accumulation in software use and implementation. With respect to a monopolistic benchmark case, we argue that in duopoly a pro- prietary sofware producer facing an open source software will reduce its selling price whether: (i) its network of users is larger than open sources one and its consumers are largely experienced on its program, (ii) it has a small network of un-skilled consumers. In opposition, after open source softwares emergence, proprietary software price does augment if proprietary software users form a large, but poorly skilled network. Fur- thermore, we show that, in all above cases, proprietary software quality increases because of the existence of a open source alternative to a previouisly monopolistic program. Finally, by modeling knowledge accumulation processes through di¤erence equations, we show that the ratio between closed and open source programs opportunity costs of software learning and deployment plays a crucial role in shaping market outcomes. Until an open source software remains too complex and technical for unskilled or time-scarse users, a shared market solution in which both softwares are adopted is predicted. In contrast, if opportunity costs in learning and understanding open source programs are remarkably low, or at least equal to opportunity costs of a closed source software, then a open source dominance outcome (i.e. all software are open ones) phases out.

The Move to the Middle: Convergence of the Open-Source and Proprietary Software Industries

A lot misinformation and mystery surrounds the topic of Open Source software. The conceptual misunderstanding of software is fostered, in some respects, by a lack of understanding within the professional ranks of the computer field. There are many different views of Open Source software today, based upon ones perspective. After about 20 years of evolution, the position of Open Source in our economy still has not coalesced. Few seems to understand whether Open Source is free software for running a computer (i.e., Linux) or just a way to obtain some software products without giving Microsoft ones money. “There is one thing stronger than all the armies in the world and that is an idea whose time has come” - Victor Hugo any view Open Source (OS) software as just a free alternative to proprietary software. The term does not mean that there is no cost associated with its procurement, although some vendors do provide free versions. The word “free” usually means the freedom to copy, modify, or distribute the software. One must be very careful when applying this broad, general meaning to Open Source software. There are many different Open Source licenses in use and it is imperative that users acquaint themselves with the legal ramifications of dealing with intellectual property rights. ` Open Source software should be viewed as a viable alternative in many software selection processes. Recently, the news has portrayed the report of India's Kerala state moving to Linux and OpenOffice for its 2,724 high schools. Likewise, OpenOffice is replacing Microsoft Office in many schools districts around the US. With tight school budgets, school superintendents are realizing significant cost savings by using the OpenOffice products for their campuses. Products such as OpenOffice may not be 100% compatible with their current proprietary counterpart, but for many applications, compatibility is not the issue. The price and the software license management of proprietary packages may be overwhelming.

Open Source Software (OSS) projects rely on the efforts of thousands of software developers. The sustainability and diversity of these communities are two important factors for the longterm viability of OSS communities. This paper reviews the research on OSS sustainability and diversity. Drawing on the findings of measures on sustainability and diversity, we applied a number of the established metrics to the Android Open Source Project and found that over a third of all contributions originate from Google. Surprisingly, in 2015 we saw a decrease in the total number of contributors within the Android project. Findings from our analysis highlight the importance of sustainability and diversity for the development of OSS.

Nowadays, Open Source Software (OSS) is widely used and plays a crucial role in the software industry. OSS development is a knowledge-intensive activity that requires very high levels of domain knowledge and needs to maintain the knowledge sharing environment. OSS project develop by the contribution of OSS members on its virtual community where every member can communicate and develop software together. To create new open source software needs the motivation of all members, the resources embedded in the relationship in community and the coordination of members as a virtual team to complete the OSS tasks. This study focused on the knowledge sharing in the OSS project community under the individual motivation, virtual community and virtual team perspectives. We analyzed 304 surveys collected from OSS communities and found that the extrinsic motivation, some perspectives of virtual community such as social interaction, identification and perspective of virtual team – team cognition have a direct impact on knowledge sharing of OSS project community. The study found that all the perspectives of virtual community have a significant impact on team cognition, and therefore have indirect effect on the knowledge sharing in OSS. Moreover, our results indicated that knowledge sharing has a significant impact on project performance. Implications for theory building, practical management and future research are also discussed.

Open-source software abbreviated as OSS is computer software that is available with source code and is provided under a software license that permits users to study, change, and improve the software. For the commercial software the source code and certain other rights are normally reserved for copyright holders,i.e. the company who developes the software. A group of people in a collaborative manner often developes the Open source software, not under the roof of a large organization. This strategy makes open source software cheap, reliable and modifiable if needed. In this context we shall discuss mainly the features of Open Source Software, differences of open source and free software and open source software movement in Indian perspective.

Open Source vs. Proprietary Software: Competition and Compatibility

Cloud computing is a Service Oriented Architecture which reduced information technology overhead for the end-user and provide great flexibility, reduced total cost of ownership, on-demand services and many other things [1]. Hence it delivered all IT related capability as services rather than product .Services on cloud are divided into three broad categories: Software as a Service, Infrastructure as a Service & Platform as a Service. Same as services cloud is also classified as Private Cloud, Public Cloud & Hybrid Cloud. Private cloud is increasingly become popular between every private organization either large or small wants .To deploy public or private cloud there are many open source software available some are Eucalyptus, Nimbus, OpenStack, Open Nebula Cloud stack and Amazon Web Services .This paper, I provide a study of the main open source software such as Eucalyptus, OpenStack and OpenNebula for cloud implementation. It is believe that the comparison presented in this paper would benefit developers in selecting best open source Software.

In The Truth About OSS-FRAND, David Kappos and Miling Harrington argue that it is both permissible and desirable to charge FRAND (“fair, reasonable, and non-discriminatory”) royalties on open source software (“OSS”) that is incorporated into a standard containing standard-essential patents (“SEPs”). In arguing that OSS and FRAND are compatible in this way, Kappos and Harrington take the position that when standard-setting communities intentionally incorporate OSS-licensed code into a standard, it is the royalty-free status of open source that should give way, not the payment of the FRAND-based royalty. This Comment examines the Open Source Definition (“OSD”), the text of OSD-compliant licenses, and discussions surrounding their creation to conclude, contrary to Kappos and Harrington, that essentially every OSD-compliant open-source license includes a royalty-free patent grant, which precludes the imposition of FRAND-based royalties. Standard-setting organizations that wish to charge FRAND royalties ultimately have the same option that commercial enterprises have when dealing with open source: respect OSD licenses, including their implied royalty-free patent grants, or create an alternative commercial license that conveys no patent grant.

This chapter discusses various ways that open source software (OSS) methods of software development interact with the corporate world. The success achieved by many OSS products has produced a range of effects on the corporate world, and likewise, the corporate world influences the success of OSS. Many times, OSS products provide a quality product with strong support, providing competition to the corporate model of proprietary software. OSS has presented the corporate world with opportunities and ideas, prompting some companies to implement components from the OSS business model. Others have formed companies to support and distribute OSS products. The corporate world, in turn, affects OSS, from funding labs where OSS is developed to engaging in intellectual property disputes with OSS entities. The consumer of software is sometimes baffled by the differences in the two, often lacking understanding about the two models and how they interact. This chapter clarifies common misconceptions about the relationship between OSS and the corporate world and explains facets of the business models of software design to better inform potential consumers.

Open source software (OSS) is computer software that has its underlying source code made available under a licence. This can allow developers and users to adapt and improve it (Raymond, 2001). Computer software can be broadly split into two development models: • Proprietary, or closed software, owned by a company or individual. Copies of the binary are made public; the source code is not usually made public. • Open-source software (OSS), where the source code is released with the binary. Users and developers can be licenced to use and modify the code, and to distribute any improvements they make. Both OSS and proprietary approaches allow companies to make a profit. Companies developing proprietary software make money by developing software and then selling licences to use the software. For example, Microsoft receives a payment for every copy of Windows sold with a personal computer. OSS companies make their money by providing services, such as advising clients on the GPL licence. The licencee can either charge a fee for this service or work free of charge. In practice, software companies often develop both types of software. OSS is developed by an ongoing, iterative process where people share the ideas expressed in the source code. The aim is that a large community of developers and users can contribute to the development of the code, check it for errors and bugs, and make the improved version available to others. Project management software is used to allow developers to keep track of the various versions. There are two main types of open-source licences (although there are many variants and subtypes developed by other companies): • Berkeley Software Distribution (BSD) Licence: This permits a licencee to “close” a version (by withholding the most recent modifications to the source code) and sell it as a proprietary product; • GNU General Public Licence (GNU, GPL, or GPL): Under this licence, licencees may not “close” versions. The licencee may modify, copy, and redistribute any derivative version, under the same GPL licence. The licencee can either charge a fee for this service or work free of charge. Free software first evolved during the 1970s but in the 1990s forked into two movements, namely free software and open source (Berry, 2004). Richard Stallman, an American software developer who believes that sharing source code and ideas is fundamental to freedom of speech, developed a free version of the widely used Unix operating system. The resulting GNU program was released under a specially created General Public Licence (GNU, GPL). This was designed to ensure that the source code would remain openly available to all. It was not intended to prevent commercial usage or distribution (Stallman, 2002). This approach was christened free software. In this context, free meant that anyone could modify the software. However, the term “free” was often misunderstood to mean no cost. Hence, during the 1990s, Eric Raymond and others proposed that open-source software was coined as a less contentious and more business-friendly term. This has become widely accepted within the software and business communities; however there are still arguments about the most appropriate term to use (Moody, 2002). The OSMs are usually organised into a network of individuals who work collaboratively on the Internet, developing major software projects that sometimes rival commercial software but are always committed to the production of quality alternatives to those produced by commercial companies (Raymond, 2001; Williams, 2002). Groups and individuals develop software to meet their own and others’ needs in a highly decentralised way, likened to a Bazaar (Raymond, 2001). These groups often make substantive value claims to support their projects and foster an ethic of community, collaboration, deliberation, and intellectual freedom. In addition, it is argued by Lessig (1999) that the FLOSS community can offer an inspiration in their commitment to transparency in their products and their ability to open up governmental regulation and control through free/libre and open source code.

Problems setting. Legal restrictions in working with open sources often concern intellectual property, and the possibility of establishing such restrictions is an important problem. The Berkeley Protocol states that investigators should be aware of any intellectual property permissions they may need to lawfully publish, distribute, and/or otherwise use the information they gather during the investigation. Analysis of recent researches and publications. The use of information from open sources is subject to both legal and technical restrictions, such as third-party rights and platform rights, the validity of the license granted to the platform providing access, the technical requirements of the platforms, the purpose of use of the works, etc. The application of many OSINT methods may encounter legal restrictions, so these restrictions require systematization, additional analysis and description in accordance with the state of technology development. Purpose of the research is to describe and systematize the main legal risks associated with intellectual property when using information from open sources. Article’s main body. To achieve the goal of the article, the following widespread methods of OSINT are considered: text and data mining, image analysis, video analysis, audio analysis, face recognition, geolocation, improvement and use of open-source software products. Conclusions and prospects for development. The following risks of OSINT activities are identified according to the probability of their occurrence: – high degree: violation of copyright of its owner due to the difficulty of identifying that owner and the difficulty of managing the distribution of information in the global network; use of works or products (even from authoritative or familiar resources for the user) that violate the intellectual property rights of third parties; violation of intellectual property rights in one country without violation of the same rights in another country due to the lack of international unified laws; violation of platform license terms due to differences in such licenses and careless reading; violation of the license terms of the open source product due to differences in such licenses or incorrect (compared to the license) interpretation of the term “open source” by the user; ignoring the collection of permissions from a large number of parties involved; – medium degree: violation of the copyright of its owner due to the use of pirated works; violation of commercial secret rights; – low degree: violation of trademarks rights of faces; violation of patent rights for products used for a particular investigation due to lack of knowledge of such rights. To reduce such risks, the most obvious are the following actions: unification of national laws; implementation of special legal regimes for the use of information from open sources at the national and/or international levels; unification of license agreements of large platforms on a voluntary basis; training researchers in intellectual property issues; intensifying the implementation of technological solutions of intellectual property rights management, such as blockchain, encryption of works and watermarks; and noncommercial use of intellectual property rights, without going beyond the scope corresponding to the intended purpose.

Over the past decade, numerous computer-assisted retrosynthesis reaction prediction methods have been reported in the chemical literature, several of which are also shared as open-source code. Reports of integrating these modern open-source retrosynthetic prediction techniques into the chemical education classroom, however, is largely absent. This article describes our efforts to teach a computer-assisted retrosynthesis workshop series using open-source reaction prediction software and methods. In addition to three workshops on selected open-source reaction prediction methods, the series included workshops on Python programming and introductory cheminformatics using the RDKit cheminformatics toolkit. A pre and post survey was distributed to better understand participant familiarity and workshop outcomes. Participants indicated that they had minimal experience with cheminformatics, and open-source retrosynthesis software, however after the workshop series they indicated increased familiarity, interest, and desire to pursue additional training related to open-source retrosynthesis software and methods. We conclude this article with our experiences and ideas for future improvements. The workshop materials and code are available with an open source license, and educators are encouraged to adapt and improve the lessons (https://github.com/UA-Libraries-Research-Data-Services/retrosynthesis).

Requirement of software is necessary for the process system-computer simulation. ln reality, costly of software is one of restriction for the software development. However, the costly constraint can be solved using open source software such as Scilab and OpenOffice. The goa lof this article formulates user friendly program of the process system. Scilab program by Graphical User Interface (GUI) and interaction with Open Office-Cale for the data-base physical property. Scilab program has been listed in this article and algorithme of rhe program as the methodology has been presented in this article. Results of the simulation program indicate goodfinding for the process system. Kata kunci : scilab; open office, simulasi komputer; oss (open source sortuare), Antar Muka Pcngguna - Graphical User Interface (GUI).