News for hackers. Stuff that matters.
Re:Barriers faced by newcomers to open source projects: a sy... by britta on Friday August 01, 2014 @03:21PM (#8122285)
This is great. I want this information to be in a form easily accessible and readable for any project maintainer who wants to learn about concrete ways to improve their projects. So, question: what form should that be? A blog post explaining the highlights, with a title with good keywords? A YouTube video with explanations and anecdotes, like a talk without a conference? Where do maintainers learn about this kind of thing (other than occasional news posts on HN with advice), so that we can make this information show up there?

I volunteer for OpenHatch (https://openhatch.org/), a non-profit open source project that aims to help newcomers contribute to projects + help projects make themselves more welcoming. What do you think is the most effective step OpenHatch could take for helping maintainers? It has some efforts already, and I have some ideas, but I'm curious to hear more ideas. (Also if you want to help, OpenHatch is already a loose collection of people who care about this; come join us.)

Re:Barriers faced by newcomers to open source projects: a sy... by vitovito on Friday August 01, 2014 @05:26PM (#8122912)
Open source project maintainers might also consider a lighter-weight implementation, a CONTRIBUTING file, per Brad Fitzpatrick's CONTRIBUTING project: http://contributing.appspot.com
Re:Barriers faced by newcomers to open source projects: a sy... by Mz on Friday August 01, 2014 @05:14PM (#8122839)
I would personally go with a "Best Practices" page that streamlines the info. I have a very long history of doing volunteer work of various sorts. Some of the early observations are things I am familiar with but I find this paper rather clunky.

I suspect there are no easy answers for some of the barriers they list. (For example, I feel like "lacks the skill to do the job" is probably not something the project manager can or should solve, anymore than a hiring manager should take just anyone who wants the job even though they aren't qualified.) But the social piece is something I can break down for you into basically two key points:

1) Greet people warmly at the door.

People who get that initial "Hi! How are you? We are so happy you dropped by!" kind of response are much, much more likely to keep coming back, even if it takes a bit to figure out where they fit in. Folks who get the cold shoulder often just disappear, never to be heard from again.

2) Never let any question go completely unanswered.

If it does not get a meaningful answer in a timely fashion, then the person in charge should at least drop the person a note to say "I don't know the answer." (When I had a directorship on a voluntary health and welfare organization trying to make the transition to full scale charity, my rule of thumb was that if it had no response after 3 days, I would step in and say something, even if I had no answer.) Depending upon the environment in question, that sometimes bumps the question and allows others to notice who may have missed it due to being away, busy, whatever. So, sometimes just answering nominally will get it answered meaningfully by another but even if it doesn't, the person doesn't wind up feeling like they are out in social Siberia and afraid to speak up again.

Re:Barriers faced by newcomers to open source projects: a sy... by restless on Friday August 01, 2014 @04:34PM (#8122658)
Thank you for the link I will explore it further this weekend
[dead]
Re:Barriers faced by newcomers to open source projects: a sy... by x0x0 on Friday August 01, 2014 @05:09PM (#8122814)
I dunno; having project members not actively be dicks to newcomers is always good advice.

That said -- and I'm being vague because some people on hn are dicks and I'm careful how trackable my online presence is -- small projects get lots of, well, basically useless people who need tons of handholding to get anything accomplished. I see the upside for them, but I don't see the upside for me: if I where to help them out, I'd spend my limited available time on handholding people who apparently managed to get ms degrees in cs without being able to code instead of doing what I enjoy. So I ignore them. Open source is apparently the new resume chit so people want to spend minimal effort to put a patch into a github project. We're always open to helpful people but I have a depth 1 decision tree for ignoring the idiots: if you can't successfully read and follow the instructions in readme.md and make, you're worthless and I kill your email.

Re:Barriers faced by newcomers to open source projects: a sy... by dictum on Friday August 01, 2014 @08:18PM (#8123534)
Okay, let's imagine you're someone who has never contributed to an open source project. How would you know which projects to "shut up and code" for?
Re:Barriers faced by newcomers to open source projects: a sy... by turingfail on Friday August 01, 2014 @08:41PM (#8123604)
> How would you know which projects to "shut up and code" for?

You should need something before you have a desire to make it. But most likely you are already using something you would like to improve upon.

If neither of those is the case, why try to write software?

Re:Barriers faced by newcomers to open source projects: a sy... by bmalee on Saturday August 02, 2014 @06:58AM (#8124616)
This is a bizarre statement. There are plenty of reasons to write software that don't revolve around "I want this software for my own personal benefit". For example the person in question may just want experience of programming, and/or they may wish to contribute to something that helps others rather than themselves.

(I suspect many people are in a similar position in their day job, given the existence of large amounts of software for which the target audience is not computer programmers.)

Re:Barriers faced by newcomers to open source projects: a sy... by turingfail on Saturday August 02, 2014 @03:40PM (#8125755)
I wasn't really trying to distinguishing between personal quantifiable gains from other gains. My being annoyed for someone else whose showed me ridiculous workarounds is a perfect example of a reason I would fix software so >I< can feel better about reality, myself and experience less pain and embarrassment for my profession if I help them again in the future.

For pure experience programming, sure we write "garbage software" to make the changes in ourselves. But if it is worth sharing (even for edification or statistical analysis) then we go back to a personal reason otherwise it has little relevance to the larger topic of discussion, and I personally focus on the garbage in "garbage software" rather than software.

Re:Barriers faced by newcomers to open source projects: a sy... by watwut on Saturday August 02, 2014 @03:40AM (#8124340)
The one that does not have dozens of ignored three years old pull requests and decent level communication with newcomers on mailing list and in issues.
Re:Barriers faced by newcomers to open source projects: a sy... by bmalee on Saturday August 02, 2014 @06:38AM (#8124591)
You say 'extrovert' and 'social' almost as if they are insults.
Re:Barriers faced by newcomers to open source projects: a sy... by pokpokpok on Friday August 01, 2014 @08:38PM (#8123600)
>someone is having a problem that I didn't have

>they must be stupid

Re:Barriers faced by newcomers to open source projects: a sy... by ben0x539 on Friday August 01, 2014 @07:52PM (#8123463)
Why are you posting this under a throwaway? Are you perhaps discouraged by politics?
Re:Barriers faced by newcomers to open source projects: a sy... by vomitcuddle on Friday August 01, 2014 @06:43PM (#8123226)
>2) Do not be discouraged by project politics (if applicable).

Yeah, too bad this only applies if you're a white male.