Slick uses the standard Typesafe Project & Developer Guidelines below for contributions. Some Slick-specific clarifications/additions:
- External contributions are generally reviewed by one core developer.
-There are no CI builds for Slick at the moment. Contributions are merged and tested manually.
- We have a [project plan](https://www.assembla.com/spaces/typesafe-slick/tickets) in Assembla tickets plus the standard Github [issue tracker](https://github.com/slick/slick/issues?state=open) for bug reports. We expect to merge these two in the future. For now, when you're referencing a (github) issue or (Assembla) ticket number in a commit, please prefix it with "issue #", or "ticket ", respectively.
-We have Circle CI and Travis CI for continuous integration tests.
- We have the standard Github [issue tracker](https://github.com/slick/slick/issues?state=open) for bug reports. When you're referencing an issue number in a commit, please prefix it with "issue #".
- Branches starting with "tmp/" or "wip/" on the official repo are considered unstable and should not be used as a basis for your work. Their history may be rewritten at any time without notice.
