scholarly journals Lesson Development for Open Source Software Best Practices Adoption

Author(s):  
Mateusz Kuzak ◽  
Jen Harrow ◽  
Rafael C. Jimenez ◽  
Paula Andrea Martinez ◽  
Fotis E. Psomopoulos ◽  
...  
GigaScience ◽  
2019 ◽  
Vol 8 (9) ◽  
Author(s):  
Peter Georgeson ◽  
Anna Syme ◽  
Clare Sloggett ◽  
Jessica Chung ◽  
Harriet Dashnow ◽  
...  

Abstract Background Bioinformatics software tools are often created ad hoc, frequently by people without extensive training in software development. In particular, for beginners, the barrier to entry in bioinformatics software development is high, especially if they want to adopt good programming practices. Even experienced developers do not always follow best practices. This results in the proliferation of poorer-quality bioinformatics software, leading to limited scalability and inefficient use of resources; lack of reproducibility, usability, adaptability, and interoperability; and erroneous or inaccurate results. Findings We have developed Bionitio, a tool that automates the process of starting new bioinformatics software projects following recommended best practices. With a single command, the user can create a new well-structured project in 1 of 12 programming languages. The resulting software is functional, carrying out a prototypical bioinformatics task, and thus serves as both a working example and a template for building new tools. Key features include command-line argument parsing, error handling, progress logging, defined exit status values, a test suite, a version number, standardized building and packaging, user documentation, code documentation, a standard open source software license, software revision control, and containerization. Conclusions Bionitio serves as a learning aid for beginner-to-intermediate bioinformatics programmers and provides an excellent starting point for new projects. This helps developers adopt good programming practices from the beginning of a project and encourages high-quality tools to be developed more rapidly. This also benefits users because tools are more easily installed and consistent in their usage. Bionitio is released as open source software under the MIT License and is available at https://github.com/bionitio-team/bionitio.


2022 ◽  
pp. 548-570
Author(s):  
Morgan Richomme

Open source communities have had and continue to have a major influence on the evolution of the Internet. By their nature, such communities involve people with diverse coding cultures and skills. Automation has consequently been of major interest to open source software developers for a long time, and many open source tools have been developed to address code variability and sustainability challenges. This chapter discusses why open source communities must automate and the challenges they will face. Solutions and current examples of automation in open source projects are provided as a guide to what is achievable. OpenShift, OpenStack, and OPNFV communities are used to illustrate different approaches and best practices. Two recently initiated automation initiatives are detailed: “Cross Community Continuous Integration” (XCI) and “Cross Testing” (Xtesting). Finally, some recommendations are provided for new projects as a guide to ease adoption of appropriate tools and methods.


Author(s):  
Morgan Richomme

Open source communities have had and continue to have a major influence on the evolution of the Internet. By their nature, such communities involve people with diverse coding cultures and skills. Automation has consequently been of major interest to open source software developers for a long time, and many open source tools have been developed to address code variability and sustainability challenges. This chapter discusses why open source communities must automate and the challenges they will face. Solutions and current examples of automation in open source projects are provided as a guide to what is achievable. OpenShift, OpenStack, and OPNFV communities are used to illustrate different approaches and best practices. Two recently initiated automation initiatives are detailed: “Cross Community Continuous Integration” (XCI) and “Cross Testing” (Xtesting). Finally, some recommendations are provided for new projects as a guide to ease adoption of appropriate tools and methods.


2018 ◽  
Vol 12 (2) ◽  
pp. 274-285 ◽  
Author(s):  
Dan Fowler ◽  
Jo Barratt ◽  
Paul Walsh

There is significant friction in the acquisition, sharing, and reuse of research data. It is estimated that eighty percent of data analysis is invested in the cleaning and mapping of data (Dasu and Johnson,2003). This friction hampers researchers not well versed in data preparation techniques from reusing an ever-increasing amount of data available within research data repositories. Frictionless Data is an ongoing project at Open Knowledge International focused on removing this friction. We are doing this by developing a set of tools, specifications, and best practices for describing, publishing, and validating data. The heart of this project is the “Data Package”, a containerization format for data based on existing practices for publishing open source software. This paper will report on current progress toward that goal.


2019 ◽  
Author(s):  
Ivonne Allmann

Viele Unternehmen definieren unter „Open Source Compliance“ Regeln für den Umgang mit Open Source Software. Die vorliegende Arbeit stellt am Beispiel der GPL die rechtlichen Besonderheiten und Risiken dar und untersucht gängige Best Practices zur Errichtung eines Open Source Compliance Systems.


2009 ◽  
pp. 1559-1576
Author(s):  
Kris Ven ◽  
Dieter Van Nuffel ◽  
Jan Verelst

Several public administrations (PA) have expressed an increasing interest in open source software in the past few years and are currently migrating to open source software on the desktop. Given the large impact such a migration has on the organization, there is a need for learning from the experiences of previous migrations. In this chapter, we deduct a number of recommendations and lessons learned from previous research conducted on the migration of PAs to open source desktop software. Next, we describe a case study on the migration of the Brussels-Capital Region towards OpenOffice.org, and compare their experiences to these recommendations. In general, our results are quite consistent with previous findings, but also indicate that additional research is still required in order to create a set of best practices—based on empirical research—for the migration towards open source software on the desktop.


Author(s):  
Kris Ven ◽  
Dieter Van Nuffel ◽  
Jan Verelst

Several public administrations (PA) have expressed an increasing interest in open source software in the past few years and are currently migrating to open source software on the desktop. Given the large impact such a migration has on the organization, there is a need for learning from the experiences of previous migrations. In this chapter, we deduct a number of recommendations and lessons learned from previous research conducted on the migration of PAs to open source desktop software. Next, we describe a case study on the migration of the Brussels-Capital Region towards OpenOffice.org, and compare their experiences to these recommendations. In general, our results are quite consistent with previous findings, but also indicate that additional research is still required in order to create a set of best practices—based on empirical research—for the migration towards open source software on the desktop.


Sign in / Sign up

Export Citation Format

Share Document