I've written a small program that I would like to release

how to make a .deb and push it to ubuntu - the post

also, what is the program about

The code is copyrighted as soon as you write it. Anyone telling you that you need to pay for a copyright is either mistaken or trying to scam you If you want to share it, youd want to put some sort of license on it. There are a bunch of different kinds of license you can use as a template deciding what you want. (Distributing your software with a license doesn't cost anything either.)

github.com

Just release it closed source there.

>>60046162
Just put the source on github with the precompiled binary (Then look into making hashes to verify the binaries)
The GPL license is the most free license

put it on github

>I know people put their stuff on github, open source, but at least for the moment I don't really want to do that.

ok, then no one will download it unless it's really useful and fills a niche

>It's not something that I think very many people would use or care about

ok, then no one will download it

The project was something i did in c# after I got bored with my programming classes' assignments. I have made some semi-useful things before, but none of them had much of a GUI to speak of. I learned a lot about making windows applications doing it, even though it's still fairly simple. Did I hear something recently about .net framework being written for linux?

The program is a Debt calculator, much like the billions of loan calculators out there. But the main point of mine is that you can enter different debts and have it rollover monthly payments of a debt when it's paid off into the next debt in the order you set. It calculates time to pay off each debt, and total interest paid, and so you can change the payment amounts, and the order/amount of payments to rollover and see which payoff strategy is best for your situation.

>>60046225
>>60046228
Thanks, i guess i didn't know you could do that. I've never used github before, I've just always heard it referred to in relation to it's massive open source community, which i would love to contribute to but I'm not sure I have enough knowledge to really help much.

>>60046234
Yeah, I know. I would just generally feel like a shmuck if i released something and someone else found a way to make money off of it. Not so much with this project but going forward I was curious how people release things. Most the software I've used had enough visible people who've used and talked about the program I could be fairly certain it was safe.

>go to github.com
>make an account
>upload your code
>make it gpl II or

>>60046162
You already own the copyright to everything you "create", in this case the computer code. If you want to show your sincerity that your code is trustworthy, particularly as a literal-who, the best way to go about it is to go open source. However, going open source =/= abandoning your rights. You can choose a license that'll retain your copyright, effectively preventing others from taking your code and forking it.

Even GPL works for this. Sure, other people can fork it, but they can't relicense your source code without your permission or use it in closed source software without violating the license, while you, as the original copyright holder, retains the right to relicense the software whenever you want (though the GPL'd versions of the software would still be redistributable under the license...).

But generally speaking, I don't think you have anything to fear from doing this.

>>60046296
>I would just generally feel like a shmuck if i released something and someone else found a way to make money off of it.
If someone uses your source code in proprietary, closed-source software without your permission it's possible to figure this out by analyzing the behaviour of the software on a low level. And if they don't have your permission (granted either by yourself personally, or via a permissive license), you could seek legal action against them if that were the case.