To avoid future problems concerning changing licensing or copyrights, all
code contributions more than a hand full of lines must be in the Public
-Domain or have the copyright assigned to Kern Sibbald as in the current
+Domain or have the copyright transferred to the Free Software Foundation
+Europe e.V. with a Fiduciary License Agreement (FLA).
+as in the current
code. Note, prior to November 2004, the code was copyrighted by Kern
-Sibbald and John Walker. When some sort of Bacula entity is created, this
-this copyright will be transferred to that entity. Hopefully this will
-happen by Q1-2007.
+Sibbald and John Walker. After November 2004, the code was copyrighted
+by Kern Sibbald, then on the 15th of November 2006, the copyright was
+transferred to the Free Software Foundation Europe e.V.
Your name should be clearly indicated as the author of the code, and you
must be extremely careful not to violate any copyrights or use other
people's code without acknowledging it. The purpose of this requirement is
to avoid future copyright, patent, or intellectual property problems. To
-understand on possible source of future problems, please examine the
+understand the possible source of future problems, please examine the
difficulties Mozilla is (was?) having finding previous contributors at
\elink{ http://www.mozilla.org/MPL/missing.html}
{http://www.mozilla.org/MPL/missing.html}. The other important issue is to
avoid copyright, patent, or intellectual property violations as are currently
(May 2003) being claimed by SCO against IBM.
-Although the copyright will be held by Kern, each developer is expected to
+Although the copyright will be held by the Free Software Foundation Europe
+e.V., each developer is expected to
indicate that he wrote and/or modified a particular module (or file) and
any other sources. The copyright assignment may seem a bit unusual, but in
-reality, it is not. Most large projects require this. In fact, the
-paperwork associated with making contributions to the Free Software
-Foundation, was for me unsurmountable, so hopefully the rather
-simplified procedure we have will not create any difficulties for
-you.
+reality, it is not. Most large projects require this.
If you have any doubts about this, please don't hesitate to ask. The
objective is to assure the long term servival of the Bacula project.
Items not needing a copyright assignment are: most small changes,
-enhancements, or bug fixes of 5-10 lines of code.
+enhancements, or bug fixes of 5-10 lines of code, which amount to
+less than 20% of any particular file.
-\subsubsection*{Copyright Assignment}
+\subsubsection*{Copyright Assignment -- Fiduciary License Agreement}
\index{Copyright Assignment}
\index{Assignment!Copyright}
-\addcontentsline{toc}{subsubsection}{Copyright Assignment}
+\addcontentsline{toc}{subsubsection}{Copyright Assignment -- Fiduciary License Agreement}
-Since this is not a commercial enterprise, and I prefer to believe in
+Since this is not a commercial enterprise, and we prefer to believe in
everyone's good faith, previously developers could assign the copyright by
explicitly acknowledging that they do so in their first submission. This
was sufficient if the developer is independent, or an employee of a
not-for-profit organization or a university. However, in an effort to
ensure that the Bacula code is really clean, beginning in August 2006, all
previous and future developers with CVS access will be asked to submit a
-copyright assignment.
+copyright assignment (or Fiduciary License Agreement -- FLA).
-Any developer who wants to contribute and is employed by a company must get
-a copyright assignment from his employer. This is to avoid
+Any developer who wants to contribute and is employed by a company should
+get a copyright assignment from his employer. This is because in many
+counties, all work that an employee does whether on company time or in the
+employee's free time is considered to be Intellectual Property of the
+company. Obtaining a signed FLA from the company will avoid
misunderstandings between the employee, the company, and the Bacula
project. A good number of companies have already followed this procedure.
-\subsubsection*{Personal Copyright Assignment Statement}
-\index{Copyright!Personal Assignment}
-\index{Personal Copyright Assignment Statement}
-\addcontentsline{toc}{subsubsection}{Personal Copyright Assignment Statement}
+The Fiduciary License Agreement is posted on the Bacula web site at:
+\elink{http://www.bacula.org/FLA-bacula.en.pdf}{http://www.bacula.org/FLA-bacula.en.pdf}
-The following statement must be filled out by each non-employed developer
-(please see below for developer's that are employed), signed, and mailed
-to my address (please ask me for my address and I will email it -- I'd prefer
-not to include it here).
+It should be filled out, then sent to:
-\footnotesize
\begin{verbatim}
-Copyright release and transfer statement.
- From: <your name>
-
- To: Kern Sibbald
- Concerning: Copyright release and transfer
-
- The undersigned hereby certifies that he/she is independent
- and wishes to develop
- code for and contribute code to the Bacula project for an
- undetermined period of time. The copyright as well as all
- other rights to and interests in such contributed code are
- hereby transferred to Kern Sibbald.
-
- Signed in <City, Country> on <Date>:
-
- <Name of Person>
-
+ Free Software Foundation Europe
+ Freedom Task Force
+ Sumatrastrasse 25
+ 8006 Zürich
+ Switzerland
\end{verbatim}
-\normalsize
-
-This release/transfer statement must be sent to:
-Kern Sibbald
-Address-to-be-given
-
-If you wish to retain the full rights to use the software you
-have contributed in different projects, this is not a problem. Just
-request a perpetual non-exclusive license before sending in your
-copyright assignment. See the file <bacula-source>/src/lib/tls.c
-for an example of such a license.
-
-
-\subsubsection*{Corporate Copyright Assignment Statement}
-\index{Copyright!Corporate Assignment}
-\index{Corporate Copyright Assignment Statement}
-\addcontentsline{toc}{subsubsection}{Corporate Copyright Assignment Statement}
-
-The following statement must be filled out by the employer, signed, and
-mailed to my address (please ask me for my address and I will email it --
-I'd prefer not to include it here).
-
-\footnotesize
-\begin{verbatim}
-Copyright release and transfer statement.
- <On company letter head>
-
- To: Kern Sibbald
- Concerning: Copyright release and transfer
-
- <Company, Inc> is hereby agrees that <names-of-developers> and
- other employees of <Company, Inc> are authorized to develop
- code for and contribute code to the Bacula project for an
- undetermined period of time. The copyright as well as all
- other rights to and interests in such contributed code are
- hereby transferred to Kern Sibbald.
-
- Signed in <City, Country> on <Date>:
-
- <Name of Person>, <Position in Company, Inc>
-
-\end{verbatim}
-\normalsize
-
-This release/transfer statement must be sent to:
-Kern Sibbald
-Address-to-be-given
-If you wish to retain the full rights to use the software you
-have contributed in different projects, this is not a problem. Just
-request a perpetual non-exclusive license before sending in your
-copyright assignment. See the file <bacula-source>/src/lib/tls.c
-for an example of such a license.
+Please note that the above address is different from the officially
+registered office mentioned in the document. When you send in such a
+complete document, please notify me: kern at sibbald dot com.
\subsection*{Basic CVS Usage}
...), his continuing support of Bacula users. He also wrote the PostgreSQL
driver for Bacula and has been a big help in correcting the SQL.
-Thanks to Phil Stracchino for writing the gnome-console {\bf ConsoleFont}
-configuration command, all the suggestions he has made, and his continuing
-suppport of Bacula users.
-
Thanks to multiple other Bacula Packagers who make and release packages for
different platforms for Bacula.
Thanks to Christopher Hull for developing the native Win32 Bacula emulation
code and for contributing it to the Bacula project.
-Thanks to Nicolas Boichat for writing wx-console and the bacula-tray-monitor.
-These are very nice GUI additions to Bacula.
-
Thanks to Thorsten Engel for his excellent knowledge of Win32 systems, and
for making the Win32 File daemon Unicode compatible, as well as making
the Win32 File daemon interface to Microsoft's Volume Shadow Copy (VSS).
These two are big pluses for Bacula!
-Thanks to Nic Bellamy for providing the bacula-dir.conf file that he uses to
-implement daily tape rotation using multiple Pools.
-
-Thanks also to Jo Simoens for finding and correcting so many typos and
-other problems with the manual.
-
Thanks to Arno Lehmann for his excellent and infatigable help and advice
to users.
Thanks to all the Bacula users, especially those of you who have contributed
ideas, bug reports, patches, and new features.
+Thanks to Nicolas Boichat for writing wx-console and the bacula-tray-monitor.
+These are very nice GUI additions to Bacula.
+
The original variable expansion code used in the LabelFormat comes from the
Open Source Software Project (www.ossp.org). It has been adapted and extended
-for use in Bacula.
+for use in Bacula. This code is now deprecated.
-For all those who I have left out, please send me a reminder, and in any case,
-thanks for your contribution.
+There have been numerous people over the years who have contributed ideas,
+code, and help to the Bacula project. The file AUTHORS in the main source
+release file contains a list of contributors. For all those who I have
+left out, please send me a reminder, and in any case, thanks for your
+contribution.
\subsection*{Copyrights and Trademarks}
\index[general]{Trademarks!Copyrights and }
projects / bacula / docs / commitdiff