A socio-cognitive analysis of online design discussions in an Open Source Software community

From AcaWiki
Jump to: navigation, search


Citation: Flore Barcellini, Françoise Détienne, Jean-Marie Burkhardt, Warren Sack (2008) A socio-cognitive analysis of online design discussions in an Open Source Software community. Interacting with Computers (RSS)

doi: 10.1016/j.intcom.2007.10.004


Tagged: Computer Science (RSS) open source (RSS), design methodology (RSS), CSCW (RSS), design rationale (RSS), Open Source Software Community (RSS), cognitive ergonomics (RSS), argumentation (RSS), online argumentation (RSS)


Summary:

This paper synthesizes Barcellini's previous research on the Python community. Its purpose is to outline a theoretical framework and methodology combining structural and content analyses. While the analysis challenges the Bazaar model of open source software development, and provides potential improvements for structural browsing of design discussions and listservs, its hand-construction is too laborious for routine use. The researchers hope that some of this methodology could be automated, for instance in the Conversation Map*.

This paper presents a theoretical framework for those earlier findings, namely focusing on three questions, from three different areas: social dynamics, thematic temporal dynamics, and design dynamics. A quotation-based graph model is used for presenting discussions of two Python listserv discussions; these discussions concerned design decisions called Python Enhancement Proposals (PEPs).

Social Dynamics

Question: whether "participants with different statuses take part differently in the online discussions and the design process". (The answer, as we know from following Barcellini's earlier work on the Python community, is yes.)

Methodology: Addressed in 4 ways: number of messages, type of quotation structure, depth of quotation, postion in the discussion.

Key Findings: Roles emerge. For instance, the project leader and the person championing a proposal are frequent contributors and their messages receive multiple responses. Only the champion writes syntheses. There is shared power, both among the leadership and with developers; developers participate "even if discussions are framed by the project leader, the administrators, and the champion of PEP".

Thematic Temporal Dynamics (how themes change over time)

Question: are designs and themes important for online design discussions? Are these discussions different from face-to-face exchanges?

Methodology: Addressed by the themes and the temporal order of posts and their quotations.


Key Findings: Initial messages are multi-theme; later messages are more specialized on a single theme. To ensure they are "timely" (according to community standards messages may be posted quickly, with many messages typically received within an hour's time.


Design Dynamics

Question: Are the collaborative design activities and sequence the same in online, open source software communities, and in face-to-face design?

Methodology: Addressed by a content analysis.

Key Findings: evaluation is key and clarification may be moved elswhere as "off-topic". "Few decisions are taken during the online discussions, but those decisions taken are explicit. "

Theoretical Framework

In addition to what was proposed in earlier work, this paper gives a theoretical framework, and gives names to ideas discussed earlier, such as

Quotation Patterns

  1. Sequential structure (quoted by one message)
  2. Branching structure (quoted by multiple messages)
  3. Closing structure (not quoted)

Temporality

  1. Quotation temporality (delay before a message is posted)
  2. Theme temporality (how long a theme is discussed)

Design View

The design view discussed in A study of online discussion in an Open-Source community: reconstructing thematic coherence and argumentation from quotation practices is further described and slightly revised, with definitions for particular activities:

  1. Proposal
  2. Evaluation
  3. Group coordination
  4. Synthesis
  5. Clarification
  6. Explicit decision
  7. Other activities (e.g. humor)

Other material not significantly discussed in Barcellini's earlier work

Additionally, these areas are

Types of collaborative design activities

  • Generative-evaluation activities - Process of solving and evaluating design problems
  • Clarification activities - (or cognitive synchronization) - Constructing a shared representation
  • Group management activities

Results section

The results section provides further analysis. Results are discussed in detail in section 6, not analyzed here. (Please add this if you can!)


pp. 233–240.

Theoretical and practical relevance:

Challenges the bazaar model, at least for the Python project. Seeks automatic analysis to repeat this work on other corpora.

Argumentation

The relevant argumentation background is that "Co-designers accomplish evaluation activities by arguing with each other." These arguments have been characterized as sequences of moves or turns, see