Joining an open source project
-
To really start writing new code, or changing existing code of a project, I assume someone should have already understand hows all underlying things work and is fully understand how the code addition or modification would impact the project, however, I don't get how people joining an active open source project could achieve this. Even for a small open source project, there are still MBs of source files, the cost to study them is just way too great for general interest. But failed to do before touching it will almost end up breaking it. I had purchased some 3rd party library with source, but I never really changed them, since I have no idea how will that affect the code overall. I don't get how people getting started to join an open source project.
-
To really start writing new code, or changing existing code of a project, I assume someone should have already understand hows all underlying things work and is fully understand how the code addition or modification would impact the project, however, I don't get how people joining an active open source project could achieve this. Even for a small open source project, there are still MBs of source files, the cost to study them is just way too great for general interest. But failed to do before touching it will almost end up breaking it. I had purchased some 3rd party library with source, but I never really changed them, since I have no idea how will that affect the code overall. I don't get how people getting started to join an open source project.
This predicament also exists in non-open source projects. When a dev first joins a group, he/she probably has no idea how the software they create works. Its the same problem, only money and jobs are at stake. :~ I suppose that large projects with a morphing dev team is a prime example of how unit tests can be used effectively. If the project has comprehensive automated tests that run every time it is compiled, the odds of introducing bugs via side effects of new code would decrease.
:josh: My WPF Blog[^]
-
To really start writing new code, or changing existing code of a project, I assume someone should have already understand hows all underlying things work and is fully understand how the code addition or modification would impact the project, however, I don't get how people joining an active open source project could achieve this. Even for a small open source project, there are still MBs of source files, the cost to study them is just way too great for general interest. But failed to do before touching it will almost end up breaking it. I had purchased some 3rd party library with source, but I never really changed them, since I have no idea how will that affect the code overall. I don't get how people getting started to join an open source project.
VAIO Blue wrote:
I don't get how people getting started to join an open source project.
The problem is not just relevant to open source projects, but is also endemic in any development effort. And the answer to the problem is unit testing (automatic) for the code, and acceptance testing (usually manual) for the product. Regression testing is now folded in to unit testing, which encompasses not only "did you break what used to work" but "does the new stuff work" tests. Marc
Some people believe what the bible says. Literally. At least [with Wikipedia] you have the chance to correct the wiki -- Jörgen Sigvardsson
People are just notoriously impossible. --DavidCrow
There's NO excuse for not commenting your code. -- John Simmons / outlaw programmer