from Hacker News

Ask HN: Should I open-source my code?

by endriju on 9/10/14, 4:02 PM with 18 comments

• by codezero on 9/10/14, 4:15 PM

  Whether anyone wants/is interested in the code, open sourcing it is effectively the modern bullet point on your resume. Open source, it, write some good documentation and let it run wild if it's desired, but if it's not, it will still look good as a personal and technical achievement.

  Good luck at globocorp! :)

• by b0ti on 9/10/14, 6:55 PM

  If you open source it, pick a license that's more restrictive (e.g. AGPL). This leaves a chance for you to get lucky and sell it to a company who wants it to use it as closed source so that you can buy a few beers. Otherwise they will just take it and use it without a single thank you. Probably I'll get downvoted for this but IMO releasing work under the BSD, Apache or a copyleft license that you created on your free time is like playing charity for large corporations.

• by jacquesm on 9/10/14, 4:49 PM

  I don't understand the 'I was hoping for it to become a product with a functioning business model, but i was struggling to come up with one.'

  On the site it says:

  > there is no fee and it’s completely free.

  So why not change that? Set up a 3 tier 'buy' page and charge $0.15 per merge if you buy 10 merges, $0.12 if you buy 50 and $0.10 if you buy a 100 pack.

  That way you can figure out if people are actually willing to pay for this service.

  Open sourcing it is great but that still requires someone to run it.

  Just try making it a paid service first, if that does not work you can always re-consider and make it open source after all.

• by endriju on 9/10/14, 7:50 PM

  Thanks everyone for the valuable feedback, i appreciate it! The option that i am most likely to go with is to open source and document the interesting parts of the code (parsing sheets, merging data) and keep the site as an example use case for the OS projects.

• by wilsonfiifi on 9/12/14, 4:35 PM

  Managing an open source project involves a bit of work and time on your behalf especially if you want to build a following. You have to keep everything up to date: documentation, wiki, code, issues etc… And if you want contributors then you have to make sure your code is understandable and properly organised. (and I should be following my own advice!)

  Once you put your code out there you must also be ready for criticism: some good and some awful. But from my experience it's the best thing you can do as a developer because it will definitely help you grow and force you to code better (hopefully).

  I think I was very lucky because when I posted my first open source project on HN (https://github.com/johnwilson/bytengine) it was a positive experience and when you get that kind of feedback you really don't want to "let the community down" by slacking on your commits and other project upkeep duties (which I have).

  So I think you basically have to ask yourself if you just want a public code archive that you can point people to once in a while and say hey I did that or if you want to build a community around your project and turn it into something great!

  Best of luck and thanks for posting this, it has given me a little kick in the butt!

• by valarauca1 on 9/10/14, 4:06 PM

  There's really no reason to not open source it. Unless you just want to burn your code and your work. Throw it on github, and maybe somebody will find a use for it.

  I'd say I'd like to play around with it. But merging data files doesn't work over a web interface :\ since then I'd need to upload like 4 GB lol.

• by buckbova on 9/10/14, 4:33 PM

  If there's a piece of this that you think'd be especially useful, like the merging of data, then it'd be nice to pull that out and open source just this piece.

  But if you don't have the time or want to expend the effort, I agree with what some others have posted here. Open source it with some decent documentation and screenshots. It could serve you well down the road.

• by pnathan on 9/10/14, 4:38 PM

  Interesting service. Spreadsheet merging isn't the easiest thing ever. :-)

  I am a firm proponent of libre software and encourage you to open source it under a strong copyleft license. If it is really useful, it will be picked up someday and looked at. If not useful, then it's not a great loss to you.

• by programminggeek on 9/10/14, 4:11 PM

  There is certainly value in open sourcing a project, just for the attention it can get you. I don't know if it's going to change much for what you are doing, but you never know.

• by anonymous_ on 9/10/14, 4:46 PM

  I'm receiving code 503 at http://app.exmerg.com/

• by wehadfun on 9/10/14, 4:36 PM

  If you can't make money on it then open source it if you have time

• by angersock on 9/10/14, 4:06 PM

  Easiest way to find out is to open-source it.