Open source projects

[EvilManagedCare]

I'm currently a computer science student. I would like to boost my resume content in terms of experience, but will more than likely not be able to participate in an internship. I have considered getting involved in some open source projects at Source Forge. Is this a good way to bolster the experience section of my resume? What are some types of projects I may want to look for?

I had in the past attempted to get involved in a couple that were entry level, but I found the complete lack of documentation or direction (to the tune of "what would you like done with this feature?", not requests for hand holding) from the project managers frustrating and never was able to very far if at all. Is this all too common in open source projects?

 

[GeekDrew]

Originally posted by: EvilManagedCare
I had in the past attempted to get involved in a couple that were entry level, but I found the complete lack of documentation or direction (to the tune of "what would you like done with this feature?", not requests for hand holding) from the project managers frustrating and never was able to very far if at all. Is this all too common in open source projects?

While I can't speak so broadly as to say "most", I do think that it is extremely common in open source projects - particularly small or niche projects - to have little or no documentation, and little direction. Perhaps you should join a project where you are able to come up with ideas and a course of direction with features or portions of the project, rather than asking for any advice at all? You'd obviously have to work with the project manager/maintainer, but if that doesn't get you anywhere, come up with your own ideas for the features/etc.

 

[Markbnj]

I agree with GeekDrew. You're probably better off starting up your own. There are well-known open source projects that would lend some credibility to a resume, and more importantly lead to networking opportunities, but it would take years of involvement to work your way to a position of prominence in one of them, or some real prodigy-type accomplishments in a short time .

But you can come up with your own ideas, and establish a project on SourceForge or CodePlex, and have a place to point people to when they express interest in your work, or are reading a resume.

 

[chronodekar]

At the moment, I'm directly working with an open source project. (don't ask which) And incomplete documentation is not the only problem.I was working on a few source files for nearly a week and after that, I thought I'd try and push a patch out to the mailing list. I then get a reply telling me that main development was moved somewhere else MONTHS ago. The documentation was, to put it lightly, out-dated.

Frustrating does not begin to describe what I felt. :|

But, that is just one bad memory. On the other side, I've had more than 10 good correspondences with the same project members.

The thing about open source projects, is even though the output of the good ones comes really close to a professional product, you must remember that, internally they are not managed that way.The key word here is community. If you and your friends made a software project that you are willing to share, and host it on source forge, how would it look like? No doubt, you would be more than happy to have other, possibly more experienced people contribute code modifications to you, but will you take the time & effort to explain/teach them your code? Most of the time, the answer is NO.

That's the way open-source is. It's all about community. I'm not saying that they don't like newbies. In fact, they are usually welcomed with open arms. (I know I was! )

What's NOT welcome are leechers. And it's difficult to distinguish between the two. The easiest way to set yourself apart from them, is to show that you have made some effort of your own to study and understand the code already posted out there. (Not many here will agree with me, but I found this : How To Ask Questions The Smart Way VERY helpful)

If you plan to work on an open source project for your resume, then I'll tell you it's a good idea. BUT, this is going to require a LOT of discipline. What drives you will be your own will. There will be no-one to push you around telling you what to do.

What happens to most well-meaning people is that real life gets in the way and we end up postponing things. Like me, for instance. I've not updated the Free References Thread (link in my signature) for quite some time now. It's not that I've forgotten it or have no more new links to put up. (I actually have some python links I've been meaning to include for about 2 weeks now) What's happening is 2 things. a) I can't seem to get 1 hour of free time to do it and b) I want to keep the information in 2 posts, and NOT consolidate it into 1 post. I just can't figure out how to reply to that suggestion on the thread ...

But that's just me. For the rest of you, it's just an excuse. (I can read your minds, you see )

-sigh- Looks like I've started ranting now.


Bottom Line: This is going to require a LOT of dedication, determination & discipline to make it work. Think you're upto it?

 

[nakedfrog]

Having reviewed a number of resumes last year when we had to replace someone, I would definitely consider this a plus.

 

[SJP0tato]

Originally posted by: EvilManagedCare
I had in the past attempted to get involved in a couple that were entry level, but I found the complete lack of documentation or direction (to the tune of "what would you like done with this feature?", not requests for hand holding) from the project managers frustrating and never was able to very far if at all. Is this all too common in open source projects?

It can be fairly common, but maybe you could find an entry level project that has a lack of documentation and offer to write it. It's not the most glamorous role in software development, but it will get your hands into the code in a way that you wouldn't normally need to do. You'll also get the pain of dealing with reading other's code, which will probably make for a good interview 'war story' or two.

Example:
Bigshot interviewer: "Well EvilManagedCare, can you tell use about some difficulties you've run into with a recent project you've worked on and how you resolved it"

EvilManagedCare: "Definitely, I was working with openSource project x, working on shoring up much of their documentation when I ran across X, Y, and Z, and had to get together several of the devs who created it and create a workable solution, etc"

 

[chronodekar]

Originally posted by: SJP0tato

Originally posted by: EvilManagedCare
I had in the past attempted to get involved in a couple that were entry level, but I found the complete lack of documentation or direction (to the tune of "what would you like done with this feature?", not requests for hand holding) from the project managers frustrating and never was able to very far if at all. Is this all too common in open source projects?

It can be fairly common, but maybe you could find an entry level project that has a lack of documentation and offer to write it. It's not the most glamorous role in software development, but it will get your hands into the code in a way that you wouldn't normally need to do. You'll also get the pain of dealing with reading other's code, which will probably make for a good interview 'war story' or two.

Example:
Bigshot interviewer: "Well EvilManagedCare, can you tell use about some difficulties you've run into with a recent project you've worked on and how you resolved it"

EvilManagedCare: "Definitely, I was working with openSource project x, working on shoring up much of their documentation when I ran across X, Y, and Z, and had to get together several of the devs who created it and create a workable solution, etc"

On a related note, it will teach you HOW to document code yourself. That is a very VERY vital skill needed in this industry and it's amazing how few people know how to do it.

A personal suggestion from me, learn doxygen. I find it most handy to document code.