What characterize documents that bridge boundaries compared to documents that do not? An exploratory study of documentation in FLOSS teams

Research output: Chapter in Book/Report/Conference proceedingConference contribution

3 Scopus citations

Abstract

Organizations bring together people with various access to and understanding of the work at hand. Despite their different stocks of background knowledge, most of them engage in documentation, whether as writers or readers. This paper explores how documents serve such diverse users by building a framework articulating the characteristics of documents supporting collaborators with asymmetric access to knowledge versus people with symmetric knowledge. Drawing on document-centric approaches we hypothesize that documents supporting asymmetric groups are likely to be more prescriptive and explicate their own use compared to documents supporting symmetric groups. Through exploratory analysis of two kinds of documents, used across three FLOSS projects, we find that documents supporting collaborators with asymmetric knowledge do appear to explicate their own use in more detail. They do so by prescribing their own 1) purpose, 2) context of use, 3) content and form in greater detail than documents used by core community members with symmetric access to project knowledge.

Original languageEnglish (US)
Title of host publicationProceedings of the 44th Annual Hawaii International Conference on System Sciences, HICSS-44 2010
DOIs
StatePublished - Mar 28 2011
Event44th Hawaii International Conference on System Sciences, HICSS-44 2010 - Koloa, Kauai, HI, United States
Duration: Jan 4 2011Jan 7 2011

Publication series

NameProceedings of the Annual Hawaii International Conference on System Sciences
ISSN (Print)1530-1605

Other

Other44th Hawaii International Conference on System Sciences, HICSS-44 2010
CountryUnited States
CityKoloa, Kauai, HI
Period1/4/111/7/11

ASJC Scopus subject areas

  • Engineering(all)

Fingerprint Dive into the research topics of 'What characterize documents that bridge boundaries compared to documents that do not? An exploratory study of documentation in FLOSS teams'. Together they form a unique fingerprint.

Cite this