Should I publish my project as open source?

Question

I'm nearing completion of my programming degree and will be getting an internship through my school early next calendar year. Up to this point I have had pretty much no programming experience out there in the real world, so my resume will hardly be impressive.

I have, however, been working on a helper utility for an obscure application as stated in my other question. So far I spent more than 30 hours on it, and produced more than 500 LOC. It's by no means finished, but it is functional, and I think it will turn out pretty well.

Being pretty sure that nobody except the person I'm writing this application for will ever need it, should I start an open source project with it? If so, could putting such a seemingly useless project on my resume possibly do more harm than good to my career opportunities?

Answer 1

Unless you can think of a way of making money off the code, share it as open source. You can upload it to something like sourceforge

The code will have your name beside it and if nothing else the world will know you made something.

It would be good to put on a resume also, it shows you independently found a problem and developed a solution. This demonstrates the kind of ambition a recruiter is looking for in most development jobs.

Answer 2

Yes. .

Answer 3

If this is a useful piece of code then you should post it in the proper website for open source projects.

As for your resume, not everything you have done should be written there, in general you need to adjust the CV to company receiving them.

But in general, many open source projects are small utilities, I don't think a recruiter will look badly on such a thing, and if he does - you probably don't to work with him.

Answer 4

You could make your project open source as long as the person you are making it for gives you their permission (assuming they might be paying you for it). If not, then I would say that it wouldn't hurt to make it open source. Other people could view the code and suggest improvements, fix bugs, help code, etc. It would also show initiative working outside of just the normal "work day". People like to see that you are active outside of work in the programming community (don't forget to mention you participate on SO). Landing a job after school is not all about who has the most experience. Your internship will definitely help and maybe making this project you are working on open source will be another interesting thing to talk about in interviews.

Answer 5

Yes, put it up on Google Code. If one other person ever needs something like that they'll be REALLY happy if they find it, and you can also list it on your resume if you need some additional information. Personally, I've been in interviews where I have been asked if I created any open source projects, or contributed to any existing ones.

Answer 6

open source projects will always gives a good values for your resume ,if you are a fresher or experienced candidate . so it will help for a good career opportunities.

You can publish it on google code ,codeplex etc .

All the best

Answer 7

If you want to see it as succesful project you should check for :

1) Usability of your project

2) As soon you will go for internship , Will you able to spend time on this project

3) What is maturity of you current developmen

Answer 8

It depends on three key factors:

1. Is the code in a fit state for use by others?
2. Will others use it? and
3. Will you maintain it?

(3) is an often neglected area of open source. Some use open source essentially as a dumping ground for mediocre code (no judgement intended regarding your code). Open source without a maintainer is just more dead buggy code.

Answer 9

In general, an effective approach to a known problem is of immediate use - just because you chose an obscure detail is no reason not to make your work available for interview purposes. Most open source license impinge a compulsory exposure clause, Creative Commons has brought the idea of Open Source several full steps ahead - I like the idea of posting the code on Google code, you can determine your own wishes for the code ( no ? ) thus just make that statement in the comments ... then post it.

An internet friend of mine who taught at GMU and holds degrees in the field as well as working a full career in the field will tell you - the interviewers are rarely accomplished programmers, academic or otherwise. Most of their questions are of the 'trick' style, intended to get them through the interview. Your decision what to do with the code should focus on making your work and the design decisions available to someone who actually knows how to program somewhat. Thus, comment the design decisions - show at least enough of the code such that if it ever is inspected potential employers can see what your level of expertise is. Don't hide here, if you are level three of seven - they need to know that.

The strange and hidden factor is that people who make licenses necessary won't bother to read the license. Note also the root word of license is lice. See Snake Oil FAQ for a discussion of the matter. If you have not worked in a commercial shop, I suggest your code has no proprietary issues. Further, note that much of actual employment consists of "get my friend a job" - it is rare that someone who finished academic training gets hired directly consequent to deep, accomplished fluency in trade craft. I have a commercial mailing house that could pump 10,000 resume's a day, so what's the point? Self publishing is an interesting approach, now with the net a pubescent novice can compete with Planetary Powerhouses - see http://www.tinaja.com/glib/casagpat.pdf to correctly identify where your publishing decision actually splits.

Mostly, focus on not wasting thousands of dollars on the resume thing.

Answer 10

I'd recommend to consider not only the reputation you'd get from such a publishing of your source, but also open source projects need someone willing to maintain the project. Are you willing to maintain it? That means you are willing to listen to bug suggestions, and fixes, incorporate them into the program and furnish new releases from time to time.

If you are not willing to maintain a community (you might be surprised how even obscure communities appreciate such efforts), I'd rather recommend to publish it in a blog and state upfront that you are "giving it away" but will not maintain the project.

This kind of decision would probably also influence your choice of license.