Create CONTRIBUTING.md
Browse files- CONTRIBUTING.md +46 -0
CONTRIBUTING.md
ADDED
@@ -0,0 +1,46 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
+
# Contributing
|
2 |
+
|
3 |
+
Thank you for considering contributing ! We appreciate your time and effort to help make this project better.
|
4 |
+
|
5 |
+
## Before You Start
|
6 |
+
|
7 |
+
1. **Search for Existing Issues or Discussions:**
|
8 |
+
- Before opening a new issue or discussion, please check if there's already an existing one related to your topic. This helps avoid duplicates and keeps discussions centralized.
|
9 |
+
|
10 |
+
2. **Discuss Your Contribution:**
|
11 |
+
- If you plan to make a significant change, it's advisable to discuss it in an issue first. This ensures that your contribution aligns with the project's goals and avoids duplicated efforts.
|
12 |
+
|
13 |
+
3. **General questions about whisper streaming web:**
|
14 |
+
- For general questions about whisper streaming web, use the discussion space on GitHub. This helps in fostering a collaborative environment and encourages knowledge-sharing.
|
15 |
+
|
16 |
+
## Opening Issues
|
17 |
+
|
18 |
+
If you encounter a problem with diart or want to suggest an improvement, please follow these guidelines when opening an issue:
|
19 |
+
|
20 |
+
- **Bug Reports:**
|
21 |
+
- Clearly describe the error. **Please indicate the parameters you use, especially the model(s)**
|
22 |
+
- Provide a minimal, reproducible example that demonstrates the issue.
|
23 |
+
|
24 |
+
- **Feature Requests:**
|
25 |
+
- Clearly outline the new feature you are proposing.
|
26 |
+
- Explain how it would benefit the project.
|
27 |
+
|
28 |
+
## Opening Pull Requests
|
29 |
+
|
30 |
+
We welcome and appreciate contributions! To ensure a smooth review process, please follow these guidelines when opening a pull request:
|
31 |
+
|
32 |
+
- **Commit Messages:**
|
33 |
+
- Write clear and concise commit messages, explaining the purpose of each change.
|
34 |
+
|
35 |
+
- **Documentation:**
|
36 |
+
- Update documentation when introducing new features or making changes that impact existing functionality.
|
37 |
+
|
38 |
+
- **Tests:**
|
39 |
+
- If applicable, add or update tests to cover your changes.
|
40 |
+
|
41 |
+
- **Discuss Before Major Changes:**
|
42 |
+
- If your PR includes significant changes, discuss it in an issue first.
|
43 |
+
|
44 |
+
## Thank You
|
45 |
+
|
46 |
+
Your contributions make diart better for everyone. Thank you for your time and dedication!
|