23

I need advice from my coding elders:

A bit of background:
So I'm a highschooler and I have made a program for my school called Passport. It's being implemented as we speak.
Take a look:
https://github.com/poster983/...

It is basically a program that helps to manage and distribute digital Library passes. (We used to go through stacks of paper passes).

It was sorta my first major project, so it is probably filled with bugs and other security vulnerabilities. Just FYI.

_______

So a guy approached me tonight and was acting very interested in what I did. (it's literally a fancy database). He wanted my to unopen-source it and sell it to a company. (Probably his or a friend of him). I politely declined because I feel this program is
1. Not up to my standards; so if I was to sell it, I would rewrite it is something more modern like node, or Python.
2. I love open source.
3. A way for my to give back to my school and maybe help other schools.

After hearing that, he started calling opensourse a failure, and he said that I will one day be wise and write code for money (which I know I will, just I want to sell GOOD code).

My question is, how do I deal with people who want my to dich the opensourse model in the future?

Comments
  • 3
    Open source obviously has its draw backs since people can easily see the back-end and find vulnerabilities in your system. But honestly you don't have to do anything.... If you want something open sourced then just do it. If its software that is going to a client and they don't want it to be available for others to use then don't open source it. If its a side project and you want it Open sourced then.... open source it. There really isnt anything to this as its your code until someone buys it privately.
  • 5
    Open source has its place, but so do proprietary investigations. If what you're writing isn't super novel, open source it. If your project is novel, sell it.

    There's a chance that the guy thought that even though your work isn't technologically novel, he may have thought it was a novel business niche.

    Remember that it can be almost impossible to make money by selling open source software, though grants are often available.

    Knowing what kinds of projects should and shouldn't be open source (and why) is probably your best way to defend your convictions.
  • 4
    I'm not a lawyer, but... Even if the project is closed with the next release... Surely any code already published online is still legally open source under the licence it was originally published under?

    I mean, you can't retroactively apply a licence to something, can you?
  • 7
    "My question is, how do I deal with people who want my to dich the opensourse model in the future?"

    There will also be people who will want you to open source your future closed source commercial software. And there will be people who think you vote for the wrong party, eat the wrong food or have the wrong hairdo.

    Tell them to write down their opinions in a text file and send it to /dev/null.
  • 3
    @nicnaknic I think that open source is awesome as the code can undergo much more scrutiny for security vulnerabilities.
  • 0
    Thanks everyone! I'll take all this advice.

    I would never sell such a potentially broken program.
  • 0
    I write more open source code at my job than I did when I was in school. Follow your heart, always.
Add Comment