When contributing to this repository, please first discuss the change you wish to make via issue or merge-request before making a change.
Please note we have a code of conduct, please follow it in all your interactions } with the project. The mayor rule is non windoser things allowed.
- Fork the project and create a new branch, use a name with feature short description, and edit files in such branch
- Ensure of none of build dependencies, removed any internet dependency before the end of the layer when doing a proposal of modifications or feature.
- Update the README-developers.md with details of changes to the interface, this includes new environment needs; if any.
- You may follow the policyt of zero internet dependency, no CDN neither crap npm/compose technology.
- You must follow the code layer and MVC way of development, we have a lib and api, apart we have a (unfortunatelly) androit app also (the exception of internet things dependency).
- Send your code by create a pull-request/merge-request so we and the comunity can check the proposal, wait for respond tomerge or reject.
IMPORTANT rejection does not means dont collaborate, any interaction is usefully for us.
In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
Two exceptions apply:
- Windosers are not good for this projects, neither M$/privative techs.
- Please mantain religion free the code and project.
- Avoid welcomes, being usefully for rest, no matter level of experience
- Its not about respectful of differing viewpoints, its about inclusion.
- Destructive criticits are accepted but only with a valid solution for our rules.
- Focusing on what is best for the community, not for technologies.
- Respect the tools and tech we used, check docs/README-developers.md
Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
Project maintainers have the right and responsibility to reject only code or commits but never edit or remove comments, issues from others contributiions.
Project maintainers only can reject other code, comments wiki edits from others contributions when are not in conform with the pledge exceptions, but must poinited a viable solution, we do not ban or remove already atributions, but we just silenced those and move to newer forms ..
This means that in any conflict or violation or non compatible contribution, we just reject such and proposed a new one, if some was already contributed we just change in the way is being allowed, contributors are advertised of our pledges and standars.
This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
This project its part of VenenuX projects also.