homer/CONTRIBUTING.md

# Introduction

### Welcome!

First off, thank you for considering contributing to Homer!

### Project philosophy

Homer is meant to be a light and very simple dashboard that keeps all your useful utilities at hands. The few features implemented in Homer focus on
UX and usability. If you are looking for a full featured dashboard, there is tons of great stuff out there like https://heimdall.site/, https://github.com/rmountjoy92/DashMachine or https://organizr.app/.

- Configuration is stored in a simple config file, avoiding the need for a backend/database while making possible to use versioning or [config template](https://docs.ansible.com/ansible/latest/user_guide/playbooks_templating.html).
- Only modern browsers are supported, feel free to use any JS features without any polyfill as soon as the latest version of the major browsers supports them.


# Ground Rules

### Code of conduct and guidelines

First of all, we expect everyone (contributors and maintainers alike) to respect the [Code of conduct](https://github.com/bastienwirtz/homer/blob/main/CODE_OF_CONDUCT.md). It is not a recommendation, it is mandatory.

For all contributions, please respect the following guidelines:

* Each pull request should implement ONE feature or bugfix. If you want to add or fix more than one thing, submit more than one pull request.
* Do not commit changes to files that are irrelevant to your feature or bugfix (e.g. `.gitignore`).
* Do not add unnecessary dependencies.
* Be aware that the pull request review process is not immediate, and is generally proportional to the size of the pull request.

# Getting started

### Discuss about ideas

If you want to add a feature, it's often best to talk about it before starting to work on it and submitting a pull request. It's not mandatory at all, but
feel free to open an issue to present your idea.

### How to submit a contribution

The general process to submit a contribution is as follow:
1. Take a look to the [development guideline](https://github.com/bastienwirtz/homer/blob/main/docs/development.md).
2. Create your own fork of the code
3. Do the changes in your fork
4. Make sure to fill the [pull request description](https://github.com/bastienwirtz/homer/blob/main/.github/PULL_REQUEST_TEMPLATE.md) properly.

### Happy coding :metal:
Adding contribution guidelines 2020-03-22 23:51:54 +01:00			`# Introduction`

			`### Welcome!`

			`First off, thank you for considering contributing to Homer!`

			`### Project philosophy`

chore: applies spell-check against entire repo (aspell) 2020-10-26 05:12:37 +01:00			`Homer is meant to be a light and very simple dashboard that keeps all your useful utilities at hands. The few features implemented in Homer focus on`
Adding contribution guidelines 2020-03-22 23:51:54 +01:00			`UX and usability. If you are looking for a full featured dashboard, there is tons of great stuff out there like https://heimdall.site/, https://github.com/rmountjoy92/DashMachine or https://organizr.app/.`

chore: applies spell-check against entire repo (aspell) 2020-10-26 05:12:37 +01:00			`- Configuration is stored in a simple config file, avoiding the need for a backend/database while making possible to use versioning or [config template](https://docs.ansible.com/ansible/latest/user_guide/playbooks_templating.html).`
Adding contribution guidelines 2020-03-22 23:51:54 +01:00			`- Only modern browsers are supported, feel free to use any JS features without any polyfill as soon as the latest version of the major browsers supports them.`


			`# Ground Rules`

			`### Code of conduct and guidelines`

Fix documentation link. 2020-12-08 07:57:44 +01:00			`First of all, we expect everyone (contributors and maintainers alike) to respect the [Code of conduct](https://github.com/bastienwirtz/homer/blob/main/CODE_OF_CONDUCT.md). It is not a recommendation, it is mandatory.`
Adding contribution guidelines 2020-03-22 23:51:54 +01:00
			`For all contributions, please respect the following guidelines:`

			`* Each pull request should implement ONE feature or bugfix. If you want to add or fix more than one thing, submit more than one pull request.`
Minor edits on readme and documentation 2020-11-14 13:25:01 +01:00			* Do not commit changes to files that are irrelevant to your feature or bugfix (e.g. `.gitignore`).
Adding contribution guidelines 2020-03-22 23:51:54 +01:00			`* Do not add unnecessary dependencies.`
			`* Be aware that the pull request review process is not immediate, and is generally proportional to the size of the pull request.`

			`# Getting started`

			`### Discuss about ideas`

Minor edits on readme and documentation 2020-11-14 13:25:01 +01:00			`If you want to add a feature, it's often best to talk about it before starting to work on it and submitting a pull request. It's not mandatory at all, but`
Adding contribution guidelines 2020-03-22 23:51:54 +01:00			`feel free to open an issue to present your idea.`

			`### How to submit a contribution`

			`The general process to submit a contribution is as follow:`
Extendable base service for easier development. 2021-10-06 22:55:09 +02:00			`1. Take a look to the [development guideline](https://github.com/bastienwirtz/homer/blob/main/docs/development.md).`
			`2. Create your own fork of the code`
			`3. Do the changes in your fork`
			`4. Make sure to fill the [pull request description](https://github.com/bastienwirtz/homer/blob/main/.github/PULL_REQUEST_TEMPLATE.md) properly.`
Adding contribution guidelines 2020-03-22 23:51:54 +01:00
			`### Happy coding :metal:`