Skip to content

Commit f9bafbe

Browse files
committed
see how to contribute
1 parent fa6a5d6 commit f9bafbe

File tree

1 file changed

+127
-0
lines changed

1 file changed

+127
-0
lines changed

contributing.md

Lines changed: 127 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,127 @@
1+
# Contributing to Deep Learning with PyTorch Tutorials
2+
3+
First off, thank you for considering contributing to our PyTorch tutorials! 🎉 It's people like you that make this resource valuable for the community. We welcome contributions from everyone, whether you're fixing a typo, suggesting improvements, or adding entirely new content.
4+
5+
## 💡 Ways to Contribute
6+
7+
There are many ways you can help improve these tutorials:
8+
9+
- **Found a typo or error?** Submit a quick fix!
10+
- **Have suggestions for clearer explanations?** We'd love to hear them!
11+
- **Want to improve code examples?** Great! More efficient or clearer examples help everyone.
12+
- **Interested in adding new visualizations?** Visual explanations can make complex concepts easier to understand.
13+
- **Have ideas for new topics?** Let us know what you'd like to see added.
14+
15+
Every contribution, no matter how small, helps make these tutorials better!
16+
17+
## 🚀 Getting Started
18+
19+
### 1. Set Up Your Environment
20+
21+
If you haven't already, set up your local environment:
22+
23+
```bash
24+
# Clone the repository
25+
git clone https://github.com/anand-me/deep-learning-with-pytorch-tutorials.git
26+
cd deep-learning-with-pytorch-tutorials
27+
28+
# Create a virtual environment
29+
python -m venv venv
30+
source venv/bin/activate # On Windows: venv\Scripts\activate
31+
32+
# Install dependencies
33+
pip install -r requirements.txt
34+
```
35+
36+
### 2. Create a Branch
37+
38+
Create a branch for your changes:
39+
40+
```bash
41+
git checkout -b your-branch-name
42+
```
43+
44+
Use a descriptive name for your branch that reflects the changes you're making, such as `fix-tensor-example` or `add-transformer-tutorial`.
45+
46+
### 3. Make Your Changes
47+
48+
Now you can make your changes to the notebooks or documentation files. Some tips:
49+
50+
- Keep code examples simple and focused
51+
- Add comments to explain complex operations
52+
- Test all code to ensure it runs without errors
53+
- Follow the existing style for consistency
54+
55+
### 4. Submit a Pull Request
56+
57+
Once you're happy with your changes:
58+
59+
1. Push your branch to GitHub:
60+
```bash
61+
git add .
62+
git commit -m "Brief description of your changes"
63+
git push origin your-branch-name
64+
```
65+
66+
2. Go to the repository on GitHub and click "Pull Request"
67+
68+
3. Provide a clear description of what your changes do and why they're valuable
69+
70+
## 📝 Contribution Guidelines
71+
72+
To ensure a smooth collaboration experience, please follow these guidelines:
73+
74+
### For Notebooks
75+
76+
- Keep cells organized and logical
77+
- Include markdown explanations before code cells
78+
- Avoid extremely long outputs
79+
- Make sure all dependencies are listed in requirements.txt
80+
- Add appropriate visualizations where helpful
81+
82+
### For Documentation
83+
84+
- Use clear, accessible language
85+
- Include examples where appropriate
86+
- Keep explanations concise but complete
87+
- Follow markdown formatting conventions
88+
89+
### Code Style
90+
91+
- Follow PEP 8 guidelines for Python code
92+
- Use descriptive variable names
93+
- Include docstrings for functions
94+
- Keep code simple and readable
95+
96+
## 👥 Community Guidelines
97+
98+
We're committed to providing a welcoming and inclusive environment. When interacting with this project and its community, please:
99+
100+
- Be respectful and kind to others
101+
- Be open to different viewpoints and experiences
102+
- Focus on what is best for the community
103+
- Give and gracefully accept constructive feedback
104+
105+
## ❓ Questions?
106+
107+
Not sure about something? Have questions about how to implement your contribution? No problem! You can:
108+
109+
- Open an issue with your question
110+
- Reach out to project maintainers
111+
- Comment on existing issues related to your question
112+
113+
We're here to help you make your contribution successful!
114+
115+
## 🎓 New to Open Source?
116+
117+
If this is your first open source contribution, welcome! Here are some resources to help you get started:
118+
119+
- [How to Contribute to Open Source](https://opensource.guide/how-to-contribute/)
120+
- [GitHub Flow Guide](https://guides.github.com/introduction/flow/)
121+
- [First Contributions Tutorial](https://github.com/firstcontributions/first-contributions)
122+
123+
Remember, every expert was once a beginner. We're happy to help you through your first contribution!
124+
125+
---
126+
127+
Thank you for helping make this project better! 💖

0 commit comments

Comments
 (0)