Re: [Qgis-community-team] QGIS documentation translation best-practices

[Yves Jacolin]

Hello,

I am currently using transifex for all translation project (MapServer, PostGIS 
and QGIS).

As Matteao explain you can download po files from transifex but I have never 
user transifex this way.

Regards,

Y.
Le vendredi 4 avril 2014, 16:32:02 matteo a écrit :
> Hi Eduardo,
> I'm working on the Italian translations (GUI, documentation and website).
> 
> You can use Transifex to translate the documentation and the website,
> but you can also download the .po files from transifex and use an
> offline editor to translate.
> 
> I think that almost all the translator use QT Linguist to translate,
> but it is up to you.
> If you choose this method, once you finished to translate, you have to
> upload the files on transifex.
> 
> If you use transifex the entire work flow is automatic updated.
> 
> 
> GUI translation is a little bit more difficult: you have to download
> the file from github, use QT-Linguist (or another editor) and then
> "push" the translated file (.ts) on github performing a *pull request*.
> 
> 
> My suggestions are:
> - use Transifex to translate when possible, so documentation and
> website (people worked very hard to allow the use of this tool)
> - explore all the Transifex possibilities (glossary, translation
> memory...). On the Transifex website you can find a lot of help
> - use QT-Linguist if you don't want to use Transifex; if you get
> trouble, qgis translator can help you faster
> 
> 
> Cheers
> 
> Matteo
> 
> 
> 
> 
> 
> 
> ___
> Qgis-community-team mailing list for organizing community resources such as
> documentation, translation etc.. Qgis-community-team@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-community-team

-- 
Yves Jacolin
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] geometric functions of field calculator

[Yves Jacolin]

Hello,

I did some documentation in french with some easy/simple example.

I can share my document (this is rst doc) and/or try to find some time to 
contribute.

Regards,

Y.
Le samedi 19 avril 2014, 12:10:46 matteo a écrit :
> > IMHO we need good man pages for each function, with images; then
> > we should reuse them as help in the application itself.
> 
> yes, this sounds as a good solution.
> Now, who can start this? I mean, I could, but I'm really confused
> about some function.
> 
> Can we fork the documentation from somewhere (like those of other
> functions that are the same in Libreoffice for example)?
> 
> > I know the focus is theoretically slightly different, but in
> > practice this is good enough, and far easier to maintain, without
> > duplication.
> 
> +1
> I think it would be a good solution, once we have an almost clear
> idea, to fill a wiki or something similar.
> 
> Cheers
> 
> Matteo
> 
> 
> ___
> Qgis-community-team mailing list for organizing community resources such as
> documentation, translation etc.. Qgis-community-team@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-community-team

-- 
Yves Jacolin
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] screenshot of the user manual

[Yves Jacolin]

On Friday, October 03, 2014 17:31:08 matteo wrote:
> Hi all,
> I'm updating some section of the user manual. In some cases I noticed
> that we have to change the screenshots. For example in
> qgis_configuration [0] in the current screenshot there isn't displayed
> the new **Color** menu.
> 
> If I'm not wrong is Alexandre that is responsible for the pictures
> right? So Alexandre, what is the best way to inform you about this issues?
> 
> Cheers
> 
> Matteo
> 
> 
> 
> [0]http://docs.qgis.org/testing/en/docs/user_manual/introduction/qgis_config
Matteo,

There are two ways to do so. 

#1 If you have a row in the manualTask wiki page, add 'yes' to the last 
column.

#2 If this is not new (so rather a missing feature), you can create an issue 
in github repository and add screnshot label (and assign the ticket to him).

Y.

___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

[Qgis-community-team] Tips in QGIS

[Yves Jacolin]

Hello,

I am wondering how to add new tips in the tips dialog in QGIS. I have some 
ideas to add:

* clic on mouse wheel to pan
* right clic to identify and choose a layer/feature
* Ctr+c, ctrl+v, ctr+x and ctr+z shorcut
* dizzy and retro renderer :)
* add an action

If you have other idea I will be happy to add them (if I can find how ;) )

Thanks,

Y.
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

[Qgis-community-team] Update translation for training

[Yves Jacolin]

Hello,

Is it possible to get an update of the french translation of the training 
manual? One of my workmet worked on this the last few weeks.

It is not urgent, of course :)

Thanks in advance.

Y.
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] Update translation for training

[Yves Jacolin]

On Friday, October 10, 2014 10:23:23 Richard Duivenvoorde wrote:
> reading sources... [ 23%]
> docs/training_manual/complete_analysis/raster_to_vector
> reading sources... [ 23%]
> docs/training_manual/create_vector_data/actions
heyhey :) This is the chapter that my workmet wored on

I will check this week-end !

Y.
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] Update translation for training

[Yves Jacolin]

Le vendredi 10 octobre 2014, 10:23:23 Richard Duivenvoorde a écrit :
> On 10-10-14 09:21, Yves Jacolin wrote:
> > Hello,
> > 
> > Is it possible to get an update of the french translation of the training
> > manual? One of my workmet worked on this the last few weeks.
> > 
> > It is not urgent, of course :)
> 
> Hi Yves,
> 
> good that you note. Because we build every day now (look at other
> languages), so french should be build tonight too.
> (you can see in the footer of the doc frontpage when the last build was)
> 
> but looking into the log I see there is an error only in french, so
> probably something in translation.
> If possible, can you have a look yourself, or somebody else? You have to
> build fr specifically, other languages seem ok.
> 
> 
> Or else I will try to have a look at it somewhere this weekend.
> 
> The error from the log:
> 
> 
> reading sources... [ 23%]
> docs/training_manual/complete_analysis/raster_to_vector
> reading sources... [ 23%]
> docs/training_manual/create_vector_data/actions
> 
> 
> Exception occurred:
> 
>   File "/usr/local/lib/python2.7/dist-packages/docutils/nodes.py", line
> 569, in __getitem__
> return self.children[key]
> 
> IndexError: list index out of range
> 
> The full traceback has been saved in /tmp/sphinx-err-4jpMF_.log, if you
> want to report the issue to the developers.
> Please also report this if it was a user error, so that a better error
> message can be provided next time.
> Either send bugs to the mailing list at
> <http://groups.google.com/group/sphinx-users/>,
> or report them in the tracker at
> <http://bitbucket.org/birkenfeld/sphinx/issues/>. Thanks!
> make[1]: *** [html] Error 1
> 
> make: *** [full] Error 2
> 
> make[1]: Leaving directory `/build'
> 
> sending incremental file list
> 
> 
> Regards,
> 
> Richard Duivenvoorde
Richard,

I built fr documentation with sucess and I can't see any problem. Frontpage 
for french translation shows that the last build was today around 17h00.

Did you work on this before me?

Thanks,


Y.
-- 
Yves Jacolin
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] Update translation for training

[Yves Jacolin]

Le samedi 11 octobre 2014, 21:50:09 Richard Duivenvoorde a écrit :
> > I built fr documentation with sucess and I can't see any problem.
> > Frontpage
> > for french translation shows that the last build was today around 17h00.
> > 
> > Did you work on this before me?
> 
> Nope, but I think somebody else fixed a translation that gave the problem?
> 
> Hope all is fine now.
> 
> Regards,
> 
> Richard
hum, but I forget to said that some chapter are not translated both in my 
local build and in the website but they have been translated in transifex (see 
trainings manual > Creator vector file > Actions

http://docs.qgis.org/2.2/fr/docs/training_manual/create_vector_data/actions.html

And there is a problem with the release number, isn't it? Should it be 2.4?

Y.
-- 
Yves Jacolin
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] Update translation for training

[Yves Jacolin]

Le samedi 11 octobre 2014, 23:10:45 Richard Duivenvoorde a écrit :
> On 11-10-14 22:26, Yves Jacolin wrote:
> > Le samedi 11 octobre 2014, 21:50:09 Richard Duivenvoorde a écrit :
> >>> I built fr documentation with sucess and I can't see any problem.
> >>> Frontpage
> >>> for french translation shows that the last build was today around 17h00.
> >>> 
> >>> Did you work on this before me?
> >> 
> >> Nope, but I think somebody else fixed a translation that gave the
> >> problem?
> >> 
> >> Hope all is fine now.
> >> 
> >> Regards,
> >> 
> >> Richard
> > 
> > hum, but I forget to said that some chapter are not translated both in my
> > local build and in the website but they have been translated in transifex
> > (see trainings manual > Creator vector file > Actions
> > 
> > http://docs.qgis.org/2.2/fr/docs/training_manual/create_vector_data/action
> > s.html
> > 
> > And there is a problem with the release number, isn't it? Should it be
> > 2.4?
> 
> Release number is still 2.2 because the docs had not been updated for
> 2.4 but we will probably release a new 2.6(!) version around the QGIS
> 2.6 release.
> 
> About the french build problem:
> 
> http://docs.qgis.org/2.2/fr/docs/ still shows 25 sept.
> 
> But the github translations are behind with the transifex translations.
> Transifex holds the latest version, and the scripts build based on the
> latest transifex version by pulling the latest version via the
> tx-command line tool (see the make file).
> 
> So can only reproduce the problem if you take the latest version from
> transifex, OR somebody pulls and puts in it Github...
> I just pulled all translations from transifex and pushed them to github,
> so now your build should fail :-)
> 
> Hope this helps,
> 
> Regards,
> 
> Richard Duivenvoorde
Richard,

Thanks, I find the problem. There is a empty msgstr (not a null one):
msgstr "  "

I am going to push the fix and correct it in transifex as soon as my build 
finished.

This is a bug from sphinx-i18n, imho.

Y.
-- 
Yves Jacolin
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] Pulling 'how to translate' to one place

[Yves Jacolin]

Le lundi 17 novembre 2014, 09:42:48 Richard Duivenvoorde a écrit :
> Hi,
> 
> Now documentation 2.6 is near, and hopefully will have a lot of
> translated versions, I thought to have a look at the different places
> where we have 'documentation/rules' about how to translate:
> 
> http://qgis.org/en/site/getinvolved/index.html#translate
> 
> is now pointing to the pretty up to date:
> 
> http://qgis.org/en/site/getinvolved/translate.html
> 
> Here there is also a pretty extensive text about how to translate:
> 
> http://docs.qgis.org/testing/en/docs/documentation_guidelines/do_translation
> s.html
> 
> And some other translation text:
> https://github.com/qgis/QGIS-Documentation#translating-the-english-qgis-docu
> mentation
> 
> 
> I propose the following:
> - only use the link to
> http://qgis.org/en/site/getinvolved/translate.html
> as the canonical place where you find up to date information about
> translating both docs, site and application.
> - all other links above will link tot that site
> 
> (first I thought to use the link in the actual documentation website,
> but because that one is 'versioned' we would have to update both the
> 'testing' as the last '2.x' version in case we change the translation
> tool chain during a release cycle, or when we 'skip' an documentation
> release like we did now)
> 
> I everybody agrees, I will try to do this this week, so we have a
> uptodate version of this in the 2.6 documentation.
> 
> Regards,
> 
> Richard Duivenvoorde
> ___
> Qgis-community-team mailing list for organizing community resources such as
> documentation, translation etc.. Qgis-community-team@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-community-team
Richard, All,

I planned to write some guidelines, documentation about the process. First to 
this mailing list then somewhere else more formaly. Do you have an idea about 
where it will be the more best location?

This documentation is for doc writer mainly.

Thanks,

Y.

-- 
Yves Jacolin
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] wrong or inexistent link in Documentation

[Yves Jacolin]

On Wednesday, November 19, 2014 10:39:43 Alexandre Neto wrote:
> I have opened an Github Issue for Documentation.
> 
> https://github.com/qgis/QGIS-Documentation/issues/359
> 
> In the following page, at Command line option --lang there is a link to the
> qgis translation progress that no long exists.
> 
> http://docs.qgis.org/testing/en/docs/user_manual/introduction/getting_starte
> d.html#command-line-options
> 
> The link was
> http://hub.qgis.org/wiki/quantum-gis/GUI_Translation_Progress <-- does not
> exist.
> 
> Is there a new link with this kind of information somewhere?
> 
> Thanks,
> 
Hello Alexandre,

Does the transifex Dashboard could be used for this purpose?

Y.

___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

[Qgis-community-team] Docker for documentation

[Yves Jacolin]

Hello,

In documentation repository there is some script to use docker to build the 
documentation. I would like to use it. The script uses qgis/sphinx but the 
qgis docker hub is empty.

Does someone could push this image in the QGIS docker hub?

I would like to test the build of the documentation because someone told me 
that there are a problem with the translation update.

Thanks,

Y.
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] Docker for documentation

[Yves Jacolin]

Thanks Werner,

Anyway, which scripts are we talking about? :)

I have :
* docker-run.sh which need qgis/sphinx
* docker-world.sh which is not useful for me

May I miss something?

Y.



On Wednesday, November 19, 2014 13:03:09 Werner Macho wrote:
> Hi Yves!
> 
> The script should build the docker image. (that way you are always up to
> date) And IIRC it should use nearly the same bandwith as the prepared image
> has .. so nearly no advantage on this side.
> 
> Unless you really don't want to build it by yourself (I can copy the
> image to my Dropbox account for download).
> 
> Beside that: I did not know we have a qgis docker hub :)
> 
> kind regards
> Werner
> 
> On Wed, Nov 19, 2014 at 11:40 AM, Yves Jacolin  wrote:
> > Hello,
> > 
> > In documentation repository there is some script to use docker to build
> > the
> > documentation. I would like to use it. The script uses qgis/sphinx but the
> > qgis docker hub is empty.
> > 
> > Does someone could push this image in the QGIS docker hub?
> > 
> > I would like to test the build of the documentation because someone told
> > me
> > that there are a problem with the translation update.
> > 
> > Thanks,
> > 
> > Y.

___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] Issue on Website : strange behaviour of font displaying in french language

[Yves Jacolin]

Le jeudi 20 novembre 2014, 15:24:24 Richard Duivenvoorde a écrit :
> On 20-11-14 15:02, Junior Delaz wrote:
> > Hi all,
> > There are some items that display differently in the website french (or
> > italian) version than in english[0] . Look at how is displayed the list
> > of names under "Packager Team" in the different languages.
> > 
> > [0]
> > http://www.qgis.org/fr/site/getinvolved/governance/organisation/governance
> > .html
> Mmm, it appears that as soon as it is translated, this 'bold' text pops
> up
> 
> Languages which have NO translation look ok, languages WITH translation
> (like Russian) start looking wrong.
> 
> Trying to relate it to recent commits:
> 
> https://github.com/qgis/QGIS-Website/commits/master/source/site/getinvolved/
> governance/organisation/governance.rst
> 
> does not ring a bell to me yet...
> 
> Anybody a clue?
> 
> Regards,
> 
> Richard Duivenvoorde

We have this html code in the english version:

Gary Sherman (Chair)

and this in the french version:

Gary Sherman (Président)

the css class "first" have a bottom margin of 10px from boostrap.css file.

May the  tag be due to transifex?

Y.

-- 
Yves Jacolin
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

[Qgis-community-team] GetInvolved > Documentation update

[Yves Jacolin]

Hello,

I am working on the documention page in getinvolved chapter website [1]

The first paragraph gives a link to the "Community Team Lead" which is the GUI 
Translation Team Lead (Werner).

Is it something true? Do we need to add a paragraph about the documentation 
team lead (Otto ?).

Thanks,

Y.
PS : this is a first mail about this task, you probably get another later :)
[1] http://qgis.org/en/site/getinvolved/document.html
-- 
Yves Jacolin
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] GetInvolved > Documentation update

[Yves Jacolin]

Le samedi 22 novembre 2014, 20:05:24 Yves Jacolin a écrit :
> Hello,
> 
> I am working on the documention page in getinvolved chapter website [1]
> 
> The first paragraph gives a link to the "Community Team Lead" which is the
> GUI Translation Team Lead (Werner).
> 
> Is it something true? Do we need to add a paragraph about the documentation
> team lead (Otto ?).
> 
> Thanks,
> 
> Y.
> PS : this is a first mail about this task, you probably get another later :)
> [1] http://qgis.org/en/site/getinvolved/document.html

I changed the link to "community-resources" rather than "gui-translation". Do 
you agreed?

I think this is more relevant.

Another question: anybody know if there is github hook for QGIS somewhere? I 
would like to contribute to create a ticket in qgis documentation each time a 
commit contains a 'FEATURE' keyword.

Thanks,

Y.
-- 
Yves Jacolin
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] Please finalise work on documentation

[Yves Jacolin]

Le samedi 29 novembre 2014, 09:17:45 Diethard Jansen a écrit :
> Hello everyone.
> 
> Please try to finalise work on documentation for release this weekend.
> 
> I also propose to keep the contents on the chapter what's new to the
> minimum. It is now almost empty but when we only include references to
> visual changes for 2.4 and 2.6 this should do.
> 
> I would not mind if on monday a branch for QGIS documentation version 2.6
> is created and release of documentation can start.
> 
> After creation of branch 2.6 we still can continue to improve documentation
> in branch master and a few months from now we can release a polished
> version 2.6.1.
> 
> Any objections?
> 
> Regards,
> Diethard Jansen
Hello,

I have just closed two tickets. The last one is #278 [1]. I have no idea how 
it should work. It seems only working with WMS layers.

If you have any idea :)

Y.
[1] https://github.com/qgis/QGIS-Documentation/issues/278
-- 
Yves Jacolin
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] QGIS Documentation 2.6 branched and released

[Yves Jacolin]

thanks Richard and all of the community team for the work done in this 
documentation!

Y.
On Wednesday, December 03, 2014 8:15:21 Junior Delaz wrote:
> Hi all,
> Thanks Richard and others for the work you've done. Great!
> 
> I would like to remind you to replace "QGIS Testing" mention by "QGIS2.6"
> in the main title of "User Guide/Manual" (in the TOC -
> http://docs.qgis.org/2.6/fr/docs/user_manual/index.html)
> 
> Once again, great work
> 
> 2014-12-02 22:57 GMT+01:00 Richard Duivenvoorde :
> > Hi,
> > 
> > today I 'frooze' the 2.2 branch at github by pulling current
> > translations from transifex.
> > 
> > After that I branched master to 2.6, created new transifex sources and
> > uploaded them to transifex: a lot of new strings to translate :-)
> > 
> > To make public I wrote a minimal blogpost both about the 2.6
> > Documentation and 2.6.1 QGIS releases. That should be on planet.qgis.org
> > by now.
> > 
> > Still some work to do (@alexander: I forgot to update the conf.py),
> > but will do that tomorrow.
> > 
> > If you miss something: just let us know: http://docs.qgis.org/2.6
> > 
> > Regards,
> > 
> > Richard Duivenvoorde
> > 
> > ps A build of one language now takes 40 minutes..
> > ___
> > Qgis-community-team mailing list for organizing community resources such
> > as documentation, translation etc..
> > Qgis-community-team@lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/qgis-community-team

___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

[Qgis-community-team] French translation of user manual

[Yves Jacolin]

Hello,

Is it possible to get some statistic on french translation of the user manual. 
For instance, total string vs string untranslated for each files.

Thanks,

Y.
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] French translation of user manual

[Yves Jacolin]

richard,

Le vendredi 9 janvier 2015, 20:29:42 Richard Duivenvoorde a écrit :
> On 09-01-15 17:40, Yves Jacolin wrote:
> > Hello,
> > 
> > Is it possible to get some statistic on french translation of the user
> > manual. For instance, total string vs string untranslated for each files.
> 
> Hi Yves,
> 
> If I'm logged in, the following url shows me per resource how many
> strings are translated:
> 
> https://www.transifex.com/projects/p/qgis-documentation/language/fr/
> 

hehe:

"Looks like you do not have the necessary permissions for the required action.

Here's a link to the homepage. You know, just in case."


> This thread:
> 
> http://lists.osgeo.org/pipermail/qgis-community-team/2014-November/003937.ht
> ml
> 
> points to some work of the Portugese community which shows the total
> number of translations per subproject:
> 
> http://www.qgis.pt/traducao.html
> 
> Hugo pointed me to this python script they use:
> 
> https://github.com/qgispt/site/blob/master/services/get_statistics.py
> 
> which uses transifex's python REST interface to get stats per resource.
> Change the langcode, user ans password, and you can print out french stats.
> 
> With some work we could at least show the totals per language somewhere
> in the website, but also the stats per resource is possible.
I will test the python commande this week-end.

Thanks !

Y.

-- 
Yves Jacolin
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

[Qgis-community-team] QGIS LTR and documentation (LTR ?)

[Yves Jacolin]

Hello,

QGIS 2.8 should be the first LTR. For this release, fix would be backported for 
one year. 

What about the documentation? Can we think a similar support to have the time 
to translate it and correct typo? 

Could this managed in transifex or is just too complex to managed 2 releases 
in the same time?

Thanks,

Y.
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] QGIS 2.8 Documentation update - use git issues for tasks?

[Yves Jacolin]

Larissa,

The proposition was to create issue for each commit in this way we 
(documentors) can be assigned to a ticket and work on this. We can add a link 
between the issue and the pull resquest, have a proof review, etc.

Currently, taks are still in the wiki which give you some work and is not easy 
to used (slow and it is difficult to see how task are done). We can keep this 
way for the QGIS 2.8 documentation.

I am pretty sure that using git issue will improve the process. Unfortunately 
I have no skills to to the automatic magic script to add a new issue when a 
commit is done with flags [FEATURE], etc. So I can't help for this last step.

Regards,

Y.


On Thursday, February 12, 2015 15:04:30 Larissa Junek wrote:
> Hello Alexandre,
> 
> I have some ressources for contributing to the new user manual. I found
> a new list on the Manual Tasks site and completed it. Are you talking
> about git log messages (= issues in documentation)?
> 
> Just tell me if there is a new procedure for writing the manual.
> Otherwise I just go on with my work and start to include the new
> information.
> 
> Kind regards,
> Larissa
> 
> Am Thu, 22 Jan 2015 10:42:56 +
> 
> schrieb Alexandre Neto :
> > Hello all,
> > 
> > With the feature freeze near by, we will enter in documentation update
> > phase again (this time LTS :)).
> > 
> > Following Yves recommendation, will we be using git issues to track
> > tasks this time?
> > 
> > Is there a way to transform [Feature] and [gui] tags in issues in
> > documentation?
> > 
> > Thanks,
> > 
> > Alexandre Neto
> 
> ___
> Qgis-community-team mailing list for organizing community resources such as
> documentation, translation etc.. Qgis-community-team@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-community-team

___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] Documentation guidelines

[Yves Jacolin]

On Wednesday, February 25, 2015 12:58:18 Paolo Cavallini wrote:
> Hi all.
> I noticed there are two places where guidelines are listed:
> 
> https://github.com/qgis/QGIS-Documentation/tree/master/source/docs/documenta
> tion_guidelines
> 
> https://github.com/qgis/QGIS-Documentation/blob/master/source/docs/user_manu
> al/preamble/conventions.rst
> 
> Wouldn't it be better to unify them?
> All the best.
Paolo,

For me both are a little bit different. conventions is read by the user to 
understand the text (so it should be in the documentation), 
documentation_guidelins aims to be read by documentors, ie which tags should 
be used for writing the documentation (so it should be located in the source, 
not in the final documentation).

Y.
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] new procedures when working on the user manual

[Yves Jacolin]

On Friday, February 27, 2015 13:46:01 Larissa Junek wrote:
> Am Fri, 27 Feb 2015 13:43:54 +0100
> 
> schrieb Larissa Junek :
> > Dear all,
> > I'd like to discuss the new procedure for the teamwork on the user
> > manual. I like using git issues to manage our work. To have an
> > overview I think it's still necessary to keep the Manual Task list
> > where you can see all the commits that need to be considered.
> > 
> > What do you think? Or is there a function in git issues where one can
> > get an overview?
> > 
> > All the best,
> > Larissa
> > ___
> > Qgis-community-team mailing list for organizing community resources
> > such as documentation, translation etc..
> > Qgis-community-team@lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/qgis-community-team
> 
> Actually I won't be at the next developer meeting, so I open the debate
> already now (-:

Here my thought about this. The process could be the following: 
each commit in QGIS core git repository create an issue in Doc git repository 
if [FEATURE] and/or [SCREENSHOOT] is in the description.

We can also add a screenshoot label to the ticket, add the commit link in the 
ticket description with the commit comment.

An admin can add the ticket to a milestome, ie 2.8, 2.8.1 or so.

We can assign to someone, who should be notified by github, add a comment, 
review a PR.

We can ask to someone else to review the PR or just let the writer the choice 
about create a PR or not.

So, I think keeping the wiki page is a work

Y.


___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] FW: Proposed questions for QGIS Certification questionnaire

[Yves Jacolin]

---
> > - Kartoza is a merger between Linfiniti and Afrispatial
> > 
> > This message has been scanned for viruses by MailControl
> > <http://www.mailcontrol.com/>, a service from BlackSpider Technology
> > Click here <https://www.mailcontrol.com/sr/MZbqvYs5QwJvpeaetUwhCQ==> to
> > report this email as spam.
> > 
> >  --
> >  *HR Wallingford and its subsidiaries* uses faxes and emails for
> > 
> > confidential and legally privileged business communications. They do not
> > of
> > themselves create legal commitments. Disclosure to parties other than
> > addressees requires our specific consent. We are not liable for
> > unauthorised disclosures nor reliance upon them.
> > If you have received this message in error please advise us immediately
> > and destroy all copies of it.
> > 
> > HR Wallingford Limited
> > Howbery Park, Wallingford, Oxfordshire, OX10 8BA, United Kingdom
> > Registered in England No. 02562099
> > 
> >  --
> >  
> >  
> >  
> >  ___
> > 
> > Qgis-community-team mailing list for organizing community resources such
> > as documentation, translation etc..
> > 
> > Qgis-community-team@lists.osgeo.org
> > 
> > http://lists.osgeo.org/mailman/listinfo/qgis-community-team
> > 
> >  --
> > 
> > -
> > 
> > Randal Hale
> > 
> > North River Geographic Systems, Inc
> > 
> > http://www.northrivergeographic.com
> > 
> > 423.653.3611 rjh...@northrivergeographic.com
> > 
> > twitter:rjhale http://about.me/rjhale
> > 
> > http://www.northrivergeographic.com/introduction-to-quantum-gis
> > 
> >  --
> >  *HR Wallingford and its subsidiaries* uses faxes and emails for
> > 
> > confidential and legally privileged business communications. They do not
> > of
> > themselves create legal commitments. Disclosure to parties other than
> > addressees requires our specific consent. We are not liable for
> > unauthorised disclosures nor reliance upon them.
> > If you have received this message in error please advise us immediately
> > and destroy all copies of it.
> > 
> > HR Wallingford Limited
> > Howbery Park, Wallingford, Oxfordshire, OX10 8BA, United Kingdom
> > Registered in England No. 02562099
> > 
> >  --
> > 
> > --
> > 
> > -
> > 
> > Randal Hale
> > 
> > North River Geographic Systems, Inc
> > 
> > http://www.northrivergeographic.com
> > 
> > 423.653.3611 rjh...@northrivergeographic.com
> > 
> > twitter:rjhale http://about.me/rjhale
> > 
> > http://www.northrivergeographic.com/introduction-to-quantum-gis
> > 
> > 
> > --
> > *HR Wallingford and its subsidiaries* uses faxes and emails for
> > confidential and legally privileged business communications. They do not
> > of
> > themselves create legal commitments. Disclosure to parties other than
> > addressees requires our specific consent. We are not liable for
> > unauthorised disclosures nor reliance upon them.
> > If you have received this message in error please advise us immediately
> > and destroy all copies of it.
> > 
> > HR Wallingford Limited
> > Howbery Park, Wallingford, Oxfordshire, OX10 8BA, United Kingdom
> > Registered in England No. 02562099
> > 
> >  --
> > 
> > ___
> > Qgis-community-team mailing list for organizing community resources such
> > as documentation, translation etc..
> > Qgis-community-team@lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/qgis-community-team
> > 
> > 
> > 
> > ___
> > Qgis-community-team mailing list for organizing community resources such
> > as documentation, translation etc..
> > Qgis-community-team@lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/qgis-community-team
> > 
> > 
> > 
> > 
> > --
> > 
> > --
> >  Tim Sutton
> > 
> > Visit http://kartoza.com to find out about open source:
> >  * Desktop GIS programming services
> >  * Geospatial web development
> > 
> > * GIS Training
> > * Consulting Services
> > Skype: timlinux Irc: timlinux on #qgis at freenode.net
> > Tim is a member of the QGIS Project Steering Committee
> > 
> > --
> > - Kartoza is a merger between Linfiniti and Afrispatial
> > 
> > 
> > ___
> > Qgis-community-team mailing list for organizing community resources such
> > as documentation, translation etc..
> > Qgis-community-team@lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/qgis-community-team

-- 
Yves Jacolin
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] new procedures when working on the user manual

[Yves Jacolin]

+1 for me. :)

Y.
On Tuesday, March 17, 2015 12:31:17 Larissa Junek wrote:
> Good idea!
> Best regards,
> Lariss Junek
> 
> Am Tue, 17 Mar 2015 10:06:13 +
> 
> schrieb Alexandre Neto :
> > Any objections to creating 3 new labels to separate documentation
> > items?
> > 
> > - User guide
> > - PyQGIS cookbook
> > - Gentle introduction
> > 
> > Best regards,
> > 
> > Alexandre Neto
> > 
> > On Tue, Mar 3, 2015 at 3:10 PM, Alexander Bruy
> > 
> >  wrote:
> > > 2015-03-03 17:04 GMT+02:00 Larissa Junek :
> > > > Who will be in charge to realize that each commit in QGIS core git
> > > > repository creates an issue in Doc git repository if [FEATURE]
> > > > and/or [SCREENSHOOT] is in the description?
> > > 
> > > I'm not sure, but seems this can be done with git hooks. We need to
> > > ask someone with admin access to our GitHub. Maybe Tim or Jurgen.
> > > 
> > > --
> > > Alexander Bruy
> 
> ___
> Qgis-community-team mailing list for organizing community resources such as
> documentation, translation etc.. Qgis-community-team@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-community-team

___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] QUGs

[Yves Jacolin]

On Wednesday, April 01, 2015 9:52:02 Paolo Cavallini wrote:
> Il 01/04/2015 09:49, Andreas Neumann ha scritto:
> > Works fine for me:
> > 
> > If I google search QGIS and Switzerland
> > 
> > https://www.google.ch/search?client=ubuntu&channel=fs&q=QGIS%C2%A0Switzerl
> > and&ie=utf-8&oe=utf-8&gfe_rd=cr&ei=v6IbVee3K8eX8QfcqIGoCg
> > 
> > first hit is qgis.ch/en
> 
> I tried this:
> 
> https://www.google.it/search?q=qgis+user+group+switzerland&ie=utf-8&oe=utf-8
> &gws_rd=cr&ei=b6MbVcC2EcHjUdqtgqAJ
> 
> not a big deal though, just FYI.
> All the best.
Paolo,

I get it in the second link with your url ;)

Google made a choice for you before sending the result.

Y.
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] statistics from transifex

[Yves Jacolin]

Matteo,

The script I sent to you come from there.

Y.

Le 30 mars 2015 20:44, Werner Macho  a écrit :
>
> -BEGIN PGP SIGNED MESSAGE- 
> Hash: SHA1 
>
> hi! 
> The portuguese users have made use of this I think 
>
> Hi and thanks for your interest! 
>
> http://qgis.pt/traducao.html 
>
> Probably they can help in what you'd like to do 
>
> kind regards 
> Werner 
>
>
> On 03/30/2015 04:59 PM, matteo wrote: 
> > Hi all, is there a simple way to get statistics from transifex? 
> > Something like translated strings, how many strings have been 
> > translated by a translator, ecc... 
> > 
> > I found this: 
> > 
> > http://docs.transifex.com/developer/api/statistics 
> > 
> > but I don't get any output.. 
> > 
> > Thanks 
> > 
> > Cheers 
> > 
> > Matteo ___ 
> > Qgis-community-team mailing list for organizing community resources 
> > such as documentation, translation etc.. 
> > Qgis-community-team@lists.osgeo.org 
> > http://lists.osgeo.org/mailman/listinfo/qgis-community-team 
> -BEGIN PGP SIGNATURE- 
> Version: GnuPG v2.0.20 (GNU/Linux) 
>
> iEUEARECAAYFAlUZmZUACgkQDAH1YiCxBgnTnQCeOyzS2VT7hgt2SHmsYEWV0LxD 
> il0AmPYK3CzANiGl1dYCCU733CiVAe8= 
> =eCq2 
> -END PGP SIGNATURE- 
> ___ 
> Qgis-community-team mailing list for organizing community resources such as 
> documentation, translation etc.. 
> Qgis-community-team@lists.osgeo.org 
> http://lists.osgeo.org/mailman/listinfo/qgis-community-team 
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] statistics from transifex

[Yves Jacolin]

Hello,

I have such script on my laptops. I will try to send you offlist this evening.

Y.

Le 30 mars 2015 16:59, matteo  a écrit :
>
> Hi all, 
> is there a simple way to get statistics from transifex? Something like 
> translated strings, how many strings have been translated by a 
> translator, ecc... 
>
> I found this: 
>
> http://docs.transifex.com/developer/api/statistics 
>
> but I don't get any output.. 
>
> Thanks 
>
> Cheers 
>
> Matteo 
> ___ 
> Qgis-community-team mailing list for organizing community resources such as 
> documentation, translation etc.. 
> Qgis-community-team@lists.osgeo.org 
> http://lists.osgeo.org/mailman/listinfo/qgis-community-team 
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

[Qgis-community-team] Add reviewer

[Yves Jacolin]

Hello,

Is it possible to add me in the french reviewer team please ? :)

Thanks,

Y.

___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] Add reviewer

[Yves Jacolin]

Hello Jean-Roc and Werner,

no, only for the documentation for the moment.

I will try to find thje right button to ask this on transifex directly ;) 

Y.
On Tuesday, May 19, 2015 11:49:01 Jean-Roc Morreale wrote:
> Hi Yves, if it's for the desktop translation I don't see your account on
> the transifex team page
> 
> Le 2015-05-19 11:26, Werner Macho a écrit :
> > Hi!
> > 
> > Sure - if you apply for being added either JRM or anyone else
> > responsible is going to add you :)
> > 
> > kind regards
> > Werner
> > 
> > On Tue, May 19, 2015 at 10:51 AM, Yves Jacolin 
> > 
> > wrote:
> >> Hello,
> >> 
> >> Is it possible to add me in the french reviewer team please ? :)
> >> 
> >> Thanks,
> >> 
> >> Y.
> 
> ___
> Qgis-community-team mailing list for organizing community resources such as
> documentation, translation etc.. Qgis-community-team@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-community-team

___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] Add reviewer

[Yves Jacolin]

ok I can't be both a translator and a reviewer!

Do you know if a reviewer can translate? I guess so.

Y.
On Tuesday, May 19, 2015 12:01:39 Yves Jacolin wrote:
> Hello Jean-Roc and Werner,
> 
> no, only for the documentation for the moment.
> 
> I will try to find thje right button to ask this on transifex directly ;)
> 
> Y.
> 
> On Tuesday, May 19, 2015 11:49:01 Jean-Roc Morreale wrote:
> > Hi Yves, if it's for the desktop translation I don't see your account on
> > the transifex team page
> > 
> > Le 2015-05-19 11:26, Werner Macho a écrit :
> > > Hi!
> > > 
> > > Sure - if you apply for being added either JRM or anyone else
> > > responsible is going to add you :)
> > > 
> > > kind regards
> > > Werner
> > > 
> > > On Tue, May 19, 2015 at 10:51 AM, Yves Jacolin 
> > > 
> > > wrote:
> > >> Hello,
> > >> 
> > >> Is it possible to add me in the french reviewer team please ? :)
> > >> 
> > >> Thanks,
> > >> 
> > >> Y.
> > 
> > ___
> > Qgis-community-team mailing list for organizing community resources such
> > as
> > documentation, translation etc.. Qgis-community-team@lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/qgis-community-team
> 
> ___
> Qgis-community-team mailing list for organizing community resources such as
> documentation, translation etc.. Qgis-community-team@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-community-team

___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] Add reviewer

[Yves Jacolin]

Thanks to all!

I will do some review this week or later following the release of 2.8 
documentation.

Y.
On Tuesday, May 19, 2015 17:42:38 Junior wrote:
> Hi Yves,
> Reviewer is a translator that can approve other's translations or modify
> translations already approved. So, yes, you can still translate.
> 
> Envoyé depuis mon HTC
> 
> - Reply message -
> De : "Yves Jacolin" 
> Pour : 
> Objet : [Qgis-community-team] Add reviewer
> Date : mar., mai 19, 2015 14:17
> 
> ok I can't be both a translator and a reviewer!
> 
> Do you know if a reviewer can translate? I guess so.
> 
> Y.
> 
> On Tuesday, May 19, 2015 12:01:39 Yves Jacolin wrote:
> > Hello Jean-Roc and Werner,
> > 
> > no, only for the documentation for the moment.
> > 
> > I will try to find thje right button to ask this on transifex directly ;)
> > 
> > Y.
> > 
> > On Tuesday, May 19, 2015 11:49:01 Jean-Roc Morreale wrote:
> > > Hi Yves, if it's for the desktop translation I don't see your account on
> > > the transifex team page
> > > 
> > > Le 2015-05-19 11:26, Werner Macho a écrit :
> > > > Hi!
> > > > 
> > > > Sure - if you apply for being added either JRM or anyone else
> > > > responsible is going to add you :)
> > > > 
> > > > kind regards
> > > > Werner
> > > > 
> > > > On Tue, May 19, 2015 at 10:51 AM, Yves Jacolin 
> > > > 
> > > > wrote:
> > > >> Hello,
> > > >> 
> > > >> Is it possible to add me in the french reviewer team please ? :)
> > > >> 
> > > >> Thanks,
> > > >> 
> > > >> Y.
> > > 
> > > ___
> > > Qgis-community-team mailing list for organizing community resources such
> > > as
> > > documentation, translation etc.. Qgis-community-team@lists.osgeo.org
> > > http://lists.osgeo.org/mailman/listinfo/qgis-community-team
> > 
> > ___
> > Qgis-community-team mailing list for organizing community resources such
> > as
> > documentation, translation etc.. Qgis-community-team@lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/qgis-community-team
> 
> ___
> Qgis-community-team mailing list for organizing community resources such as
> documentation, translation etc.. Qgis-community-team@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-community-team

___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] Updating images in Documentation

[Yves Jacolin]

Hello

I merged the 2 PR but I wondered if this not breaks picture path when building 
documentation?

I am building the doc in my laptop but I get some errors link to jinja2glue.py 
file.

Y.
On Monday, June 01, 2015 13:04:52 DelazJ wrote:
> Hi,
> Following this discussion, I opened an issue (
> https://github.com/qgis/QGIS-Documentation/issues/487) and now added two PR
> (for 2.8 and master) that aim to remove from localized documentation all
> the outdated screenshots.
> If someone can merge them, it'd really help (generating QGIS2.8
> documentation with screenshots from 1.x version is not really good..)
> 
> Thanks...
> 
> 2015-03-09 17:57 GMT+01:00 Richard Duivenvoorde :
> > On 09-03-15 17:41, Junior Delaz wrote:
> > > Thanks Richard, I think it's clear.
> > > My main "problem" is that we have in documentation many images from
> > > earlier releases.
> > 
> > http://docs.qgis.org/2.6/fr/docs/user_manual/working_with_vector/supported
> > _data.html#figure-vector-3
> > 
> > http://docs.qgis.org/2.6/fr/docs/user_manual/working_with_vector/vector_pr
> > operties.html#figure-symbology-2> 
> > > ...
> > > and this concern most of the localized images, as they have been added
> > > two years ago. Many things have changed since...
> > > 
> > > I think, instead of having wrong images in another language with the
> > > risk that may confuse the reader, it's better to keep english images.
> > > Then if i want to purge outdated images from the documentation, I just
> > > have to find them in
> > 
> > https://github.com/qgis/QGIs-Documentation/tree/master/resources/otherlang
> > uagethanEN> 
> > > and delete them. Right?
> > 
> > Yep, but even better, do it on the currently translated branch too (that
> > is: manual_en_v2.6)
> > 
> > And this actually makes me think that I think we should actually remove
> > ALL non-english resources from the master(!) branch. Just like we do
> > with the translation (i18n folder)...
> > 
> > Because I think IF people create localized screenshot, they will
> > probably do that in the translation branch we have at that moment.
> > In this case it is always clear where the 'latest' localized images are
> > (on the 'translation' branch).
> > 
> > Right?
> > 
> > Regards,
> > 
> > Richard

___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] Participate in the french documentation

[Yves Jacolin]

Hello,

Jenny sent me an email few minutes before so I answered directly.

I just added a link for transifex user from MapServer documentation I wrote: 
http://mapserver.org/fr/development/translation.html

Y.
On Monday, June 01, 2015 15:36:42 Werner Macho wrote:
> Hi and welcome!
> 
> (I think one of the french coordinators will also reply) ;)
> 
> I think the most important information is there:
> http://www.qgis.org/fr/site/getinvolved/document.html
> 
> So basically get an account on transifex and assign for the
> QGIS-Documentation - after being accepted you can go on with transifex
> and translate.
> 
> Thanks for offering your help.
> 
> kind regards
> Werner
> 
> On Mon, Jun 1, 2015 at 3:26 PM, Jenny Dupuy  wrote:
> > Hi,
> > 
> > I would like to particpate in translating or writing of the French QGIS
> > documentation.
> > Could you explain how the team works and how to join the team ?
> > 
> > Thanks.
> > 
> > Jenny Dupuy
> > 
> > ___
> > Qgis-community-team mailing list for organizing community resources such
> > as
> > documentation, translation etc..
> > Qgis-community-team@lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/qgis-community-team
> 
> ___
> Qgis-community-team mailing list for organizing community resources such as
> documentation, translation etc.. Qgis-community-team@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-community-team

___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] Updating images in Documentation

[Yves Jacolin]

Hello,


thanks for your answer about default path on english image, i didn't know 
that.

About my issu when building the doc is not important. I will try to fix it 
later.

Thanks,

Y.
Le lundi 1 juin 2015, 21:18:59 DelazJ a écrit :
> Hi
> Yves,That's weird. My PR just remove some localised screenshots and if I'm
> not wrong, english screenshots are supposed to be the default path. So that
> shouldn't raise an issue.
> Which documentation were you trying to build? 2.8? I can see that online
> Testing Documentation is already up to date.
> 
> And by the way, Thanks Richard for the "fix me" link at the bottom of the
> pages
> 
> 2015-06-01 14:13 GMT+02:00 Yves Jacolin :
> > Hello
> > 
> > I merged the 2 PR but I wondered if this not breaks picture path when
> > building
> > documentation?
> > 
> > I am building the doc in my laptop but I get some errors link to
> > jinja2glue.py
> > file.
> > 
> > Y.
> > 
> > On Monday, June 01, 2015 13:04:52 DelazJ wrote:
> > > Hi,
> > > Following this discussion, I opened an issue (
> > > https://github.com/qgis/QGIS-Documentation/issues/487) and now added
> > 
> > two PR
> > 
> > > (for 2.8 and master) that aim to remove from localized documentation all
> > > the outdated screenshots.
> > > If someone can merge them, it'd really help (generating QGIS2.8
> > > documentation with screenshots from 1.x version is not really good..)
> > > 
> > > Thanks...
> > > 
> > > 2015-03-09 17:57 GMT+01:00 Richard Duivenvoorde :
> > > > On 09-03-15 17:41, Junior Delaz wrote:
> > > > > Thanks Richard, I think it's clear.
> > > > > My main "problem" is that we have in documentation many images from
> > > > > earlier releases.
> > 
> > http://docs.qgis.org/2.6/fr/docs/user_manual/working_with_vector/supported
> > 
> > > > _data.html#figure-vector-3
> > 
> > http://docs.qgis.org/2.6/fr/docs/user_manual/working_with_vector/vector_pr
> > 
> > > > operties.html#figure-symbology-2>
> > > > 
> > > > > ...
> > > > > and this concern most of the localized images, as they have been
> > 
> > added
> > 
> > > > > two years ago. Many things have changed since...
> > > > > 
> > > > > I think, instead of having wrong images in another language with the
> > > > > risk that may confuse the reader, it's better to keep english
> > > > > images.
> > > > > Then if i want to purge outdated images from the documentation, I
> > 
> > just
> > 
> > > > > have to find them in
> > 
> > https://github.com/qgis/QGIs-Documentation/tree/master/resources/otherlang
> > 
> > > > uagethanEN>
> > > > 
> > > > > and delete them. Right?
> > > > 
> > > > Yep, but even better, do it on the currently translated branch too
> > 
> > (that
> > 
> > > > is: manual_en_v2.6)
> > > > 
> > > > And this actually makes me think that I think we should actually
> > > > remove
> > > > ALL non-english resources from the master(!) branch. Just like we do
> > > > with the translation (i18n folder)...
> > > > 
> > > > Because I think IF people create localized screenshot, they will
> > > > probably do that in the translation branch we have at that moment.
> > > > In this case it is always clear where the 'latest' localized images
> > > > are
> > > > (on the 'translation' branch).
> > > > 
> > > > Right?
> > > > 
> > > > Regards,
> > > > 
> > > > Richard

-- 
Yves Jacolin
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

[Qgis-community-team] French translation of python cookbook show english sentences

[Yves Jacolin]

Hello,

Sorry for the long topic but someone showed me on the documentation that there 
is some issue with the translation.

Just before the "Ressource file" title we can read an english sentence 
(untranslated ?) : 
http://docs.qgis.org/2.8/fr/docs/pyqgis_developer_cookbook/plugins.html#resource-file

But in transifex, this chapter shows a 100 % string translated. Anyone knows 
why this sentence (and others) are missing?

Thanks,

Y.
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] French translation of python cookbook show english sentences

[Yves Jacolin]

Hello,

On Friday, June 05, 2015 13:42:10 DelazJ wrote:
> Hi,
> Yves, are you sure you sent the right link? The page you linked is already
> all in French (except code part, of course), unless it has been fixed after
> your message.

You are right, the sentence is now in french :)
 
> But there are pages on the QGIS website that contain English test although
> this is supposed to be 100% fully translated in French( not exhaustive
> list):
> http://qgis.org/fr/site/getinvolved/document.html#helping-with-an-existing-t
> ranslation (already translated )
> http://qgis.org/fr/site/getinvolved/development/addinggrasstools.html#adding
> -grass-tools (already translated - many subsections in english)
> http://qgis.org/fr/site/getinvolved/development/index.html#credits-for-contr
> ibutions (not yet available in Transifex)

I will check this this week-end,

Thanks,

Y.
 
> 2015-06-05 11:40 GMT+02:00 Yves Jacolin :
> > Hello,
> > 
> > Sorry for the long topic but someone showed me on the documentation that
> > there
> > is some issue with the translation.
> > 
> > Just before the "Ressource file" title we can read an english sentence
> > (untranslated ?) :
> > 
> > http://docs.qgis.org/2.8/fr/docs/pyqgis_developer_cookbook/plugins.html#re
> > source-file
> > 
> > But in transifex, this chapter shows a 100 % string translated. Anyone
> > knows
> > why this sentence (and others) are missing?
> > 
> > Thanks,
> > 
> > Y.
> > ___
> > Qgis-community-team mailing list for organizing community resources such
> > as documentation, translation etc..
> > Qgis-community-team@lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/qgis-community-team

___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] Proposal to divide some pages in QGIS documentation

[Yves Jacolin]

Hello,

A big +1 for this. This is something we need to do some time. I remember did 
it for the vector chapter last year.

I started to read and comment your PR. I need to build it before give more 
comment but the PR seems ok for me except one small thing.

Rst engine will always start with a H1 header with the first symbol line found 
in the rst file.

So each time you use -- for instance, it will become a H1 
header [1]. Same for [2] with   line.

There is two small issues with this:
1. it is less readable for the same level of header, if sometime you use 
"" and another time "==="
2. if later you need to add another (sub)-sectionin [1], you should find 
another symbol, so it will be probably one of ***, , +++ and they will 
look a greater level (only to me?).

We should keep rst file human readable.

I will build your PR tomorrow if no one merge your PR before :)

Y.
[1] composer_items/composer_scale_bar.rst
[2] print_composer/first_steps.rst with

Le samedi 6 juin 2015, 01:22:26 DelazJ a écrit :
> Hi Folks,
> 
> While reading QGIS documentation, there are some pages that leave me
> puzzled. You may have a look at Print Composer [1], vector properties
> dialog [2] pages.
> IMHO, these pages are too long. For the reader, scrolling can become
> tedious while looking for a precise information. Sure, the subject is wide
> and there is a lot of informations at these pages but I think that, because
> subject is wide, it can be splited into several pages, shorter, more
> precise and readable. As there are Previous/Next buttons, skipping sections
> while reading can easily be done.
> From writer side, I think that having short (and specialized) page helps us
> to quickly identify where there may be a lack of documentation, easily
> update or improve them...
> 
> So, few days ago, I made a pull request [3] that splits Print Composer
> chapter into many pages, reorganizing sections and sequences.
> 
> If you agree with the spliting principle of these chapters, can some
> documentation writers review it, amend it and let me know if it is ok? It's
> the first time I use rst files so it'd be nice if someone can review my PR
> before I begin spliting vector properties chapter.
> 
> Regards,
> Harrissou
> 
> [1]
> http://docs.qgis.org/2.8/fr/docs/user_manual/print_composer/print_composer.h
> tml [2]
> http://docs.qgis.org/2.8/fr/docs/user_manual/working_with_vector/vector_prop
> erties.html [3] https://github.com/qgis/QGIS-Documentation/pull/544/

-- 
Yves Jacolin
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] Proposal to divide some pages in QGIS documentation

[Yves Jacolin]

Le samedi 6 juin 2015, 01:22:26 DelazJ a écrit :
> Hi Folks,
> 
> While reading QGIS documentation, there are some pages that leave me
> puzzled. You may have a look at Print Composer [1], vector properties
> dialog [2] pages.
> IMHO, these pages are too long. For the reader, scrolling can become
> tedious while looking for a precise information. Sure, the subject is wide
> and there is a lot of informations at these pages but I think that, because
> subject is wide, it can be splited into several pages, shorter, more
> precise and readable. As there are Previous/Next buttons, skipping sections
> while reading can easily be done.
> From writer side, I think that having short (and specialized) page helps us
> to quickly identify where there may be a lack of documentation, easily
> update or improve them...
> 
> So, few days ago, I made a pull request [3] that splits Print Composer
> chapter into many pages, reorganizing sections and sequences.
> 
> If you agree with the spliting principle of these chapters, can some
> documentation writers review it, amend it and let me know if it is ok? It's
> the first time I use rst files so it'd be nice if someone can review my PR
> before I begin spliting vector properties chapter.
> 
> Regards,
> Harrissou
> 
> [1]
> http://docs.qgis.org/2.8/fr/docs/user_manual/print_composer/print_composer.h
> tml [2]
> http://docs.qgis.org/2.8/fr/docs/user_manual/working_with_vector/vector_prop
> erties.html [3] https://github.com/qgis/QGIS-Documentation/pull/544/
DelazJ,

My opinions is that your split is perfect. As you said all in one page should 
be too much and the split is great.

One more feedback (with my comments in you Pr): the index page contains only a 
toc, do you think we can add a small paragraph to introduce the composer 
chapter? As the one in "First Steps" section for instance?

Otherwise just merge.

Y.
-- 
Yves Jacolin
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] QGIS Browser in french

[Yves Jacolin]

Jenny,

This is a comit number so you can really do anything with it. But you can 
install again the windows release (the nigthly build) that you can find in the 
qgis download page (I guess).

Bon week-end,

Y.
Le vendredi 19 juin 2015, 20:15:43 Jenny Dupuy a écrit :
> HI Jürgen,
> 
> I am a beginner in the team so I do not know where I should look for
> your reference
> 35f3838.
> 
> Thanks.
> 
> Jenny
> 
> 2015-06-19 17:08 GMT+02:00 Jürgen E. :
> > Hi Jenny,
> > 
> > On Fri, 19. Jun 2015 at 11:58:40 +0200, Jenny Dupuy wrote:
> > > In Transifex, QGIS Browser is translated in french, but when I execute
> > 
> > QGIS
> > 
> > > Browser by Start Menu, the GUI is in english.
> > > How set QGIS Browser in a specific language ? It's possible ?
> > 
> > Yes, fixed in 35f3838
> > 
> > 
> > Jürgen
> > 
> > --
> > Jürgen E. Fischer   norBIT GmbH Tel.
> > +49-4931-918175-31
> > Dipl.-Inf. (FH) Rheinstraße 13  Fax.
> > +49-4931-918175-50
> > Software Engineer   D-26506 Norden
> > http://www.norbit.de
> > QGIS release manager (PSC)  GermanyIRC: jef on
> > FreeNode
> > 
> > ___
> > Qgis-community-team mailing list for organizing community resources such
> > as documentation, translation etc..
> > Qgis-community-team@lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/qgis-community-team

-- 
Yves Jacolin
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] any (Asian/South American) community news?

[Yves Jacolin]

Richard,

OSGeo-fr will organize the third QGIS-fr conference in december in 
Montpellier. We / I have no more information yet, so it is probably too soon 
to announce it  :)

Y.
Le dimanche 2 août 2015, 14:16:02 Richard Duivenvoorde a écrit :
> Hi,
> 
> our 'Upcoming User & Developer Meetings' list on the frontpage of
> qgis.org is just 2 items long currently (just removed 2 old items).
> 
> anybody aware of some upcoming meeting?
> 
> I'm also eager to know if there is anything happening in the Asian
> communities.
> 
> No need to translate, just sent me 3 lines which I can copy paste in
> 
> https://github.com/qgis/QGIS-Website/blob/master/source/feeds/qugsnews.atom
> 
> 1) a title containing date + place
> 2) one line or a short description
> 3) a link to a describing webpage
> 
> Let's show the world we are indeed a global community :-)
> 
> Regards,
> 
> Richard
> ___
> Qgis-community-team mailing list for organizing community resources such as
> documentation, translation etc.. Qgis-community-team@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-community-team

-- 
Yves Jacolin
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] 2.12 documentation

[Yves Jacolin]

Hello,

I am currently working on the documentation (just a first start). 

I started the new section for 2.10 and 2.12 (better to work on both release, 
isn't?) on the QGIS hub [1] and I will add tickets in the QGIS Documentation. 
I created the "QGIS 2.10" milestone [2] in this purpose.

I will create 2.12 tickets as well as soon as possible.

I will send a tweet/annonce for a call for help next week.

I am quiet busy at this moment so I won't do all the documentation but if we 
can have some step done, it will better than nothing.

Y.
[1] http://hub.qgis.org/projects/quantum-gis/wiki/ManualTasks
[2] https://github.com/qgis/QGIS-Documentation/milestones/QGIS%202.10



Le mercredi 30 septembre 2015, 17:58:01 Richard Duivenvoorde a écrit :
> On 30-09-15 17:37, Radim Blazek wrote:
> > Hi,
> > 
> > I don't see any manual_en_v2.10 branch in
> > github.com/qgis/QGIS-Documentation. Where can I write documentation
> > for 2.12?
> 
> in current master branch
> 
> with release 2.12 we will branch current master to a 2.12 branch
> 
> Regards,
> 
> Richard Duivenvoorde
> 
> ___
> Qgis-community-team mailing list for organizing community resources such as
> documentation, translation etc.. Qgis-community-team@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-community-team

-- 
Yves Jacolin
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] 2.12 documentation

[Yves Jacolin]

Hello,

Le dimanche 4 octobre 2015, 21:20:57 DelazJ a écrit :
> Hi,
> 
> 2015-10-04 19:50 GMT+02:00 Yves Jacolin :
> > Hello,
> > 
> > I am currently working on the documentation (just a first start).
> > 
> > I started the new section for 2.10 and 2.12 (better to work on both
> > release,
> > isn't?) on the QGIS hub [1] and I will add tickets in the QGIS
> > Documentation.
> > I created the "QGIS 2.10" milestone [2] in this purpose.
> > 
> > Will a documentation for 2.10 be published? I thought it'd be skipped as
> 
> we did for 2.4.

Yes, indeed, but we can focus on 2.10 feature at least for the begining then 
2.12 and release both all together.

Note that I almost finished pushing the new ticket for 2.12 release.

Y.
-- 
Yves Jacolin
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] [Qgis-developer] [Qgis-user] Call for applications: QGIS Manual Update and Improvement

[Yves Jacolin]

On Monday, October 05, 2015 13:23:44 Paolo Cavallini wrote:
> Il 05/10/2015 12:52, DelazJ ha scritto:
> > +1
> > Great initiative!!! we really need an uptodate documentation...
> 
> Of course, donations and sponsorship from users will greatly speed up
> the process. So please those who need an updated documentation, come and
> help!
> https://www.qgis.org/en/site/about/sponsorship.html
> https://www.qgis.org/en/site/getinvolved/donations.html
> All the best.
Or send a contribution either via a Pull Request or a comment in the ticket:

https://github.com/qgis/QGIS-Documentation/milestones/QGIS%202.10
https://github.com/qgis/QGIS-Documentation/milestones/QGIS%202.12

I will push all contrib from coment of any tickets in this milestone and give 
credit to the author.

Y.
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] 2.12 documentation

[Yves Jacolin]

No I only meant (sorry for my poor english) that we should publish both 
milestone (from github point in view) at  the same time into Transifex as we 
already did in the past.

So there won't be a 2.10 branch but directly 2.12 branch (with 2.10 feature). 
It is only my point of view not a fact.

More I write, less I think I am clear :)

Y.
On Monday, October 05, 2015 14:42:59 DelazJ wrote:
> Hi,
> Indeed, 2.10 is a basis to document 2.12 features.
> I may misunderstand but what do you mean by" releasing both manuals"? Does
> it mean a 2.10 manual will also be pushed to transifex for translation?
> Does it worth publishing and translating a manual since most of users will
> either stay on 2.8-ltr or move to 2.12?
> Note that there's no branch for 2.10 yet.
> Great work BTW for the tickets.
> 
> 2015-10-04 21:23 GMT+02:00 Yves Jacolin :
> > Hello,
> > 
> > Le dimanche 4 octobre 2015, 21:20:57 DelazJ a écrit :
> > > Hi,
> > > 
> > > 2015-10-04 19:50 GMT+02:00 Yves Jacolin :
> > > > Hello,
> > > > 
> > > > I am currently working on the documentation (just a first start).
> > > > 
> > > > I started the new section for 2.10 and 2.12 (better to work on both
> > > > release,
> > > > isn't?) on the QGIS hub [1] and I will add tickets in the QGIS
> > > > Documentation.
> > > > I created the "QGIS 2.10" milestone [2] in this purpose.
> > > > 
> > > > Will a documentation for 2.10 be published? I thought it'd be skipped
> > 
> > as
> > 
> > > we did for 2.4.
> > 
> > Yes, indeed, but we can focus on 2.10 feature at least for the begining
> > then
> > 2.12 and release both all together.
> > 
> > Note that I almost finished pushing the new ticket for 2.12 release.
> > 
> > Y.
> > --
> > Yves Jacolin

___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] Books section on our website

[Yves Jacolin]

+1 from also!

I could help in some way sending a PR this evening (with a proof reading 
before merging).

Y.
On Tuesday, October 13, 2015 9:55:50 João Gaspar wrote:
> Hi Andreas,
> i think that is a good idea.
> 
> +1
> 
> João
> 
> 2015-10-13 9:52 GMT+01:00 Tim Sutton :
> > Hi
> > 
> > 
> > On Tue, Oct 13, 2015 at 10:42 AM, Neumann, Andreas 
> > 
> > wrote:
> >> Hi website team,
> >> 
> >> I have been in contact with the company PacktPub - a company specializing
> >> in IT and in particular OpenSource IT books. They publish several books
> >> on
> >> QGIS. The nice thing is that they return some of the revenues back to the
> >> Open Source projects. We just received a payment over € 140 from Anitas
> >> book. They will add the other books to our royalty scheme.
> >> 
> >> We also just recently added an entry in their Open Source section:
> >> https://www.packtpub.com/books/info/packt/open-source-projects-starting-q
> >> 
> >> I noticed that we don't have a book section yet on our website. Given
> >> that there are more and more books on QGIS, it would be nice to have such
> >> a
> >> section. It would be a win-win situation - for PacktPub and for us. And
> >> of
> >> course it wouldn't have to be limited to books from PacktPub but can
> >> reference any books.
> >> 
> >> The PacktPub manager would offer us additional discount codes or group
> >> discounts for ebooks if one wants to buy all QGIS ebooks at once - if we
> >> integrate this in our web page. Please note - the more books there are
> >> sold
> >> - the more we also get back from the royalty scheme program.
> > 
> > ​+1 from me to add a books section​
> > 
> >> Thanks,
> >> 
> >> Andreas
> >> 
> >> 
> >> 
> >> 
> >> ___
> >> Qgis-community-team mailing list for organizing community resources such
> >> as documentation, translation etc..
> >> Qgis-community-team@lists.osgeo.org
> >> http://lists.osgeo.org/mailman/listinfo/qgis-community-team
> > 
> > --
> > 
> > --
> >  Tim Sutton
> > 
> > Visit http://kartoza.com to find out about open source:
> >  * Desktop GIS programming services
> >  * Geospatial web development
> > 
> > * GIS Training
> > * Consulting Services
> > Skype: timlinux Irc: timlinux on #qgis at freenode.net
> > Tim is a member of the QGIS Project Steering Committee
> > 
> > --
> > - Kartoza is a merger between Linfiniti and Afrispatial
> > 
> > ___
> > Qgis-community-team mailing list for organizing community resources such
> > as documentation, translation etc..
> > Qgis-community-team@lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/qgis-community-team

___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

[Qgis-community-team] QGIS user meeting (10 and 11 of december 2015) at Montpellier (France)

[Yves Jacolin]

The Francophone local chapter of OSGeo (OSGeo-fr) and Montpellier SupAgro are 
organizing a two-day meeting around QGIS for the Francophone community. This 
meeting will take place on 10th and 11th December at Montpellier SupAgro.

Several presentations will take place on the first day. This year, the theme of 
this day is "QGIS: What are the uses case today What are the uses case 
tomorrow?". In the evening we invite you to join us for a drink in a place 
that will be given during the day.

The second day is organized as a barcamp: an informal workshops where you can 
suggest topics, present papers, exchange, discuss. It is an informal but 
organized time to exchange between users, contributors and financiers. Feel 
free to discover an original form of contributions to QGIS!

Some topics:

* How to translate QGIS
* How to use QGIS on a tablet (QField)
* How to create a map with QGIS and broadcast on the net
* QGIS and PostGIS couple

If you want to get some feedback from the community, get some help to prepare 
or discuss a particular topic before the day you can discuss it on the 
Francophone list (https://lists.osgeo.org/mailman/admin/francophone).

>> The detailed program, registration form and other information are available 
on the official page http://www.agrotic.org/blog/seminaire-qgis-2015/ <<

We would like to thank to all of our "mécènes" level sponsors :

* 3Liz company
* Camptocamp company
* Conservatoires of Natural Space Network (Réseau des Conservatoires d'espaces 
naturels)

**About Montpellier SupAgro and AgroTIC training**

Montpellier SupAgro is a teaching and research institution that trains 
agronomists. The AgroTIC training is a training carried by Montpellier 
SupAgro. Every year we train fifteen agronomists with dual expertise in 
geomatics. QGIS is a central tool in our training on the one hand to the 
functionality of spatial information management it offers and also because it 
is open and free and can be reused by our future graduates whatever their 
professional context. For 3 years, we organize an event around QGIS discussion 
in which our students can meet professionals who use this software. This event 
also allows them to value the teachings they have followed since they also 
present new features of QGIS before the professionals.

Montpellier SupAgro : www.supagro.fr

AgroTIC : www.agrotic.org

**About OSGeo-fr**

OSGeo-fr is a legal association, formely the Francophone representation of 
Open Source Geospatial Foundation, whose mission is to support and promote the 
collaborative development of geospatial data and open technologies. The 
association serves as a legal entity to which community members can contribute 
by source code, sponsorisation and other resources to ensure that their 
contributions will be maintained for public benefit. OSGeo also serves as 
organization of reference and support for open source geospatial community, 
and provides a common forum and shared to improve collaboration between 
infrastructure projects.

http://www.osgeo.asso.fr 
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

[Qgis-community-team] Transifex: translator mangement

[Yves Jacolin]

Hello,

Could I have the right needed to manage translator for the french translator 
team ?

Friday I will present the translation process and need to give access to the 
futur user to transifex.

Thanks,

Y.
-- 
Yves Jacolin
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] Transifex: translator mangement

[Yves Jacolin]

Jean-roc,

Could you add me (I just asked to jointhe french team)

Thanks,

Y.
On Sunday, December 06, 2015 19:40:15 MORREALE Jean Roc wrote:
> Hi Yves,
> 
> It would be a pleasure, suscribe to the fr desktop team and I'll give
> you the coordinator status.
> 
> Le 06/12/2015 18:54, Yves Jacolin a écrit :
> > Hello,
> > 
> > Could I have the right needed to manage translator for the french
> > translator team ?
> > 
> > Friday I will present the translation process and need to give access to
> > the futur user to transifex.
> > 
> > Thanks,
> > 
> > Y.
> 
> ___
> Qgis-community-team mailing list for organizing community resources such as
> documentation, translation etc.. Qgis-community-team@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-community-team

___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] Transifex: translator mangement

[Yves Jacolin]

Great, thank Jean-Roc.

Y.
On Wednesday, December 09, 2015 13:39:11 Jean-Roc Morreale wrote:
> Already done :)
> 
> Le 2015-12-09 13:29, Yves Jacolin a écrit :
> > Jean-roc,
> > 
> > Could you add me (I just asked to jointhe french team)
> > 
> > Thanks,
> > 
> > Y.
> > 
> > On Sunday, December 06, 2015 19:40:15 MORREALE Jean Roc wrote:
> >> Hi Yves,
> >> 
> >> It would be a pleasure, suscribe to the fr desktop team and I'll give
> >> you the coordinator status.
> >> 
> >> Le 06/12/2015 18:54, Yves Jacolin a écrit :
> >> > Hello,
> >> > 
> >> > Could I have the right needed to manage translator for the french
> >> > translator team ?
> >> > 
> >> > Friday I will present the translation process and need to give access
> >> > to
> >> > the futur user to transifex.
> >> > 
> >> > Thanks,
> >> > 
> >> > Y.
> >> 
> >> ___
> >> Qgis-community-team mailing list for organizing community resources
> >> such as
> >> documentation, translation etc.. Qgis-community-team@lists.osgeo.org
> >> http://lists.osgeo.org/mailman/listinfo/qgis-community-team

___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

[Qgis-community-team] About documentation : line size

[Yves Jacolin]

Hello,

In code source there is some "standards" and good practice as limite the line 
length to 80 letters.

Is it something we want to do also in documentation? I would say yes, we want 
as all documentation seems to follow this rule but there is some PR which 
change this.

Any though?

Thanks,

Y.
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] Cleaning issue report queue in Website and Documentation repo

[Yves Jacolin]

On Tuesday, January 05, 2016 14:58:38 Richard Duivenvoorde wrote:
> On 05-01-16 14:54, DelazJ wrote:
> > Hi,
> > Below is a list of issue reports that have been fixed but are still open
> > in their repo.
> > 
> > WEBSITE repo:
> > #169, #89
> > #272, #241 seem invalid (related to QGIS Desktop)
> > State of #46, #43, #42, #33?
> > 
> > DOCUMENTATION repo:
> > #661, #644, #601, #599, #596, #594, #592 (?), #589, #588, #567
> > 
> > Thanks to close them, please.
> > 
> > Regards,
> > Harrissou
> 
> Harrissou,
> 
> normally they are closed automatically when you commit a pull request
> and there is something like 'fixes #599' in the commit message or so...
> 
> but as you are doing so much doc/site work (for which a big THANKYOU!),
> what about giving you commit access? Others agree?
+1 I try to do some doc review but more people involved the better!

Harrissou made great contribution to the doc.

Y.
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

[Qgis-community-team] [Doc] what's new page

[Yves Jacolin]

Hello,

We have a what's new feature in documentation and visual changelog in website. 
Do we want to keep both of them?

Do we need to remove what's new and add a link to the visual changelog page?

Y.
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

[Qgis-community-team] [Doc] 2.10, 2.12 and master branch

[Yves Jacolin]

Hello,

Following this PR [1], we had a discussion on how to manage feature from 
future 2.14 release.

DelazJ proposed to create a 2.12 branch but this bring some though to me:

* do we want to manage backport from master to 2.12 (and what about 2.10?) new 
feature?
* can you just forget 2.10 and 2.12 documentation and focus on the next 2.14 
release?

This mail aims to start discussion about this

Thanks,

Y.
PS : It seems that there is some activities on the documentation part and this 
is a great thing!

[1] https://github.com/qgis/QGIS-Documentation/pull/748#issuecomment-170869066

___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] Doc writing: simpler writing and styling

[Yves Jacolin]

Otto,

Le samedi 16 janvier 2016, 20:54:50 Otto Dassau a écrit :
> a) Go through the "User Manual" issues and add missing issues that need to
>   be documented for 2.14. from changelog.
>   
> https://github.com/qgis/QGIS-Documentation/issues?q=is%3Aopen+is%3Aissue+label%3A%22User+Manual%22
I can confirm that I did all needed for 2.10 and 2.12 release (if anyone need 
confirmation).

> b) Create a list which issues should go to which chapter and make a
>proposal which could be done by whom. 

May be using labels in github will help?

I will try to do my best to help to update documentation.

We have 3 releases to documente. 2.10 is close to be finished (only 6 issues).

Y.
-- 
Yves Jacolin
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] Doc writing: simpler writing and styling

[Yves Jacolin]

Otto,

I did it from git changelog for 2.10 and 2.12, but directly intho github 
issues.

For 2.14 it should be automatic but may be there is some new feature missing 
(the first one to be merged probably).

Y;
Le dimanche 17 janvier 2016, 20:43:59 Otto Dassau a écrit :
> Hi Yves,
> 
> Am Sun, 17 Jan 2016 19:59:57 +0100
> 
> schrieb Yves Jacolin :
> > Otto,
> > 
> > Le samedi 16 janvier 2016, 20:54:50 Otto Dassau a écrit :
> > > a) Go through the "User Manual" issues and add missing issues that need
> > > to be documented for 2.14. from changelog.
> > > 
> > >   https://github.com/qgis/QGIS-Documentation/issues?q=is%3Aopen+is%3Aiss
> > >   ue+label%3A%22User+Manual%22> 
> > I can confirm that I did all needed for 2.10 and 2.12 release (if anyone
> > need confirmation).
> > 
> > > b) Create a list which issues should go to which chapter and make a
> > > 
> > >proposal which could be done by whom.
> > 
> > May be using labels in github will help?
> > 
> > I will try to do my best to help to update documentation.
> > 
> > We have 3 releases to documente. 2.10 is close to be finished (only 6
> > issues).
> 
> Thanks a lot for the work you hava already done and yes, quite some work to
> do for 3 releases. I just added a list of all [FEATURES] to the wiki for
> 2.10 - 2.14:
> 
> http://hub.qgis.org/wiki/quantum-gis/ManualTasks#Updates-210-214-User-Guide
> 
> Next step would be to go through the wiki list and compare it with the "User
> Manual" issues in github. We could add all missing [FEATURES] (mostly 2.14
> I guess) there and define labels. And we could add a done to the wiki list,
> if a feature is already added to github. So finally we would work on the
> issues in github. I guess that would be the best procedure...
> 
> If you find some time to help, it is welcome...
> 
> Regards,
> Otto
> _______
> Qgis-community-team mailing list for organizing community resources such as
> documentation, translation etc.. Qgis-community-team@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-community-team

-- 
Yves Jacolin
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] Doc images and github

[Yves Jacolin]

Richard,

I am not a big contributor. But I am ok with option 2 as well.

Y.
On Wednesday, January 27, 2016 10:00:39 Richard Duivenvoorde wrote:
> Others?
> 
> Else I think I'll start to do all whole rst files in working_with_vector
> directory and commit in one go. So it can be reversed if we hit problems.
> 
> @Alexandre: putting ALL rst file in one dir would indeed help, but I
> think we need the structure to be able to eventually build partial
> documentation sets.
> We could put the substitutions maybe in the index.rst files in the
> directory where the images dir also is, but that would also scatter the
> substitutions. Then I think having them in de file where you need them
> is easiest, also because then you can move around the rst file in the
> directory structure without fixing relative paths... (as long as you
> copy the images also to the right place off course :-) ).
> 
> Anyway: proceed?
> 
> Richard
> 
> On 26-01-16 14:08, Otto Dassau wrote:
> > Hi Richard,
> > 
> > thanks a lot for this grep/count. In this case I would vote for option 2:
> > 
> > ..."define figures locally in the rst file where you use them. This has as
> > drawback that very often used inline images (like the checkbox) are
> > defined
> > + image copied very often. BUT the nice thing about it is that IF you
> > define them in the rst file, Github is able to resolve those SO they show
> > up as inline images there."
> > 
> > Regards
> > Otto
> > 
> > Am Mon, 25 Jan 2016 21:34:51 +0100
> > 
> > schrieb Richard Duivenvoorde :
> >> On 25-01-16 11:06, Alexandre Neto wrote:
> >>> Not an easy choice... I'm not very fond of duplicating substitutions
> >>> images as I believe it will lead to pages with different icons because
> >>> someone just update one place. Maybe it would be possible to have a
> >>> common place with all  images and some kind of script to copy the icons
> >>> to a child forder near the rst?
> >> 
> >> FYI, I did a quick grep/count on all substitutions over ALL docs (so not
> >> only manual).
> >> 
> >> While I agree with your point... there are not so many images used > 2
> >> times...
> >> 
> >> |nix| 45
> >> |win| 15
> >> |osx| 9
> >> |action| 2
> >> |analysis| 1
> >> |attributes| 4
> >> |basic_statistics| 2
> >> |browsebutton| 10
> >> |buffer| 2
> >> |calendarwidget| 0
> >> |checkbox| 41
> >> |checkbox_checked| 1
> >> |checkbox_unchecked| 1
> >> |check_geometry| 2
> >> |centroids| 2
> >> |clip| 2
> >> |color| 0
> >> |colormap| 0
> >> |columnview| 0
> >> |combobox| 0
> >> |commandlinkbutton| 0
> >> |convex_hull| 2
> >> |coordinate_capture| 2
> >> |copyright_label| 2
> >> |CRS| 1
> >> |create_gpx| 1
> >> |dateedit| 0
> >> |datetimeedit| 0
> >> |dbmanager| 2
> >> |define_projection| 2
> >> |delaunay| 2
> >> |delimited_text| 2
> >> |dem_analysis| 1
> >> |diagram| 2
> >> |dial| 0
> >> |dialogbuttonbox| 0
> >> |difference| 2
> >> |digitising| 0
> >> |dissolve| 2
> >> |dockwidget| 0
> >> |doublespinbox| 0
> >> |dxf2shp_converter| 3
> >> |edit| 4
> >> |eliminate| 1
> >> |event_browser| 1
> >> |event_id| 3
> >> |evis_connect| 2
> >> |evis_file| 2
> >> |export_geometry| 2
> >> |export_projection| 1
> >> |extract_nodes| 2
> >> |fontcombobox| 0
> >> |frame| 0
> >> |ftools| 2
> >> |fullCumulativeStretch| 1
> >> |FullHistogramStretch| 1
> >> |gdal| 1
> >> |gdal_about| 0
> >> |gdal_assign_projection| 1
> >> |gdal_contour| 1
> >> |gdal_dem| 1
> >> |gdal_edit| 0
> >> |gdal_extract_projection| 1
> >> |gdal_fillnodata| 1
> >> |gdal_grid| 1
> >> |gdal_merge| 1
> >> |gdal_nearblack| 1
> >> |gdal_polygonize| 1
> >> |gdal_proximity| 1
> >> |gdal_raster-clip| 1
> >> |gdal_raster-overview| 1
> >> |gdal_raster-paletted| 0
> >> |gdal_raster-rgb| 1
> >> |gdal_rasterize| 1
> >> |gdal_reset| 0
> >> |gdal_sieve| 1
> >> |gdal_tileindex| 1
> >> |gdal_tooltip| 0
> >> |gdal_translate| 1
> >> |gdal_vrt| 1
> >> |gdal_warp| 1
> >> |general| 2
> >> |gentlelogo| 10
> >> |geographic| 3
> >> |geometry| 1
> >> |geometrychecker| 2
> >> |geometrysnapper| 2
> >> |geoprocessing| 2
> >> |georeferencer| 1
> >> |geRasterometry| 0
> >> |gps_importer| 2
> >> |gpstrack_barchart| 2
> >> |gpstrack_polarchart| 2
> >> |graphicsview| 0
> >> |grass| 2
> >> |grass_close_mapset| 2
> >> |grass_location| 1
> >> |grass_new_mapset| 3
> >> |grass_open_mapset| 2
> >> |grass_region| 2
> >> |grass_set_region| 1
> >> |grass_region_edit| 1
> >> |grass_tools| 3
> >> |groupbox| 0
> >> |groupboxcollapsible| 0
> >> |heatmap| 4
> >> |histogram| 0
> >> |hscrollbar| 0
> >> |hslider| 0
> >> |hsplit| 0
> >> |iconAboutConsole| 0
> >> |iconClassBrowserConsole| 0
> >> |iconClassConsole| 0
> >> |iconClassTreeWidgetConsole| 0
> >> |iconClearConsole| 0
> >> |iconCloseTabEditorConsole| 0
> >> |iconCodepadConsole| 0
> >> |iconCommentEditorConsole| 0
> >> |iconCopyEditorConsole| 0
> >> |iconCutEditorConsole| 0
> >> |iconFileTabsMenuConsole| 0
> >> |iconFunctionTreeWidgetConsole| 0
> >> |iconHelpConsole| 0
> >> |iconHideToolConsole| 0
> >> |iconIfaceConsole| 0
> >> |iconMethodTreeWidgetConsole| 

Re: [Qgis-community-team] Manual revision

[Yves Jacolin]

On Monday, February 08, 2016 9:23:04 Otto Dassau wrote:
> Hi,
> 
> Nicholas Duggan and Frank Sokolic are are mainly supposed to work on a
> manual revision for the 2.14 manual release. For sure we still have a lot of
> open, not yet documented issues, so until now they checked and revised a
> lot of closed issues
> 
> At this point I wonder, if there are already some, completed sections /
> chapters that they could have a look at? So we can say, this is done...? Or
> should we wait a little longer?
> 
> Regards,
> Otto

Not sure how to be sure. I think 'working with vector' is not ready. We are 
close to finish 2.10 release documentation on which I focus my work.

Y.

___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] Manual revision

[Yves Jacolin]

On Monday, February 08, 2016 10:12:14 Richard Duivenvoorde wrote:
> On 08-02-16 09:29, Yves Jacolin wrote:
> > On Monday, February 08, 2016 9:23:04 Otto Dassau wrote:
> >> Hi,
> >> 
> >> Nicholas Duggan and Frank Sokolic are are mainly supposed to work on a
> >> manual revision for the 2.14 manual release. For sure we still have a lot
> >> of open, not yet documented issues, so until now they checked and
> >> revised a lot of closed issues
> >> 
> >> At this point I wonder, if there are already some, completed sections /
> >> chapters that they could have a look at? So we can say, this is done...?
> >> Or
> >> should we wait a little longer?
> >> 
> >> Regards,
> >> Otto
> > 
> > Not sure how to be sure. I think 'working with vector' is not ready. We
> > are
> > close to finish 2.10 release documentation on which I focus my work.
> 
> Hi Yves,
> 
> just to be clear: you mean handling all 2.10 related documentation updates?
Yep, see milestone 2.10 in Github issues for QGIS-doc repository. There is 
only around 10 issues to close.

> for what I know there will be no 2.10 (or 2.12) build/translation
> somewhere, only 2.14 when all is finished.
Yes,but  I will work on 2.12 issues next and so on until 2.14.

Y.

___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

[Qgis-community-team] Right to QGIS-Website repository

[Yves Jacolin]

Hello,

Could I have right to the QGIS-Website repository? Mainly to assign issue or 
PR to me and make review.

For big contribution I will let other native english langage finalize it.

Thanks,

Y.
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] Right to QGIS-Website repository

[Yves Jacolin]

On Tuesday, February 09, 2016 9:15:31 Yves Jacolin wrote:
> Hello,
> 
> Could I have right to the QGIS-Website repository? Mainly to assign issue or
> PR to me and make review.
> 
> For big contribution I will let other native english langage finalize it.
> 
> Thanks,
> 
> Y.

Thanks Richard :)

Y.
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

[Qgis-community-team] WebSite French translation problem

[Yves Jacolin]

Hello,

An user find an issue with transifex and WebSite (he posted it on OSGeo-fr ML):

This page : 
https://www.qgis.org/en/site/getinvolved/development/bugreporting.html

is inside the "site_getinvolved_development_index" transifex category. All 
string are translated but the website is not.

It seems also to me that the transifex category should be something like 
"site_getinvolved_development_bugreporting".

Any idea?

Y.
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] [Qgis-developer] new commit label: [NEEDS-DOCS] for QGIS commits will also raise an issue in QGIS-Documentation

[Yves Jacolin]

Le mercredi 17 février 2016, 19:53:54 Richard Duivenvoorde a écrit :
> On 17-02-16 19:42, DelazJ wrote:
> > To have a complete list of issues for documentation (especially for
> > needs_docs tag), does it mean that developers should amend their
> > previous commits message (don't know if it's doable)  so that a grep can
> > retrieve these commits? Or do we consider that they are "lost" improveme
> 
> Well, not sure if that is technically possible: it means changing the
> commit message by adding a label AND writing some prose about the
> addition. But dev's feel free to add the label if possible, or else:
> sent an email to the documentation team describing what you fixed/added
> to excisting features :-)
> 
> Regards,
> 
> R

Harrissou,

Note that this is only true for 2.14 release as I copy pasted the commit 
message into each issue for 2.10 and 2.12. Batch script was up for 2.14.

But if I remembered correctly, Otto did a check for 2.14.

Y.
-- 
Yves Jacolin
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

[Qgis-community-team] How to contribute to QGIS-Documentation (via github)

[Yves Jacolin]

Hello,

I wrote a quick and easy how-to to explain how to contribute to QGIS-
Documentation with github. This is currently in a wiki page in my fork but I 
planed to include it in the documentation guidelines with screenshots. 

This could be the step 1 of several how-to. The next one could be the page 
which explains the tags [1] for example.

Feel free to add more information and rephrasing anything.

https://github.com/yjacolin/QGIS-Documentation/wiki/howto_contribute_QGIS-Doc

Thanks,

Y.
[1] 
http://docs.qgis.org/2.8/en/docs/documentation_guidelines/README.html#introduction
-- 
Yves Jacolin
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] Translated websites

[Yves Jacolin]

Richard,

On Wednesday, March 02, 2016 10:19:14 Richard Duivenvoorde wrote:
> As said: if somebody has some sparetime, please try and report back.
> I'll dive into the rest when I find time
I can have a look into this but only this week-end (on sunday).

Y.
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] [Doc] what's new page

[Yves Jacolin]

On Thursday, March 03, 2016 16:00:38 Otto Dassau wrote:
> I would propose that we only add the link to the visual changelog in the
> manual and remove the rest. It makes no sense to me to have it twice.
+1

Y.
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] New translations for website

[Yves Jacolin]

On Saturday, March 05, 2016 16:00:07 Richard Duivenvoorde wrote:
> :ref:`thisref`
> 
> there MUST be space after.
> Another problem I fixed a lot is the 'strong text' starts: if you use
> double ** or single * be sure you use them twice, AND no spaces so NOT:
>  * important * or *important *
> but
>  *important* (keep them close to the text  )
and do not translate :ref: label :)

Thanks,

Y.
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] Translated websites

[Yves Jacolin]

On Wednesday, March 02, 2016 10:52:05 Yves Jacolin wrote:
> Richard,
> 
> On Wednesday, March 02, 2016 10:19:14 Richard Duivenvoorde wrote:
> > As said: if somebody has some sparetime, please try and report back.
> > I'll dive into the rest when I find time
> 
> I can have a look into this but only this week-end (on sunday).
> 
> Y.

Richard,

I successfully built the french documentation, but I just see that you talked 
about website :/

I will see this afternoon in the train.

Y.

___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

[Qgis-community-team] An Unofficial Workshop during HackFest

[Yves Jacolin]

Hello community,

I will present an unofficial workshop on how to write documentation for QGIS.

This is a so called unofficial workshop as:
*  it will held during the QGIS hackfest, not for the official workshop on next 
tuesday (jornadas SIG Libre)
* I prepare some slides, just to give me reminder of link and important 
informations, but it will be done in a practical way.

I planned to do it on friday morning. If you want to contribute this way and 
don't know how, you are very welcome!

You just need git in your machine, an editor (vim, kate, Notepad++, etc.), a 
browser and a github account :)

If you don't know git but are not afraid with command line we will find a 
moment to explain the concept.

We just have 152 issues to closed during the hackfest :)

Y.
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] An Unofficial Workshop during HackFest

[Yves Jacolin]

On Friday, May 20, 2016 8:54:27 matteo wrote:
> Hi Yves,
> 
> will be there too!
> Planning to update some part of the Cookbook, but I will help closing
> issues for the main manual as well ;)
> 

Woww I didn't think I will have some much feedback :) Great!

Matteo, Paolo,

The 152 issues is for all manual (user, training, cookbook) I will focus on 
issues of the user manual.

Thanks,

Y.

___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] documentation testing branch currently rebuild every hour

[Yves Jacolin]

On Saturday, May 28, 2016 10:10:54 DelazJ wrote:
> Thanks Richard
> it'll be helpful.
> 
> 2016-05-28 10:04 GMT+02:00 Richard Duivenvoorde :
> > FYI:
> > 
> > during the hackfest the documentation building branch:
> > 
> > http://docs.qgis.org/testing/
> > 
> > (for upcoming 2.14 docs release)
> > 
> > is being rebuild every hour so you can preview your edits
> > 
> > Please help getting 2.14 docs out!! \o/
> > 
> > (2.8 branch is not rebuild during this time)
> > 
> > Regards,
> > 
> > Richard

The testing doc should be soon up to date with 2.10 release (the last 2 PR 
should be merged soon), and tomorrow for 2.12?

Y.
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] New QGIS Documentation Subscriber

[Yves Jacolin]

Hello,

A good start for an english native speaker could be:
* make review of Pull request
* proof read the doc to see english error, etc. and create issue with the 
correct sentence.

That would be a really huge enhancement, but also a hard work.

Y.


On Thursday, June 02, 2016 1:20:25 DelazJ wrote:
> Hi,
> 
> Welcome Angie and thanks for offering your help!
> 
> As already pointed out by Richard you'll find few recommendations to follow
> when contributing to QGIS Documentation writing at
> http://docs.qgis.org/testing/en/docs/documentation_guidelines/
> But prior to this, In order to contribute, you'll need as stated at
> http://qgis.org/en/site/getinvolved/document.html#becoming-a-documenter  to:
> - create a GitHub account
> - and fork (copy) the doc repo
> 
> Once done, feel free to pick any issue in the list and write about. You can
> also go through the doc being written (docs.qgis.org/testing/en/docs) and
> fix potential typo errors, "bad english" (most of us are not native
> speaker) or review/comment contributions of others (
> https://github.com/qgis/QGIS-Documentation/pulls).
> 
> Once again, welcome to you and if something is unclear, just ask. Someone
> will try to explain to you.
> 
> Regards,
> Harrissou
> 
> 2016-06-02 0:17 GMT+02:00 Alexandre Neto :
> > Angie,
> > 
> > Welcome to the team. Thanks you for helping us with the docs.
> > 
> > I normally do the screenshots, so anything you need, let me know. Are you
> > on github already?
> > 
> > Alexandre Beto
> > 
> > A qua, 1/06/2016, 22:50, Angie Garcia  escreveu:
> >> Richard,
> >> 
> >> English is my primary language.  Read QGIS is natively developed in
> >> English, if you need assistance in looking at text before pulling it into
> >> the docs, glad to help just need to know what needs to be done.
> >> 
> >> Best Regards,
> >> Angie
> >> 
> >> 
> >> 
> >> From: Richard Duivenvoorde 
> >> Sent: Tuesday, May 31, 2016 11:53:43 PM
> >> To: Angie Garcia
> >> Cc: das...@gbd-consult.de; Junior Delaz; Yves Jacolin; qgis-community
> >> Subject: Re: New QGIS Documentation Subscriber
> >> 
> >> On 31-05-16 22:33, Angie Garcia wrote:
> >> > Hi Richard,
> >> > 
> >> > I have recently subscribed and would like to participate with updating
> >> > User Guide and assist in suggestions to aid in the documentation work
> >> > flow.  In going through all online/materials, it mentioned that one
> >> > should contact team lead in specific area of interest to get some
> >> > assistance in the process.  I have cc Otto as he was the person I sent
> >> > email to, however, have not heard from him and thought you might be
> >> > able
> >> > to help me or point me in the right direction to move forward.
> >> > 
> >> > Is there a new welcoming documentation packet which helps one get
> >> > setup,
> >> > have a mailing list of individuals to contact, talks a little about the
> >> > various emails and limitations, etc...
> >> 
> >> Hi Angie,
> >> 
> >> For what I know this:
> >> 
> >> http://docs.qgis.org/testing/en/docs/documentation_guidelines/
> >> 
> >> are the guidelines. In the README at:
> >> 
> >> https://github.com/qgis/QGIS-Documentation
> >> 
> >> is more information about how to actually BUILD the docs.
> >> 
> >> Note that it is actually not persee nessecary to build it yourself. If
> >> you follow the 'fix me' link in the footer of the pages on current
> >> 'testing' (==2.14 to be) version:
> >> 
> >> http://docs.qgis.org/testing/en/docs/user_manual/index.html
> >> 
> >> you can write/fix smaller parts of the docs in Github.
> >> 
> >> I added Harrisou and Yves in cc, they have been mostly active I think
> >> recently, and maybe can give you a hand too.
> >> I will also sent this email to the community list where most document
> >> writers hang out.
> >> 
> >> Here:
> >> 
> >> https://github.com/qgis/QGIS-Documentation/issues
> >> all issues labeld QGIS 2.14
> >> https://github.com/qgis/QGIS-Documentation/milestones/QGIS%202.14
> >> should be taken up in short notice.
> >> Not sure if you are native speaker, but we also look for native speakers
> >> to have a look at texts of others bef

Re: [Qgis-community-team] New QGIS Documentation Subscriber

[Yves Jacolin]

Angie,

On Monday, June 06, 2016 2:09:20 Angie Garcia wrote:
> In addition, when I make changes using the fix me link to transfer the pdf
> to GitHub and it’s in my repository, will the changes I make affect the
> original (Master) document User Guide 2.14. Or will it ONLY affect my clone
> repository in my account?  Will everyone be able to go to my repository and
> see the changes I made to the document?  Hence, the reason I did not make
> any changes yet to the Github QGIS User Guide 2.14 document.
You don't have write access to the main repository of QGIS-Documentation, so 
yes all changes that you do will be in one of your branch of your repository 
(check the url to see that it points to your repository).

Everyone can see your changes going to your repository :)

Y.
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] QGIS-Documentation-testing builds twice a day now

[Yves Jacolin]

On Wednesday, June 08, 2016 9:49:39 Richard Duivenvoorde wrote:
> Hi Community,
> 
> during the hackfest we build the master/testing/2.14tobe
> QGIS-Documentation once every hour.
> Before it was once a day.
> 
> I'll changed it back to twice a day now.
> 
> Off course every change and pull request will be viewable in Travis:
> 
> https://travis-ci.org/qgis/QGIS-Documentation
> 
> Regards,
> 
> Richard Duivenvoorde

Perfect Richard! Thanks.

Y.
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] 2.14 Documentation release date?

[Yves Jacolin]

Harrissou, All,

I thought something similar, so +1 for your proposition. We can also move 
bugs, python cookbook (5 tickets) to the next release.

For the last 40 issues we can share the tickets between 4-5 peoples :)

Camptocamp will invest 3 days of my time to work on this in the next weeks. So 
~ 20 tickets could be closed around the end of june. I will try to close 2 
tickets by week-end on my own time.

Y.

On Thursday, June 16, 2016 14:01:23 DelazJ wrote:
> Hi,
> Afaik, there's no date published. But I was planning to send an email
> proposing to the community to release 2.14 doc with the release of QGIS
> 2.16. At that moment QGIS 2.14 becomes LTR so nice to announce it
> concomitantly with a doc released.
> 
> I don't know if we'll have all the 2.14 issues fixed at that moment so
> given that Richard has suggested in a previous thread that documenters
> decide when they are ready, I'd like to propose the use of a special tag
> (let's say "Blocker") to identify the features we'd like documented with
> the release. We then will concentrate our energy prioritarily on these ones.
> opinions?
> 
> Regards,
> Harrissou
> 
> 2016-06-16 13:35 GMT+02:00 Alexandre Neto :
> > Hi all,
> > 
> > I was wondering, can anyone tell me if we already have a release date for
> > 2.14 Documentation.
> > 
> > I want to make some contributions and I would like to make sure I have
> > time for it.
> > 
> > Thanks!
> > 
> > Alexandre Neto
> > --
> > Alexandre Neto
> > -
> > @AlexNetoGeo
> > http://sigsemgrilhetas.wordpress.com
> > http://gisunchained.wordpress.com
> > 
> > ___
> > Qgis-community-team mailing list for organizing community resources such
> > as documentation, translation etc..
> > Qgis-community-team@lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/qgis-community-team

___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] Stickers?

[Yves Jacolin]

On Sunday, June 19, 2016 23:20:44 Tim Sutton wrote:
> Hi
> 
> I think it will be great to have a bunch of stickers made - and maybe learn
> from my mistakes in the last run I did:
> 
> * Print on round sticker stock (I couldn’t organise round ones with the
> printer I worked with in Indonesia - they wanted to cut them out by hand
> :-P ) * Print on vinyl so they are more durable
> * print on thick vinyl so they hide those pesky dell / apple / etc. logos
> etc.
> 
> I would prefer just the plain Q logo without text - a little bit of
> minimalism is nice.
> 
> Regarding the timeframe mentioned by Andreas, I think it is OK as long and
> we do not do such a huge print run that we are using the stickers for years
> to come. Actually they will become a collectors item maybe :-)
> 

+1 for all this points :)

Y.

___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

[Qgis-community-team] Documentation process

[Yves Jacolin]

Hello doc contributor,

Currently for each issue or changes in documentation I am using a PR process. 
That's mean that I always create a branch and a Pull Request to let other 
contributor to comment my contribution.

This way I can let other contributor know my changes and get some feedback 
about wrong guidelines, typos, etc.

All in all, this improve the quality of the documentation.

What do you think about this process? Do you think we can ask to everybody to 
work following such process?

Thanks for your feedback,

Y.

signature.asc
Description: This is a digitally signed message part.
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] Documentation process

[Yves Jacolin]

Hello,

On Thursday, June 23, 2016 9:20:31 matteo wrote:
> Hi all,
> maybe the suggestions come from yesterday and the caos I did.. :)
Well, as I said in the ticket another build break  occurs yesterday. This is 
something that can occurs, even for typos.

But my workflow is not only for this kind of small issue, it is a good way to 
create a dynamic, interac with people, correct typos in the PR, make sur we 
follow the guidelines, get some suggestion.

I am using this workflow with delazj and this is really great to get such 
valuable feeback.

> well, Yves, do you suggest the following workflow?
> 
> * fork the project
> * create a branch for the feature
> * make changes locally on the created branch
> * push back to the forked repo
> * create a pull request from the new branch and the master one of the
> "original" repo

Yes, it is what I meant, just add 2 last steps:
* make a review of another PR
* wait for a +1 before merging.
 
> could it be a reasonable worflow?
> 
> finally I think, as Alexandre said, that for small changes (e.g. a typo)
> one can directly work on the main repo.. or do you suggest to make other
> branches?
Yes for typo it should be straighforward. We should be pragmatic!

Y.
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] Problem in working with Select by expession tool

[Yves Jacolin]

On Wednesday, July 06, 2016 0:44:13 Wifra wrote:
> Hello guysl
> 
> I'm getting a bit challenges on querying multiple Regions from country
> Shapefile consisting about 30 regions, can anyone please help me with proper
> syntax of writting the expression to sellect about 3 different regions from
> country shape file?
> 
> Thanks
> 
Wifra,

This mailing list is to discussed about documentation and other community 
related. Not for use of QGIS. There is a QGIS-user mailing list for this 
purpose.

To answer to your question, go to the property of the layer, go to the general 
tab and click on the "Query builder" button and add this:

"region" = 'Savoie' OR "region" = "Vienne" OR "region" = 'Alsace'

You can also use this:

"region" IN ('Savoie', 'Vienne', 'Alsace')

Here:
* region is the attribute name
* Savoie, Vienne, Alsace are different value of region

Y.
PS : for french people: yes these values are not french region :)

___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

[Qgis-community-team] Documentation discussion for Bonn Hackfest

[Yves Jacolin]

Hello,

I created a wiki page for the next hackfest in Bonn to list some topics [1]. 
Feel free to add more topics. 

Some of the ones I added come from some discussion we added in previous Pull 
Request.

Thanks,

Y.
[1] https://github.com/qgis/QGIS-Documentation/wiki/hackfest_Bonn_2016

signature.asc
Description: This is a digitally signed message part.
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

[Qgis-community-team] Make the 2.14 documentation a reality!

[Yves Jacolin]

Hello,

Today we have only 18 issues in the documentation tracker and we have almost 
now the QGIS 2.16 released. It is probably a good moment to plan the 2.14 
release of the documentation.

What I have currently in mind is to move all issues labelled "python cookbook" 
and "training manual" to 2.16 release (or even for the next release if we
can't find any contributors).
 
Consequently of this, we will have only 8 open issues. From theses 8
issues, only 3 have no contributors. One is really easy to closed, others
need more work. So we can add a short description and improve it for the next
release (I have this one in mind:"Add N:M relation editing possibilities"
#705). We have 2 documentation issues labelled as blocker.

Unfortunately, we ("we" means only the French contributors) have a half week 
as we have a day off on Thursday.

Let's try to plan the next release: we can try to close 5 tickets this
week as some are already almost finished. We can plan a release next week,
say Friday 22nd of July.

Opinions? Here a synthesis (+1/0/-1):
* move python cookbook and training manual to 2.16/3.0
* quickly fix the last 6 remaining issues
* add a short description for the last 3 issues
* release on 22nd of July

Thanks,

Y.





signature.asc
Description: This is a digitally signed message part.
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] [Qgis-developer] QGIS Hackfest in Bonn

[Yves Jacolin]

On Tuesday, July 12, 2016 9:01:29 Tim Sutton wrote:
> Dear QGIS Lovers
> 
> Bonn is drawing close and we need to start getting organised for the
> hackfest.
> 
> Paolo has been petitioning to shut down the current wiki in anticipation of
> a future migration off Redmine and because the content there is not
> maintained. Thus for this hackfest I have started the wiki page on the QGIS
> GitHub wiki here:
> 
> https://github.com/qgis/QGIS/wiki/QGIS-Hackfest---Bonn---August-2016
> 
> 
> It is just a stub at the moment - I hope collaboratively we can get things
> organised. We really need a local organiser who can make sure everything is
> in place - are there any volunteers out there?
> 
> If you are not able to write to the wiki page, please contact me with your
> github name and I will see to it that you have the needed permissions.
> 
> Note that there are two FOSS4G2016 conference hacking sprints during Bonn -
> our plan was to make the first (Aug 21-23 2016) the 'official' QGIS one and
> if others wish to hack during the weekend after FOSS4G, you are welcome to
> do so.
> 
> @Astrid could you give us some help in terms of accommodation and hacking
> venue? I believe the camper van place is already full - can you recommend
> some other nearby and cheap places to stay?
> 
> Regards
> 
> Tim

Hello,

We (some camptocamp guys) booked at the Bonnox hotel [2], It should be ~ 10 mn 
to the hackfest place. This is one accomodation listed in the OSGeo Code 
sprint wiki page [1].

Y.
[1] https://wiki.osgeo.org/wiki/FOSS4G_2016_Code_Sprint
[2] http://www.bonnox.de/en/
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] Stickers?

[Yves Jacolin]

Richard,

OSGeo-fr organize a QGIS user -fr meeting in december (~ 100 people) I will be 
please to share some stickers ;)

Y.
On Tuesday, July 12, 2016 10:32:37 Richard Duivenvoorde wrote:
> Ok I received a quick quote:
> 
> 7x7cm 2100 on 7 roles: 275 euro ex vat
> 3x3cm 2100 on 7 roles: 200 euro ex vat
> 
> printing more makes them a little cheaper, like:
> 7x7cm 5000 is 350 ex vat
> 
> I reckon you can get the cheaper in ... but I just want stickers, and I
> can pick these up next week and take them to Bonn in august.
> 
> Opinion about size?
> Else, I think I go for 3x3
> No idea about the amount... is 2100 stickers a lot? Not if we give
> everybody 1 meter of sticker ;-)
> 
> Regards,
> 
> Richard
> 
> On 06-07-16 21:22, Randal Hale wrote:
> > I might just do that - pay day is coming up soon and I smell 'business
> > expense' in the air. hah.
> > 
> > Randy
> > 
> > On 07/06/2016 03:20 PM, Richard Duivenvoorde wrote:
> >> On 19-06-16 18:35, Randal Hale wrote:
> >>> I'd be interested in printing some up - I'm trying to do a few QGIS
> >>> meetup events in the SE US. We do stickers for Geohipster (I'm one of
> >>> the interviewers) and after last FOSS4GNA I've got GRASS, MapStory,
> >>> Fulcrum etc stickers - but no QGIS.
> >> 
> >> Hi Randal,
> >> 
> >> just for fun I'm asking for a quote now at a local printshop. They were
> >> talking about 'rolls' of round stickers of about 4cm.
> >> 
> >> will let you know more if I know more.
> >> 
> >> feel free to organise something yourself.
> >> 
> >> based on this email thread I decided to stick with
> >> 
> >> https://github.com/qgis/QGIS-Promotion/blob/master/sticker/round3.svg
> >> 
> >> without text
> >> 
> >> Regards,
> >> 
> >> Richard
> 
> ___
> Qgis-community-team mailing list for organizing community resources such as
> documentation, translation etc.. Qgis-community-team@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-community-team

___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] missing processing projects and data for the training manual

[Yves Jacolin]

On Wednesday, July 20, 2016 14:48:43 matteo wrote:
> https://github.com/qgis/QGIS-Documentation/tree/master/source/docs/training_
> manual/exercise_data/processing
> 
> but the zip file misses many of them
> 
> http://qgis.org/downloads/data/training_manual_exercise_data.zip
This is two different locations. A synchronisation is needed or better a link 
to a specific github repository for data sample?

Y.
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] missing processing projects and data for the training manual

[Yves Jacolin]

On Thursday, July 21, 2016 9:19:24 matteo wrote:
> Hi Richard,
> 
> > no scripts.. I fixed the zips some time ago by hand (adding a
> > 'changelog' file in them..
> > 
> > IF you create a script for that... even better ! :-)
> > I think you have to 'merge' the stuff from github with already available
> > data in zip? Or is ALL on github?
> 
> I think it is all on github.. for one exercise I prepared back in
> Nodebo, I loaded project file and data directly on GH, and I think also
> other people did so..
> 
> As you said, it seems just a matter or merging GH in the zip file..
> But it would very useful to make something that keeps those 2 sources
> synchronized..
> 
> > Happy to put a new zip on qgis.org (or ask anybody on irc that has
> > access to qgis)...
> > 
> > Thanks for taking care of this!
> 
> Thank you!
> 
> Cheers
> 
> Matteo
If we use another specific repository, we can easily link to the repository 
tarball:

For example, the one for QGIS source code: 
https://github.com/qgis/QGIS-Documentation/archive/master.zip

What do you think about this?

Y.

___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] missing processing projects and data for the training manual

[Yves Jacolin]

On Thursday, July 21, 2016 9:33:33 matteo wrote:
> Yves,
> 
> you are suggesting to have another repo just for the exercise data?
Yes, basicly, for all data needed for training and GIS introduction!

This doesn't change so much for the current situation, except that we should 
create another repository but all in all, this will improve the data 
management.

Y.

___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] QGIS 2.14 doc available only in english?

[Yves Jacolin]

I tried with docker but I get only english string in the fr directory.

I guess I have to pull transifex string, isn't?

Y.
On Wednesday, July 27, 2016 11:49:01 DelazJ wrote:
> Hi,
> 
> Thanks for the explanations, Richard.
> I'm going to try to build french doc and let you know when it's ready (if
> ever i succeed).
> 
> 2016-07-20 23:22 GMT+02:00 Richard Duivenvoorde :
> > On 20-07-16 11:52, DelazJ wrote:
> > > Hi,
> > > 
> > > Not sure if it's a local issue (i have cleaned my cache) but from any
> > > page of the 2.14 doc i'm unable to find (and thus select) language other
> > > than English.
> > > 
> > > Anyone confirms?
> > 
> > Yes confirmed :-)
> > 
> > I was busy yesterday (left for holiday this morning), but had build
> > errors in the first non-english build I tried (nl)... so decided to not
> > fix those (as I already fixed all non building websites that day), and
> > ask for others to please try to build your language yourself (including
> > pulling the translations from transifex).
> > Problems are often small: translators that break rst because the
> > translate labels (often bronze, silver and gold...), or break the
> > url-construct `xxx `_ etc
> > So: build your languages, fix the warnings/errors in translations untill
> > ok...
> > 
> > So please help and build/fix your language, and let me know when all is
> > ok, I'll then reenable the dropdown and multilingual builds again...
> > 
> > Regards,
> > 
> > Richard
> > ___
> > Qgis-community-team mailing list for organizing community resources such
> > as documentation, translation etc..
> > Qgis-community-team@lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/qgis-community-team

___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] QGIS 2.14 doc available only in english?

[Yves Jacolin]

On Wednesday, July 27, 2016 17:57:57 Richard Duivenvoorde wrote:
> On 27-07-16 11:56, Yves Jacolin wrote:
> > I tried with docker but I get only english string in the fr directory.
> > 
> > I guess I have to pull transifex string, isn't?
> 
> Hi Yves,
> 
> see:
> 
> https://github.com/qgis/QGIS-Documentation/blob/manual_en_2.14/docker-world.
> sh#L29
> 
> langs=fr ./docker-world.sh
> 
> should work...
> 
> Note that ( I think ) you need a .transifexrc with your credentials in
> your home directory, as it is copied into the container to pull the
> strings from transifex
> 
> https://github.com/qgis/QGIS-Documentation/blob/manual_en_2.14/docker-run.sh
> #L7
> 
> also note that it will try to build both pdf and html AND try to sync
> the result to qgis.org (which will fail unless you have a key for
> it)
> 
> Let me know if this works...
> 
> Regards,
> 
Richard,

It fails with this message:
> Warning, treated as error:
> /site/source/site/forusers/support.rst:60: WARNING: inconsistent term 
references in translated message

Looking at transifex, all seems correct but you changed the string 15 days 
ago. Does it meant that my translation files are not uptodate?

I have a ~/.transifexrc file.

Thanks,

Y.

___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] [Qgis-developer] Change PSC Community Manager Role

[Yves Jacolin]

On Thursday, August 25, 2016 22:28:10 Tim Sutton wrote:
> Hi Otto
> 
> > On 23 Aug 2016, at 5:11 PM, Otto Dassau  wrote:
> > 
> > Dear Community,
> > 
> > there will be a change in the QGIS PSC.
> > 
> > I (Otto) decided to step back from my PSC role as Community Advisor. I
> > enjoyed being part of the PSC for a couple of years but realized that I
> > won't find enough time in the future for this job anymore.
> > 
> > At the hackfest in Bonn the PSC decided not to recast the Community
> > Advisor
> > role. Instead there will be team managers who together with a team of
> > contributors will take care about the tasks this role has included so far.
> > 
> > In this context we are happy to announce that we have already found two
> > well known community members to fill this gap - Lene Fischer from Denmark
> > and Yves Jacoline from France. Lene will concentrate on community tasks
> > and Yves on documentation.
> > 
> > More details about the new structure will be announced by the PSC in the
> > near future.
> 
> You have done an amazing job in the QGIS project and in the PSC over the
> years -having great user documentation is a huge selling point for QGIS. I
> thank you on behalf of everyone in the project and we look forward in
> collaborating with you in the future, even if you are no longer actively
> serving on the PSC.
> 
> To Lene and Yves, a huge thank you for stepping in to fill Otto's shoes - we
> could not have asked for more capable substitutes!
> 
> Regards
> 
> Tim
> 
> > Best wishes
> > Otto

Hello,

Back to holidays and after the time needed to read all my waiting email :) I 
am here again.

I would like to thanks Otto also. He did a lot of good jobs on documentation 
and was a great help when I started to contribute. I remember that you tell me 
that I have the skills to contribute during my first QGIS hackfest. Even if I 
started from the most part of my contribution to work on the translation, I am 
now working on the documentation.

This is something I learned working with such a great community: help people 
to contribute, and wait. At one moment, they will contribute more and more. it 
can be sum up with "Plant a seed. Be patient.".

Thanks you Otto :) and the PSC!

Y.

___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

[Qgis-community-team] Call for sponsorship for the QGIS code sprint in Lyon (12-13 december)

[Yves Jacolin]

Hello,

The Francophone local chapter of OSGeo organized in december a developer 
meeting for the QGIS project in Lyon.
 
This is 2 days during which the developers have the opportunity to share and 
work together on the next major QGIS release. This contributors meeting will 
make significant progress on the project.

The OSGeo-fr, organizer of the event, looks for sponsors to fund the event. 
One level of sponsorship 500 € was established. If you wish to contribute 
financially, you can make a donation on our platform: 
https://www.helloasso.com/associations/osgeo-fr/collectes/code-sprint-qgis-2016 
The unused budget will be divided between the OSGeo-fr (max 30%) and 
the QGIS association (> 70% of the remainder).

If you use QGIS on a regular basis, sponsorship of this meeting is an 
opportunity to advance the project.

Your organization wants to provide financial support for OSGeo-fr to set up the 
meeting? Do you want more information? Contact us at conferences 
osgeo.asso.fr.

The deadline for this sponsor call is December 7. However we recommend that 
you contact us promptly to allow the best possible organization.
 
The OSGeo-fr team

signature.asc
Description: This is a digitally signed message part.
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] Documentation about OGC conformance tests

[Yves Jacolin]

On Friday, December 09, 2016 10:49:24 Marco Hugentobler wrote:
> Hi documentation team
> 
> I'd like to add a short description how to install and run the OGC WMS
> conformance tests for QGIS Server. Is
> docs/user_manual/working_with_ogc/ogc_server_support.rst a good place or
> do you have another suggestion?
> 
> Thanks,
> 
Marco,

This is a good question. Who will use this doc? User (even advanced user) or 
developper (ie QGIS contributor).

We could have a developper section as we have an user_manual section or add 
this in the QGIS repository (not the doc one) depending who is the target. 
This developper section could contains "pyqgis_developer_cookbook" and some 
other advanced low level documentation but I am not sure that there will have 
enought doc inside.

So I have no strong opinion but if we choose the user manual, I prefer to add 
this in a new chapter or section, outside ogc_server_support.rst (something at 
the same level though), something like:

Working with OGC Data

QGIS as OGC Data Client
QGIS as OGC Data Server
OGC conformance tests

Regards,

Y.
PS: we will use probably this for the next hackfest, on monday in Lyon :)

___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] Documentation about OGC conformance tests

[Yves Jacolin]

On Friday, December 09, 2016 14:46:40 Marco Hugentobler wrote:
> Yes, the documentation about the OGC conformance tests would probably fit
> into the developers guide. Shall I write it to the developers guide (which
> will then be migrated to the doku) for now?
+1 for me

Let's start like this and move the content later. I will probably do it next 
week at the QGIS code sprint in Lyon (if you are fast enough) :)

Y.
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] [URGENT!] QGIS Seem To Bypass PostgreSQL/PostGIS User Privileges/Permissions

[Yves Jacolin]

Hello,

On vendredi 17 mars 2017 14:18:36 CET Oduware Godwin Osahon wrote:
> QGIS is bypassing the permissions set for the same user in the
> PostgreSQL/PostGIS database

This is not possible, imho. This is not QGIS that protects the edition process 
into your table but PostGreSQL itself.

Did you check that the user is really correct?
Did you check that your credential are still valid when working in QGIS 
(something like transaction or so)?

As far as I know this issue never occurs in my PostGIS training (I am using 
QGIS as viewer for SQL results).

Y.

signature.asc
Description: This is a digitally signed message part.
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] Management of release-independent documents

[Yves Jacolin]

Harrissou,

I agree with you but your 3 propositions are not really proposition because as 
you said 1. is not appropriate (I agree completly with you), 2. needs somt 
work and I think it is not possible to mix branch into transifex or will add 
more complexity and 3. well, ...   :)

For me, if I need a choice between this 3 propositions, I am in favor of #3. 
We can have a "third" repository for a "static" documentation (means not link 
to a QGIS release), WebSite and QGIS doc are the 2 first in my mind.

Y.
Le samedi 22 avril 2017, 19:27:42 CEST DelazJ a écrit :
>  Hi List,
> 
> In the QGIS Documentation repository we maintain and publish different
> documents:
> A/
>- the User Manual
>- the Training Manual
>- the PyQGIS Cookbook
> B/
>- the Documentation Guidelines (how to write the docs)
>- the gentle introduction in GIS (what's GIS)
>- and (coming soon) the Developer Guidelines (rules to contribute to
> QGIS Desktop and Server coding)
> 
> Each time we release a new doc, we actually publish a new version of all
> these documents (in html, and some of them also in pdf) and changes in each
> of these documents are pushed to translation (currently 18 languages
> published).
> 
> While the first three documents are really related to and dependent on QGIS
> versions, the latter are not. Hence I think we should stop releasing them
> altogether and have different cycles of releases:
> - release the manuals when they are ready, as we use to do;
> - and release the others when there are new texts, the way we do for QGIS
> website: this means that there will be a unique version available for these
> documents, hence a unique url and they will be live updated and translated.
> 
> *Why?*
> 
> - The gentle introduction in GIS is almost the same between 2.0, 2.14 and
> testing (except typo and rendering fixes). Should we still publish all the
> versions?
> - The documentation guidelines can change between versions but have
> interest only for the document(s) being written so i'm not sure it's worth
> publishing previous versions: there's actually no reason for anyone to
> check what were the rules in 2.2 e.g.
> - The documentation and developers guidelines will gain to be published and
> translated when they are needed ie, during writing/coding cycle and not
> after the battle, once the targeted version is released.
> - with QGIS 3 and its API break, there are some changes to dev guidelines.
> It makes no sense to put them in 2.18 doc branch so, according to the
> current process, they'd be merged in master branch, hence available in
> testing doc. But the testing documentation will not be released before
> summer 2018 (as of QGIS3.2 release) so no translated version until then.
> While a doc writer should be able to deal with English version of doc
> guidelines, speaking English shouldn't be a prerequisite for coders so,
> imho (from a non English native speaker) it's really a pity in this case.
> 
> 
> *What'd that mean?*
> 
> 1- remove all links to previous versions of these three documents from
> http://qgis.org/en/docs/index.html . By removing these documents for each
> previous release, we will aerate a bit that page and clean it fom unneeded
> and repetitive documents. It will also free space in our storage disks.
> 2- with some magic, point them to a url that won't change  E.g. if someone,
> for some reasons (bookmark, web search...) try to open
> http://docs.qgis.org/2.2/nl/docs/documentation_guidelin
> es/do_translations.html
>  tml> we'll
> rather open something like
> http://docs.qgis.org/nl/docs/documentation_guidelines/do_translations.html
>  tml>
> 
> 3- reorganize the index page to list those unique docs in a more visible
> way.
> 
> The only issue I can see is how do we manage the only version related page
> in documentation guidelines http://docs.qgis.org/testing/
> en/docs/documentation_guidelines/substitutions.html
> 
> *What in the backend?*
> 
> I can see different options:
> 
> 1/ Move (back?) those documents to QGIS website repository; It'd be the
> easiest way but I'm not sure website repo is very appropriate and coherent
> to store doc source files
> 2/ Keeping them in the Documentation repository, use only the master branch
> (the basement and red wire branch of the repo) as source; it means that the
> master branch will generate:
>   - docs in English only (user manual, cookbook and training manual) at
> http://docs.qgis.org/testing/en/docs
>   - and translated docs (gentle introduction, developers and documentation
> guidelines) using e.g. http://docs.qgis.org/nl/docs/ Changes to these
> documents will prioritarily go to master
> That said, I have no idea of the amount of work it'd require, especially on
> Transifex infrastructure (and I do not have the skills to do it)- nor even
> if that's possible.
> 3/ cre

Re: [Qgis-community-team] QGIS in optical networks case study

[Yves Jacolin]

Artur,

I will be happy to add your case study into the website.  thanks!

Harrissou, 

I have no idea what is the best way to do such contribution: mailing list is 
ok for me even if it needs to subscribe.

Y.
Le samedi 22 avril 2017, 19:20:27 CEST DelazJ a écrit :
> Hi,
> 
> Just wanted to know if someone has replied to Artur (and received his
> document) and whether we should add a qgis.org (community manager?) address
> at http://www.qgis.org/en/site/about/case_studies/index.html so that people
> directly send their texts. Or is it intended that people send to (or
> contact beforehand) the mailing-list?
> 
> regards,
> 
> Harrissou
> 
> 2017-04-19 10:23 GMT+02:00 Artur Mamuszka :
> > Hello,
> > 
> > I have a case study about using QGIS in FTTH networks and I would like to
> > share this experience. Can anybody tell me to who personally I should send
> > a document describing case study to be evaluated and published?
> > 
> > --
> > Artur Mamuszka
> > e-mail: artur.mamus...@softelnet.pl
> > 
> > ___
> > Qgis-community-team mailing list for organizing community resources such
> > as documentation, translation etc..
> > Qgis-community-team@lists.osgeo.org
> > https://lists.osgeo.org/mailman/listinfo/qgis-community-team


___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/qgis-community-team

[Qgis-community-team] 2.18 LTR Documentation

[Yves Jacolin]

Hello doc contributors,

Finishing the hackfest we are close to release the 2.18 release of the QGIS 
Documentation.

I planned to work on this all the week to finish my PR waiting to be merged and 
backporting to master/release_2_18, reviewing PR.

Are people available to help reviewing and merging PR? Are you ok to focus on 
issue in 2.16 and 2.18 milestone for this week?

A side note when reviewing, could you use github tools with the following:

1. if you add one comment (even really smal) note the Pr as "changes needed "
2. if the PR is ok (not any comment) mark it as "Approved"
3. if you start a review, assign the ticket to you as a reviewer and keep the 
work going as soon as the PR is merged.

Finally, we have 10 open issues in 2.16 and 2 in 2.18 about python cookbook. I 
am in favor to migrate them to milestone 3.0 except someone can take care of 
it soon.

We had also 3 ticket in 2.18 that I can take care of: #1353, #1835 and #1579. 
If you want to help working on this ticket, fell free to ask!

Thanks all for your help for the documentation!

Y.

signature.asc
Description: This is a digitally signed message part.
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] 2.18 LTR Documentation

[Yves Jacolin]

Hello,

On lundi 1 mai 2017 13:55:10 CEST Alexandre Neto wrote:
> Hello Yves,
> 
> Thanks for all your work this weekend. I tried to keep up and do some work,
> but it was a family tagged weekend :-)
:))
 
> I will try to put some more work this week into solving 2.16 and 2.18
> issues.
great! 

> Do we have a hard deadline for 2.18 documentation? I would say we can keep
> work on it until 2.18 becomes LTR (June?).

No hard deadline but I am available this week and probably next week-end (May 
6-7) . So I would like to give a strong push to finalize it and start thinking 
QGIS 3.0 documentation. Even if there is some new ticket for 2.18, we can make 
the changes when they come.

Harrissou sent an email last week and I have also some concern for the 3.0, 
and I guess you have some ideas.

I will probably triggers a meeting (in june?) to discuss this topic. One 
example of work we need to focus on is the "Add layer" refactoring which will 
lead to a strong changes in the structure of the doc. So if we want to not 
have any problem on doc contribution (like conflicts), we need to plan this.

Y.


> Thanks
> 
> Alex Neto
> 
> Yves Jacolin  escreveu no dia segunda, 1/05/2017 às 14:40:
> > Hello doc contributors,
> > 
> > Finishing the hackfest we are close to release the 2.18 release of the
> > QGIS
> > Documentation.
> > 
> > I planned to work on this all the week to finish my PR waiting to be
> > merged and
> > backporting to master/release_2_18, reviewing PR.
> > 
> > Are people available to help reviewing and merging PR? Are you ok to focus
> > on
> > issue in 2.16 and 2.18 milestone for this week?
> > 
> > A side note when reviewing, could you use github tools with the following:
> > 
> > 1. if you add one comment (even really smal) note the Pr as "changes
> > needed "
> > 2. if the PR is ok (not any comment) mark it as "Approved"
> > 3. if you start a review, assign the ticket to you as a reviewer and keep
> > the
> > work going as soon as the PR is merged.
> > 
> > Finally, we have 10 open issues in 2.16 and 2 in 2.18 about python
> > cookbook. I
> > am in favor to migrate them to milestone 3.0 except someone can take care
> > of
> > it soon.
> > 
> > We had also 3 ticket in 2.18 that I can take care of: #1353, #1835 and
> > #1579.
> > If you want to help working on this ticket, fell free to ask!
> > 
> > Thanks all for your help for the documentation!
> > 
> > Y.___
> > Qgis-community-team mailing list for organizing community resources such
> > as documentation, translation etc..
> > Qgis-community-team@lists.osgeo.org
> > https://lists.osgeo.org/mailman/listinfo/qgis-community-team



signature.asc
Description: This is a digitally signed message part.
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/qgis-community-team

Re: [Qgis-community-team] 2.18 LTR Documentation

[Yves Jacolin]

Harrissou, Alexandre, and all :)

This wish list is great and interesting but really challenging. I have some 
idea about highest priority but we need to find a good way for discussion. Here 
my though (draft for now):

* [june] move all tickets on PyQGIS to 3.0 and close the ones that don't make 
sense to keep (hard to know if we don't have knowledge on PyQGIS API)
* [july] finish the 2.18 documentation, we are almost done but we need some 
time. I have, at least, 2-3 tickets to finalize or start for  the 2.18
* [june-august] create tickets (with special flags) for all you want to see in 
QGIS 3.0, add it in QGIS3 milestone. We can probably use "project" [1] feature 
on github and create  "new", "on discussion", "todo", "need review", "done" 
steps.
* [july-september] vote/discuss on each tickets

We should improve planning (summer holidays will really slow down the work) 
and define the process. Could you give your though (Alexandre)?

Regards,

Y.
[1] https://github.com/qgis/QGIS-Documentation/projects

On dimanche 4 juin 2017 20:36:14 CEST DelazJ wrote:
>  Hi,
> 
> A month later, could be nice to revive this thread and discuss ideas to
> improve QGIS Docs...
> Some of the top topics imho could be :
> - release of 2.18 docs:  If I'm not wrong, the May release was supposed to
> be the new LTR then I guess, given issues that occurred, the LTR release
> will be June's. Are we ready? Status of remaining issues/PR?
> - QGIS3 and link to online documentation (aka the new help system): how
> could we ensure the best experience to the users? Collaboration with dev
> team?
> - Strategy to have the documentation budget always used each year, because
> QGIS documentation has needs and projects (right?).
> 
> I've listed some items that I have in mind and somehow appear to me like
> issues or questions to answer. They are referenced in a wiki page of my
> repository (https://github.com/DelazJ/QGIS-Documentation/wiki/On-the-ro
> ad-to-QGIS3 - a kind of quick cheat sheet). If valuable, we can use it as a
> basis and improve/clean it and produce a more structured and shared doc,
> maybe in the QGIS Doc wiki (I don't really know what is its current status
> - could we put things on it?).
> The main idea would be to come up with plans, strategy or call it the way
> you want we could submit to PSC and dev list (our priorities, what we do
> need help for?...). Another option could be to discuss directly the points
> in (one of?) those lists but I'm afraid, we miss the prioritization step :(
> 
> regards,
> Harrissou
> 
> 2017-05-01 20:03 GMT+02:00 Alexandre Neto :
> > It would be great if we have some help from a developer to tackle the
> > PyQGIS Cookbook issues. I will probably take too much time to make user
> > I'm
> > documenting it correctly...
> > 
> > I would leave big changes in documentation structure to 3.0 milestone. It
> > might be the perfect time for "breaking" the documentation. There will be
> > features documentation that will need to be revisited several times
> > because
> > of all the changes. During that time, it may be the perfect time for us to
> > do a stand by in documenting new features and draw a plan for moving stuff
> > around.
> > 
> > Thanks
> > 
> > Alex
> > 
> > DelazJ  escreveu no dia segunda, 1/05/2017 às 15:15:
> >> Hi,
> >> 
> >> 2017-05-01 15:55 GMT+02:00 Alexandre Neto :
> >>> Hello Yves,
> >>> 
> >>> Thanks for all your work this weekend. I tried to keep up and do some
> >>> work, but it was a family tagged weekend :-)
> >>> 
> >>> Indeed, we had a superYves this hackfest. I also had difficulties in
> >> 
> >> following his rhythm. Nice work!!!
> >> 
> >>> I will try to put some more work this week into solving 2.16 and 2.18
> >>> issues.
> >>> 
> >>> Do we have a hard deadline for 2.18 documentation? I would say we can
> >>> keep work on it until 2.18 becomes LTR (June?).
> >>> 
> >>> Agreed, while it's a good thing to keep this level (or a bit slower :)
> >> 
> >> ?) of production, there's no hard deadline for 2.18 and I can't ensure
> >> that
> >> I'll be available on demand (but still, will do my best)
> >> 
> >> Also note that some no milestoned issues can/should be fixed if we have
> >> time and energy before the release. They are not milestoned as 2.16or
> >> 2.18
> >> either because they are infrastructure issues or they are there for a
> >> long
>

Re: [Qgis-community-team] 2.18 LTR Documentation

[Yves Jacolin]

Alexandre,

On mercredi 14 juin 2017 23:05:49 CEST Alexandre Neto wrote:
> Harrissou et al.,
> 
> Sorry for the silence, but this threads are so big that I never find time
> to read and answer properly.
> 
> Harrissou, thanks for gathering all that ideas and TODOs. Most of them are
> in fact very important for 3.x (I dare to say 3.2 as I don't think we
> should do an official doc release for 3.0).
> 
> Our biggest problem is (still) not having enough human power. We are barely
> able to keep the User's Manual updated on time. Training manual probably is
> few versions behind and PyQGIS cook book I have no idea. So, IMHO, we
> should focus our efforts on what's more important. And for me it's the User
> manual. Which I consider to be mandatory to deliver. The other two are nice
> to have. For the cook book we need developers to take care of it, and the
> training, we need trainers (people o rely on it to give training) to take
> care of it.
> 
> I say we should not ambiss to change 2.18 structure. Nor to make it
> perfect. I would vote for setting a deadline and release the docs, even if
> something was not completed. July would be ok for me.
> 
> From that point on, we can focus on 3.x users manual and all the
> improvements we would like to do. Planning the docs Restructuring would be
> my top priority as we might not be  able to do it again soon​ (to not break
> help links).
> 
> My second priority would go to update the sphinx / bootstrap etc versions.
> 
> Assuming that all tasks make sense, before even go to the PSC, I would add
> a column with the needed (human) resources for each task. That will
> probably determine what is going forward and what is not.
> 
> I would not rush in converting the tasks into github issues for now. a wiki
> or Google Doc may be more practical as we can see the all picture easily.
> And we can elaborate a final document to send to others.

I agree with all above except this part: I am not sure that a wiki or Google 
doc will give you a nice picture of task to do. We can filter issue easily in 
"project" and/or milestone.

Y.



signature.asc
Description: This is a digitally signed message part.
___
Qgis-community-team mailing list for organizing community resources such as 
documentation, translation etc..
Qgis-community-team@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/qgis-community-team