3. |
What work practices and culture should be promoted? |
Totally Irrelevant |
Extremely Relevant |
|
|
3.1
|
Sense of responsibility |
|
|
3.2
|
Measurement of quality of code |
|
|
3.3
|
Prioritization of new features |
|
|
3.4
|
Reinforcing explicit development roles |
|
|
3.5
|
Reuse of existing source code |
|
|
3.6
|
Do not focus on the volume of software created, but usefulness
Comment: |
All software is valuable, regardless of size or purpose. None should be discouraged.
|
|
|
|
3.7
|
Emphasis on history, reuse old resources |
|
|
3.8
|
Computer science/software engineering knowledge |
|
|
3.9
|
Creating a public library atomsphere, giving users as much freedom as possible and staying out of the users' way |
|
|
3.10
|
Documentation of source code and standards in writing style |
|
|
3.11
|
Distributed style of development and decentralised decision-making |
|
|
3.12
|
Welcome help from less skilled developers and understand their potential to become high skilled developers |
|
|
3.13
|
Tolerance, respect and patience |
|
|
3.14
|
Awareness of different culture and language background |
|
|
3.15
|
Awareness of different technology background |
|
|
3.16
|
Listening to others |
|
|
3.17
|
Flexibility towards volunteers |
|
|
3.18
|
The value of heterogeneity, differences as assets |
|
|
3.19
|
Nothing should be 'promoted'. |
|
|
3.20
|
Openness in attitude, no hidden agenda |
|
|
3.21
|
Openness in procedures and policies |
|
|
3.22
|
Cooperation and collaboration, encourage involvement of developers to share the load of development |
|
|
3.23
|
Firmness
Comment: |
eh? No one likes a flabby arse.
|
|
|
|
3.24
|
Keeping promises
Comment: |
If a site agrees to make their CVS server stable, it should be stable. :-)
|
|
|
|
3.25
|
Avoid force
|
|
|
3.26
|
Critique for the sake of the task |
|
|
3.27
|
Jane Jacob's systems of survival's commercial moral syndrome
Comment: |
Provide a hyperlink to what you mean here. http://www.grist.org/articles/2000/00.10.19_Systems_of_Survival.html
|
|
|
|
3.28
|
Using centralised repository for source code |
|
|
3.29
|
To include automated building and testing facilities in releases |
|
|
3.30
|
Easy to use, high usability |
|
|
3.31
|
Flexibility in tools for rapid project administration |
|
|
3.32
|
A system to attribute credit
Comment: |
USeful for those who wish to brag, or more important when a projects copyright is being tested
|
|
|
|
3.33
|
Standards in software design |
|
|
3.34
|
The practices of Extreme Programming
Comment: |
This is very cool. Most sites do not help pair programming and refactoring, and it's necessary
|
|
|
|
3.35
|
Clarity, simpleness of code |
|
|
3.36
|
Standards coding style
Comment: |
K&R is Evil(tm). The "GNU Coding Standards" are wrong and lead directly to lesser quality code.
|
|
|
|
3.37
|
Fun and good spirit and hope
Comment: |
If you don't like it, don't do it.
|
|
|
|
3.38
|
Frequent submissions of contributions
Comment: |
Speed of projects is irrelevant - particularly volunteer led ones.
|
|
|