<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi Ori, (CCing OSGeo SeasonOfDocs with permission),</p>
<p>Yes, based on how things are shaping up, I'm reasonably
comfortable that we will be creating a
method/framework/template/writing guide for creating certain doc
types - almost certainly covering training material. I'm expecting
Jared Morgan is going to be really helpful in this regard, as he
is deeply embedded in the WriteTheDocs community and should be
able to help us tap into great insights here.<br>
</p>
<p>I see us testing these on QGIS and GeoNetwork and OSGeoLive
within the SeasonOfDocs timeframe. People have volunteered to help
with content writing - although not to the volume required to
create a course from scratch. This is where we need to start
talking about existing material to draw upon.</p>
<p>Re "Protecting" material or not. This is a decision for you to
make internally. I feel that any material worked on in this
project should be developed under an Open License (probably
CC-By-SA). I think you will find that people are keen to volunteer
to contribute to open material but not to contribute to something
that leads to a lock out situation. Decision comes down to free
content + get free labour, or lock down content and pay for your
own labour. More comprehensive description of this business case
is here: <a
href="http://cameronshorter.blogspot.com/2018/10/the-open-business-business-case.html">http://cameronshorter.blogspot.com/2018/10/the-open-business-business-case.html</a></p>
<p>For the more nitty-gritty details about content to create, and
who does what and when, I'm looking for input from you folk
actively involved in GIS training to discuss this together. Don't
be shy, do speak up.</p>
<p>Cheers, Cameron<br>
</p>
<div class="moz-cite-prefix">On 23/5/19 4:34 pm, Ori Gudes wrote:<br>
</div>
<blockquote type="cite"
cite="mid:ME1PR01MB1876E5B48BE94F1FAE4CA71FA4010@ME1PR01MB1876.ausprd01.prod.outlook.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
mso-fareast-language:EN-AU;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal">Hi Cameron,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks for your detailed email, I believe
there are many valid points here, and at this stage I did not
address all of them.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I think for a start, we do need to identify
what is our <u>collaborative vision</u> here? As this will
derive everything we do. Do we develop a method / a framework
in which training materials can be easily updated or
maintained? Are we focused only on QGIS? Or also other open
Geo projects? <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">How can we protect our content?
Ultimately, what we would like to achieve, having all partners
/ technical writers / capacity involved? What is achievable
in the time frame of 6 months? Do we need to have focus groups
based on certain tools / products? (e.g., QGIS, other open
source tools etc. ). I think these are critical points /
questions need to be asked/ discussed/ answered before we move
on and discuss about writing, style technical details etc.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Feel free to share my response if it adds
anything?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Regards Ori<o:p></o:p></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Sun, 19 May 2019 at 09:18, Cameron
Shorter <<a href="mailto:cameron.shorter@gmail.com"
moz-do-not-send="true">cameron.shorter@gmail.com</a>>
wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC
1.0pt;padding:0cm 0cm 0cm
6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<p>OSGeo Season of Docs folks, (BCCed to a few potential
collaborators),<o:p></o:p></p>
<p>As you know, the OSGeo Foundation will be allocated 1
paid technical writer, for equivalent of ~ 3 months
(probably spread over 6), as part of Google's commitment
to Season of Docs [0].<o:p></o:p></p>
<p>But more valuable are the 18+ serious volunteers (on
this list) wanting to be involved, and 5+ QGIS training
material baselines that we can potentially build upon.
[1] I'm hoping to discuss these baselines within this
email thread and build a collaborative vision which
focuses our Season of Docs direction.<o:p></o:p></p>
<p>(Chris, Ori, Scott from Uni of NSW), Charlie from Uni
of Massachusetts, Piers from Gaia Resources, Jo from
Austun Technology, Matteo from QGIS docs, Nick from Uni
College of London, Phil from
<span
style="font-size:10.5pt;font-family:"Arial",sans-serif;color:#252525;background:white">GeoAcademy</span>:
You all have mentioned training material that you might
be able to access. I'm hoping you might restate your
ideas here. (Cut and paste from before is fine).<o:p></o:p></p>
<p>My observations so far (based on input so far):<o:p></o:p></p>
<p>* We have multiple offers of material to start from,
but less interest in building from someone else's
material.<o:p></o:p></p>
<p>* We all find it hard to sustain the maintenance of
material, acknowledging the rapid innovation of QGIS
(and other OSGeo projects). We'd all love external help
updating our material.<o:p></o:p></p>
<p>* We are all concerned about the free-rider problem. We
are mindful that collaborators in material development
are potential competitors for students (and hence
funding). Our organisation's reputation is an important
part of this story.<o:p></o:p></p>
<p>* We need to balance generic content that is easy to
maintain versus use case specific training for targeted
customers. (Especially important around local maps and
datums used).<o:p></o:p></p>
<p>* It seems like there is core functionality that we can
probably all agree to use as a starting point for
collaboration. What is it? This might be our best pilot
focus area.<o:p></o:p></p>
<p>* We could also define a best practices formula for
building training material that we all adopt, addressing
structure, writing style, etc. This is something a
senior technical writer could define, (and could be
extended to other OSGeo projects and to the greater Open
Source community). This would help students who are
progressing through multiple training courses as they'd
become familiar with writing styles. Would you be
prepared to adopt such a guide (assuming it is better
than what you already have)?<o:p></o:p></p>
<p>* We'll need to agree on a license that everyone can
use, probably Creative Commons by Attribution.<o:p></o:p></p>
<p>So for those of you wanting to collaborate around
training material - how can we help you do that? How can
you help others?<o:p></o:p></p>
<p>[0] <a
href="https://wiki.osgeo.org/wiki/Season_of_Docs_Ideas_2019#Leveraging_Google.E2.80.99s_Season-of-Docs"
target="_blank" moz-do-not-send="true">
https://wiki.osgeo.org/wiki/Season_of_Docs_Ideas_2019#Leveraging_Google.E2.80.99s_Season-of-Docs</a><o:p></o:p></p>
<p>[1] <a
href="https://wiki.osgeo.org/wiki/Season_of_Docs_Ideas_2019#Interested.3F"
target="_blank" moz-do-not-send="true">
https://wiki.osgeo.org/wiki/Season_of_Docs_Ideas_2019#Interested.3F</a><o:p></o:p></p>
<pre>-- <o:p></o:p></pre>
<pre>Cameron Shorter<o:p></o:p></pre>
<pre>Technology Demystifier<o:p></o:p></pre>
<pre>Open Technologies and Geospatial Consultant<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>M +61 (0) 419 142 254<o:p></o:p></pre>
</div>
</blockquote>
</div>
<p class="MsoNormal"><br clear="all">
<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">-- <o:p></o:p></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span
style="font-size:9.5pt">Cameron Shorter</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Technology Demystifier<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Open Technologies and
Geospatial Consultant<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">M +61 (0) 419 142 254<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"
style="margin-bottom:12.0pt"><o:p> </o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<pre class="moz-signature" cols="72">--
Cameron Shorter
Technology Demystifier
Open Technologies and Geospatial Consultant
M +61 (0) 419 142 254</pre>
</body>
</html>