Contributing to QCObjects
The following is a set of guidelines for contributing to QCObjects, which is hosted in the Quickcorp Organization on GitHub. These are mostly guidelines, not rules. Use your best judgment, and feel free to propose changes to this document in a pull request.
Any contribution code, comment, issue and or request must be written in English.
Table Of Contents
- Contributing to QCObjects
- Make Your Own QCObjects based tool or framework
- Become a Sponsor
- Become a Patreon
Code of Conduct
This project and everyone participating in it is governed by the QCObjects Code of Conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior to email@example.com.
Contributing Issues Guidelines
Please, before to create a new issue, read all the old issues here
Please follow the next link and create a Feature Request Issue
#### Bug Report
If you've found a bug, please report it following the template for a Bug Report Issue
Non related issue
If you want to contribute with an non-listed issue you can do it here
Please fork this project and make a link to this project into your README.md file. Read the LICENSE.txt file before you use this code.
Make Your Own QCObjects based tool or framework
You can make YOUR OWN TOOL based on QCObjects. For that you only need to follow the next guidelines:
- To make your tool recognized and listed in the file toolslist.md just send an email to firstname.lastname@example.org indicating the link of the GitHub project and a short description of the purpose of your tool.
- If you are making a QCObjects App Template and you want to be listed in apptemplatelist.md, please send an email to email@example.com indicating the link of the package in npmjs.com. Your App Template will be accepted only if it is using QCObjects as the main framework to render the app and the license of your project is under LGPL-3.
Become a Sponsor
If you want to become a sponsor for this wonderful project you can do it here
If you like this code please DONATE!