88Community
99#########
1010
11+ ************************
12+ Meetings and discussions
13+ ************************
14+
1115We hold semi-regular meetings on Zoom
1216to discuss all things related to Unit
1317with our tightly knit and vibrant community.
@@ -17,41 +21,70 @@ Recorded sessions:
1721- `NGINX Unit Community Call No.1
1822 <https://www.youtube.com/watch?v=EZbcc6D03Io> `__
1923
24+ *************************
25+ Reporting bugs and issues
26+ *************************
2027
21- ************
22- Contribution
23- ************
28+ You can report bugs and issues on GitHub:
2429
30+ <<<<<<< HEAD
31+ - You can report issues and bugs on the
32+ `Issues <https://github.com/nginx/unit-docs/issues >`_
33+ section of the Unit repo.
34+ =======
2535NGINX Unit is released under the
2636`Apache 2.0 license <https://github.com/nginx/unit/blob/master/LICENSE >`_;
2737we maintain GitHub
2838`repos <https://github.com/nginx >`_.
39+ >>>>>>> origin/main
40+
41+ - If you have found a fix or want to suggest a change to the code,
42+ you can open a `pull request <https://github.com/nginx/unit-docs/pulls >`_
43+ on the Unit repo.
44+
45+ You can also ask questions and discuss your suggestions for Unit by
46+ `subscribing <https://mailman.nginx.org/mailman3/lists/unit.nginx.org/ >`_
47+ to the unit@nginx.org mailing list and posting your ideas there.
2948
30- Please report any security-related issues
31- concerning Unit to
49+ ***************************
50+ Reporting security concerns
51+ ***************************
52+
53+ Please report any security-related issues concerning Unit to
3254`security-alert@nginx.org <security-alert@nginx.org >`__.
33- For our mutual convenience,
34- specifically mention NGINX Unit in the subject
35- and follow the
36- `CVSS v3.1 <https://www.first.org/cvss/v3.1/specification-document >`__
37- specification.
55+ For our mutual convenience, specifically mention **NGINX Unit ** in the subject and follow the
56+ `CVSS v3.1 <https://www.first.org/cvss/v3.1/specification-document >`__.
57+
58+
59+ ************
60+ Contributing
61+ ************
3862
39- To suggest changes in code or documentation and ask questions,
40- `subscribe <https://mailman.nginx.org/mailman3/lists/unit.nginx.org/ >`_
41- to the unit@nginx.org mailing list
42- and post your ideas there.
43- Also, you can open a pull request on GitHub
44- or join our
45- `Slack community <https://community.nginx.org/joinslack >`__.
63+ We welcome contributions to the NGINX Unit project.
64+ If you have a feature request or a bug fix, please submit a pull request on the
65+ `unit repo <https://github.com/nginx/unit-docs/pulls >`_.
4666
47- Source code:
67+ Please review the `Contributing Guideliens <https://github.com/nginx/unit/blob/master/CONTRIBUTING.md >`_
68+ before submitting your pull request.
4869
49- - GitHub repository: https://github.com/nginx/unit
70+ If you are interested in contributing to the Unit documentation,
71+ or find a typo or an error in the docs, you can submit a pull request on the
72+ `unit-docs repo <https://github.com/nginx/unit-docs/pulls >`_.
5073
51- Command-line tools:
5274
53- - GitHub repository: https://github.com/nginx/unit/tree/master/tools
75+ ***********
76+ Source Code
77+ ***********
78+ The source code for the NGINX Unit project is available on GitHub.
5479
55- Documentation:
80+ .. list-table ::
81+ :header-rows: 1
5682
57- - GitHub repository: https://github.com/nginx/unit-docs
83+ * - Repository
84+ - Description
85+ * - `github.com/nginx/unit <https://github.com/nginx/unit >`_
86+ - The repository for the NGINX Unit project source code.
87+ * - `github.com/nginx/unit-docs <https://github.com/nginx/unit-docs >`_
88+ - The source code for the NGINX Unit documentation you are currently reading.
89+ * - `github.com/nginx/unit/tree/master/tools <https://github.com/nginx/unit/tree/master/tools >`_
90+ - Source code for the NGINX Unit command-line tools.
0 commit comments