-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathindex.html
146 lines (136 loc) · 7.62 KB
/
index.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
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
<!DOCTYPE html>
<html>
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta name="description" content="">
<title>Laravel Frontend Presets </title>
<script src="https://code.jquery.com/jquery-2.2.4.min.js" integrity="sha256-BbhdlvQf/xTY9gja0Dq3HiwQF8LaCRTXxZKRutelT44=" crossorigin="anonymous"></script>
<script src="https://cdnjs.cloudflare.com/ajax/libs/markdown-it/7.0.0/markdown-it.min.js" ></script>
<link href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap.min.css" rel="stylesheet" integrity="sha384-BVYiiSIFeK1dGmJRAkycuHAHRg32OmUcww7on3RYdg4Va+PmSTsz/K68vbdEjh4u" crossorigin="anonymous">
<link href='https://maxcdn.bootstrapcdn.com/font-awesome/4.6.3/css/font-awesome.min.css' rel='stylesheet' type='text/css'>
<link href='https://fonts.googleapis.com/css?family=Open+Sans:400,600,700' rel='stylesheet' type='text/css'>
<link rel="stylesheet" href="/assets/prism.css">
<link rel="stylesheet" href="/assets/css/all.css">
</head>
<body>
<div class="wow">
<img src="/assets/logo.png"
alt="Laravel Frontend Presets">
<h1>Laravel Frontend Presets</h1>
<h2>A collection of custom presets for Laravel 5.5</h2>
<a href="https://github.com/laravel-frontend-presets">
GitHub
</a>
<i>  .  </i>
<a href="https://packagist.org/packages/laravel-frontend-presets">
Packagist
</a>
</div>
<div class="container">
<div class="row">
<div class="col-md-2">
<ul class="menu-list">
<li><a href="/">Contributing</a></li>
</ul>
<p class="menu-label">Presets</p>
<ul class="menu-list">
<li><a href="/zurb-foundation/">Zurb Foundation</a></li>
<li><a href="/bulma/">Bulma</a></li>
<li><a href="/uikit3/">UIKit 3</a></li>
<li><a href="/primercss/">Primer CSS</a></li>
<li><a href="/w3css/">W3CSS</a></li>
<li><a href="/tachyons/">Tachyons</a></li>
<li><a href="/tailwindcss/">Tailwind CSS</a></li>
<li><a href="/karma-eslint/">Karma Eslint</a></li>
</ul>
</div>
<div class="col-md-10 realContent">
<h1>Contribution</h1>
<p>If you'd like to add a custom driver to the list, please download our <a href="https://github.com/laravel-frontend-presets/skeleton">skeleton repo</a>, and open a new issue on our <a href="https://github.com/laravel-frontend-presets/internals">internals repo</a>.</p>
<p>Contributions are <strong>welcome</strong> and will be fully <strong>credited</strong>.</p>
<p>Please read and understand the contribution guide before creating an issue or pull request.</p>
<h2>FAQ</h2>
<h3>Who owns the work?</h3>
<p>It is up to the package author to maintain the repository after it has been released.</p>
<p>You'll be given <strong>admin rights</strong> to your repo. So you are in total control. Only if you ever do something like breaking semver we'll step in.</p>
<p>If some problems should arise you're always free to copy over the code to your own repo and abandon the one in our organization.</p>
<h3>What level of access is given?</h3>
<p>Admin Rights</p>
<h3>What happens to the package, if the author decides to abandon or quit?</h3>
<p>Probably we, as a community, will step in until we find a replacement.</p>
<h3>What rights are being taken away from the author automatically?</h3>
<p>None</p>
<h3>What are their rights as an author?</h3>
<p>Technically: Admin rights, and you may do with the code whatever your want.</p>
<h3>Who decides who can be part of the package as a collaborator?</h3>
<p>As an admin, package maintainers can choose their own collaborators.</p>
<h3>Things you should be knowing:</h3>
<p>If you need help with anything just ask us. We're nice guys.</p>
<p><a href="https://twitter.com/m1guelpf">Miguel Piedrafita</a></p>
<p><a href="https://twitter.com/owenmelbz">Owen Melbourne</a></p>
<p><a href="https://twitter.com/Laraveldeep">Laraveldeep</a></p>
<h3>What are the rules?</h3>
<p>You're reading them. If we have the same values (creating a good experience for the users) we don't need too many rules.</p>
<h3>What are the benefits?</h3>
<p>For package users: an excellent experience</p>
<p>For package creators: a small ecosystem of package creators that can help each other</p>
<h2>Etiquette</h2>
<p>These projects are open source, and as such, the maintainers give their free time to build and maintain the source code
held within. They make the code freely available in the hope that it will be of use to other developers. It would be
extremely unfair for them to suffer abuse or anger for their hard work.</p>
<p>Please be considerate towards maintainers when raising issues or presenting pull requests. Let's show the
world that developers are civilized and selfless people.</p>
<p>It's the duty of the maintainer to ensure that all submissions to the project are of sufficient
quality to benefit the project. Many developers have different skillsets, strengths, and weaknesses. Respect the maintainer's decision, and do not be upset or abusive if your submission is not used.</p>
<h2>Viability</h2>
<p>When requesting or submitting new features, first consider whether it might be useful to others. Open
source projects are used by many developers, who may have entirely different needs to your own. Think about
whether or not your feature is likely to be used by other users of the project.</p>
<h2>Procedure</h2>
<p>Before filing an issue:</p>
<ul>
<li>Attempt to replicate the problem, to ensure that it wasn't a coincidental incident.</li>
<li>Check to make sure your feature suggestion isn't already present within the project.</li>
<li>Check the pull requests tab to ensure that the bug doesn't have a fix in progress.</li>
<li>Check the pull requests tab to ensure that the feature isn't already in progress.</li>
</ul>
<p>Before submitting a pull request:</p>
<ul>
<li>Check the codebase to ensure that your feature doesn't already exist.</li>
<li>Check the pull requests to ensure that another person hasn't already submitted the feature or fix.</li>
</ul>
<h2>Requirements</h2>
<p>If the project maintainer has any additional requirements, you will find them listed here.</p>
<ul>
<li>
<p><strong><a href="https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-2-coding-style-guide.md">PSR-2 Coding Standard</a></strong> - The easiest way to apply the conventions is to install <a href="http://pear.php.net/package/PHP_CodeSniffer">PHP Code Sniffer</a>.</p>
</li>
<li>
<p><strong>Add tests!</strong> - Your patch may not be accepted if it doesn't have tests.</p>
</li>
<li>
<p><strong>Document any change in behaviour</strong> - Make sure the <code>README.md</code> and any other relevant documentation are kept up-to-date.</p>
</li>
<li>
<p><strong>Consider our release cycle</strong> - We try to follow <a href="http://semver.org/">SemVer v2.0.0</a>. Randomly breaking public APIs is not an option.</p>
</li>
<li>
<p><strong>One pull request per feature</strong> - If you want to do more than one thing, send multiple pull requests.</p>
</li>
<li><strong>Send coherent history</strong> - Make sure each individual commit in your pull request is meaningful. If you had to make multiple intermediate commits while developing, please <a href="http://www.git-scm.com/book/en/v2/Git-Tools-Rewriting-History#Changing-Multiple-Commit-Messages">squash them</a> before submitting.</li>
</ul>
<p><strong>Happy coding</strong>!</p>
</div>
</div>
</div>
<footer>
<div class="container">
<div class="content">
© Copyright 2018 Laravel Frontend Presets
</div>
</div>
</footer>
<script src="/assets/prism.js"></script>
</body>
</html>