4

With the ease usage and good design of github, we, actually just two, in a small technical company (or a mid-sized animation studio) would like to get involved in an open source project: partio. We forked it and started committed/pushed some stuff. It just started and nothing bad or good happened. Because benefiting from open source for such a long time, I would like to feed back something useful or meaningful. I am wondering what should or shouldn't I do to make our tiny efforts contributive, but not harmful?

And then, another further question: what should we take care of while involved in open source projects?

Some other questions I have checked:

Community
  • 1
  • 1
Drake Guan
  • 14,514
  • 15
  • 67
  • 94

1 Answers1

5

A technical point:
Please rebase your local work on top of the branch from the original repo (that you add as a remote), before pushing your own branch and making pull request to said original project.
That will ensure that your pull request can be applied in a fast-forward manner, without any merge conflict. (See also Cherrypicking versus Rebasing)

The rest is mainly a question of communication, typically through a bug-tracker in order to identify the current bug to fix and the features to add.
On that front, the GitHub pull request2.0 is a good illustration of that communication topic.

As of today, pull requests are living discussions about the code you want merged. They're our take on code review and represent a big part of our vision for collaborative development.

enter image description here

Community
  • 1
  • 1
VonC
  • 1,262,500
  • 529
  • 4,410
  • 5,250
  • 2
    +1 on the communication part. Github/git is the tool only. Another important thing is that building merit requires you to solve things for the project, usually starting with simpler tasks. For project leaders, the opposite is true: You must make it possible for others to build merit by having a wide spectrum of problems of different skillset/difficulty. – I GIVE CRAP ANSWERS Jan 26 '11 at 16:45