1
- # Contributing to Angular Material
1
+ # Contributing to AngularJS Material
2
2
3
3
- [ Code of Conduct] ( #coc )
4
4
- [ Signing the CLA] ( #cla ) <br /><br />
9
9
- [ Submission Guidelines] ( #submit )
10
10
11
11
## <a name =" coc " ></a > Code of Conduct
12
- Help us keep Angular open and inclusive.
12
+ Help us keep AngularJS open and inclusive.
13
13
14
14
Please read and follow our
15
15
[ Code of Conduct] ( https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md ) .
16
16
17
17
<br />
18
18
## <a name =" question " ></a > Have a Question, Problem, or Idea?
19
19
20
- If you have questions or ideas regarding Angular Material, please direct these to the
21
- [ Angular Material Forum] ( https://groups.google.com/forum/#!forum/ngmaterial ) .
20
+ If you have questions or ideas regarding AngularJS Material, please direct these to the
21
+ [ AngularJS Material Forum] ( https://groups.google.com/forum/#!forum/ngmaterial ) .
22
22
23
23
Otherwise, do you:
24
24
@@ -44,7 +44,7 @@ You can request a new feature by
44
44
implement a new feature then consider what kind of change it is:
45
45
46
46
* ** Major Changes** that you wish to contribute to the project should be discussed first on our
47
- [ Angular Material Forum] ( https://groups.google.com/forum/#!forum/ngmaterial ) , so that we can better
47
+ [ AngularJS Material Forum] ( https://groups.google.com/forum/#!forum/ngmaterial ) , so that we can better
48
48
coordinate our efforts, prevent duplication of work, and help you to craft the change so that it is
49
49
successfully accepted into the project.
50
50
* ** Small Changes** can be crafted and submitted to the
@@ -80,12 +80,12 @@ quickly:
80
80
81
81
* ** Overview of the Issue** - if an error is being thrown, a non-minified stack trace helps.
82
82
83
- * ** Angular Material Version** - check the header of your ` angular-material.js ` file to determine
83
+ * ** AngularJS Material Version** - check the header of your ` angular-material.js ` file to determine
84
84
your specific version #.
85
85
86
86
``` js
87
87
/* !
88
- * Angular Material Design
88
+ * AngularJS Material Design
89
89
* https://github.com/angular/material
90
90
* @license MIT
91
91
* v0.6.0-rc1-master-57f10f7
@@ -104,13 +104,13 @@ Here are two examples of well-defined issues:
104
104
#### <a name =" submitpr " ></a >Submitting Pull Requests
105
105
106
106
** Important** : With the exception of minor bugs and doc fixes, we are not actively reviewing
107
- unsolicited PRs to Angular Material.
107
+ unsolicited PRs to AngularJS Material.
108
108
109
109
Please check with us via [ the discussion forum] ( https://groups.google.com/forum/#!forum/ngmaterial )
110
110
before investing significant effort in a planned Pull Request submission; it's likely that we are already
111
111
working on a related PR.
112
112
113
- * All contributions must be consistent with the Angular Material coding conventions. See the
113
+ * All contributions must be consistent with the AngularJS Material coding conventions. See the
114
114
[ Coding Guidelines] ( ../docs/guides/CODING.md )
115
115
* Submit proposed changes or additions as GitHub pull requests. See the
116
116
[ Pull Request Guidelines] ( ../docs/guides/PULL_REQUESTS.md )
@@ -120,7 +120,7 @@ working on a related PR.
120
120
121
121
We have very precise rules over how our git commit messages can be formatted. This leads to ** more
122
122
readable messages** that are easy to follow when looking through the ** project history** . It is
123
- important to note that we use the git commit messages to ** generate** the Angular Material
123
+ important to note that we use the git commit messages to ** generate** the AngularJS Material
124
124
[ Changelog] ( ../../CHANGELOG.md ) document.
125
125
126
126
> A detailed explanation of guidelines and conventions can be found in this
@@ -201,9 +201,9 @@ refactor(content): prefix mdContent scroll- attributes
201
201
## <a name =" pr_forks " ></a > Guidelines for Developer Commit Authorizations
202
202
203
203
Please review the [ Commit Level and Authorization Guidelines] ( ../docs/guides/COMMIT_LEVELS.md ) for
204
- details on how to implement and submit your fixes, changes, or enhancements to Angular Material.
204
+ details on how to implement and submit your fixes, changes, or enhancements to AngularJS Material.
205
205
206
- This guideline provides details on creating a repository Fork of the Angular Material repository
206
+ This guideline provides details on creating a repository Fork of the AngularJS Material repository
207
207
and how to submit Pull Requests.
208
208
209
209
0 commit comments