I just read some artical about publishing software and I am personally developing some random metero application at the moment.

The artical were suggesting the software should have a publisher website.

But what I have to put down in the publisher website to keep my copyright?

Is it simply really just "Designed/Developed @ 2012 By King Chan" at the bottom of the site and software and is enough?

Or do I have to even write a long paragraph of license/agreement said the user who download/use the software cannot copy the icon/functionality etc?

(The Apple and Samsung things get me worry about CopyRight now....)


You almost certainly own the copyright on your code (1)

You don't need to do anything to claim that - although putting an explicit claim in the code makes it clearer.

A license is there to control what other people can do with your code (MIT requires them to mention you, GPL requires that they also make their code GPL etc). If you don't want to put any extra restrictions on users of your code then you don't need to do anything.

1 - unless you are in some weird country that isn't in the Berne convention. Or if your employer claims copyright on anything you do and you live somewhere that would uphold this.

|improve this answer|||||
  • So I don't to register anything specially on any site too? – King Chan Nov 3 '12 at 21:46
  • No - you CAN register things with the US copyright office which gives you advantages in court in proving that you had the idea first. But there is no need to do anything – Martin Beckett Nov 3 '12 at 22:43
  • I am in Canada, is it depends on where I live? Or where the place I sell to? Just want to know beforehand. – King Chan Nov 3 '12 at 23:13
  • Not for most civilized countries (including Canada) see en.wikipedia.org/wiki/… – Martin Beckett Nov 4 '12 at 0:18

Copyright & licensing are separate issues. Copyright prevents unauthorized duplication of your software/website. By default, nobody can copy and use your software because of copyright.

A license defines the terms under which you allow people to use the software. It also defines & limits what your obligations to the user are. Generally there's language in there to stop them from suing you if the software breaks.

They're both important. I suggest getting a lawyer if you're releasing it commercially - if you're releasing it for free, I strongly suggest going with a standard open source license.

|improve this answer|||||
  • Nice explaination, thanks! +1, but I am just going to release some small application to try out for fun. :) – King Chan Nov 3 '12 at 23:14

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.