<html style="direction: ltr;">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css">body p { margin-bottom: 0cm; margin-top: 0pt; } </style>
</head>
<body bidimailui-charset-is-forced="true" style="direction: ltr;"
text="#000000" bgcolor="#FFFFFF">
<br>
<br>
<div class="moz-cite-prefix">On 04/16/2018 03:31 PM, DelazJ wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAECJsSqVZWXy2LK8-7-NyoBVGXmatrzxGBUKEbPkpt30Yupu=Q@mail.gmail.com">
<div dir="ltr">Hi,<br>
<br>
<div class="gmail_extra">
<div class="gmail_extra">
<div class="gmail_quote">2018-04-15 15:40 GMT+02:00 Patrick
Dunford <span dir="ltr"><<a
href="mailto:enzedrailmaps@gmail.com" target="_blank"
moz-do-not-send="true">enzedrailmaps@gmail.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">I find that hard to
understand. I started off using Qgis on Windows and then
became a novice Linux user and started installing it on
Linux right away. I don't recall ever struggling to
understand how to install it on Linux. It would be no
harder to install than anything else on my system apart
from the usual noob stuff.<br>
<br>
</blockquote>
<div>What do you want? We are not equal in front of IT.<br>
<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
If people find it hard to follow the instructions they
do have the option of installing from their distro. They
won't get the latest version a lot of the time but it
does have the advantage of appearing by default in their
Software Center or whatever package management GUI the
distro provides<span class="gmail-im gmail-HOEnZb"><br>
</span></blockquote>
</div>
</div>
<br>
Yes, maybe the installation instructions should remind people
to check/use their Software center but as you also mention, it
may not provide the version he wants (latest, LTR...?) so the
user has to try the "add repo" steps, hence needs affordable
instructions.<br>
<br>
</div>
<div class="gmail_extra">
<div class="gmail_quote">2018-04-16 4:22 GMT+02:00 Patrick
Dunford <span dir="ltr"><<a
href="mailto:enzedrailmaps@gmail.com" target="_blank"
moz-do-not-send="true">enzedrailmaps@gmail.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">If I was
doing it, it would just be for debian/ubuntu section, the
rest would be copied/pasted from the existing one.<br>
<br>
</blockquote>
<div>The request was already that one: make the
ubuntu/debian section more understandable (if it's not).
Other distros were not concerned as far as i know.<br>
<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
But it seems to me there are really only a small number of
people that actually find it difficult. Like seriously,
why would you put in the example name for you distro when
it clearly says "this is an example".<br>
<br>
</blockquote>
<div>I never made a count but I have the (wrong?) feeling to
often see messages in the different qgis lists about
ubuntu/debian installation process
failures/misunderstandings/missing features. Given that
these instructions are not provided only in English, i
feel the issue is not only about the original writers
English capabilities (but maybe in the way the information
is structured).<br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
I fully agree with Harrisou. Installation and update issues pop up
all too often.<br>
I consider myself an experienced Linux user, and have installed and
used QGIS for over a decade, and still with almost every version
update of QGIS I find myself reshuffling *.list repo files to get
everything working again. Sometimes the problem is caused by GRASS
updates not synchronized with QGIS updates. But the bottom line is
recurring confusion. <br>
<br>
<blockquote type="cite"
cite="mid:CAECJsSqVZWXy2LK8-7-NyoBVGXmatrzxGBUKEbPkpt30Yupu=Q@mail.gmail.com">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div><br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
How far can you practically go to make it easier for a
small number of people who are either Linux novices, have
a poor grasp of English or have comprehension
difficulties?</blockquote>
</div>
</div>
</div>
</blockquote>
<br>
English is my mother tongue, so that's not the cause of the
confusion for me...<br>
<br>
In my opinion, the ideal situation would be:<br>
1- A collection of stable geo software maintained in the regular
ubuntu repositories. So users who want the "LTR" version do not need
to add anything to the sources.list.d. Thus the ubuntugis-ltr would
become unnecesary<br>
2- User's wanting the newer "unstable" version would add the
ubuntugis repo, as explained in qgis.org, and would get a collection
of more recent versions of the geo stack. And thus there would be no
need for the "ubuntugis-unstable" repo.<br>
3- And a third repo - ubuntu-dev aimed for developers.<br>
<br>
I realize that there are lots of dedicated people doing great and
thankless work in all the packaging behind the scenes, and I
certainly don't mean to criticize their efforts. But it seems that
some consolidation might be helpful.<br>
<br>
Regards,<br>
Micha<br>
<blockquote type="cite"
cite="mid:CAECJsSqVZWXy2LK8-7-NyoBVGXmatrzxGBUKEbPkpt30Yupu=Q@mail.gmail.com">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div><br>
</div>
<div>That's the challenge: being able to take the place of
(sigh!) <i>those people</i> and be understood by them.<br>
</div>
<div>QGIS is a world-wide, welcoming and inclusive project
so in any part of the project, (my understanding is that)
it should as far as possible lower the entrance barrier,
for everybody.</div>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"> I have
learning disabilities and had never used Linux before when
I started to use the instructions but I never found them
difficult to understand. The only real improvement I could
think of is to perhaps put a little more detail or
explanation in here and there, if there is enough space.
I've got a rough draft but right now it might easily be
50% or more longer than what's there at the moment.
<div class="HOEnZb">
<div class="h5"><br>
</div>
</div>
</blockquote>
<div> Please, share what you've written so far. If it
improves the situation, then I'm pretty sure there will be
reviewers to help you find the appropriate size (if ever
space should be a limitation).<br>
<br>
</div>
<div>Looking forward...<br>
And thanks for contributing<br>
<br>
</div>
<div>Harrissou<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb">
<div class="h5">
<br>
<br>
On 15/04/18 19:07, Richard Duivenvoorde wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
On 14-04-18 22:30, Patrick Dunford wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
No offence, but it might have been written by
someone who doesn't have<br>
English as their first language.<br>
<br>
It would be interesting for me to try rewriting it
myself...<br>
</blockquote>
Hi Patrick,<br>
<br>
in the footer of the page you will find a 'fixme'
link. If you click<br>
that one, you will be sent to a github page:<br>
<br>
<a
href="https://github.com/qgis/QGIS-Website/edit/master/source/site/forusers/alldownloads.rst"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://github.com/qgis/QGIS-W<wbr>ebsite/edit/master/source/site<wbr>/forusers/alldownloads.rst</a><br>
<br>
AND probably be asked to create a fork of the repo
(do it) and then you<br>
can do a rewrite and can ask for a pull request, so
others can have a<br>
look at your proposal.<br>
<br>
Feel free to do it! But do not underestimate the
complexity of all the<br>
different setups, exclusions, possibilities etc
etc... The different<br>
setups are there for example because one has latest
versions of<br>
software, and another one only the stable versions
etc etc.<br>
<br>
If you can get your head around it, AND do a human
write-up that would<br>
be great. Note that this page has gone over a lot of
iterations already:<br>
<br>
<a
href="https://github.com/qgis/QGIS-Website/commits/master/source/site/forusers/alldownloads.rst"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://github.com/qgis/QGIS-W<wbr>ebsite/commits/master/source/s<wbr>ite/forusers/alldownloads.rst</a><br>
<br>
It is just pretty complex :-)<br>
<br>
But maybe a fresh mind could be a win!<br>
<br>
Regards,<br>
<br>
Richard Duivenvoorde<br>
</blockquote>
<br>
______________________________<wbr>_________________<br>
Qgis-user mailing list<br>
<a href="mailto:Qgis-user@lists.osgeo.org"
target="_blank" moz-do-not-send="true">Qgis-user@lists.osgeo.org</a><br>
List info: <a
href="https://lists.osgeo.org/mailman/listinfo/qgis-user"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://lists.osgeo.org/mailma<wbr>n/listinfo/qgis-user</a><br>
Unsubscribe: <a
href="https://lists.osgeo.org/mailman/listinfo/qgis-user"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://lists.osgeo.org/mailma<wbr>n/listinfo/qgis-user</a></div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Qgis-user mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Qgis-user@lists.osgeo.org">Qgis-user@lists.osgeo.org</a>
List info: <a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/qgis-user">https://lists.osgeo.org/mailman/listinfo/qgis-user</a>
Unsubscribe: <a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/qgis-user">https://lists.osgeo.org/mailman/listinfo/qgis-user</a></pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Micha Silver
Ben Gurion Univ.
Sde Boker, Remote Sensing Lab
cell: +972-523-665918</pre>
</body>
</html>