Skip to main content

Table 2 The research instrument with questions and their coded answers

From: Organizing for openness: six models for developer involvement in hybrid OSS projects

  Eclipse Netbeans Qt Vaadin GTK+ Sailfish
A Who can contribute source code? 2 2 3 3 3 2a
B Who can test code contributions? 3 2 3 0 3 1a
C Who can accept code contributions? 2 2 2 0 2 1a
D Who can access the complete, live development version? 3 3 1 3 3 0a
E Who can impact work issue priorities? 3 3 3 0 3 0a
F Who knows integration status of code contributions? 3 2 3 3 3 1
G Who can view the product roadmap? 3 3 1 0 3 0
H Who knows release timing and content? 3 3 1 3 3 0
I Who knows priorities of work issues? 3 3 3 0 3 0
  1. 0) Closed from outsiders, 1) Open only to an exclusive group, 2) Open to accredited individuals, 3) Open to any external observer
  2. aDue to the distributed repository strategy, practices vary per software component