How artefacts rule web-based communities: practices of free software development

Stefano De Paoli, Vincenzo D'Andrea

Research output: Contribution to journalArticlepeer-review

4 Citations (Scopus)


This paper seeks to understand how complex tasks are accomplished by large web-based communities. In order to do so, we consider that technologies may embody organisational rules, hence becoming the core of coordination efforts in such communities. Our analysis is based on the concepts of translation and inscription taken from the Actor-Network Theory, while the data have been gathered using an ethnographic approach. We base our observation on the case of a Geographic Information System (GIS): the Geographic Resources Analysis Support System (GRASS) is a system developed by a small group of developers but sustained by a very large users| base located worldwide. In particular, we focus on small explanatory examples of everyday development activities of the GRASS community in relation to the internationalisation process. We focus on artefacts, such as the Concurrent Versioning System and the GRASS source code, that greatly affect the everyday activities of the community. The main result of our research is the illustration that complex tasks are accomplished by large web-based communities, thanks to many small contributions shaped and organised by the rules embodied in artefacts.
Original languageEnglish
Pages (from-to)199-219
Number of pages21
JournalInternational Journal of Web Based Communities
Issue number2
Publication statusPublished - 2008
Externally publishedYes


  • Bazaar development style
  • Programming practices
  • Translation process
  • Coordination
  • Artefacts
  • Web based communities
  • Free software
  • Software development
  • Actor-network theory
  • Ethnography
  • Geographical information system
  • GIS
  • Online communities
  • Virtual communities


Dive into the research topics of 'How artefacts rule web-based communities: practices of free software development'. Together they form a unique fingerprint.

Cite this