|
2 | 2 |
|
3 | 3 | ## RESOURCES |
4 | 4 |
|
5 | | -If you wish to contribute to Zend Framework, please be sure to |
| 5 | +If you wish to contribute to this project, please be sure to |
6 | 6 | read/subscribe to the following resources: |
7 | 7 |
|
8 | | - - [Coding Standards](https://github.com/zendframework/zf2/wiki/Coding-Standards) |
9 | | - - [Contributor's Guide](CONTRIBUTING.md) |
10 | | - - ZF Contributor's mailing list: |
11 | | - Archives: http://zend-framework-community.634137.n4.nabble.com/ZF-Contributor-f680267.html |
12 | | - |
13 | | - - ZF Contributor's IRC channel: |
14 | | - #zftalk.dev on Freenode.net |
| 8 | + - [Coding Standards](https://github.com/zendframework/zend-coding-standard) |
| 9 | + - [Forums](https://discourse.zendframework.com/c/contributors) |
| 10 | + - [Slack](https://zendframework-slack.herokuapp.com) |
| 11 | + - [Code of Conduct](CODE_OF_CONDUCT.md) |
15 | 12 |
|
16 | | -If you are working on new features or refactoring [create a proposal](https://github.com/zendframework/zend-expressive/issues/new). |
17 | | - |
18 | | -## Reporting Potential Security Issues |
19 | | - |
20 | | -If you have encountered a potential security vulnerability, please **DO NOT** report it on the public |
21 | | -issue tracker: send it to us at [[email protected]](mailto:[email protected]) instead. |
22 | | -We will work with you to verify the vulnerability and patch it as soon as possible. |
23 | | - |
24 | | -When reporting issues, please provide the following information: |
25 | | - |
26 | | -- Component(s) affected |
27 | | -- A description indicating how to reproduce the issue |
28 | | -- A summary of the security vulnerability and impact |
29 | | - |
30 | | -We request that you contact us via the email address above and give the project |
31 | | -contributors a chance to resolve the vulnerability and issue a new release prior |
32 | | -to any public exposure; this helps protect users and provides them with a chance |
33 | | -to upgrade and/or update in order to protect their applications. |
34 | | - |
35 | | -For sensitive email communications, please use [our PGP key](http://framework.zend.com/zf-security-pgp-key.asc). |
| 13 | +If you are working on new features or refactoring |
| 14 | +[create a proposal](https://github.com/zendframework/zend-expressive/issues/new). |
36 | 15 |
|
37 | 16 | ## RUNNING TESTS |
38 | 17 |
|
@@ -86,18 +65,6 @@ $ composer cs-fix |
86 | 65 | If the above fixes any CS issues, please re-run the tests to ensure |
87 | 66 | they pass, and make sure you add and commit the changes after verification. |
88 | 67 |
|
89 | | -## Running License Checks |
90 | | - |
91 | | -File-level docblocks should follow the format demonstrated in `.docheader`. To |
92 | | -check for conformity, use: |
93 | | - |
94 | | -```console |
95 | | -$ composer license-check |
96 | | -``` |
97 | | - |
98 | | -This will flag files that are incorrect, which you can then update. Re-run the |
99 | | -tool to verify your changes. |
100 | | - |
101 | 68 | ## Recommended Workflow for Contributions |
102 | 69 |
|
103 | 70 | Your first step is to establish a public repository from which we can |
@@ -189,15 +156,7 @@ To send a pull request, you have two options. |
189 | 156 | If using GitHub, you can do the pull request from there. Navigate to |
190 | 157 | your repository, select the branch you just created, and then select the |
191 | 158 | "Pull Request" button in the upper right. Select the user/organization |
192 | | -"zendframework" as the recipient. |
193 | | - |
194 | | -If using your own repository - or even if using GitHub - you can use `git |
195 | | -format-patch` to create a patchset for us to apply; in fact, this is |
196 | | -**recommended** for security-related patches. If you use `format-patch`, please |
197 | | -send the patches as attachments to: |
198 | | - |
199 | | -- [email protected] for patches without security implications |
200 | | -- [email protected] for security patches |
| 159 | +"zendframework" (or whatever the upstream organization is) as the recipient. |
201 | 160 |
|
202 | 161 | #### What branch to issue the pull request against? |
203 | 162 |
|
@@ -228,7 +187,3 @@ repository, we suggest doing some cleanup of these branches. |
228 | 187 | ```console |
229 | 188 | $ git push {username} :<branchname> |
230 | 189 | ``` |
231 | | - |
232 | | -## Conduct |
233 | | - |
234 | | -Please see our [CONDUCT.md](CONDUCT.md) to understand expected behavior when interacting with others in the project. |
0 commit comments