Updating and adding pages.

Signed-off-by: Dennis Labordus <[email protected]>

Author: Dennis Labordus

docs/DEVELOPING.md

@@ -3,7 +3,6 @@
 #### Table Of Contents
 
 * [Tooling](#tooling)
-* [Styleguides](#styleguides)
 * [IDEs](#ides)
 * [GitHub Actions](#github-actions)
 * [Others](#others)
@@ -44,7 +43,7 @@ The project uses Maven to manage the build. Most projects use multi-module struc
 $ maven clean verify
 ```
 
-### GitHub Packages in Maven
+#### GitHub Packages in Maven
 To use GitHub Packages in Maven an extra repository need to be added to the build process.
 ```xml
 <repositories>
@@ -57,7 +56,7 @@ To use GitHub Packages in Maven an extra repository need to be added to the buil
 ```
 Because credentials are needed for GitHub Packages, these will be passed by using the Settings.xml file.
 
-### Maven Local Settings.xml for GitHub Packages
+#### Maven Local Settings.xml for GitHub Packages
 Edit (or create if not already exists) the `~/.m2/settings.xml` file and add the following content:
 ```xml
 <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0" 
@@ -80,26 +79,6 @@ Add this server section. The ID of the server must be the same as the ID found i
 Username should be your GitHub username, password can both be your own [encrypted password](https://maven.apache.org/guides/mini/guide-encryption.html)
 or a [Personal Access Token](https://docs.github.com/en/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token).
 
-## Styleguides
-
-### Git Commit Messages
-
-As usual, please start the commit message with a short line describing the commit, then leave a blank line, then give more context and explanations. You can use GitHub's integrations, for exemple to link to existing issues. In general, pull requests with more than one commits will be squashed when merged in master.
-
-### Java StyleGuide
-
-- The project uses modern java, feel free to use any new APIs provided by the current java version (currently java 8).
-- New API classes and methods should be documented with javadoc. Write higher level documentation for classes and lower level documentation for methods. For example, ...
-- User-facing configuration options and general design decisions should be documented (where?)
-- We use standard configurations of well known tools like checkstyle and sonarqube to enforce a coherent coding style, please consult those tools for justifications on these rules.
-
-As a simple yet instructive example, consider ...
-```java
-/**
- * Example?
- */
-```
-
 ## IDEs
 If your IDE is supported by sonarlint (both IntelliJ IDEA and the Eclipse IDE are supported), it is recommended to install it. 
 It provides immediate feedback on most sonar issues. Running tests individually is often possible in IDEs without invoking maven. 

docs/GOVERNANCE.md

@@ -10,19 +10,25 @@
 
 ## Project Owner
 
-CoMPAS is part of the [LF Energy Foundation](https://www.lfenergy.org/), a project of The Linux Foundation that supports open source innovation projects within the energy and electricity sectors.
+CoMPAS is part of the [LF Energy Foundation](https://www.lfenergy.org/), a project of The Linux Foundation that supports 
+open source innovation projects within the energy and electricity sectors.
 
 ## Technical Charter
 
-The Project's [Technical Charter](blob-files/CoMPAS_Technical_Charter_2020-06-07.pdf) sets forth the responsibilities and procedures for technical contribution to, and oversight of, the COMPAS Project.
+The Project's [Technical Charter](blob-files/CoMPAS_Technical_Charter_2020-06-07.pdf) sets forth the responsibilities and 
+procedures for technical contribution to, and oversight of, the COMPAS Project.
 
 ## Committers
 
-Committers are contributors who have made several valuable contributions to the project and are now relied upon to both write code directly to the repository and screen the contributions of others. In many cases they are programmers but it is also possible that they contribute in a different role. Typically, a committer will focus on a specific aspect of the project, and will bring a level of expertise and understanding that earns them the respect of the community and the project owner.
+Committers are contributors who have made several valuable contributions to the project and are now relied upon to both 
+write code directly to the repository and screen the contributions of others. In many cases they are programmers, 
+but it is also possible that they contribute in a different role. Typically, a committer will focus on a specific aspect 
+of the project, and will bring a level of expertise and understanding that earns them the respect of the community and the project owner.
 
 ## Technical Steering Committee
 
-The Technical Steering Committee (TSC) is composed of voting members elected by the active Committers as described in the project’s Technical Charter. The TSC is responsible for the technical direction of the project.
+The Technical Steering Committee (TSC) is composed of voting members elected by the active Committers as described in the 
+project’s Technical Charter. The TSC is responsible for the technical direction of the project.
 
 ## Members
 
@@ -36,21 +42,26 @@ CoMPAS TSC voting members are:
 
 ## Voting
 
-While the Project aims to operate as a consensus-based community, if any TSC decision requires a vote to move the Project forward, the voting members of the TSC will vote on a one vote per voting member basis. The simple majority is needed to approve proposals.
+While the Project aims to operate as a consensus-based community, if any TSC decision requires a vote to move the Project 
+forward, the voting members of the TSC will vote on a one vote per voting member basis. The simple majority is needed to approve proposals.
 The preferred way to vote is to create a poll [here](https://lists.lfenergy.org/g/CoMPAS-tsc/addpoll).
 
 ## Responsibilities
 
-The project is split into several repositories. There is at least one Committer in charge of each repository. By "in charge", we mean:
--	best effort to review the pull request,
--	best effort to resolve issues,
--	building and publishing the releases, including writing the release notes and informing the community,
--	in case of unability to perform the above tasks, the Committer in charge has to ask the TSC through the list [[email protected]](mailto:[email protected]) to find another Committer to review the pull request, resolve the issue or build and publish the release.
+The project is split into several repositories. There is at least one Committer in charge of each repository. 
+By "in charge", we mean:
+- best effort to review the pull request,
+- best effort to resolve issues,
+- building and publishing the releases, including writing the release notes and informing the community,
+- in case of inability to perform the above tasks, the Committer in charge has to ask the TSC through the list 
+  [[email protected]](mailto:[email protected]) to find another Committer to review the pull request, 
+  resolve the issue or build and publish the release.
 
-Please refer to our [maintainers file](MAINTAINERS.md) for more details about our work division.
+Please refer to our [commiters file](https://github.com/com-pas/contributing/blob/master/COMMITERS.md) for more details about our work division.
 
 ## Contributors
 
 Contributors include anyone in the technical community that contributes code, documentation, or other technical artifacts to the Project.
 
-Anyone can become a contributor. There is no expectation of commitment to the project, no specific skill requirements and no selection process. To become a contributor, a community member simply has to perform one or more actions that are beneficial to the project.
+Anyone can become a contributor. There is no expectation of commitment to the project, no specific skill requirements and no selection process. 
+To become a contributor, a community member simply has to perform one or more actions that are beneficial to the project.