]> Git — Sourcephile - gargantext.git/blob - CODE_OF_CONDUCT.md
[VERSION] +1 to 0.0.6.9.9.4.3
[gargantext.git] / CODE_OF_CONDUCT.md
1 # GarganText "Code of Conduct"
2
3 The GarganText Project, the contributors of the GarganText eco-system,
4 have adopted a code of conduct for participants to any modes of
5 communication within the project.
6
7 ## Be respectful
8
9 In a project the size of GarganText, inevitably there will be people
10 with whom you may disagree, or find it difficult to cooperate. Accept
11 that, but even so, remain respectful. Disagreement is no excuse for poor
12 behaviour or personal attacks, and a community in which people feel
13 threatened is not a healthy community.
14
15 ## Assume good faith
16
17 GarganText Contributors have many ways of reaching our common goal of
18 a free digital ecosystem which may differ from your ways. Assume that
19 other people are working towards this goal.
20
21 Note that many of our Contributors are not native English speakers
22 or may have different cultural backgrounds.
23
24 ## Be collaborative
25
26 GarganText is a large and complex project; there is always more to
27 learn within GarganText. It's good to ask for help when you need it.
28 Similarly, offers for help should be seen in the context of our shared
29 goal of improving GarganText.
30
31 When you make something for the benefit of the project, be willing
32 to explain to others how it works, so that they can build on your work
33 to make it even better.
34
35 ## Try to be concise
36
37 Keep in mind that what you write once will be read by many others
38 persons. Writing a short email means people can understand the
39 conversation as efficiently as possible. When a long explanation is
40 necessary, consider adding a summary.
41
42 Try to bring new arguments to a conversation so that each comment
43 adds something unique to the thread, keeping in mind that the rest of
44 the thread still contains the other messages with arguments that have
45 already been made.
46
47 Try to stay on topic, especially in discussions that are already
48 fairly large.
49
50 ## Be open
51
52 Most ways of communication used within GarganText allow for public and
53 private communication. You should preferably use public methods of
54 communication for GarganText-related messages, unless posting something
55 sensitive.
56
57 This applies to messages for help or GarganText-related support,
58 too; not only is a public support request much more likely to
59 result in an answer to your question, it also makes sure that any
60 inadvertent mistakes made by people answering your question will be
61 more easily detected and corrected.
62
63 While this code of conduct should be adhered to by participants,
64 we recognize that sometimes people may have a bad day, or be unaware
65 of some of the guidelines in this code of conduct. When that happens,
66 you may reply to them and point out this code of conduct. Such messages
67 may be in public or in private, whatever is most appropriate. However,
68 regardless of whether the message is public or not, it should still
69 adhere to the relevant parts of this code of conduct; in particular, it
70 should not be abusive or disrespectful. Assume good faith; it is more
71 likely that participants are unaware of their bad behaviour than that
72 they intentionally try to degrade the quality of the discussion.
73
74 Serious or persistent offenders will be temporarily or permanently
75 banned from communicating through GarganText's ecosystem. Complaints
76 should be made (in private) to the administrators of the GarganText
77 communication forum in question. To find contact information for these
78 administrators, please see the page on GarganText's organizational
79 structure.