<div dir="ltr">this is where i think software like basecamp has a role to play: <a href="http://www.basecamphq.com/">http://www.basecamphq.com/</a> which is free for a single project i.e. one conference<br><br>however we have already got a set of tools i'm not sure its worth changing horse mid stream?<br>
<br><div class="gmail_quote">2008/9/25 Cameron Shorter <span dir="ltr"><<a href="mailto:cameron.shorter@gmail.com">cameron.shorter@gmail.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
-0 for collaborative editing using a wiki.<br>
<br>
Wikis are a poor tool for tracking changes because you can't easily see what has changed, what it was before, or who changed it (Yes, you can do a history diff, but it is messy). Open Office is better, but doesn't do a good job with inserting comments. Much as I hate saying it, Word is the best tool I seen yet for this.<br>
<br>
My preference is to use tracked changes in word, followed by tracked changes in Open Office.<br>
(Note, the document authors, usually Tour Hosts, should be able to merge changes from multiple authors)<br>
<br>
Bruce Bannerman wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div></div><div class="Wj3C7c">
+1<br>
<br>
I don't use MS Word as a rule (except at my old job), preferring Open<br>
Office. <br>
I also don't have access to it now, and have no intention of buying a<br>
license.<br>
<br>
B<br>
<br>
<br>
On Wed, 2008-09-24 at 22:45 -0700, Dave Patton wrote:<br>
<br>
</div></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div></div><div class="Wj3C7c">
The current process that we are using for<br>
making collaborative changes to documents<br>
isn't working for me. Currently, once a<br>
document(e.g. a flier) is created, it's<br>
mailed to 'the list' as a Word document,<br>
and people are invited to make comments<br>
and changes, using Word's 'track changes'.<br>
As has already been demonstrated, as soon<br>
as someone forgets to use 'track changes',<br>
or two people make changes to their copy<br>
of the original, the system breaks down,<br>
and requires people to re-review, and even<br>
redo changes they already have made.<br>
<br>
I'd suggest that we switch to a method where<br>
there is a "single source document" that is<br>
used for any collaborative editing/review.<br>
<br>
My vote would be to use a wiki page, which will<br>
be suitable for anything where we are 'just<br>
reviewing text'. If there are also going to<br>
be 'layout issues'(e.g. formatting, what images<br>
to use, etc.) with the document, then address<br>
them using commentary on a PDF version that is<br>
mailed to the list, after the text is 'finalized'.<br>
<br></div></div>
------------------------------------------------------------------------<div class="Ih2E3d"><br>
<br>
_______________________________________________<br>
Foss4g2009 mailing list<br>
<a href="mailto:Foss4g2009@lists.osgeo.org" target="_blank">Foss4g2009@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/foss4g2009" target="_blank">http://lists.osgeo.org/mailman/listinfo/foss4g2009</a><br>
<br>
</div></blockquote></blockquote>
<br>
<br>
-- <br>
Cameron Shorter<br>
Geospatial Systems Architect<br>
Tel: +61 (0)2 8570 5050<br>
Mob: +61 (0)419 142 254<br>
<br>
Think Globally, Fix Locally<br>
Geospatial Solutions enhanced with Open Standards and Open Source<br>
<a href="http://www.lisasoft.com" target="_blank">http://www.lisasoft.com</a><div><div></div><div class="Wj3C7c"><br>
<br>
_______________________________________________<br>
Foss4g2009 mailing list<br>
<a href="mailto:Foss4g2009@lists.osgeo.org" target="_blank">Foss4g2009@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/foss4g2009" target="_blank">http://lists.osgeo.org/mailman/listinfo/foss4g2009</a><br>
</div></div></blockquote></div><br></div>