First off, thank you for considering contributing to Adobe CCF Policy Generator! It's people like you that make this tool better for everyone.
By participating in this project, you are expected to uphold our Code of Conduct. Please report unacceptable behavior to [project maintainers].
Before creating bug reports, please check the existing issues list as you might find that you don't need to create one. When you create a bug report, please include as many details as possible:
- Use a clear and descriptive title
- Describe the exact steps to reproduce the problem
- Provide specific examples to demonstrate the steps
- Describe the behavior you observed
- Explain the behavior you expected
- Include screenshots or logs if possible
Enhancement suggestions are tracked as GitHub issues. When creating an enhancement suggestion, please include:
- Use a clear and descriptive title
- Provide a detailed description of the suggested enhancement
- Explain why this enhancement would be useful
- List some examples of how it would be used
- Fork the repo and create your branch from
main
- If you've added code that should be tested, add tests
- If you've changed APIs, update the documentation
- Ensure the test suite passes
- Make sure your code follows the existing style
- Issue the pull request!
- Clone the repository:
git clone https://github.com/markac007/adobe-ccf-policy-generator.git
cd adobe-ccf-policy-generator
- Install dependencies:
cd backend
pip install -r requirements.txt
- Run tests:
python -m pytest
- Use the present tense ("Add feature" not "Added feature")
- Use the imperative mood ("Move cursor to..." not "Moves cursor to...")
- Limit the first line to 72 characters or less
- Reference issues and pull requests liberally after the first line
- Follow PEP 8
- Use meaningful variable names
- Include docstrings for functions and classes
- Add comments for complex logic
- Use Markdown for documentation
- Include code examples when relevant
- Keep language clear and concise
- Update README.md if needed
When contributing, please maintain the existing project structure:
backend/
├── src/ # Source code
├── scripts/ # Scripts and entry points
├── templates/ # Template files
├── data/ # Data files
│ ├── processed/ # Processed JSON data
│ └── raw/ # Raw CSV data
└── tests/ # Test files
- Write tests for new features
- Update tests when modifying existing features
- Ensure all tests pass before submitting PR
- Include both unit tests and integration tests when applicable
# Run all tests
python -m pytest
# Run specific test file
python -m pytest tests/test_specific.py
# Run with coverage
python -m pytest --cov=src
bug
- Confirmed bugs or reports likely to be bugsenhancement
- New feature or requestdocumentation
- Documentation only changeshelp-wanted
- Extra attention is neededgood-first-issue
- Good for newcomers
Contributors will be recognized in the following ways:
- Listed in CONTRIBUTORS.md
- Mentioned in release notes for significant contributions
- Added to GitHub contributors list
Don't hesitate to ask questions about contributing. You can:
- Open an issue with your question
- Contact the maintainers directly
- Join our community discussions
Thank you for contributing to Adobe CCF Policy Generator!