|
22.
|
|
|
Nobody is expected to be perfect in this community. Asking questions
early avoids many problems later, so questions are encouraged,
though they may be directed to the appropriate forum. Those who are
asked should be responsive and helpful.
|
|
|
type: Plain text
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
CodeOfConduct.txt:79
|
|
23.
|
|
|
'''Step down considerately.'''
|
|
|
type: Plain text
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
CodeOfConduct.txt:81
|
|
24.
|
|
|
When somebody leaves or disengages from the project, we ask that
they do so in a way that minimises disruption to the project. They
should tell people they are leaving and take the proper steps to
ensure that others can pick up where they left off.
|
|
|
type: Plain text
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
CodeOfConduct.txt:86
|
|
25.
|
|
|
== Leadership, Authority and Responsibility ==
|
|
|
type: Plain text
|
|
|
|
(no translation yet)
|
|
|
|
Located in
CodeOfConduct.txt:89
|
|
26.
|
|
|
We all lead by example, in debate and in action. We encourage new participants to feel empowered to lead, to take action, and to experiment when they feel innovation could improve the project. Leadership can be exercised by anyone simply by taking action, there is no need to wait for recognition when the opportunity to lead presents itself.
|
|
|
type: Plain text
|
|
|
|
(no translation yet)
|
|
|
|
Located in
CodeOfConduct.txt:96
|
|
33.
|
|
|
'''We value discussion, data and decisiveness.'''
|
|
|
type: Plain text
|
|
|
|
(no translation yet)
|
|
|
|
Located in
CodeOfConduct.txt:120
|
|
34.
|
|
|
We gather opinions, data and commitments from concerned parties before taking a decision. We expect leaders to help teams come to a decision in a reasonable time, to seek guidance or be willing to take the decision themselves when consensus is lacking, and to take responsibility for implementation.
|
|
|
type: Plain text
|
|
|
|
(no translation yet)
|
|
|
|
Located in
CodeOfConduct.txt:126
|
|
35.
|
|
|
The poorest decision of all is no decision: clarity of direction has value in itself. Sometimes all the data are not available, or consensus is elusive. A decision must still be made. There is no guarantee of a perfect decision every time - we prefer to err, learn, and err less in future than to postpone action indefinitely.
|
|
|
type: Plain text
|
|
|
|
(no translation yet)
|
|
|
|
Located in
CodeOfConduct.txt:132
|
|
36.
|
|
|
We recognise that the project works better when we trust the teams closest to a problem to make the decision for the project. If we learn of a decision that we disagree with, we can engage the relevant team to find common ground, and failing that, we have a governance structure that can review the decision. Ultimately, if a decision has been taken by the people responsible for it, and is supported by the project governance, it will stand. None of us expects to agree with every decision, and we value highly the willingness to stand by the project and help it deliver even on the occasions when we ourselves may prefer a different route.
|
|
|
type: Plain text
|
|
|
|
(no translation yet)
|
|
|
|
Located in
CodeOfConduct.txt:143
|
|
37.
|
|
|
'''Open meritocracy.'''
|
|
|
type: Plain text
|
|
|
|
(no translation yet)
|
|
|
|
Located in
CodeOfConduct.txt:145
|