saw this over on dev@community... i reckon "Finding a way to start" and "Code issues" are the most significant barriers here, but it'd be great to get feedback from any lurkers here:)
here's a couple concrete actions I think we could take... 1) Intentionally leave some small, approachable issues unfixed for a while (e.g. BLUR-351[1]). Promote them on twitter/mail list. 2) Create some docs on the overall structure of the code, how the projects fit together, maybe highlight some 'paths' through the code. thoughts? --tim [1] - https://issues.apache.org/jira/browse/BLUR-351 ---------- Forwarded message ---------- From: Nick Burch <[email protected]> Date: Tue, Aug 5, 2014 at 9:49 AM Subject: Article on "Barriers faced by newcomers to open source" To: [email protected] Hi All For those thinking about how to make it easier to new comers into your projects, and get them to stay, you may find this review article (especially section 3) of interest: http://www.igor.pro.br/publica/papers/OSS2014.pdf Nick
