3. |
What work practices and culture should be promoted? |
Average
Totally Irrelevant |
Extremely Relevant |
|
No. of Votes
|
|
|
|
3.34
|
The practices of Extreme Programming |
|
10
|
|
Details |
|
|
|
3.25
|
Avoid force |
|
9
|
|
Details |
|
|
|
3.36
|
Standards coding style |
|
9
|
|
Details |
|
|
|
3.19
|
Nothing should be 'promoted'. |
|
9
|
|
Details |
|
|
|
3.37
|
Fun and good spirit and hope |
|
10
|
|
Details |
|
|
|
3.14
|
Awareness of different culture and language background |
|
10
|
|
Details |
|
|
|
3.5
|
Reuse of existing source code |
|
10
|
|
Details |
|
|
|
3.20
|
Openness in attitude, no hidden agenda |
|
9
|
|
Details |
|
|
|
3.11
|
Distributed style of development and decentralised decision-making |
|
10
|
|
Details |
|
|
|
3.2
|
Measurement of quality of code |
|
10
|
|
Details |
|
|
|
3.32
|
A system to attribute credit |
|
10
|
|
Details |
|
|
|
3.28
|
Using centralised repository for source code |
|
10
|
|
Details |
|
|
|
3.6
|
Do not focus on the volume of software created, but usefulness |
|
10
|
|
Details |
|
This sub-question is summarised from the following answer(s) from round 1
|
Mark
|
reuse of existing code by developers! sourceforge in particular fails horribly to promote a culture of reuse, by collecting and "ranking" statistics on such misguided metrics as "number of new commits to CVS". since sourceforge is a commercial venture, they want to promote the multiplicity of projects, but this behaviour undermines the central benefit of free software: reuse and modification of others' code.
clarification: the "number of new commits to CVS" is a very sourceforge-specific example, and is meaningless as a general survey concept. they also, for example, have a "new projects this week" statistic which is troubling. what I really wanted to get at was: don't focus the site purely on the "creation of new software" (though this is perhaps the most fun part of programming) but rather on "finding software which solves your problem". e.g. make it easy for one project to depend on another (or several others), make it easy to cross-reference documentation between projects, etc.
|
Comment made in round 2
|
Neil
| All software is valuable, regardless of size or purpose. None should be discouraged.
|
Relevant Glossary
|
Concurrent Versions System ,
SourceForge |
|
|
3.22
|
Cooperation and collaboration, encourage involvement of developers to share the load of development |
|
10
|
|
Details |
|
|
|
3.8
|
Computer science/software engineering knowledge |
|
10
|
|
Details |
|
|
|
3.4
|
Reinforcing explicit development roles |
|
10
|
|
Details |
|
|
|
3.23
|
Firmness |
|
8
|
|
Details |
|
|
|
3.24
|
Keeping promises |
|
8
|
|
Details |
|
|
|
3.3
|
Prioritization of new features |
|
9
|
|
Details |
|
|
|
3.12
|
Welcome help from less skilled developers and understand their potential to become high skilled developers |
|
10
|
|
Details |
|
|
|
3.15
|
Awareness of different technology background |
|
10
|
|
Details |
|
|
|
3.18
|
The value of heterogeneity, differences as assets |
|
10
|
|
Details |
|
|
|
3.21
|
Openness in procedures and policies |
|
10
|
|
Details |
|
|
|
3.7
|
Emphasis on history, reuse old resources |
|
10
|
|
Details |
|
|
|
3.33
|
Standards in software design |
|
10
|
|
Details |
|
|
|
3.26
|
Critique for the sake of the task |
|
10
|
|
Details |
|
|
|
3.13
|
Tolerance, respect and patience |
|
10
|
|
Details |
|
|
|
3.30
|
Easy to use, high usability |
|
10
|
|
Details |
|
|
|
3.9
|
Creating a public library atomsphere, giving users as much freedom as possible and staying out of the users' way |
|
10
|
|
Details |
|
|
|
3.31
|
Flexibility in tools for rapid project administration |
|
9
|
|
Details |
|
|
|
3.16
|
Listening to others |
|
9
|
|
Details |
|
|
|
3.38
|
Frequent submissions of contributions |
|
10
|
|
Details |
|
|
|
3.10
|
Documentation of source code and standards in writing style |
|
10
|
|
Details |
|
|
|
3.17
|
Flexibility towards volunteers |
|
10
|
|
Details |
|
|
|
3.29
|
To include automated building and testing facilities in releases |
|
10
|
|
Details |
|
|
|
3.1
|
Sense of responsibility |
|
10
|
|
Details |
|
|
|
3.35
|
Clarity, simpleness of code |
|
10
|
|
Details |
|
|
|
3.27
|
Jane Jacob's systems of survival's commercial moral syndrome |
|
2
|
|
Details |
|
|