The right way to participate in open source projects?

Thanks to the ease of use and the good github design, we, in fact, are only two, in a small tech company (or medium-sized animation studio) we would like to participate in an open source project: partio . We branched it and started improving / pushing some things. It has just begun, and nothing bad or good has happened. Since you have been using open source for such a long time, I would like to return something useful or meaningful. I wonder what to do or not to make our tiny efforts capable, but not harmful?

And one more question: what should we take care of when participating in open source projects?

Some other questions I checked:

+4
source share
1 answer

Technical point:
Please replace your local work on top of the branch from the original repository (which you add as a remote one) before clicking on your branch and pulling out a request for the specified original project.
This ensures that your transfer request can be applied in a quick manner without a merge conflict. (See Also Cherrypicking vs. Rebasing )

The rest is mainly about the message , usually through the error controller, to identify the current error for correction and added functions.
On this front, GitHub pull request2.0 is a good illustration of this communication topic.

Today, port requests are lively discussions about the code you want to combine. They are our view on code review and represent most of our vision for collaborative development.

enter image description here

+5
source

Source: https://habr.com/ru/post/1337158/


All Articles