tags:

views:

370

answers:

11

Is putting copyright notice in the 'about' window enough? I know that a software program is copyrighted by default, but it's recommended to add a notice somewhere anyway, well as far as i know.

+3  A: 

IANAL, but clearly any notice about the copyright (including one in 'about') should be enough, since no notice at all is also technically enough (having a notice is of course better than none, as it makes it easier for interested parties to get in touch with the copyright owner and try to negotiate licenses, for example).

Alex Martelli
+3  A: 

If you are distributing software you should not only copyright it but also indicate the license under which it is being distributed. See here for more information.

Vinay Sajip
I just want to put in on internet, so anyone can download the software, not sure why i have to use license, i though i only have to copyright it, but i'm not really familiar with those things so maybe i'm wrong...
Copyright is your declaration that you wrote the code in question and are perpetually licensed to use it. License is how you grant others the right to this code. WikiAnswers has a decent explanation: http://wiki.answers.com/Q/What_is_the_difference_between_license_and_copyright_Doesnt_license_come_with_copyright
Chris Boran
+2  A: 

Every place I've ever worked adds a header to each source file declaring a boiler plate copyright with the years in which the software files were modified, plus a license.txt file in the software declaring licensing and copyright terms. The UI 'About' box has usually been a minor afterthought. At a minimum I'd do the source file declaration and the license.txt file.

Chris Boran
A: 

IANAL but as long as there is a copyright notice you should be good. The notice just needs to be enough to prove the would-be-pirate knew/should have known it was under copyright.

Paul
A: 

In FOSS world the conventional way is to distribute the license along with the program/source code and add a short copyright notice at the top of every source file.

maksymko
+3  A: 

This is not the place to be asking legal question. Seriously, see a lawyer. My employer (a big one) puts copyright messages (very specific formats) in:

  • all documentation.
  • all source files.
  • all re-distributable files (even if liberally licenced).
  • all object files.
  • all executables.
  • just about anything else that we produce that even has a snowflake's hope in Hades of being seen by non-employees.

They also register their code with the Library of Congress. This isn't necessary for copyright protection under the Berne convention (actually none of those steps above are) but it adds extra protection in the US since it's prima facie evidence that you hold the copyright validly (harder for the other guy to disprove your claim).

paxdiablo
Pax, I think perhaps you meant "employer" when you said "employee".
Vinay Sajip
A: 

As many other have already said, copyright isn't enough. If you sell me your copyrighted software, I will probably have more rights to it that you imagine. That is why software is licensed.

The only thing you need to do to copywrite something is to avoid writing "This is released to the public domain". I believe you are correct when you say stuff is authomatically copyrighted even if you don't add any language to that effect.

MatthewMartin
+7  A: 

You automatically get a copyright on anything you create. You do not need to put a notice on the software or register it. However, adding a notice is a good way to remind users that the software is copyrighted.

Copyright challenges are more likely to hold up in court if you register your work with the US Copyright Office (if you live in the US).

bestattendance
+2  A: 
  • Make sure you copyright your source code. This is where it all begins
    // *********************************************************************
    // [DCOM Productions]
    // [Copyright (C) DCOM Productions All rights reserved.]
    // *********************************************************************
  • Sign all your assemblies with a Strong Named Key (Digital Signature)
  • Provide copyright text both reviewed on installation, as well as copyright.rtf/txt
  • Provide an 'about dialog' which displays simplified copyright information about your application
  • Logo your application, provide your company logo on a splash screen (only if it actually loads something!) or again your 'about dialog'
David Anderson
My application is not open source, but thanks anyway.
Doesn't have anything to do with whether it is open or closed source.
David Anderson
A: 

So, if i want to apply license to my application what should i do? I mean saying "you can blah blah" and "you can't blah blah" has no legal meaning(you know what i mean), right? See for example part of the uTorrent license:

"These BitTorrent, Inc. terms will be governed by and construed in accordance with the laws of California, USA, without regard to conflicts of law rules. The United Nations Convention on Contracts for the International Sale of Goods will not apply. The failure by either party to enforce any provision will not constitute a waiver..."

Do i have to use something like the text in bold? Btw, i'm not an US citizen. And yeah, i checked all those sites in internet that covers this subject and some of them are very vague or complicated...

+1  A: 

Pick a license, any license!

Bastien Léonard
+100, dealing with an open-source project with no license is unpleasant to say the least.
romkyns