cgal/Packages/Developers_manual/web_site.tex

110 lines
4.2 KiB
TeX

\chapter{The \cgal\ Web Site}
\label{chap:web_site}
\ccIndexMainItemBegin{web site}
The web site for the \cgal\ organization is \path|http://www.cgal.org|.
This is currently hosted by the MPI and is maintained by
\ccAnchor{mailto:kettner@mpi-sb.mpg.de}{Lutz Kettner}.
\section{CVS Package and Maintenance}
The maintenance of the actual contents is decentralized and can be
done according to responsibilities and interests of the different
contributors with access to the corresponding CVS package
\begin{quote}
\textbf{Web\_pages}
\end{quote}
that contains most of the web pages. Exceptions are large binaries and,
for example, the Manual, which is generated (and large) and is thus
not suitable to be put in CVS. One can see the distinction in the
URL's, everything starting with
\begin{quote}
\textbf{pub/}\\
\textbf{Members/pub/}\\
\textbf{Manual/}
\end{quote}
is not in CVS. If you want something changed or added here, you have to
contact \ccAnchor{mailto:kettner@mpi-sb.mpg.de}{Lutz Kettner} (or some
other \cgal\ person at MPI). (For the manual an exception for the
above exception are some HTML files, for example the frameset,
that are actually available in the CVS package \texttt{Manual}.)
Several developers have write access to the new \texttt{Web\_pages}
package, or might get it whenever need arises. Note that the CVS package
\begin{quote}
\textit{\textbf{is not automatically syncronized}}
\end{quote}
with the actual web pages. It is a manual \texttt{cvs up} call that
has to be initiated at MPI. This is also intended as a final quality
control before updates show up on our web pages. It allows us to have
the set of people with write access to the CVS package not to be too
restrictive.
How do you get your changes finally on the web pages of \cgal?
The CVS server actually informs the maintainer at MPI (see above)
automatically by email about committed changes in the
\texttt{Web\_pages} package. So, either just commit small changes, the
maintainer verifies them and integrates them in the next update of the
web pages. If you plan something bigger, please let the maintainer
know, so that updates can be suspended until you are done. Or, if you
plan to have the updates done with a particular deadline, inform the
maintainer with enough time ahead to plan this, since:
\begin{itemize}
\item
The maintainer does not necessarily read email all the time
(maybe not even daily ;-).
\item
The maintainer might not consider your request as important as
other tasks, especially since
\item
typically nothing on CGAL's web site has the importance that needs
24/7 service, and most things can also wait a week.
\end{itemize}
If you plan updates that are not obviously consensus, you should discuss them
beforehand on the usual mailing lists. The maintainer might block an
update if its status is not clear.
\section{Regular Tasks}
Some aspects of the web pages need constant attention to keep them
up-to-date. If you can please do the necessary updates yourself,
notify the corresponding maintainer, or the maintainer mentioned above
if you know about updates for the following:
\begin{itemize}
\item new
\ccAnchor{http://www.cgal.org/publications_frame.html}{publications}
related to \cgal, maintained by
\ccAnchor{mailto:Monique.Teillaud@sophia.inria.fr}{Monique Teillaud};
\item updates for the
\ccAnchor{http://www.cgal.org/in_progress_frame.html}{work in progress}
page, which includes work that is finished and thus no longer in
progress and new work.
\item new
\ccAnchor{http://www.cgal.org/demos_frame.html}{demo programs}
to be included on the web site. (See Section~\ref{sec:demos_web_page}
for the precise specification of how to submit these.)
\item new
\ccAnchor{http://www.cgal.org/people_frame.html}{people}
involved in the project
\item new
\ccAnchor{http://www.cgal.org/projects_frame.html}{projects}
using \cgal\ by people other than developers.
\end{itemize}
And, of course, please tell the maintainer about any problems you have
with the web site.
\ccIndexMainItemEnd{web site}