<?xml version="1.0" encoding="UTF-8"?> 
<?xml-stylesheet href="https://dev.horde.org/themes/horde//default/feed-rss.xsl" type="text/xsl"?> 
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> 
 <channel> 
  <title>some copyright and license statements are missing</title> 
  <pubDate>Thu, 09 Apr 2026 14:31:08 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/6661</link> 
  <atom:link rel="self" type="application/rss+xml" title="some copyright and license statements are missing" href="https://bugs.horde.org/ticket/6661/rss" /> 
  <description>some copyright and license statements are missing</description> 
 
   
   
  <item> 
   <title>Hi,



While creating the copyright file for debian packagin</title> 
   <description>Hi,



While creating the copyright file for debian packaging, I found that horde miss some info.



According to http://www.gnu.org/licenses/gpl-howto.html :

&lt;&lt;&lt;

Whichever license you plan to use, the process involves adding two elements to **each** source file of your program: a copyright notice (such as Copyright 1999 Terry Jones), and a statement of copying permission, saying that the program is distributed under the terms of the GNU General Public License (or the Lesser GPL).

&gt;&gt;&gt;



this is not the case

This probably also apply to other apps.</description> 
   <pubDate>Tue, 29 Apr 2008 19:08:56 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6661#t44988</link> 
  </item> 
   
  <item> 
   <title>Attached is some files without copyright notice. Some are th</title> 
   <description>Attached is some files without copyright notice. Some are third-party tools (./services/editor/*, scriptaculous) and some are not.



I can give some help if needed</description> 
   <pubDate>Tue, 29 Apr 2008 19:11:48 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6661#t44989</link> 
  </item> 
   
  <item> 
   <title>- we should not add copyrights to third-party tools

- we sh</title> 
   <description>- we should not add copyrights to third-party tools

- we shouldn&#039;t add copyrights to the compressed javascript files

- I&#039;m not sure about putting them in SQL scripts

- I don&#039;t think we should put copyright notices in .htaccess files

- definitely shouldn&#039;t be any notices in favicon.ico files (those are graphics)

- the themed_graphics files are empty placeholders, they don&#039;t need copyright

- I&#039;m not sure about the help.xml and .po files

- I&#039;m against putting copyright notices into every template file



A patch for everything else would be great, along with thoughts on these - thanks.</description> 
   <pubDate>Thu, 01 May 2008 21:06:07 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6661#t45050</link> 
  </item> 
   
  <item> 
   <title>Attached an updated version. Ordered by sections. 



I can </title> 
   <description>Attached an updated version. Ordered by sections. 



I can provide a patch. But I need information (which sections, whose copyright ?)



Also note that (c) doesn&#039;t have any legal value. &#039;&#039;Copyright&#039;&#039; or © should be used.



TOC:

* PHP FILES: copyright is probably needed

* JAVASCRIPT: copyright is probably needed

* PHP/CSS THEME FILES: copyright is probably needed

* VARIOUS SCRIPTS: copyright is probably needed

* SQL: ?

* CONFIG: copyright is probably not needed

* DOC: copyright is probably not needed

* L10N (po): copyright is probably needed

* L10N (XML): ?

* TEMPLATES: ?

* HTACCESS: no copyright needed



Other files have strange copyright (missing copyright holder, year, ...):

./po/uk_UA.po:# Copyright (C)

./po/km_KH.po:# Copyright (C) YEAR Horde Project

./po/fi_FI.po:# Copyright (C)

./po/horde.pot:# Copyright (C) YEAR Horde Project

./po/pt_BR.po:# Copyright (C) YEAR Horde Project.

./po/ru_RU.po:# Copyright (C)



Also, all &quot;Copyright (C) AAAA Horde Project&quot; should probably replaced by &quot;Copyright AAAA The Horde Project (http://www.horde.org/)&quot; (this is cosmetic)</description> 
   <pubDate>Sat, 03 May 2008 10:52:57 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6661#t45153</link> 
  </item> 
   
  <item> 
   <title>Attached patch for the cosmetic stuff. Applicable to the hor</title> 
   <description>Attached patch for the cosmetic stuff. Applicable to the horde module.</description> 
   <pubDate>Sat, 03 May 2008 11:46:34 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6661#t45154</link> 
  </item> 
   
  <item> 
   <title>From Michael Slusarz:



This has been on my mind for awhile</title> 
   <description>From Michael Slusarz:



This has been on my mind for awhile and thought I&#039;d get it out there - for the various 3rd party apps we distribute along with our code (right now, all I can think of is xinha, fckeditor, tinymce, scriptaculous, and prototype), we should probably have a wiki page  

tracking their licenses.  For those under the GPL/LGPL/MPL (fckeditor), I don&#039;t believe we are distributing the full source distribution so we should probably be keeping a local copy of the base distribution in case anyone ever asks us for the source code.  I think xinha is BSD so we just need to have the license in the distribution). scriptaculous is MIT-like, so we just need to make sure we distribute scriptaculous.js with all apps using it (we do this). prototype is MIT-like but doesn&#039;t require copyright notices so technically, with the above changes, we don&#039;t need to do anything.</description> 
   <pubDate>Sun, 04 May 2008 04:11:23 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6661#t45155</link> 
  </item> 
   
  <item> 
   <title>There&#039;s also lib/Horde/MIME/Viewer/ooo/* which is LGPL2.1 or</title> 
   <description>There&#039;s also lib/Horde/MIME/Viewer/ooo/* which is LGPL2.1 or SISL. Copyright 2000-2002 by Sun Microsystems, Inc.</description> 
   <pubDate>Sun, 04 May 2008 16:14:47 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6661#t45160</link> 
  </item> 
   
  <item> 
   <title>http://horde.org/horde/docs/?f=CODING_STANDARDS.html#header-</title> 
   <description>http://horde.org/horde/docs/?f=CODING_STANDARDS.html#header-comment-blocks describes the formatting. Copyrights should be to The Horde Project (http://www.horde.org/)</description> 
   <pubDate>Mon, 05 May 2008 04:33:45 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6661#t45164</link> 
  </item> 
   
  <item> 
   <title>Any updated patch coming?</title> 
   <description>Any updated patch coming?</description> 
   <pubDate>Fri, 23 May 2008 19:21:21 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6661#t45506</link> 
  </item> 
   
  <item> 
   <title>horde.diff was fine and it has been applied:

http://lists.h</title> 
   <description>horde.diff was fine and it has been applied:

http://lists.horde.org/archives/cvs/Week-of-Mon-20080519/078782.html</description> 
   <pubDate>Fri, 23 May 2008 19:25:17 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6661#t45509</link> 
  </item> 
   
  <item> 
   <title>Hi,



I can&#039;t provide a patch, I don&#039;t know who owns copyri</title> 
   <description>Hi,



I can&#039;t provide a patch, I don&#039;t know who owns copyright.



</description> 
   <pubDate>Sat, 24 May 2008 16:35:53 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6661#t45535</link> 
  </item> 
   
  <item> 
   <title>&gt; Copyrights should be to The Horde Project (http://www.hord</title> 
   <description>&gt; Copyrights should be to The Horde Project (http://www.horde.org/)



excepting external code of course.</description> 
   <pubDate>Sat, 24 May 2008 18:38:49 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6661#t45553</link> 
  </item> 
   
  <item> 
   <title>Meanwhile, it&#039;s Horde LLC.

Suse legal team had some revie</title> 
   <description>Meanwhile, it&#039;s Horde LLC.

Suse legal team had some review of horde 4 package licenses and copyrights, a lot of issues have been raised on the mailing list and after that there have been a lot of fixes.

I think we can close this now.</description> 
   <pubDate>Sat, 17 Sep 2011 07:21:08 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6661#t67553</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
