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
+7-8Lines changed: 7 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -31,21 +31,20 @@ Please read the [Eclipse Foundation policy on accepting contributions via Git](h
31
31
9. Push the changes in your branch to your forked repository.
32
32
10. Finally, go to [https://github.com/eclipse/paho.mqtt.embedded-c](https://github.com/eclipse/paho.mqtt.embedded-c) and create a pull request from your "YOUR_BRANCH_NAME" branch to the ```develop``` one to request review and merge of the commits in your pushed branch.
33
33
34
-
35
-
What happens next depends on the content of the patch. If it is 100% authored
36
-
by the contributor and is less than 1000 lines (and meets the needs of the
37
-
project), then it can be pulled into the main repository. If not, more steps
38
-
are required. These are detailed in the
39
-
[legal process poster](http://www.eclipse.org/legal/EclipseLegalProcessPoster.pdf).
40
-
41
-
34
+
What happens next depends on the content of the patch.
35
+
If it is 100% authored by the contributor with less than 1000 lines of new product code that meets
36
+
the needs of the project (refactored, test code and sample code is excluded from the count), then it
37
+
can be pulled into the main repository. When there are more than 1000 lines of new product code,
38
+
more steps are required. More details are provided in the [handbook](https://www.eclipse.org/projects/handbook/#ip).
42
39
43
40
## Developer resources:
44
41
45
42
46
43
Information regarding source code management, builds, coding standards, and more.
0 commit comments