Add contributing guidelines

Author: ogxd

CONTRIBUTING.md

@@ -0,0 +1,34 @@
+# Contributing Guidelines
+
+Thank you for considering contributing to this project! To help maintain a healthy and productive environment, please follow these basic guidelines.
+
+## Creating Issues
+
+Here are the minimum requirements for creating a issue on this project.  
+**Any issue with a too vague description or inappropriate language may be closed without notice**: it often takes orders of magnitude more time to answer theses than the time it took for the author to write them.
+
+### 1. Clear and Descriptive Title
+The title should give a quick understanding of what the issue is about.
+
+Examples:
+- ✅ "TypeError when processing empty strings"
+- ✅ "Documentation unclear about parameter X usage"
+- ❌ "It doesn't work"
+- ❌ "Bad implementation"
+
+### 2. Meaningful Description
+Your description should help others understand your issue. While the format is flexible, please make sure to convey:
+- What you're trying to do
+- What's not working as expected
+- Any relevant context that could help understand the situation
+
+The key is being clear and providing enough information so others can understand and help you.
+
+### 3. Respectful Communication
+Remember that open source maintainers are volunteers working on this project in their free time. Please:
+- Be respectful and constructive (there is no "it should be like this", or "this is bad"...)
+- Understand that the project spirit may not align with your expectations
+
+## Submitting a Pull Request
+
+Pull requests are welcome! Make sure to properly explain the changes you're proposing in an issue, especially for significant changes.

README.md

@@ -3,6 +3,7 @@
 Equativ.RoaringBitmaps is a pure C# implementation of [RoaringBitmap](http://roaringbitmap.org).
 - ✨ **Fully managed code!** No risk of segfaults or memory leaks due to missed disposals.
 - 🚀 **Blazingly fast!** See [benchmarks](#performance).
+-  **Portable**: It works everywhere where .NET is supported.
 
 ## Usage
 
@@ -36,9 +37,11 @@ Charts are generated using [chartbenchmark.net](https://chartbenchmark.net/).
 ![Performance](Resources/bench_m1.png)  
 (lower is better)
 
+## F.A.Q.
+
 ### How can this be faster than the C implementation?
 
-Several reasons can explain why this benchmark numbers are sometimes in favor of this implementation:
+There can be a few reasons:
+- Modern C# performs really well for this kind of workloads, it shall not be underestimated.
 - [Roaring.Net](https://github.com/k-wojcik/Roaring.Net) is wrapper, which means that there is a marshalling cost between C# and C.
-- This implementation has a few optimizations that are not present in the C implementation.
-- Modern C# is perform really well for this kind of workloads.
+- This implementation has a few optimizations that are not present in the C implementation, especially for ARM CPUs.