scholarly journals Role of Open Source Software in Modern Development of Enterprise Information Systems

2021 ◽  
Vol 21 (2) ◽  
pp. 16-22
Author(s):  
A.A. Shinkarev ◽  
Keyword(s):  
Open Source ◽  
Open Source Software ◽  
Source Code ◽  
Enterprise Information ◽  
Enterprise Information Systems ◽  
Software Products ◽  
Modern Development ◽  
Software Product ◽  
The Moment ◽  
Product Package

At the moment there are many open source software products and packages, and their number is increasing every day. So it can be concluded that publishing source code is becoming more and more popular in the world of software development. When publishing the source code of a software solution or software package for use in the developer community, special attention should be given to the license type – this affects which scenarios will be available for use of the published package or software solution. It is also necessary to draw up full and detailed documentation and decide on the ways to promote the published package among developers. The purpose of the study was to justify the feasibility and necessity of publishing software products, packages and libraries for their use by other developers to build their own systems and services. The author meant to describe the major open source licenses, identify their features and differences, and those situations for which this or that type of license is suitable, as well as to demonstrate the need of writing documentation and describe ways to promote and popularize published software products, packages, and libraries in the developer community. Materials and methods. The paper considers official license documents describing conditions of use, reproduction, and distribution. The author analyzes the main ways and means to promote open source software products. Results. The article substantiates the relevance of publishing and using the source code of a software product, package or library. The author describes the main provisions of the most common licenses and gives advice on choosing the type of license when publishing source code for free use. The necessity of writing documentation for the published software product is substantiated. The article also describes some of the ways to promote published packages, such as the choice of name, speaking at conferences, and publishing articles with case studies.

scholarly journals Open Plot Project: an open-source toolkit for 3-D structural data analysis

Solid Earth ◽  
2011 ◽  
Vol 2 (1) ◽  
pp. 53-63 ◽  
Author(s):  
S. Tavani ◽  
P. Arbues ◽  
M. Snidero ◽  
N. Carrera ◽  
J. A. Muñoz
Keyword(s):  
Spatial Distribution ◽  
Data Analysis ◽  
Open Source ◽  
Open Source Software ◽  
Source Code ◽  
Structural Data ◽  
Geological Modelling ◽  
Analysis Tools ◽  
Transect Analysis ◽  
Selection Of

Abstract. In this work we present the Open Plot Project, an open-source software for structural data analysis, including a 3-D environment. The software includes many classical functionalities of structural data analysis tools, like stereoplot, contouring, tensorial regression, scatterplots, histograms and transect analysis. In addition, efficient filtering tools are present allowing the selection of data according to their attributes, including spatial distribution and orientation. This first alpha release represents a stand-alone toolkit for structural data analysis. The presence of a 3-D environment with digitalising tools allows the integration of structural data with information extracted from georeferenced images to produce structurally validated dip domains. This, coupled with many import/export facilities, allows easy incorporation of structural analyses in workflows for 3-D geological modelling. Accordingly, Open Plot Project also candidates as a structural add-on for 3-D geological modelling software. The software (for both Windows and Linux O.S.), the User Manual, a set of example movies (complementary to the User Manual), and the source code are provided as Supplement. We intend the publication of the source code to set the foundation for free, public software that, hopefully, the structural geologists' community will use, modify, and implement. The creation of additional public controls/tools is strongly encouraged.

Establishing Ethos on Proprietary and Open Source Software Websites

2014 ◽  
pp. 915-935
Author(s):  
Kevin Brock
Keyword(s):  
Operating System ◽  
Software Development ◽  
Open Source ◽  
Open Source Software ◽  
Image Manipulation ◽  
Public Acceptance ◽  
Web Browser ◽  
Software Products ◽  
Tremendous Amount ◽  
Rhetorical Appeals

The increasing prominence and variety of open source software (OSS) threaten to upset conventional approaches to software development and marketing. While a tremendous amount of scholarship has been published on the differences between proprietary and OSS development, little has been discussed regarding the effect of rhetorical appeals used to promote either type of software. This chapter offers just such an examination, focusing its scrutiny on the websites for three pairs of competitors (operating system, Web browser, and image manipulation program). The means by which the OSS websites promote their programs provide a significant set of insights into the potential trajectory of OSS development and its widespread public acceptance, in terms of both its initial philosophy and its perceived alternative nature to traditional software products and models.

Review of Open Source Software (OSS)

2012 ◽  
pp. 26-40
Author(s):  
Bhasker Mukerji ◽  
Ramaraj Palanisamy
Keyword(s):  
Developing Countries ◽  
Public Sector ◽  
Open Source ◽  
Open Source Software ◽  
Low Cost ◽  
Source Code ◽  
Developed Countries ◽  
Economic Resources ◽  
Large Pool ◽  
Public Sector Organizations

The popularity of Open Source Software (OSS) in developing countries is quiet evident from its widespread adoption across government departments and public sector organizations. The use of OSS saves economic resources of cash starved countries, provides an opportunity to promote e-government, and to utilize their resources in other sectors. Many developing countries have a large pool of skilled developers who can modify the source code of the OSS at a very low cost. Many governments in developing and developed countries have switched to OSS which probably encourages others to follow the trend. It was not possible to follow the adoption trend in all the developing countries but the usage of OSS in countries like India, Brazil, and Venezuela provides us an insight. The successful adoption of OSS requires thorough analysis of its advantages as well as the issues associated with it. This chapter will provide an overview of OSS, characteristics of OSS developers, and their motivation to volunteer by contributing in OSS projects, followed by the advantages and issues associated with OSS.

Key Concepts and Definitions of Open Source Communities

2010 ◽  
pp. 753-760
Author(s):  
Ruben van Wendel de Joode ◽  
Sebastian Spaeth
Keyword(s):  
Software Development ◽  
Open Source ◽  
Open Source Software ◽  
Online Communities ◽  
Source Code ◽  
Professional Organizations ◽  
Large Numbers ◽  
Key Concepts ◽  
Open Source Communities ◽  
Do So

Most open source software is developed in online communities. These communities are typically referred to as “open source software communities” or “OSS communities.” In OSS communities, the source code, which is the human-readable part of software, is treated as something that is open and that should be downloadable and modifiable to anyone who wishes to do so. The availability of the source code has enabled a practice of decentralized software development in which large numbers of people contribute time and effort. Communities like Linux and Apache, for instance, have been able to connect thousands of individual programmers and professional organizations (although most project communities remain relatively small). These people and organizations are not confined to certain geographical places; on the contrary, they come from literally all continents and they interact and collaborate virtually.

Open Source Web Portals

2012 ◽  
Vol 4 (4) ◽  
pp. 16-32
Author(s):  
Vanessa P. Braganholo ◽  
Bernardo Miranda ◽  
Marta Mattoso
Keyword(s):  
Open Source ◽  
Open Source Software ◽  
Source Code ◽  
Web Portals ◽  
Web Portal ◽  
Easy Task ◽  
User Community

Open source software is required to be widely available to the user community. To help developers fulfill this requirement, Web portals provide a way to make open source projects public so that the user community has access to their source code, can contribute to their development, and can interact with the developer team. However, choosing a Web portal is not an easy task. There are several options available, each of them offering a set of tools and features to its users. The goal of this article is to analyze a set of existing Web portals (SourceForge.net, Apache, Tigris, ObjectWeb, and Savannah) in the hopes that this will help users to choose a hosting site for their projects.

Structural Epochs in Software

2014 ◽  
Vol 5 (2) ◽  
pp. 1-12 ◽  
Author(s):  
Patrick A Gray ◽  
Bo Sandén ◽  
Phillip Laplante
Keyword(s):  
Open Source ◽  
Open Source Software ◽  
Object Oriented ◽  
Hierarchical Organization ◽  
Software Projects ◽  
Software Products ◽  
Topological Features ◽  
Method Class ◽  
Structural Levels ◽  
Structural Shifts

A way to measure the complexity of object-oriented software involves topological features of the code's hierarchical organization at the method, class, package, and component levels. Sangwan et al (2008) suggested that as certain software products evolve, this complexity shifts from lower to higher structural levels, or vice-versa. They studied three widely used open source software programs and showed that these structural shifts called “epochs” were present and suspected that this phenomenon was pervasive. To support or refute this assertion, 30 open source programs were studied and structural shifts in complexity were found significantly in 27 of them. In those projects where no complexity shift was evident, no refactoring had occurred. These findings further suggest that in large, open source software projects, when refactoring occurs a shifting in complexity from one level to another will occur.

Open Source in Government

2011 ◽  
pp. 1287-1290 ◽  
Author(s):  
D. Berry
Keyword(s):  
Open Source ◽  
Open Source Software ◽  
General Public ◽  
Source Code ◽  
Computer Software ◽  
Free Software ◽  
Software Projects ◽  
Software Companies ◽  
Develop Software ◽  
Software Distribution

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.

Community Customers

2011 ◽  
pp. 510-521 ◽  
Author(s):  
Jeroen Hoppenbrouwers
Keyword(s):  
Life Cycle ◽  
Open Source ◽  
Community Participation ◽  
Open Source Software ◽  
Product Life Cycle ◽  
Development Process ◽  
Sales Process ◽  
Software Product ◽  
Specific Community

This chapter discusses the role of the project/product community in the open source product life cycle. It outlines how a community-driven approach affects not only the development process, but also (and more importantly) the marketing/sales process, the deployment, the operation, and in general the resulting software product. Participation in the community is essential for any organization using the product, leading to the concept of a community customer. Specific community participation guidelines are given to organizations and individuals who deploy and use open source software, further develop it, or offer lifetime services on the product.

scholarly journals The Penguin Has Entered the Building: The Commercialization of Open Source Software Products

2008 ◽  
Vol 19 (2) ◽  
pp. 292-305 ◽  
Author(s):  
Andrea Fosfuri ◽  
Marco S. Giarratana ◽  
Alessandra Luzzi
Keyword(s):  
Open Source ◽  
Open Source Software ◽  
Software Products

scholarly journals Open Source Paradigm: A Synopsis of The Cathedral and the Bazaar for Health and Social Care

2016 ◽  
Vol 23 (2) ◽  
pp. 488
Author(s):  
Tim Benson
Keyword(s):  
Open Source ◽  
Open Source Software ◽  
Social Care ◽  
Source Code ◽  
Comprehensive Description ◽  
The Third ◽  
It Impacts ◽  
Health And Social Care ◽  
Software Engineers ◽  
Closed Source

Background: Open source software (OSS) is becoming more fashionable in health and social care, although the ideas are not new. However progress has been slower than many had expected.Objective: The purpose is to summarise the Free/Libre Open Source Software (FLOSS) paradigm in terms of what it is, how it impacts users and software engineers and how it can work as a business model in health and social care sectors.Method: Much of this paper is a synopsis of Eric Raymond’s seminal book The Cathedral and the Bazaar, which was the first comprehensive description of the open source ecosystem, set out in three long essays. Direct quotes from the book are used liberally, without reference to specific passages. The first part contrasts open and closed source approaches to software development and support. The second part describes the culture and practices of the open source movement. The third part considers business models.Conclusion: A key benefit of open source is that users can access and collaborate on improving the software if they wish. Closed source code may be regarded as a strategic business risk that that may be unacceptable if there is an open source alternative. The sharing culture of the open source movement fits well with that of health and social care.

Sign in / Sign up

Export Citation Format

Share Document