@@ -8,11 +8,18 @@ contribute.
8
8
9
9
## Purpose
10
10
11
- Our development team is small, our ability to quickly evaluate a need or a code submission is
12
- therefore critical. Please follow the present contributing guidelines so that we can efficiently
13
- consider your proposal. You should also read or our [ code of conduct] ( CODE_OF_CONDUCT.md ) , providing
11
+ We aim to evaluate needs and code submissions as efficiently as possible. Since the Pillarbox web
12
+ suite is a collaborative effort across multiple contributors and teams, following these contribution
13
+ guidelines helps us streamline reviews and maintain consistency.
14
+
15
+ You should also read or our [ code of conduct] ( CODE_OF_CONDUCT.md ) , providing
14
16
a few guidelines to keep interactions as respectful as possible.
15
17
18
+ ## Scope and Ownership
19
+
20
+ The Pillarbox web suite is a collaborative effort involving multiple teams. No single team owns the
21
+ entire suite, and contributions come from various stakeholders.
22
+
16
23
## Contributions we are looking for
17
24
18
25
Any kind of contribution is welcome, as long as it improves the overall quality of our product, for
@@ -24,15 +31,19 @@ example:
24
31
* Translation improvements.
25
32
26
33
Contributions can either take the form of simple issues where you describe the problem you face or
27
- what you would like to see in our products. If you feel up to the challenge, you can even submit
28
- code in the form of pull requests which our team will review.
34
+ what you would like to see in our products. If you feel up to the challenge, you can submit code via
35
+ pull requests, which will be reviewed by the Pillarbox team and other maintainers involved in this
36
+ shared effort.
29
37
30
38
## Contributions we are not looking for
31
39
32
40
Requests which are too vague or not related to our product will not be taken into account. We also
33
41
have no editorial influence, any issue related to the content available on our platform will simply
34
42
be closed.
35
43
44
+ This repository focuses specifically on components related to video.js and Pillarbox only.
45
+ Contributions unrelated to these components or outside this scope are unlikely to be accepted.
46
+
36
47
## Making a contribution
37
48
38
49
You can use issues to report bugs, submit ideas or request features. People with a programming
@@ -55,12 +66,14 @@ Templates are available when you want to contribute:
55
66
56
67
## Code conventions
57
68
58
- We currently have no formal code conventions, but we try to keep our codebase consistent. In
59
- general, having a look at the code itself should be enough for you to discover how you should write
60
- your changes.
69
+ While there are no formal, rigid code conventions in place, we strive to maintain a consistent
70
+ codebase across all contributors and teams involved in the Pillarbox web suite. Please follow the
71
+ existing style and patterns you observe in the code to ensure your changes integrate smoothly with
72
+ the shared components.
61
73
62
74
## Code review
63
75
64
- Pull requests, once complete, can be submitted for review by our team. Depending on the complexity
65
- of the involved changes, a few iterations might be needed. Once a pull request has been approved, it
66
- will be rebased, merged back into the development trunk and delivered with the next release.
76
+ Pull requests will be reviewed by members of the Pillarbox team and other contributors involved in
77
+ maintaining the shared components. Depending on the complexity of the changes, multiple review
78
+ cycles may be needed to ensure quality and compatibility. Approved pull requests will be rebased and
79
+ merged into the main development branch and included in the next release.
0 commit comments