"Fossies" - the Fresh Open Source Software Archive  

Source code changes of the file "CONTRIBUTING.md" between
ISPConfig-3.2.4.tar.gz and ISPConfig-3.2.5.tar.gz

About: ISPConfig is an ISP management and Hosting Control Panel (for different Managed Services).

CONTRIBUTING.md  (ISPConfig-3.2.4):CONTRIBUTING.md  (ISPConfig-3.2.5)
skipping to change at line 12 skipping to change at line 12
ISPConfig is a open source project and community contributions are very welcome. To contribute, please stick to the guidelines. ISPConfig is a open source project and community contributions are very welcome. To contribute, please stick to the guidelines.
This document is under development and will be continuously improved. This document is under development and will be continuously improved.
# Issues # Issues
* Before opening a new issue, use the search function to check if there isn't a bug report / feature request already. * Before opening a new issue, use the search function to check if there isn't a bug report / feature request already.
* If you are reporting a bug, please share your OS and PHP (CLI) version. * If you are reporting a bug, please share your OS and PHP (CLI) version.
* If you want to report several bugs or request several features, open a separat e issue for each one of them. * If you want to report several bugs or request several features, open a separat e issue for each one of them.
# Branches # Branches
* If you are a new user, please send an email to: dev [at] ispconfig [dot] org t o receive rights to fork the project.
* Please create an issue for each contribution you want to make. * Please create an issue for each contribution you want to make.
* Do not put multiple contributions into a single branch and merge request. Each contribution should have it's own branch. * Do not put multiple contributions into a single branch and merge request. Each contribution should have it's own branch.
* Do not use the develop branch in your forked project for your contribution. Cr eate a separate branch for each issue. * Do not use the develop branch in your forked project for your contribution. Cr eate a separate branch for each issue.
* Give your branch a name, e. g. `6049-update-the-contributing-doc ` where 6049 is the issue number. * Give your branch a name, e. g. `6049-update-the-contributing-doc ` where 6049 is the issue number.
# Merge requests # Merge requests
Please give your merge request a description that shortly states what it is abou t. Merge requests without a good title or with missing description will get dela yed because it is more effort for us to check the meaning of the changes made. Please give your merge request a description that shortly states what it is abou t. Merge requests without a good title or with missing description will get dela yed because it is more effort for us to check the meaning of the changes made.
Once again: Do not put multiple things into a single merge request. If you for e xample fix two issues where one affects apache and one mail users, use separate issues and separate merge requests. Once again: Do not put multiple things into a single merge request. If you for e xample fix two issues where one affects apache and one mail users, use separate issues and separate merge requests.
You can group multiple issues in a single merge request if they have the same sp ecific topic, e. g. if you have one issue stating that a language entry in mail users is missing and a second issue that a language entry for server config is m issing, you can put both issues into a single branch and merge request. Be sure to include all issue ids (if multiple) into the merge request's description in t his case. You can group multiple issues in a single merge request if they have the same sp ecific topic, e. g. if you have one issue stating that a language entry in mail users is missing and a second issue that a language entry for server config is m issing, you can put both issues into a single branch and merge request. Be sure to include all issue ids (if multiple) into the merge request's description in t his case.
* Open a issue for the bug you want to fix / the feature you want to implement * Open a issue for the bug you want to fix / the feature you want to implement
 End of changes. 1 change blocks. 
0 lines changed or deleted 1 lines changed or added

Home  |  About  |  Features  |  All  |  Newest  |  Dox  |  Diffs  |  RSS Feeds  |  Screenshots  |  Comments  |  Imprint  |  Privacy  |  HTTP(S)