CoChat
Sign Up
Cited by 14Open Source Software InnovationsSoftware Engineering Techniques and PracticesAdvanced Software Engineering Methodologies

A Community Strategy Framework – How to obtain influence on requirements in meritocratic open source software communities?

Open access
Linåker, J., Regnell, B., Damian, D.·2019·Information and Software Technology
DOI 10.1016/j.infsof.2019.04.010
Open this paper in CoChat — free accountOpen PDF

The claims and statistics of this paper haven’t been checked yet.

Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.

A few free checks a day · papers already verified open instantly · results are public

Integrity signals

Registry

Crossref · 10.1016/j.infsof.2019.04.010

Cites

6 of 6 references verified0 citation errors · 0 not checkable

Statistics

Claims the paper makes

The claims and statistics of this paper haven’t been checked yet.

Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.

A few free checks a day · papers already verified open instantly · results are public

Claims other papers make about this one

Each is checked against this paper’s own text: does it say what the citing paper says it does?

  • Early governance models, such as benevolent dictator or consensus-based meritocracies, depended on informal social contracts, technical reputation, and sustained contribution instead of codified policy.

    “Early governance models, such as the benevolent dictator paradigm or consensus-based meritocracies, depended on informal social contracts, technical reputation, and sustained contribution instead of codified policy [4, 30, 42].”

    From Governance in Practice: How Open Source Projects Define and Document Roles (2026) · cites this paper as [30]

    Section 2.2 (pp. 4–6) describes dictator-based and meritocratic governance and says authority in meritocracies is earned through trust, status, and contributions. Section 6.2 (p. 24) also describes earning trust and respect in dictator-based communities. The paper does not establish that these were early models governed by informal social contracts instead of codified policy, and it cautions that merit is not limited to technical contributions. (LLM, conf=0.85)

    Experimental — accuracy not yet measured

Self-check

Percentages, sums and reported differences re-computed from the paper’s own numbers.

The self-check needs the paper’s full text.

Cites

Flagged first, then by citations

Research works printed but not linked: 44

  1. [2][2] S. Butler, J. Gamalielsson, B. Lundell, P. Jonsson, J. Sj¨ oberg, A. Mattsson, N. Rick¨ o, T. Gustavsson, J. Feist, S. Landemoo, et al., An investigation of work practices used by companies making contributions to established oss projects, in: Proceedings of the 40th International Conference on Software Engineering: Software Engineering in Practice, ACM, 2018, pp. 201-210. -
  2. [3][3] S. Jansen, M. A. Cusumano, Software ecosystems: analyzing and managing business networks in the software industry, Edward Elgar Publishing, 2013, Ch. Defining software ecosystems: a survey of software platforms and business network governance, pp. 13-28. -
  3. [4][4] M. Glinz, R. J. Wieringa, Guest editors' introduction: Stakeholders in requirements engineering, IEEE Software 24 (2) (2007) 18-20. -
  4. [5][5] B. Regnell, S. Brinkkemper, Market-driven requirements engineering for software products, in: Engineering and managing software requirements, Springer, 2005, pp. 287-308. -
  5. [8][8] H. M¨ aenp¨ a¨ a, S. M¨ akinen, T. Kilamo, T. Mikkonen, T. M¨ annist¨ o, P. Ritala, Organizing for openness: six models for developer involvement in hybrid oss projects, Journal of Internet Services and Applications 9 (1) (2018) 17. -
  6. [10][10] K. Wnuk, D. Pfahl, D. Callele, E.-A. Karlsson, How can open source software development help requirements management gain the potential of open innovation: an exploratory study, in: Proceedings of the ACM-IEEE International Symposium on Empirical Software Engineering and Measurement, ACM, 2012, pp. 271-280. -
  7. [12][12] P. Laurent, J. Cleland-Huang, Lessons learned from open source projects for facilitating online requirements processes, in: Requirements Engineering: Foundation for Software Quality, Springer, 2009, pp. 240-255. -
  8. [13][13] J. Noll, Innovation in open source software development: A tale of two features, in: J. Feller, B. Fitzgerald, W. Scacchi, A. Sillitti (Eds.), Open Source Development, Adoption and Innovation, Springer US, Boston, MA, 2007, pp. 109-120. -
  9. [14][14] M. L. Markus, The governance of free/open source software projects: monolithic, multidimensional, or configurational?, Journal of Management & Governance 11 (2) (2007) 151-163. -
  10. [15][15] P. B. De Laat, Governance of open source software: state of the art, Journal of Management & Governance 11 (2) (2007) 165-177. -
  11. [17][17] R. T. Fielding, Shared leadership in the apache project, Communications of the ACM 42 (4) (1999) 42-43. -
  12. [18][18] E. Eckhardt, E. Kaats, S. Jansen, C. Alves, The merits of a meritocracy in open source software ecosystems, in: Proceedings of the 2014 European Conference on Software Architecture Workshops, ACM, 2014, p. 7. -
  13. [22][22] M. Syeed, J. Lindman, I. Hammouda, Measuring perceived trust in open source software communities, in: F. Balaguer, R. Di Cosmo, A. Garrido, F. Kon, G. Robles, S. Zacchiroli (Eds.), Open Source Systems: Towards Robust Practices, Springer International Publishing, Cham, 2017, pp. 4954. -
  14. [23][23] A. Nguyen-Duc, D. S. Cruzes, S. Terje, P. Abrahamsson, Do software firms collaborate or compete? a model of coopetition in community-initiated oss projects, e-Informatica Software Engineering Journal 13 (1) (2019) 37-62. -
  15. [24][24] J. Lin˚ aker, B. Regnell, H. Munir, Requirements engineering in open innovation: a research agenda, in: Proceedings of the 2015 International Conference on Software and System Process, ACM, 2015, pp. 208-212. -
  16. [25][25] C. Alves, J. Oliveira, S. Jansen, Software ecosystems governance-a systematic literature review and research agenda, in: Proceedings of the 19th International Conference on Enterprise Information Systems, Vol. 3, 2017, pp. 26-29. -
  17. [28][28] R. J. Wieringa, Design science methodology for information systems and software engineering, Springer, 2014. -
  18. [29][29] P. Runeson, M. H¨ ost, A. Rainer, B. Regnell, Case Study Research in Software Engineering - Guidelines and Examples, Wiley, 2012. -
  19. [31][31] T. Alspaugh, W. Scacchi, et al., Ongoing software development without classical requirements, in: 21st International Requirements Engineering Conference, IEEE, 2013, pp. 165-174. -
  20. [32][32] P. J. ˚ Agerfalk, B. Fitzgerald, Outsourcing to an unknown workforce: Exploring opensurcing as a global sourcing strategy, MIS quarterly (2008) 385-409. -
  21. [33][33] J. Kuriakose, J. Parsons, How do open source software (oss) developers practice and perceive requirements engineering? an empirical study, in: 2015 IEEE Fifth International Workshop on Empirical Requirements Engineering (EmpiRE), 2015, pp. 49-56. -
  22. [34][34] J. W. Castro Llanos, S. T. Acu˜ na Castillo, Differences between traditional and open source development activities, in: O. Dieste, A. Jedlitschka, N. Juristo (Eds.), Product-Focused Software Process Improvement, Springer Berlin Heidelberg, Berlin, Heidelberg, 2012, pp. 131-144. -
  23. [35][35] W. Scacchi, Collaboration practices and affordances in free/open source software development, in: Collaborative software engineering, Springer, 2010, pp. 307-327. -
  24. [36][36] T. Bhowmik, A. Q. Do, Refinement and resolution of just-in-time requirements in open source software and a closer look into non-functional requirements, Journal of Industrial Information Integration (2018) . -
  25. [37][37] N. Ernst, G. C. Murphy, Case studies in just-in-time requirements analysis, in: 2nd International Workshop on Empirical Requirements Engineering, IEEE, 2012, pp. 25-32. -
  26. [38][38] T. Bhowmik, N. Niu, P. Singhania, W. Wang, On the role of structural holes in requirements identification: An exploratory study on open-source software development, ACM Trans. Manage. Inf. Syst. 6 (3) (2015) 10:110:30. -
  27. [40][40] K. Nakakoji, Y. Yamamoto, Y. Nishinaka, K. Kishida, Y. Ye, Evolution patterns of open-source software systems and communities, in: Proceedings of the International Workshop on Principles of Software Evolution, IWPSE '02, ACM, New York, NY, USA, 2002, pp. 76-85. -
  28. [41][41] M. Joblin, S. Apel, C. Hunsen, W. Mauerer, Classifying developers into core and peripheral: An empirical study on count and network metrics, in: 39th International Conference on Software Engineering, 2017, pp. 164-174. -
  29. [42][42] C. Jensen, W. Scacchi, Role migration and advancement processes in ossd projects: A comparative case study, in: 29th International Conference on Software Engineering, 2007, IEEE, 2007, pp. 364-374. -
  30. [43][43] I. De Noni, A. Ganzaroli, L. Orsi, The evolution of oss governance: a dimensional comparative analysis, Scandinavian Journal of Management 29 (3) (2013) 247-263. -
  31. [44][44] E. Capra, A. I. Wasserman, A framework for evaluating managerial styles in open source projects, in: B. Russo, E. Damiani, S. Hissam, B. Lundell, G. Succi (Eds.), Open Source Development, Communities and Quality, Springer US, Boston, MA, 2008, pp. 1-14. -
  32. [46][46] S. O'Mahony, The governance of open source initiatives: what does it mean to be community managed?, Journal of Management & Governance 11 (2) (2007) 139-150. -
  33. [47][47] M. Germonprez, J. E. Kendall, K. E. Kendall, B. Young, Collectivism, creativity, competition, and control in open source software development: reflections on the emergent governance of the spdx working group, International Journal of Information Systems and Management 1 (1-2) (2014) 125-145. -
  34. [48][48] S. O'Mahony, Nonprofit foundations and their role in community-firm software collaboration, in: Perspectives on Free and Open Source Software, MIT Press, Cambridge, MA, 2005, pp. 393-414. -
  35. [50][50] J. Lerner, J. Tirole, Some simple economics of open source, The journal of industrial economics 50 (2) (2002) 197-234. -
  36. [51][51] S. O'Mahony, B. A. Bechky, Boundary organizations: Enabling collaboration among unexpected allies, Administrative Science Quarterly 53 (3) (2008) 422-459. -
  37. [52][52] A. Nguyen Duc, D. S. Cruzes, G. K. Hanssen, T. Snarby, P. Abrahamsson, Coopetition of software firms in open source software ecosystems, in: A. Ojala, H. Holmstr¨ om Olsson, K. Werder (Eds.), Software Business, Springer International Publishing, Cham, 2017, pp. 146-160. -
  38. [53][53] B. Lundell, B. Lings, E. Lindqvist, Open source in swedish companies: where are we?, Information Systems Journal 20 (6) (2010) 519-535. -
  39. [57][57] S. Shahrivar, S. Elahi, A. Hassanzadeh, G. Montazer, A business model for commercial open source software: A systematic literature review, Information and Software Technology 103 (2018) 202-214. -
  40. [58][58] J. Lin˚ aker, H. Munir, K. Wnuk, C. E. Mols, Motivating the contributions: An open innovation perspective on what to share as open source software, Journal of Systems and Software 135 (2018) 17-36. -
  41. [62][62] H. Chesbrough, M. Appleyard, Open innovation and strategy, California management review 50 (1) (2007) 57-76. -
  42. [65][65] S. Jansen, S. Brinkkemper, J. Souer, L. Luinenburg, Shades of gray: Opening up a software producing organization with the open software enterprise model, Journal of Systems and Software 85 (7) (2012) 1495-1510. -
  43. [66][66] A. Baars, S. Jansen, A framework for software ecosystem governance, in: M. A. Cusumano, B. Iyer, N. Venkatraman (Eds.), Software Business, Springer Berlin Heidelberg, Berlin, Heidelberg, 2012, pp. 168-180. -
  44. [67][67] G. Valen¸ ca, C. Alves, A theory of power in emerging software ecosystems formed by small-to-medium enterprises, Journal of Systems and Software 134 (2017) 76-104. -

Cited by

Sorted by citations

Authors
Linåker, J., Regnell, B., & Damian, D.
Affiliations
  • Lund University (SE)
  • University of Victoria (CA)
Corresponding author
Linåker, J.
ORCID
Venue
Information and Software Technology
Publisher
Elsevier BV
Published
2019-08
Volume
112
Pages
102-114
ISSN
0950-5849 (ISSN-L)
DOI
10.1016/j.infsof.2019.04.010
OpenAlex
W2936511742
Cited by
14
References
6
Citations by year
2026: 3 · 2025: 2 · 2024: 1 · 2023: 2 · 2022: 3 · 2020: 3
FWCI
1.55
Type
journal article
Language
en
Open access
Licence
Locations
  • Information and Software Technology (publishedVersion)
  • arXiv (Cornell University) (submittedVersion)
  • Lund University Publications (Lund University) (submittedVersion)
  • arXiv (Cornell University) (cc-by)
Funders
National Science Foundation
Topics
  • Physical Sciences › Computer Science › Computer Science Applications › Open Source Software Innovations
  • Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
  • Physical Sciences › Computer Science › Artificial Intelligence › Advanced Software Engineering Methodologies
Keywords
open source communities, requirements engineering, stakeholder influence, requirements alignment, community strategies

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review