@proceedings {1467,
	title = {A Linguistic Analysis on How Contributors Solve Software Problems in a Distributed Context},
	volume = {378},
	year = {2012},
	note = {"... a sample of 4109 bug reports was extracted from Bugzilla bug report repository"
"The analysis of our sample allows identifying the roles of participants in this activity according to their hierarchical statutes in the community. "
"we look statistically at words that people use in Bugzilla to discern differences in the discourse and representation between participants (core and periphery)"},
	month = {09/2012},
	pages = {322-330},
	publisher = {IFIP AICT,  Springer},
	abstract = {There is a little understanding of distributed solving activities in Open Source communities. This study aimed to provide some insights in this way. It was applied to the context of Bugzilla, the bug tracking system of Mozilla community. This study investigated the organizational aspects of this meditated, complex and highly distributed context through a linguistic analysis method. The main finding of this research shows that the organization of distributed problem-solving activities in Bugzilla isn{\textquoteright}t based only on the hierarchical distribution of the work between core and periphery participants but on their implication in the interactions. This implication varies according to the status of each one participant in the community. That is why we distinguish their roles, as well as, the established modes to manage such activity.},
	keywords = {bug report, bugzilla, linguistic, text mining},
	author = {Masmoudi, H{\'e}la and Boughzala, Imed}
}
@conference {593,
	title = {Peeling the Onion},
	booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)},
	series = {IFIP Advances in Information and Communication Technology },
	volume = {299/2009},
	year = {2009},
	month = {2009///},
	pages = {284 - 297},
	publisher = {Springer},
	organization = {Springer},
	chapter = {25},
	abstract = {According to the now widely accepted {\textquotedblleft}onion-model{\textquotedblright} of the organization of open source software development, an open source project typically relies on a core of developers that is assisted by a larger periphery of users. But what does the role of the periphery consist of? Raymond{\textquoteright}s Linus{\textquoteright}s Law which states that {\textquotedblleft}given enough eyeballs all bugs are shallow{\textquotedblright} suggests at least one important function: the detection of defects. Yet, what are the ways through which core and periphery interact with each other? With the help of text-mining methods, we study the treatment of bugs that affected the Firefox Internet browser as reflected in the discussions and actions recorded in Mozilla{\textquoteright}s issue tracking system Bugzilla. We find various patterns in the modes of interactions between core and peripheral members of the community. For instance, core members seem to engage more frequently with the periphery when the latter proposes a solution (a patch). This leads us to conclude that Alan Cox{\textquoteright}s dictum {\textquotedblleft}show me the code{\textquotedblright}, perhaps even more than Linus{\textquoteright}s law, seems to be the dominant rule that governs the development of software like Firefox.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_25},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Peeling\%20the\%20Onion.pdf},
	author = {Masmoudi, H{\'e}la and den Besten, Matthijs and de Loupy, Claude and Jean-Michel Dalle}
}
@conference {549,
	title = {Channeling Firefox Developers: Mom and Dad Aren{\textquoteright}t Happy Yet},
	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 = {265 - 271},
	publisher = {Springer},
	organization = {Springer},
	chapter = {22},
	abstract = {Firefox, a browser targeted at mainstream users, has been one of the big successes of open source development in recent years. That Firefox succeeded where earlier attempts failed is undoubtedly due to the particular choices that were made in the process of development. In this paper, we look at this process in more detail. Mining bug reports and feature requests related to Firefox in Mozilla{\textquoteright}s Bugzilla bug tracker system, we find that the attention developers devoted to reports and requests was influenced by several factors. Most importantly, other things being equal, reports and requests from outsiders increasingly tend to be ignored. While such behavior may have helped to shield Firefox from the {\textquotedblleft}alpha-geek power user{\textquotedblright} in the early stages of development, it also makes it difficult for {\textquotedblleft}mom and dad{\textquotedblright} to let their voice be heard even after they have adopted Firefox.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_22},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Channeling\%20Firefox\%20Developers.pdf},
	author = {Jean-Michel Dalle and den Besten, Matthijs and Masmoudi, H{\'e}la}
}
@conference {1213,
	title = {Working with Open Source Development Data: Considerations triggered by a study of bug scenarios},
	booktitle = {2nd Workshop on Public Data about Software Development (WoPDaSD 2007)},
	year = {2007},
	month = {2007},
	abstract = {The retrieval and preparation of public data on software development calls for more than just technical skills. In 
addition, care and judgement are needed to avoid disproportionate costs to the providers of data or unnecessary embarrassment to the participants tracked in the data. Taking the extraction of bug scenarios as a use case, we illustrate these concerns and discuss how they could be translated into social requirements that would help to make retrieval and preparation a sustainable exercise. In particular, we call for more efforts to establish institutional repositories of public data on software development and, besides, we suggest that reviewers could play a role in making sure that empirical research is performed in a way that does not bring the long-term relationship between software developers and researchers in jeopardy. },
	keywords = {bug reports, bug scenarios, Data Collection},
	attachments = {https://flosshub.org/sites/flosshub.org/files/denBesten-wopdasd.pdf},
	author = {den Besten, Matthijs and Masmoudi, H{\'e}la and Jean-Michel Dalle}
}
