You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
description: Apply to become a committer with merge rights on the PrestaShop project.
3
+
body:
4
+
- type: markdown
5
+
attributes:
6
+
value: |
7
+
## About the Committer role
8
+
9
+
Committers are contributors with merge rights who participate in reviewing code contributions.
10
+
11
+
> **A note on what this role is - and isn't.**
12
+
> Being a committer is not about gaining power or having the final say on things. It is about showing up: reading pull requests carefully, leaving thoughtful feedback, helping contributors improve their work, and taking shared responsibility for the quality of the codebase. The merge button is a tool for serving the project, not a status symbol.
13
+
14
+
### Prerequisites
15
+
16
+
Before applying, make sure you meet the following criteria:
17
+
18
+
- **Active participation** in the project
19
+
- **At least one accepted, quality Pull Request**
20
+
- A record of **Pull Request reviews**
21
+
- Real interest in getting involved in code review
22
+
- Respect for the [Code of Conduct](https://www.prestashop-project.org/code-of-conduct/)
23
+
- Alignment with the project's goals (Symfony migration, VueJS adoption, etc.)
24
+
25
+
### How the process works
26
+
27
+
1. Submit this issue explaining why you'd like to become a committer
28
+
2. If **three members of technical council approve it**, your application is accepted
29
+
3. If the issue does not receive three positive votes within **30 days**, it is considered rejected and closed
30
+
4. Upon approval, you receive full committer rights for a **90-day trial period**
31
+
5. At the end of the trial, your status is confirmed
32
+
33
+
> ℹ️ The voting process is not mandatory if you are offered the role directly by technical council members (with at least three supporters).
34
+
35
+
- type: checkboxes
36
+
attributes:
37
+
label: Prerequisites
38
+
options:
39
+
- label: I understand and accept the project's [Code of Conduct](https://www.prestashop-project.org/code-of-conduct/).
40
+
required: true
41
+
- label: I have a record of accepted Pull Requests in the PrestaShop project.
42
+
required: true
43
+
- label: I have reviewed Pull Requests from other contributors.
44
+
required: true
45
+
- label: I am aware that this role comes with responsibilities around code review, quality standards, and active participation.
46
+
required: true
47
+
48
+
- type: dropdown
49
+
id: project-scope
50
+
attributes:
51
+
label: Which part of the project are you applying for?
52
+
description: You can apply for one or several areas.
53
+
multiple: true
54
+
options:
55
+
- Core (PrestaShop/PrestaShop)
56
+
- Modules
57
+
- Theme
58
+
- Documentation
59
+
- Other
60
+
validations:
61
+
required: true
62
+
63
+
- type: textarea
64
+
id: accepted-prs
65
+
attributes:
66
+
label: Links to your accepted Pull Requests
67
+
description: List Pull Requests you authored that were merged into the project.
68
+
placeholder: |
69
+
- https://github.com/PrestaShop/PrestaShop/pull/…
70
+
- https://github.com/PrestaShop/PrestaShop/pull/…
71
+
validations:
72
+
required: true
73
+
74
+
- type: textarea
75
+
id: pr-reviews
76
+
attributes:
77
+
label: Links to Pull Request reviews you performed
78
+
description: Show your track record as a reviewer.
description: Report an issue on the prestashop-project.org website. Do NOT report PrestaShop software bugs here.
3
+
labels: ['Bug']
4
+
body:
5
+
- type: markdown
6
+
attributes:
7
+
value: |
8
+
### ❗️ Read this before submitting a bug report:
9
+
- This repository is for the **prestashop-project.org website** only. To report a bug in the PrestaShop software, use the [PrestaShop core repository](https://github.com/PrestaShop/PrestaShop/issues/new/choose).
10
+
- **Write in English.** Reports in other languages will be closed.
Copy file name to clipboardExpand all lines: content/maintainers-guide/how-to-become-a-committer.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,12 +12,12 @@ Committers participate in reviewing code contributions.
12
12
## Prerequisites to become a committer
13
13
14
14
1.**Active participation in the project**
15
-
- Have at least one accepted, quality Pull Request.
15
+
- Have a record of quality Pull Requests.
16
16
- Display a record of Pull Request reviews.
17
17
- Real interest in getting involved in code review.
18
18
2.**Cultural convergence**
19
19
- Respect the Code of Conduct; behave respectfully and in good faith.
20
-
- Agree to work together with the rest of the maintainer team towards main goals (see [The Future Architecture][future-architecture]): migration to Symfony, adoption of VueJS ...
20
+
- Agree to work together with the rest of the project members towards main goals (see [The Future Architecture][future-architecture]): migration to Symfony, adoption of VueJS ...
21
21
22
22
## Requirements to continue being a committer
23
23
@@ -34,12 +34,12 @@ All the above, plus:
34
34
## How to apply to be a committer
35
35
36
36
1.[Open an issue on the open source repository](https://github.com/PrestaShop/open-source/issues/new) explaining why you apply to become a committer, and on what part of the project (Core or module/subproject).
37
-
2. If three maintainers approve the application, the new committer is approved.
37
+
2. If three members of the technical council approve the application, the new committer is approved.
38
38
3. After 30 days, if the issue did not receive three positive votes, it is considered rejected and closed.
39
39
40
-
Note: the above process is not mandatory for individuals who are offered the committer role by maintainers, as long as the candidate is supported by at least three maintainers.
40
+
Note: the above process is not mandatory for individuals who are offered the committer role by technical council members, as long as the candidate is supported by at least three technical council members.
41
41
42
-
Upon approval, new committer is granted full committer rights and accesses for a 90-day trial period. This period aims to provide both the maintainer team and the new committer a better understanding of this new arrival and to validate whether expectations meet reality. Both maintainer team or new committer can express their wish for this situation to end before the 90-day trial period, revoking the committer status.
42
+
Upon approval, new committer is granted full committer rights and accesses for a 90-day trial period. This period aims to provide both the technical council and the new committer a better understanding of this new arrival and to validate whether expectations meet reality. Both technical council or new committer can express their wish for this situation to end before the 90-day trial period, revoking the committer status.
43
43
44
44
At the end of the 90-day trial period, the committer is confirmed in his position.
45
45
@@ -51,7 +51,7 @@ A project committer status can be revoked for any of the following reasons:
51
51
- Lack of activity for the past three months.
52
52
- Willful negligence or intent to harm the PrestaShop project.
53
53
- On their demand, for personal reasons.
54
-
- On request of at least three maintainers.
54
+
- On request of at least three members of the technical and/or leadership council, for any reason.
0 commit comments