%0 Conference Proceedings %B 23rd IEEE International Conference on Software Analysis, Evolution, and Reengineering (SANER 2016) at Osaka %D 2016 %T Analyzing the Decision Criteria of Software Developers Based on Prospect Theory %A Kanako Kina %A Tsunoda, Masateru %A Tamada, Haruaki %A Hiroshi Igaki %K flossmole %X To enhance the quality of software, many software development support tools and software development methodologies have been proposed. However, not all proposed tools and methodologies are widely used in software development. We assume that the evaluation of tools and methodologies by developers is different from the evaluation by researchers, and that this is one of the reasons why the tools and methodologies are not widely used. We analyzed the decision criteria of software developers as applied to the tools and methodologies, to clarify whether the difference exists or not. In behavioral economics, there are theories which assume people have biases, and they do not always act reasonably. In the experiment, we made a questionnaire based on behavioral economics, and collected answers from open source software developers. The results suggest that developers do not always act to maximize expected profit because of the certainty effect and ambiguity aversion. Therefore, we should reconsider the evaluation criteria of tools such as the f-measure or AUC, which mainly focus on the expected profit. %B 23rd IEEE International Conference on Software Analysis, Evolution, and Reengineering (SANER 2016) at Osaka %8 03/2016 %U http://se-naist.jp/pman3/pman3.cgi?DOWNLOAD=579 %> https://flosshub.org/sites/flosshub.org/files/saner2016-kina.pdf %0 Conference Proceedings %B 12th International Symposium on Open Collaboration (OpenSym 2016) %D 2016 %T Differentiating Communication Styles of Leaders on the Linux Kernel Mailing List %A Schneider, Daniel %A Spurlock, Scott %A Squire, Megan %K email %K flossmole %K linus torvalds %K linux %K lkml %X Much communication between developers of free, libre, and open source software (FLOSS) projects happens on email mailing lists. Geographically and temporally dispersed development teams use email as an asynchronous, centralized, persistently stored institutional memory for sharing code samples, discussing bugs, and making decisions. Email is especially important to large, mature projects, such as the Linux kernel, which has thousands of developers and a multi-layered leadership structure. In this paper, we collect and analyze data to understand the communication patterns in such a community. How do the leaders of the Linux Kernel project write in email? What are the salient features of their writing, and can we discern one leader from another? We find that there are clear written markers for two leaders who have been particularly important to recent discussions of leadership style on the Linux Kernel Mailing List (LKML): Linux Torvalds and Greg Kroah-Hartman. Furthermore, we show that it is straightforward to use a machine learning strategy to automatically differentiate these two leaders based on their writing. Our findings will help researchers understand how this community works, and why there is occasional controversy regarding differences in communication styles on the LKML. %B 12th International Symposium on Open Collaboration (OpenSym 2016) %I ACM %8 08/2016 %> https://flosshub.org/sites/flosshub.org/files/v3_0.pdf %0 Conference Paper %B 2015 IEEE Symposium on Service-Oriented System Engineering (SOSE) %D 2015 %T OSSEAN: Mining Crowd Wisdom in Open Source Communities %A Yin, Gang %A Wang, Tao %A Wang, Huaimin %A Fan, Qiang %A Zhang, Yang %A Yu, Yue %A Yang, Cheng %K flossmole %X Nowadays open source software represents a successful crowd-based software production model and is becoming an ecosystem combining huge amounts of software producers (such as software developers) and consumers (such as software users and customers). Lots of research work has been conducted on analyzing software artifacts created by producers, but few of them reveal the power of feedback from consumers which we believe is very important for the evaluation and evolution of open source software. This paper introduces OSSEAN, a platform for Open Source Software Evaluating, Analyzing and Networking. OSSEAN divides the open source communities into two groups: software production communities and software consumption communities. The former contain structured software artifacts such as projects, source code and issues, while the latter are full of textual documents with rich semantics of user feedback. We show the power of OSSEAN with some interesting demos by analyzing more than 200 thousands of open source projects and 10 million documents. %B 2015 IEEE Symposium on Service-Oriented System Engineering (SOSE) %I IEEE %C San Francisco Bay, CA, USA %P 367 - 371 %R 10.1109/SOSE.2015.51 %0 Conference Paper %B Proceedings of the 5th International Workshop on Emerging Trends in Software Metrics - WETSoM 2014 %D 2014 %T "May the fork be with you": novel metrics to analyze collaboration on GitHub %A Marco Biazzini %A Benoit Baudry %Y Counsell, Steve %Y Marchesi, Michele L. %Y Visaggio, Aaron %Y Zhang, Hongyu %Y Venkatasubramanyam, Radhika %K flossmole %K github %X Multi–repository software projects are becoming more and more popular, thanks to web–based facilities such as GitHub. Code and process metrics generally assume a single repository must be analyzed, in order to measure the characteristics of a codebase. Thus they are not apt to measure how much relevant information is hosted in multiple repositories contributing to the same codebase. Nor can they feature the characteristics of such a distributed development process. We present a set of novel metrics, based on an original classification of commits, conceived to capture some interesting aspects of a multi–repository development process. We also describe an efficient way to build a data structure that allows to compute these metrics on a set of Git repositories. Interesting outcomes, obtained by applying our metrics on a large sample of projects hosted on GitHub, show the usefulness of our contribution. %B Proceedings of the 5th International Workshop on Emerging Trends in Software Metrics - WETSoM 2014 %I ACM Press %C New York, New York, USA %P 37 - 43 %@ 9781450328548 %U http://marbiaz.github.io/docs/Biazzini14b.pdf %! WETSoM 2014 %R 10.1145/2593868.2593875 %0 Generic %D 2014 %T The Small World Network Effect in Software Project Teams %A Kevin Peterson %K flossmole %X Team cohesion and the dynamics of team formation are important parts of any project, with software projects being no exception. An interesting aspect of team building is the relationships formed between the team members. Because of these relationships, representing software team members as a graph may be a natural way to explore team dynamics. As team members move between projects, these graphs be- come more and more connected as team members col- laborate and form new relationships. We show that this connectivity, known as the “small world effect,” has a positive impact on team performance when the connectivity levels are moderate. Performance de- grades, however, at both very high and very low lev- els of connectivity. This aligns with similar research findings of non-software teams. %U https://www.researchgate.net/publication/259217372_The_Small_World_Network_Effect_in_Software_Project_Teams %> https://flosshub.org/sites/flosshub.org/files/kpeterson-small-world-software.pdf %0 Conference Paper %B Proceedings of the 29th IEEE International Conference on Software Maintainability %D 2013 %T How does Context affect the Distribution of Software Maintainability Metrics? %A Zhang, Feng %A Audris Mockus %A Ying Zou %A Foutse Khomh %A Hassan, Ahmed E. %K benchmark %K context %K contextual factor %K flossmole %K large scale %K metrics %K mining software repositories %K sampling %K software maintainability %K sourceforge %K static metrics %X Software metrics have many uses, e.g., defect prediction, effort estimation, and benchmarking an organization against peers and industry standards. In all these cases, metrics may depend on the context, such as the programming language. Here we aim to investigate if the distributions of commonly used metrics do, in fact, vary with six context factors: application domain, programming language, age, lifespan, the number of changes, and the number of downloads. For this preliminary study we select 320 nontrivial software systems from SourceForge. These software systems are randomly sampled from nine popular application domains of SourceForge. We calculate 39 metrics commonly used to assess software maintainability for each software system and use Kruskal Wallis test and Mann-Whitney U test to determine if there are significant differences among the distributions with respect to each of the six context factors. We use Cliff’s delta to measure the magnitude of the differences and find that all six context factors affect the distribution of 20 metrics and the programming language factor affects 35 metrics. We also briefly discuss how each context factor may affect the distribution of metric values.We expect our results to help software benchmarking and other software engineering methods that rely on these commonly used metrics to be tailored to a particular context. %B Proceedings of the 29th IEEE International Conference on Software Maintainability %S ICSM '13 %> https://flosshub.org/sites/flosshub.org/files/icsm2013_contextstudy.pdf %0 Book %B IFIP Advances in Information and Communication Technology Open Source Software: Quality Verification %D 2013 %T How Healthy Is My Project? Open Source Project Attributes as Indicators of Success %A Piggot, James %A Amrit, Chintan %E Petrinja, Etiel %E Succi, Giancarlo %E Ioini, Nabil %E Sillitti, Alberto %K flossmole %K sourceforge %X Determining what factors can influence the successful outcome of a software project has been labeled by many scholars and software engineers as a difficult problem. In this paper we use machine learning to create a model that can determine the stage a software project has obtained with some accuracy. Our model uses 8 Open Source project metrics to determine the stage a project is in. We validate our model using two performance measures; the exact success rate of classifying an Open Source Software project and the success rate over an interval of one stage of its actual performance using different scales of our dependent variable. In all cases we obtain an accuracy of above 70% with one away classification (a classification which is away by one) and about 40% accuracy with an exact classification. We also determine the factors (according to one classifier) that uses only eight variables among all the variables available in SourceForge, that determine the health of an OSS project. %B IFIP Advances in Information and Communication Technology Open Source Software: Quality Verification %I Springer Berlin Heidelberg %C Berlin, Heidelberg %V 404 %P 30 - 44 %@ 978-3-642-38928-3 %U http://link.springer.com/chapter/10.1007/978-3-642-38928-3_3 %R 10.1007/978-3-642-38928-3_3 %> https://flosshub.org/sites/flosshub.org/files/OSSHealth_1.0.pdf %0 Conference Paper %B Artificial Intelligence and Applications %D 2013 %T Linchpin Developers in Open Source Software Projects %A Corona, Erika Ingrid Mastranzo %A Rossi, Bruno %K flossmole %X In Open Source Software (OSS) development, the so-called linchpin developers are those that contribute contemporaneously to several projects, contributing to keeping the community tied together. While such developers have been identified in previous research, their importance within the OSS community has not been widely discussed. The main objective of this work is to analyze their “weaving” role across projects. With this aim, we mined software repositories, using text mining techniques as log-likehood ratio and co-word analysis, further building social networks of developers within emerging communities. The findings show that linchpin developers generally attach in a preferential way to projects in a single specific domain. They tend to be more “project managers”, and “all-hands-persons”, meaning that they bring multi-disciplinary experience across projects. They tend to cover the same role across projects. They generally have high centrality in their projects, and contribute to create projects that ease the transition from a fragmented projects community to a more core-periphery community. %B Artificial Intelligence and Applications %I ACTAPRESS %C Innsbruck, AustriaCalgary,AB,Canada %U https://www.researchgate.net/publication/266632252_Linchpin_Developers_in_Open_Source_Software_Projects %R 10.2316/P.2013.796-018 %0 Journal Article %J International Journal of the Commons %D 2013 %T Preliminary steps toward a general theory of internet-based collective-action in digital information commons: Findings from a study of open source software projects %A Charles Schweik %A Robert English %K collaborative success and abandonment %K common property regime %K digital information commons %K flossmole %K Free/libre software %K open source software %K sourceforge %K srda %X This paper presents some of the findings from a 5-year empirical study of FOSS (free/libre and open source software) commons, completed in 2011. FOSS projects are Internet-based common property regimes where the project source code is developed over the Internet. The resulting software is generally distributed with a license that provides users with the freedoms to access, use, read, modify and redistribute the software. In this study we used three different and very large datasets (approximately 107,000; 174,000 and 1400 cases respectively) with information on FOSS projects residing in Sourceforge.net, one of the largest, if not the largest, FOSS repository in the world. We employ various quantitative methods to uncover factors that lead some FOSS projects to ongoing collaborative success, while others become abandoned. After presenting some of our study’s results, we articulate the collaborative “story” of FOSS that emerged. We close the paper by discussing some key findings that can contribute to a general theory of Internet-based collective-action and FOSS-like forms of digital online commons. %B International Journal of the Commons %V 7 %U http://www.thecommonsjournal.org/index.php/ijc/article/view/URN%3ANBN%3ANL%3AUI%3A10-1-114926 %0 Report %D 2012 %T Integrating FLOSS repositories on the Web %A Iqbal, Aftab %A Cyganiak, Richard %A Hausenblas, Michael %K flossmole %K google code %K sourceforge %X This paper provides a novel approach to the problem of integrating data from multiple code forges of FLOSS. We review the current problems in integrating the data from multiple forges and argue that Semantic Web technologies are suitable for representing knowledge contained in code forges. Further, we show the advantage of linking the metadata of projects to other data sources on the Web which will enable querying extra information from the Web. The paper briefly describes how the modeling is achieved and what benefits can be obtained by enabling linking to other relevant data sources already available on the Web. %B DERI Technical Report 2012-12-10 %8 2012 %U https://www.researchgate.net/publication/259757473_Integrating_FLOSS_repositories_on_the_Web %> https://flosshub.org/sites/flosshub.org/files/DERI-TR-AFTAB-2012-12-10_0.pdf %0 Book %D 2012 %T Internet Success: A Study of Open Source Software Commons %A Schweik, C. M. %A English, R. %K flossmole %K srda %I MIT Press %C Cambridge, MA, USA %U http://tinyurl.com/d3e4545 %9 Book %0 Journal Article %J Journal of Software: Evolution and Process %D 2012 %T Similarities, challenges and opportunities of Wikipedia content and open source projects %A Capiluppi, Andrea %K flossmole %X Several years of research and evidence have demonstrated that open source software portals often contain a large amount of software projects that simply do not evolve, developed by relatively small communities, struggling to attract a sustained number of contributors. These portals have started to increasingly act as a storage for abandoned projects, and researchers and practitioners should try and point out how to take advantage of such content. Similarly, other online content portals (like Wikipedia) could be harvested for valuable content. In this paper we argue that, even with differences in the requested expertise, many projects reliant on content and contributions by users undergo a similar evolution, and follow similar patterns: when a project fails to attract contributors, it appears to be not evolving, or abandoned. Far from a negative finding, even those projects could provide valuable content that should be harvested and identified based on common characteristics: by using the attributes of ‘usefulness’ and ‘modularity’ we isolate valuable content in both Wikipedia pages and open source software projects. %B Journal of Software: Evolution and Process %P n/a - n/a %8 08/2012 %U https://www.researchgate.net/publication/259684110_Similarities_challenges_and_opportunities_of_Wikipedia_content_and_open_source_projects %! J. Softw. Evol. and Proc. %R 10.1002/smr.1570 %> https://flosshub.org/sites/flosshub.org/files/jsep2012.pdf %0 Thesis %D 2012 %T Software Libre y abierto: comunidades y redes de producción digital de bienes comunes %A Tania E. Turner Sen %K bienes comunes %K commons %K comunidades virtuales %K FLOSS %K flossmole %K hackers %K redes virtuales %K repositories %K repositorios %K Software libre y abierto %K virtual communities %K virtual networks %X This thesis is about a collective form of production that have expanded and strengthen in the global high technology market. It is about FLOSS production. The study takes on account that technnologies are not neutral, they emerge as strategies and mechanisms of politics and economic interests. Although, FLOSS production is inserted in the capitalist context, the collective work of the communities and networks that produce it is based on ideas about freedom and solidarity. The types of rules and organization of labour inside of this communities have develop a kind of product that it is well categorized as part of the new commons. The conclusions at the end of this work pretend to offer a clear approach to the FLOSS production networks dynamics inside the virtual infrastructure. Specifically, it offers an approach of the interaction and forms of cooperation, as well of the individual and collective schemas that motivates the cooperation action of the individuals. %I Universidad Nacional Autónoma de México %C Ciudad de México, México %P 269 pages %U http://132.248.9.195/ptd2012/agosto/406008604/Index.html %> https://flosshub.org/sites/flosshub.org/files/Tesis.pdf %0 Conference Paper %B 2010 43rd Hawaii International Conference on System Sciences (HICSS 2010) %D 2010 %T Analyzing Leadership Dynamics in Distributed Group Communication %A Kevin Crowston %A Andrea Wiggins %A Howison, James %K core %K DYNAMICS %K email %K email archives %K fire %K flossmole %K gaim %K leadership %K mailing list %K project success %K social network analysis %K srda %X We apply social network analysis (SNA) to examine the dynamics of leadership in distributed groups, specifically Free/Libre Open Source Software development projects, and its relation to group performance. Based on prior work on leadership in distributed groups, we identify leaders with those who make the highest level of contribution to the group and assess the degree of leadership by measuring centralization of communications. We compare the dynamics of leadership in two FLOSS projects, one more and one less effective. We find that in both projects, centralization was higher in developer-oriented communications venues than in user-oriented venues, suggesting higher degrees of leadership in developer venues. However, we do not find a consistent relation between centralization and effectiveness. We suggest that SNA can instead be useful for identifying interesting periods in the history of the project, e.g., periods where the leadership of the project is in transition. %B 2010 43rd Hawaii International Conference on System Sciences (HICSS 2010) %I IEEE %C Honolulu, Hawaii, USA %P 1 - 10 %@ 978-1-4244-5509-6 %R 10.1109/HICSS.2010.62 %> https://flosshub.org/sites/flosshub.org/files/07-06-02.pdf %0 Journal Article %J Revista de Administração de Empresas %D 2010 %T Atratividade de projetos de software livre: importância teórica e estratégias para administração %A Santos Jr, Carlos Denner dos %K flossmole %X Milhares de Projetos de Software Livre (PSL) foram e continuam sendo criados na Internet. Esse cenário aumenta as oportunidades de colaboração tanto quanto acirra a concorrência por usuários e contribuidores, que elevariam esses projetos a níveis superiores aos que seriam alcançados por seus fundadores sozinhos. E dado que o aprimoramento por meio de colaboração é o principal objetivo dos fundadores de PSL, a importância de entender e administrar a capacidade de atrair usuários e contribuidores fica estabelecida. Para auxiliar pesquisadores e fundadores nesse desafio, o conceito de atratividade é introduzido neste artigo, que desenvolve um ferramental teórico-gerencial sobre as causas, indicadores e consequências da atratividade, viabilizando sua administração estratégica. %B Revista de Administração de Empresas %V 50 %P 424 - 438 %8 2010 %N 4 %! Rev. adm. empres. %R 10.1590/S0034-75902010000400007 %0 Book Section %B Open Source Software: New Horizons %D 2010 %T Download Patterns and Releases in Open Source Software Projects: A Perfect Symbiosis? %A Rossi, Bruno %A Russo, Barbara %A Succi, Giancarlo %E Ågerfalk, Pär %E Boldyreff, Cornelia %E González-Barahona, Jesús %E Madey, Gregory %E Noll, John %K flossmole %K oss2010 %K sourceforge %X Software usage by end-users is one of the factors used to evaluate the success of software projects. In the context of open source software, there is no single and non-controversial measure of usage, though. Still, one of the most used and readily available measure is data about projects downloads. Nevertheless, download counts and averages do not convey as much information as the patterns in the original downloads time series. In this research, we propose a method to increase the expressiveness of mere download rates by considering download patterns against software releases. We apply experimentally our method to the most downloaded projects of SourceForge's history crawled through the FLOSSMole repository. Findings show that projects with similar usage can have indeed different levels of sensitivity to releases, revealing different behaviors of users. Future research will develop further the pattern recognition approach to automatically categorize open source projects according to their download patterns. %B Open Source Software: New Horizons %S IFIP Advances in Information and Communication Technology %I Springer Boston %V 319 %P 252-267 %U http://dx.doi.org/10.1007/978-3-642-13244-5_20 %0 Journal Article %J INFOCOMP Special Edition %D 2010 %T Proposed Application of Data Mining Techniques for Clustering Software Projects %A Rezende, Henrique Ribiero %A Esmin, Ahmed Ali Abdalla %K flossmole %X Software projects always generate a lot of data, ranging from informal documentation to a database with thousands of lines of code. This information extracted from software projects takes even greater when it comes to OSS (Open Source Software). Such data may include source code base, historical change in the software, bug reports, mailing lists, among others. Using data mining techniques, we can extract valuable knowledge of this set of in formation, thus providing improvements throughout the process of software development. The results can be used to improve the quality of software, or even to manage the project in order to obtain maximum efficiency. This article proposes the application of data mining techniques to cluster software projects, cites the advantages that can be obtained with these techniques, and illustrates the application of data mining in a Open Source Software database %B INFOCOMP Special Edition %P 43-48 %> https://flosshub.org/sites/flosshub.org/files/art06.pdf %0 Conference Paper %B Second International Workshop on Building Sustainable Open Source Communities (OSCOMM 2010) %D 2010 %T Success and Abandonment in Open Source Commons: Selected Findings from an Empirical Study of Sourceforge.net Projects %A Schweik, C. M. %A English, R. %A Paienjton, Q. %A Haire, S. %K abandonment %K flossmole %K metadata %K project failure %K project success %K sourceforge %K time %X Some open source software collaborations are sustained over long periods of time and across several versions of a software product, while others become abandoned even before the first version of the product has been developed. In this study, we identify factors that might be responsible for one or the other of these collaborative trajectories. We examine 107,747 open source software projects hosted on Sourceforge.net in August 2006 using data available through the FLOSSmole Project. We employ Classification and Regression Tree modeling and Random Forests statistical approaches to begin to establish an understanding of how various project attributes, especially physical and community ones, contribute to project success or abandonment. We find that factors associated with success and abandonment differ for projects in the early stage of development (pre-first release) compared to projects that have had a first release, and that product utility, project vision, leadership, and group-size are associated with success in open source collaborations. We also find that successful open source projects exist across all types of software and not simply in areas associated with the open source “movement.” Other evidence suggests that Sourceforge.net may play an important role in “intellectual match-making.” %B Second International Workshop on Building Sustainable Open Source Communities (OSCOMM 2010) %8 05/2010 %> https://flosshub.org/sites/flosshub.org/files/osscomm003.pdf %0 Conference Paper %B 6th IEEE Working Conference on Mining Software Repositories %D 2009 %T Amassing and indexing a large sample of version control systems: towards the census of public source code history %A Audris Mockus %K bazaar %K cvs %K flossmole %K git %K mercurial %K source code %K sourceforge %K subversion %K version control %X The source code and its history represent the output and process of software development activities and are an in- valuable resource for study and improvement of software development practice. While individual projects and groups of projects have been extensively analyzed, some fundamental questions, such as the spread of innovation or genealogy of the source code, can be answered only by considering the entire universe of publicly available source code and its history. We describe methods we developed over the last six years to gather, index, and update an approximation of such a universal repository for publicly accessible version control systems and for the source code inside a large corporation. While challenging, the task is achievable with limited resources. The bottlenecks in network bandwidth, processing, and disk access can be dealt with using inherent parallelism of the tasks and suitable tradeoffs between the amount of storage and computations, but a completely automated discovery of public version control systems may require enticing participation of the sampled projects. Such universal repository would allow studies of global properties and origins of the source code that are not possible through other means. %B 6th IEEE Working Conference on Mining Software Repositories %8 May 16–17 %G eng %> https://flosshub.org/sites/flosshub.org/files/11amassing.pdf %0 Conference Paper %B 3rd Workshop on Public Data about Software Development (WoPDaSD 2008) %D 2008 %T Author Entropy: A Metric for Characterization of Software Authorship Patterns %A Taylor, Quinn C. %A Stevenson, James E. %A Delorey, Daniel P. %A Knutson, Charles D. %K developers %K entropy %K flossmole %K sourceforge %X We propose the concept of author entropy and describe how file-level entropy measures may be used to understand and characterize authorship patterns within individual files, as well as across an entire project. As a proof of concept, we compute author entropy for 28,955 files from 33 open-source projects. We explore patterns of author entropy, identify techniques for visualizing author entropy, and propose avenues for further study. %B 3rd Workshop on Public Data about Software Development (WoPDaSD 2008) %P 42-47 %8 2008 %> https://flosshub.org/sites/flosshub.org/files/entropy2008.pdf %0 Conference Paper %B 3rd Workshop on Public Data about Software Development (WoPDaSD 2008) %D 2008 %T Cross-repository data linking with RDF and OWL %A Howison, James %K data integration %K flossmole %K forges %K integration %K owl %K RDF %K repositories %K semantic %K semantic Web %K sparql %K srda %X This paper provides an approach to the problem of integrating data from multiple research repositories for FLOSS data. It introduces semantic web technologies (RDF, OWL, OWL-DL reasoners and SPARQL) to argue that these are useful for building shared research infrastructure. The paper illustrates its point by describing parts of an ontology developed for the integration and analysis of project communications drawn from FLOSSmole, the Notre Dame archive and direct collection of data. RDF vocabularies provide a way to agree on things we agree about as well as a way to be clearer about ways in which we disagree. %B 3rd Workshop on Public Data about Software Development (WoPDaSD 2008) %P 15-22 %8 2009 %> https://flosshub.org/sites/flosshub.org/files/howison2008.pdf %0 Journal Article %J Upgrade: The European Journal for the Informatics Professional %D 2007 %T Identifying Success and Abandonment of Free/Libre and Open Source (FLOSS) Commons: A Preliminary Classification of Sourceforge.net projects %A English, R. %A Schweik, C. M. %K flossmole %K sourceforge %K success %X Free/Libre and Open Source Software (FLOSS) projects are a form of commons where individuals work collectively to produce software that is a public, rather than a private, good. The famous phrase “Tragedy of the Commons” describes a situation where a natural resource commons, such as a pasture, or a water supply, gets depleted because of overuse. The tragedy in FLOSS commons is distinctly different: It occurs when collective action ceases before a software product is produced or reaches its full potential. This paper builds on previous work about defining success in FLOSS projects by taking a collective action perspective. We first report the results of interviews with FLOSS developers regarding our ideas about success and failure in FLOSS projects. Building on those interviews and previous work, we then describe our criteria for defining success/tragedy in FLOSS commons. Finally, we discuss the results of a preliminary classification of nearly all projects hosted on Sourceforge.net as of August 2006. %B Upgrade: The European Journal for the Informatics Professional %V VIII %P 54-59 %U http://www.cepis.org/upgrade/files/full-VI-07.pdf %N 6 (December) %0 Conference Paper %B 2nd Workshop on Public Data about Software Development (WoPDaSD 2007) %D 2007 %T A Preliminary Analysis of Publicly Available FLOSS Measurements: Towards Discovering Maintainability Trends %A Samoladas, Ioannis %A Bibi, Stamatia %A Ioannis Stamelos %A Sowe, Sulayman K. %A Deligiannis, Ignatios %K decision tree %K flossmole %K java %K machine learning %K metrics %K sourcekibitzer %X The spread of free/libre/open source software (FLOSS) and the openness of its development model offer researchers a valuable source of information regarding software data. The creation of large portals, which host a vast amount of FLOSS projects make it easy to create large datasets with valuable information regarding the FLOSS development process. In addition initiatives such as FLOSSMole provide researchers with a single point and continuing access to those data. Up to now the majority of datasets from FLOSSMole offered data regarding the development process and not the code itself. From February 2007 FLOSSMole offers data donated by SourceKibitzer, which contain source code metrics for FLOSS projects written in Java. In this paper we provide a premilinary analysis on those data using machine learning techniques, such as classification rules and decision trees. Using the first available data from February 2007, we tried to build rules that can be used in order to estimate the future values of metrics offered for March. Here we present some preliminary results that are encouraging and deserve to be further analyzed in future releases of SourceKibitzer datasets. %B 2nd Workshop on Public Data about Software Development (WoPDaSD 2007) %8 2007 %> https://flosshub.org/sites/flosshub.org/files/Samolades2007.pdf %0 Journal Article %J 2nd Workshop on Public Data about Software Development (WopDaSD 2007) %D 2007 %T Using FLOSSmole Data in Determining Business Readiness Ratings %A Wasserman, Anthony %A Ashutosh Das %K brr %K business readiness rating %K flossmole %X This paper is a preliminary report on using FLOSSmole data retrieved from open source repositories (forges) to calculate Business Readiness Rating scores. %B 2nd Workshop on Public Data about Software Development (WopDaSD 2007) %8 2007 %> https://flosshub.org/sites/flosshub.org/files/Using%20FLOSSmole%20Data%20in%20Determining%20Business%20Readiness%20Ratings.pdf %0 Conference Paper %B 9th International Workshop on Learning Software Organizations %D 2006 %T The FLOSSWALD information system on free and open source software %A Reichle, M. %A Hanft, A. %K debian %K flossmole %X We propose the implementation of an intelligent information system on free and open source software. This system will consist of a case-based reasoning (CBR) system and several machine learning modules to maintain the knowledge base and train the CBR system thus enhancing its performance. Our knowledge base will include data on free and open source software provided by the Debian project, the FLOSSmole project, and other public free and open source software directories. We plan to enrich these data by learning additional information such as concepts and different similarities. With this knowledge base, we hope to be able to create an information system that will be capable of answering queries based on precise as well as vague criteria and give intelligent recommendations on software based on the preferences of the user. %B 9th International Workshop on Learning Software Organizations %8 10/2006 %> https://flosshub.org/sites/flosshub.org/files/flosswald.pdf %0 Journal Article %J Software Process–Improvement and Practice %D 2006 %T Information systems success in Free and Open Source Software development: Theory and measures %A Kevin Crowston %A Howison, James %A Hala Annabi %K bug fixing %K developers %K downloads %K FLOSS %K flossmole %K page views %K popularity %K project success %K size %K sourceforge %K success %K team size %X Information systems success is one of the most widely used dependent variables in information systems (IS) research, but research on Free/Libre and Open Source software (FLOSS) often fails to appropriately conceptualize this important concept. In this paper, we reconsider what success means within a FLOSS context. We first review existing models of IS success and success variables used in FLOSS research and assess them for their usefulness, practicality and fit to the FLOSS context. Then, drawing on a theoretical model of group effectiveness in the FLOSS development process, as well as an online discussion group with developers, we present additional concepts that are central to an appropriate understanding of success for FLOSS. In order to examine the practicality and validity of this conceptual scheme, the second half of our paper presents an empirical study that demonstrates its operationalization of the chosen measures and assesses their internal validity. We use data from SourceForge to measure the project’s effectiveness in team building, the speed of the project at responding to bug reports and the project’s popularity. We conclude by discussing the implications of this study for our proposed extension of IS success in the context of FLOSS development and highlight future directions for research. %B Software Process–Improvement and Practice %V 11 %P 123–148 %R 10.1002/spip.259 %> https://flosshub.org/sites/flosshub.org/files/CrowstonHowisonAnnabi2006.pdf %0 Journal Article %J IEEE Intelligent Systems %D 2006 %T Self-Organization Patterns in Wasp and Open Source Communities %A Valverde, S. %A Theraulaz, G. %A Gautrais, J. %A Fourcassie, V. %A Sole, R.V. %K agents %K decentralization %K developers %K email %K email archives %K flossmole %K hierarchy %K labor division %K organization %K self-organizing teams %K social network analysis %K social networks %K sourceforge %K teams %K wasps %X In this paper, we conducted a comparative study of how social organization takes place in a wasp colony and OSS developer communities. Both these systems display similar global organization patterns, such as hierarchies and clear labor divisions. As our analysis shows, both systems also define interacting agent networks with similar common features that reflect limited information sharing among agents. As far as we know, this is the first research study analyzing the patterns and functional significance of these systems' weighted-interaction networks. By illuminating the extent to which self-organization is responsible for patterns such as hierarchical structure, we can gain insight into the origins of organization in OSS communities. %B IEEE Intelligent Systems %V 21 %P 36 - 40 %8 03/2006 %U http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.95.5574&rep=rep1&type=pdf %N 2 %! IEEE Intell. Syst. %R 10.1109/MIS.2006.34 %> https://flosshub.org/sites/flosshub.org/files/valverde.pdf