Skip to content

Commit 049f2b8

Browse files
feat: update readme, add contributing (#35)
* fix: update crawler and fetching time * fix: update time running on gpu * fix: update license * fix: number of days * test: add sampling time * docs: update README.md * fix: update pyproject.toml * docs: add CONTRIBUTING.md
1 parent 27a6fc4 commit 049f2b8

File tree

5 files changed

+350
-67
lines changed

5 files changed

+350
-67
lines changed

CONTRIBUTING.md

Lines changed: 219 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,219 @@
1+
# 🤝 Contributing to QASports
2+
3+
We warmly welcome contributions from the community! Whether you're a researcher, developer, or sports enthusiast, your contributions help make QASports better for everyone.
4+
5+
## 🌟 How You Can Contribute
6+
7+
### 🐛 Report Issues
8+
- Found a bug? Report it on [GitHub Issues](https://github.com/leomaurodesenv/qasports-dataset-scripts/issues)
9+
- Include detailed steps to reproduce the problem
10+
- Share your environment details (Python version, OS, etc.)
11+
12+
### 💡 Suggest Improvements
13+
- Have ideas for new features? We'd love to hear them!
14+
- Propose enhancements to the dataset generation pipeline
15+
- Suggest new sports or data sources to include
16+
- Recommend improvements to documentation or experiments
17+
18+
### 🔧 Fix Issues
19+
- Browse our [open issues](https://github.com/leomaurodesenv/qasports-dataset-scripts/issues)
20+
- Pick an issue that interests you
21+
- Comment on the issue to let us know you're working on it
22+
- Submit a pull request with your fix
23+
24+
### 📚 Improve Documentation
25+
- Help improve our README, code comments, or docstrings
26+
- Add examples or tutorials
27+
- Translate documentation to other languages
28+
- Create guides for specific use cases
29+
30+
### 🧪 Enhance Experiments
31+
- Improve existing experiment frameworks
32+
- Add new evaluation metrics
33+
- Implement new models or approaches
34+
- Create benchmark comparisons
35+
36+
## 🚀 Getting Started
37+
38+
### Prerequisites
39+
- Python 3.9+
40+
- [uv](https://github.com/astral-sh/uv) package manager
41+
- Git
42+
43+
### Setup Development Environment
44+
45+
```bash
46+
# Fork and clone the repository
47+
git clone https://github.com/YOUR_USERNAME/qasports-dataset-scripts.git
48+
cd qasports-dataset-scripts
49+
50+
# Add the original repository as upstream
51+
git remote add upstream https://github.com/leomaurodesenv/qasports-dataset-scripts.git
52+
53+
# Install dependencies
54+
uv sync
55+
56+
# Install development dependencies
57+
uv sync --group dev
58+
59+
# Set up pre-commit hooks
60+
uv run pre-commit install
61+
```
62+
63+
### Development Workflow
64+
65+
```bash
66+
# Create a new branch for your work
67+
git checkout -b feature/your-feature-name
68+
69+
# Make your changes
70+
# ... edit files ...
71+
72+
# Run tests and checks
73+
uv run pre-commit run --all-files
74+
75+
# Commit your changes
76+
git add .
77+
git commit -m "feat: add your feature description"
78+
79+
# Push to your fork
80+
git push origin feature/your-feature-name
81+
```
82+
83+
## 📋 Contribution Guidelines
84+
85+
### Code Style
86+
- Follow [PEP 8](https://pep8.org/) style guidelines
87+
- Use [ruff](https://github.com/astral-sh/ruff) for linting and formatting
88+
- Write clear, descriptive commit messages
89+
- Add type hints where appropriate
90+
91+
### Commit Message Format
92+
We use [Conventional Commits](https://www.conventionalcommits.org/):
93+
94+
```
95+
type(scope): description
96+
97+
[optional body]
98+
99+
[optional footer]
100+
```
101+
102+
Examples:
103+
- `feat: add new sports data source`
104+
- `fix(experiments): resolve pkg_resources import error`
105+
- `docs: improve README installation instructions`
106+
- `test: add unit tests for data processing`
107+
108+
### Pull Request Process
109+
110+
1. **Fork the repository** and create a feature branch
111+
2. **Make your changes** following the code style guidelines
112+
3. **Test your changes** thoroughly
113+
4. **Update documentation** if needed
114+
5. **Submit a pull request** with a clear description
115+
116+
### Pull Request Template
117+
118+
```markdown
119+
## Description
120+
Brief description of what this PR does.
121+
122+
## Type of Change
123+
- [ ] Bug fix
124+
- [ ] New feature
125+
- [ ] Documentation update
126+
- [ ] Performance improvement
127+
- [ ] Refactoring
128+
129+
## Testing
130+
- [ ] I have tested my changes locally
131+
- [ ] I have added/updated tests
132+
- [ ] All tests pass
133+
134+
## Checklist
135+
- [ ] My code follows the style guidelines
136+
- [ ] I have updated documentation as needed
137+
- [ ] My changes generate no new warnings
138+
- [ ] I have added comments to my code where necessary
139+
```
140+
141+
## 🎯 Areas for Contribution
142+
143+
### High Priority
144+
- **Bug fixes** in the dataset generation pipeline
145+
- **Performance improvements** for large-scale processing
146+
- **Documentation enhancements** and tutorials
147+
- **Test coverage** improvements
148+
149+
### Medium Priority
150+
- **New sports data sources** (tennis, baseball, hockey, etc.)
151+
- **Enhanced experiment frameworks** with new models
152+
- **Data quality improvements** and validation
153+
- **Multi-language support** for questions and answers
154+
155+
### Low Priority
156+
- **UI/UX improvements** for experiment interfaces
157+
- **Additional export formats** for the dataset
158+
- **Integration examples** with popular ML frameworks
159+
- **Community tutorials** and use cases
160+
161+
## 🏷️ Issue Labels
162+
163+
We use labels to categorize issues:
164+
165+
- `good first issue` - Perfect for newcomers
166+
- `bug` - Something isn't working
167+
- `enhancement` - New feature or request
168+
- `documentation` - Improvements to docs
169+
- `help wanted` - Extra attention needed
170+
- `question` - Further information is requested
171+
172+
## 🤝 Community Guidelines
173+
174+
### Be Respectful
175+
- Treat all contributors with respect and kindness
176+
- Be patient with newcomers
177+
- Provide constructive feedback
178+
- Celebrate others' contributions
179+
180+
### Be Helpful
181+
- Answer questions when you can
182+
- Share your knowledge and experience
183+
- Help review pull requests
184+
- Welcome new contributors
185+
186+
### Be Professional
187+
- Keep discussions focused and on-topic
188+
- Use clear, professional language
189+
- Follow the project's code of conduct
190+
- Respect maintainers' decisions
191+
192+
## 📞 Getting Help
193+
194+
### Questions?
195+
- Check our [documentation](README.md)
196+
- Search [existing issues](https://github.com/leomaurodesenv/qasports-dataset-scripts/issues)
197+
- Ask in [GitHub Discussions](https://github.com/leomaurodesenv/qasports-dataset-scripts/discussions)
198+
199+
### Stuck?
200+
- Don't hesitate to ask for help!
201+
- We're here to support you
202+
- No question is too small
203+
204+
## 🎉 Recognition
205+
206+
Contributors will be:
207+
- Mentioned in release notes
208+
- Acknowledged in research papers when appropriate
209+
- Featured in our community highlights
210+
211+
## 📄 License
212+
213+
By contributing to QASports, you agree that your contributions will be licensed under the same [MIT License](LICENSE) that covers the project.
214+
215+
---
216+
217+
**Thank you for contributing to QASports!** 🏆
218+
219+
Your contributions help advance sports analytics and question answering research. Together, we're building the future of sports data science.

LICENSE

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
MIT License
22

3-
Copyright (c) 2024 Leonardo Mauro <leomaurodesenv>, Pedro Jardim <Pedro-C-Jardim>
3+
Copyright (c) 2025 Leonardo Mauro <leomaurodesenv>, Pedro Jardim <Pedro-C-Jardim>
44

55
Permission is hereby granted, free of charge, to any person obtaining a copy
66
of this software and associated documentation files (the "Software"), to deal

0 commit comments

Comments
 (0)