Proceedings. IEEE 8th International Workshops on Enabling Technologies: Infrastructure for Collaborative Enterprises (WET ICE'9
DOI: 10.1109/enabl.1999.805176
|View full text |Cite
|
Sign up to set email alerts
|

Coordinating open-source software development

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
20
0
2

Publication Types

Select...
3
2
2

Relationship

1
6

Authors

Journals

citations
Cited by 22 publications
(22 citation statements)
references
References 8 publications
0
20
0
2
Order By: Relevance
“…are typically widely distributed, communication tends to be asynchronous, and to be supported electronically [5].…”
Section: Communication Channels Since Project Membersmentioning
confidence: 99%
See 1 more Smart Citation
“…are typically widely distributed, communication tends to be asynchronous, and to be supported electronically [5].…”
Section: Communication Channels Since Project Membersmentioning
confidence: 99%
“…There are three parameters in any request from the client for suggestions. Two of the arguments are required: the first identifies anonymously the user, 5 and the second identifies artifact for which related items are sought. An optional third argument is intended to further describe the context of the query for additional tailoring of recommendations, although it is not used at this time.…”
Section: Hipikat Prototypementioning
confidence: 99%
“…Open Source (OSS) projects represent the typical situation where coordination problems arise, since developers contribute from around the world, meet face-to-face infrequently, and need to coordinate virtually (Crowston et al, 2005). For example, the entry barrier is a problem that has been acknowledged by OSS developers (Cubranic and Booth, 1999): a newcomer needs to understand the existing code and read the available documentation. Usually, this is a very time consuming and tedious task.…”
Section: Introductionmentioning
confidence: 99%
“…The details of conduct, input and output elements, sequencing, and resource needs of tasks are central elements of any software development method and the core of this discourse (e.g., Cubranic and Booth 1999;Egyedi 2004).…”
Section: Software Development Methods As Socio-technical Theoriesmentioning
confidence: 99%
“…Members of any project move from peripheral roles to a core developer role in the proj ect through a merit-based process (Cubranic and Booth 1999). An individual' s technical expertise and participation in developing the product results in his/her inclusion in the core group of developers.…”
Section: Free/libre Open Source Softwarementioning
confidence: 99%