<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi<div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 18 May 2016, at 12:49, DelazJ <<a href="mailto:delazj@gmail.com" class="">delazj@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Hi,<br class=""><br class="">2016-05-18 8:24 GMT+02:00 Tim Sutton <span dir="ltr" class=""><<a href="mailto:tim@kartoza.com" target="_blank" class="">tim@kartoza.com</a>></span>:<br class=""><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="word-wrap:break-word" class="">Hi<div class=""><br class=""></div><div class=""><br class=""></div><div class="">After rereading the thread I think I am +1 for moving to RST in the QGIS Docs repo with the following thinking:</div><div class=""><br class=""></div></div></blockquote><div class="">Is the Doc repo a better candidate for this (if we get the go!) than QGIS website?<br class=""></div></div></div></blockquote><div><br class=""></div><div>Sorry yes, you are correct, the Web site is the better place.</div><div><br class=""></div><div>Regards</div><div><br class=""></div><div>Tim</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><br class=""></div><div class="">*
QGIS Website is always translatable, so can easily show the most recent
procedure in different languages. It also provides a chapter on
development steps, might be worth having this beside.<br class=""></div><div class="">*
Using website, we have a unique hyperlink (to use in our
communication if needed) instead of having to update it after each released
doc <br class=""></div><div class="">* testing doc (which in the ideal world, is related to master) is not to be translated<br class="">*
not all QGIS versions are/will be documented: the last doc provided is
2.8. The next should be 2.14 (btw, still looking for volunteers to write
it - around 80 issues remaining and not the least) but when will be the
release?<br class=""></div><div class=""><br class=""></div><div class=""> <br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="word-wrap:break-word" class=""><div class="">* all the good stuff Junior mentioned like translatability, visibility etc.</div><div class="">*
when we hit release freeze we could copy the latest output from sphinx
(maybe generated as plain text file?) to INSTALL.txt and remove the
sources for the install docs from the QGIS code tree. That way the QGIS
sources always contain the current notes for that release and the doc
sources contain only the most recent procedure.</div><div class="">* we could add
a note in the docs sources saying ‘these instructions are for the
current state of the develop branch only, for version specific install
procedures, please see the INSTALL.txt in the source tree for that
release’</div><div class=""><br class=""></div></div></blockquote><div class="">+1 though the copy would be from the website repo (as suggested above)<br class=""> <br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="word-wrap:break-word" class=""><div class="">I
think that workflow is not too much different from the current system.
Of course someone needs to volunteer to get all the processes above into
place :-P</div><div class=""><br class=""></div></div></blockquote><div class="">I'd RSTed the
install doc and opened a pull request at
<a href="https://github.com/qgis/QGIS-Website/pull/343/files" class="">https://github.com/qgis/QGIS-Website/pull/343/files</a>. Might need
correction. It's the content on April 15th. Don't however know the steps
to keep this up to date nor automate some changes (like date of doc).<br class=""><br class=""></div><div class="">Regards,<br class=""></div><div class="">Harrissou<br class=""><br class=""></div><br class=""></div><div class="gmail_extra"><br class=""><div class="gmail_quote">2016-05-18 8:49 GMT+02:00 Jürgen E. <span dir="ltr" class=""><<a href="mailto:jef@norbit.de" target="_blank" class="">jef@norbit.de</a>></span>:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Tim,<br class="">
<span class=""><br class="">
On Wed, 18. May 2016 at 08:24:05 +0200, Tim Sutton wrote:<br class="">
> @Jürgen regarding your comments below, I used to use apt-get build-dep too<br class="">
> but I actually like the explicit package list your script generates more in<br class="">
> some ways because it is deterministic compared to build-dep which will only<br class="">
> reflect the deps from the current latest package in apt sources.<br class="">
<br class="">
</span>The dependencies of the latest automatic nightly are probably more up-to-date<br class="">
than the list from the latest manual INSTALL update run.<br class="">
<span class="im HOEnZb"><br class="">
<br class="">
Jürgen<br class="">
<br class="">
--<br class="">
Jürgen E. Fischer norBIT GmbH Tel. <a href="tel:%2B49-4931-918175-31" value="+49493191817531" class="">+49-4931-918175-31</a><br class="">
</span><span class="im HOEnZb">Dipl.-Inf. (FH) Rheinstraße 13 Fax. <a href="tel:%2B49-4931-918175-50" value="+49493191817550" class="">+49-4931-918175-50</a><br class="">
</span><div class="HOEnZb"><div class="h5">Software Engineer D-26506 Norden <a href="http://www.norbit.de/" rel="noreferrer" target="_blank" class="">http://www.norbit.de</a><br class="">
QGIS release manager (PSC) Germany IRC: jef on FreeNode<br class="">
</div></div><br class="">_______________________________________________<br class="">
Qgis-community-team mailing list for organizing community resources such as documentation, translation etc..<br class="">
<a href="mailto:Qgis-community-team@lists.osgeo.org" class="">Qgis-community-team@lists.osgeo.org</a><br class="">
<a href="http://lists.osgeo.org/mailman/listinfo/qgis-community-team" rel="noreferrer" target="_blank" class="">http://lists.osgeo.org/mailman/listinfo/qgis-community-team</a><br class=""></blockquote></div><br class=""></div>
_______________________________________________<br class="">Qgis-developer mailing list<br class=""><a href="mailto:Qgis-developer@lists.osgeo.org" class="">Qgis-developer@lists.osgeo.org</a><br class="">List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer<br class="">Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer</div></blockquote></div><br class=""><div class="">
<span><img height="65" width="59" apple-inline="yes" id="E1C8B451-D76F-4A0F-B541-25A9BA485C78" apple-width="yes" apple-height="yes" src="cid:879A6E78-CA46-47B2-AA0E-1810BD833229" class=""></span><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; line-height: normal; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="font-weight: normal;" class=""><br class="Apple-interchange-newline"><br class="Apple-interchange-newline">---</div><div style="font-weight: normal;" class=""><br class=""></div><div class=""><b class="">Tim Sutton</b></div><div style="font-weight: normal;" class="">QGIS Project Steering Committee Chair</div><div style="font-weight: normal;" class=""><a href="mailto:tim@qgis.org" class="">tim@qgis.org</a></div><div style="font-weight: normal;" class=""><br class=""></div></div><br class="Apple-interchange-newline" style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; line-height: normal;"><br class="Apple-interchange-newline" style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
</div>
<br class=""></div></body></html>