How to Contribute
WakaPAC is actively developed and maintained by one person — contributions are genuinely appreciated, not just tolerated. Every PR gets a personal review within 1-2 days.
Quick Start
# Fork https://github.com/quellabs/wakapac on GitHub
git clone https://github.com/YOUR-USERNAME/wakapac.git
cd wakapac
git remote add upstream https://github.com/quellabs/wakapac.git
Contribution Workflow
# Create a feature branch
git checkout -b feature/your-feature-name
# Make changes and update docs
# Lint the code
eslint ./wakapac.js
# Commit and push
git add .
git commit -m "feat: your feature description"
git push origin feature/your-feature-name
# Open a PR at https://github.com/quellabs/wakapac/pulls
Not sure whether your idea fits? Open a GitHub Discussion first. A quick conversation saves everyone time.
Code Style
WakaPAC follows these conventions: tabs (not spaces), opening braces on the same line, PascalCase for classes, camelCase for methods and properties, UPPER_SNAKE_CASE for constants. Include JSDoc blocks for all classes and public methods.
Reporting Issues
Report bugs at github.com/quellabs/wakapac/issues
Helpful to include: expected vs actual behaviour, steps to reproduce, WakaPAC version, browser/runtime environment, and any error output. The more specific, the faster it gets fixed.
Code Review
You'll get feedback within 1-2 days. If something needs changing, push new commits to the same branch and the PR updates automatically — no need to close and reopen. When you're happy with the changes, leave a comment and I'll re-review.
Versioning
WakaPAC follows Semantic Versioning. Breaking changes are MAJOR, new backwards-compatible features are MINOR, bug fixes are PATCH. The main branch is always stable.