Update CONTRIBUTING.adoc

[Ayko1595]

Contact Details

Konstantin.ay@intunio.se

What benefits does the suggestion solve?

This would make it more clear to future developers how they could contribute in a way that adheres to guidelines set by this project.

Feature suggestion description

The contributing doc should be updated with the following:

• [ ] Accessibility guidelines (WCAG 2.0)
• [x] UX guidelines
• [x] Testing guidelines
• [x] License guidelines
• [x] Branch names
• [x] Commit message structure: #{issue number}: {Commit message} (e.g. #1: This is a commit message)
• [x] Branch deletion when PR is merged
• [x] Test on all clients: Web, MacOS and PC
• [x] Add relevant documentation, if needed
• [x] Licenses for images, videos etc
• [x] Guidelines related to meeting link generation (should not be too easy or too hard?)

Additionally, we should also add a more detailed description of this project's vision and enforce adherence to that vision whenever someone makes a PR.

Alternative solutions

No response

Additional information

No response

[Ayko1595]

We should also add some sort of vision to the README:

The purpose of this plug-in is to simplify the process of adding video conference links to meeting bookings. It is designed for users who value and require simplicity to complete their tasks quickly and intuitively. Therefore, it is important to preserve this simplicity as new features are added. Any additional contributions to the software must be designed in a way that does not interfere with or complicate the core functionality of booking a regular meeting with just one click.