<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">It is great to hear that we have free
training material seeding the ELOGeo repository.<br>
I think the next step is to work out writing and maintenance
guidelines which can be applied to ensure a consistent, and
up-to-date level of quality across all training material.<br>
<br>
Once this is in place, it will make it much easier for the
community to develop and maintain our documentation.<br>
<br>
So questions I'd like to ask workshop authors are:<br>
<br>
* Are there any examples or best practices in place for outlining
the structure of a training course? (I'm looking for something
similar to our OSGeo-Live documentation processes here: <a
href="http://wiki.osgeo.org/wiki/Live_GIS_Add_Project#Documentation">http://wiki.osgeo.org/wiki/Live_GIS_Add_Project#Documentation</a>
)<br>
<br>
* How can we collect and then incorporate user feedback on the
documentation? I like how the Postgres documentation allows users
to "Add Comment" to each page:<br>
<a
href="http://www.postgresql.org/docs/9.2/interactive/index.html">http://www.postgresql.org/docs/9.2/interactive/index.html</a><br>
<br>
* What technologies should we be using to create the
documentation? For OSGeo-Live we use RST and subversion. I'd be
interested to hear whether this is a technical barrier for tutors,
and maybe we should be adopting a CMS, or wiki, or open office, or
...<br>
<br>
On 29/04/2013 6:11 PM, Lluís Vicens wrote:<br>
</div>
<blockquote cite="mid:517E2B4E.6040408@sigte.udg.es" type="cite">
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<div class="moz-cite-prefix">Al 27/04/13 23:01, En/na Jeremy
Morley ha escrit:<br>
</div>
<blockquote
cite="mid:8EAEC7CE-B68D-4D4E-9F85-A51916C9B140@exmail.nottingham.ac.uk"
type="cite">
<pre wrap="">Dear Cameron,
As a contributor to the Summer School, I'd certainly be happy to contribute material from that to the Live DVD. As I recall, at least some of the material is in ELOGeo under a CC-by-SA licence but of content is updated each year. We have some funding to do some more work on ELOGeo this year, and I plan to convert my course material based on the OSGeo Live USB system to content in ELOGeo. This might serve both purposes. Happy to discuss further.
Jeremy
</pre>
</blockquote>
<font face="Ubuntu">Dear Cameron, as Jeremy points out, all the
documentation used as training material during the previous
editions of the summer school [1][2][3], are freely available
for download in the summer school website as well as from the
ELOGeo[4] repository under a creative commons license. Using
this material as a starting point for educational material
related to OSGeo-Live sounds good. Do you think that a CC-By-SA
is a proper license for this kind of material? <br>
<br>
Cheers,<br>
Lluís<br>
<br>
[1] <a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://www.sigte.udg.edu/summerschool2010/Materials">http://www.sigte.udg.edu/summerschool2010/Materials</a><br>
[2] <a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://www.sigte.udg.edu/summerschool2011/programme/Materials">http://www.sigte.udg.edu/summerschool2011/programme/Materials</a><br>
[3] <a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://www.sigte.udg.edu/summerschool2012/Materials">http://www.sigte.udg.edu/summerschool2012/Materials</a><br>
[4] <a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://elogeo.nottingham.ac.uk/">http://elogeo.nottingham.ac.uk/</a><br>
</font><br>
<pre class="moz-signature" cols="72">--
Lluís Vicens
SIGTE - Universitat de Girona
Pl. Ferrater Mora, 1
17071 Girona
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Cameron Shorter
Geospatial Solutions Manager
Tel: +61 (0)2 8570 5050
Mob: +61 (0)419 142 254
Think Globally, Fix Locally
Geospatial Solutions enhanced with Open Standards and Open Source
<a class="moz-txt-link-freetext" href="http://www.lisasoft.com">http://www.lisasoft.com</a>
</pre>
</body>
</html>