Re: [Debconf-team] How's the debconf6 report coming?
On 3/28/07, Alexander Schmehl <tolimar@debconf.org> wrote:
Don't know of the others (svn looks quite untouched), but at least
proofreading my germish part of the report [1] would be welcome :)
I'm not a native speaker, but I spotted a couple of errors (aspell
helped too :)). Some of them are for en_GB, but I don't know if it's
the preferred locale:
@@ -1,29 +1,29 @@
-\section{Full service please -- Organizing the sessions}
+\section{Full service please -- Organising the sessions}
\label{sec:organizing_events}
\begin{center}
\textcolor{red}{Alexander "Tolimar" Schmehl}
- \small{Head of the speaker team and co-organizer}
+ \small{Head of the speaker team and co-organiser}
%% Uhm... how do we call the "chief" of a team?
%% Should be synchronzied for all "titles"
\end{center}
-Organizing DebConf is a unique thing regarding many aspects. Since
+Organising DebConf is a unique thing regarding many aspects. Since
its attendees are scattered around the world and seldom meet each
other in person DebConf is heavily used for discussing various topics,
outline new ideas, collect feedback and implement them.
This leads high fluctuation of the schedule and all the
-organizational problem involved with that. New ad hoc session are
+organisational problem involved with that. New ad-hoc session are
added on a frequent basis and needs to be announced to other
attendees, conflicts with other sessions must be avoided. And that
while the usual every conference stuff happens (e.g. speaker
requesting other slots or inform you about special needs).
-An example for such an ad hoc session would be the one where Debians
-new python policy was drafted. It started with an ad hoc session
+An example for such an ad-hoc session would be the one where Debian's
+new python policy was drafted. It started with an ad-hoc session
visited by 30 Debian Developers. And reached a somehow critical point
right when the room should have been used an other session.
@@ -41,15 +41,15 @@
nearly every session, they streamed them to the outside world so
interested people who couldn't attend DebConf could participate.
-But that lead to a problem: Seeing a hearing a talk is just half of
+But that lead to a problem: Seeing and hearing a talk is just half of
the fun. To truly participate you need a communication channel back
to the audience to ask questions and get involved in discussions.
-That's even more true for ad hoc sessions.
+That's even more true for ad-hoc sessions.
So we had yet an other job: Playing IRC-proxy and forwarding
questions asked for those who couldn't attend. Many of the Debian
folks are familiar with Internet relay chat. So we created some
-special irc-channels for the audience to discuss and ask questions
+special IRC-channels for the audience to discuss and ask questions
which we in turn would ask loudly. Of course it didn't worked
perfect. Sometimes we had technical problems, sometimes during a
heated debate forwarding questions proofed to be quite complicate.
@@ -59,10 +59,10 @@
\medskip
If you read last years report you'll already know most of our attempts
-to make live for our speaker as easy as possible. Measures like
+to make life for our speakers as easy as possible. Measures like
warning signs if they run out of time (neither all rooms had watches
nor does every speaker look at their own) or a new introduced sign
-signaling the speaker to speak slower proofed again very useful.
+signalling the speaker to speak slower proofed again very useful.
But even if last years conference was a big success we thought there
might still be place for improvements. We got the idea that some kind
@@ -79,7 +79,7 @@
-It will be hard to find a way for further improvements for next years
+It will be hard to find a way for further improvements for next year's
DebConf.
\includegraphics[width=7.5cm]{images/photos/tower_session.jpg}
--
Martín Ferrari
Reply to: