Redesign contributing workflow

[norberttech]

Change Log

Added

• Issue Templates

Fixed

Changed

• Contributing guildelines

Removed

Deprecated

Security

---

Nothing here is yet decided, it's the best time to propose changes to the process!

[norberttech]

I made the first batch of changes, which are mostly defining the new contributing workflow.
For a very long time, I was trying to please the contributors even when later I was the one who had to maintain or even finish not fully baked features.
Unfortunately, that approach has become too expensive and time-consuming.

I'm hoping that creating proposals before opening a PR will give both sides (contributors and maintainers) the opportunity to properly set the expectations, which should also speed up the review process.

I'm aware that those changes might deter some devs from contributing or give them the impression that I'm not interested in contributions. Opposite! What I'm trying to build here is a framework that will give more power to the community about what and when is going to be added to this project.

At the end of the day, even if because of that process, the project will lose some potential contributions, it's okay. We need to keep in mind that contributions to the project are meant to serve all users and not only the use case of the contributor.

Opinions and thoughts are more than welcome! 🙏 (Even if you fully disagree with the direction of changes, feel free to let me know - it's ok to have different views and opinions, just stay respectful)