<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
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;}
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;
color:black;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1952659698;
mso-list-template-ids:-1076876894;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></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]-->
</head>
<body bgcolor="white" lang="EN-GB" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:windowtext;mso-fareast-language:EN-US">Dear all,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext;mso-fareast-language:EN-US">I would like to share my humble opinion in this topic.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext;mso-fareast-language:EN-US">I think that a quick way to illustrate QGIS functionality could be via videos.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext;mso-fareast-language:EN-US">I have seen how videos can complement an user guide or tutorial.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext;mso-fareast-language:EN-US">What I propose is:
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext;mso-fareast-language:EN-US"> For end users, design a workflow (written/diagram) and add a short video of the how-to. Recording screens can be faster than deciding the right sentence, e.g., the
exact semantic.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext;mso-fareast-language:EN-US"> I think that perhaps this approach can speed the documentation process. This could seem a naïve suggestion from a beginner user/documenter but big companies are doing
so.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext;mso-fareast-language:EN-US">Cheers<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext;mso-fareast-language:EN-US">Rosa<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="color:windowtext">From:</span></b><span lang="EN-US" style="color:windowtext"> Qgis-community-team <qgis-community-team-bounces@lists.osgeo.org>
<b>On Behalf Of </b>Andreas Neumann<br>
<b>Sent:</b> 26 August 2019 14:43<br>
<b>To:</b> qgis-community-team@lists.osgeo.org<br>
<b>Subject:</b> Re: [Qgis-community-team] Draft paper discussing QGIS docs<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p>Hi again,<o:p></o:p></p>
<p>Another observation I have is that there is an awful lot of documentation about QGIS out their on the web, spread into many personal blog websites, company blog posts and news sites, youtube movies, social media posts, etc. etc. However, all of this vast
and de-centralized information doesn't end up in our central documentation.<o:p></o:p></p>
<p>My assumption is that people prefer to add such information more to their own, personal website, rather than to QGIS.OR because it helps them to:<o:p></o:p></p>
<ul type="disc">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
build personal reputation (individual persons). I think about people like Anita Graser, Klas Karlsson, and probably many others who always add the new cool stuff to their own websites, but not to QGIS.ORG<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
show off what cool features the company added recently to QGIS core (which helps their business) - examples are companies like OpenGIS, Oslandia, etc. who add new cool stuff to their company website, but not to QGIS.ORG<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
better learn and understand how QGIS works (which is useful for building up their skills). I heard from Harrissou that this was his main motivation to contribute to the centralized QGIS documentation.<o:p></o:p></li></ul>
<p>From these above three different motivations, only the last one can be fulfilled by adding new information to our centralized documentation, the other two are better done outside of the centralized documentation.<o:p></o:p></p>
<p>So I wonder if the huge work of documentors in the centralized documentation could be better credited/attributed to individuals, so that the other two motivations of gaining personal or company reputation by contributing to the centralized QGIS documentation
is better fulfilled?<o:p></o:p></p>
<p>Just some thoughts ...<o:p></o:p></p>
<p>Andreas<o:p></o:p></p>
<div>
<p class="MsoNormal">Am 26.08.19 um 15:10 schrieb Andreas Neumann:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Hi Cameron, <br>
<br>
Thank you for summarizing your observations and assessment on the current state of documentation in QGIS.
<br>
<br>
I agree that the documentation task seems to be overwhelming and might also be daunting for newcomers, volunteers and even paid people. I also agree that the team is under-resourced.
<br>
<br>
However, we already knew this before your assessment. <br>
<br>
So I wonder if you could add your thoughts and recommendations on how to improve our situation? We already know about our misery and bad state, but it would be encouraging to hear more suggestions for how to improve the situation. This would be really valuable
for us. <br>
<br>
It is not primarily a problem of finding financial resources. Every year we assigned funds for documentation and in most years those funds haven't been used. Even if we would make more funds available to the team, I feel this wouldn't solve the problems the
team is facing. <br>
<br>
Should the team focus on smaller chunks/goals in order to have better progress and a better success feeling?
<br>
<br>
Are the tools to complicated? <br>
<br>
Is there not enough information provided by developers or organizations who fund a new features?
<br>
<br>
Thanks again for adding more suggestions and advice to your document - this would help us much more than just the assessment of the current state.
<br>
<br>
Andreas <br>
<br>
Am 26.08.19 um 14:35 schrieb Cameron Shorter: <br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal" style="margin-bottom:12.0pt">For those involved in QGIS docs,
<br>
<br>
After a bit of brainstorming with Matteo about what next for QGIS docs, I offered to put some ideas down into an article to give him something tangible to take to the QGIS Project Steering Committee next week.
<br>
<br>
I feel my thoughts have room to be developed a bit and I'd be keen to hear feedback on them before I copy to my blog at the end of this week.
<br>
<br>
<a href="https://docs.google.com/document/d/11N5d1aBgkdQ80I7RKBlt_jx9Uk1RGsvOTeq_TSFeljA/edit">https://docs.google.com/document/d/11N5d1aBgkdQ80I7RKBlt_jx9Uk1RGsvOTeq_TSFeljA/edit#</a>
<br>
<br>
Comments are preferred to track changes (which become hard to manage). If you comment, please log in first so I know who said what.
<o:p></o:p></p>
</blockquote>
<p class="MsoNormal">_______________________________________________ <br>
Qgis-community-team mailing list for organizing community resources such as documentation, translation etc..
<br>
<a href="mailto:Qgis-community-team@lists.osgeo.org">Qgis-community-team@lists.osgeo.org</a>
<br>
<a href="https://lists.osgeo.org/mailman/listinfo/qgis-community-team">https://lists.osgeo.org/mailman/listinfo/qgis-community-team</a><o:p></o:p></p>
</blockquote>
</div>
</body>
</html>