@proceedings {1890, title = {Designing for Participation: Three Models for Developer Involvement in Hybrid OSS Projects}, volume = {496}, year = {2017}, month = {05/2017}, pages = {23-33}, publisher = {Springer}, abstract = {This paper reports governance practices of three profit oriented companies that develop OSS software with the help of their respective open development communities. We explore how the companies allow development contributions from external stakeholders, and what knowledge they let out of their internal software development activities. The results lay ground for further research on how to organize openness of the software development process in hybrid setups where the needs of different stakeholders are partly competing - yet complementary.}, keywords = {Community Management, Hybrid open source, open source}, doi = {10.1007/978-3-319-57735-7_3}, url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_3}, author = {M{\"a}enp{\"a}{\"a}, Hanna and Kilamo, Terhi and Mikkonen, Tommi and M{\"a}nnist{\"o}, Tomi} } @proceedings {1459, title = {Perspectives on Code Forking and Sustainability in Open Source Software}, volume = {378}, year = {2012}, month = {09/2012}, pages = {274-279}, publisher = {IFIP AICT, Springer}, abstract = {The ability to create high-quality software artifacts that are usable over time is one of the essential requirements of the software business. In such a setting, open source software offers excellent opportunities for sustainability. In particular, safeguarding mechanisms against planned obsolescence by any single actor are built into the definition of open source. The most powerful of these mechanisms is the ability to fork the project. In this paper we argue that the possibility to fork serves as the invisible hand of sustainability that ensures that code remains open and that the code that best serves the community lives on. Furthermore, the mere option to fork provides a mechanism for safeguarding against despotic decisions by the project lead, who is thus guided in their actions to consider the best interest of the community.}, author = {Nyman, Linus and Mikkonen, Tommi and Juho Lindman and FougeĢ€re, Martin} } @proceedings {1287, title = {To Fork or Not to Fork: Fork Motivations in SourceForge Projects}, year = {2011}, note = {"Using this search function, we compiled a list of all of the programs with the word {\textquotedblleft}fork{\textquotedblright}..." "We then analyzed the motivations stated in the descriptions of the forked programs...." "Based on the descriptions entered by the developer, we were able to identify motivations for 381 of the forks." }, month = {10/2011}, pages = {259-268}, publisher = {Springer}, abstract = {A project fork occurs when software developers take a copy of source code from one software package and use it to begin an independent development work that is maintained separately from its origin. Although forking in open source software does not require the permission of the original authors, the new version, nevertheless, competes for the attention of the same developers that have worked on the original version. The motivations developers have for performing forks are many, but in general they have received little attention. In this paper, we present the results of a study of forks performed in SourceForge (http://sourceforge.net/) and list the developers{\textquoteright} motivations for their actions. The main motivation, seen in close to half of the cases of forking, was content modification; either adding content to the original program or focusing the content to the needs of a specific segment of users. In a quarter of the cases the motivation was technical modification; either porting the program to new hardware or software, or improving the original.}, keywords = {fork rate, sourceforge}, author = {Nyman, Linus and Mikkonen, Tommi} } @conference {529, title = {Forging A Community {\textendash} Not: Experiences On Establishing An Open Source Project}, booktitle = {OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)}, series = {IFIP International Federation for Information Processing}, volume = {275/2008}, year = {2008}, month = {2008///}, pages = {15 - 27}, publisher = {Springer}, organization = {Springer}, chapter = {2}, abstract = {Open source has recently become a practical and advocated fashion to develop, integrate, and license software. As a consequence, open source communities that commonly perform the development work are becoming important in the practice of software engineering. A community that is lively can often produce high-quality systems that continuously grow in terms of features, whereas communities that do not gain interest will inevitably perish. Despite their newly established central role, creation, organization, and management of such communities have not yet been widely studied from the viewpoint of software engineering practices. In this paper, we discuss experiences gained in the scope of Laika, an open source project established to develop an integrated software development environment for developing applications that run in Linux based mobile devices. }, issn = {978-0-387-09683-4}, doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_2}, attachments = {https://flosshub.org/sites/flosshub.org/files/forging\%20a\%20community.pdf}, author = {J{\"a}rvensivu, Juha and Mikkonen, Tommi} }