- Leynier Gutiérrez González (@leynier)
- Norlan Capote Díaz (@norlancd)
- Roberto Marti Cedeño (@rmarticedeno)
- Gabriel A. López López (@glpzzz)
- Leonel A. García López (@stdevlag)
- Carlos Bermudez Porto (@stdevCbermudez)
You can help out by:
- Reporting a bug
- Reviewing the code
- Submitting a fix
- Proposing new features
- Becoming a maintainer
We're using the following branches to manage work:
developis semi-stable and should be used as the branch to fork frommasteris stable and ready for prod (or it will be once we merge in the first release)feature,bugbranches: unstable development
We use GitHub issues to track public bugs. Report a bug by opening a new issue; it's that easy!
Great Bug Reports tend to have:
- A quick summary and/or background
- Steps to reproduce
- Be specific!
- Give sample code if you can.
- What you expected to happen
- What actually happens
- Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)
We <3 thorough bug reports.
We use GitHub to host code, to track issues and feature requests, as well as accept pull requests.
Pull requests are the best way to propose changes to the codebase. We use a loose version of Git Flow and actively welcome your pull requests:
- Set up your local development environment. See USAGE.md for instructions.
- Make sure to use the latest Flutter stable-channel SDK release.
- Create a new branch based on
develop:- Feature branches should start with
feature/ - Bugfix branches should start with
bug/
- Feature branches should start with
- Implement your changes.
- Add tests if applicable.
- Make sure your code lints.
- Issue that pull request!
When you submit code changes, your submissions are understood to be under the same GPL-3.0 that covers the project.