Skip to content
Free planNo credit card requiredStart writing
AI for Research home
AI for Research home
Dashboard
Sign inGet started

Search 250 million research papers

Read the abstract, see who wrote it and who cites it, and get the citation in APA, MLA, Chicago or Harvard.

About 10,000 papers for “open source projects”

Open Source MPI Projects

Will Ross, Stuart Turner, Scale X Lax Westin et al. · 2007

Overview of the OpenEMPI Project OpenEMPI seeks to provide an open community to develop and to critically evaluate open source solutions for use as an Enterprise Master Person Index (EMPI) • Articulate an accessible framework for development of open source MPI in any computing environment (J2EE, PHP,.NET, etc.) • Contribute meta-analysis useful for open source MPI implementations on any computing platform • Seek recommendations for a standards based approach towards development of an EMPI • Aim for a structured evaluation process

Cited by 0

Writing Open Source Documentation for Open Source Projects

Wickert, Christoph · TIB KMO / FLOWWORKS GmbH · 2018

To publish it's documentation, SUSE has developed not only a comprehensiveOpen Source toolchain to create and publish documentation but also an openworkflow that allows community and partners to provide feedback andcontribute. These tools and processes can easily be adopted by other projectsto write high quality software documentation. SUSE has been around as Linux vendor for a long time and from it's early daysonwards, delivered not only software but also the documentation to use it. Infact, SUSE is not only writing the documentation for it's own distributionsbut for upstream projects like OpenStack as well. Over time, the SUSEdocumentation team has developed not only a comprehensive, completely Free andOpen Source toolchain to create, edit, manage, and publish documentation butalso an open workflow that allows community and partners to provide feedbackand contribute. These tools and processes can easily be adopted by otherprojects to write high quality software documentation, everything from a manpage to a reference guide. In this talk, Christoph will introduce the complete SUSE/openSUSEdocumentation workflow and tool chain. It will cover both the technicaldetails like formats, tools, or branching model and the organizational aspectssuch as the feature planning and tracking, distribution of work and feedbackprocess.

Cited by 0Open access

Contributing to open source projects.

John D. Blischak (631103), Emily R. Davenport (105267), Greg Wilson (521084) · Figshare · 2016

<p>We would like you to add an empty file that is named after your GitHub username to the repo used to write this manuscript. (A) Using your internet browser, navigate to <a href="https://github.com/jdblischak/git-for-science" target="_blank">https://github.com/jdblischak/git-for-science</a>. (B) Click on the “Fork” button to create a copy of this repo on GitHub under your username. (C) On your computer, type git clone <a href="https://github.com/username/git-for-science.git" target="_blank">https://github.com/username/git-for-science.git</a>, which will create a copy of git-for-science on your local machine. (D) Navigate to the readers directory by typing cd git-for-science/readers/. Create an empty file that is titled with your GitHub username by typing touch username.txt. Commit that new file by adding it to the staging area (git add username.txt) and committing with a message (git commit -m "Add username to directory of readers."). Note that your commit identifier will be different than what is shown here. (E) You have committed your new file locally, and the next step is to push that new commit up to the git-for-science repo under your username on GitHub. To do so, type git push origin master. (F) To request to add your commits to the original git-for-science repo, issue a pull request from the git-for-science repo under your username on GitHub. Once your Pull Request is reviewed and accepted, you will be able to see the file you committed with your username in the original git-for-science repository.</p>

Cited by 0Open access

Reflections on Open Source Projects

Payne, Sam · Figshare · 2017

This is a presentation by Brendan MacLean from the Open Source Software workshop at ASMS 2017

Cited by 0Open access

Reflections on Open Source Projects

Payne, Sam · Figshare · 2017

This is a presentation by Brendan MacLean from the Open Source Software workshop at ASMS 2017

Cited by 0Open access

Open Borders? Immigration in Open Source Projects

Christian Bird, Alex Gourley, Prémkumar Dévanbu et al. · 2007

Open source software is built by teams of volunteers. Each project has a core team of developers, who have the authority to commit changes to the repository; this team is the elite, committed foundation of the project, selected through a meritocratic process from a larger number of people who participate on the mailing list. Most projects carefully regulate admission of outsiders to full developer privileges; some projects even have formal descriptions of this process. Understanding the factors that influence the "who, how and when" of this process is critical, both for the sustainability of FLOSS projects, and for outside stakeholders who want to gain entry and succeed. In this paper we mount a quantitative case study of the process by which people join FLOSS projects, using data mined from the Apache Web server, Postgres, and Python. We develop a theory of open source project joining, and evaluate this theory based on our data.

Cited by 136

Estimating Usage of Open Source Projects

Sophia Vargas, Georg J.P. Link, J. Lee · 2024

While open source projects can benefit from usage telemetry to understand their impact, privacy concerns often arise. This paper explores using publicly available metrics as proxies for actual usage data. Using the Flutter project as a case study, we found a strong correlation between these public metrics and Flutter's active user count, demonstrating that such publicly available metrics can offer insights into project usage while respecting user privacy.

Cited by 0

FREE AND OPEN SOURCE SOFTWARE PROJECTS

K. Sowe, Supervisor Prof, Ioannis G. Stamelos et al. · 2008

This work is licensed under a Creative Commons Attribution-Share Alike (by-sa) License. (see Appendix E for further details). ΜΕΛΕΤΗ ΤΗΣ ΔΙΑΜΟΙΡΑΣΗΣ ΓΝΩΣΗΣ ΣΤΑ ΕΡΓΑ ΕΛΕΥΘΕΡΟΥ ΛΟΓΙΣΜΙΚΟΥ/ΛΟΓΙΣΜΙΚΟΥ ΑΝΟΙΚΤΟΥ ΚΩΔΙΚΑ

Cited by 0

Control objectives in open source projects

Kris Ven · 2004

Many studies on open source software development (OSSD) have been published in the past years. In these studies, OSSD has received positive comments and is proposed as a new way of developing software. We investigate how project management is used in open source software (OSS) projects to exercise control of development activities. Project management in OSSD is worth studying, because research has shown that project management is a critical success factor in traditional software development. We use the COBIT framework to audit project management practices commonly found in OSS projects with the aim of determining which practices are currently missing or can be further improved upon. The framework identifies several potential threats to the long term continuity of OSS projects.

Cited by 1

Open Source Health Information Technology Projects

Evangelos Katsamakas, Balaji Janamanchi, Wullianallur Raghupathi et al. · IGI Global eBooks · 2013

This chapter discusses the growth of open source software projects in healthcare. It proposes a research framework that examines the roles of project sponsorship, license type, development status and technological complements in the success of open source health information technology (HIT) projects, and it develops a systematic method for classifying projects based on their success potential. Using data from Sourceforge, an open source software development portal, we find that although project sponsorship and license restrictiveness influence project metrics, they are not significant predictors of project success categorization. On the other hand, development status, operating system, and programming language are significant predictors of an OSS project’s success categorization. We discuss research and application implications and suggest future research directions.Request access from your librarian to read this chapter's full text.

Cited by 0

Open source projects for software vulnerabilities

Nguyen, Van · IEEE DataPort · 2021

Here are some real-world data sets for software vulnerabilities.The original real-world data sets, collected by Lin et al. (https://github.com/DanielLin1986/TransferRepresentationLearning), which contain the source codes of vulnerable and non-vulnerable functions obtained from six real-world software projects, namely FFmpeg, LibTIFF, LibPNG, VLC and Pidgin. These datasets cover both multimedia and image application categories.To obtain our used data sets, we preprocess these data sets before inputting into the deep neural networks. Firstly, we standardize the source codes by removing comments, blank lines and non-ASCII characters. Secondly, we map user-defined variables to symbolic names (e.g., “var1”, “var2”) and user-defined functions to symbolic names (e.g., “func1”, “func2”). We also replace integers, real and hexadecimal numbers with a generic "num" token and strings with a generic "str" token. We usehttps://joern.readthedocs.io/en/latest/to analyze the source codes to get user-defined variables and functions.

Cited by 0Open access

Mechanical Categorization of Open Source Projects

Shino Iwami · 2023

Open source projects with open source software (OSS) have permeated society, and no industry can exist without OSS. At the same time, the risks and life cycle of OSS have severely impacted business and social life. Therefore, organizations utilizing OSS have started to analyze trends of OSS and use the analysis in their own organization's strategy. In an effort to look at OSS from a bird's eye view, OSS classification is important for human recognition. Without the OSS category, important OSS for the organization's business will be missed among too many OSS. At present, as multiple initiatives coexist, each uses its specialized OSS category, even in a single organization. For a long time, OSS stakeholders have manually organized OSS categories, and they have put in a great deal of effort. If manual work continues in the future, much effort will be required in the rapidly changing world of OSS. This research is fundamental and widely available for every analysis related to OSS, providing a universal methodology for OSS categorization with high validation accuracies of 0.98 by means of artificial intelligence technology. During this execution, there was an issue that the accuracy was low due to the small amount of suitable training data for OSS, but it was resolved with data augmentation.

Cited by 0

Release Management Within Open Source Projects

Institute For Software · 2007

A simple classification system for release management practices is presented. When applied to a set of projects, in this case a set of open source projects, distinctive practices are highlighted and relative strengths can be assessed. Three projects are studied, the Linux kernel, Subversion, and the Apache HTTP server. Their release practices, as portrayed by the classification system, emerge as a complex combination of subprocesses and tools chosen to support specific project goals and properties. Through application of this classification, we identify areas of weaknesses in the projects' release management processes and conclude with an overview of potential improvements to the processes and tools that can be made.

Cited by 0

Contribution Barriers to Open Source Projects

Christoph Hannebauer · DuEPublico (University of Duisburg-Essen) · 2016

Contribution barriers are properties of Free/Libre and Open Source Software (FLOSS) projects that may prevent newcomers from contributing.Contribution barriers can be seen as forces that oppose the motivations of newcomers.While there is extensive research on the motivation of FLOSS developers, little is known about contribution barriers.However, a steady influx of new developers is connected to the success of a FLOSS project.The first part of this thesis adds two surveys to the existing research that target contribution barriers and motivations of newcomers.The first exploratory survey provides the indications to formulate research hypotheses for the second main survey with 117 responses from newcomers in the two FLOSS projects Mozilla and GNOME.The results lead to an assessment of the importance of the identified contribution barriers and to a new model of the joining process that allows the identification of subgroups of newcomers affected by specific contribution barriers.The second part of the thesis uses the pattern concept to externalize knowledge about techniques lowering contribution barriers.This includes a complete categorization of the existing work on FLOSS patterns and the first empirical evaluation of these FLOSS patterns and their relationships.The thesis contains six FLOSS patterns that lower specific important contribution barriers identified in the surveys.Wikis are web-based systems that allow its users to modify the wiki's contents.They found on wiki principles with which they minimize contribution barriers.The last part of the thesis explores whether a wiki, whose content is usually natural text, can also be used for software development.Such a Wiki Development Environment (WikiDE) must fulfill the requirements of both an Integrated Development Environment (IDE) and a wiki.The simultaneous compliance of both sets of requirements imposes special challenges.The thesis describes an adapted contribution process supported by an architecture concept that solves these challenges.Two components of a WikiDE are discussed in detail.Each of them helps to lower a contribution barrier.A Proof of Concept (PoC) realization demonstrates the feasibility of the concept. II

Cited by 1Open access