|
|
|
|
|
|
by code_pockets
5238 days ago
|
|
|
3. Not sure where to start. This was particularly true among younger developers. They'd be interested in joining a project to improve their skills and work w/ others, but they weren't sure how to get started. What should they work on? Where is the project headed? If they just start hacking on stuff, will the lead contributor find it useful? This is a deal-killer for me. Some of the OSS projects I've wanted to contribute to make getting up to speed rather difficult. Few offer documentation that makes joining and getting up to speed quickly easy. I know why such documentation does not exist, because we just want to code. But every OSS project (that allows others to actively contribute), should have some kind of welcome-here-is-what-you-need-to-start-package. Even a simple README committed to the git repo that outlines it would work fine. * That is one interesting app you got there. |
|
|