-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathcontributing.html
52 lines (39 loc) · 3.19 KB
/
contributing.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
<!DOCTYPE html>
<!--[if lt IE 7]> <html class="no-js lt-ie9 lt-ie8 lt-ie7"> <![endif]-->
<!--[if IE 7]> <html class="no-js lt-ie9 lt-ie8"> <![endif]-->
<!--[if IE 8]> <html class="no-js lt-ie9"> <![endif]-->
<!--[if gt IE 8]><!--> <html class="no-js"> <!--<![endif]-->
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
<title>Contributing To Laravel</title>
<link rel="stylesheet" href="css/style.css">
<link rel="stylesheet" href="css/ubuntu-font.css">
<script src="vendor/modernizr-2.6.2.min.js"></script>
<script type="text/javascript" src="vendor/google-code-prettify/prettify.js"></script>
</head><body><section class="docs-content"><div class="container">
<article class="docs-body"><h1>Contributing To Laravel</h1>
<p><a name="introduction"></a></p>
<h2>Introduction</h2>
<p>Laravel is free, open-source software, meaning anyone can contribute to its development and progress. Laravel source code is currently hosted on <a href="http://github.com">Github</a>, which provides an easy method for forking the project and merging your contributions.</p>
<p><a name="pull-requests"></a></p>
<h2>Pull Requests</h2>
<p>The pull request process differs for new features and bugs. Before sending a pull request for a new feature, you should first create an issue with <code>[Proposal]</code> in the title. The proposal should describe the new feature, as well as implementation ideas. The proposal will then be reviewed and either approved or denied. Once a proposal is approved, a pull request may be created implementing the new feature. Pull requests which do not follow this guideline will be closed immediately.</p>
<p>Pull requests for bugs may be sent without creating any proposal issue. If you believe that you know of a solution for a bug that has been filed on Github, please leave a comment detailing your proposed fix.</p>
<h3>Feature Requests</h3>
<p>If you have an idea for a new feature you would like to see added to Laravel, you may create an issue on Github with <code>[Request]</code> in the title. The feature request will then be reviewed by a core contributor.</p>
<p><a name="coding-guidelines"></a></p>
<h2>Coding Guidelines</h2>
<p>Laravel follows the <a href="https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-0.md">PSR-0</a> and <a href="https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-1-basic-coding-standard.md">PSR-1</a> coding standards. In addition to these standards, below is a list of other coding standards that should be followed:</p>
<ul>
<li>Namespace declarations should be on the same line as <code><?php</code>.</li>
<li>Class opening <code>{</code> should be on the same line as the class name.</li>
<li>Function and control structure opening <code>{</code> should be on a separate line.</li>
<li>Interface names are suffixed with <code>Interface</code> (<code>FooInterface</code>)</li>
</ul></article><div class="clearfix"></div>
</div>
</section>
<script src="js/jquery.min.js"></script>
<script src="js/plugins.js"></script>
<script type="text/javascript" src="vendor/google-code-prettify/run_prettify.js"></script>
</body></html>