Update Contribution file

Author: Aeliux

CONTRIBUTING.md

@@ -1,34 +1,107 @@
-# Contributing to this project
+# Contributing to EasySign Project
 
-This project has adopted the code of conduct defined by the Contributor Covenant to clarify expected behavior in our community.
-For more information see the [.NET Foundation Code of Conduct](https://dotnetfoundation.org/code-of-conduct).
+Thank you for considering contributing to EasySign! We welcome contributions from the community and are excited to work with you. This guide will help you get started with contributing to the project.
 
-## Prerequisites
+## Table of Contents
 
-This project is actively developed using the following software.
-It is highly recommended that anyone contributing to this library use the same
-software.
+- [Code of Conduct](#code-of-conduct)
+- [How to Contribute](#how-to-contribute)
+  - [Reporting Bugs](#reporting-bugs)
+  - [Suggesting Features](#suggesting-features)
+  - [Submitting Pull Requests](#submitting-pull-requests)
+- [Development Setup](#development-setup)
+- [Style Guide](#style-guide)
+- [License](#license)
 
-1. [Visual Studio 2022][VS]
+## Code of Conduct
 
-## Building
+Please read and follow our [Code of Conduct](CODE-OF-CONDUCT.md) to ensure a welcoming and inclusive environment for everyone.
 
-To build this repository from the command line, you could run this command in the root of the repo:
+## How to Contribute
 
-    dotnet build
+### Reporting Bugs
 
-## Testing
+If you find a bug in the project, please create an issue on GitHub with the following information:
+- A clear and descriptive title.
+- A detailed description of the problem.
+- Steps to reproduce the issue.
+- Any relevant logs, screenshots, or error messages.
 
-The Visual Studio 2022 Test Explorer will list and execute all tests.
+If the bug is related to security, **DO NOT REPORT IT ON GITHUB ISSUES**, please read our [Security Guidelines](SECURITY.md).
 
-## Pull requests
+### Suggesting Features
 
-Pull requests are welcome! They may contain additional test cases (e.g. to demonstrate a failure),
-and/or product changes (with bug fixes or features). All product changes should be accompanied by
-additional tests to cover and justify the product change unless the product change is strictly an
-efficiency improvement and no outwardly observable change is expected.
+We welcome feature suggestions! To suggest a new feature, please create an issue on GitHub with the following information:
+- A clear and descriptive title.
+- A detailed description of the proposed feature.
+- Any relevant use cases or examples.
 
-In the master branch, all tests should always pass. Added tests that fail should be marked as Skip
-via `[Fact(Skip = "Test does not pass yet")]` or similar message to keep our test pass rate at 100%.
+### Submitting Pull Requests
 
- [VS]: https://www.visualstudio.com/downloads/
+We appreciate your contributions! To submit a pull request, follow these steps:
+1. Fork the repository and clone your fork.
+2. Create a new branch for your changes.
+3. Make your changes, ensuring that your code adheres to the project's style guide.
+4. Commit your changes with a clear and descriptive commit message.
+5. Push your changes to your fork.
+6. Create a pull request on GitHub, providing a detailed description of your changes.
+
+## Development Setup
+
+To set up your development environment, follow these steps:
+1. Ensure you have [.NET SDK](https://dotnet.microsoft.com/download) installed. You must have .NET SDK 6, 8 and 9 installed.
+2. Clone the repository:
+   
+```
+   git clone https://github.com/SAPTeamDEV/EasySign.git
+   cd EasySign
+   
+```
+
+3. Restore the project dependencies:
+   
+```
+   dotnet restore
+   
+```
+
+4. Build the project:
+   
+```
+   dotnet build
+   
+```
+
+You could find output files in artifacts folder.
+
+## Native AOT Compilation
+
+After setting up the development environment, you can compile the EasySign CLI using Native AOT. This is useful for creating fast applications that do not require a separate .NET runtime installation.
+
+To compile the CLI using Native AOT, follow these steps:
+1. Ensure you have the AOT compilation [requirements](https://learn.microsoft.com/en-us/dotnet/core/deploying/native-aot/#prerequisites) for your platform.
+2. Compile EasySign.Cli with the following command:
+
+Windows
+```
+dotnet publish src\EasySign.Cli\EasySign.Cli.csproj /p:AotCompile=true -f net9.0 -o artifacts\AOT
+```
+
+Linux/MacOS
+```
+dotnet publish src/EasySign.Cli/EasySign.Cli.csproj /p:AotCompile=true -f net9.0 -o artifacts/AOT
+```
+
+## Style Guide
+
+Please follow these guidelines to ensure consistency in the codebase:
+- Use [C# coding conventions](https://docs.microsoft.com/en-us/dotnet/csharp/fundamentals/coding-style/coding-conventions).
+- Write clear and descriptive commit messages.
+- Ensure your code is well-documented with XML comments where appropriate.
+- Run tests before submitting your pull request to ensure your changes do not break existing functionality.
+
+## License
+
+By contributing to EasySign, you agree that your contributions will be licensed under the [MIT License](LICENSE.md).
+
+Thank you for your contributions!

SECURITY.md

@@ -1,4 +1,4 @@
-# Security
+# Security Vulnerability Reportiing Guideline
 
 The maintainers of this project take security seriously, and the reporting of potential security issues. If you believe you have found a security vulnerability in code from this repository that meets [Microsoft's definition of a security vulnerability](https://docs.microsoft.com/previous-versions/tn-archive/cc751383(v=technet.10)), please report it to us as described below.
 

build/DoxyHome.md

@@ -121,7 +121,7 @@ esign verify /path/to/dir
 
 ## Security Vulnerability Reporting
 
-If you discover any security vulnerabilities, please report them by following our guidelines [Security Guidelines](SECURITY.md).
+If you discover any security vulnerabilities, please report them by following our [Security Guidelines](SECURITY.md).
 
 ## Contributing