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
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+8-10Lines changed: 8 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,7 +40,7 @@ but it should be easily transferable to other (sub)projects.
40
40
41
41
> **Note:** Please don't file an issue to ask a question. You'll get faster results by using the resources below.
42
42
43
-
For general questions, please refer to [OpenCloud's FAQs](https://opencloud.eu/faq/) or check the [project page](https://github.com/opencloud-eu) for communication channels.
43
+
For general questions, please refer to [OpenCloud's FAQs](https://docs.opencloud.eu/docs/admin/resources/faq/) or check the [project page](https://github.com/opencloud-eu) for communication channels.
44
44
45
45
## What to know before getting started
46
46
@@ -55,7 +55,7 @@ The OpenCloud project follows the strict GitHub workflow of development as brief
55
55
### OpenCloud Company, Engineering Partners and Community
56
56
57
57
OpenCloud is largely created by developers who are employed by the [OpenCloud company](https://opencloud.eu), which is located in Germany.
58
-
It is providing support for OpenCloud for customers mainly in the EU. In addition, there are engineering partners who also work full-time on OpenCloud related code, for example, on the component [REVA](https://github.com/cs3org/reva/).
58
+
It is providing support for OpenCloud for customers mainly in the EU. In addition, there are engineering partners who also work full-time on OpenCloud related code, for example, on the component [REVA](https://github.com/opencloud-eu/reva/).
59
59
60
60
Because of that fact, the pace that the development is moving forward is sometimes high for people who are not willing and/or able to spend a comparable amount of time to contribute.
61
61
Even though this can be a challenge, it should not scare anybody away. Here is our clear commitment that we feel honored by everybody who is interested in our work and improves it, no matter how big the contribution might be.
@@ -113,7 +113,7 @@ Explain the problem and include additional details to help maintainers reproduce
113
113
Provide more context by answering these questions:
114
114
115
115
***Did the problem start happening recently** (e.g. after updating to a new version) or was this always a problem?
116
-
* If the problem started happening recently, **can you reproduce the problem in an older version?** What's the most recent version in which the problem doesn't happen? You can find more information about how to set up [test environments](https://docs.opencloud.eu/devel/testing)in the [developer documentation](https://docs.opencloud.eu/docs/dev/intro).
116
+
* If the problem started happening recently, **can you reproduce the problem in an older version?** What's the most recent version in which the problem doesn't happen? You can find more information about how to set up in the [Getting Started guide](https://docs.opencloud.eu/docs/admin/getting-started).
117
117
***Can you reliably reproduce the issue?** If not, provide details about how often the problem happens and under which conditions it normally happens.
118
118
119
119
Include details about your configuration and environment as asked for in the template.
@@ -146,15 +146,13 @@ Enhancement suggestions are tracked as [GitHub issues](https://guides.github.com
146
146
147
147
Unsure where to begin contributing to OpenCloud? You can start by looking through these `Needs-help` issues:
148
148
149
-
* The [Good first issue](https://github.com/opencloud-eu/opencloud/labels/Topic%3Agood-first-issue) label marks good items to start with.
150
-
*[Tests needed](https://github.com/opencloud-eu/opencloud/labels/Interaction%3ANeeds-tests) - issues which would benefit from a test.
151
-
*[Help wanted issues](https://github.com/opencloud-eu/opencloud/labels/Interaction%3ANeeds-help) - issues which should be a bit more involved.
149
+
* The [Good first issue](https://github.com/opencloud-eu/opencloud/labels/Type%3Agood-first-issue) label marks good items to start with.
150
+
* The [Feature Request](https://github.com/opencloud-eu/opencloud/issues?q=state%3Aopen%20label%3AType%3AFeature-Request) label lists features the community would like to see implemented.
152
151
153
152
It is fine to pick one of the lists following personal preference.
154
153
While not perfect, the number of comments is a reasonable proxy for the impact a given change will have.
155
154
156
-
To find out how to set up OpenCloud for local development, please refer to the [Developer Documentation](https://docs.opencloud.eu/docs/dev/web/getting-started).
157
-
It contains a lot of information that will come in handy when starting to work on the project.
155
+
To find out how to set up OpenCloud for local development, please refer to the [Developer Documentation](https://docs.opencloud.eu/docs/dev/web/getting-started) for the web side, and the general server [README](https://github.com/opencloud-eu/opencloud/blob/main/README.md) for backend setup. Both contain information that will come in handy when starting to work on the project.
158
156
159
157
### Pull Requests
160
158
@@ -221,7 +219,7 @@ To help you find issues and pull requests, each label can be used in search link
221
219
The labels are loosely grouped by their purpose, but it's not required that every issue has a label from every group or that an issue can't have more than one label from the same group.
222
220
223
221
The list here contains all the more general categories of issues which are followed by a colon and a specific value.
224
-
For example, severity 1 looks like `Severity:sev1-critical`.
222
+
For example, severity 1 looks like `Priority:p1-urgent`.
225
223
226
224
#### Platform
227
225
@@ -257,7 +255,7 @@ Categorizes the issue to also indicate the type of the issue.
257
255
258
256
#### Status
259
257
260
-
The status in the ticket life cycle. Keep an eye on that one, especially for the `Waiting-for-Feedback` tag which might indicate that the reporter is asked for feedback.
258
+
The status in the ticket life cycle. Keep an eye on that one, especially for the `Status:Needs-Review` tag which might indicate that the reporter is asked for feedback.
0 commit comments