<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<!--Converted with LaTeX2HTML 2008 (1.71)
original version by: Nikos Drakos, CBLU, University of Leeds
* revised and updated by: Marcus Hennecke, Ross Moore, Herb Swan
* with significant contributions from:
Jens Lippmann, Marek Rouchal, Martin Wilck and others -->
<HTML>
<HEAD>
<TITLE>Bacula Code Submissions and Projects</TITLE>
<META NAME="description" CONTENT="Bacula Code Submissions and Projects">
<META NAME="keywords" CONTENT="developers">
<META NAME="resource-type" CONTENT="document">
<META NAME="distribution" CONTENT="global">
<META NAME="Generator" CONTENT="LaTeX2HTML v2008">
<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
<LINK REL="STYLESHEET" HREF="developers.css">
<LINK REL="next" HREF="Patches_Released_Versions.html">
<LINK REL="previous" HREF="Development_Cycle.html">
<LINK REL="up" HREF="Bacula_Developer_Notes.html">
<LINK REL="next" HREF="Patches_Released_Versions.html">
</HEAD>
<BODY >
<!--Navigation Panel-->
<A NAME="tex2html479"
HREF="Patches_Released_Versions.html">
<IMG WIDTH="37" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="next" SRC="next.png"></A>
<A NAME="tex2html473"
HREF="Bacula_Developer_Notes.html">
<IMG WIDTH="26" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="up" SRC="up.png"></A>
<A NAME="tex2html467"
HREF="Development_Cycle.html">
<IMG WIDTH="63" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="previous" SRC="prev.png"></A>
<A NAME="tex2html475"
HREF="Contents.html">
<IMG WIDTH="65" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="contents" SRC="contents.png"></A>
<A NAME="tex2html477"
HREF="GNU_Free_Documentation_Lice.html">
<IMG WIDTH="43" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="index" SRC="index.png"></A>
<BR>
<B> Next:</B> <A NAME="tex2html480"
HREF="Patches_Released_Versions.html">Patches for Released Versions</A>
<B> Up:</B> <A NAME="tex2html474"
HREF="Bacula_Developer_Notes.html">Bacula Developer Notes</A>
<B> Previous:</B> <A NAME="tex2html468"
HREF="Development_Cycle.html">The Development Cycle</A>
<B> <A NAME="tex2html476"
HREF="Contents.html">Contents</A></B>
<B> <A NAME="tex2html478"
HREF="GNU_Free_Documentation_Lice.html">Index</A></B>
<BR>
<BR>
<!--End of Navigation Panel-->
<H1><A NAME="SECTION00220000000000000000"></A>
<A NAME="157"></A>
<BR>
Bacula Code Submissions and Projects
</H1>
<P>
Getting code implemented in Bacula works roughly as follows:
<P>
<UL>
<LI>Kern is the project manager, but prefers not to be a "gate keeper".
This means that the developers are expected to be self-motivated,
and once they have experience submit directly to the Git
repositories. However,
it is a good idea to have your patches reviewed prior to submitting,
and it is a bad idea to submit monster patches because no one will
be able to properly review them. See below for more details on this.
<P>
</LI>
<LI>There are growing numbers of contributions (very good).
<P>
</LI>
<LI>Some contributions come in the form of relatively small patches,
which Kern reviews, integrates, documents, tests, and maintains.
<P>
</LI>
<LI>All Bacula developers take full
responsibility for writing the code, posting as patches so that we can
review it as time permits, integrating it at an appropriate time,
responding to our requests for tweaking it (name changes, ...),
document it in the code, document it in the manual (even though
their mother tongue is not English), test it, develop and commit
regression scripts, and answer in a timely fashion all bug reports -
even occasionally accepting additional bugs :-)
<P>
This is a sustainable way of going forward with Bacula, and the
direction that the project will be taking more and more. For
example, in the past, we have had some very dedicated programmers
who did major projects. However, some of these
programmers due to outside obligations (job responsibilities change of
job, school duties, ...) could not continue to maintain the code. In
those cases, the code suffers from lack of maintenance, sometimes we
patch it, sometimes not. In the end, if the code is not maintained, the
code gets dropped from the project (there are two such contributions
that are heading in that direction). When ever possible, we would like
to avoid this, and ensure a continuation of the code and a sharing of
the development, debugging, documentation, and maintenance
responsibilities.
</LI>
</UL>
<P>
<HR>
<!--Navigation Panel-->
<A NAME="tex2html479"
HREF="Patches_Released_Versions.html">
<IMG WIDTH="37" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="next" SRC="next.png"></A>
<A NAME="tex2html473"
HREF="Bacula_Developer_Notes.html">
<IMG WIDTH="26" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="up" SRC="up.png"></A>
<A NAME="tex2html467"
HREF="Development_Cycle.html">
<IMG WIDTH="63" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="previous" SRC="prev.png"></A>
<A NAME="tex2html475"
HREF="Contents.html">
<IMG WIDTH="65" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="contents" SRC="contents.png"></A>
<A NAME="tex2html477"
HREF="GNU_Free_Documentation_Lice.html">
<IMG WIDTH="43" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="index" SRC="index.png"></A>
<BR>
<B> Next:</B> <A NAME="tex2html480"
HREF="Patches_Released_Versions.html">Patches for Released Versions</A>
<B> Up:</B> <A NAME="tex2html474"
HREF="Bacula_Developer_Notes.html">Bacula Developer Notes</A>
<B> Previous:</B> <A NAME="tex2html468"
HREF="Development_Cycle.html">The Development Cycle</A>
<B> <A NAME="tex2html476"
HREF="Contents.html">Contents</A></B>
<B> <A NAME="tex2html478"
HREF="GNU_Free_Documentation_Lice.html">Index</A></B>
<!--End of Navigation Panel-->
<ADDRESS>
2012-01-24
</ADDRESS>
</BODY>
</HTML>
