Menu
I browsed some of their sites. They always point to bug list as start of participating project.But, as a newbie in that project? How can I fix bug at the beginning?
Can anybody give me some suggestions about this?
899
Yes, it is possible to make an open source project into a closed source project. The copyright holder can change the license of a project at any time, or cease to distribute source code of new releases. New releases can therefore be made closed source.
With closed source software (also known as proprietary software), the public is not given access to the source code, so they can't see or modify it in any way. But with open source software, the source code is publicly available to anyone who wants it, and programmers can read or change that code if they desire.
Open-source projects that are hosted in public repositories benefit from contributions made by the broader developer community, and are typically managed through Git.
Issac Truett's answer is good.
My only suggestion would be to pick a project and download their source code. Most open source projects use CVS, Subversion, or Git to manage the source code.
Pick an integrated development environment (IDE) that supports the language of the project and attach the IDE to their source code manager.
Spend some time getting familiar with the source code, and the bug list will make more sense.
68
Almost every Open Source project I've ever seen has a stack of minor issues in the corner - cosmetic or otherwise largely inconsequential things that nobody has considered worth their time. If you just want to get your foot in the door, that's probably a good way to introduce yourself. Just find something easy, make sure you implement it well, and follow the project's rules on coding style, submission for review, etc.
Or, ask the project. "I'm new, I want to help, this is my skill set. Would someone be willing to mentor me?"
39
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
