2

In order to fulfill license obligations (in some cases) one must display the copyright information (when not delivering source code).

Should one display (in GUI or IFU) the copyright information of each file or only the one in the main COPYING file ?

Clarification: I am not referring to how to add the Copyright information to the source code. From this point of view, @John has a very good point.

  • 3
    Which open source license are you asking about? The answer depends on which one. – Brandin Sep 20 '18 at 16:12
  • @Brandin since the op explicitly refers to the COPYING file, I'd infer we're talking gpl. – John Forkosh Sep 21 '18 at 6:26
1

Some copyright licenses contain the requirement that you must reproduce the copyright license information in the GUI and/or documentation of your binary distribution. The idea behind such a requirement is that the end-user gets informed about the rights they have with regards to (parts of) the software they receive.

When using third-party software in your product, you usually drag it in in larger components, like "the Linux kernel", "the foo library" or "the bar package". It is common to reproduce the license information also on that level of granularity. And even then, if multiple third-party parts use the exact same license, those parts are often grouped such that the license text is only reproduced once.

0

Each file, for sure -- even if it's not "for sure", legally, it can't hurt. Every module of my gpl'ed programs always begins with an elaborate header comment block, summarizing the gpl and referring to COPYING in the zip file distribution. I just cut-and-paste it from one module into a new module, and then edit as required. Here's a typical example which you can use as a template, if you like. And note the eco case# -- I always officially register copyrights, and would encourage you to do the same...

/****************************************************************************
 *
 * Copyright(c) 2014-2017, John Forkosh Associates, Inc. All rights reserved.
 *   ( eco.copyright.gov -- Case# 1-5321264531   Date opened: 6/5/2017 )
 *           http://www.forkosh.com   mailto: john@forkosh.com
 * --------------------------------------------------------------------------
 * This file, gifscroll.c, is part of gifscroll, which is free software.
 * You may redistribute and/or modify gifscroll under the terms of the
 * GNU General Public License, version 3 or later, as published by the
 * Free Software Foundation.
 *      gifscroll is distributed in the hope that it will be useful, but
 * WITHOUT ANY WARRANTY, not even the implied warranty of MERCHANTABILITY.
 * See the GNU General Public License for specific details.
 *      By using gifscroll, you warrant that you have read, understood
 * and agreed to these terms and conditions, and that you possess the legal
 * right and ability to enter into this agreement and to use gifscroll
 * in accordance with it.
 *      Your gifscroll.zip distribution file should contain the file
 * COPYING, an ascii text copy of the GNU General Public License,
 * version 3. If not, point your browser to  http://www.gnu.org/licenses/
 * or write to the Free Software Foundation, Inc., 59 Temple Place,
 * Suite 330,  Boston, MA 02111-1307 USA.
 * --------------------------------------------------------------------------
 *
 * Purpose:   o gifscroll generates an animated gif displaying a message
 *              like a scrolling led sign in store windows.
 *              See the "Notes:" below, and also
 *                http://www.forkosh.com/gifscroll.html
 *              for further details about gifscroll.
 *
 * Source:    o gifscroll.c
 *
 * Functions: o The following "table of contents" lists each function
 *              comprising gifscroll in the order it appears in this file.
 *              See individual function entry points for specific comments
 *              about purpose, calling sequence, side effects, etc.
 *              =============================================================
 *              +---
 *              | gifscroll functions
 *              +-----------------------
 *              main(argc,argv)                      cgi driver for gifscroll
 *              rasterize_this(msgorpbm,type)   rasterize message or pbm file
 *              new_raster(width,height)    raster allocation and constructor
 *              delete_raster(rp)                       destructor for raster
 *              etc, etc
 *
 * --------------------------------------------------------------------------
 *
 * Notes:     o gifscroll() presently runs on Unix and Windows
 *            o etc, etc
 *
 * --------------------------------------------------------------------------
 * Revision History:
 * 03/23/14     J.Forkosh       Installation.
 * 10/04/17     J.Forkosh       Most recent revision
 * See  http://www.forkosh.com/gifscrollchangelog.html  for further details.
 *
 ***************************************************************************/
  • 1
    Thank you for your answer but I am more interested in how to fulfil the license obligations. I guess my question is not very clear. – ossx Sep 21 '18 at 7:52
  • “By using gifscroll”... That paragraph goes against the GPL :-(. (Specifically, section 9 of GPL v3.) – Stephen Kitt Sep 22 '18 at 23:58
  • @StephenKitt Thanks for the remark. It raised a question, at least for me, elaborated at opensource.stackexchange.com/questions/7363/… – John Forkosh Sep 23 '18 at 8:48

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

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