[FIX] Code Of Conduct simpler

CODE_OF_CONDUCT.md

-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, gender identity and expression, level of experience,
-nationality, personal appearance, race, religion, or sexual identity and
-orientation.
-
-## Our Standards
-
-Examples of behavior that contributes to creating a positive environment
-include:
-
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
-
-Examples of unacceptable behavior by participants include:
-
-* The use of sexualized language or imagery and unwelcome sexual attention or
-advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic
-  address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Our Responsibilities
-
-Project maintainers are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
-
-Project maintainers have the right and responsibility to remove, edit, or
-reject comments, commits, code, wiki edits, issues, and other contributions
-that are not aligned to this Code of Conduct, or to ban temporarily or
-permanently any contributor for other behaviors that they deem inappropriate,
-threatening, offensive, or harmful.
-
-## Scope
-
-This Code of Conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project e-mail
-address, posting via an official social media account, or acting as an appointed
-representative at an online or offline event. Representation of a project may be
-further defined and clarified by project maintainers.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at [sos AT gargantext DOT org]. All
-complaints will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. The project team is
-obligated to maintain confidentiality with regard to the reporter of an incident.
-Further details of specific enforcement policies may be posted separately.
-
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
-available at [http://contributor-covenant.org/version/1/4][version]
-
-[homepage]: http://contributor-covenant.org
-[version]: http://contributor-covenant.org/version/1/4/
+# GarganText "Code of Conduct"
+
+The GarganText Project, the contributors of the GarganText eco-system,
+have adopted a code of conduct for participants to any modes of
+communication within the project.
+
+## Be respectful
+
+In a project the size of GarganText, inevitably there will be people
+with whom you may disagree, or find it difficult to cooperate. Accept
+that, but even so, remain respectful. Disagreement is no excuse for poor
+behaviour or personal attacks, and a community in which people feel
+threatened is not a healthy community.
+
+## Assume good faith
+
+GarganText Contributors have many ways of reaching our common goal of
+a free digital ecosystem which may differ from your ways. Assume that
+other people are working towards this goal.
+
+Note that many of our Contributors are not native English speakers
+or may have different cultural backgrounds.
+
+## Be collaborative
+
+GarganText is a large and complex project; there is always more to
+learn within GarganText. It's good to ask for help when you need it.
+Similarly, offers for help should be seen in the context of our shared
+goal of improving GarganText.
+
+When you make something for the benefit of the project, be willing
+to explain to others how it works, so that they can build on your work
+to make it even better.
+
+## Try to be concise
+
+Keep in mind that what you write once will be read by many others
+persons. Writing a short email means people can understand the
+conversation as efficiently as possible. When a long explanation is
+necessary, consider adding a summary.
+
+Try to bring new arguments to a conversation so that each comment
+adds something unique to the thread, keeping in mind that the rest of
+the thread still contains the other messages with arguments that have
+already been made.
+
+Try to stay on topic, especially in discussions that are already
+fairly large.
+
+## Be open
+
+Most ways of communication used within GarganText allow for public and
+private communication. You should preferably use public methods of
+communication for GarganText-related messages, unless posting something
+sensitive.
+
+This applies to messages for help or GarganText-related support,
+too; not only is a public support request much more likely to
+result in an answer to your question, it also makes sure that any
+inadvertent mistakes made by people answering your question will be
+more easily detected and corrected.
+
+While this code of conduct should be adhered to by participants,
+we recognize that sometimes people may have a bad day, or be unaware
+of some of the guidelines in this code of conduct. When that happens,
+you may reply to them and point out this code of conduct. Such messages
+may be in public or in private, whatever is most appropriate. However,
+regardless of whether the message is public or not, it should still
+adhere to the relevant parts of this code of conduct; in particular, it
+should not be abusive or disrespectful. Assume good faith; it is more
+likely that participants are unaware of their bad behaviour than that
+they intentionally try to degrade the quality of the discussion.
+
+Serious or persistent offenders will be temporarily or permanently
+banned from communicating through GarganText's ecosystem. Complaints
+should be made (in private) to the administrators of the GarganText
+communication forum in question. To find contact information for these
+administrators, please see the page on GarganText's organizational
+structure.

src/Gargantext/Core/Viz/Graph.hs

@@ -227,7 +227,8 @@ graphV3ToGraph (GraphV3 links nodes) = Graph { _graph_nodes = map nodeV32node no
                        , node_x_coord = 0
                        , node_y_coord = 0
                        , node_attributes = Attributes cl'
-                       , node_children = [] }
+                       , node_children = []
+                       }
 
     linkV32edge :: Int -> EdgeV3 -> Edge
     linkV32edge n (EdgeV3 eo_s' eo_t' eo_w') =