Dilemmas within commercial involvement in open source software

Ciesielska, Małgorzata; Westenholz, Ann

doi:10.1108/jocm-04-2013-0058

Cited by 12 publications

(25 citation statements)

References 36 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Although a number of studies looked into the benefits of using open source software by a company(e.g. [27]), and the result of commercial involvement [8,35] by studying different project level metrics like sustainability, developer inflow and retention etc., to our knowledge no study has looked into the difference in types of contribution of individual commercial and non-commercial users on a large scale software ecosystem like NPM and used it for predicting if a user has commercial affiliation.…”

Section: Related Workmentioning

confidence: 99%

“…The data for item (1) was collected from the npms.io website, using the API provided 7 . The associated GitHub repository URL (item 2) and the list of dependencies of the NPM packages (used for item 8) were collected from their metadata information, which was obtained by using a "follower" script, as described in NPM's GitHub repository 8 . After filtering for our criteria that the NPM package must have more than 10,000 monthly downloads (since January, 2018), a functional link to its GitHub repository, and at least one issue, we were left with 4433 different NPM packages.…”

Section: Data Collectionmentioning

confidence: 99%

“…The transitive dependency map of item (8) was constructed by doing a recursive search using the dependency information collected for the packages. We listed the direct dependencies of a package as level 1 dependencies of that package, the dependencies of the packages in level 1 as level 2 dependencies of that package, and so on.…”

Section: Data Collectionmentioning

confidence: 99%

See 2 more Smart Citations

Patterns of Effort Contribution and Demand and User Classification based on Participation Patterns in NPM Ecosystem

Dey

Mockus

2019

Proceedings of the Fifteenth International Conference on Predictive Models and Data Analytics in Software Engineering

View full text Add to dashboard Cite

Background: Open source requires participation of volunteer and commercial developers (users) in order to deliver functional highquality components. Developers both contribute effort in the form of patches and demand effort from the component maintainers to resolve issues reported against it. Aim: Identify and characterize patterns of effort contribution and demand throughout the open source supply chain and investigate if and how these patterns vary with developer activity; identify different groups of developers; and predict developers' company affiliation based on their participation patterns. Method: 1,376,946 issues and pull-requests created for 4433 NPM packages with over 10,000 monthly downloads and full (public) commit activity data of the 272,142 issue creators is obtained and analyzed and dependencies on NPM packages are identified. Fuzzy c-means clustering algorithm is used to find the groups among the users based on their effort contribution and demand patterns, and Random Forest is used as the predictive modeling technique to identify their company affiliations. Result: Users contribute and demand effort primarily from packages that they depend on directly with only a tiny fraction of contributions and demand going to transitive dependencies. A significant portion of demand goes into packages outside the users' respective supply chains (constructed based on publicly visible version control data). Three and two different groups of users are observed based on the effort demand and effort contribution patterns respectively. The Random Forest model used for identifying the company affiliation of the users gives a AUC-ROC value of 0.68. Conclusion: Our results give new insights into effort demand and supply at different parts of the supply chain of the NPM ecosystem and its users and suggests the need to increase visibility further upstream. CCS CONCEPTS• Software and its engineering → Open source model; • Computing methodologies → Supervised learning by classification; Cluster analysis;

show abstract

Section: Related Workmentioning

confidence: 99%

Section: Data Collectionmentioning

confidence: 99%

See 1 more Smart Citation

Patterns of Effort Contribution and Demand and User Classification based on Participation Patterns in NPM Ecosystem

Dey

Mockus

2019

Proceedings of the Fifteenth International Conference on Predictive Models and Data Analytics in Software Engineering

View full text Add to dashboard Cite

show abstract

“…Although the strategic perspective argues that open innovation is inevitable, it remains a challenge for business organizations seeking to benefit from external knowledge sources but still operating like closed systems. The change in the business model requires not only adapted structures and systems, but also the redefining of a company's role in those structures and systems (Ciesielska & Westenholz, 2016). the OSS projects and changing two thirds of it in-house, for use on the internet tablet.…”

Section: Learning Outcomesmentioning

confidence: 99%

“…Such a policy resulted in submitting only minor repairs of bugs to open source projects and thus contradicted the rules of the open source system (Ciesielska & Westenholz, 2016).…”

Section: Learning Outcomesmentioning

confidence: 99%

Nokia on the slope

Ciesielska

2017

The International Journal of Entrepreneurship and Innovation

Self Cite

View full text Add to dashboard Cite

This case study explores the origins of Nokia’s decline in the mobile technology market, as an unsuccessful attempt to introduce an open-source strategy into the business. Nokia created a hybrid model, which codified conflicting principles taken from closed and open mode of collaboration. A series of implementation problems resulted in Nokia struggling to attract open-source partners, growing issues with managing in-house staff and ultimately failing to develop a new mobile operating system fast enough to stay competitive. Key learning outcomes: At the completion of the case study, students will understand the complexity of open innovation implementation when paradigmatic differences between businesses and/or partners are not resolved.

show abstract