34 lines
1.2 KiB
Markdown
34 lines
1.2 KiB
Markdown
|
Contributing to Jocly
|
||
|
|
=====================
|
||
|
|
|
||
|
|
Contribute source code
|
||
|
|
----------------------
|
||
|
|
|
||
|
|
You are very welcome to contribute source code with bug fixes, improvements and new
|
||
|
|
features.
|
||
|
|
|
||
|
|
Contributions must be done as Pull Requests (PR) to the Jocly repository on github:
|
||
|
|
[https://github.com/mi-g/jocly](https://github.com/mi-g/jocly).
|
||
|
|
|
||
|
|
Prior to working on Jocly source code, it is a good idea to tell us about it
|
||
|
|
on the [Jocly Community Group](https://groups.google.com/forum/#!forum/jocly-community).
|
||
|
|
It may save you time and energy getting the right advice upfront.
|
||
|
|
|
||
|
|
By submitting a PR to the Jocly repository, you acknowledge that:
|
||
|
|
- the submitted code is under AGPL v3
|
||
|
|
- you give us, Jocly, the right to sub-license the submitted code under the current
|
||
|
|
Jocly AGPL/Proprietary dual-licensing model
|
||
|
|
|
||
|
|
Reporting issues
|
||
|
|
----------------
|
||
|
|
|
||
|
|
If you discover issues with features covered by Jocly, you are very welcome to file
|
||
|
|
an issue in the [github repository](https://github.com/mi-g/jocly/issues/new).
|
||
|
|
|
||
|
|
Using Jocly in your project
|
||
|
|
---------------------------
|
||
|
|
|
||
|
|
If you use Jocly in your project, Web site or else, let us know in the
|
||
|
|
[Jocly Community Group](https://groups.google.com/forum/#!forum/jocly-community) so
|
||
|
|
we can ~~brag~~ talk about it.
|