<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Thank you for your feedback, just some thought about your first
feedback.</p>
<p>"Blocker" level should be fast and easy to fix, so fixing some
typos is easy and generally doesn't need too much discussion.</p>
<p>"Not important" level: this is probably not the best word to
describe this level because it could be important. What I mean is
that it need more discussion to find a common consensus. For
example, location of a description.</p>
For me, typos in a text is a problem. If the location of the
description is not the best one, I probably can find it (search with
Google or so), this is not a problem that occurs often and as said,
if someone says this is not a good location, if the contributor
agreed he can move it.<br>
<br>
Finally, about pushing some fix in a branch of other contributor: I
think this shouldn't be done. I see a branch as a personal work and
pushing a commit, quiet <span id="result_box" class="short_text"
lang="en"><span class="">invasive</span></span>. Personally, I
commit with amend flag then "push force" most of the time in my
branch.<br>
<br>
@paolo, as soon as we find a consensus, we will write it into the
guidelines. I will then help to find someone to be paid to write
documentation.<br>
<br>
Thanks,<br>
<br>
Y.<br>
<br>
<div class="moz-cite-prefix">Le 19/09/2018 à 07:21, Paolo Cavallini
a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:7ab86b81-e22c-1d2c-596c-099c18542eb5@faunalia.it">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<p>Lots of good ideas, thanks everybody. Yves, could you please
keep track of the discussion and implement its conclusions? I
think we all agree on these. In case of doubt, please refer to
PSC.</p>
<p>Thanks.<br>
</p>
<br>
<div class="moz-cite-prefix">Il 09/18/2018 07:14 PM, Alexandre
Neto ha scritto:<br>
</div>
<blockquote type="cite"
cite="mid:CA+H0G_HqcMtqwyxYyw7DHmPfT8K5X=eouWEP+Q1TMUUUw97nWQ@mail.gmail.com">
<meta http-equiv="content-type" content="text/html;
charset=utf-8">
<div dir="ltr">
<div>Hi Yves, thanks for raising this matter.</div>
<div><br>
</div>
<div>+1 for making it easier to accept and merge
contributions.<br>
</div>
<div><br>
</div>
<div>I would just swap the "There are typos" with the
"location of the contributions" position. Mainly because the
typos can be fixed later (unless there are major English
problem that make the text difficult to understand), where
contribution location can mess things up badly, and might be
more difficult to untangle later. <br>
</div>
<div><br>
</div>
<div>Maybe, we should open dedicated tickets for reviewing and
"sphinxifying" content for non important and no blocker
merged PRs (or remove some tags and add some others
(Screenshots, Needs English Review, Sphinx)).<br>
</div>
<div><br>
</div>
<div> Maybe we could use QGIS funds to hire someone that could
tackle those "after content writing" tickets, which may be
much easier than finding candidates that are both QGIS
(advanced) users, good writing technical English, and
familiar with sphinx syntax.</div>
<div><br>
</div>
<div>Thanks,</div>
<div><br>
</div>
<div>Alexandre Neto<br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr">Yves Jacolin <<a
href="mailto:yjacolin@free.fr" moz-do-not-send="true">yjacolin@free.fr</a>>
escreveu no dia terça, 18/09/2018 às 16:45:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hello
community and documentation contributors,<br>
<br>
I would like to raise a discussion about the merge process
in the QGIS<br>
documentation.<br>
<br>
My opinion is that the documentation process should be made
easier in<br>
order to increase the dynamic and the speed of feature
documentation. I<br>
do think we try to do our best to do some doc review, but
probably not<br>
enough and not fast enough. We should improve this and be
faster in<br>
order to be closer to the QGIS feature of the current public
release,<br>
then look at how to improve documentation later. If features
are well<br>
documented, we can probably pay for someone to proof read
and fix<br>
english issue.<br>
<br>
In this purpose I would like to propose some keys to help
merging PR and<br>
I would like to get your opinion.<br>
<br>
I would like to create three "levels" (a kind of guidelines)
to<br>
accept/refuse a PR, in a similar way as QGIS issues:<br>
<br>
# Blocker (="need change" in review process)<br>
<br>
Impossible to merge the PR because:<br>
<br>
* Travis failed<br>
* There is typos<br>
* Write does not use any rst tags (:guilabel:, code-block,
index, title,<br>
etc.)<br>
<br>
# No blocker but important (="comment" in review process)<br>
<br>
PR can be merged but contributors can improve it before
merging because:<br>
<br>
* There is some missing rst tag<br>
* Some sentences are not well written (I mean most of doc
contributor<br>
are not native english writer and so we are nos using the
best english,<br>
this email is a good illustration)<br>
<br>
# Not important, just feedback (="comment" in review
process)<br>
<br>
PR can be merged, this is mainly subjective or small changes
as:<br>
<br>
* location of the contribution<br>
* need screenshot (or update)<br>
* fix a problem which has not been created by the PR<br>
* Not enough description<br>
<br>
Other contribution can create issue to not forget some of
this changes<br>
proposals.<br>
<br>
We already agreed on the following, but better to tell it
again: small<br>
fix (add rst tag, fix typos) could be merged as soon as
travis is a<br>
success! So please, focus in small fix outside bigger PR :)<br>
<br>
I am looking forward to read your opinion :)<br>
<br>
Thanks to all for your great contributions!<br>
<br>
Y.<br>
<br>
-- <br>
<a href="http://yjacolin.gloobe.org" rel="noreferrer"
target="_blank" moz-do-not-send="true">http://yjacolin.gloobe.org</a><br>
<br>
<br>
_______________________________________________<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"
target="_blank" moz-do-not-send="true">Qgis-community-team@lists.osgeo.org</a><br>
<a
href="https://lists.osgeo.org/mailman/listinfo/qgis-community-team"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/qgis-community-team</a></blockquote>
</div>
-- <br>
<div dir="ltr" class="gmail_signature"
data-smartmail="gmail_signature">
<div dir="ltr">
<div>Alexandre Neto</div>
<div>---------------------</div>
<div>@AlexNetoGeo</div>
<div><a href="http://sigsemgrilhetas.wordpress.com"
moz-do-not-send="true">http://sigsemgrilhetas.wordpress.com</a></div>
<a href="http://gisunchained.wordpress.com"
moz-do-not-send="true">http://gisunchained.wordpress.com</a><br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Qgis-community-team mailing list for organizing community resources such as documentation, translation etc..
<a class="moz-txt-link-abbreviated" href="mailto:Qgis-community-team@lists.osgeo.org" moz-do-not-send="true">Qgis-community-team@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/qgis-community-team" moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/qgis-community-team</a></pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Paolo Cavallini - <a class="moz-txt-link-abbreviated" href="http://www.faunalia.eu" moz-do-not-send="true">www.faunalia.eu</a>
QGIS.ORG Chair:
<a class="moz-txt-link-freetext" href="http://planet.qgis.org/planet/user/28/tag/qgis%20board/" moz-do-not-send="true">http://planet.qgis.org/planet/user/28/tag/qgis%20board/</a></pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Qgis-community-team mailing list for organizing community resources such as documentation, translation etc..
<a class="moz-txt-link-abbreviated" href="mailto:Qgis-community-team@lists.osgeo.org">Qgis-community-team@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/qgis-community-team">https://lists.osgeo.org/mailman/listinfo/qgis-community-team</a></pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
<a class="moz-txt-link-freetext" href="http://yjacolin.gloobe.org">http://yjacolin.gloobe.org</a></pre>
</body>
</html>