https://wiki.osgeo.org/w/api.php?action=feedcontributions&user=Bakaniko&feedformat=atomOSGeo - User contributions [en]2024-03-28T18:51:53ZUser contributionsMediaWiki 1.35.9https://wiki.osgeo.org/w/index.php?title=FOSS4G&diff=130476FOSS4G2023-07-01T07:50:59Z<p>Bakaniko: /* Overview of past conferences and attendances */</p>
<hr />
<div>== Introduction ==<br />
FOSS4G is the acronym for Free and Open Source Software for Geospatial. It is the annual recurring global event hosted by OSGeo since it's inception in 2006. Its predecessors were rooted in the GRASS and MapServer communities and can be traced back to the beginning of this millennium. Find all recent conference web sites under the year followed by foss4g.org as in http://2011.foss4g.org/<br />
<br />
== History of the Acronym ==<br />
<br />
The FOSS4G was first coined in early 2004 as an acronym for Free and Open Source Software for Geoinformatics by a research group working on I18N of GRASS and MapServer. The first publication defining and using the FOSS4G acronym was published in Japan in March 2004 in a paper entitled [http://dlisv03.media.osaka-cu.ac.jp/contents/osakacu/kiyo/DB00011169.pdf "Development of training material and internationalization of GRASS GIS and MapServer for advancing FOSS4G solutions"] published in the Bulletin of Osaka City University Media Center(ISSN: 1345-4145). It was later used at the<br />
<!-- [http://gisws.media.osaka-cu.ac.jp/grass04/index.php Free/Libre and Open Source Software for Geoinformatics: GIS-GRASS Users Conference] --><br />
[http://www.ces.iisc.ernet.in/energy/water/paper/fossgrdss/conference.htm Free/Libre and Open Source Software for Geoinformatics: GIS-GRASS Users Conference]<br />
held between September 12 - 14, 2004 in Bangkok, Thailand in a publication entitled [http://gisws.media.osaka-cu.ac.jp/grass04/viewabstract.php?id=33 Implementation of Web Map Server Test-bed and Development of Training Material for Advancing FOSS4G Solutions] and subsequently in several<br />
other international and national conferences and meetings.<br />
<br />
<br />
[[File:foss4g2004bkk.jpg]]<br />
<br />
== History of foss4g.org domain name ==<br />
<br />
The foss4g.org (and grass-japan.org) domain was registered to make available to the public the outcome of the project on Internationalization of GRASS5.0 and MapServer. The project was funded by IPA (Information-technology Promotion Agency,Japan). The project was carried in cooperation between Orkney Inc. and Osaka City University(OCU). Apart form software internationalization (i18n), OCU was also responsible for testing, preparation of test data, sample applications and implementation and management of the portal site. The main portal site was made available at www.foss4g.org/FOSS4G/ and also www.grass-japan.org/FOSS4G/<br />
<br />
The domains were registered with Venkatesh Raghavan (aka Venka)and Shinji Masumoto of Osaka City University, Japan in 2003 and the project portal site went online in March 2004. Venkatesh Raghavan (aka Venka)and Shinji Masumoto agreed to donate the foss4g.org domain name to OSGeo on 3rd October 2007 with the understanding that there will be no restrictions on the free usage of the FOSS4G acronym for the legitimate purpose of promoting Free and Open Source Software for Geoinformatics. Subsequent to the transfer of foss4g.org domain name to OSGeo, it was used as a domain name for FOSS4G events since FOSS4G2008 held in Cape Town, South Africa.<br />
<br />
== Organizing FOSS4G ==<br />
The OSGeo [[Conference Committee]] is the steadying factor of FOSS4G over the years. Organization of FOSS4G starts roughly 2 years in advance as the venue rotates around the world when a call for bids is sent out.<br />
<br />
=== Local Organizing Committee ===<br />
All the hands-on ground work is done by a volunteering Local Organizing Committees that form each year and have so far always excelled themselves at putting together a great conference. OSGeo is very thankful and excited to see this much effort going into each conference. As of 2007 all conference web sites can be found under the generic OSGeo URL by replacing the year as in http://2010.foss4g.org/ <br />
<br />
=== Overview of past conferences and attendances ===<br />
{| border="1"<br />
! Event !! Location !! Number of Attendees<br />
-<br />
<br />
|-<br />
| [[FOSS4G 2023]] || Prizren, Kosovo || 683<br />
|-<br />
| [[FOSS4G 2022]] || Firenze, Italia || 1000+<br />
|-<br />
| [[FOSS4G 2021]] || Online - Buenos Aires, Argentina || 1.899<br />
|-<br />
| [[FOSS4G 2020]] || Calgary, Canada || cancelled due COVID<br />
|-<br />
| [[FOSS4G 2019]] || Bucharest, Romania || 1.032<br />
|-<br />
| [[FOSS4G 2018]] || Dar es Salaam, Tanzania || 1.057<br />
|-<br />
| [[FOSS4G 2017]] || Boston, USA || 1.162<br />
|-<br />
| [[FOSS4G 2016]] || Bonn, Germany || 889<br />
|-<br />
| [[FOSS4G 2015]] || Seoul, South Korea || 562<br />
|-<br />
| [[FOSS4G 2014]] || Portland, OR, USA || 858<br />
|-<br />
| [[FOSS4G 2013]] || Nottingham, England || ~800<br />
|-<br />
| [[FOSS4G 2012]] || Beijing, China || cancelled<br />
|-<br />
| [[FOSS4G 2011]] || Denver, USA || 914<br />
|-<br />
| [[FOSS4G 2010]] || Barcelona, Spain || 869<br />
|-<br />
| [[FOSS4G 2009]] || Sydney, Australia || 436<br />
|-<br />
| [[FOSS4G 2008]] || Cape Town, South Africa || 550<br />
|-<br />
| [[FOSS4G 2007]] || Victoria, Canada || 721<br />
|-<br />
| [[FOSS4G2006 | FOSS4G 2006]] || Lausanne, Switzland || 560<br />
|-<br />
| 2005 OSG conference || Minneapolis, MN || 350<br />
|-<br />
| FOSS4G 2004 - [https://gisws.media.osaka-cu.ac.jp/grass04/ Free/Libre and Open Source Software for Geoinformatics]: GIS-GRASS Users Conference || Bangkok, Thailand || ~150<br />
|-<br />
| [https://web.archive.org/web/20040415000450/http://www.omsug.ca/ OSGIS 2004] || Ottawa, Canada || 210<br />
|-<br />
| 2003 MapServer Users Meeting || St Paul, MN, United States || 125<br />
|-<br />
| [http://www.ing.unitn.it/~grass/conferences/GRASS2002/home.html Open Source Free Software GIS] - GRASS users conference 2002 || Trento, Italy || 140<br />
|}<br />
<br />
More detailed metrics of the more recent conferences are here: https://docs.google.com/spreadsheets/d/1BpkO5WOFQ_DZEWNMLj_hAhEre0m0io_j-JGf7geAW5Y/edit?hl=en_GB#gid=57<br />
<br />
== Localized FOSS4G Conferences ==<br />
Some Local Chapters put on localized FOSS4G conferences, for example:<br />
* [http://www.osgeo.kr/ Korean chapter] has held annual FOSS4G Korea conference in Seoul since 2011. <br />
* [http://www.osgeo.jp/ Japan chapter] holds FOSS4G events in Tokyo, Osaka, and Hokkaido each year. <br />
* Germany has the [[FOSSGIS]] conferences in German language. <br />
* Portugal Local Chapter conferences: [http://osgeopt.pt/sasig4 SASIG 4, Guimarães, 2011], [http://lisboa.sigaberto.org SASIG III, Lisboa, 2010], [http://evora.sigaberto.org SASIG II, Évora, 2009], [http://agueda.sigaberto.org SASIG, Águeda, 2008]<br />
* [http://foss4g-na.org/ FOSS4G North America] is an annual event since 2012<br />
* [[Europe]] (formerly "Central and Eastern Europe") is an annual event since 2012<br />
* [http://www.foss4g.org.ar/ FOSS4G Argentina] first occurred in 2013<br />
* [http://lsi.iiit.ac.in/foss4gindia/ FOSS4G India] first occurred in 2013<br />
* [https://osgeo.nl Dutch Local Chapter] had annual OSGeo.nl Day starting in 2012, rebranded to [https://foss4g.nl/ FOSS4G-NL] starting in 2017<br />
* [https://wiki.osgeo.org/wiki/Oceania OSGeo Oceania] organises the annual [https://foss4g-oceania.org/ FOSS4G SotM Oceania] since [https://2018.foss4g-oceania.org 2018].<br />
* ''(please add your own event)''<br />
<br />
=== Roll Your Own Conference ===<br />
If you are interested in organizing "your own" conference please contact the [[Conference Committee]] and advertize on the Discuss Mailing List. OSGeo is always interested in lending a helping hand to seed organize local events. We are also building a [[FOSS4G Cookbook]] to help in planning and executing a FOSS4G conference.<br />
<br />
=== Using the Name FOSS4G ===<br />
FOSS4G is not registered as a trademark but has a long tradition of being used in the context of Free and Open Source Software for Geospatial. The domain was originally registered by [[Venkatesh Raghavan]] (Venka) who later graciously [http://lists.osgeo.org/pipermail/conference_dev/2007-August/000379.html donated] it to OSGeo - under the condition that using the name should stay open to anybody who does something reasonably related to Free and Open Source Geospatial. If you are not sure, simply ask on the main mailing list (starting from [http://lists.osgeo.org/pipermail/discuss/2011-November/009762.html here]).<br />
<br />
<br />
[[Category:FOSS4G]]<br />
[[Category:History]]</div>Bakanikohttps://wiki.osgeo.org/w/index.php?title=FOSS4G_2023_Community_Sprint&diff=130474FOSS4G 2023 Community Sprint2023-07-01T07:14:23Z<p>Bakaniko: </p>
<hr />
<div>== Community Sprint ==<br />
<br />
Also this year, after the conference, there will be the '''OSGeo community sprint'''.<br />
<br />
Participation is free of charge and anyone involved or interested in getting involved in OSGeo community projects is welcome.<br />
<br />
You can choose to contribute to one or more projects. The sky is the limit. There’s always plenty to do – and it’s not all about programming. Translation, documentation, feedback, discussions, and testing are very important for projects! Conference registration is not a prerequisite for participation in the community sprint.<br />
<br />
=== When ===<br />
<br />
The community sprint will be held on 01-02 of July.<br />
* 8:00 - 21:00<br />
<br />
=== Where ===<br />
<br />
The community sprint will be hosted at the Innovation and Training Park Prizren.<br />
* [https://www.openstreetmap.org/?mlat=42.2194195&mlon=20.7531639#map=19/42.2194195/20.7531639 Location on OSM]<br />
<br />
== Registered Attendees ==<br />
<br />
The community sprint is free of charge but we kindly ask you to write down your name for better planning.<br />
<br />
{| border="1" cellpadding="2" class="wikitable sortable"<br />
!width="30"|No<br />
!width="250"|Name<br />
!width="250"|Email<br />
!width="250"|Projects<br />
!width="250"|Registered to FOSS4G conference<br />
!width="250"|Present on Sat 1st<br />
!width="250"|Present on Sun 2nd<br />
|-<br />
|1 || [[User:Astrid_Emde|Astrid Emde]] || astrid_emde osgeo org || OSGeo, OSGeoLive, Mapbender || Yes || Yes || Yes<br />
|+<br />
|2 || [[User:Raymondnijssen|Raymond Nijssen]] || raymond.nijssen terglobo nl || QGIS || Yes || Yes || Yes<br />
|+<br />
|3 || [[User:Ivansanchez|Ivansanchez]] ([[User talk:Ivansanchez|talk]]) || ivan sanchezortega es || Leaflet, Gleo, OGC standards || Yes || Yes || Yes<br />
|+<br />
|4 || [[User:s1m0ns|Simon Šanca]] || simon.sanca hvl no || QGIS, GRASS GIS || Yes || Yes || No<br />
|+<br />
|5 || [[User:Cvvergara|Vicky Vergara]] || vicky.vergara at osgeo.org || pgRouting, OSgeo, OSGeolive || Yes || No || Yes<br />
|+<br />
|6 || [[User:Jesperlarsson|Jesper Larsson]] || jesper.larsson at constellr com || Helping out with anything :) || Yes || Yes || yes<br />
|+<br />
|7 || [[User:Jive|Jody Garnett]] || jody.garnett@gmail.com || OpenGIS Harmonization || yes || yes || yes ||<br />
|+<br />
|8 || [[User:Aaime|Andrea Aime]] || andrea.aime at geosolutionsgroup com || OpenGIS Harmonization || yes || yes || Morning only ||<br />
|+<br />
|9 || [[User:ianturton|Ian Turton]] || ian at ianturton.com || OpenGIS Harmonization || yes || yes || No ||<br />
|+<br />
|10 || [[User:Xamanu|Felix Delattre]] || felix delattre de || Helping out with anything || Yes || Yes || No ||<br />
|+<br />
|11 || [[User:aanthieni|Ariel Anthieni]] || aanthieni at kan dot com dot ar || Geonode || Yes || Yes || x ||<br />
|+<br />
|12 || Walter Shilman || wshilman at kan dot com dot ar || Geonode || Yes || Yes || x ||<br />
|+<br />
|13 || [[User:lads|Luís de Sousa]] || luis dot de dot sousa at protonmail dot com || PyWPS, pygeometa, GRASS || Yes || Yes || Yes ||<br />
|+<br />
|14 || [[User:Just|Just van den Broecke]] || just at gmail dot com || pygeoapi, GeoHealthCheck, map5topo || Yes || Yes || Yes ||<br />
|+<br />
<br />
|15 || [[User:Irdi|Irdi Ismaili]] || irdiismaili11 at protonmail dot com || Helping out with anything|| Yes || Yes || Yes ||<br />
|+<br />
|16 || [[User:kalxas|Angelos Tzotsos]] || tzotsos(at)osgeo.org || pycsw, OSGeoLive, GeoNode, UbuntuGIS, pygeoapi, OTB || Yes || Yes || Yes || <br />
|+<br />
|17 || [[User:jerstlouis|Jerome St-Louis]] || jerome(at)ecere.com || OGC APIs / Styles & Symbology Standards, Ecere SDK, GNOSIS SDK/Map Server/Cartographer || Yes || Yes || Yes || <br />
|+<br />
|18 || [[User:sbl|Stefan Blumentrath]] || stefan.blumentrath@gmx.de || GRASS GIS, actinia || Yes || Yes || Maybe || <br />
|+<br />
|19 || [[User:Smellman|Taro Matsuzawa]] || taro@georepublic.co.jp ||QGIS, SMASH, UNVT || Yes || yes || Maybe ||<br />
|+<br />
|20 || [[User:mwall|Marcel Wallschlaeger]] || marcel.wallschlaeger(at)zalf.de ||GeoNode || Yes || yes || Maybe ||<br />
|+<br />
|21 || [[User:mstuyts|ShogoHirasawa]] || s.hirasawa@eukarya.io || Plug-in development for Re:Earth || Yes || No || Yes ||<br />
|+<br />
|22 || [[User:mstuyts|Hidemichi Baba]] || h.baba@eukarya.io || Plug-in development for Re:Earth || Yes || No || Yes ||<br />
|+<br />
|23 || [[User:mstuyts|Arisa Mikumo ]] || a.mikumo@eukarya.io || Plug-in development for Re:Earth || Yes || No || Yes ||<br />
|+<br />
|24 || [[User:mstuyts|Aki Sato]] || satoaki087@gmail.com || Plug-in development for Re:Earth || Yes || No || Yes ||<br />
|+<br />
|25 || [[User:ricardogsilva|Ricardo Garcia Silva]] || ricardo.garcia.silva@geobeyond.it || pygeoapi, maybe also help with other stuff || Yes || Yes || Yes ||<br />
|+<br />
|26 || [[User:Bdon|Brandon Liu]] || brandon@protomaps.com || OpenLayers, MapLibre GL, QGIS, Protomaps || Yes || Yes || Yes ||<br />
|+<br />
|27 || Yui Matsumura(Yuiseki) || yuiseki at gmail.com || UNVT || Yes || Yes || Maybe ||<br />
|+<br />
|28 || [[User:mstuyts|Michel Stuyts]] || info (at) michelstuyts (dot) be|| QGIS, OSGeoLive || Yes || No || Yes ||<br />
|+<br />
|29 || [[User:Bakaniko|Nicolas Roelandt]] || roelandtn.pro@gmail.com|| OSGeoLive, French Local chapter paperwork || Yes || Yes || Yes ||<br />
|+<br />
|N || my name || my email || projects I will work on || x || x || x ||<br />
|}<br />
<br />
== Workgroups ==<br />
<br />
<br />
=== pgRouting ===<br />
<br />
[[Image:Pgrouting-logo.png|right]]<br />
<br />
==== Attending ====<br />
<br />
* [[User:Cvvergara|Vicky Vergara]]<br />
<br />
==== Goals ====<br />
<br />
* Work on incubation tasks<br />
<br />
=== OpenGIS Harmonization ===<br />
<br />
The OGC GeoAPI Implementation Specification requires exclusive use of the '''org.opengis''' Java package. OSGeo experimented in cross-project collaboration using “geoapi-pending” interfaces defined in the '''org.opengis''' Java package. This activity removes use '''org.opengis''' from OSGeo projects, and provides scripts to help the wider Java community adapt to the change.<br />
<br />
Visit OSGeo [https://www.osgeo.org/opengis-harmonization/ opengis-harmonization] initiative activity background, including sponsorship opportunities. See GeoTools [https://github.com/geotools/geotools/wiki/Remove-OpenGIS wiki] for technical details on is challenge.<br />
<br />
==== Attending ====<br />
<br />
* Jody Garnett<br />
* Andrea Aime<br />
* Ian Turton<br />
<br />
==== Goals ====<br />
<br />
# Introduce an org.geotools.api packages as a drop-in replacement for org.opengis packages<br />
# Pull methods down into existing GeoTools interface and extends relationship<br />
# Produce linux or ant script to migrate client code (to be provided with update instructions)<br />
# Stretch goal: Remove interfaces that have no implementations<br />
<br />
=== GeoNode ===<br />
<br />
Working in contribute to the accessibility of different languages to the official documentation and software<br />
<br />
==== Attending ====<br />
<br />
* Ariel Anthieni<br />
* Walter Shilman<br />
* Marcel Wallschläger<br />
* Irdi Ismaili<br />
<br />
==== Goals ====<br />
<br />
* Review set translation process in transifex<br />
* Think of a proposal to improve the metadata module<br />
* Generate translation proccess form sotfware<br />
<br />
<br />
=== GRASS GIS ===<br />
<br />
[[Image:Grasslogo_vector_small.png|right]]<br />
<br />
<br />
==== Attending ====<br />
<br />
* Stefan<br />
<br />
=== Re:Earth ===<br />
<br />
<br />
Re:Earth" is a WebGIS platform that serves as the foundation for a "digital twin" that reproduces information from physical space in virtual space. This tool is released as open source software, and the source code is freely available. It has the following features<br />
<br />
- Provides an environment for easy utilization of geospatial (physical space) data, which is becoming increasingly complex and large-scale<br />
<br />
- General-purpose for management, analysis, and visualization of geospatial data<br />
<br />
- Realization of WebGIS:<br />
Expanding functionality by developing plug-ins for various fields<br />
Re:Earth" is developed using the latest Web technology, and a full-fledged GIS environment can be easily used on a Web browser without the need for installation. By making Re:Earth open source, we aim to form a worldwide OSS community with engineers from all over the world, including developers of the main unit and plug-ins.<br />
<br />
Visit Re:Earth [https://reearth.io/] . See GitHub [https://github.com/reearth/reearth] .<br />
<br />
==== Attending ====<br />
<br />
* Shogo Hirasawa<br />
* Hidemichi Baba<br />
* Arisa Mikumo<br />
* Aki Sato<br />
<br />
==== Goals ====<br />
<br />
# Create a project in Re:Earth<br />
# Creating Re:Earth plug-ins<br />
<br />
== Event Organization ==<br />
<br />
The [https://2023.foss4g.org/about/ FOSS4G 2023 Team] is the proud organiser of the community sprint.<br />
<br />
For any question you can contact [[User:Raymondnijssen|Raymond Nijssen]], the person in charge of the community sprint. <br />
<br />
<br />
[[Category:FOSS4G2022]] [[Category:FOSS4G]] [[Category:Code_Sprints]]</div>Bakanikohttps://wiki.osgeo.org/w/index.php?title=OSGeoLive&diff=129067OSGeoLive2022-08-28T12:57:12Z<p>Bakaniko: </p>
<hr />
<div>[[image:OSGeo_project.png|right|180px|caption]]<br />
This page is '''deprecated''', please find the latest version here :https://trac.osgeo.org/osgeolive/wiki <br />
= OSGeo-Live wiki docs migrating =<br />
June 2018: OSGeo-Live howto wiki documentation is is in the process of migrating to: https://trac.osgeo.org/osgeolive/wiki<br />
It is best to try the new docs first, then come back to this wiki afterwards if you can't find what you are looking for.<br />
<br />
= About OSGeo-Live =<br />
<br />
[[File:Osgeolive wordle.png|center|link=http://live.osgeo.org|750px]]<br />
<br />
[http://live.osgeo.org OSGeoLive] provides bootable ISO-Images and [http://en.wikipedia.org/wiki/Virtual_machine Virtual Machines] which allow users to try out fully-operational versions of popular Free Geospatial Software without the need to install a thing. <br />
<br />
We do this in large part by maintaining automated build scripts which collect many [[OSGeo]] programs and sample data-sets together, and then combine them to form the Live disc or VM itself. By tweaking these scripts, users are free to make their own custom distributions, for example localized in their own language and with local map data.<br />
<br />
= For users =<br />
== Quick Start ==<br />
* [https://live.osgeo.org/en/quickstart/osgeolive_quickstart.html OSGeoLive Quick Start]<br />
<br />
== Documentation ==<br />
June 2018: The OSGeo-Live documentation process is changing to use transfix and the process for using it is moving wikis to: https://trac.osgeo.org/osgeolive/wiki/How%20to%20document%20a%20project<br />
<br />
It is best to try the new docs first, then come back to wiki pages below if you don't find what you are looking for:<br />
<br />
[[OSGeoLive_AddProject#Documentation]]<br />
<br />
Stable release: http://live.osgeo.org <br />
<br />
Nightly build: http://adhoc.osgeo.osuosl.org/livedvd/docs/en/index.html<br />
<br />
Source is stored in git: https://github.com/OSGeo/OSGeoLive-doc<br />
<br />
== Package List ==<br />
* [https://docs.google.com/spreadsheets/d/1Q5BaEgQtgw4O1bXyeWMlM8XtAOhUgcjZ7Y2O0FZc2H0/edit?hl=en_GB#gid=2014800150 Package List]<br />
* [[Live_GIS_Disc_Packages#Package_wishlist|Future/wishlist]]<br />
<br />
=== Project Metrics ===<br />
* Metrics from Open Hub (former Ohloh): https://www.openhub.net/p/OSGeo-Live<br />
* https://live.osgeo.org/en/metrics.html<br />
* Transifex OSGeoLive Translation Stats: https://www.transifex.com/osgeo/osgeolive/languages/<br />
<br />
== Contact Us ==<br />
Refer to: https://trac.osgeo.org/osgeolive#Communication<br />
<br />
== Downloads ==<br />
<br />
Latest Stable Release: http://live.osgeo.org/en/download.html<br />
<br />
Latest Development Release: http://aiolos.survey.ntua.gr/gisvm/dev/<br />
<br />
Older Releases: http://download.osgeo.org/livedvd<br />
<br />
== Including OSGeoLive at your event ==<br />
[http://live.osgeo.org OSGeoLive] provides a DVD, USB and a Virtual Machine which allow users to try out fully-operational versions of popular Free Geospatial Software without the need to install a thing. It also includes documentation and a comprehensive presentation.<br />
<br />
This is the process to follow if you wish to make use of OSGeoLive at your conference, workshop or similar event.<br />
<br />
; Tell Us<br />
: Add your event to our [[OSGeoLive_History|OSGeoLive History]] page and tell us how you would like to use OSGeoLive on our [http://lists.osgeo.org/mailman/listinfo/live-demo email list] (or email [http://wiki.osgeo.org/wiki/OSGeo_Advocate#Cameron_Shorter Cameron Shorter] directly). Hearing how OSGeoLive is used motivates us to keep going, and we plan releases around upcoming events.<br />
<br />
; Presentation<br />
: Conference attendees appreciate the [http://live.osgeo.org/en/presentation/index.html OSGeoLive Lightning Overview], which explains the breadth of OSGeo software, abstract [http://live.osgeo.org/en/presentation/abstract.txt here]. It is often presented by one of the conference organisors, or keynote speakers. You may wish to find a suitable speaker from the [[OSGeo Advocate]] list. The presentation may be given as is, or modified to align with time constraints, presenter's interest, or conference focus. (For prior variants, see [[Live GIS Presentation]].)<br />
<br />
; Handing out USBs or DVDs<br />
: OSGeoLive DVDs and/or USBs are often handed out to all conference delegates, or a smaller number handed out from an OSGeo booth. DVDs are cheaper (around $2 per copy), but USBs provide a better experience as they are faster to boot up and run. You will need to:<br />
:# Work out how to pay for the USBs/DVDs. Usually the price is factored into event budgets. This means you will require commitment from the event Organisors. However you may find an external sponsor, or for smaller print runs, you might find volunteers to print from their computers.<br />
:# Source a local printer, preferably local. Printers typically require 2 weeks to do the print run, although they often will turn around faster if you pay more money.<br />
:# Printing DVDs: The printer will require an [http://live.osgeo.org/en/download.html ISO image], and artwork for the DVD face and DVD sleeve. You may make use of existing [https://svn.osgeo.org/osgeo/livedvd/artwork/sleeve/ artwork] or create your own.<br />
:# Printing USBs: A 4 Gig USB is required for [http://live.osgeo.org/en/download.html osgeo-live-mini] (8 Gig if you wish the full image with windows and mac installers). The process for installing USBs is described [http://live.osgeo.org/en/quickstart/usb_quickstart.html here]. Note that it is important to ask the printer if they can create '''bootable''' USBs. (We have found that many printers are not familiar with the process). It is prudent to [http://live.osgeo.org/en/quickstart/osgeolive_quickstart.html check] the first USB that is printed before printing the rest. You can also print a logo on the USB.<br />
<br />
; Workshops<br />
: For workshops, we recommend using OSGeoLive from a [http://live.osgeo.org/en/quickstart/virtualization_quickstart.html Virtual Machine] or from a USB. Note that some computers can't boot from a USB. OSGeoLive on a DVD is slow and as such is not recommended for workshops. However it is wise to have a few spare DVDs in case one of your computers can't boot from the USB. Note that OSGeoLive we have heard some issues when running on Apple Macs, so if using Macs, please test first.<br />
; Poster<br />
: We have a [http://wiki.osgeo.org/wiki/OSGeoLive#Poster Poster] which is useful for hanging on a wall of a conference booth.<br />
<br />
== Workshops with OSGeoLive ==<br />
<br />
[[ Workshops with OSGeoLive ]]<br />
<br />
== Presentation ==<br />
<br />
[[ OSGeoLive Presentation ]]<br />
<br />
== Poster ==<br />
<br />
[[OSGeoLive Poster]]<br />
<br />
== History ==<br />
[[Live GIS History]]<br />
<br />
== Testimonials ==<br />
[[OSGeoLive_Testimonials]]<br />
<br />
== Press Releases ==<br />
<br />
This content has being moved to: [https://trac.osgeo.org/osgeolive/wiki/Press%20Releases Press Releases]<br />
<br />
== FAQ ==<br />
* [[Live GIS Disc FAQ]]<br />
<br />
== Want to help? ==<br />
We love volunteers, and would love to hear from you if you would like to help out. Best place to start is to introduce yourself on our [https://wiki.osgeo.org/wiki/Live_GIS_Disc#Contact_Us email list], maybe mention how you'd like to get involved. Here are some ideas about things that you might want to help with:<br />
; Translations: Know another language? Why not join our team of translators:<br />
: http://wiki.osgeo.org/wiki/Live_GIS_Disc#Translate<br />
<br />
; Testing:<br />
; Quickstarts: <br />
; Debian Packaging:<br />
<br />
= Use Cases =<br />
<br />
There are multiple use cases for this product:<br />
<br />
* '''Demo DVD/USB''' that can be handed out at conferences.<br />This will contain a wide variety of applications, preconfigured with some sample data and containing introductory tutorials. It should be able to function completely offline, at least within the scope of the tutorials, and should provide an introduction to many products. This is very much a Live DVD, and as such should be conservative with regards to size (it will be run from RAM).<br />
* '''Education DVD'''<br />This seems to be a more involved version than the Demo DVD, including more involved material, including train-the-trainer style material. This is targeted at those who will be teaching others, be it in workshops or university classes/labs. My expectation (mleslie: feel free to correct me) is that this is more likely to be installed on machines and used as a teaching resource, as opposed to a toy to play with, as with the Demo DVD. This will require material developed through the [[Category:Education|Education initiative]].<br />
* '''Workstation Install DVD'''<br /> This need was seen in Cape Town, where the bandwidth seems to be a very limiting factor. Using the DVD to install either a complete OS, a set of packages to an existing Linux, or Windows installers completely offline is of great value in the developing world. Would it be of greater value to lose the Edu or demo material and put in complete application documentation?<br />
<br />
=For developers or people would like to contribute=<br />
<br />
== How to add a project to OSGeoLive ==<br />
* [[OSGeoLive_Apply| Requesting to add an application to OSGeoLive]]<br />
* [[OSGeoLive_AddProject| OSGeoLive Add Project]]<br />
<br />
== Source code ==<br />
<br />
https://github.com/OSGeo/OSGeoLive<br />
<br />
You can find instructions how to contribute to OSGeoLive source code in the [https://trac.osgeo.org/osgeolive/wiki/Source_code Trac page]<br />
<br />
== License ==<br />
[https://github.com/OSGeo/OSGeoLive/blob/master/LICENSE.txt OSGeoLive license]<br />
<br />
== Issue Tracker ==<br />
Our issue tracker is [http://trac.osgeo.org/osgeolive/query?group=status&component=OSGeoLive&order=priority hosted at OSGeo's Trac system], and you will need to create an [http://www.osgeo.org/osgeo_userid OSGeo UserId] before you can login and edit issues. Please use the following conventions:<br />
; Component field<br />
: Set to `<tt>OSGeoLive</tt>`<br />
; Keywords:<br />
: Milestone: Set to base release version: eg: OSGeoLive11.0<br />
: Keywords: Add the relevant application to the issue (use lower case): eg: "geoserver"<br />
<br />
* [https://trac.osgeo.org/osgeolive/report/10 List of open tickets]<br />
* [https://trac.osgeo.org/osgeolive/report/11 Just those concerning the upcoming release]<br />
* [https://trac.osgeo.org/osgeolive/query?status=closed&group=type&order=priority&component=LiveDVD List of tickets already fixed]<br />
* [https://trac.osgeo.org/osgeolive/query?component=Documentation&group=status&order=priority Documentation tickets]<br />
<br />
== Schedule ==<br />
* [http://spreadsheets.google.com/ccc?key=tMRaCwabv7SiIG3moHEfMrQ&hl=en_GB Live GIS Disc Schedule]<br />
<br />
== Build Process ==<br />
* [[OSGeoLive Build]] instructions<br />
<br />
== Project Steering Committee (PSC) ==<br />
[https://trac.osgeo.org/osgeolive/wiki/OSGeoLive%20PSC OSGeoLive PSC Trac Page]<br />
<br />
== Translate ==<br />
* OSGeoLive Translation Process has been moved here: https://trac.osgeo.org/osgeolive/wiki/translation_on_transifex<br />
* [https://www.transifex.com/osgeo/osgeolive/languages/ Translation Status on Transifex] <br />
* You find the latest Translation Build at: http://adhoc.osgeo.osuosl.org/livedvd/docs/en/index.html (not using Transifex)<br />
* [https://wiki.osgeo.org/wiki/Talk:Live_GIS_Translate Discussion about moving to Transifex]<br />
<br />
== Artwork ==<br />
You can find the artwork sleeves, background images, booklet at:<br />
* http://trac.osgeo.org/osgeo/browser/livedvd/artwork/<br />
<br />
== Review ==<br />
<br />
* [[OSGeoLive Review]]<br />
* [[OSGeoLive_AddProject#Quickstart_Review_Checklist|Quickstart Review]]<br />
<br />
== USB Creation ==<br />
* Quickstart on creating a USB is here: https://live.osgeo.org/en/quickstart/usb_quickstart.html<br />
* Wiki with extra information and tips is here: [[OSGeoLive Quickstart USB]]<br />
<br />
==Code of Conduct==<br />
Within the OSGeoLive community we act respectfully toward others in line with the [http://www.osgeo.org/code_of_conduct OSGeo Code of Conduct].<br />
<br />
== OSGeo Incubation ==<br />
<br />
* [[OSGeoLive_Incubation]]<br />
<br />
== Google Summer of Code ==<br />
* [[Live GIS GSoC 2014]]<br />
* [[Live GIS GSoC 2015]]<br />
* [https://github.com/hotosm/HOT-Project-Ideas/issues/15 Cross project OSGeo-Live and HOT in GSoC 2015]<br />
<br />
<br />
= Links to related projects =<br />
* [http://wiki.debian.org/DebianGis DebianGIS]. We encourage projects to package applications into Debian, which in turn is incorporated into Ubuntu.<br />
* [https://wiki.ubuntu.com/UbuntuGIS UbuntuGIS]<br />
* [http://wiki.osgeo.org/wiki/Enterprise_Linux_GIS Enterprise Linux GIS] packages as RPMs for redhat based systems.<br />
* [http://www.gisvm.com/ GISVM home page] (GIS Virtual Machine by [[Ricardo Pinho]])<br />
* [http://wiki.debian.org/DebianGis/LiveImages DebianGIS Live Image]<br />
: [http://svn.debian.org/viewsvn/pkg-grass/packages/debian-gis/ Build scripts in DebianGIS's SVN]<br />
* [http://livecd.ominiverdi.org/index.php?page=LiveCD&toc=livecd Omniverdi LiveCD project]<br />
* [http://grass.osgeo.org/download/cdrom.php List of live CDs from the GRASS download site]<br />
* [http://wiki.gfoss.it/index.php/LiveDVD-GFOSS.it Gfoss.it live DVD ]<br />
* [http://www.archaeogeek.com/portable-gis.html Portable GIS] - Zero-install GIS for MS Windows on a USB stick<br />
* [http://www.poseidonlinux.org/ Poseidon Linux]<br />
* [http://www.fossgis.de/projekte_gislive.html GISLive] - LiveDVD project from [http://www.fossgis.de FOSSGIS e.V.] (German language)<br />
* [http://imincik.github.io/gis-lab/ GIS.lab] - Automatic deployment of GIS infrastructure<br />
<br />
[[Category: Software Stack]]<br />
[[Category: OSGeoLive]]</div>Bakanikohttps://wiki.osgeo.org/w/index.php?title=OSGeoLive&diff=129066OSGeoLive2022-08-28T12:35:11Z<p>Bakaniko: </p>
<hr />
<div>[[image:OSGeo_project.png|right|180px|caption]]<br />
This page is '''deprecated''', please find the latest version here :https://trac.osgeo.org/osgeolive/wiki <br />
= OSGeo-Live wiki docs migrating =<br />
June 2018: OSGeo-Live howto wiki documentation is is in the process of migrating to: https://trac.osgeo.org/osgeolive/wiki<br />
It is best to try the new docs first, then come back to this wiki afterwards if you can't find what you are looking for.<br />
<br />
= About OSGeo-Live =<br />
<br />
[[File:Osgeolive wordle.png|center|link=http://live.osgeo.org|750px]]<br />
<br />
[http://live.osgeo.org OSGeoLive] provides bootable ISO-Images and [http://en.wikipedia.org/wiki/Virtual_machine Virtual Machines] which allow users to try out fully-operational versions of popular Free Geospatial Software without the need to install a thing. <br />
<br />
We do this in large part by maintaining automated build scripts which collect many [[OSGeo]] programs and sample data-sets together, and then combine them to form the Live disc or VM itself. By tweaking these scripts, users are free to make their own custom distributions, for example localized in their own language and with local map data.<br />
<br />
= For users =<br />
== Quick Start ==<br />
* [https://live.osgeo.org/en/quickstart/osgeolive_quickstart.html OSGeoLive Quick Start]<br />
<br />
== Documentation ==<br />
June 2018: The OSGeo-Live documentation process is changing to use transfix and the process for using it is moving wikis to: https://trac.osgeo.org/osgeolive/wiki/How%20to%20document%20a%20project<br />
<br />
It is best to try the new docs first, then come back to wiki pages below if you don't find what you are looking for:<br />
<br />
[[OSGeoLive_AddProject#Documentation]]<br />
<br />
Stable release: http://live.osgeo.org <br />
<br />
Nightly build: http://adhoc.osgeo.osuosl.org/livedvd/docs/en/index.html<br />
<br />
Source is stored in git: https://github.com/OSGeo/OSGeoLive-doc<br />
<br />
== Package List ==<br />
* [https://docs.google.com/spreadsheets/d/1Q5BaEgQtgw4O1bXyeWMlM8XtAOhUgcjZ7Y2O0FZc2H0/edit?hl=en_GB#gid=2014800150 Package List]<br />
* [[Live_GIS_Disc_Packages#Package_wishlist|Future/wishlist]]<br />
<br />
=== Project Metrics ===<br />
* Metrics from Open Hub (former Ohloh): https://www.openhub.net/p/OSGeo-Live<br />
* https://live.osgeo.org/en/metrics.html<br />
* Transifex OSGeoLive Translation Stats: https://www.transifex.com/osgeo/osgeolive/languages/<br />
<br />
== Contact Us ==<br />
Refer to: https://trac.osgeo.org/osgeolive#Communication<br />
<br />
== Downloads ==<br />
<br />
Latest Stable Release: http://live.osgeo.org/en/download.html<br />
<br />
Latest Development Release: http://aiolos.survey.ntua.gr/gisvm/dev/<br />
<br />
Older Releases: http://download.osgeo.org/livedvd<br />
<br />
== Including OSGeoLive at your event ==<br />
[http://live.osgeo.org OSGeoLive] provides a DVD, USB and a Virtual Machine which allow users to try out fully-operational versions of popular Free Geospatial Software without the need to install a thing. It also includes documentation and a comprehensive presentation.<br />
<br />
This is the process to follow if you wish to make use of OSGeoLive at your conference, workshop or similar event.<br />
<br />
; Tell Us<br />
: Add your event to our [[OSGeoLive_History|OSGeoLive History]] page and tell us how you would like to use OSGeoLive on our [http://lists.osgeo.org/mailman/listinfo/live-demo email list] (or email [http://wiki.osgeo.org/wiki/OSGeo_Advocate#Cameron_Shorter Cameron Shorter] directly). Hearing how OSGeoLive is used motivates us to keep going, and we plan releases around upcoming events.<br />
<br />
; Presentation<br />
: Conference attendees appreciate the [http://live.osgeo.org/en/presentation/index.html OSGeoLive Lightning Overview], which explains the breadth of OSGeo software, abstract [http://live.osgeo.org/en/presentation/abstract.txt here]. It is often presented by one of the conference organisors, or keynote speakers. You may wish to find a suitable speaker from the [[OSGeo Advocate]] list. The presentation may be given as is, or modified to align with time constraints, presenter's interest, or conference focus. (For prior variants, see [[Live GIS Presentation]].)<br />
<br />
; Handing out USBs or DVDs<br />
: OSGeoLive DVDs and/or USBs are often handed out to all conference delegates, or a smaller number handed out from an OSGeo booth. DVDs are cheaper (around $2 per copy), but USBs provide a better experience as they are faster to boot up and run. You will need to:<br />
:# Work out how to pay for the USBs/DVDs. Usually the price is factored into event budgets. This means you will require commitment from the event Organisors. However you may find an external sponsor, or for smaller print runs, you might find volunteers to print from their computers.<br />
:# Source a local printer, preferably local. Printers typically require 2 weeks to do the print run, although they often will turn around faster if you pay more money.<br />
:# Printing DVDs: The printer will require an [http://live.osgeo.org/en/download.html ISO image], and artwork for the DVD face and DVD sleeve. You may make use of existing [https://svn.osgeo.org/osgeo/livedvd/artwork/sleeve/ artwork] or create your own.<br />
:# Printing USBs: A 4 Gig USB is required for [http://live.osgeo.org/en/download.html osgeo-live-mini] (8 Gig if you wish the full image with windows and mac installers). The process for installing USBs is described [http://live.osgeo.org/en/quickstart/usb_quickstart.html here]. Note that it is important to ask the printer if they can create '''bootable''' USBs. (We have found that many printers are not familiar with the process). It is prudent to [http://live.osgeo.org/en/quickstart/osgeolive_quickstart.html check] the first USB that is printed before printing the rest. You can also print a logo on the USB.<br />
<br />
; Workshops<br />
: For workshops, we recommend using OSGeoLive from a [http://live.osgeo.org/en/quickstart/virtualization_quickstart.html Virtual Machine] or from a USB. Note that some computers can't boot from a USB. OSGeoLive on a DVD is slow and as such is not recommended for workshops. However it is wise to have a few spare DVDs in case one of your computers can't boot from the USB. Note that OSGeoLive we have heard some issues when running on Apple Macs, so if using Macs, please test first.<br />
; Poster<br />
: We have a [http://wiki.osgeo.org/wiki/OSGeoLive#Poster Poster] which is useful for hanging on a wall of a conference booth.<br />
<br />
== Workshops with OSGeoLive ==<br />
<br />
[[ Workshops with OSGeoLive ]]<br />
<br />
== Presentation ==<br />
<br />
[[ OSGeoLive Presentation ]]<br />
<br />
== Poster ==<br />
<br />
[[OSGeoLive Poster]]<br />
<br />
== History ==<br />
[[Live GIS History]]<br />
<br />
== Testimonials ==<br />
[[OSGeoLive_Testimonials]]<br />
<br />
== Press Releases ==<br />
<br />
This content has being moved to: [https://trac.osgeo.org/osgeolive/wiki/Press%20Releases Press Releases]<br />
<br />
== FAQ ==<br />
* [[Live GIS Disc FAQ]]<br />
<br />
== Want to help? ==<br />
We love volunteers, and would love to hear from you if you would like to help out. Best place to start is to introduce yourself on our [https://wiki.osgeo.org/wiki/Live_GIS_Disc#Contact_Us email list], maybe mention how you'd like to get involved. Here are some ideas about things that you might want to help with:<br />
; Translations: Know another language? Why not join our team of translators:<br />
: http://wiki.osgeo.org/wiki/Live_GIS_Disc#Translate<br />
<br />
; Testing:<br />
; Quickstarts: <br />
; Debian Packaging:<br />
<br />
= Use Cases =<br />
<br />
There are multiple use cases for this product:<br />
<br />
* '''Demo DVD/USB''' that can be handed out at conferences.<br />This will contain a wide variety of applications, preconfigured with some sample data and containing introductory tutorials. It should be able to function completely offline, at least within the scope of the tutorials, and should provide an introduction to many products. This is very much a Live DVD, and as such should be conservative with regards to size (it will be run from RAM).<br />
* '''Education DVD'''<br />This seems to be a more involved version than the Demo DVD, including more involved material, including train-the-trainer style material. This is targeted at those who will be teaching others, be it in workshops or university classes/labs. My expectation (mleslie: feel free to correct me) is that this is more likely to be installed on machines and used as a teaching resource, as opposed to a toy to play with, as with the Demo DVD. This will require material developed through the [[Category:Education|Education initiative]].<br />
* '''Workstation Install DVD'''<br /> This need was seen in Cape Town, where the bandwidth seems to be a very limiting factor. Using the DVD to install either a complete OS, a set of packages to an existing Linux, or Windows installers completely offline is of great value in the developing world. Would it be of greater value to lose the Edu or demo material and put in complete application documentation?<br />
<br />
=For developers or people would like to contribute=<br />
<br />
== How to add a project to OSGeoLive ==<br />
* [[OSGeoLive_Apply| Requesting to add an application to OSGeoLive]]<br />
* [[OSGeoLive_AddProject| OSGeoLive Add Project]]<br />
<br />
== Source code ==<br />
<br />
https://github.com/OSGeo/OSGeoLive<br />
<br />
You can find instructions how to contribute to OSGeoLive source code in the [https://trac.osgeo.org/osgeolive/wiki/Source_code Trac page]<br />
<br />
== License ==<br />
[https://github.com/OSGeo/OSGeoLive/blob/master/LICENSE.txt OSGeoLive license]<br />
<br />
== Issue Tracker ==<br />
Our issue tracker is [http://trac.osgeo.org/osgeolive/query?group=status&component=OSGeoLive&order=priority hosted at OSGeo's Trac system], and you will need to create an [http://www.osgeo.org/osgeo_userid OSGeo UserId] before you can login and edit issues. Please use the following conventions:<br />
; Component field<br />
: Set to `<tt>OSGeoLive</tt>`<br />
; Keywords:<br />
: Milestone: Set to base release version: eg: OSGeoLive11.0<br />
: Keywords: Add the relevant application to the issue (use lower case): eg: "geoserver"<br />
<br />
* [https://trac.osgeo.org/osgeolive/report/10 List of open tickets]<br />
* [https://trac.osgeo.org/osgeolive/report/11 Just those concerning the upcoming release]<br />
* [https://trac.osgeo.org/osgeolive/query?status=closed&group=type&order=priority&component=LiveDVD List of tickets already fixed]<br />
* [https://trac.osgeo.org/osgeolive/query?component=Documentation&group=status&order=priority Documentation tickets]<br />
<br />
== Schedule ==<br />
* [http://spreadsheets.google.com/ccc?key=tMRaCwabv7SiIG3moHEfMrQ&hl=en_GB Live GIS Disc Schedule]<br />
<br />
== Build Process ==<br />
* [[OSGeoLive Build]] instructions<br />
<br />
== Project Steering Committee (PSC) ==<br />
[https://trac.osgeo.org/osgeolive/wiki/OSGeoLive%20PSC OSGeoLive PSC Trac Page]<br />
<br />
== Translate ==<br />
* [[OSGeoLive Translation Process]] WIP<br />
* [https://www.transifex.com/osgeo/osgeolive/languages/ Translation Status on Transifex] <br />
* You find the latest Translation Build at: http://adhoc.osgeo.osuosl.org/livedvd/docs/en/index.html (not using Transifex)<br />
* [https://wiki.osgeo.org/wiki/Talk:Live_GIS_Translate Discussion about moving to Transifex]<br />
<br />
== Artwork ==<br />
You can find the artwork sleeves, background images, booklet at:<br />
* http://trac.osgeo.org/osgeo/browser/livedvd/artwork/<br />
<br />
== Review ==<br />
<br />
* [[OSGeoLive Review]]<br />
* [[OSGeoLive_AddProject#Quickstart_Review_Checklist|Quickstart Review]]<br />
<br />
== USB Creation ==<br />
* Quickstart on creating a USB is here: https://live.osgeo.org/en/quickstart/usb_quickstart.html<br />
* Wiki with extra information and tips is here: [[OSGeoLive Quickstart USB]]<br />
<br />
==Code of Conduct==<br />
Within the OSGeoLive community we act respectfully toward others in line with the [http://www.osgeo.org/code_of_conduct OSGeo Code of Conduct].<br />
<br />
== OSGeo Incubation ==<br />
<br />
* [[OSGeoLive_Incubation]]<br />
<br />
== Google Summer of Code ==<br />
* [[Live GIS GSoC 2014]]<br />
* [[Live GIS GSoC 2015]]<br />
* [https://github.com/hotosm/HOT-Project-Ideas/issues/15 Cross project OSGeo-Live and HOT in GSoC 2015]<br />
<br />
<br />
= Links to related projects =<br />
* [http://wiki.debian.org/DebianGis DebianGIS]. We encourage projects to package applications into Debian, which in turn is incorporated into Ubuntu.<br />
* [https://wiki.ubuntu.com/UbuntuGIS UbuntuGIS]<br />
* [http://wiki.osgeo.org/wiki/Enterprise_Linux_GIS Enterprise Linux GIS] packages as RPMs for redhat based systems.<br />
* [http://www.gisvm.com/ GISVM home page] (GIS Virtual Machine by [[Ricardo Pinho]])<br />
* [http://wiki.debian.org/DebianGis/LiveImages DebianGIS Live Image]<br />
: [http://svn.debian.org/viewsvn/pkg-grass/packages/debian-gis/ Build scripts in DebianGIS's SVN]<br />
* [http://livecd.ominiverdi.org/index.php?page=LiveCD&toc=livecd Omniverdi LiveCD project]<br />
* [http://grass.osgeo.org/download/cdrom.php List of live CDs from the GRASS download site]<br />
* [http://wiki.gfoss.it/index.php/LiveDVD-GFOSS.it Gfoss.it live DVD ]<br />
* [http://www.archaeogeek.com/portable-gis.html Portable GIS] - Zero-install GIS for MS Windows on a USB stick<br />
* [http://www.poseidonlinux.org/ Poseidon Linux]<br />
* [http://www.fossgis.de/projekte_gislive.html GISLive] - LiveDVD project from [http://www.fossgis.de FOSSGIS e.V.] (German language)<br />
* [http://imincik.github.io/gis-lab/ GIS.lab] - Automatic deployment of GIS infrastructure<br />
<br />
[[Category: Software Stack]]<br />
[[Category: OSGeoLive]]</div>Bakanikohttps://wiki.osgeo.org/w/index.php?title=FOSS4G_2022/Community_sprint&diff=129006FOSS4G 2022/Community sprint2022-08-26T09:40:43Z<p>Bakaniko: </p>
<hr />
<div>== Code Sprint ==<br />
<br />
Also this year, after the online conference, there will be the '''OSGeo community sprint'''.<br />
<br />
Participation is free of charge and anyone involved or interested in getting involved in OSGeo community projects is welcome.<br />
<br />
This year we will try to offer the format '''an hour with the developer''', where we ask seasoned community members to donate time for welcoming new members and introduce them to different projects or guide them through the setup of the development environment or translation tools and get started on the Foss4G journey. <br />
<br />
You can choose to contribute to one or more projects. The sky is the limit. There’s always plenty to do – and it’s not all about programming. Translation, documentation, feedback, discussions, and testing are very important for projects! Conference registration is not a prerequisite for participation in the code sprint.<br />
<br />
=== When ===<br />
<br />
The code sprint will be held on 27-28 of August.<br />
<br />
=== Where ===<br />
<br />
The codesprint will be hosted at the University of Florence. <br />
<br />
More information about the rooms and social channels for the codesprint will be notified later.<br />
<br />
== Registered Attendees ==<br />
<br />
The code sprint is free of charge but we kindly ask you to write down your name for better planning.<br />
<br />
{| border="1" cellpadding="2" class="wikitable sortable"<br />
!width="30"|No<br />
!width="250"|Name<br />
!width="250"|Email<br />
!width="250"|Projects<br />
!width="250"|Registered to FOSS4G conference<br />
!width="250"|Present on Sat 27th<br />
!width="250"|Present on Sun 28th<br />
|-<br />
|1 || Andrea Antonello || andrea.antonello at gmail || Codesprint Org, [https://www.geopaparazzi.org/smash/index.html SMASH], [https://integratedmodelling.org/getting-started/ k.LAB] || x || x || x<br />
|-<br />
|2 || Jody Garnett || jody.garnett at gmail.com || geotools.org, geoserver.org || x || ||<br />
|-<br />
|3 || Vicky Vergara || vicky at georepublic.de || pgRoutig, OSGeoLive, OSGeo Website || x || || x<br />
|-<br />
|4 || Markus Neteler || neteler at osgeo.org || GRASS GIS, actinia, GRASS Website || x || ||<br />
|-<br />
|5 || Howard Butler || howard at hobu.co || PDAL, GDAL, and PROJ || x || ||<br />
|-<br />
|6 || Akin Kuye || t_kuye@yahoo.com || Codesprint Org, SMASH || x || ||<br />
|-<br />
|7 || Emmanuel Dubois || emmanuel.dubois@cnes.fr || OTB and 3D CNES tools: CARS, pandora, demcompare || x || ||<br />
|-<br />
|8 || Anna Petrasova || wenzeslaus gmail com || GRASS GIS || x || x || x<br />
|-<br />
|9 || Vaclav Petras || kratochanna gmail com || GRASS GIS || x || x || x<br />
|-<br />
|10 || Tom Kralidis || tomkralidis gmail com || Geopython (pygeoapi, pycsw, pygeometa, OWSLib, etc.) || x || || x<br />
|-<br />
|11 || Veronica Andreo || veroandreo gmail com || GRASS GIS || x || x || <br />
|-<br />
|12 || [user:astrid_emde|Astrid Emde] || astrid dot emde at wheregroup dot com || Mapbender / OSGeoLive || x || x || -<br />
|-<br />
|13 || Silvia Franceschi || silvia.franceschi at gmail || Codesprint Org, [https://www.geopaparazzi.org/smash/index.html SMASH], [https://integratedmodelling.org/getting-started/ k.LAB] || x || x || x<br />
|-<br />
|14 || Luca Delucchi || lucadeluge gmail com || GRASS GIS, OSGeoLive || x || x || x<br />
|-<br />
|15 || Laura Mugeha || mugeha dot okole at gmail dot com || OSGeoLive || x || x || x<br />
|-<br />
|16 || Caitlin Haedrich || caitlin dot haedrich gmail com || GRASS GIS || x || x || x<br />
|-<br />
|17 || Linda Kladivova || lindakladivova gmail com || GRASS GIS || x || x || <br />
|-<br />
|18 || Torsten Friebe || friebe AT lat-lon DOT de || deegree || x || x || x<br />
|-<br />
|19 || Luigi Ponti || quartese at gmail.com || GRASS GIS || || x || ?<br />
|-<br />
|20 || Carmen Tawalika || tawalika at mundialis dot de || actinia || x || x || ?<br />
|-<br />
|21 || Taro Matsuzawa || taro at georepublic dot de || OSGeoLive || x || || <br />
|-<br />
|22 || Weston Renoud || weston dot renoud at qps dot nl || PDAL, GDAL, and PROJ || x || x || x<br />
|-<br />
|22 || Joris Van den Bossche || joris at voltrondata dot com || Shapely/GEOS, GeoPandas || x || x || <br />
|-<br />
|23 || Jerome Jacovella-St-Louis || jerome at ecere dot com || OGC Styles & Symbology || x || x || x<br />
|-<br />
|24 || Olivier Ertz || olivier dot ertz at heig-vd dot ch || OGC Styles & Symbology || x || x ||<br />
|-<br />
|25 || Maxime Collombin || maxime dot collombin at heig-vd dot ch || OGC Styles & Symbology || x || x ||<br />
|-<br />
|26 || Ariel Anthieni || aanthieni at kan dot com dot ar || Geonode || x || x || x ||<br />
|-<br />
|27 || Walter Shilman || wshilman at kan dot com dot ar || Geonode || x || x || x ||<br />
|-<br />
|28 || Mara Rojas || mrojas at kan dot com dot ar || Geonode || x || x || x ||<br />
|-<br />
|29 || Julia Martinuzzi || jmartinuzzi at kan dot com dot ar || Geonode || x || x || x ||<br />
|-<br />
|30 || Corey White || ctwhite48 at gmail dot com || GRASS GIS, actinia, OpenPlains || x || || ||<br />
|-<br />
|31 || Piero Toffanin || pt at uav4geo.com || OpenDroneMap, DroneDB || x || x ||<br />
|-<br />
|32 || Luca Di Leo || ldileo at digipa.it || OpenDroneMap, DroneDB || x || x ||<br />
|-<br />
|33 || Luís de Sousa || luis dot de dot sousa at protonmail dot ch || Geopython (pygeoapi, pycsw, pygeometa, OWSLib, etc.) || x || x || x||<br />
|-<br />
|34 || Pete Gadomski || pete.gadomski at Gmail || pystac, pystac-client, stactools || x || x || ||<br />
|-<br />
|35 || Krishna Lodha || me at krisnaglodha.com || Geopython || x || x || x ||<br />
|-<br />
|36 || Xu Cong || red at eukarya.io || [https://reearth.io/ Re:Earth], Re:Earth-Plugin, Re:Earth-Flow || x || x || ||<br />
|-<br />
|37 || Ondřej Pešek || pesej dot ondrek at gmail || GRASS GIS || x || x || x ||<br />
|-<br />
|38 || Jakub Nowosad || nowosad dot jakub at gmail || Geocomputation with R || x || x || ||<br />
|-<br />
|39 || Arisa Mikumo || arisamikumo at eukarya.io || [https://reearth.io/ Re:Earth], Re:Earth-Plugin, Re:Earth-Flow || x || x || ||<br />
|-<br />
|40 || Howard Butler || howard at hobu.co || PROJ, GDAL, PDAL || x || x || ||<br />
|-<br />
|41 || A nice guy that didn't have wiki access... || ...so I took a picture of his badge... || ...but then my phone broke. So this is his place :-) || x || x || x ||<br />
|-<br />
|42 || Nick Bearman || nick at geospatialtrainingsolutions.co.uk || R-Spatial, Geocomputation with R|| x || x || ||<br />
|-<br />
|43 || Angelos Tzotsos || tzotsos at osgeo.org || OSGeoLive, pycsw, pygeoapi, GeoNode, OWSLib|| x || || x ||<br />
|-<br />
|44 || Nicolas Roelandt || roelandtn.pro at gmail.com || OSGeoLive, r-spatial || x || x || (x) ||<br />
|-<br />
|45 || my name || my email || projects I will work on || x || x || x ||<br />
|}<br />
<br />
== Workgroups ==<br />
<br />
=== Project-name ===<br />
<br />
To participate, copy this project skeleton and start a section below (alphabetically) for your project.<br />
<br />
==== Attending ====<br />
<br />
*user <br />
*user<br />
<br />
==== Goals ====<br />
<br />
*your goals<br />
<br />
==== Participation at '''an hour with the developer''' ====<br />
<br />
* name of the developer - time/day of availability<br />
<br />
=== GeoServer ===<br />
<br />
Working on GeoServer community goals.<br />
<br />
==== Attending ====<br />
<br />
* jody.garentt<br />
<br />
==== Goals ====<br />
<br />
* Dropping Java 8 - removing java 8 from our documentation and build process is a good team activity that can support a wide range of skills<br />
* Java 17 LTS - it is working now with lots of "add opens" for easymock testing; migrating these tests to mockito is a good technical activity<br />
<br />
==== Participation at '''an hour with the developer''' ====<br />
<br />
* Jody Garnett, standing offer to help new developers checkout and build GeoServer during sprint<br />
<br />
=== GRASS GIS ===<br />
<br />
[[Image:Grasslogo_vector_small.png|right]]<br />
<br />
==== Attending ====<br />
<br />
* Markus Neteler<br />
* Anna Petrasova<br />
* Vaclav Petras<br />
* Veronica Andreo<br />
* Luca Delucchi<br />
* Wolf Bergenheim (online)<br />
* Ondřej Pešek<br />
<br />
==== Goals ====<br />
<br />
* Help starting contributors.<br />
* Python and command line usability issues.<br />
* Discuss hard-to-finish PRs.<br />
* Sync with the PDAL project.<br />
<br />
==== Participation at '''an hour with the developer''' ====<br />
<br />
* Vaclav (Vashek) Petras - times: find me, ask me ([[User:Wenzeslaus]])<br />
<br />
=== SMASH ===<br />
<br />
Working on SMASH digital field mapping app enhancements.<br />
<br />
==== Attending ====<br />
<br />
* Andrea Antonello<br />
* Silvia Franceschi<br />
* Akin Kuye<br />
* Fredric R<br />
<br />
==== Goals ====<br />
<br />
* bugfixing<br />
* server-app enhancements<br />
<br />
==== Participation at '''an hour with the developer''' ====<br />
<br />
* Andrea Antonello - time to be defined, based on organization issues<br />
<br />
=== pgRouting ===<br />
<br />
* Working on tasks for becoming an OSGeo project<br />
* Release of v3.3.2<br />
<br />
==== Attending ====<br />
<br />
* vicky Vergara<br />
<br />
==== Goals ====<br />
<br />
* Work on tasks to become an OSGeo project<br />
<br />
==== Participation at '''an hour with the developer''' ====<br />
<br />
* Vicky Vergara - Sunday all day<br />
<br />
=== deegree ===<br />
<br />
Working on [https://github.com/deegree/deegree3/issues open issues] for deegree 3.5.<br />
<br />
==== Attending ====<br />
<br />
* Torsten Friebe [[User:Tfr42]]<br />
<br />
==== Goals ====<br />
<br />
* improvements for 3.4 and 3.5 <br />
<br />
==== Participation at '''an hour with the developer''' ====<br />
<br />
* Torsten Friebe - Saturday, time to be defined, find & ask me or join the IRC channel [https://web.libera.chat/#deegree #deegree] and get in contact.<br />
<br />
=== pygeoapi ===<br />
<br />
The pygeoapi team will be working on the [https://github.com/geopython/pygeoapi/issues issue backlog].<br />
<br />
==== Attending ====<br />
<br />
* Tom Kralidis (day 2 [Sunday])<br />
* Luís de Sousa<br />
<br />
==== Goals ====<br />
<br />
* 0.13 release<br />
<br />
==== Participation at '''an hour with the developer''' ====<br />
<br />
* Tom Kralidis, standing offer to help new developers with pygeoapi (please contact me to setup time)<br />
<br />
=== pycsw ===<br />
<br />
The pycsw team will be working on the [https://github.com/geopython/pycsw/issues issue backlog].<br />
<br />
==== Attending ====<br />
<br />
* Tom Kralidis (day 2 [Sunday])<br />
<br />
==== Goals ====<br />
<br />
* JSON storage<br />
<br />
==== Participation at '''an hour with the developer''' ====<br />
<br />
* Tom Kralidis, standing offer to help new developers with pycsw (please contact me to setup time)<br />
<br />
=== pygeometa ===<br />
<br />
Exploratory work on new functionality for the Semantic Web.<br />
<br />
==== Attending ====<br />
<br />
* Luís de Sousa<br />
<br />
==== Goals ====<br />
<br />
* Map pygeoeta abstraction to meta-data ontologies: VCard, Doublin Core, DCat, Provenance, etc.<br />
* Design method(s) for RDF output <br />
<br />
==== Participation at '''an hour with the developer''' ====<br />
<br />
* TBC<br />
<br />
=== pystac-client (and stactools, and pystac) ===<br />
<br />
The Python STAC ecosystem.<br />
<br />
==== Attending ====<br />
<br />
* Pete Gadomski (Saturday only)<br />
<br />
==== Goals ====<br />
<br />
* Release v0.5.0 of pystac-client (PR already open)<br />
* Triage (and create) issues for v0.6 of pystac-client<br />
* Roadmap v1.0 of pystac-client<br />
* General work and help on the other Python STAC libraries<br />
<br />
==== Participation at '''an hour with the developer''' ====<br />
<br />
* Pete Gadomski, really whenever on Saturday<br />
<br />
=== OpenStreetMap Galaxy ===<br />
<br />
Introducing and help set up development environment for various software components involving [https://galaxy.hotosm.org Galaxy]<br />
<br />
==== Attending ====<br />
<br />
* ramya<br />
* kshitij<br />
* robsavoye<br />
<br />
==== Goals ====<br />
<br />
* Successfully setup development environments for various Galaxy components and understand the code base<br />
<br />
==== Participation at '''an hour with the developer''' ====<br />
<br />
* Kshitij Sharma - available on Saturday & Sunday<br />
* Rob Savoye - available on Saturday & Sunday<br />
<br />
=== OGC Styles and Symbology ===<br />
<br />
The OGC Styles and Symbology team will be working on a minor revision to the conceptual and logical model (SymCore) as well as extensions for styling vector features and coverage. [https://github.com/opengeospatial/styles-and-symbology/issues issue backlog].<br />
<br />
==== Attending ====<br />
<br />
* Jerome Jacovella-St-Louis (Saturday and Sunday)<br />
* Olivier Ertz (Saturday)<br />
* Maxime Collombin (Saturday)<br />
<br />
==== Goals ====<br />
<br />
* https://github.com/opengeospatial/styles-and-symbology/issues/5<br />
* https://github.com/opengeospatial/styles-and-symbology/issues/6<br />
* https://github.com/opengeospatial/styles-and-symbology/issues/8<br />
* https://github.com/opengeospatial/styles-and-symbology/issues/10<br />
* https://github.com/opengeospatial/styles-and-symbology/issues/11<br />
<br />
<br />
=== GeoNode ===<br />
<br />
Working in contribute to the accessibility of different languages to the official documentation.<br />
<br />
==== Attending ====<br />
<br />
* Ariel Anthieni<br />
* Mara Rojas<br />
* Walter Shilman<br />
* Julia Martinuzzi<br />
<br />
==== Goals ====<br />
<br />
* Automation of file generation for transifex<br />
* Set translation process in transifex<br />
* Think of a proposal to improve the metadata module<br />
<br />
==== Participation at '''an hour with the developer''' ====<br />
<br />
* <br />
<br />
=== Shapely (GEOS), GeoPandas ===<br />
<br />
Getting started with contributing to Shapely or GeoPandas. Helping with finalizing the Shapely 2.0 release.<br />
<br />
==== Attending ====<br />
<br />
* Joris Van den Bossche (Saturday)<br />
<br />
==== Goals ====<br />
<br />
* Shapely 2.0 milestone issues: https://github.com/shapely/shapely/milestone/43<br />
* GeoPandas issue and PR backlog<br />
<br />
==== Participation at '''an hour with the developer''' ====<br />
<br />
* Joris Van den Bossche (Saturday)<br />
<br />
=== Geocomputation with R ===<br />
<br />
Working on the second edition of the Geocomputation with R book with a focus on the bridges between R and GRASS GIS. <br />
<br />
==== Attending ====<br />
<br />
* Jakub Nowosad<br />
<br />
==== Goals ====<br />
<br />
* Help people interested in #rspatial and Geocomputation with R<br />
* To test connection between the rgrass R package and GRASS GIS<br />
* To write a section on the bridges between R and GRASS GIS<br />
<br />
==== Participation at '''an hour with the developer''' ====<br />
<br />
* Jakub Nowosad - Saturday (all day)<br />
<br />
=== R-Spatial ===<br />
<br />
Working on registering R-Spatial with OSGeo, if needed. <br />
<br />
==== Attending ====<br />
<br />
* Nick Bearman<br />
* Nicolas Roelandt<br />
==== Goals ====<br />
<br />
* Work on application for R-Spatial as an OSGeo project (if needed)<br />
<br />
==== Participation at '''an hour with the developer''' ====<br />
<br />
* Nick Bearman - Saturday (all day)<br />
<br />
<br />
[[Category:FOSS4G2022]] [[Category:FOSS4G]] [[Category:Code_Sprints]]</div>Bakanikohttps://wiki.osgeo.org/w/index.php?title=FOSS4G_2021/Community_sprint&diff=127304FOSS4G 2021/Community sprint2021-09-29T20:32:26Z<p>Bakaniko: /* Registered Attendees */</p>
<hr />
<div>== Code Sprint ==<br />
<br />
Also this year, after the online conference, there will be the '''OSGeo community sprint'''.<br />
<br />
Participation is free of charge and anyone involved or interested in getting involved in OSGeo community projects is welcome.<br />
<br />
You can choose to contribute to one or more projects. The sky is the limit. There’s always plenty to do – and it’s not all about programming. Translation, documentation, feedback, discussions, and testing are very important for projects! Conference registration is not a prerequisite for participation in the code sprint.<br />
<br />
<!-- shouldn't we say something about the planned activities - or WIP plans?? Also, the room will be open the whole week, AFAIU, shouldn't we say so?? --><br />
=== When ===<br />
The code sprint will be held on Saturday October 2nd, 2021.<br />
<br />
=== Where ===<br />
Online, we will use [https://workadventu.re/ WorkAdventu.re] plus a bounce of Jitsi channels for each project.<br />
<br />
== Registered Attendees ==<br />
<br />
The code sprint is free of charge but we kindly ask you to write down your name for better planning.<br />
<br />
{| border="1" cellpadding="2" class="wikitable sortable"<br />
!width="30"|No<br />
!width="250"|Name<br />
!width="250"|Email<br />
!width="250"|Projects<br />
!width="250"|Registered to FOSS4G conference<br />
|-<br />
|1 || [[User:Lucadelu|Luca Delucchi]] || lucadeluge gmail com || GRASS GIS, pyModis, OSGeoLive (code sprint organizer) || x<br />
|-<br />
|2 || [[User:Cvvergara|Vicky Vergara]] || vicky at georepublic de || Contributions with Translations|| x<br />
|-<br />
|3 || [[User:Astrid_emde|Astrid Emde]] || astrid_emde at osgeo dot org || OSGeoLive, Mapbender, OSGeo || x<br />
|-<br />
|4 || [[User:Veroandreo|Vero Andreo]] || veroandreo at gmail dot com || GRASS GIS || x<br />
|-<br />
|5 || [[User:Tomkralidis|Tom Kralidis]] || tomkralidis at gmail dot com || Geopython, MapServer, QGIS, go-spatial || x<br />
|-<br />
|6 || Shubham|Shubham Kumar || 2020kucp1062@iiitkota.ac.in || Project ||<br />
|-<br />
|7 || [[User:kalxas|Angelos Tzotsos]] || tzotsos at osgeo dot org || pycsw, OSGeoLive, Geopython || x<br />
|-<br />
|8 || Carmen Tawalika || carmen.tawalika at gmail dot com || actinia || x<br />
|-<br />
|9 || [[User:Neteler|Markus Neteler]] || neteler at osgeo dot org || GRASS GIS, actinia || x<br />
|-<br />
|10 || Anika Weinmann || weinmann at mundialis dot de || GRASS GIS, actinia || x<br />
|-<br />
|11 || Guido Riembauer || riembauer at mundialis dot de || GRASS GIS, actinia || x<br />
|-<br />
|12 || [[User:mmetz|Markus Metz]] || metz at mundialis dot de || GRASS GIS, actinia ||<br />
|-<br />
|13 || [[User:Robe|Regina Obe]] || lr at pcorp dot us || PostGIS, pgRouting, Translations || x<br />
|-<br />
|14 || [[User:Bakaniko|Nicolas Roelandt]] || roelandtn.pro at gmail dot com || OSGeoLive || x)<br />
|-<br />
|15 || [[User:Chrismarx|Chris Marx]] || chrismarx at gmail dot com || Unaffiliated || x<br />
|-<br />
|16 || [[User:Pkopparla|Pushkar Kopparla]] || pushkarkopparla at gmail dot com || Unaffiliated || <br />
|-<br />
|17 || [[User:LauraMugeha|Laura Mugeha]] || mugeha dot okole at gmail dot com || Unaffiliated || x<br />
|-<br />
|18 || [[User:Felipebarros|Felipe Barros]] || felipe.b4rros at gmail dot com || Unaffiliated || x<br />
|-<br />
|18 || [[User:Jive|Jody Garnett]] || jody.garnett@gmail.com || GeoTools, GeoServer, OSGeo || x<br />
|-<br />
|20 || [[User:Wolf|Wolf Bergenheim]] || wolf _at_ bergenheim.net || Unaffiliated (GRASS and GDAL in the past) || x<br />
|}<br />
<br />
== Workgroups ==<br />
<br />
=== Project-name ===<br />
To participate, copy this project skeleton and start a section below for your project.<br />
<br />
'''Attending:''' <br />
*user <br />
*user<br />
<br />
'''Goals:''' <br />
*your goals<br />
<br />
<br />
=== GRASS GIS ===<br />
''' Attending:'''<br />
* [[User:Lucadelu|Luca Delucchi]]<br />
* [[User:Veroandreo|Vero Andreo]]<br />
* [[User:Neteler|Markus Neteler]]<br />
* Anika Weinmann<br />
* Guido Riembauer<br />
* [[User:mmetz|Markus Metz]]<br />
* [[User:Wolf|Wolf Bergenheim]]<br />
* ...<br />
<br />
'''Goals:''' <br />
* TBD<br />
<br />
=== Contributions with translations ===<br />
Translations on transifex<br />
Please register to any of your favorite projects:<br />
* OSGeoLive: https://www.transifex.com/osgeo/osgeolive<br />
* pgRouting: https://www.transifex.com/pgrouting/pgrouting<br />
* PostGIS: https://www.transifex.com/postgis/postgis<br />
''' Attending:'''<br />
* [[User:Cvvergara|Vicky Vergara]]<br />
* [[User:robe|Regina Obe]]<br />
<br />
'''Goals:''' <br />
* Translations<br />
<br />
=== actinia ===<br />
''' Attending:'''<br />
* Carmen Tawalika<br />
* [[User:Neteler|Markus Neteler]]<br />
* Anika Weinmann<br />
* Guido Riembauer<br />
* ...<br />
<br />
'''Goals:''' <br />
* see https://github.com/mundialis/actinia_core/projects/2<br />
<br />
=== OSGeoLive ===<br />
<br />
'''Attending:''' <br />
* [[User:Bakaniko|Nicolas Roelandt]]<br />
<br />
<br />
'''Goals:''' <br />
* Update translations<br />
* Work on translations<br />
<br />
=== GeoServer ===<br />
<br />
'''Attending:''' <br />
* [[User:Jive|Jody Garnett]]<br />
<br />
<br />
'''Goals:''' <br />
* User interface layout improvements<br />
<br />
[[Category:FOSS4G2021]] [[Category:FOSS4G]] [[Category:Code_Sprints]]</div>Bakanikohttps://wiki.osgeo.org/w/index.php?title=FOSS4G_2021/Community_sprint&diff=127225FOSS4G 2021/Community sprint2021-08-24T17:51:08Z<p>Bakaniko: /* Workgroups */</p>
<hr />
<div>== Code Sprint ==<br />
<br />
Also this year, after the online conference, there will be the '''OSGeo community sprint'''.<br />
<br />
Participation is free of charge and anyone involved or interested in getting involved in OSGeo community projects is welcome.<br />
<br />
You can choose to contribute to one or more projects. The sky is the limit. There’s always plenty to do – and it’s not all about programming. Translation, documentation, feedback, discussions, and testing are very important for projects! Conference registration is not a prerequisite for participation in the code sprint.<br />
<br />
<!-- shouldn't we say something about the planned activities - or WIP plans?? Also, the room will be open the whole week, AFAIU, shouldn't we say so?? --><br />
=== When ===<br />
The code sprint will be held on Saturday October 2nd, 2021.<br />
<br />
=== Where ===<br />
Online, we will use [https://workadventu.re/ WorkAdventu.re] plus a bounce of Jitsi channels for each project.<br />
<br />
== Registered Attendees ==<br />
The code sprint is free of charge but we kindly ask you to write down your name for better planning.<br />
<br />
{| border="1" cellpadding="2" class="wikitable sortable"<br />
!width="30"|No<br />
!width="250"|Name<br />
!width="250"|Email<br />
!width="250"|Projects<br />
!width="250"|Registered to FOSS4G conference<br />
|-<br />
|1 || [[User:Lucadelu|Luca Delucchi]] || lucadeluge gmail com || GRASS GIS, pyModis, OSGeoLive (code sprint organizer) || x<br />
|+<br />
|2 || [[User:Cvvergara|Vicky Vergara]] || vicky at georepublic de || Contributions with Translations|| x<br />
|+<br />
|3 || [[User:Astrid_emde|Astrid Emde]] || astrid_emde at osgeo dot org || OSGeoLive, Mapbender, OSGeo || x<br />
|+<br />
|4 || [[User:Veroandreo|Vero Andreo]] || veroandreo at gmail dot com || GRASS GIS || x<br />
|+<br />
|5 || [[User:Tomkralidis|Tom Kralidis]] || tomkralidis at gmail dot com || Geopython, MapServer, QGIS, go-spatial || x<br />
|+<br />
|6 || Shubham|Shubham Kumar || 2020kucp1062@iiitkota.ac.in || Project ||<br />
|+<br />
|7 || [[User:kalxas|Angelos Tzotsos]] || tzotsos at osgeo dot org || pycsw, OSGeoLive, Geopython || x<br />
|+<br />
|8 || Carmen Tawalika || carmen.tawalika at gmail dot com || actinia || x<br />
|+<br />
|9 || [[User:Neteler|Markus Neteler]] || neteler at osgeo dot org || GRASS GIS, actinia || x<br />
|+<br />
|10 || Anika Weinmann || weinmann at mundialis dot de || GRASS GIS, actinia || x<br />
|+<br />
|11 || Guido Riembauer || riembauer at mundialis dot de || GRASS GIS, actinia || x<br />
|+<br />
|12 || [[User:mmetz|Markus Metz]] || metz at mundialis dot de || GRASS GIS, actinia ||<br />
|+<br />
|13 || [[User:Robe|Regina Obe]] || lr at pcorp dot us || PostGIS, pgRouting || x<br />
|+<br />
|14 || [[User:Bakaniko|Nicolas Roelandt]] || roelandtn.pro at gmail dot com || OSGeoLive || pending (waiting free ticket)<br />
|}<br />
<br />
== Workgroups ==<br />
<br />
=== Project-name ===<br />
To participate, copy this project skeleton and start a section below for your project.<br />
<br />
'''Attending:''' <br />
*user <br />
*user<br />
<br />
'''Goals:''' <br />
*your goals<br />
<br />
<br />
=== GRASS GIS ===<br />
''' Attending:'''<br />
* [[User:Lucadelu|Luca Delucchi]]<br />
* [[User:Veroandreo|Vero Andreo]]<br />
* [[User:Neteler|Markus Neteler]]<br />
* Anika Weinmann<br />
* Guido Riembauer<br />
* [[User:mmetz|Markus Metz]]<br />
* ...<br />
<br />
'''Goals:''' <br />
* TBD<br />
<br />
=== Contributions with translations ===<br />
Translations on transifex<br />
Please register to any of your favorite projects:<br />
* OsgeoLive: https://www.transifex.com/osgeo/osgeolive<br />
* pgRouting: https://www.transifex.com/pgrouting/pgrouting<br />
<br />
''' Attending:'''<br />
* [[User:Cvvergara|Vicky Vergara]]<br />
<br />
'''Goals:''' <br />
* Translations<br />
<br />
=== actinia ===<br />
''' Attending:'''<br />
* Carmen Tawalika<br />
* [[User:Neteler|Markus Neteler]]<br />
* Anika Weinmann<br />
* Guido Riembauer<br />
* ...<br />
<br />
'''Goals:''' <br />
* see https://github.com/mundialis/actinia_core/projects/2<br />
<br />
=== OSGeoLive ===<br />
<br />
'''Attending:''' <br />
* [[User:Bakaniko|Nicolas Roelandt]]<br />
<br />
<br />
'''Goals:''' <br />
* Update translations<br />
* Work on translations<br />
<br />
<br />
[[Category:FOSS4G2021]] [[Category:FOSS4G]] [[Category:Code_Sprints]]</div>Bakanikohttps://wiki.osgeo.org/w/index.php?title=User:Bakaniko&diff=127224User:Bakaniko2021-08-24T17:48:45Z<p>Bakaniko: </p>
<hr />
<div>{{OSGeo Member<br />
|Name=Nicolas Roelandt<br />
|JobTitle=GIS Engineer<br />
|Company=Univ. Gustave Eiffel<br />
|Country=France<br />
|City=Bron<br />
|Coordinate=45.736, 4.926<br />
|LocalChapter=Francophone OSGeo Chapter<br />
|SocialMedia=Roelandtn42 (twitter);<br />
|Photo=nicolas_roelandt.jpg<br />
|Languages=French; English;<br />
|languages=French, English<br />
\<br />
}}<br />
{{OSGeo Experience<br />
|User=Yes<br />
|Committee=No<br />
|Board=No<br />
|Coder=No<br />
|Translate=Yes<br />
|PSC=Yes<br />
|ExBoard=No<br />
|Charter=Yes<br />
|Chair=No<br />
|SolKatz=No<br />
|Committer=Yes<br />
}}<br />
GIS user and FOSS hactivist, I combined both by joining the French chapter of OSGeo.<br />
<br />
I participate to the OSGeoLive documentation and translation on [Transifex https://www.transifex.com/osgeo/osgeolive/dashboard/]<br />
<br />
<br />
<br />
<br />
2016: FOSS4G-fr, Paris, France: organization, program committee<br />
<br />
2017: FOSS4G-EU, Paris France: organization, workshop committee<br />
<br />
2017: OSGEO charter member<br />
<br />
2017: OSGeoLive PSC<br />
<br />
2018: FOSS4G-fr, Paris, France: organization, program committee<br />
<br />
2019: FOSS4G Bucarest, Romania: [https://bakaniko.github.io/FOSS4G2019_Geoprocessing_with_R_workshop/ R spatial workshop], OSGeoLive workshop, [https://roelandtn.frama.io/slides/20190830_FOSS4G_Command_line_GIS.html Are we going back to command line ?], gFlowiz project presentation<br />
<br />
2021: FOSS4G-fr chapter president<br />
<br />
[[Category:OSGeo_Advocate]]</div>Bakanikohttps://wiki.osgeo.org/w/index.php?title=User:Bakaniko&diff=127223User:Bakaniko2021-08-24T17:48:04Z<p>Bakaniko: </p>
<hr />
<div>{{OSGeo Member<br />
|Name=Nicolas Roelandt<br />
|JobTitle=GIS Engineer<br />
|Company=Univ. Gustave Eiffel<br />
|Country=France<br />
|City=Bron<br />
|Coordinate=45.736, 4.926<br />
|LocalChapter=Francophone OSGeo Chapter<br />
|SocialMedia=Roelandtn42 (twitter);<br />
|Photo=nicolas_roelandt.jpg<br />
|Languages=French; English;<br />
|languages=French, English<br />
\<br />
}}<br />
{{OSGeo Experience<br />
|User=Yes<br />
|Committee=No<br />
|Board=No<br />
|Coder=No<br />
|Translate=Yes<br />
|PSC=Yes<br />
|ExBoard=No<br />
|Charter=Yes<br />
|Chair=No<br />
|SolKatz=No<br />
|Committer=Yes<br />
}}<br />
GIS user and FOSS hactivist, I combined both by joining the French chapter of OSGeo.<br />
<br />
I participate to the OSGeoLive documentation and translation on [Transifex https://www.transifex.com/osgeo/osgeolive/dashboard/]<br />
<br />
<br />
<br />
<br />
2016: FOSS4G-fr, Paris, France: organization, program committee<br />
<br />
2017: FOSS4G-EU, Paris France: organization, workshop committee<br />
<br />
2017: OSGEO charter member<br />
<br />
2017: OSGeoLive PSC<br />
<br />
2018: FOSS4G-fr, Paris, France: organization, program committee<br />
<br />
2019: FOSS4G Bucarest, Romania: [https://bakaniko.github.io/FOSS4G2019_Geoprocessing_with_R_workshop/ R spatial workshop], OSGeoLive workshop, [https://roelandtn.frama.io/slides/20190830_FOSS4G_Command_line_GIS.html Are we going back to command line ?], gFlowiz project presentation<br />
<br />
<br />
[[Category:OSGeo_Advocate]]</div>Bakanikohttps://wiki.osgeo.org/w/index.php?title=FOSS4G_2021/Community_sprint&diff=127221FOSS4G 2021/Community sprint2021-08-24T17:46:23Z<p>Bakaniko: /* Registered Attendees */</p>
<hr />
<div>== Code Sprint ==<br />
<br />
Also this year, after the online conference, there will be the '''OSGeo community sprint'''.<br />
<br />
Participation is free of charge and anyone involved or interested in getting involved in OSGeo community projects is welcome.<br />
<br />
You can choose to contribute to one or more projects. The sky is the limit. There’s always plenty to do – and it’s not all about programming. Translation, documentation, feedback, discussions, and testing are very important for projects! Conference registration is not a prerequisite for participation in the code sprint.<br />
<br />
<!-- shouldn't we say something about the planned activities - or WIP plans?? Also, the room will be open the whole week, AFAIU, shouldn't we say so?? --><br />
=== When ===<br />
The code sprint will be held on Saturday October 2nd, 2021.<br />
<br />
=== Where ===<br />
Online, we will use [https://workadventu.re/ WorkAdventu.re] plus a bounce of Jitsi channels for each project.<br />
<br />
== Registered Attendees ==<br />
The code sprint is free of charge but we kindly ask you to write down your name for better planning.<br />
<br />
{| border="1" cellpadding="2" class="wikitable sortable"<br />
!width="30"|No<br />
!width="250"|Name<br />
!width="250"|Email<br />
!width="250"|Projects<br />
!width="250"|Registered to FOSS4G conference<br />
|-<br />
|1 || [[User:Lucadelu|Luca Delucchi]] || lucadeluge gmail com || GRASS GIS, pyModis, OSGeoLive (code sprint organizer) || x<br />
|+<br />
|2 || [[User:Cvvergara|Vicky Vergara]] || vicky at georepublic de || Contributions with Translations|| x<br />
|+<br />
|3 || [[User:Astrid_emde|Astrid Emde]] || astrid_emde at osgeo dot org || OSGeoLive, Mapbender, OSGeo || x<br />
|+<br />
|4 || [[User:Veroandreo|Vero Andreo]] || veroandreo at gmail dot com || GRASS GIS || x<br />
|+<br />
|5 || [[User:Tomkralidis|Tom Kralidis]] || tomkralidis at gmail dot com || Geopython, MapServer, QGIS, go-spatial || x<br />
|+<br />
|6 || Shubham|Shubham Kumar || 2020kucp1062@iiitkota.ac.in || Project ||<br />
|+<br />
|7 || [[User:kalxas|Angelos Tzotsos]] || tzotsos at osgeo dot org || pycsw, OSGeoLive, Geopython || x<br />
|+<br />
|8 || Carmen Tawalika || carmen.tawalika at gmail dot com || actinia || x<br />
|+<br />
|9 || [[User:Neteler|Markus Neteler]] || neteler at osgeo dot org || GRASS GIS, actinia || x<br />
|+<br />
|10 || Anika Weinmann || weinmann at mundialis dot de || GRASS GIS, actinia || x<br />
|+<br />
|11 || Guido Riembauer || riembauer at mundialis dot de || GRASS GIS, actinia || x<br />
|+<br />
|12 || [[User:mmetz|Markus Metz]] || metz at mundialis dot de || GRASS GIS, actinia ||<br />
|+<br />
|13 || [[User:Robe|Regina Obe]] || lr at pcorp dot us || PostGIS, pgRouting || x<br />
|+<br />
|14 || [[User:Bakaniko|Nicolas Roelandt]] || roelandtn.pro at gmail dot com || OSGeoLive || pending (waiting free ticket)<br />
|}<br />
<br />
== Workgroups ==<br />
<br />
=== Project-name ===<br />
To participate, copy this project skeleton and start a section below for your project.<br />
<br />
'''Attending:''' <br />
*user <br />
*user<br />
<br />
'''Goals:''' <br />
*your goals<br />
<br />
<br />
=== GRASS GIS ===<br />
''' Attending:'''<br />
* [[User:Lucadelu|Luca Delucchi]]<br />
* [[User:Veroandreo|Vero Andreo]]<br />
* [[User:Neteler|Markus Neteler]]<br />
* Anika Weinmann<br />
* Guido Riembauer<br />
* [[User:mmetz|Markus Metz]]<br />
* ...<br />
<br />
'''Goals:''' <br />
* TBD<br />
<br />
=== pgRouting ===<br />
''' Attending:'''<br />
* [[User:Cvvergara|Vicky Vergara]]<br />
<br />
'''Goals:''' <br />
* Translations<br />
<br />
=== actinia ===<br />
''' Attending:'''<br />
* Carmen Tawalika<br />
* [[User:Neteler|Markus Neteler]]<br />
* Anika Weinmann<br />
* Guido Riembauer<br />
* ...<br />
<br />
'''Goals:''' <br />
* see https://github.com/mundialis/actinia_core/projects/2<br />
<br />
[[Category:FOSS4G2021]] [[Category:FOSS4G]] [[Category:Code_Sprints]]</div>Bakanikohttps://wiki.osgeo.org/w/index.php?title=User_talk:Roelandtn&diff=127008User talk:Roelandtn2021-07-29T19:36:11Z<p>Bakaniko: Bakaniko moved page User talk:Roelandtn to User talk:Bakaniko: Automatically moved page while renaming the user "Roelandtn" to "Bakaniko"</p>
<hr />
<div>#REDIRECT [[User talk:Bakaniko]]</div>Bakanikohttps://wiki.osgeo.org/w/index.php?title=User_talk:Bakaniko&diff=127007User talk:Bakaniko2021-07-29T19:36:11Z<p>Bakaniko: Bakaniko moved page User talk:Roelandtn to User talk:Bakaniko: Automatically moved page while renaming the user "Roelandtn" to "Bakaniko"</p>
<hr />
<div>'''Welcome to ''OSGeo Wiki''!'''<br />
We hope you will contribute much and well.<br />
You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages].<br />
Again, welcome and have fun! [[User:Neteler|Neteler]] ([[User talk:Neteler|talk]]) 14:48, 27 January 2016 (PST)</div>Bakanikohttps://wiki.osgeo.org/w/index.php?title=User:Roelandtn&diff=127006User:Roelandtn2021-07-29T19:36:11Z<p>Bakaniko: Bakaniko moved page User:Roelandtn to User:Bakaniko: Automatically moved page while renaming the user "Roelandtn" to "Bakaniko"</p>
<hr />
<div>#REDIRECT [[User:Bakaniko]]</div>Bakanikohttps://wiki.osgeo.org/w/index.php?title=User:Bakaniko&diff=127005User:Bakaniko2021-07-29T19:36:10Z<p>Bakaniko: Bakaniko moved page User:Roelandtn to User:Bakaniko: Automatically moved page while renaming the user "Roelandtn" to "Bakaniko"</p>
<hr />
<div>{{OSGeo Member<br />
|Name=Nicolas Roelandt<br />
|JobTitle=GIS Engineer<br />
|Company=IFSTTAR<br />
|Country=France<br />
|City=Marne-la-Vallée<br />
|Coordinate=48.842298, 2.587371<br />
|LocalChapter=Francophone OSGeo Chapter<br />
|SocialMedia=Roelandtn42 (twitter);<br />
|Photo=nicolas_roelandt.jpg<br />
|Languages=French; English;<br />
|languages=French, English<br />
\<br />
}}<br />
{{OSGeo Experience<br />
|User=Yes<br />
|Committee=No<br />
|Board=No<br />
|Coder=No<br />
|Translate=Yes<br />
|PSC=Yes<br />
|ExBoard=No<br />
|Charter=Yes<br />
|Chair=No<br />
|SolKatz=No<br />
|Committer=Yes<br />
}}<br />
GIS user and FOSS hactivist, I combined both by joining the French chapter of OSGeo.<br />
<br />
I participate to the OSGeoLive documentation and translation on [Transifex https://www.transifex.com/osgeo/osgeolive/dashboard/]<br />
<br />
<br />
<br />
<br />
2016: FOSS4G-fr, Paris, France: organization, program committee<br />
<br />
2017: FOSS4G-EU, Paris France: organization, workshop committee<br />
<br />
2017: OSGEO charter member<br />
<br />
2017: OSGeoLive PSC<br />
<br />
2018: FOSS4G-fr, Paris, France: organization, program committee<br />
<br />
2019: FOSS4G Bucarest, Romania: [https://bakaniko.github.io/FOSS4G2019_Geoprocessing_with_R_workshop/ R spatial workshop], OSGeoLive workshop, [https://roelandtn.frama.io/slides/20190830_FOSS4G_Command_line_GIS.html Are we going back to command line ?], gFlowiz project presentation<br />
<br />
<br />
[[Category:OSGeo_Advocate]]</div>Bakanikohttps://wiki.osgeo.org/w/index.php?title=OSGeo_Virtual_Community_Sprint_2020&diff=125730OSGeo Virtual Community Sprint 20202020-11-19T20:44:10Z<p>Bakaniko: /* Participants */</p>
<hr />
<div>Due to COVID-19 the Annual OSGeo Code Sprint will take place online in 2020 - November 17-18-19<br />
<br />
Powered by [[Image:Osgeo-logo.png|250px|link=https://www.osgeo.org]]<br />
<br />
<br />
== Purpose ==<br />
<br />
Bring together project members to make decisions and tackle larger geospatial <br />
problems as in previous years: <br />
* [[OSGeo_Community_Sprint_2019|Minnesota]] (2019)<br />
* [[OSGeo Code Sprint 2018|Bonn]] (2018)<br />
* [[Daytona Beach Code Sprint 2017|Daytona_Beach]] (2017)<br />
* [[Paris Code Sprint 2016|Paris]] (2016)<br />
* [[Philadelphia Code Sprint 2015|Philadelphia]] (2015)<br />
* [[Vienna Code Sprint 2014|Vienna]] (2014)<br />
* [[Boston Code Sprint 2013|Boston]] (2013)<br />
* [[IslandWood Code Sprint 2012|Island Wood (Seattle)]] (2012)<br />
* [[Montreal Code Sprint 2011|Montreal]] (2011)<br />
* [[New York Code Sprint 2010|New York City]] (2010)<br />
* [[Toronto Code Sprint 2009|Toronto]] (2009)<br />
<br />
== Sponsors == <br />
<br />
'''Sponsoring ''' Find out about [[OSGeo_Virtual_Community_Sprint_2020#Sponsoring |Sponsoring the Event]].<br />
<br />
; <big>Gold Sponsors</big> <br />
{| border=0 cellspacing=15 cellpadding=10<br />
||<br />
[[File:GC-Group logo.png|220px|GeoCue|link=http://www.geocue.com/]]<br />
<br><br />
http://www.geocue.com/<br />
||<br />
[[File:safe-software-logo.png|220px|Safe Software|link=https://www.safe.com/]]<br />
<br><br><br />
https://www.safe.com/<br />
||<br />
[[File:RIEGL.png|310px|RIEGL|link=http://www.riegl.com/]]<br />
<br><br />
http://www.riegl.com/<br />
|}<br />
<br />
; <big>Silver Sponsors</big> <br />
{| border=0 cellspacing=15 cellpadding=10<br />
||<br />
[[File:Hobulogo.png|160px|Hobu|link=https://hobu.co/]]<br />
<br><br />
https://hobu.co/<br />
||<br />
[[File:Bh-logo.jpg|300px|link=https://www.bhinc.com/]]<br />
<br><br />
[https://www.bhinc.com/ https://www.bhinc.com/]<br />
||<br />
[[File:Crunchydata.png|160px|CrunchyData||link=http://www.crunchydata.com/]]<br />
<br><br />
[http://www.crunchydata.com/ http://www.crunchydata.com/]<br />
|}<br />
{| border=0 cellspacing=15 cellpadding=10<br />
||<br />
[[File:Gaia3D.png|240px|Gaia3D||link=https://gaia3d.com/en/]]<br />
<br><br />
[https://gaia3d.com/en/ https://gaia3d.com/en/]<br />
|}<br />
<br />
; <big>Bronze Sponsors</big><br />
{| border=0 cellspacing=15 cellpadding=10<br />
||<br />
[[File:CoordinateSolutions_TRANS.png|210px|link=http://www.coordinatesolutions.com/]]<br />
<br><br />
[http://www.coordinatesolutions.com/ http://www.coordinatesolutions.com/]<br />
||<br />
[[File:Logo-EOX.png|140px|EOX IT Services GmbH|link=http://eox.at]]<br />
<br><br />
[http://eox.at http://eox.at]<br />
||<br />
[[File:Pixel8_logo_full.png|140px|link=https://www.pixel8.earth/]]<br />
<br><br />
[https://www.pixel8.earth/ https://www.pixel8.earth/]<br />
|}<br />
{| border=0 cellspacing=15 cellpadding=10<br />
||<br />
[[File:Azavea-logo.png|160px|link=https://www.azavea.com/]]<br />
<br><br />
[https://www.azavea.com/ https://www.azavea.com/]<br />
||<br />
[[File:Greenwood_logo.png|210px|link=https://greenwoodmap.com/]]<br />
<br><br />
[https://greenwoodmap.com/ https://greenwoodmap.com/]<br />
|}<br />
<br />
== Dates and Times ==<br />
<br />
* Date: Nov 17-19<br />
* Time: 08:00 UTC to 24:00 UTC (projects can choose their own plan all 24h, if that fits their schedule/time zone).<br />
<br />
== Schedule ==<br />
* Kick off meeting each day around 08:00 UTC<br />
* Welcome session Tue Nov 17 13:00 UTC (will be recorded on YouTube)<br />
* Daily report every day around 22:00 UTC<br />
* Closing event Thu 19 Nov 22:00 UTC<br />
<br />
== Presentation Slots ==<br />
* Welcome presentation, Tue 17 Nov 13:00 UTC (30 min)<br />
* OGC Introduction, Tue 17 Nov 22:00 UTC (10 mins)<br />
* ESA EOEPCA Exploitation Platform, Wed 18 Nov 08:00 UTC (20 mins)<br />
* ''Please add your presentation slot here''<br />
<br />
== Other Events in November 2020 ==<br />
<br />
* ''please add your event''<br />
<br />
== Location ==<br />
<br />
* Main zoom channel for kick off, presentations, free discussion and daily reports [https://zoom.us/j/95817956179?pwd=VGROK0NVK2lTaDg4eHJkdW1IdWNlUT09 https://zoom.us/j/95817956179?pwd=VGROK0NVK2lTaDg4eHJkdW1IdWNlUT09]<br />
* Jitsi channels will be listed here by projects<br />
** https://meet.jit.si/tosprint (Lobby channel for free discussion)<br />
** https://meet.jit.si/OSGeo (generic OSGeo channel)<br />
** https://meet.jit.si/OSGeoBoard (Board sprint room)<br />
** https://meet.jit.si/OGC-API (generic OGC APIs channel, SWGs can spin their own channel e.g. https://meet.jit.si/OGC-API-Features)<br />
** https://meet.jit.si/GDAL<br />
** https://meet.jit.si/QGIS<br />
** https://meet.jit.si/PostGIS<br />
** https://meet.jit.si/GEOS<br />
** https://meet.jit.si/GeoServer<br />
** https://meet.jit.si/MapServer<br />
** https://meet.jit.si/GRASS<br />
** https://meet.jit.si/OSGeoLive<br />
** https://meet.jit.si/geopython (channel for pycsw, pygeoapi, pygeometa, GeoNode, OWSLib, GeoHealthCheck, MapProxy development, other geopython projects are welcome)<br />
** TEAM Engine (scheduled [https://github.com/opengeospatial/cite/wiki/TEAM-Engine-at-the-OSGeo-Virtual-Community-Sprint-2020#teleconference-schedule Gotomeeting] sessions)<br />
** https://open.meet.garr.it/OSGeo_Virtual_Community_Sprint_Italian_Translation (Italian community for translation)<br />
** https://meet.jit.si/EOEPCA (meeting room for ESA EOEPCA project participating in the code sprint)<br />
** https://meet.jit.si/pgrouting and https://gitter.im/pgRouting/pgrouting will be used for written communication.<br />
** https://meet.jit.si/GeoNode<br />
<br />
== Project Plans ==<br />
(i.e what do you wish/want/plan to work on during the sprint ?)<br />
<br />
* '''OSGeoLive''':<br />
** Work towards 14.0 release<br />
<br />
* '''PostGIS''':<br />
** Work towards PostGIS 3.1.0 in Sept/Oct<br />
<br />
* '''GEOS''':<br />
** Work towards 3.9.0 release<br />
<br />
* '''GeoServer MapML Community Module''':<br />
** Validate / socialize concepts, work toward extension module status<br />
<br />
* '''GRASS GIS''':<br />
** Addons improvements<br />
** Translation<br />
** Work towards 8.0.0 release<br />
** see https://github.com/OSGeo/grass/projects/4<br />
<br />
* '''TEAM Engine''':<br />
** Progress towards OSGeo graduation (details [https://github.com/opengeospatial/cite/wiki/TEAM-Engine-at-the-OSGeo-Virtual-Community-Sprint-2020 here])<br />
** Executable Test Suites for OGC APIs<br />
<br />
* '''ESA EOEPCA''':<br />
** Integration of Resource Catalogue with Data Access Service<br />
** Contributions to Resource Catalogue and View Service modules.<br />
<br />
* '''pgRouting''':<br />
** Work towards release 3.0.3 & 3.1.1<br />
** Work on workshop details for OSGeoLive 14<br />
<br />
* '''MobilityDB''':<br />
** Works towards the application to become an OSGeo Community Project<br />
<br />
== Participants ==<br />
<br />
Please add your name and the projects you are planning to sprint and note the likeliness of your attendance.<br />
<br />
{| border="1" cellpadding="2" class="wikitable sortable"<br />
!width="25"|No<br />
!width="250"|Name<br />
!width="100"|Country<br />
!width="250"|Email<br />
!width="250"|Organisation<br />
!width="250"|Projects<br />
!width="25"|Tue<br />
!width="25"|Wed<br />
!width="25"|Thu<br />
|-<br />
| 1 || [[User:kalxas|Angelos Tzotsos]] || GR || tzotsos(at)osgeo.org || OSGeo || pycsw, OSGeoLive, GeoNode, UbuntuGIS, pygeoapi, OTB || x || x || x<br />
|-<br />
| 2 || [[User:msmitherdc|Michael Smith]] || US || Michael.smith.erdc(at)gmail.com || USACE || pdal, gdal, mapserver || x || x || x<br />
|-<br />
| 3 || [[User:prushforth|Peter Rushforth]] || CA || peter.rushforth(at)gmail.com || W3C Maps for HTML Community Group|| GeoServer MapML Community Module || x starting at 14 UTC each day || x || x<br />
|-<br />
| 4 || [[User:Lucadelu|Luca Delucchi]] || IT || lucadeluge@gmail.com || Fondazione Edmund Mach || GRASS GIS, pyModis, OSGeoLive || x || x || x<br />
|-<br />
| 5 || [[User:Wenzeslaus|Vaclav Petras]] || US || wenzeslaus(at)gmail.com || North Carolina State University || GRASS GIS || x || x || x<br />
|-<br />
| 6 || [[User:Sethg|Seth Girvin]] || FR/IE || sethg(at)geographika.co.uk || OSGeo || MapServer, OSGeoLive, GeoExt || x || x || x<br />
|-<br />
| 7 || [[User:Astrid_Emde|Astrid Emde]] || DE || astrid_emde (at) osgeo.org || OSGeo || OSGeoLive || x starting at 14 UTC each day || x || x<br />
|-<br />
| 8 || [[User:Veroandreo|Veronica Andreo]] || AR || veroandreo@gmail.com || Conicet || GRASS GIS || x || x || x<br />
|-<br />
| 9 || [[User:Cvvergara|Vicky Vergara]] || MX || vicky@georepublic.de || OSGeo || OSGeoLive pgRouting MobilityDB || x || x || x<br />
|-<br />
| 10 || [[User:Ghobona-ogc|Gobe Hobona]] || GB || ghobona (at) ogc.org || OGC || Team Engine and test suites of OGC APIs || x || x || x<br />
|-<br />
| 11 || [[User:Schpidi|Stephan Meißl]] || AT || stephan.meissl (at) eox.at || EOX || Various as time permits || (x) || (x) || (x)<br />
|-<br />
| 12 || [[Markus_Neteler|Markus Neteler]] || AT || neteler (at) mundialis.de || mundialis || Various as time permits || (x) || (x) || (x)<br />
|-<br />
| 13 || [[User:Tomkralidis|Tom Kralidis]] || CA || tomkralidis (at) gmail.com || OSGeo || pycsw, OWSLib, pygeoapi, GeoHealthCheck, MapServer, other geopython projects || (x) || (x) || (x)<br />
|-<br />
| 14 || [[User:jerstlouis|Jerome St-Louis]] || CA || jerome (at) ecere.com || Ecere || Ecere SDK, GNOSIS SDK || (x) || (x) || (x)<br />
|-<br />
| 15 || [[User:darkblue_b|Brian M Hamlin]] || US || maplabs -at- light42 -dot- com || OSGeo || OSGeoLive, GEOS || (x) || (x) || (x)<br />
|-<br />
| 16 || [[User:T-book|Toni Schönbuchner]] || DE || toni.schoenbuchner -at- csgis -dot- de || csgis || GeoNode|| - || - || x<br />
|-<br />
| 17 || [[User:PierreAbbat|Pierre Abbat]] || US || phma@bezitopo.org || OSGeo || OSGeoLive, PDAL || x || x || x<br />
|-<br />
| 18 || [[User:dovsienko|Denis Ovsienko]] || UK || denis@ovsienko.info || || GRASS GIS || x || x || x<br />
|-<br />
| 19 || [[Florian Hoedt]] || DE || florian.hoedt -at- thuenen.de || Thünen Institut || GeoNode || - || - || x<br />
|-<br />
| 20 ||[[User:alexgleith|Alex Leith]] || AU || alexgleith@gmail.com || Geoscience Australia || The Open Data Cube || (x) || (x) || (x)<br />
|-<br />
| 21 ||[[User:Jgrocha|Jorge Gustavo Rocha]] || PT || jgr@geomaster.pt || Geomaster || QGIS Bug fixing || x || x || x<br />
|-<br />
| 22 || [[User:chiossif|Christos Iosifidis]] || GR || chiossif(at)yahoo.com || NTUA, GRNET || OSGeoLive, GRASS GIS, SAGA GIS || x || x || x<br />
|-<br />
| 23 || Ricardo Garcia Silva || PT || ricardo.garcia.silva(at)gmail.com || Kartoza || GeoNode, pycsw || x || || <br />
|-<br />
| 24 || [[User:sdlime|Steve Lime]] || US || sdlime(at)gmail.com || MNIT || MapServer (as time permits) || (x) || (x) || (x)<br />
|-<br />
| 25 || [[User:Stenger|Dirk Stenger]] || DE || stenger at lat-lon dot de || lat/lon || TEAM Engine || (x) || ||<br />
|-<br />
| 26 || [[User:jboue|Jérome Boué]] || FR || jbo-ads (at) mailo.com || || MapCache, MapServer (as time permits, mainly on #mapserver and #tosprint IRC channels) || (x) || (x) || (x)<br />
|-<br />
| 27 || [[User:Rajatshinde|Rajat Shinde]] || IN || rajatshinde2303 (at) gmail.com || || pgRouting Workshop || x || || <br />
|-<br />
| 28 || [[User:Mahmsakr|Mahmoud SAKR]] || BE || mahmoud.sakr@ulb.ac.be || Université Libre de Bruxelles || MobilityDB, and will be visiting OSGeoLive, OGC, and pgRouting || (x) || || (x)<br />
|-<br />
| 29 || [[User:Krashish8|Ashish Kumar]] || IN || ashishkr23438 (at) gmail.com || || pgRouting || x || || <br />
|-<br />
| 30 || [[User:djay|Gérald Fenoy]] || FR || gerald.fenoy (at) geolabs.fr || GeoLabs || ZOO-Project, OGC API - Processes || || x || x<br />
|-<br />
| 31 ||[[User:rouault|Even Rouault]] || FR || even.rouault at spatialys.com || Spatialys || GDAL, PROJ, Mapserver || x || x || x<br />
|-<br />
| 32 || [[User:Enock4seth|Enock Seth Nyamador]] || DE/GH || enockseth (at) gmail.com || || OSGeoLive || || x || x<br />
|-<br />
| 33 || [[User:Roelandtn|Nicolas Roelandt]] || FR || roelandtn.pro (at) gmail.com || || OSGeoLive || x || x || x<br />
|-<br />
| 34 || Add your info here || || || || || || ||<br />
|-<br />
|}<br />
<br />
== Communication ==<br />
<br />
* Please join the mailing list: https://lists.osgeo.org/mailman/listinfo/tosprint<br />
* IRC chat during the event: #tosprint Server: irc.freenode.net<br />
* Gitter channel: https://gitter.im/OSGeo/Sprint<br />
* Projects can report their progress by adding slides to the event presentation https://docs.google.com/presentation/d/1jKInzGnY_9ad4srD4TtfD7jKBjMrcyL51QIR3z13Ov8/edit?usp=sharing<br />
<br />
== Sponsoring ==<br />
<br />
The Open Source Geospatial Foundation (OSGeo) has a long tradition of organizing code sprints for developers of Open Source GIS software.<br />
(https://wiki.osgeo.org/wiki/Category:Code_Sprints).<br />
<br />
An international community/code sprint for OSGeo will take place Nov 17-19, 2020.<br />
<br />
We expect about 80 developers from all over the world to come from various [https://www.osgeo.org/, OSGeo] projects. Whether desktop application, geospatial library, metadata catalog or web mapping: be sure to find products in the list that you use. The sprint is also an opportunity for your developers to meet with the core developers of the projects, get a deeper insight into the software and participate in the development.<br />
<br />
This years' sprint will take place online.<br />
<br />
Usually the code sprint costs involve providing the technical infrastructure and space, food and drink for the developers as well as social events. This year only the technical infrastructure costs will be covered since we will be online. <br />
<br />
In order to cover these costs we would be overjoyed to accept offers of sponsorship!<br />
<br />
What we can offer:<br />
* Your logo on top of the [https://www.osgeo.org/events/OSGeo_Community_Sprint_2020/ community sprint website] as well as on all official documents used during the sprint<br />
* Acknowledgement in all sprint related emails<br />
* Our undying gratitude, which comes in handy when you least expect it (remember that feature you wanted?)<br />
<br />
Our sponsorship levels:<br />
* Gold: >= 2500 USD<br />
* Silver: 1500 USD<br />
* Bronze: 750 USD<br />
<br />
So...<br />
* get your company talking to the top project developers.<br />
* encourage your GIS developers to take advantage of this opportunity, there is no better opportunity to learn!<br />
* support the software you use - you benefit immediately.<br />
<br />
Thank you very much!<br />
<br />
Contact: To sponsor, please contact tzotsos@osgeo.org directly.<br />
<br />
== Event Owner ==<br />
* OSGeo Board<br />
<br />
<br />
== Press Release ==<br />
<br />
We are looking forward to the next OSGeo Code Sprint!<br />
<br />
[[Category:Code_Sprints]]<br />
[[Category:C Tribe Code Sprint]]</div>Bakanikohttps://wiki.osgeo.org/w/index.php?title=OSGeo_Virtual_Community_Sprint_2020&diff=125729OSGeo Virtual Community Sprint 20202020-11-19T20:43:20Z<p>Bakaniko: /* Participants */</p>
<hr />
<div>Due to COVID-19 the Annual OSGeo Code Sprint will take place online in 2020 - November 17-18-19<br />
<br />
Powered by [[Image:Osgeo-logo.png|250px|link=https://www.osgeo.org]]<br />
<br />
<br />
== Purpose ==<br />
<br />
Bring together project members to make decisions and tackle larger geospatial <br />
problems as in previous years: <br />
* [[OSGeo_Community_Sprint_2019|Minnesota]] (2019)<br />
* [[OSGeo Code Sprint 2018|Bonn]] (2018)<br />
* [[Daytona Beach Code Sprint 2017|Daytona_Beach]] (2017)<br />
* [[Paris Code Sprint 2016|Paris]] (2016)<br />
* [[Philadelphia Code Sprint 2015|Philadelphia]] (2015)<br />
* [[Vienna Code Sprint 2014|Vienna]] (2014)<br />
* [[Boston Code Sprint 2013|Boston]] (2013)<br />
* [[IslandWood Code Sprint 2012|Island Wood (Seattle)]] (2012)<br />
* [[Montreal Code Sprint 2011|Montreal]] (2011)<br />
* [[New York Code Sprint 2010|New York City]] (2010)<br />
* [[Toronto Code Sprint 2009|Toronto]] (2009)<br />
<br />
== Sponsors == <br />
<br />
'''Sponsoring ''' Find out about [[OSGeo_Virtual_Community_Sprint_2020#Sponsoring |Sponsoring the Event]].<br />
<br />
; <big>Gold Sponsors</big> <br />
{| border=0 cellspacing=15 cellpadding=10<br />
||<br />
[[File:GC-Group logo.png|220px|GeoCue|link=http://www.geocue.com/]]<br />
<br><br />
http://www.geocue.com/<br />
||<br />
[[File:safe-software-logo.png|220px|Safe Software|link=https://www.safe.com/]]<br />
<br><br><br />
https://www.safe.com/<br />
||<br />
[[File:RIEGL.png|310px|RIEGL|link=http://www.riegl.com/]]<br />
<br><br />
http://www.riegl.com/<br />
|}<br />
<br />
; <big>Silver Sponsors</big> <br />
{| border=0 cellspacing=15 cellpadding=10<br />
||<br />
[[File:Hobulogo.png|160px|Hobu|link=https://hobu.co/]]<br />
<br><br />
https://hobu.co/<br />
||<br />
[[File:Bh-logo.jpg|300px|link=https://www.bhinc.com/]]<br />
<br><br />
[https://www.bhinc.com/ https://www.bhinc.com/]<br />
||<br />
[[File:Crunchydata.png|160px|CrunchyData||link=http://www.crunchydata.com/]]<br />
<br><br />
[http://www.crunchydata.com/ http://www.crunchydata.com/]<br />
|}<br />
{| border=0 cellspacing=15 cellpadding=10<br />
||<br />
[[File:Gaia3D.png|240px|Gaia3D||link=https://gaia3d.com/en/]]<br />
<br><br />
[https://gaia3d.com/en/ https://gaia3d.com/en/]<br />
|}<br />
<br />
; <big>Bronze Sponsors</big><br />
{| border=0 cellspacing=15 cellpadding=10<br />
||<br />
[[File:CoordinateSolutions_TRANS.png|210px|link=http://www.coordinatesolutions.com/]]<br />
<br><br />
[http://www.coordinatesolutions.com/ http://www.coordinatesolutions.com/]<br />
||<br />
[[File:Logo-EOX.png|140px|EOX IT Services GmbH|link=http://eox.at]]<br />
<br><br />
[http://eox.at http://eox.at]<br />
||<br />
[[File:Pixel8_logo_full.png|140px|link=https://www.pixel8.earth/]]<br />
<br><br />
[https://www.pixel8.earth/ https://www.pixel8.earth/]<br />
|}<br />
{| border=0 cellspacing=15 cellpadding=10<br />
||<br />
[[File:Azavea-logo.png|160px|link=https://www.azavea.com/]]<br />
<br><br />
[https://www.azavea.com/ https://www.azavea.com/]<br />
||<br />
[[File:Greenwood_logo.png|210px|link=https://greenwoodmap.com/]]<br />
<br><br />
[https://greenwoodmap.com/ https://greenwoodmap.com/]<br />
|}<br />
<br />
== Dates and Times ==<br />
<br />
* Date: Nov 17-19<br />
* Time: 08:00 UTC to 24:00 UTC (projects can choose their own plan all 24h, if that fits their schedule/time zone).<br />
<br />
== Schedule ==<br />
* Kick off meeting each day around 08:00 UTC<br />
* Welcome session Tue Nov 17 13:00 UTC (will be recorded on YouTube)<br />
* Daily report every day around 22:00 UTC<br />
* Closing event Thu 19 Nov 22:00 UTC<br />
<br />
== Presentation Slots ==<br />
* Welcome presentation, Tue 17 Nov 13:00 UTC (30 min)<br />
* OGC Introduction, Tue 17 Nov 22:00 UTC (10 mins)<br />
* ESA EOEPCA Exploitation Platform, Wed 18 Nov 08:00 UTC (20 mins)<br />
* ''Please add your presentation slot here''<br />
<br />
== Other Events in November 2020 ==<br />
<br />
* ''please add your event''<br />
<br />
== Location ==<br />
<br />
* Main zoom channel for kick off, presentations, free discussion and daily reports [https://zoom.us/j/95817956179?pwd=VGROK0NVK2lTaDg4eHJkdW1IdWNlUT09 https://zoom.us/j/95817956179?pwd=VGROK0NVK2lTaDg4eHJkdW1IdWNlUT09]<br />
* Jitsi channels will be listed here by projects<br />
** https://meet.jit.si/tosprint (Lobby channel for free discussion)<br />
** https://meet.jit.si/OSGeo (generic OSGeo channel)<br />
** https://meet.jit.si/OSGeoBoard (Board sprint room)<br />
** https://meet.jit.si/OGC-API (generic OGC APIs channel, SWGs can spin their own channel e.g. https://meet.jit.si/OGC-API-Features)<br />
** https://meet.jit.si/GDAL<br />
** https://meet.jit.si/QGIS<br />
** https://meet.jit.si/PostGIS<br />
** https://meet.jit.si/GEOS<br />
** https://meet.jit.si/GeoServer<br />
** https://meet.jit.si/MapServer<br />
** https://meet.jit.si/GRASS<br />
** https://meet.jit.si/OSGeoLive<br />
** https://meet.jit.si/geopython (channel for pycsw, pygeoapi, pygeometa, GeoNode, OWSLib, GeoHealthCheck, MapProxy development, other geopython projects are welcome)<br />
** TEAM Engine (scheduled [https://github.com/opengeospatial/cite/wiki/TEAM-Engine-at-the-OSGeo-Virtual-Community-Sprint-2020#teleconference-schedule Gotomeeting] sessions)<br />
** https://open.meet.garr.it/OSGeo_Virtual_Community_Sprint_Italian_Translation (Italian community for translation)<br />
** https://meet.jit.si/EOEPCA (meeting room for ESA EOEPCA project participating in the code sprint)<br />
** https://meet.jit.si/pgrouting and https://gitter.im/pgRouting/pgrouting will be used for written communication.<br />
** https://meet.jit.si/GeoNode<br />
<br />
== Project Plans ==<br />
(i.e what do you wish/want/plan to work on during the sprint ?)<br />
<br />
* '''OSGeoLive''':<br />
** Work towards 14.0 release<br />
<br />
* '''PostGIS''':<br />
** Work towards PostGIS 3.1.0 in Sept/Oct<br />
<br />
* '''GEOS''':<br />
** Work towards 3.9.0 release<br />
<br />
* '''GeoServer MapML Community Module''':<br />
** Validate / socialize concepts, work toward extension module status<br />
<br />
* '''GRASS GIS''':<br />
** Addons improvements<br />
** Translation<br />
** Work towards 8.0.0 release<br />
** see https://github.com/OSGeo/grass/projects/4<br />
<br />
* '''TEAM Engine''':<br />
** Progress towards OSGeo graduation (details [https://github.com/opengeospatial/cite/wiki/TEAM-Engine-at-the-OSGeo-Virtual-Community-Sprint-2020 here])<br />
** Executable Test Suites for OGC APIs<br />
<br />
* '''ESA EOEPCA''':<br />
** Integration of Resource Catalogue with Data Access Service<br />
** Contributions to Resource Catalogue and View Service modules.<br />
<br />
* '''pgRouting''':<br />
** Work towards release 3.0.3 & 3.1.1<br />
** Work on workshop details for OSGeoLive 14<br />
<br />
* '''MobilityDB''':<br />
** Works towards the application to become an OSGeo Community Project<br />
<br />
== Participants ==<br />
<br />
Please add your name and the projects you are planning to sprint and note the likeliness of your attendance.<br />
<br />
{| border="1" cellpadding="2" class="wikitable sortable"<br />
!width="25"|No<br />
!width="250"|Name<br />
!width="100"|Country<br />
!width="250"|Email<br />
!width="250"|Organisation<br />
!width="250"|Projects<br />
!width="25"|Tue<br />
!width="25"|Wed<br />
!width="25"|Thu<br />
|-<br />
| 1 || [[User:kalxas|Angelos Tzotsos]] || GR || tzotsos(at)osgeo.org || OSGeo || pycsw, OSGeoLive, GeoNode, UbuntuGIS, pygeoapi, OTB || x || x || x<br />
|-<br />
| 2 || [[User:msmitherdc|Michael Smith]] || US || Michael.smith.erdc(at)gmail.com || USACE || pdal, gdal, mapserver || x || x || x<br />
|-<br />
| 3 || [[User:prushforth|Peter Rushforth]] || CA || peter.rushforth(at)gmail.com || W3C Maps for HTML Community Group|| GeoServer MapML Community Module || x starting at 14 UTC each day || x || x<br />
|-<br />
| 4 || [[User:Lucadelu|Luca Delucchi]] || IT || lucadeluge@gmail.com || Fondazione Edmund Mach || GRASS GIS, pyModis, OSGeoLive || x || x || x<br />
|-<br />
| 5 || [[User:Wenzeslaus|Vaclav Petras]] || US || wenzeslaus(at)gmail.com || North Carolina State University || GRASS GIS || x || x || x<br />
|-<br />
| 6 || [[User:Sethg|Seth Girvin]] || FR/IE || sethg(at)geographika.co.uk || OSGeo || MapServer, OSGeoLive, GeoExt || x || x || x<br />
|-<br />
| 7 || [[User:Astrid_Emde|Astrid Emde]] || DE || astrid_emde (at) osgeo.org || OSGeo || OSGeoLive || x starting at 14 UTC each day || x || x<br />
|-<br />
| 8 || [[User:Veroandreo|Veronica Andreo]] || AR || veroandreo@gmail.com || Conicet || GRASS GIS || x || x || x<br />
|-<br />
| 9 || [[User:Cvvergara|Vicky Vergara]] || MX || vicky@georepublic.de || OSGeo || OSGeoLive pgRouting MobilityDB || x || x || x<br />
|-<br />
| 10 || [[User:Ghobona-ogc|Gobe Hobona]] || GB || ghobona (at) ogc.org || OGC || Team Engine and test suites of OGC APIs || x || x || x<br />
|-<br />
| 11 || [[User:Schpidi|Stephan Meißl]] || AT || stephan.meissl (at) eox.at || EOX || Various as time permits || (x) || (x) || (x)<br />
|-<br />
| 12 || [[Markus_Neteler|Markus Neteler]] || AT || neteler (at) mundialis.de || mundialis || Various as time permits || (x) || (x) || (x)<br />
|-<br />
| 13 || [[User:Tomkralidis|Tom Kralidis]] || CA || tomkralidis (at) gmail.com || OSGeo || pycsw, OWSLib, pygeoapi, GeoHealthCheck, MapServer, other geopython projects || (x) || (x) || (x)<br />
|-<br />
| 14 || [[User:jerstlouis|Jerome St-Louis]] || CA || jerome (at) ecere.com || Ecere || Ecere SDK, GNOSIS SDK || (x) || (x) || (x)<br />
|-<br />
| 15 || [[User:darkblue_b|Brian M Hamlin]] || US || maplabs -at- light42 -dot- com || OSGeo || OSGeoLive, GEOS || (x) || (x) || (x)<br />
|-<br />
| 16 || [[User:T-book|Toni Schönbuchner]] || DE || toni.schoenbuchner -at- csgis -dot- de || csgis || GeoNode|| - || - || x<br />
|-<br />
| 17 || [[User:PierreAbbat|Pierre Abbat]] || US || phma@bezitopo.org || OSGeo || OSGeoLive, PDAL || x || x || x<br />
|-<br />
| 18 || [[User:dovsienko|Denis Ovsienko]] || UK || denis@ovsienko.info || || GRASS GIS || x || x || x<br />
|-<br />
| 19 || [[Florian Hoedt]] || DE || florian.hoedt -at- thuenen.de || Thünen Institut || GeoNode || - || - || x<br />
|-<br />
| 20 ||[[User:alexgleith|Alex Leith]] || AU || alexgleith@gmail.com || Geoscience Australia || The Open Data Cube || (x) || (x) || (x)<br />
|-<br />
| 21 ||[[User:Jgrocha|Jorge Gustavo Rocha]] || PT || jgr@geomaster.pt || Geomaster || QGIS Bug fixing || x || x || x<br />
|-<br />
| 22 || [[User:chiossif|Christos Iosifidis]] || GR || chiossif(at)yahoo.com || NTUA, GRNET || OSGeoLive, GRASS GIS, SAGA GIS || x || x || x<br />
|-<br />
| 23 || Ricardo Garcia Silva || PT || ricardo.garcia.silva(at)gmail.com || Kartoza || GeoNode, pycsw || x || || <br />
|-<br />
| 24 || [[User:sdlime|Steve Lime]] || US || sdlime(at)gmail.com || MNIT || MapServer (as time permits) || (x) || (x) || (x)<br />
|-<br />
| 25 || [[User:Stenger|Dirk Stenger]] || DE || stenger at lat-lon dot de || lat/lon || TEAM Engine || (x) || ||<br />
|-<br />
| 26 || [[User:jboue|Jérome Boué]] || FR || jbo-ads (at) mailo.com || || MapCache, MapServer (as time permits, mainly on #mapserver and #tosprint IRC channels) || (x) || (x) || (x)<br />
|-<br />
| 27 || [[User:Rajatshinde|Rajat Shinde]] || IN || rajatshinde2303 (at) gmail.com || || pgRouting Workshop || x || || <br />
|-<br />
| 28 || [[User:Mahmsakr|Mahmoud SAKR]] || BE || mahmoud.sakr@ulb.ac.be || Université Libre de Bruxelles || MobilityDB, and will be visiting OSGeoLive, OGC, and pgRouting || (x) || || (x)<br />
|-<br />
| 29 || [[User:Krashish8|Ashish Kumar]] || IN || ashishkr23438 (at) gmail.com || || pgRouting || x || || <br />
|-<br />
| 30 || [[User:djay|Gérald Fenoy]] || FR || gerald.fenoy (at) geolabs.fr || GeoLabs || ZOO-Project, OGC API - Processes || || x || x<br />
|-<br />
| 31 ||[[User:rouault|Even Rouault]] || FR || even.rouault at spatialys.com || Spatialys || GDAL, PROJ, Mapserver || x || x || x<br />
|-<br />
| 32 || [[User:Enock4seth|Enock Seth Nyamador]] || DE/GH || enockseth (at) gmail.com || || OSGeoLive || || x || x<br />
|-<br />
| 33 || [[User:Bakaniko|Nicolas Roelandt]] || FR || roelandtn.pro (at) gmail.com || || OSGeoLive || x || x || x<br />
|-<br />
| 34 || Add your info here || || || || || || ||<br />
|-<br />
|}<br />
<br />
== Communication ==<br />
<br />
* Please join the mailing list: https://lists.osgeo.org/mailman/listinfo/tosprint<br />
* IRC chat during the event: #tosprint Server: irc.freenode.net<br />
* Gitter channel: https://gitter.im/OSGeo/Sprint<br />
* Projects can report their progress by adding slides to the event presentation https://docs.google.com/presentation/d/1jKInzGnY_9ad4srD4TtfD7jKBjMrcyL51QIR3z13Ov8/edit?usp=sharing<br />
<br />
== Sponsoring ==<br />
<br />
The Open Source Geospatial Foundation (OSGeo) has a long tradition of organizing code sprints for developers of Open Source GIS software.<br />
(https://wiki.osgeo.org/wiki/Category:Code_Sprints).<br />
<br />
An international community/code sprint for OSGeo will take place Nov 17-19, 2020.<br />
<br />
We expect about 80 developers from all over the world to come from various [https://www.osgeo.org/, OSGeo] projects. Whether desktop application, geospatial library, metadata catalog or web mapping: be sure to find products in the list that you use. The sprint is also an opportunity for your developers to meet with the core developers of the projects, get a deeper insight into the software and participate in the development.<br />
<br />
This years' sprint will take place online.<br />
<br />
Usually the code sprint costs involve providing the technical infrastructure and space, food and drink for the developers as well as social events. This year only the technical infrastructure costs will be covered since we will be online. <br />
<br />
In order to cover these costs we would be overjoyed to accept offers of sponsorship!<br />
<br />
What we can offer:<br />
* Your logo on top of the [https://www.osgeo.org/events/OSGeo_Community_Sprint_2020/ community sprint website] as well as on all official documents used during the sprint<br />
* Acknowledgement in all sprint related emails<br />
* Our undying gratitude, which comes in handy when you least expect it (remember that feature you wanted?)<br />
<br />
Our sponsorship levels:<br />
* Gold: >= 2500 USD<br />
* Silver: 1500 USD<br />
* Bronze: 750 USD<br />
<br />
So...<br />
* get your company talking to the top project developers.<br />
* encourage your GIS developers to take advantage of this opportunity, there is no better opportunity to learn!<br />
* support the software you use - you benefit immediately.<br />
<br />
Thank you very much!<br />
<br />
Contact: To sponsor, please contact tzotsos@osgeo.org directly.<br />
<br />
== Event Owner ==<br />
* OSGeo Board<br />
<br />
<br />
== Press Release ==<br />
<br />
We are looking forward to the next OSGeo Code Sprint!<br />
<br />
[[Category:Code_Sprints]]<br />
[[Category:C Tribe Code Sprint]]</div>Bakanikohttps://wiki.osgeo.org/w/index.php?title=OSGeo_Community_Sprint_2022&diff=123006OSGeo Community Sprint 20222020-01-13T19:59:57Z<p>Bakaniko: /* Participants */</p>
<hr />
<div>Annual Code Sprint comes to Athens (Greece) in 2020!<br />
<br />
Powered by [[Image:Osgeo-logo.png|250px|link=https://www.osgeo.org]]<br />
<br />
<br />
== Purpose ==<br />
<br />
Bring together project members to make decisions and tackle larger geospatial <br />
problems as in previous years: <br />
* [[OSGeo_Community_Sprint_2019|Minnesota]] (2019)<br />
* [[OSGeo Code Sprint 2018|Bonn]] (2018)<br />
* [[Daytona Beach Code Sprint 2017|Daytona_Beach]] (2017)<br />
* [[Paris Code Sprint 2016|Paris]] (2016)<br />
* [[Philadelphia Code Sprint 2015|Philadelphia]] (2015)<br />
* [[Vienna Code Sprint 2014|Vienna]] (2014)<br />
* [[Boston Code Sprint 2013|Boston]] (2013)<br />
* [[IslandWood Code Sprint 2012|Island Wood (Seattle)]] (2012)<br />
* [[Montreal Code Sprint 2011|Montreal]] (2011)<br />
* [[New York Code Sprint 2010|New York City]] (2010)<br />
* [[Toronto Code Sprint 2009|Toronto]] (2009)<br />
<br />
== Sponsors == <br />
<br />
'''Sponsoring ''' Find out about [[OSGeo_Community_Sprint_2020#Sponsoring |Sponsoring the Event]].<br />
<br />
; <big>Venue Sponsor</big><br />
{| border=0 cellspacing=15 cellpadding=10<br />
||<br />
[[File:logo_daem.png|200px|Municipality of Athens, DAEM S.A.|link=https://www.cityofathens.gr/en/]]<br />
<br><br />
https://www.cityofathens.gr/en/<br />
<br />
|}<br />
<br />
== Dates and Times ==<br />
<br />
* Date: May 25-29 (5 days)<br />
* Time: 8:30am to 4:30pm each day<br />
<br />
== Other Events from January to September 2020 ==<br />
<br />
* [http://2020.foss4g.org/ FOSS4G 2020], August 24-29 in Calgary, Canada<br />
* FOSS4G Europe 2020, July 13-18 (?) in Valmiera, Latvia<br />
* ''please add your event''<br />
<br />
== Location ==<br />
<br />
* [http://www.serafio.gr/portfolio/main-hall/ Serafio main hall], Municipality of Athens<br />
* [https://www.openstreetmap.org/#map=19/37.97325/23.70656 OpenStreetMap]<br />
<br />
<br />
== Project Plans ==<br />
(i.e what do you wish/want/plan to work on during the sprint ?)<br />
<br />
* '''OSGeoLive''':<br />
** Work towards 14.0 release in August<br />
<br />
== Participants ==<br />
<br />
Please add your name and the projects you are planning to sprint and note the likeliness of your attendance.<br />
<br />
{| border="1" cellpadding="2" class="wikitable sortable"<br />
!width="25"|No<br />
!width="250"|Name<br />
!width="100"|Country<br />
!width="250"|Email<br />
!width="250"|Organisation<br />
!width="250"|Projects<br />
!width="25"|Mon<br />
!width="25"|Tue<br />
!width="25"|Wed<br />
!width="25"|Thu<br />
!width="25"|Fri<br />
!width="60"|Accommodation<br />
!width="60"|Likelihood<br />
!width="30"|Food Restrictions<br />
!width="60"|social event<br />
|-<br />
| 1 ||[[User:kalxas|Angelos Tzotsos]] || GR || tzotsos(at)osgeo.org || OSGeo || pycsw, OSGeoLive, GeoNode, UbuntuGIS, pygeoapi, OTB || x || x || x || x || x || booked || Organizer :) || No || x ||<br />
|-<br />
| 2 ||[[User:tomkralidis|Tom Kralidis]] || CA || tomkralidis at gmail.com || self || pycsw, OWSLib, pygeoapi, GeoHealthCheck, MapServer, other geopython projects || x || x || x || x || x || TBD || Likely || No || x ||<br />
|-<br />
| 3 ||[[User:msmitherdc|Michael Smith]] || US || michael.smith.erdc at gmail.com || US Army Corps || PDAL, MapServer, proj, GDAL || x || x || x || x || x || TBD || Likely || No || x ||<br />
|-<br />
| 4 ||[[User:dmorissette|Daniel Morissette]] || CA || dmorissette at mapgears.com || Mapgears || MapServer, GDAL/OGR, MapML || x || x || x || x || x || TBD || Very Likely || No || x ||<br />
|-<br />
| 5 ||[[User:Cvvergara|Vicky Vergara]] || MX || vicky at georepublic.de || Georepublic, OSGeo || pgRouting, OSGeoLive || x || x || x || x || x || TBD || Very Likely || No fish || x ||<br />
|-<br />
| 6 ||[[User:Neteler|Markus Neteler]] || DE || neteler at mundialis.de || mundialis || GRASS GIS,... || x || x || x || x || x || TBD || Likely || No || x ||<br />
|-<br />
| 7 ||[[User:Schpidi|Stephan Meißl]] || AT || stephan.meissl at eox.at || EOX IT Services GmbH || MapServer, EOxServer || x || x || x || x || x || TBD || Very likely || No || x ||<br />
|-<br />
| 8 ||[[User:pwramsey3|Paul Ramsey]] || CA || pramsey at cleverelephant.ca || Crunchy Data || PostGIS, GEOS || ? || x || x || x || x || TBD || Very likely || No || x ||<br />
|-<br />
| 9 ||[[User:pierotofy|Piero Toffanin]] || US || pt at uav4geo.com || OpenDroneMap || OpenDroneMap, PDAL, rio-tiler, DroneDB || ? || x || x || x || x || TBD || Very likely || No || x ||<br />
|-<br />
| 10 ||[[User:hobu|Howard Butler]] || US || howard@hobu.co || Hobu, Inc. || PDAL, Entwine, DroneDB, GDAL, PROJ || x || x || x || x || x || TBD || Very likely || No || x ||<br />
|-<br />
| 11 ||Connor Manning || US || connor@hobu.co || Hobu, Inc. || Entwine, PDAL || x || x || x || x || x || TBD || Very likely || No || x ||<br />
|-<br />
| 12 ||[[User:Chiossif|Christos Iossifides]] || GR || chiossif (at) gmail.com || NTUA || GRASS GIS || x || x || x || x || x || booked || Very likely || No || x ||<br />
|-<br />
| 13 ||[[User:Chambbj|Brad Chambers]] || US || brad.chambers at gmail.com || Grover Consulting Services || PDAL || x || x || x || x || x || TBD || Very likely || No || x ||<br />
|-<br />
| 14 ||[[User:Roelandtn|Nicolas Roelandt]] || FR || roelandtn.pro (at) gmail.com || self || OSGeoLive || x || x || x || x || x || TBD || likely || No || x ||<br />
|}<br />
<br />
== Communication ==<br />
<br />
* Please join the mailing list: https://lists.osgeo.org/mailman/listinfo/tosprint<br />
* IRC chat during the event: #tosprint Server: irc.freenode.net<br />
* Gitter channel: https://gitter.im/OSGeo/Sprint<br />
<br />
== Costs ==<br />
<br />
Participants should plan for the following costs:<br />
<br />
* Travel to Athens<br />
* Accommodation for x nights <br />
<br />
== Individual preparation ==<br />
<br />
* Bring your own laptop<br />
* Bring [https://en.wikipedia.org/wiki/Mains_electricity_by_country your power connector adapter] if needed (photo: [https://en.wikipedia.org/wiki/File:Schuko_plug_and_socket.png Greece]). See also http://www.power-plugs-sockets.com/<br />
* Install Git and compiler tools, and come with a working development environment<br />
<br />
== Sponsoring ==<br />
<br />
The Open Source Geospatial Foundation (OSGeo) has a long tradition of organizing code sprints for developers of Open Source GIS software.<br />
(https://wiki.osgeo.org/wiki/Category:Code_Sprints).<br />
<br />
An international community/code sprint for OSGeo will take place May 25-29, 2020.<br />
<br />
We expect about 80 developers from all over the world to come from various [https://www.osgeo.org/, OSGeo] projects. Whether desktop application, geospatial library, metadata catalog or web mapping: be sure to find products in the list that you use. The sprint is also an opportunity for your developers to meet with the core developers of the projects, get a deeper insight into the software and participate in the development.<br />
<br />
This years' sprint will take place in Athens and will be hosted by [https://www.cityofathens.gr/en/, Municipality of Athens] and organized by members of the local OSGeo Greek chapter.<br />
<br />
In addition to the costs of providing the technical infrastructure and space, food and drink for the developers represents the main cost. Morning/afternoon meals and drinks during the day are planned. In addition, we hope to provide several evening meals and social events.<br />
<br />
In order to cover these costs we would be overjoyed to accept offers of sponsorship!<br />
<br />
What we can offer:<br />
* Your logo on top of the [https://www.osgeo.org/events/OSGeo_Community_Sprint_2020/ community sprint website] as well as on all official documents used during the sprint<br />
* Acknowledgement in all sprint related emails<br />
* Our undying gratitude, which comes in handy when you least expect it (remember that feature you wanted?)<br />
<br />
Our sponsorship levels:<br />
* Gold: >= 2500 USD<br />
* Silver: 1500 USD<br />
* Bronze: 750 USD<br />
<br />
So...<br />
* get your company talking to the top project developers.<br />
* encourage your GIS developers to take advantage of this opportunity, there is no better opportunity to learn!<br />
* support the software you use - you benefit immediately.<br />
<br />
Thank you very much!<br />
<br />
Contact: To sponsor, please contact tosprint@lists.osgeo.org directly.<br />
<br />
== Event Owner ==<br />
* [[User:kalxas|Angelos Tzotsos]]<br />
<br />
== Press Release ==<br />
<br />
We are looking forward to the next OSGeo Code Sprint!<br />
<br />
[[Category:Code_Sprints]]<br />
[[Category:C Tribe Code Sprint]]</div>Bakanikohttps://wiki.osgeo.org/w/index.php?title=OSGeoLive_PSC&diff=121808OSGeoLive PSC2019-09-17T20:03:15Z<p>Bakaniko: </p>
<hr />
<div>The OSGeoLive Project Steering Committee (PSC) is the official managing body of OSGeoLive and is responsible for setting overall project direction. The committee is drawn from the OSGeoLive community and is based on merit and interest.<br />
<br />
==Decisions==<br />
Decisions are based on voting using the following:<br />
* +1 : For<br />
* +0: Mildly for, but mostly indifferent<br />
* 0: Indifferent<br />
* -0: Mildly against, but mostly indifferent<br />
* -1 : Strongly against. This is expected to be accompanied by a reason.<br />
<br />
For most decisions, a motion is raised within one of the OSGeoLive open forums (IRC, email list, etc) and those present vote and decide. Should a decision:<br />
* Be strategic or impact many within OSGeoLive, <br />
* Or if there be contention in deciding, and after discussion at least one member is still strongly against the motion, by continuing to vote -1, <br />
Then the motion should be referred to the PSC. <br />
<br />
For motions presented to the PSC, a motion is considered passed when there are more PSC +1 votes than -1 votes, and either all PSC members have voted, or 4 days have passed. In the case of a tie, the PSC chair shall have 1.5 votes.<br />
<br />
==PSC Members==<br />
* [[Angelos_Tzotsos]] (Chair)<br />
* Brian M Hamlin<br />
* Cameron Shorter<br />
* Alex Mandel<br />
* Johan Van de Wauw<br />
* Bas Couwenberg<br />
* Massimo De Stefano<br />
* Astrid Emde<br />
* [https://wiki.osgeo.org/wiki/User:Roelandtn Nicolas Roelandt]<br />
* Vicky Vergara<br />
<br />
Our thanks to previous PSC members:<br />
* Hamish Bowman<br />
* Ben Caradoc-Davies<br />
<br />
Selection of new PSC members is determined by PSC vote. PSC members may retire any time. If a PSC member becomes inactive for many months they may be invited to retire, and if unresponsive they may be removed by the existing PSC.<br />
<br />
==Expectations of PSC members==<br />
* Regularly contribute to OSGeoLive or related activities<br />
* Help with whatever dirty work is required to keep the project moving forward<br />
* Monitor OSGeo-Live conversations, either in weekly IRC meetings, or on the email list, and contribute constructively where appropriate<br />
* Vote promptly (within days) to motions being raised<br />
<br />
''Credit: This management process draws heavily from other OSGeo project PMC processes.''<br />
<br />
[[Category: OSGeoLive]]</div>Bakanikohttps://wiki.osgeo.org/w/index.php?title=User:Bakaniko&diff=121650User:Bakaniko2019-08-31T06:50:26Z<p>Bakaniko: </p>
<hr />
<div>{{OSGeo Member<br />
|Name=Nicolas Roelandt<br />
|JobTitle=GIS Engineer<br />
|Company=IFSTTAR<br />
|Country=France<br />
|City=Marne-la-Vallée<br />
|Coordinate=48.842298, 2.587371<br />
|LocalChapter=Francophone OSGeo Chapter<br />
|SocialMedia=Roelandtn42 (twitter);<br />
|Photo=nicolas_roelandt.jpg<br />
|Languages=French; English;<br />
|languages=French, English<br />
\<br />
}}<br />
{{OSGeo Experience<br />
|User=Yes<br />
|Committee=No<br />
|Board=No<br />
|Coder=No<br />
|Translate=Yes<br />
|PSC=Yes<br />
|ExBoard=No<br />
|Charter=Yes<br />
|Chair=No<br />
|SolKatz=No<br />
|Committer=Yes<br />
}}<br />
GIS user and FOSS hactivist, I combined both by joining the French chapter of OSGeo.<br />
<br />
I participate to the OSGeoLive documentation and translation on [Transifex https://www.transifex.com/osgeo/osgeolive/dashboard/]<br />
<br />
<br />
<br />
<br />
2016: FOSS4G-fr, Paris, France: organization, program committee<br />
<br />
2017: FOSS4G-EU, Paris France: organization, workshop committee<br />
<br />
2017: OSGEO charter member<br />
<br />
2017: OSGeoLive PSC<br />
<br />
2018: FOSS4G-fr, Paris, France: organization, program committee<br />
<br />
2019: FOSS4G Bucarest, Romania: [https://bakaniko.github.io/FOSS4G2019_Geoprocessing_with_R_workshop/ R spatial workshop], OSGeoLive workshop, [https://roelandtn.frama.io/slides/20190830_FOSS4G_Command_line_GIS.html Are we going back to command line ?], gFlowiz project presentation<br />
<br />
<br />
[[Category:OSGeo_Advocate]]</div>Bakanikohttps://wiki.osgeo.org/w/index.php?title=User:Bakaniko&diff=121649User:Bakaniko2019-08-31T06:45:20Z<p>Bakaniko: </p>
<hr />
<div>{{OSGeo Member<br />
|Name=Nicolas Roelandt<br />
|JobTitle=GIS Engineer<br />
|Company=IFSTTAR<br />
|Country=France<br />
|City=Marne-la-Vallée<br />
|Coordinate=48.842298, 2.587371<br />
|LocalChapter=Francophone OSGeo Chapter<br />
|SocialMedia=Roelandtn42 (twitter);<br />
|Photo=nicolas_roelandt.jpg<br />
|Languages=French; English;<br />
|languages=French, English<br />
\<br />
}}<br />
{{OSGeo Experience<br />
|User=Yes<br />
|Committee=No<br />
|Board=No<br />
|Coder=No<br />
|Translate=Yes<br />
|PSC=Yes<br />
|ExBoard=No<br />
|Charter=Yes<br />
|Chair=No<br />
|SolKatz=No<br />
|Committer=Yes<br />
}}<br />
<br />
GIS user and FOSS hactivist, I combined both by joining the French chapter of OSGeo.<br />
<br />
2016: FOSS4G-fr, Paris, France: organization, program committee<br />
<br />
2017: FOSS4G-EU, Paris France: organization, workshop committee<br />
<br />
2017: OSGEO charter member<br />
<br />
2017: OSGeoLive PSC<br />
<br />
2018: FOSS4G-fr, Paris, France: organization, program committee<br />
<br />
2019: FOSS4G Bucarest, Romania: [https://bakaniko.github.io/FOSS4G2019_Geoprocessing_with_R_workshop/ R spatial workshop], OSGeoLive workshop, [https://roelandtn.frama.io/slides/20190830_FOSS4G_Command_line_GIS.html Are we going back to command line ?], gFlowiz project presentation<br />
<br />
<br />
[[Category:OSGeo_Advocate]]</div>Bakanikohttps://wiki.osgeo.org/w/index.php?title=User:Bakaniko&diff=121648User:Bakaniko2019-08-31T06:44:48Z<p>Bakaniko: </p>
<hr />
<div>{{OSGeo Member<br />
|Name=Nicolas Roelandt<br />
|JobTitle=GIS Engineer<br />
|Company=IFSTTAR<br />
|Country=France<br />
|City=Marne-la-Vallée<br />
|Coordinate=48.842298, 2.587371<br />
|LocalChapter=Francophone OSGeo Chapter<br />
|SocialMedia=Roelandtn42 (twitter);<br />
|Photo=nicolas_roelandt.jpg<br />
|Languages=French; English;<br />
|languages=French, English<br />
\<br />
}}<br />
{{OSGeo Experience<br />
|User=Yes<br />
|Committee=No<br />
|Board=No<br />
|Coder=No<br />
|Translate=Yes<br />
|PSC=Yes<br />
|ExBoard=No<br />
|Charter=Yes<br />
|Chair=No<br />
|SolKatz=No<br />
|Committer=Yes<br />
}}<br />
GIS user and FOSS hactivist, I combined both by joining the French chapter of OSGeo.<br />
I also join the OSGeo-Live PSC and participated to the organization of several local FOSS4G.<br />
<br />
2016: FOSS4G-fr, Paris, France: organization, program committee<br />
<br />
2017: FOSS4G-EU, Paris France: organization, workshop committee<br />
<br />
2017: OSGEO charter member<br />
<br />
2017: OSGeoLive PSC<br />
<br />
2018: FOSS4G-fr, Paris, France: organization, program committee<br />
<br />
2019: FOSS4G Bucarest, Romania: [https://bakaniko.github.io/FOSS4G2019_Geoprocessing_with_R_workshop/ R spatial workshop], OSGeoLive workshop, [https://roelandtn.frama.io/slides/20190830_FOSS4G_Command_line_GIS.html Are we going back to command line ?], gFlowiz project presentation<br />
<br />
<br />
[[Category:OSGeo_Advocate]]</div>Bakanikohttps://wiki.osgeo.org/w/index.php?title=User:Bakaniko&diff=121647User:Bakaniko2019-08-31T06:41:32Z<p>Bakaniko: </p>
<hr />
<div>{{OSGeo Member<br />
|Name=Nicolas Roelandt<br />
|JobTitle=GIS Engineer<br />
|Company=IFSTTAR<br />
|Country=France<br />
|City=Marne-la-Vallée<br />
|Coordinate=48.842298, 2.587371<br />
|LocalChapter=Francophone OSGeo Chapter<br />
|SocialMedia=Roelandtn42 (twitter);<br />
|Photo=nicolas_roelandt.jpg<br />
|Languages=French; English;<br />
|languages=French, English<br />
\<br />
}}<br />
{{OSGeo Experience<br />
|User=Yes<br />
|Committee=No<br />
|Board=No<br />
|Coder=No<br />
|Translate=Yes<br />
|PSC=Yes<br />
|ExBoard=No<br />
|Charter=Yes<br />
|Chair=No<br />
|SolKatz=No<br />
|Committer=Yes<br />
}}<br />
GIS user and FOSS hactivist, I combined both by joining the French chapter of OSGeo.<br />
I also join the OSGeo-Live PSC and participated to the organization of several local FOSS4G.<br />
<br />
2016: FOSS4G-fr, Paris, France: organization, program committee<br />
<br />
2017: FOSS4G-EU, Paris France: organization, workshop committee<br />
<br />
2017: OSGEO charter member<br />
<br />
2017: OSGeoLive PSC<br />
<br />
2018: FOSS4G-fr, Paris, France: organization, program committee<br />
<br />
2019: FOSS4G Bucarest, Romania: R spatial workshop, OSGeoLive workshop, several presentations<br />
<br />
<br />
[[Category:OSGeo_Advocate]]</div>Bakanikohttps://wiki.osgeo.org/w/index.php?title=User:Bakaniko&diff=121645User:Bakaniko2019-08-31T06:40:02Z<p>Bakaniko: </p>
<hr />
<div>{{OSGeo Member<br />
|Name=Nicolas Roelandt<br />
|JobTitle=GIS Engineer<br />
|Company=IFSTTAR<br />
|Country=France<br />
|City=Marne-la-Vallée<br />
|Coordinate=48.842298, 2.587371<br />
|LocalChapter=Francophone OSGeo Chapter<br />
|SocialMedia=Roelandtn42 (twitter);<br />
|Photo=nicolas_roelandt.jpg<br />
|Languages=French; English;<br />
|languages=French, English<br />
\<br />
}}<br />
{{OSGeo Experience<br />
|User=Yes<br />
|Committee=No<br />
|Board=No<br />
|Coder=No<br />
|Translate=Yes<br />
|PSC=Yes<br />
|ExBoard=No<br />
|Charter=Yes<br />
|Chair=No<br />
|SolKatz=No<br />
|Committer=Yes<br />
}}<br />
GIS user and FOSS hactivist, I combined both by joining the French chapter of OSGeo.<br />
I also join the OSGeo-Live PSC and participated to the organization of several local FOSS4G.<br />
<br />
2016: FOSS4G-fr, Paris, France: organization, program committee<br />
<br />
2017: FOSS4G-EU, Paris France: organization, workshop committee<br />
<br />
2017: OSGEO charter member<br />
<br />
2017: OSGeoLive PSC<br />
<br />
2018: FOSS4G-fr, Paris, France: organization, program committee<br />
<br />
2019: FOSS4G Bucarest, Romania: R spatial workshop, OSGeoLive workshop,<br />
<br />
<br />
[[Category:OSGeo_Advocate]]</div>Bakanikohttps://wiki.osgeo.org/w/index.php?title=User:Bakaniko&diff=121644User:Bakaniko2019-08-31T06:39:30Z<p>Bakaniko: </p>
<hr />
<div>{{OSGeo Member<br />
|Name=Nicolas Roelandt<br />
|JobTitle=GIS Engineer<br />
|Company=IFSTTAR<br />
|Country=France<br />
|City=Marne-la-Vallée<br />
|Coordinate=48.842298, 2.587371<br />
|LocalChapter=Francophone OSGeo Chapter<br />
|SocialMedia=Roelandtn42 (twitter);<br />
|Photo=nicolas_roelandt.jpg<br />
|Languages=French; English;<br />
|languages=French, English<br />
\<br />
}}<br />
{{OSGeo Experience<br />
|User=Yes<br />
|Committee=No<br />
|Board=No<br />
|Coder=No<br />
|Translate=Yes<br />
|PSC=Yes<br />
|ExBoard=No<br />
|Charter=Yes<br />
|Chair=No<br />
|SolKatz=No<br />
|Committer=Yes<br />
}}<br />
GIS user and FOSS hactivist, I combined both by joining the French chapter of OSGeo.<br />
I also join the OSGeo-Live PSC and participated to the organization of several local FOSS4G.<br />
<br />
2016: FOSS4G-fr, Paris, France: organization, program committee<br />
2017: FOSS4G-EU, Paris France: organization, workshop committee<br />
2017: OSGEO charter member<br />
2017: OSGeoLive PSC<br />
2018: FOSS4G-fr, Paris, France: organization, program committee<br />
2019: FOSS4G Bucarest, Romania: R spatial workshop, OSGeoLive workshop,<br />
<br />
<br />
[[Category:OSGeo_Advocate]]</div>Bakanikohttps://wiki.osgeo.org/w/index.php?title=FOSS4G_2019_Community_Sprint&diff=121638FOSS4G 2019 Community Sprint2019-08-31T06:24:45Z<p>Bakaniko: </p>
<hr />
<div>== Code Sprint ==<br />
<br />
This year, we are following the OSGeo tradition of hosting a code sprint right after [http://2019.foss4g.org FOSS4G 2019]. <br />
<br />
Participation is free of charge and anyone involved or interested in getting involved in OSGeo community projects is welcome.<br />
<br />
You can choose to contribute to one or more projects. The sky is the limit. There’s always plenty to do – it’s not all about programming. Translation, documentation, feedback, discussions, and testing are very important for projects! Conference registration is not a prerequisite for participation in code sprint.<br />
<br />
=== When ===<br />
The code sprint will be held Saturday August 31 2019.<br />
<br />
=== Where ===<br />
<br />
University of Bucharest, Faculty of Geography (Bucharest, Romania) <br />
* Bulevardul Nicolae Bălcescu 1, Bulevardul Nicolae Bălcescu 1<br />
* https://en.unibuc.ro/academic-programmes/faculties/faculty-of-geography/<br />
<br />
== Registered Attendees ==<br />
The code sprint is free of charge but we kindly ask you to write down your name for better planning<br />
<br />
{| border="1" cellpadding="2" class="wikitable sortable"<br />
!width="30"|No<br />
!width="250"|Name<br />
!width="250"|Email<br />
!width="250"|Projects<br />
!width="250"|Saturday<br />
!width="30"|vegetarian food<br />
|-<br />
|1 || [[User:Lucadelu|Luca Delucchi]] || lucadeluge gmail com || GRASS GIS, pyModis, OSGeoLive (code sprint organizer) || x || <br />
|+<br />
|2 || [[User:Neteler|Markus Neteler]] || neteler osgeo org || GRASS GIS, actinia, ... || x || (preferably)<br />
|+<br />
|3 || [[User:Astrid_Emde|Astrid Emde]] || astrid_emde osgeo org || OSGeo, OSGeoLive, Mapbender || x || x<br />
|+<br />
|4 || [[User:Tomkralidis|Tom Kralidis]] || tomkralidis gmail com|| pycsw, OWSLib, pygeoapi, GeoHealthCheck, MapServer, other geopython projects || x || x<br />
|+<br />
|5 || [[User:Veroandreo|Veronica Andreo]] || veroandreo gmail com|| GRASS GIS || x || <br />
|+<br />
|6 || [[User:Komzpa|Darafei Praliaskouski]] || komzpa@gmail.com || PostGIS || x || <br />
|+<br />
|7 || [[User:Kalxas|Angelos Tzotsos]] || tzotsos osgeo org|| OSGeoLive, pycsw, GeoNode, pygeoapi, OWSLib, UbuntuGIS || x ||<br />
|+<br />
|8 || [[User:Cvvergara|Vicky Vergara]] || vicky at georepublic.de || pgRouting, OSGeoLive, OSGeo web page || x || <br />
|+<br />
|9 || [[User:boonen|Jan Boonen]] || jan.boonen at geodan.nl || GeoTools, GeoServer, PostGIS || x (have to catch a flight at 18h) || x <br />
|+<br />
|10 || [[User:StephanR|Stephan Reichhelm]] || reichhelm grit de || deegree || x || <br />
|+<br />
|11 || [[User:Lastools|Martin Isenburg]] || martin rapidlasso com || RasterLAZ driver for GDAL || x || (no plastic) <br />
|+<br />
|12 || [[User:Just|Just van den Broecke]] || justb4 gmail com || pygeoapi, GeoHealthCheck, other geopython projects || x (have to catch a flight at 16h) || x <br />
|+<br />
|13 || [[User:Francbartoli|Francesco Bartoli]] || xbartolone at gmail com || pygeoapi, GeoNode || x (have to catch a flight at 18h) || <br />
|+<br />
|14 || [[User:bphamhuu|Bang Pham Huu]] || b.phamhuu at jacobs-university.de|| Rasdaman || x || <br />
|+<br />
|15 || [[User:djay|Gérald Fenoy]] || gerald.fenoy at geolabs.fr|| ZOO-Project || x || <br />
|+<br />
|16 || [[User:Mlennert|Moritz Lennert]] || mlennert at club.worldonline.be|| GRASS GIS || x (only in the morning - train at 14:00) || <br />
|+<br />
|17 || [[User:johanvdw|Johan Van de Wauw]] || johan at gisky.be|| SAGA GIS, FOSS4G.be || x || x<br />
|+<br />
|18 || [[User:Jgrocha|Jorge Gustavo Rocha]] || jgr@geomaster.pt || QGIS || x (have to catch a flight at 16h40) ||<br />
|+<br />
|19 || [[User:sethg|Seth Girvin]] || sethg at geographika.co.uk || MapServer, GeoExt, OSGeoLive|| x (have to catch a flight at 14h30) ||<br />
|+<br />
|20 || [[User:Lads|Luís de Sousa]] || luis.de.sousa at protonmail dot ch || PyWPS, pyGeoAPI || x ||<br />
|+<br />
|21 || [[User:Vmische|Volker Mische]] || volker.mische at gmail.com|| IPFS, Noise || x ||<br />
|+<br />
|22 || [[User:Tkardi|Tõnis Kärdi]] || tonis.kardi at gmail.com|| OSGeoLive, ... || x ||<br />
|+<br />
|23 || [[User:pesekon2|Ondřej Pešek]] || pesej.ondrek at gmail.com|| GRASS GIS || x ||<br />
|+<br />
|24 || [[User:Mazingaro|Alen Mangafić]] || amangaf at gmail.com|| || have to catch a flight at 18h || x <br />
|+<br />
|25 || [[Tomaž Žagar]] || ztomaz108 at gmail.com|| || have to catch a flight at 18h || x <br />
|+<br />
|26 || [[User:jerstlouis|Jerome St-Louis]] || jerome at ecere.com|| eC, Ecere, GNOSIS || x || <br />
|+<br />
|27 || [[User:ImreSamu|Imre Samu]] || pella.samu gmail.com || OSM, taginfo, data , ... || x ||<br />
|+<br />
|28 || [[User:Martinl|Martin Landa]] || landa.martin gmail.com || GRASS GIS || x ||<br />
|+<br />
|29 || [[User:posiki|Pekka Sarkola]] || pos iki.fi || QGIS, Geoserver || x ||<br />
|+<br />
|30 || [[User:santtuvp|Santtu Pyykkönen]] || santtu.pyykkonen gmail.com || QGIS, OSGeoLive || x ||<br />
|+<br />
|31 || [[User:Roelandtn|Nicolas Roelandt]] || roelandt.pro gmail.com || OSGeoLive || x ||<br />
|}<br />
<br />
== Workgroups ==<br />
<br />
=== Project-name ===<br />
To participate, copy this project skeleton and start a section below for your project.<br />
<br />
'''Attending:''' <br />
*user <br />
*user<br />
<br />
'''Goals:''' <br />
*your goals<br />
<br />
<br />
=== OSGeoLive ===<br />
<br />
'''Attending:''' <br />
* [[User:Astrid_Emde|Astrid Emde]]<br />
* [[User:Cvvergara|Vicky Vergara]]<br />
* [[User:Tkardi|Tõnis Kärdi]]<br />
* [[User:Roelandtn|Nicolas Roelandt]]<br />
<br />
'''Goals:''' <br />
* Documentation<br />
<br />
=== GeoServer ===<br />
<br />
'''Attending:''' <br />
* [[User:Jive|Jody Garnett]]<br />
* [[User:boonen|Jan Boonen]]<br />
<br />
'''Goals:''' <br />
*Follow up to Ian Turton's *Becoming a Documentation Contributor* lab with documentation activities.<br />
*Follow up to GeoServer Developers workshop with mentoring sessions towards your first pull-request.<br />
*TBD<br />
<br />
=== GRASS GIS ===<br />
<br />
'''Attending:''' <br />
* [[User:Neteler|Markus Neteler]]<br />
* [[User:Mlennert|Moritz Lennert]]<br />
* [[User:Veroandreo| Veronica Andreo]]<br />
* [[User:pesekon2| Ondřej Pešek]]<br />
* [[User:Martinl|Martin Landa]]<br />
<br />
'''Goals:''' <br />
* Finetune git workflows<br />
* New GRASS GIS Web site<br />
* [https://github.com/mundialis/actinia_core/ actinia OSGeo community project]: how to contribute<br />
* fix WinGRASS builds<br />
* band references discussion, https://github.com/OSGeo/grass/pull/63<br />
* ubuntugis expr GRASS 7.8.0RC1<br />
<br />
=== PyWPS + pyGeoAPI + GeoHealthCheck ===<br />
<br />
'''Attending:''' <br />
* [[User:Lads|Luís de Sousa]]<br />
* [[User:Just|Just van den Broecke]] <br />
<br />
'''Goals:''' <br />
* Python 3<br />
* New OGC standards<br />
<br />
=== CRO ===<br />
<br />
'''Attending:''' <br />
* [[User:Cvvergara|Vicky Vergara]]<br />
<br />
<br />
'''Goals:''' <br />
* Update procedures to recent approved rules<br />
<br />
=== eC / Ecere / GNOSIS SDKs ===<br />
<br />
'''Attending:''' <br />
* [[User:jerstlouis|Jerome St-Louis]]<br />
<br />
<br />
'''Goals:''' <br />
* Work on maps rendering in new GNOSIS 3 library<br />
* Discuss our open-source projects (http://github.com/ecere/ecere-sdk), or open specifications (e.g. GNOSIS Map Tiles, CMSS styling language) if anyone is interested<br />
<br />
== Event Organization ==<br />
<br />
The [https://2019.foss4g.org/about/committees BLOC] is the proud organiser of the code sprint.<br />
<br />
For any question you can contact [[User:Lucadelu|Luca Delucchi]], the person in charge of the code sprint. <br />
<br />
<br />
[[Category:FOSS4G2019]] [[Category:FOSS4G]] [[Category:Code_Sprints]]</div>Bakanikohttps://wiki.osgeo.org/w/index.php?title=OSGeoLive_Budget_2019&diff=119316OSGeoLive Budget 20192019-01-22T20:46:11Z<p>Bakaniko: </p>
<hr />
<div>=OSGeoLive Budget 2019=<br />
<br />
The OSGeoLive project requests to OSGeo a total budget for the 2019 of 1,000 USD.<br />
<br />
This is intended to cover:<br />
<br />
T-shirts for community sprints & promotion/users 500 USD<br />
Stickers and postcards (conferences, talks, general promotion) 500 USD<br />
Project development (Transifex Machine Translation, Cloud services) : 1000 USD<br />
<br />
As it is the first time the OSGeoLive project request a budget, all expenses are not known.<br />
We might request advances if the project has to provide USB keys to conferences as suggested in the marketing committee mailing list.</div>Bakanikohttps://wiki.osgeo.org/w/index.php?title=OSGeoLive_Budget_2019&diff=119315OSGeoLive Budget 20192019-01-22T20:33:29Z<p>Bakaniko: Created page with "= OSGeoLive Budget 2019= The OSGeoLive project requests to OSGeo a total budget for the 2019 of 1,000 USD. This is intended to cover: T-shirts for community sprints & p..."</p>
<hr />
<div>= OSGeoLive Budget 2019=<br />
<br />
The OSGeoLive project requests to OSGeo a total budget for the 2019 of 1,000 USD.<br />
<br />
This is intended to cover:<br />
<br />
T-shirts for community sprints & promotion/users 500 USD<br />
Stickers and postcards (conferences, talks, general promotion) 500 USD<br />
Project development (Transifex Machine Translation, Cloud services) : 1000 USD<br />
<br />
As it is the first time the OSGeoLive project request a budget,</div>Bakanikohttps://wiki.osgeo.org/w/index.php?title=Capitole_du_libre_2018&diff=118122Capitole du libre 20182018-11-19T20:03:52Z<p>Bakaniko: /* Bénévoles présents */</p>
<hr />
<div>OSGeo-fr summary of Capitole du Libre 2018 event at Toulouse (in French)<br />
<br />
= Capitole du Libre =<br />
Date: 17 et 18 décembre 2018<br />
<br />
== Bénévoles présents ==<br />
<br />
* Damien Despres<br />
* Anne Quesnel<br />
* Manuel Grizonnet<br />
* Nicolas Roelandt<br />
<br />
== Description de l'événement ==<br />
<br />
* Sur deux jours, le weekend du 17 et 18 novembre 2018<br />
* 1600 visiteurs le samedi, 700 visiteurs le dimanche (comptage organisateurs)<br />
* village associatif avec 26 stands<br />
* 118 speakers, 95 conférences, 25 ateliers<br />
<br />
== Rôle de l'OSGeo-fr ==<br />
* Tenir un stand en companie d'OSM France<br />
* Renseigner les curieux sur la géomatique et les outils géomatiques libres<br />
* Faire des démos courtes sur les outils (QGIS, OSGeoLive, PostGIS), les standards et protocoles (WMTS avec OSM, librairies GDAL/OGR), <br />
l'éducation (tutoriels OSGeoLive) et les données libres (Natural Earth, OSM, fichiers IGN en licence ouverte) en géomatique<br />
<br />
== Visiteurs comptabilisés au stand ==<br />
* samedi: 33 personnes<br />
* dimanche : 17 personnes<br />
<br />
Soit un total de 50 personnes. Beaucoup venaient voir OSM, certains avaient quand même des problématiques<br />
géospatiales ou étaient curieux / intéressés par l'OSGeo et les FOSS4G.<br />
<br />
== Goodies ==<br />
<br />
Damien a réceptionné chez lui les goodies suivants:<br />
- autocollants OSGeo francophone<br />
- Totem OSGeo-fr<br />
- Colis OSGeo marketing: stickers QGIS, OSM; cartes postales OSGeoLive<br />
<br />
Nous remercions Damien d'avoir accepté de les recevoir à son domicile.<br />
Les stickers ont été distribués en partie, la majorité remonte à Paris avec NR pour le POSS en décembre 2018.<br />
<br />
<br />
== Contacts ==<br />
=== Pierre Vrot ===<br />
=> Géomaticien toulousain qui cherche à s'impliquer dans les activités de l'association.<br />
Invité à se faire connaître sur la liste francophone et éventuellement rejoindre un projet OSGeo.<br />
Participer aux groupes de travail.<br />
<br />
Il y a un travail à faire sur "Comment les gens souhaitent devenir bénévoles peuvent s'impliquer dans les activités de l'association"<br />
Uniquement pendant les événements OSGO-fr et en représentation (POSS, Capitole du Libre, FOSSDEM) ?<br />
Autres activités ?<br />
<br />
=== Vincent Privat ===<br />
Core developper de JOSM, pourrait aider à maintenir JOSM au sein d'OsgeoLive<br />
<br />
=== Alban Kraus ===<br />
Géomaticien Agglo de Tulle : géomatique libre en collectivité territoriale au FOSS4G 2020 ?<br />
Invité à rejoindre la mailing list francophone<br />
<br />
=== Contributeurs OSM toulousains ===<br />
Vincent, Sébastien<br />
<br />
=== Pistes d'améliorations ===<br />
<br />
1. poster avec les projets OSGeo (Nom + logos)<br />
2. affiche avec les prochains événements<br />
3. plaquettes de présentation de l'OSGeo</div>Bakanikohttps://wiki.osgeo.org/w/index.php?title=Capitole_du_libre_2018&diff=118121Capitole du libre 20182018-11-19T20:03:29Z<p>Bakaniko: /* Bénévoles présents */</p>
<hr />
<div>OSGeo-fr summary of Capitole du Libre 2018 event at Toulouse (in French)<br />
<br />
= Capitole du Libre =<br />
Date: 17 et 18 décembre 2018<br />
<br />
== Bénévoles présents ==<br />
<br />
1. Damien Despres<br />
2. Anne Quesnel<br />
3. Manuel Grizonnet<br />
4. Nicolas Roelandt<br />
<br />
== Description de l'événement ==<br />
<br />
* Sur deux jours, le weekend du 17 et 18 novembre 2018<br />
* 1600 visiteurs le samedi, 700 visiteurs le dimanche (comptage organisateurs)<br />
* village associatif avec 26 stands<br />
* 118 speakers, 95 conférences, 25 ateliers<br />
<br />
== Rôle de l'OSGeo-fr ==<br />
* Tenir un stand en companie d'OSM France<br />
* Renseigner les curieux sur la géomatique et les outils géomatiques libres<br />
* Faire des démos courtes sur les outils (QGIS, OSGeoLive, PostGIS), les standards et protocoles (WMTS avec OSM, librairies GDAL/OGR), <br />
l'éducation (tutoriels OSGeoLive) et les données libres (Natural Earth, OSM, fichiers IGN en licence ouverte) en géomatique<br />
<br />
== Visiteurs comptabilisés au stand ==<br />
* samedi: 33 personnes<br />
* dimanche : 17 personnes<br />
<br />
Soit un total de 50 personnes. Beaucoup venaient voir OSM, certains avaient quand même des problématiques<br />
géospatiales ou étaient curieux / intéressés par l'OSGeo et les FOSS4G.<br />
<br />
== Goodies ==<br />
<br />
Damien a réceptionné chez lui les goodies suivants:<br />
- autocollants OSGeo francophone<br />
- Totem OSGeo-fr<br />
- Colis OSGeo marketing: stickers QGIS, OSM; cartes postales OSGeoLive<br />
<br />
Nous remercions Damien d'avoir accepté de les recevoir à son domicile.<br />
Les stickers ont été distribués en partie, la majorité remonte à Paris avec NR pour le POSS en décembre 2018.<br />
<br />
<br />
== Contacts ==<br />
=== Pierre Vrot ===<br />
=> Géomaticien toulousain qui cherche à s'impliquer dans les activités de l'association.<br />
Invité à se faire connaître sur la liste francophone et éventuellement rejoindre un projet OSGeo.<br />
Participer aux groupes de travail.<br />
<br />
Il y a un travail à faire sur "Comment les gens souhaitent devenir bénévoles peuvent s'impliquer dans les activités de l'association"<br />
Uniquement pendant les événements OSGO-fr et en représentation (POSS, Capitole du Libre, FOSSDEM) ?<br />
Autres activités ?<br />
<br />
=== Vincent Privat ===<br />
Core developper de JOSM, pourrait aider à maintenir JOSM au sein d'OsgeoLive<br />
<br />
=== Alban Kraus ===<br />
Géomaticien Agglo de Tulle : géomatique libre en collectivité territoriale au FOSS4G 2020 ?<br />
Invité à rejoindre la mailing list francophone<br />
<br />
=== Contributeurs OSM toulousains ===<br />
Vincent, Sébastien<br />
<br />
=== Pistes d'améliorations ===<br />
<br />
1. poster avec les projets OSGeo (Nom + logos)<br />
2. affiche avec les prochains événements<br />
3. plaquettes de présentation de l'OSGeo</div>Bakanikohttps://wiki.osgeo.org/w/index.php?title=Capitole_du_libre_2018&diff=118120Capitole du libre 20182018-11-19T20:03:17Z<p>Bakaniko: /* Visiteurs comptabilisés au stand */</p>
<hr />
<div>OSGeo-fr summary of Capitole du Libre 2018 event at Toulouse (in French)<br />
<br />
= Capitole du Libre =<br />
Date: 17 et 18 décembre 2018<br />
<br />
== Bénévoles présents ==<br />
1. Damien Despres<br />
2. Anne Quesnel<br />
3. Manuel Grizonnet<br />
4. Nicolas Roelandt<br />
<br />
== Description de l'événement ==<br />
<br />
* Sur deux jours, le weekend du 17 et 18 novembre 2018<br />
* 1600 visiteurs le samedi, 700 visiteurs le dimanche (comptage organisateurs)<br />
* village associatif avec 26 stands<br />
* 118 speakers, 95 conférences, 25 ateliers<br />
<br />
== Rôle de l'OSGeo-fr ==<br />
* Tenir un stand en companie d'OSM France<br />
* Renseigner les curieux sur la géomatique et les outils géomatiques libres<br />
* Faire des démos courtes sur les outils (QGIS, OSGeoLive, PostGIS), les standards et protocoles (WMTS avec OSM, librairies GDAL/OGR), <br />
l'éducation (tutoriels OSGeoLive) et les données libres (Natural Earth, OSM, fichiers IGN en licence ouverte) en géomatique<br />
<br />
== Visiteurs comptabilisés au stand ==<br />
* samedi: 33 personnes<br />
* dimanche : 17 personnes<br />
<br />
Soit un total de 50 personnes. Beaucoup venaient voir OSM, certains avaient quand même des problématiques<br />
géospatiales ou étaient curieux / intéressés par l'OSGeo et les FOSS4G.<br />
<br />
== Goodies ==<br />
<br />
Damien a réceptionné chez lui les goodies suivants:<br />
- autocollants OSGeo francophone<br />
- Totem OSGeo-fr<br />
- Colis OSGeo marketing: stickers QGIS, OSM; cartes postales OSGeoLive<br />
<br />
Nous remercions Damien d'avoir accepté de les recevoir à son domicile.<br />
Les stickers ont été distribués en partie, la majorité remonte à Paris avec NR pour le POSS en décembre 2018.<br />
<br />
<br />
== Contacts ==<br />
=== Pierre Vrot ===<br />
=> Géomaticien toulousain qui cherche à s'impliquer dans les activités de l'association.<br />
Invité à se faire connaître sur la liste francophone et éventuellement rejoindre un projet OSGeo.<br />
Participer aux groupes de travail.<br />
<br />
Il y a un travail à faire sur "Comment les gens souhaitent devenir bénévoles peuvent s'impliquer dans les activités de l'association"<br />
Uniquement pendant les événements OSGO-fr et en représentation (POSS, Capitole du Libre, FOSSDEM) ?<br />
Autres activités ?<br />
<br />
=== Vincent Privat ===<br />
Core developper de JOSM, pourrait aider à maintenir JOSM au sein d'OsgeoLive<br />
<br />
=== Alban Kraus ===<br />
Géomaticien Agglo de Tulle : géomatique libre en collectivité territoriale au FOSS4G 2020 ?<br />
Invité à rejoindre la mailing list francophone<br />
<br />
=== Contributeurs OSM toulousains ===<br />
Vincent, Sébastien<br />
<br />
=== Pistes d'améliorations ===<br />
<br />
1. poster avec les projets OSGeo (Nom + logos)<br />
2. affiche avec les prochains événements<br />
3. plaquettes de présentation de l'OSGeo</div>Bakanikohttps://wiki.osgeo.org/w/index.php?title=Capitole_du_libre_2018&diff=118119Capitole du libre 20182018-11-19T19:36:01Z<p>Bakaniko: Created page with "OSGeo-fr summary of Capitole du Libre 2018 event at Toulouse (in French) = Capitole du Libre = Date: 17 et 18 décembre 2018 == Bénévoles présents == 1. Damien Despres 2...."</p>
<hr />
<div>OSGeo-fr summary of Capitole du Libre 2018 event at Toulouse (in French)<br />
<br />
= Capitole du Libre =<br />
Date: 17 et 18 décembre 2018<br />
<br />
== Bénévoles présents ==<br />
1. Damien Despres<br />
2. Anne Quesnel<br />
3. Manuel Grizonnet<br />
4. Nicolas Roelandt<br />
<br />
== Description de l'événement ==<br />
<br />
* Sur deux jours, le weekend du 17 et 18 novembre 2018<br />
* 1600 visiteurs le samedi, 700 visiteurs le dimanche (comptage organisateurs)<br />
* village associatif avec 26 stands<br />
* 118 speakers, 95 conférences, 25 ateliers<br />
<br />
== Rôle de l'OSGeo-fr ==<br />
* Tenir un stand en companie d'OSM France<br />
* Renseigner les curieux sur la géomatique et les outils géomatiques libres<br />
* Faire des démos courtes sur les outils (QGIS, OSGeoLive, PostGIS), les standards et protocoles (WMTS avec OSM, librairies GDAL/OGR), <br />
l'éducation (tutoriels OSGeoLive) et les données libres (Natural Earth, OSM, fichiers IGN en licence ouverte) en géomatique<br />
<br />
== Visiteurs comptabilisés au stand ==<br />
* samedi: 33 personnes<br />
* dimanche : 17 personnes<br />
<br />
Soit un total de 50 personnes. Beaucoup venaient voir OSM, certains avaient quand même des problématiques<br />
géospatiales ou été curieux / intéressé par l'OSGeo et les FOSS4G.<br />
<br />
== Goodies ==<br />
<br />
Damien a réceptionné chez lui les goodies suivants:<br />
- autocollants OSGeo francophone<br />
- Totem OSGeo-fr<br />
- Colis OSGeo marketing: stickers QGIS, OSM; cartes postales OSGeoLive<br />
<br />
Nous remercions Damien d'avoir accepté de les recevoir à son domicile.<br />
Les stickers ont été distribués en partie, la majorité remonte à Paris avec NR pour le POSS en décembre 2018.<br />
<br />
<br />
== Contacts ==<br />
=== Pierre Vrot ===<br />
=> Géomaticien toulousain qui cherche à s'impliquer dans les activités de l'association.<br />
Invité à se faire connaître sur la liste francophone et éventuellement rejoindre un projet OSGeo.<br />
Participer aux groupes de travail.<br />
<br />
Il y a un travail à faire sur "Comment les gens souhaitent devenir bénévoles peuvent s'impliquer dans les activités de l'association"<br />
Uniquement pendant les événements OSGO-fr et en représentation (POSS, Capitole du Libre, FOSSDEM) ?<br />
Autres activités ?<br />
<br />
=== Vincent Privat ===<br />
Core developper de JOSM, pourrait aider à maintenir JOSM au sein d'OsgeoLive<br />
<br />
=== Alban Kraus ===<br />
Géomaticien Agglo de Tulle : géomatique libre en collectivité territoriale au FOSS4G 2020 ?<br />
Invité à rejoindre la mailing list francophone<br />
<br />
=== Contributeurs OSM toulousains ===<br />
Vincent, Sébastien<br />
<br />
=== Pistes d'améliorations ===<br />
<br />
1. poster avec les projets OSGeo (Nom + logos)<br />
2. affiche avec les prochains événements<br />
3. plaquettes de présentation de l'OSGeo</div>Bakanikohttps://wiki.osgeo.org/w/index.php?title=User:Bakaniko&diff=117523User:Bakaniko2018-10-30T17:01:06Z<p>Bakaniko: </p>
<hr />
<div>{{OSGeo Member<br />
|Name=Nicolas Roelandt<br />
|JobTitle=GIS Engineer<br />
|Company=IFSTTAR<br />
|Country=France<br />
|City=Marne-la-Vallée<br />
|Coordinate=48.842298, 2.587371<br />
|LocalChapter=Francophone OSGeo Chapter<br />
|SocialMedia=Roelandtn42 (twitter);<br />
|Photo=nicolas_roelandt.jpg<br />
|Languages=French; English;<br />
|languages=French, English<br />
\<br />
}}<br />
{{OSGeo Experience<br />
|User=Yes<br />
|Committee=No<br />
|Board=No<br />
|Coder=No<br />
|Translate=Yes<br />
|PSC=Yes<br />
|ExBoard=No<br />
|Charter=Yes<br />
|Chair=No<br />
|SolKatz=No<br />
|Committer=No<br />
}}<br />
GIS user and FOSS hactivist, i combined both by joining the French chapter of OSGeo.<br />
I also join the OSGeo-Live PSC and participated to the organization of FOSS4G-fr 2016 and FOSS4G-EU 2017.<br />
<br />
<br />
<br />
[[Category:OSGeo_Advocate]]</div>Bakanikohttps://wiki.osgeo.org/w/index.php?title=Board-fr_election_2018&diff=116738Board-fr election 20182018-09-26T18:57:46Z<p>Bakaniko: /* Personnes candidates */</p>
<hr />
<div>= Election du Bureau OSGeo-fr 2018 =<br />
<br />
== Personnes candidates ==<br />
<br />
Par fonction avec la date de la déclaration<br />
<br />
* Trésorier : <br />
* Président : xxx le jj mm<br />
* Secrétaire : xxx le jj mm<br />
* Responsable communication xxx le jj mm<br />
* Responsable infrastructure : xxx le jj mm<br />
<br />
Régis Haubourg le 25 septembre<br />
<br />
Nicolas Roelandt le 26 septembre 2018<br />
<br />
== Programmes des candidats ==<br />
<br />
=== Régis Haubourg ===<br />
<br />
Agronome, Administrateur de données pendant 11 ans pour un établissement public, passionné de géomatique, ma vie professionnelle a basculé à 100% vers l'Open Source depuis 2016. <br />
Très impliqué dans le projet QGIS, grand fan de PostgreSQL, et charter member de l'OSGEO, j'ai participé à mon premier FOSS4G international en 2018 à Dar-es-Salaam. Ce évènement et cette communauté mondiale m'a réellement touché, autant par son dynamisme, l'appui au développement dans le monde qu'elle permet, que par sa capacité à inclure la diversité. <br />
<br />
En deux mots, mes ambitions pour l'OSGEO-fr sont:<br />
<br />
- Donner un coup de main ! <br />
- Œuvrer à la refonte des statuts pour accepter les personnes morales<br />
- Au passage permettre la collecte d'adhésion fournissant un budget plus important pour appuyer les événements OSGEO-fr, financer les projets OSGEO et les différentes initiatives <br />
- Structurer l'OSGEO pour qu'elle puisse héberger des groupes d'intérêt "Utilisateur"<br />
- Mettre en œuvre des règles de gouvernance démocratiques permettant aux membres de piloter l'utilisation des budgets et ressources de l'OSGEO. Il y a pas mal de challenges sur le montage, autour des règles de conduites pour éviter les conflits d'intérêt, éviter une distorsion entre grand, petits acteurs et individus, mais aussi sur les risques de dispersion entre toutes les communautés sous-jacentes. Mais si les autres y arrivent, ça devrait l'faire!<br />
- Recruter des adhérent(e)s ! <br />
[http://Mon%20CV%20OSGEO https://wiki.osgeo.org/wiki/User:Rhaubourg]<br />
<br />
=== Nicolas Roelandt ===<br />
<br />
Secrétaire adjoint de l'OSGeo-fr depuis 1 an, je me suis investi dans les actions de l'association depuis 2016 en participant à l'organisation des FOSS4G et en représentant l'association au Paris Open Source Summit. Je suis au Charter Member de l'OSGeo depuis 2017, et au comité de pilotage d'OSGeoLive depuis 2016.<br />
<br />
Les grands chantiers pour les années à venir sont la refonte des statuts pour accueillir des personnes morales et aussi de continuer à recruter des volontaires et à les impliquer dans la vie de l'association. J'entends bien participer à ces chantiers et y faire ma part.<br />
<br />
Au delà des fonctions de secrétaire, j'aimerai pouvoir donner la main pour le suivi de l'infrastructure (du site et des services) voire en développer de nouveaux (nextcloud et mattermost notamment).<br />
<br />
<br />
[[Category: Local chapter francophone]]</div>Bakanikohttps://wiki.osgeo.org/w/index.php?title=Board-fr_election_2018&diff=116737Board-fr election 20182018-09-26T18:49:28Z<p>Bakaniko: /* Programmes des candidats */</p>
<hr />
<div>= Election du Bureau OSGeo-fr 2018 =<br />
<br />
== Personnes candidates ==<br />
<br />
Par fonction avec la date de la déclaration<br />
<br />
* Trésorier : <br />
* Président : xxx le jj mm<br />
* Secrétaire : xxx le jj mm<br />
* Responsable communication xxx le jj mm<br />
* Responsable infrastructure : xxx le jj mm<br />
<br />
Régis Haubourg le 25 septembre<br />
Nicolas Roelandt le 26 septembre 2018<br />
<br />
== Programmes des candidats ==<br />
<br />
=== Régis Haubourg ===<br />
<br />
Agronome, Administrateur de données pendant 11 ans pour un établissement public, passionné de géomatique, ma vie professionnelle a basculé à 100% vers l'Open Source depuis 2016. <br />
Très impliqué dans le projet QGIS, grand fan de PostgreSQL, et charter member de l'OSGEO, j'ai participé à mon premier FOSS4G international en 2018 à Dar-es-Salaam. Ce évènement et cette communauté mondiale m'a réellement touché, autant par son dynamisme, l'appui au développement dans le monde qu'elle permet, que par sa capacité à inclure la diversité. <br />
<br />
En deux mots, mes ambitions pour l'OSGEO-fr sont:<br />
<br />
- Donner un coup de main ! <br />
- Œuvrer à la refonte des statuts pour accepter les personnes morales<br />
- Au passage permettre la collecte d'adhésion fournissant un budget plus important pour appuyer les événements OSGEO-fr, financer les projets OSGEO et les différentes initiatives <br />
- Structurer l'OSGEO pour qu'elle puisse héberger des groupes d'intérêt "Utilisateur"<br />
- Mettre en œuvre des règles de gouvernance démocratiques permettant aux membres de piloter l'utilisation des budgets et ressources de l'OSGEO. Il y a pas mal de challenges sur le montage, autour des règles de conduites pour éviter les conflits d'intérêt, éviter une distorsion entre grand, petits acteurs et individus, mais aussi sur les risques de dispersion entre toutes les communautés sous-jacentes. Mais si les autres y arrivent, ça devrait l'faire!<br />
- Recruter des adhérent(e)s ! <br />
[http://Mon%20CV%20OSGEO https://wiki.osgeo.org/wiki/User:Rhaubourg]<br />
<br />
=== Nicolas Roelandt ===<br />
<br />
Secrétaire adjoint de l'OSGeo-fr depuis 1 an, je me suis investi dans les actions de l'association depuis 2016 en participant à l'organisation des FOSS4G et en représentant l'association au Paris Open Source Summit. Je suis au Charter Member de l'OSGeo depuis 2017, et au comité de pilotage d'OSGeoLive depuis 2016.<br />
<br />
Les grands chantiers pour les années à venir sont la refonte des statuts pour accueillir des personnes morales et aussi de continuer à recruter des volontaires et à les impliquer dans la vie de l'association. J'entends bien participer à ces chantiers et y faire ma part.<br />
<br />
Au delà des fonctions de secrétaire, j'aimerai pouvoir donner la main pour le suivi de l'infrastructure (du site et des services) voire en développer de nouveaux (nextcloud et mattermost notamment).<br />
<br />
<br />
[[Category: Local chapter francophone]]</div>Bakanikohttps://wiki.osgeo.org/w/index.php?title=Board-fr_election_2018&diff=116736Board-fr election 20182018-09-26T18:27:54Z<p>Bakaniko: /* Personnes candidates */</p>
<hr />
<div>= Election du Bureau OSGeo-fr 2018 =<br />
<br />
== Personnes candidates ==<br />
<br />
Par fonction avec la date de la déclaration<br />
<br />
* Trésorier : <br />
* Président : xxx le jj mm<br />
* Secrétaire : xxx le jj mm<br />
* Responsable communication xxx le jj mm<br />
* Responsable infrastructure : xxx le jj mm<br />
<br />
Régis Haubourg le 25 septembre<br />
Nicolas Roelandt le 26 septembre 2018<br />
<br />
== Programmes des candidats ==<br />
<br />
=== Régis Haubourg ===<br />
<br />
Agronome, Administrateur de données pendant 11 ans pour un établissement public, passionné de géomatique, ma vie professionnelle a basculé à 100% vers l'Open Source depuis 2016. <br />
Très impliqué dans le projet QGIS, grand fan de PostgreSQL, et charter member de l'OSGEO, j'ai participé à mon premier FOSS4G international en 2018 à Dar-es-Salaam. Ce évènement et cette communauté mondiale m'a réellement touché, autant par son dynamisme, l'appui au développement dans le monde qu'elle permet, que par sa capacité à inclure la diversité. <br />
<br />
En deux mots, mes ambitions pour l'OSGEO-fr sont:<br />
<br />
- Donner un coup de main ! <br />
- Œuvrer à la refonte des statuts pour accepter les personnes morales<br />
- Au passage permettre la collecte d'adhésion fournissant un budget plus important pour appuyer les événements OSGEO-fr, financer les projets OSGEO et les différentes initiatives <br />
- Structurer l'OSGEO pour qu'elle puisse héberger des groupes d'intérêt "Utilisateur"<br />
- Mettre en œuvre des règles de gouvernance démocratiques permettant aux membres de piloter l'utilisation des budgets et ressources de l'OSGEO. Il y a pas mal de challenges sur le montage, autour des règles de conduites pour éviter les conflits d'intérêt, éviter une distorsion entre grand, petits acteurs et individus, mais aussi sur les risques de dispersion entre toutes les communautés sous-jacentes. Mais si les autres y arrivent, ça devrait l'faire!<br />
- Recruter des adhérent(e)s ! <br />
[http://Mon%20CV%20OSGEO https://wiki.osgeo.org/wiki/User:Rhaubourg]<br />
<br />
[[Category: Local chapter francophone]]</div>Bakanikohttps://wiki.osgeo.org/w/index.php?title=OSGeoLive_Translation_Process&diff=113846OSGeoLive Translation Process2018-02-28T20:26:07Z<p>Bakaniko: /* Build the documentation */</p>
<hr />
<div><br />
This document is divided in two part, if you want to help us translate the OSGeoLive documentation, the first part will guide you through the Transifex platform. If you want to help us build it the second part will give you more technical information about Transifex, sphinx and the building process.<br />
<br />
__FORCETOC__<br />
<br />
= Translate on Transifex =<br />
<br />
Thanks for helping us translate the OSGeoLive project documentation !<br />
<br />
You can find us there: [https://www.transifex.com/osgeo/osgeolive/]<br />
<br />
== Available languages ==<br />
<br />
As for now (february 2018), there is 18 registered languages for the project. <br />
If your language is not in the list below (or on the updated list on Transifex),<br />
please make a request to add it !<br />
<br />
<br />
The list of [https://www.transifex.com/osgeo/osgeolive/languages/ Languages]:<br />
<br />
* Bengali<br />
* Catalan<br />
* Dutch<br />
* Finnish<br />
* French<br />
* German<br />
* Greek<br />
* Hindi<br />
* Hungarian<br />
* Italian <br />
* Japanese<br />
* Polish<br />
* Portuguese<br />
* Russian<br />
* Spanish<br />
* Mexican spanish<br />
<br />
<br />
== Connect to the Transifex platform == <br />
<br />
If you don't have an account, please create one and then go to the project page.<br />
<br />
Look for the language you want to help with (or ask to add it if it is not there already).<br />
<br />
For each languages, there is a list of '''resources''', it is the files to translate (actually 180 of them).<br />
<br />
[[File: Language resources.png | 600px ]]<br />
<br />
== Files to translate ==<br />
The list of [https://www.transifex.com/osgeo/osgeolive/content/ resources]<br />
are classified as:<br />
* ">>" Urgent - OSGeo-Live related files<br />
<br />
[[File: OSGEo-Live_transifex_01_index.png | 600px ]]<br />
<br />
* "^" High - Projects related files<br />
<br />
[[File: OSGEo-Live_transifex_02_second_priority.png | 600px ]]<br />
<br />
* "-" Normal - Deprecated projects files (not for translating)<br />
<br />
[[File: OSGEo-Live_transifex_03_retired_files.png | 600px ]]<br />
<br />
You can easily order them by Version (v11) and and descending priority<br />
<br />
[[File : OSGEo-Live_transifex_04_priority.png | 600px ]]<br />
<br />
Please note that the urgent files are the OSGeoLive project files, if you <br />
are more comfortable translating only the files of a project provided by OSGeoLive,<br />
it is perfectly ok. :)<br />
<br />
Please note each project has 2 files:<br />
* an overview prefixed with ''overview--<name of the project>''<br />
* a quickstart prefixed with ''quickstart--<name of the project>''<br />
<br />
== Translation ==<br />
<br />
Once you have choose a file to translate, a little summary appears:<br />
<br />
[[File : OsgeoLive translation choosen file.png | 600px ]]<br />
<br />
1. The choosen resource and the language, here ''overview--overview (French)''<br />
2. Word count<br />
3. String count<br />
4. Translation button<br />
<br />
After clicking on the translation button, you access to the translation panels:<br />
<br />
[[File : OsgeoLive_translation_translatefile.png | 600px ]]<br />
<br />
1. String counts: Total, non translated, non revised<br />
2. Reviewed string<br />
3. Translated non reviewed string<br />
4. raw string (in English)<br />
5. Raw string to be translated<br />
6. Translation panel<br />
7. Translation save button<br />
8. Review button (if you are a reviewer)<br />
9. Suggestions panel (from past translations, by similarity)<br />
<br />
By clicking on a string in the left panel, it will be placed in the panel 5 and if possible a translation will be proposed in 6. You can edit this translation right from the panel 6 then save it by clicking on 7.<br />
<br />
You are an OSGeoLive translator ! Congratulations !<br />
<br />
Thanks for helping us !<br />
<br />
Now, you can translate another string then another, etc. And Then another file :)<br />
<br />
Welcome aboard !<br />
<br />
== Roles ==<br />
<br />
There is several roles where you can help us.<br />
<br />
=== Translator ===<br />
<br />
This role can translate strings, it is the most important job !<br />
<br />
=== Reviewer ===<br />
<br />
If your a confident enough in your language and technical knowledge, you can become <br />
a reviewer and review strings to fix the possible typos. <br />
<br />
=== Language coordinator ===<br />
<br />
A coordinator can accept new Translator and grant Reviewer privileges. With a lot of different languages, <br />
it helps a lot the administrator.<br />
<br />
<br />
= Build the documentation =<br />
== The general process OSGeo-Live used for documentation: ==<br />
<br />
This section is a work in progress, please excuse us.<br />
<br />
<br />
<ul><br />
<li>The developer use [http://docutils.sourceforge.net/docs/user/rst/quickstart.html ReStructuredText] syntax to write the documentation in English.</li><br />
<li>That documentation is then used with [http://sphinx-doc.org/contents.html Sphinx] to generate the english html, man, pdf, etc.</li><br />
<li>Also using [http://sphinx-doc.org/latest/intl.html Sphinx-intl] the <code>*.pot</code> files are generated.</li><br />
<li>Those <code>*.pot</code> files are used by [https://www.transifex.com/osgeo/osgeolive Transifex] and they contain only the strings that need to be translated.</li><br />
<li>Translator works with those strings using the process bellow.</li><br />
<li>When the translator finishes a language, the git hub mantainers proceed to download the generated <code>*.po</code> files that contain the translated strings and commit them in git hub and update the documentation page.</li><br />
<li><p>Users can create their translation using:</p><br />
<p>tools/transifex/create_translation.sh fr</p></li></ul><br />
<br />
Translations to French are going to be used as examples along this wiki, we choose French so you can focus on what is being translated and what is not.<br />
<br />
== Before you start ==<br />
<br />
=== Prepare your clone for documentation ===<br />
<br />
<pre><br />
## Prepare the directory<br />
git clone https://github.com/OSGeo/OSGeoLive-doc docClone<br />
cd docClone<br />
git checkout develop ## new things come into develop, then are merged into master<br />
mkdir build<br />
cd build<br />
<br />
## prepare the documentation for French (English is automatically build)<br />
cmake -DHTML=ON -DFR=ON .. <br />
## Build the doc<br />
make doc<br />
cd ..</pre><br />
<br />
=== Downloading translation ===<br />
<br />
* To download a particular file.<br />
<br />
Best when reviewing the file:<br />
<br />
<pre><br />
tx pull -l fr -r osgeolive.quickstart--ideditor_quickstart<br />
</pre><br />
<br />
* Download the latest translated <code>*.po</code> files of your language based on translation percentage.<br />
<br />
<pre><br />
tx pull -l fr --minimum-perc=100<br />
</pre><br />
<br />
<br />
* Ask for help:<br />
<br />
<pre><br />
tx pull --help<br />
</pre><br />
<br />
==== Checking the download ====<br />
<br />
<pre><br />
git status<br />
</pre><br />
<br />
A possible output:<br />
<br />
=== Have your language documentation html open. ===<br />
<br />
Viewing your language html will help to put strings in context and/or check the translation.<br />
<br />
<pre>tools/transifex/create_translations.sh fr</pre><br />
The French documentation would be in<br />
<br />
<pre>build/doc/html/fr/doc/index.html</pre><br />
<br />
=== Transifex files that are not accepting translations. ===<br />
<br />
Files not accepting translations are marked with a red dot, maybe the file belongs to a previous version of OSGeo-Live documentation, or it was moved from one directory to another. Those files are not erased from the system so any translated string can be reused.<br />
<br />
=== English spelling and grammar ===<br />
<br />
Sometimes the developers and the reviewers have typos in the English version, you will see spelling typos with a wavy red line, unfortunately it is too late to correct them for the current version. So proceed with the translation with the best of your ability. For the grammar, if you don't understand what is being told, please go to [https://github.com/pgRouting/pgrouting/issues/200 issue 200] to post a comment stating the file and pasting the English string. If a change has been considered, the string to be translated will be posted on the &quot;instructions&quot; for the string.<br />
<br />
== Working with small strings ==<br />
<br />
=== Choose the small files first. ===<br />
<br />
For &quot;small&quot; I mean the ones that have very few strings to be translated. That will start building up a bank of translated strings that can be used in larger files. To detect a &quot;small&quot; file go to the list of [resources] (https://www.transifex.com/projects/p/pgrouting/resources/) and choose a file with few words or few strings.<br />
<br />
=== Use &quot;translate&quot; button ===<br />
<br />
The &quot;translate button&quot; comes quite handy, you still have to check the translation, and there is an &quot;undo&quot; button if you think that its better for you to type the translation than to modify the machine's translation.<br />
<br />
Don't use &quot;translate&quot; button on stand alone references like<br />
<br />
<pre>en: :ref:`sample`<br />
ja: :ref:`サンプル` &lt;--- wrong</pre><br />
=== Use a &quot;suggestion&quot; ===<br />
<br />
When you work with transifex it builds up a translated string bank and it will show one or more suggestions. If the suggestion is very close to what is needed, use it, and change the translation to the final translation of the string. Example:<br />
<br />
<pre>en: :ref:`pgr_astar&lt;pgr_astar&gt;` - Shortest Path A*<br />
Use suggestion: pgr_astar - A*アルゴリズムを用いた最短経路探索<br />
Modify to: :ref:`pgr_astar&lt;pgr_astar&gt;` - A*アルゴリズムを用いた最短経路探索</pre><br />
=== Use &quot;copy button&quot; ===<br />
<br />
Copy the the stand alone references like<br />
<br />
<pre>en: :ref:`sample`<br />
ja: :ref:`sample`</pre><br />
=== Type a translation ===<br />
<br />
You can just type your translation.<br />
<br />
=== Go to the next string ===<br />
<br />
When you finished translating the string press &quot;tab&quot;, that way it get's saved, if you click to a different string, maybe because the next string is already translated, then it won't be saved (green/white stripes).<br />
<br />
=== Save your translation ===<br />
<br />
Make sure all strings using the &quot;Save all unsaved translations&quot; button.<br />
<br />
== Check your work ==<br />
<br />
This step is needed not to check the translation but to check that ReStructuredText in the translated strings is correct. Many things might be wrong, an extra space, a missing space or a missing character &quot;`&quot; .<br />
<br />
=== Download the translated file and recreate the translation ===<br />
<br />
If the file you modified in transifex is doc--src--changelog--index and want to check the Japanese translation<br />
<br />
<pre>tools/transifex/download_translation.sh ja pgrouting.doc--src--changelog--index<br />
tools/transifex/create_translations.sh ja</pre><br />
Navigate to the the translated file, for this example it would be<br />
<br />
<pre>build/doc/html/ja/doc/src/changelog/index.html</pre><br />
Notice the relation between names:<br />
<br />
<pre>Transifex name: pgrouting.doc--src--changelog--index<br />
Html Generated File: build/doc/html/ja/doc/src/changelog/index.html</pre><br />
And visualy compare the &quot;looks&quot; with the [English version] (http://docs.pgrouting.org/2.0/en/doc/index.html)<br />
<br />
=== Use the &quot;Approve translation&quot; button ===<br />
<br />
When the file is fully translated (except the navigation bar), you can are about to approve the translation, '''????????'''<br />
<br />
* Check the links first, example: there is a link to sample data.<br />
<br />
Example:<br />
<br />
<pre>html: 上記クエリは サンプルデータ のネットワークを使用しています。 &lt;-- sample data is translated<br />
or: 上記クエリは Sample Data のネットワークを使用しています。 &lt;--- sample data needs translation</pre><br />
If you can navigate the links, you are ok<br />
<br />
* When using create_translation script there was no &quot;inline&quot; error (see [[Translation Troubleshooting]] ), you are ok<br />
<br />
If you are ok, then choose a string and click the &quot;Approve translation&quot; button.<br />
<br />
== Which file is next ==<br />
<br />
=== Do doc--index last ===<br />
<br />
That way you can use the &quot;Use suggestion&quot; in this file.<br />
<br />
=== Work &quot;important&quot; files first ===<br />
<br />
All files are important, but the following files are the core of the project. Most of them have repeated strings, so the &quot;Use Suggestion&quot; tactic is perfect, and you can use the search box to find them.<br />
<br />
- your project files: you know that project certainly better than us, especially in your language; starting by the overview then the quickstart<br />
- OSGeoLive files: there is several core files for the OSgeoLive documentation:<br />
- index<br />
- overview--overview<br />
- overview--toc<br />
- quickstart--virtualization_quickstart<br />
- quickstart--usb_quickstart<br />
- quickstart--osgeolive_quickstart<br />
- copyright<br />
- contributors<br />
- translators<br />
- presentation<br />
- sponsors<br />
<br />
etc<br />
<br />
They are listed with a red double ">" priority sign<br />
<br />
=== Work the &quot;almost finished&quot; files ===<br />
<br />
After you finish a file, you can choose a file that is &quot;almost done&quot;. I found pretty uncomfortable the list placed at the left, so to choose an almost done file I recommend:<br />
<br />
* Click Documentation<br />
* Click on your language<br />
* click on the sorting button (sorts by % of termination)<br />
<br />
This is very useful when you have a lot of files already translated<br />
<br />
=== Work files that belong to a directory ===<br />
<br />
Based on the following files:<br />
<br />
* doc--src--changelog--1_x ... 150 words (25 strings) ...<br />
* doc--src--changelog--2_0 ... 277 words (26 strings) ...<br />
* doc--src--changelog--index ... 4 words (3 strings) ...<br />
<br />
Maybe you started working with doc--src--changelog--index, so the next step would be to work with<br />
<br />
* doc--src--changelog--1_x<br />
* doc--src--changelog--2_0<br />
<br />
So you finished a section, go [[Translation Check your work]].<br />
<br />
= Troubleshooting =<br />
<br />
Please post any question in [https://github.com/pgRouting/pgrouting/issues/200 issue 200]<br />
<br />
=== The :ref:`nameoflink` link is not translated ===<br />
<br />
Example<br />
<br />
<pre>en: The queries use the :ref:`sampledata` network.<br />
ja: 上記クエリは :ref:`sampledata` のネットワークを使用しています。 <br />
html: 上記クエリは Sample Data のネットワークを使用しています。</pre><br />
Thats and indication that the referenced page for Sample Data, isn't fully translated. If you can click on the link and navigate you are ok.<br />
<br />
=== The :ref:`nameoflink` link is the only thing that is translated ===<br />
<br />
Example<br />
<br />
<pre>en: The queries use the :ref:`sampledata` network.<br />
ja: The queries use the :ref:`sampledata` network.<br />
html: The queries use the サンプルデータ network.</pre><br />
Maybe you navigated into an untranslated page that has a reference to a translated page.<br />
<br />
=== I don't see the link but I can read :ref: in the html page ===<br />
<br />
This is a common problem when using the translation button.<br /><br />
Example<br />
<br />
<pre>en: The queries use the :ref:`sampledata` network.<br />
ja: 上記クエリは: ref:'sampledata'のネットワークを使用しています。 <br />
html: 上記クエリは: ref:'sampledata'のネットワークを使用しています。</pre><br />
The link's generated by the button need to be corrected, I suggest to copy the link together with its sorrounding spaces from the English version:<br />
<br />
<pre> -------------------<br />
en: The queries use the :ref:`sampledata` network.<br />
ja: 上記クエリは :ref:`sampledata` のネットワークを使用しています。 <br />
html: 上記クエリは サンプルデータ のネットワークを使用しています。<br />
or: 上記クエリは Sample Data のネットワークを使用しています。</pre><br />
<br />
=== WARNING: Inline literal start-string without end-string. ===<br />
<br />
You will get this error is when using ''tools/transifex/create_translations.sh''. Languages like Japanese that don't use spaces to separate words are more likely to have this error. Unfortunately the error is shown only in line 1.<br />
<br />
Inline literals [specs] (http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#inline-markup) require a space before and after. The inline literals we use the most are of the type ``inlineliteral`` like in:<br />
<br />
<pre>``int4`` id of the end point<br />
``int4``型の始点ノードのID &lt;--- this will generate the error<br />
``int4 `` 型の始点ノードのID &lt;--- this will also generate the error (a space is after the 4)<br />
``int4`` 型の始点ノードのID &lt;--- a space is (before as a new line and) after the inline literal</pre><br />
= Tools for the Reviewer =<br />
<br />
=== tools/transifex/download_translation.sh ===<br />
<br />
Use to update the <code>*.po</code> files that are in your system with the latest translation stored in Transifex.<br /><br />
Languages available:<br />
<br />
* es - Spanish<br />
* fr - French<br />
* ja - Japanese<br />
* de - German<br />
<br />
tools/transifex/download_translation.sh [es|ja|fr|de] [pgrouting.&lt;filename&gt;]<br />
<br />
To download all language translations:<br />
<br />
<pre>tools/transifex/download_translation.sh</pre><br />
To download all the translations of a particular language:<br />
<br />
<pre>tools/transifex/download_translation.sh [es|ja|fr|de]</pre><br />
To download the translation of a specific file you need to state the language also<br />
<br />
<pre>tools/transifex/download_translation.sh [es|ja|fr|de] [pgrouting.&lt;filename&gt;]</pre><br />
<br />
=== tools/transifex/create_translations.sh ===<br />
<br />
Use to create: html, man, pdf documentation of the languages based on the <code>*.po</code> files stored in your system. Languages available:<br />
<br />
* es - Spanish<br />
* fr - French<br />
* ja - Japanese<br />
* de - German<br />
<br />
To create the documentation of all the languages<br />
<br />
<pre>tools/transifex/create_translations.sh</pre><br />
To create the documentation of a particular language:<br />
<br />
<pre>tools/transifex/create_translations.sh [es|ja|fr|de]</pre><br />
The main index.html of the documentation will be located at:<br />
<br />
<pre>build/doc/html/[es|ja|fr|de]/doc/index.html</pre><br />
<br />
= Main wiki page =<br />
<br />
* [https://wiki.osgeo.org/wiki/OSGeoLive OSGeoLive Wiki]<br />
<br />
<br />
[[Category: OSGeoLive]]</div>Bakanikohttps://wiki.osgeo.org/w/index.php?title=OSGeoLive_Translation_Process&diff=113845OSGeoLive Translation Process2018-02-28T20:24:32Z<p>Bakaniko: </p>
<hr />
<div><br />
This document is divided in two part, if you want to help us translate the OSGeoLive documentation, the first part will guide you through the Transifex platform. If you want to help us build it the second part will give you more technical information about Transifex, sphinx and the building process.<br />
<br />
__FORCETOC__<br />
<br />
= Translate on Transifex =<br />
<br />
Thanks for helping us translate the OSGeoLive project documentation !<br />
<br />
You can find us there: [https://www.transifex.com/osgeo/osgeolive/]<br />
<br />
== Available languages ==<br />
<br />
As for now (february 2018), there is 18 registered languages for the project. <br />
If your language is not in the list below (or on the updated list on Transifex),<br />
please make a request to add it !<br />
<br />
<br />
The list of [https://www.transifex.com/osgeo/osgeolive/languages/ Languages]:<br />
<br />
* Bengali<br />
* Catalan<br />
* Dutch<br />
* Finnish<br />
* French<br />
* German<br />
* Greek<br />
* Hindi<br />
* Hungarian<br />
* Italian <br />
* Japanese<br />
* Polish<br />
* Portuguese<br />
* Russian<br />
* Spanish<br />
* Mexican spanish<br />
<br />
<br />
== Connect to the Transifex platform == <br />
<br />
If you don't have an account, please create one and then go to the project page.<br />
<br />
Look for the language you want to help with (or ask to add it if it is not there already).<br />
<br />
For each languages, there is a list of '''resources''', it is the files to translate (actually 180 of them).<br />
<br />
[[File: Language resources.png | 600px ]]<br />
<br />
== Files to translate ==<br />
The list of [https://www.transifex.com/osgeo/osgeolive/content/ resources]<br />
are classified as:<br />
* ">>" Urgent - OSGeo-Live related files<br />
<br />
[[File: OSGEo-Live_transifex_01_index.png | 600px ]]<br />
<br />
* "^" High - Projects related files<br />
<br />
[[File: OSGEo-Live_transifex_02_second_priority.png | 600px ]]<br />
<br />
* "-" Normal - Deprecated projects files (not for translating)<br />
<br />
[[File: OSGEo-Live_transifex_03_retired_files.png | 600px ]]<br />
<br />
You can easily order them by Version (v11) and and descending priority<br />
<br />
[[File : OSGEo-Live_transifex_04_priority.png | 600px ]]<br />
<br />
Please note that the urgent files are the OSGeoLive project files, if you <br />
are more comfortable translating only the files of a project provided by OSGeoLive,<br />
it is perfectly ok. :)<br />
<br />
Please note each project has 2 files:<br />
* an overview prefixed with ''overview--<name of the project>''<br />
* a quickstart prefixed with ''quickstart--<name of the project>''<br />
<br />
== Translation ==<br />
<br />
Once you have choose a file to translate, a little summary appears:<br />
<br />
[[File : OsgeoLive translation choosen file.png | 600px ]]<br />
<br />
1. The choosen resource and the language, here ''overview--overview (French)''<br />
2. Word count<br />
3. String count<br />
4. Translation button<br />
<br />
After clicking on the translation button, you access to the translation panels:<br />
<br />
[[File : OsgeoLive_translation_translatefile.png | 600px ]]<br />
<br />
1. String counts: Total, non translated, non revised<br />
2. Reviewed string<br />
3. Translated non reviewed string<br />
4. raw string (in English)<br />
5. Raw string to be translated<br />
6. Translation panel<br />
7. Translation save button<br />
8. Review button (if you are a reviewer)<br />
9. Suggestions panel (from past translations, by similarity)<br />
<br />
By clicking on a string in the left panel, it will be placed in the panel 5 and if possible a translation will be proposed in 6. You can edit this translation right from the panel 6 then save it by clicking on 7.<br />
<br />
You are an OSGeoLive translator ! Congratulations !<br />
<br />
Thanks for helping us !<br />
<br />
Now, you can translate another string then another, etc. And Then another file :)<br />
<br />
Welcome aboard !<br />
<br />
== Roles ==<br />
<br />
There is several roles where you can help us.<br />
<br />
=== Translator ===<br />
<br />
This role can translate strings, it is the most important job !<br />
<br />
=== Reviewer ===<br />
<br />
If your a confident enough in your language and technical knowledge, you can become <br />
a reviewer and review strings to fix the possible typos. <br />
<br />
=== Language coordinator ===<br />
<br />
A coordinator can accept new Translator and grant Reviewer privileges. With a lot of different languages, <br />
it helps a lot the administrator.<br />
<br />
<br />
= Build the documentation =<br />
== The general process OSGeo-Live used for documentation: ==<br />
<br />
<ul><br />
<li>The developer use [http://docutils.sourceforge.net/docs/user/rst/quickstart.html ReStructuredText] syntax to write the documentation in English.</li><br />
<li>That documentation is then used with [http://sphinx-doc.org/contents.html Sphinx] to generate the english html, man, pdf, etc.</li><br />
<li>Also using [http://sphinx-doc.org/latest/intl.html Sphinx-intl] the <code>*.pot</code> files are generated.</li><br />
<li>Those <code>*.pot</code> files are used by [https://www.transifex.com/osgeo/osgeolive Transifex] and they contain only the strings that need to be translated.</li><br />
<li>Translator works with those strings using the process bellow.</li><br />
<li>When the translator finishes a language, the git hub mantainers proceed to download the generated <code>*.po</code> files that contain the translated strings and commit them in git hub and update the documentation page.</li><br />
<li><p>Users can create their translation using:</p><br />
<p>tools/transifex/create_translation.sh fr</p></li></ul><br />
<br />
Translations to French are going to be used as examples along this wiki, we choose French so you can focus on what is being translated and what is not.<br />
<br />
== Before you start ==<br />
<br />
=== Prepare your clone for documentation ===<br />
<br />
<pre><br />
## Prepare the directory<br />
git clone https://github.com/OSGeo/OSGeoLive-doc docClone<br />
cd docClone<br />
git checkout develop ## new things come into develop, then are merged into master<br />
mkdir build<br />
cd build<br />
<br />
## prepare the documentation for French (English is automatically build)<br />
cmake -DHTML=ON -DFR=ON .. <br />
## Build the doc<br />
make doc<br />
cd ..</pre><br />
<br />
=== Downloading translation ===<br />
<br />
* To download a particular file.<br />
<br />
Best when reviewing the file:<br />
<br />
<pre><br />
tx pull -l fr -r osgeolive.quickstart--ideditor_quickstart<br />
</pre><br />
<br />
* Download the latest translated <code>*.po</code> files of your language based on translation percentage.<br />
<br />
<pre><br />
tx pull -l fr --minimum-perc=100<br />
</pre><br />
<br />
<br />
* Ask for help:<br />
<br />
<pre><br />
tx pull --help<br />
</pre><br />
<br />
==== Checking the download ====<br />
<br />
<pre><br />
git status<br />
</pre><br />
<br />
A possible output:<br />
<br />
=== Have your language documentation html open. ===<br />
<br />
Viewing your language html will help to put strings in context and/or check the translation.<br />
<br />
<pre>tools/transifex/create_translations.sh fr</pre><br />
The French documentation would be in<br />
<br />
<pre>build/doc/html/fr/doc/index.html</pre><br />
<br />
=== Transifex files that are not accepting translations. ===<br />
<br />
Files not accepting translations are marked with a red dot, maybe the file belongs to a previous version of OSGeo-Live documentation, or it was moved from one directory to another. Those files are not erased from the system so any translated string can be reused.<br />
<br />
=== English spelling and grammar ===<br />
<br />
Sometimes the developers and the reviewers have typos in the English version, you will see spelling typos with a wavy red line, unfortunately it is too late to correct them for the current version. So proceed with the translation with the best of your ability. For the grammar, if you don't understand what is being told, please go to [https://github.com/pgRouting/pgrouting/issues/200 issue 200] to post a comment stating the file and pasting the English string. If a change has been considered, the string to be translated will be posted on the &quot;instructions&quot; for the string.<br />
<br />
== Working with small strings ==<br />
<br />
=== Choose the small files first. ===<br />
<br />
For &quot;small&quot; I mean the ones that have very few strings to be translated. That will start building up a bank of translated strings that can be used in larger files. To detect a &quot;small&quot; file go to the list of [resources] (https://www.transifex.com/projects/p/pgrouting/resources/) and choose a file with few words or few strings.<br />
<br />
=== Use &quot;translate&quot; button ===<br />
<br />
The &quot;translate button&quot; comes quite handy, you still have to check the translation, and there is an &quot;undo&quot; button if you think that its better for you to type the translation than to modify the machine's translation.<br />
<br />
Don't use &quot;translate&quot; button on stand alone references like<br />
<br />
<pre>en: :ref:`sample`<br />
ja: :ref:`サンプル` &lt;--- wrong</pre><br />
=== Use a &quot;suggestion&quot; ===<br />
<br />
When you work with transifex it builds up a translated string bank and it will show one or more suggestions. If the suggestion is very close to what is needed, use it, and change the translation to the final translation of the string. Example:<br />
<br />
<pre>en: :ref:`pgr_astar&lt;pgr_astar&gt;` - Shortest Path A*<br />
Use suggestion: pgr_astar - A*アルゴリズムを用いた最短経路探索<br />
Modify to: :ref:`pgr_astar&lt;pgr_astar&gt;` - A*アルゴリズムを用いた最短経路探索</pre><br />
=== Use &quot;copy button&quot; ===<br />
<br />
Copy the the stand alone references like<br />
<br />
<pre>en: :ref:`sample`<br />
ja: :ref:`sample`</pre><br />
=== Type a translation ===<br />
<br />
You can just type your translation.<br />
<br />
=== Go to the next string ===<br />
<br />
When you finished translating the string press &quot;tab&quot;, that way it get's saved, if you click to a different string, maybe because the next string is already translated, then it won't be saved (green/white stripes).<br />
<br />
=== Save your translation ===<br />
<br />
Make sure all strings using the &quot;Save all unsaved translations&quot; button.<br />
<br />
== Check your work ==<br />
<br />
This step is needed not to check the translation but to check that ReStructuredText in the translated strings is correct. Many things might be wrong, an extra space, a missing space or a missing character &quot;`&quot; .<br />
<br />
=== Download the translated file and recreate the translation ===<br />
<br />
If the file you modified in transifex is doc--src--changelog--index and want to check the Japanese translation<br />
<br />
<pre>tools/transifex/download_translation.sh ja pgrouting.doc--src--changelog--index<br />
tools/transifex/create_translations.sh ja</pre><br />
Navigate to the the translated file, for this example it would be<br />
<br />
<pre>build/doc/html/ja/doc/src/changelog/index.html</pre><br />
Notice the relation between names:<br />
<br />
<pre>Transifex name: pgrouting.doc--src--changelog--index<br />
Html Generated File: build/doc/html/ja/doc/src/changelog/index.html</pre><br />
And visualy compare the &quot;looks&quot; with the [English version] (http://docs.pgrouting.org/2.0/en/doc/index.html)<br />
<br />
=== Use the &quot;Approve translation&quot; button ===<br />
<br />
When the file is fully translated (except the navigation bar), you can are about to approve the translation, '''????????'''<br />
<br />
* Check the links first, example: there is a link to sample data.<br />
<br />
Example:<br />
<br />
<pre>html: 上記クエリは サンプルデータ のネットワークを使用しています。 &lt;-- sample data is translated<br />
or: 上記クエリは Sample Data のネットワークを使用しています。 &lt;--- sample data needs translation</pre><br />
If you can navigate the links, you are ok<br />
<br />
* When using create_translation script there was no &quot;inline&quot; error (see [[Translation Troubleshooting]] ), you are ok<br />
<br />
If you are ok, then choose a string and click the &quot;Approve translation&quot; button.<br />
<br />
== Which file is next ==<br />
<br />
=== Do doc--index last ===<br />
<br />
That way you can use the &quot;Use suggestion&quot; in this file.<br />
<br />
=== Work &quot;important&quot; files first ===<br />
<br />
All files are important, but the following files are the core of the project. Most of them have repeated strings, so the &quot;Use Suggestion&quot; tactic is perfect, and you can use the search box to find them.<br />
<br />
- your project files: you know that project certainly better than us, especially in your language; starting by the overview then the quickstart<br />
- OSGeoLive files: there is several core files for the OSgeoLive documentation:<br />
- index<br />
- overview--overview<br />
- overview--toc<br />
- quickstart--virtualization_quickstart<br />
- quickstart--usb_quickstart<br />
- quickstart--osgeolive_quickstart<br />
- copyright<br />
- contributors<br />
- translators<br />
- presentation<br />
- sponsors<br />
<br />
etc<br />
<br />
They are listed with a red double ">" priority sign<br />
<br />
=== Work the &quot;almost finished&quot; files ===<br />
<br />
After you finish a file, you can choose a file that is &quot;almost done&quot;. I found pretty uncomfortable the list placed at the left, so to choose an almost done file I recommend:<br />
<br />
* Click Documentation<br />
* Click on your language<br />
* click on the sorting button (sorts by % of termination)<br />
<br />
This is very useful when you have a lot of files already translated<br />
<br />
=== Work files that belong to a directory ===<br />
<br />
Based on the following files:<br />
<br />
* doc--src--changelog--1_x ... 150 words (25 strings) ...<br />
* doc--src--changelog--2_0 ... 277 words (26 strings) ...<br />
* doc--src--changelog--index ... 4 words (3 strings) ...<br />
<br />
Maybe you started working with doc--src--changelog--index, so the next step would be to work with<br />
<br />
* doc--src--changelog--1_x<br />
* doc--src--changelog--2_0<br />
<br />
So you finished a section, go [[Translation Check your work]].<br />
<br />
= Troubleshooting =<br />
<br />
Please post any question in [https://github.com/pgRouting/pgrouting/issues/200 issue 200]<br />
<br />
=== The :ref:`nameoflink` link is not translated ===<br />
<br />
Example<br />
<br />
<pre>en: The queries use the :ref:`sampledata` network.<br />
ja: 上記クエリは :ref:`sampledata` のネットワークを使用しています。 <br />
html: 上記クエリは Sample Data のネットワークを使用しています。</pre><br />
Thats and indication that the referenced page for Sample Data, isn't fully translated. If you can click on the link and navigate you are ok.<br />
<br />
=== The :ref:`nameoflink` link is the only thing that is translated ===<br />
<br />
Example<br />
<br />
<pre>en: The queries use the :ref:`sampledata` network.<br />
ja: The queries use the :ref:`sampledata` network.<br />
html: The queries use the サンプルデータ network.</pre><br />
Maybe you navigated into an untranslated page that has a reference to a translated page.<br />
<br />
=== I don't see the link but I can read :ref: in the html page ===<br />
<br />
This is a common problem when using the translation button.<br /><br />
Example<br />
<br />
<pre>en: The queries use the :ref:`sampledata` network.<br />
ja: 上記クエリは: ref:'sampledata'のネットワークを使用しています。 <br />
html: 上記クエリは: ref:'sampledata'のネットワークを使用しています。</pre><br />
The link's generated by the button need to be corrected, I suggest to copy the link together with its sorrounding spaces from the English version:<br />
<br />
<pre> -------------------<br />
en: The queries use the :ref:`sampledata` network.<br />
ja: 上記クエリは :ref:`sampledata` のネットワークを使用しています。 <br />
html: 上記クエリは サンプルデータ のネットワークを使用しています。<br />
or: 上記クエリは Sample Data のネットワークを使用しています。</pre><br />
<br />
=== WARNING: Inline literal start-string without end-string. ===<br />
<br />
You will get this error is when using ''tools/transifex/create_translations.sh''. Languages like Japanese that don't use spaces to separate words are more likely to have this error. Unfortunately the error is shown only in line 1.<br />
<br />
Inline literals [specs] (http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#inline-markup) require a space before and after. The inline literals we use the most are of the type ``inlineliteral`` like in:<br />
<br />
<pre>``int4`` id of the end point<br />
``int4``型の始点ノードのID &lt;--- this will generate the error<br />
``int4 `` 型の始点ノードのID &lt;--- this will also generate the error (a space is after the 4)<br />
``int4`` 型の始点ノードのID &lt;--- a space is (before as a new line and) after the inline literal</pre><br />
= Tools for the Reviewer =<br />
<br />
=== tools/transifex/download_translation.sh ===<br />
<br />
Use to update the <code>*.po</code> files that are in your system with the latest translation stored in Transifex.<br /><br />
Languages available:<br />
<br />
* es - Spanish<br />
* fr - French<br />
* ja - Japanese<br />
* de - German<br />
<br />
tools/transifex/download_translation.sh [es|ja|fr|de] [pgrouting.&lt;filename&gt;]<br />
<br />
To download all language translations:<br />
<br />
<pre>tools/transifex/download_translation.sh</pre><br />
To download all the translations of a particular language:<br />
<br />
<pre>tools/transifex/download_translation.sh [es|ja|fr|de]</pre><br />
To download the translation of a specific file you need to state the language also<br />
<br />
<pre>tools/transifex/download_translation.sh [es|ja|fr|de] [pgrouting.&lt;filename&gt;]</pre><br />
<br />
=== tools/transifex/create_translations.sh ===<br />
<br />
Use to create: html, man, pdf documentation of the languages based on the <code>*.po</code> files stored in your system. Languages available:<br />
<br />
* es - Spanish<br />
* fr - French<br />
* ja - Japanese<br />
* de - German<br />
<br />
To create the documentation of all the languages<br />
<br />
<pre>tools/transifex/create_translations.sh</pre><br />
To create the documentation of a particular language:<br />
<br />
<pre>tools/transifex/create_translations.sh [es|ja|fr|de]</pre><br />
The main index.html of the documentation will be located at:<br />
<br />
<pre>build/doc/html/[es|ja|fr|de]/doc/index.html</pre><br />
<br />
= Main wiki page =<br />
<br />
* [https://wiki.osgeo.org/wiki/OSGeoLive OSGeoLive Wiki]<br />
<br />
<br />
[[Category: OSGeoLive]]</div>Bakanikohttps://wiki.osgeo.org/w/index.php?title=OSGeoLive_Translation_Process&diff=113844OSGeoLive Translation Process2018-02-28T20:10:11Z<p>Bakaniko: </p>
<hr />
<div><br />
This document is divided in two part, if you want to help us translate the OSGeoLive documentation, the first part will guide you through the Transifex platform. If you want to help us build it the second part will give you more technical information about Transifex, sphinx and the building process.<br />
<br />
__FORCETOC__<br />
<br />
= Translate on Transifex =<br />
<br />
Thanks for helping us translate the OSGeoLive project documentation !<br />
<br />
You can find us there: [https://www.transifex.com/osgeo/osgeolive/]<br />
<br />
== Available languages ==<br />
<br />
As for now (february 2018), there is 18 registered languages for the project. <br />
If your language is not in the list below (or on the updated list on Transifex),<br />
please make a request to add it !<br />
<br />
<br />
The list of [https://www.transifex.com/osgeo/osgeolive/languages/ Languages]:<br />
<br />
* Bengali<br />
* Catalan<br />
* Dutch<br />
* Finnish<br />
* French<br />
* German<br />
* Greek<br />
* Hindi<br />
* Hungarian<br />
* Italian <br />
* Japanese<br />
* Polish<br />
* Portuguese<br />
* Russian<br />
* Spanish<br />
* Mexican spanish<br />
<br />
<br />
== Connect to the Transifex platform == <br />
<br />
If you don't have an account, please create one and then go to the project page.<br />
<br />
Look for the language you want to help with (or ask to add it if it is not there already).<br />
<br />
For each languages, there is a list of '''resources''', it is the files to translate (actually 180 of them).<br />
<br />
[[File: Language resources.png | 600px ]]<br />
<br />
== Files to translate ==<br />
The list of [https://www.transifex.com/osgeo/osgeolive/content/ resources]<br />
are classified as:<br />
* ">>" Urgent - OSGeo-Live related files<br />
<br />
[[File: OSGEo-Live_transifex_01_index.png | 600px ]]<br />
<br />
* "^" High - Projects related files<br />
<br />
[[File: OSGEo-Live_transifex_02_second_priority.png | 600px ]]<br />
<br />
* "-" Normal - Deprecated projects files (not for translating)<br />
<br />
[[File: OSGEo-Live_transifex_03_retired_files.png | 600px ]]<br />
<br />
You can easily order them by Version (v11) and and descending priority<br />
<br />
[[File : OSGEo-Live_transifex_04_priority.png | 600px ]]<br />
<br />
Please note that the urgent files are the OSGeoLive project files, if you <br />
are more comfortable translating only the files of a project provided by OSGeoLive,<br />
it is perfectly ok. :)<br />
<br />
Please note each project has 2 files:<br />
* an overview prefixed with ''overview--<name of the project>''<br />
* a quickstart prefixed with ''quickstart--<name of the project>''<br />
<br />
== Translation ==<br />
<br />
Once you have choose a file to translate<br />
<br />
<br />
[[File : OsgeoLive translation choosen file.png | 600px ]]<br />
<br />
<br />
[[File : OsgeoLive_translation_translatefile.png | 600px ]]<br />
<br />
== Roles ==<br />
<br />
There is several roles where you can help us.<br />
<br />
=== Translator ===<br />
<br />
This role can translate strings, it is the most important job !<br />
<br />
=== Reviewer ===<br />
<br />
If your a confident enough in your language and technical knowledge, you can become <br />
a reviewer and review strings to fix the possible typos. <br />
<br />
=== Language coordinator ===<br />
<br />
A coordinator can accept new Translator and grant Reviewer privileges. With a lot of different languages, <br />
it helps a lot the administrator.<br />
<br />
<br />
= Build the documentation =<br />
== The general process OSGeo-Live used for documentation: ==<br />
<br />
<ul><br />
<li>The developer use [http://docutils.sourceforge.net/docs/user/rst/quickstart.html ReStructuredText] syntax to write the documentation in English.</li><br />
<li>That documentation is then used with [http://sphinx-doc.org/contents.html Sphinx] to generate the english html, man, pdf, etc.</li><br />
<li>Also using [http://sphinx-doc.org/latest/intl.html Sphinx-intl] the <code>*.pot</code> files are generated.</li><br />
<li>Those <code>*.pot</code> files are used by [https://www.transifex.com/osgeo/osgeolive Transifex] and they contain only the strings that need to be translated.</li><br />
<li>Translator works with those strings using the process bellow.</li><br />
<li>When the translator finishes a language, the git hub mantainers proceed to download the generated <code>*.po</code> files that contain the translated strings and commit them in git hub and update the documentation page.</li><br />
<li><p>Users can create their translation using:</p><br />
<p>tools/transifex/create_translation.sh fr</p></li></ul><br />
<br />
Translations to French are going to be used as examples along this wiki, we choose French so you can focus on what is being translated and what is not.<br />
<br />
== Before you start ==<br />
<br />
=== Prepare your clone for documentation ===<br />
<br />
<pre><br />
## Prepare the directory<br />
git clone https://github.com/OSGeo/OSGeoLive-doc docClone<br />
cd docClone<br />
git checkout develop ## new things come into develop, then are merged into master<br />
mkdir build<br />
cd build<br />
<br />
## prepare the documentation for French (English is automatically build)<br />
cmake -DHTML=ON -DFR=ON .. <br />
## Build the doc<br />
make doc<br />
cd ..</pre><br />
<br />
=== Downloading translation ===<br />
<br />
* To download a particular file.<br />
<br />
Best when reviewing the file:<br />
<br />
<pre><br />
tx pull -l fr -r osgeolive.quickstart--ideditor_quickstart<br />
</pre><br />
<br />
* Download the latest translated <code>*.po</code> files of your language based on translation percentage.<br />
<br />
<pre><br />
tx pull -l fr --minimum-perc=100<br />
</pre><br />
<br />
<br />
* Ask for help:<br />
<br />
<pre><br />
tx pull --help<br />
</pre><br />
<br />
==== Checking the download ====<br />
<br />
<pre><br />
git status<br />
</pre><br />
<br />
A possible output:<br />
<br />
=== Have your language documentation html open. ===<br />
<br />
Viewing your language html will help to put strings in context and/or check the translation.<br />
<br />
<pre>tools/transifex/create_translations.sh fr</pre><br />
The French documentation would be in<br />
<br />
<pre>build/doc/html/fr/doc/index.html</pre><br />
<br />
=== Transifex files that are not accepting translations. ===<br />
<br />
Files not accepting translations are marked with a red dot, maybe the file belongs to a previous version of OSGeo-Live documentation, or it was moved from one directory to another. Those files are not erased from the system so any translated string can be reused.<br />
<br />
=== English spelling and grammar ===<br />
<br />
Sometimes the developers and the reviewers have typos in the English version, you will see spelling typos with a wavy red line, unfortunately it is too late to correct them for the current version. So proceed with the translation with the best of your ability. For the grammar, if you don't understand what is being told, please go to [https://github.com/pgRouting/pgrouting/issues/200 issue 200] to post a comment stating the file and pasting the English string. If a change has been considered, the string to be translated will be posted on the &quot;instructions&quot; for the string.<br />
<br />
== Working with small strings ==<br />
<br />
=== Choose the small files first. ===<br />
<br />
For &quot;small&quot; I mean the ones that have very few strings to be translated. That will start building up a bank of translated strings that can be used in larger files. To detect a &quot;small&quot; file go to the list of [resources] (https://www.transifex.com/projects/p/pgrouting/resources/) and choose a file with few words or few strings.<br />
<br />
=== Use &quot;translate&quot; button ===<br />
<br />
The &quot;translate button&quot; comes quite handy, you still have to check the translation, and there is an &quot;undo&quot; button if you think that its better for you to type the translation than to modify the machine's translation.<br />
<br />
Don't use &quot;translate&quot; button on stand alone references like<br />
<br />
<pre>en: :ref:`sample`<br />
ja: :ref:`サンプル` &lt;--- wrong</pre><br />
=== Use a &quot;suggestion&quot; ===<br />
<br />
When you work with transifex it builds up a translated string bank and it will show one or more suggestions. If the suggestion is very close to what is needed, use it, and change the translation to the final translation of the string. Example:<br />
<br />
<pre>en: :ref:`pgr_astar&lt;pgr_astar&gt;` - Shortest Path A*<br />
Use suggestion: pgr_astar - A*アルゴリズムを用いた最短経路探索<br />
Modify to: :ref:`pgr_astar&lt;pgr_astar&gt;` - A*アルゴリズムを用いた最短経路探索</pre><br />
=== Use &quot;copy button&quot; ===<br />
<br />
Copy the the stand alone references like<br />
<br />
<pre>en: :ref:`sample`<br />
ja: :ref:`sample`</pre><br />
=== Type a translation ===<br />
<br />
You can just type your translation.<br />
<br />
=== Go to the next string ===<br />
<br />
When you finished translating the string press &quot;tab&quot;, that way it get's saved, if you click to a different string, maybe because the next string is already translated, then it won't be saved (green/white stripes).<br />
<br />
=== Save your translation ===<br />
<br />
Make sure all strings using the &quot;Save all unsaved translations&quot; button.<br />
<br />
== Check your work ==<br />
<br />
This step is needed not to check the translation but to check that ReStructuredText in the translated strings is correct. Many things might be wrong, an extra space, a missing space or a missing character &quot;`&quot; .<br />
<br />
=== Download the translated file and recreate the translation ===<br />
<br />
If the file you modified in transifex is doc--src--changelog--index and want to check the Japanese translation<br />
<br />
<pre>tools/transifex/download_translation.sh ja pgrouting.doc--src--changelog--index<br />
tools/transifex/create_translations.sh ja</pre><br />
Navigate to the the translated file, for this example it would be<br />
<br />
<pre>build/doc/html/ja/doc/src/changelog/index.html</pre><br />
Notice the relation between names:<br />
<br />
<pre>Transifex name: pgrouting.doc--src--changelog--index<br />
Html Generated File: build/doc/html/ja/doc/src/changelog/index.html</pre><br />
And visualy compare the &quot;looks&quot; with the [English version] (http://docs.pgrouting.org/2.0/en/doc/index.html)<br />
<br />
=== Use the &quot;Approve translation&quot; button ===<br />
<br />
When the file is fully translated (except the navigation bar), you can are about to approve the translation, '''????????'''<br />
<br />
* Check the links first, example: there is a link to sample data.<br />
<br />
Example:<br />
<br />
<pre>html: 上記クエリは サンプルデータ のネットワークを使用しています。 &lt;-- sample data is translated<br />
or: 上記クエリは Sample Data のネットワークを使用しています。 &lt;--- sample data needs translation</pre><br />
If you can navigate the links, you are ok<br />
<br />
* When using create_translation script there was no &quot;inline&quot; error (see [[Translation Troubleshooting]] ), you are ok<br />
<br />
If you are ok, then choose a string and click the &quot;Approve translation&quot; button.<br />
<br />
== Which file is next ==<br />
<br />
=== Do doc--index last ===<br />
<br />
That way you can use the &quot;Use suggestion&quot; in this file.<br />
<br />
=== Work &quot;important&quot; files first ===<br />
<br />
All files are important, but the following files are the core of the project. Most of them have repeated strings, so the &quot;Use Suggestion&quot; tactic is perfect, and you can use the search box to find them.<br />
<br />
- your project files: you know that project certainly better than us, especially in your language; starting by the overview then the quickstart<br />
- OSGeoLive files: there is several core files for the OSgeoLive documentation:<br />
- index<br />
- overview--overview<br />
- overview--toc<br />
- quickstart--virtualization_quickstart<br />
- quickstart--usb_quickstart<br />
- quickstart--osgeolive_quickstart<br />
- copyright<br />
- contributors<br />
- translators<br />
- presentation<br />
- sponsors<br />
<br />
etc<br />
<br />
They are listed with a red double ">" priority sign<br />
<br />
=== Work the &quot;almost finished&quot; files ===<br />
<br />
After you finish a file, you can choose a file that is &quot;almost done&quot;. I found pretty uncomfortable the list placed at the left, so to choose an almost done file I recommend:<br />
<br />
* Click Documentation<br />
* Click on your language<br />
* click on the sorting button (sorts by % of termination)<br />
<br />
This is very useful when you have a lot of files already translated<br />
<br />
=== Work files that belong to a directory ===<br />
<br />
Based on the following files:<br />
<br />
* doc--src--changelog--1_x ... 150 words (25 strings) ...<br />
* doc--src--changelog--2_0 ... 277 words (26 strings) ...<br />
* doc--src--changelog--index ... 4 words (3 strings) ...<br />
<br />
Maybe you started working with doc--src--changelog--index, so the next step would be to work with<br />
<br />
* doc--src--changelog--1_x<br />
* doc--src--changelog--2_0<br />
<br />
So you finished a section, go [[Translation Check your work]].<br />
<br />
= Troubleshooting =<br />
<br />
Please post any question in [https://github.com/pgRouting/pgrouting/issues/200 issue 200]<br />
<br />
=== The :ref:`nameoflink` link is not translated ===<br />
<br />
Example<br />
<br />
<pre>en: The queries use the :ref:`sampledata` network.<br />
ja: 上記クエリは :ref:`sampledata` のネットワークを使用しています。 <br />
html: 上記クエリは Sample Data のネットワークを使用しています。</pre><br />
Thats and indication that the referenced page for Sample Data, isn't fully translated. If you can click on the link and navigate you are ok.<br />
<br />
=== The :ref:`nameoflink` link is the only thing that is translated ===<br />
<br />
Example<br />
<br />
<pre>en: The queries use the :ref:`sampledata` network.<br />
ja: The queries use the :ref:`sampledata` network.<br />
html: The queries use the サンプルデータ network.</pre><br />
Maybe you navigated into an untranslated page that has a reference to a translated page.<br />
<br />
=== I don't see the link but I can read :ref: in the html page ===<br />
<br />
This is a common problem when using the translation button.<br /><br />
Example<br />
<br />
<pre>en: The queries use the :ref:`sampledata` network.<br />
ja: 上記クエリは: ref:'sampledata'のネットワークを使用しています。 <br />
html: 上記クエリは: ref:'sampledata'のネットワークを使用しています。</pre><br />
The link's generated by the button need to be corrected, I suggest to copy the link together with its sorrounding spaces from the English version:<br />
<br />
<pre> -------------------<br />
en: The queries use the :ref:`sampledata` network.<br />
ja: 上記クエリは :ref:`sampledata` のネットワークを使用しています。 <br />
html: 上記クエリは サンプルデータ のネットワークを使用しています。<br />
or: 上記クエリは Sample Data のネットワークを使用しています。</pre><br />
<br />
=== WARNING: Inline literal start-string without end-string. ===<br />
<br />
You will get this error is when using ''tools/transifex/create_translations.sh''. Languages like Japanese that don't use spaces to separate words are more likely to have this error. Unfortunately the error is shown only in line 1.<br />
<br />
Inline literals [specs] (http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#inline-markup) require a space before and after. The inline literals we use the most are of the type ``inlineliteral`` like in:<br />
<br />
<pre>``int4`` id of the end point<br />
``int4``型の始点ノードのID &lt;--- this will generate the error<br />
``int4 `` 型の始点ノードのID &lt;--- this will also generate the error (a space is after the 4)<br />
``int4`` 型の始点ノードのID &lt;--- a space is (before as a new line and) after the inline literal</pre><br />
= Tools for the Reviewer =<br />
<br />
=== tools/transifex/download_translation.sh ===<br />
<br />
Use to update the <code>*.po</code> files that are in your system with the latest translation stored in Transifex.<br /><br />
Languages available:<br />
<br />
* es - Spanish<br />
* fr - French<br />
* ja - Japanese<br />
* de - German<br />
<br />
tools/transifex/download_translation.sh [es|ja|fr|de] [pgrouting.&lt;filename&gt;]<br />
<br />
To download all language translations:<br />
<br />
<pre>tools/transifex/download_translation.sh</pre><br />
To download all the translations of a particular language:<br />
<br />
<pre>tools/transifex/download_translation.sh [es|ja|fr|de]</pre><br />
To download the translation of a specific file you need to state the language also<br />
<br />
<pre>tools/transifex/download_translation.sh [es|ja|fr|de] [pgrouting.&lt;filename&gt;]</pre><br />
<br />
=== tools/transifex/create_translations.sh ===<br />
<br />
Use to create: html, man, pdf documentation of the languages based on the <code>*.po</code> files stored in your system. Languages available:<br />
<br />
* es - Spanish<br />
* fr - French<br />
* ja - Japanese<br />
* de - German<br />
<br />
To create the documentation of all the languages<br />
<br />
<pre>tools/transifex/create_translations.sh</pre><br />
To create the documentation of a particular language:<br />
<br />
<pre>tools/transifex/create_translations.sh [es|ja|fr|de]</pre><br />
The main index.html of the documentation will be located at:<br />
<br />
<pre>build/doc/html/[es|ja|fr|de]/doc/index.html</pre><br />
<br />
= Main wiki page =<br />
<br />
* [https://wiki.osgeo.org/wiki/OSGeoLive OSGeoLive Wiki]<br />
<br />
<br />
[[Category: OSGeoLive]]</div>Bakanikohttps://wiki.osgeo.org/w/index.php?title=File:OsgeoLive_translation_translatefile.png&diff=113843File:OsgeoLive translation translatefile.png2018-02-28T20:09:45Z<p>Bakaniko: </p>
<hr />
<div></div>Bakanikohttps://wiki.osgeo.org/w/index.php?title=OSGeoLive_Translation_Process&diff=113842OSGeoLive Translation Process2018-02-28T20:09:27Z<p>Bakaniko: </p>
<hr />
<div><br />
This document is divided in two part, if you want to help us translate the OSGeoLive documentation, the first part will guide you through the Transifex platform. If you want to help us build it the second part will give you more technical information about Transifex, sphinx and the building process.<br />
<br />
__FORCETOC__<br />
<br />
= Translate on Transifex =<br />
<br />
Thanks for helping us translate the OSGeoLive project documentation !<br />
<br />
You can find us there: [https://www.transifex.com/osgeo/osgeolive/]<br />
<br />
== Available languages ==<br />
<br />
As for now (february 2018), there is 18 registered languages for the project. <br />
If your language is not in the list below (or on the updated list on Transifex),<br />
please make a request to add it !<br />
<br />
<br />
The list of [https://www.transifex.com/osgeo/osgeolive/languages/ Languages]:<br />
<br />
* Bengali<br />
* Catalan<br />
* Dutch<br />
* Finnish<br />
* French<br />
* German<br />
* Greek<br />
* Hindi<br />
* Hungarian<br />
* Italian <br />
* Japanese<br />
* Polish<br />
* Portuguese<br />
* Russian<br />
* Spanish<br />
* Mexican spanish<br />
<br />
<br />
== Connect to the Transifex platform == <br />
<br />
If you don't have an account, please create one and then go to the project page.<br />
<br />
Look for the language you want to help with (or ask to add it if it is not there already).<br />
<br />
For each languages, there is a list of '''resources''', it is the files to translate (actually 180 of them).<br />
<br />
[[File: Language resources.png | 600px ]]<br />
<br />
== Files to translate ==<br />
The list of [https://www.transifex.com/osgeo/osgeolive/content/ resources]<br />
are classified as:<br />
* ">>" Urgent - OSGeo-Live related files<br />
<br />
[[File: OSGEo-Live_transifex_01_index.png | 600px ]]<br />
<br />
* "^" High - Projects related files<br />
<br />
[[File: OSGEo-Live_transifex_02_second_priority.png | 600px ]]<br />
<br />
* "-" Normal - Deprecated projects files (not for translating)<br />
<br />
[[File: OSGEo-Live_transifex_03_retired_files.png | 600px ]]<br />
<br />
You can easily order them by Version (v11) and and descending priority<br />
<br />
[[File : OSGEo-Live_transifex_04_priority.png | 600px ]]<br />
<br />
Please note that the urgent files are the OSGeoLive project files, if you <br />
are more comfortable translating only the files of a project provided by OSGeoLive,<br />
it is perfectly ok. :)<br />
<br />
Please note each project has 2 files:<br />
* an overview prefixed with ''overview--<name of the project>''<br />
* a quickstart prefixed with ''quickstart--<name of the project>''<br />
<br />
== Translation ==<br />
<br />
Once you have choose a file to translate<br />
<br />
<br />
[[File : OsgeoLive translation choosen file.png | 600px ]]<br />
<br />
<br />
[[File : OsgeoLive translation choosen file.png | 600px ]]<br />
<br />
== Roles ==<br />
<br />
There is several roles where you can help us.<br />
<br />
=== Translator ===<br />
<br />
This role can translate strings, it is the most important job !<br />
<br />
=== Reviewer ===<br />
<br />
If your a confident enough in your language and technical knowledge, you can become <br />
a reviewer and review strings to fix the possible typos. <br />
<br />
=== Language coordinator ===<br />
<br />
A coordinator can accept new Translator and grant Reviewer privileges. With a lot of different languages, <br />
it helps a lot the administrator.<br />
<br />
<br />
= Build the documentation =<br />
== The general process OSGeo-Live used for documentation: ==<br />
<br />
<ul><br />
<li>The developer use [http://docutils.sourceforge.net/docs/user/rst/quickstart.html ReStructuredText] syntax to write the documentation in English.</li><br />
<li>That documentation is then used with [http://sphinx-doc.org/contents.html Sphinx] to generate the english html, man, pdf, etc.</li><br />
<li>Also using [http://sphinx-doc.org/latest/intl.html Sphinx-intl] the <code>*.pot</code> files are generated.</li><br />
<li>Those <code>*.pot</code> files are used by [https://www.transifex.com/osgeo/osgeolive Transifex] and they contain only the strings that need to be translated.</li><br />
<li>Translator works with those strings using the process bellow.</li><br />
<li>When the translator finishes a language, the git hub mantainers proceed to download the generated <code>*.po</code> files that contain the translated strings and commit them in git hub and update the documentation page.</li><br />
<li><p>Users can create their translation using:</p><br />
<p>tools/transifex/create_translation.sh fr</p></li></ul><br />
<br />
Translations to French are going to be used as examples along this wiki, we choose French so you can focus on what is being translated and what is not.<br />
<br />
== Before you start ==<br />
<br />
=== Prepare your clone for documentation ===<br />
<br />
<pre><br />
## Prepare the directory<br />
git clone https://github.com/OSGeo/OSGeoLive-doc docClone<br />
cd docClone<br />
git checkout develop ## new things come into develop, then are merged into master<br />
mkdir build<br />
cd build<br />
<br />
## prepare the documentation for French (English is automatically build)<br />
cmake -DHTML=ON -DFR=ON .. <br />
## Build the doc<br />
make doc<br />
cd ..</pre><br />
<br />
=== Downloading translation ===<br />
<br />
* To download a particular file.<br />
<br />
Best when reviewing the file:<br />
<br />
<pre><br />
tx pull -l fr -r osgeolive.quickstart--ideditor_quickstart<br />
</pre><br />
<br />
* Download the latest translated <code>*.po</code> files of your language based on translation percentage.<br />
<br />
<pre><br />
tx pull -l fr --minimum-perc=100<br />
</pre><br />
<br />
<br />
* Ask for help:<br />
<br />
<pre><br />
tx pull --help<br />
</pre><br />
<br />
==== Checking the download ====<br />
<br />
<pre><br />
git status<br />
</pre><br />
<br />
A possible output:<br />
<br />
=== Have your language documentation html open. ===<br />
<br />
Viewing your language html will help to put strings in context and/or check the translation.<br />
<br />
<pre>tools/transifex/create_translations.sh fr</pre><br />
The French documentation would be in<br />
<br />
<pre>build/doc/html/fr/doc/index.html</pre><br />
<br />
=== Transifex files that are not accepting translations. ===<br />
<br />
Files not accepting translations are marked with a red dot, maybe the file belongs to a previous version of OSGeo-Live documentation, or it was moved from one directory to another. Those files are not erased from the system so any translated string can be reused.<br />
<br />
=== English spelling and grammar ===<br />
<br />
Sometimes the developers and the reviewers have typos in the English version, you will see spelling typos with a wavy red line, unfortunately it is too late to correct them for the current version. So proceed with the translation with the best of your ability. For the grammar, if you don't understand what is being told, please go to [https://github.com/pgRouting/pgrouting/issues/200 issue 200] to post a comment stating the file and pasting the English string. If a change has been considered, the string to be translated will be posted on the &quot;instructions&quot; for the string.<br />
<br />
== Working with small strings ==<br />
<br />
=== Choose the small files first. ===<br />
<br />
For &quot;small&quot; I mean the ones that have very few strings to be translated. That will start building up a bank of translated strings that can be used in larger files. To detect a &quot;small&quot; file go to the list of [resources] (https://www.transifex.com/projects/p/pgrouting/resources/) and choose a file with few words or few strings.<br />
<br />
=== Use &quot;translate&quot; button ===<br />
<br />
The &quot;translate button&quot; comes quite handy, you still have to check the translation, and there is an &quot;undo&quot; button if you think that its better for you to type the translation than to modify the machine's translation.<br />
<br />
Don't use &quot;translate&quot; button on stand alone references like<br />
<br />
<pre>en: :ref:`sample`<br />
ja: :ref:`サンプル` &lt;--- wrong</pre><br />
=== Use a &quot;suggestion&quot; ===<br />
<br />
When you work with transifex it builds up a translated string bank and it will show one or more suggestions. If the suggestion is very close to what is needed, use it, and change the translation to the final translation of the string. Example:<br />
<br />
<pre>en: :ref:`pgr_astar&lt;pgr_astar&gt;` - Shortest Path A*<br />
Use suggestion: pgr_astar - A*アルゴリズムを用いた最短経路探索<br />
Modify to: :ref:`pgr_astar&lt;pgr_astar&gt;` - A*アルゴリズムを用いた最短経路探索</pre><br />
=== Use &quot;copy button&quot; ===<br />
<br />
Copy the the stand alone references like<br />
<br />
<pre>en: :ref:`sample`<br />
ja: :ref:`sample`</pre><br />
=== Type a translation ===<br />
<br />
You can just type your translation.<br />
<br />
=== Go to the next string ===<br />
<br />
When you finished translating the string press &quot;tab&quot;, that way it get's saved, if you click to a different string, maybe because the next string is already translated, then it won't be saved (green/white stripes).<br />
<br />
=== Save your translation ===<br />
<br />
Make sure all strings using the &quot;Save all unsaved translations&quot; button.<br />
<br />
== Check your work ==<br />
<br />
This step is needed not to check the translation but to check that ReStructuredText in the translated strings is correct. Many things might be wrong, an extra space, a missing space or a missing character &quot;`&quot; .<br />
<br />
=== Download the translated file and recreate the translation ===<br />
<br />
If the file you modified in transifex is doc--src--changelog--index and want to check the Japanese translation<br />
<br />
<pre>tools/transifex/download_translation.sh ja pgrouting.doc--src--changelog--index<br />
tools/transifex/create_translations.sh ja</pre><br />
Navigate to the the translated file, for this example it would be<br />
<br />
<pre>build/doc/html/ja/doc/src/changelog/index.html</pre><br />
Notice the relation between names:<br />
<br />
<pre>Transifex name: pgrouting.doc--src--changelog--index<br />
Html Generated File: build/doc/html/ja/doc/src/changelog/index.html</pre><br />
And visualy compare the &quot;looks&quot; with the [English version] (http://docs.pgrouting.org/2.0/en/doc/index.html)<br />
<br />
=== Use the &quot;Approve translation&quot; button ===<br />
<br />
When the file is fully translated (except the navigation bar), you can are about to approve the translation, '''????????'''<br />
<br />
* Check the links first, example: there is a link to sample data.<br />
<br />
Example:<br />
<br />
<pre>html: 上記クエリは サンプルデータ のネットワークを使用しています。 &lt;-- sample data is translated<br />
or: 上記クエリは Sample Data のネットワークを使用しています。 &lt;--- sample data needs translation</pre><br />
If you can navigate the links, you are ok<br />
<br />
* When using create_translation script there was no &quot;inline&quot; error (see [[Translation Troubleshooting]] ), you are ok<br />
<br />
If you are ok, then choose a string and click the &quot;Approve translation&quot; button.<br />
<br />
== Which file is next ==<br />
<br />
=== Do doc--index last ===<br />
<br />
That way you can use the &quot;Use suggestion&quot; in this file.<br />
<br />
=== Work &quot;important&quot; files first ===<br />
<br />
All files are important, but the following files are the core of the project. Most of them have repeated strings, so the &quot;Use Suggestion&quot; tactic is perfect, and you can use the search box to find them.<br />
<br />
- your project files: you know that project certainly better than us, especially in your language; starting by the overview then the quickstart<br />
- OSGeoLive files: there is several core files for the OSgeoLive documentation:<br />
- index<br />
- overview--overview<br />
- overview--toc<br />
- quickstart--virtualization_quickstart<br />
- quickstart--usb_quickstart<br />
- quickstart--osgeolive_quickstart<br />
- copyright<br />
- contributors<br />
- translators<br />
- presentation<br />
- sponsors<br />
<br />
etc<br />
<br />
They are listed with a red double ">" priority sign<br />
<br />
=== Work the &quot;almost finished&quot; files ===<br />
<br />
After you finish a file, you can choose a file that is &quot;almost done&quot;. I found pretty uncomfortable the list placed at the left, so to choose an almost done file I recommend:<br />
<br />
* Click Documentation<br />
* Click on your language<br />
* click on the sorting button (sorts by % of termination)<br />
<br />
This is very useful when you have a lot of files already translated<br />
<br />
=== Work files that belong to a directory ===<br />
<br />
Based on the following files:<br />
<br />
* doc--src--changelog--1_x ... 150 words (25 strings) ...<br />
* doc--src--changelog--2_0 ... 277 words (26 strings) ...<br />
* doc--src--changelog--index ... 4 words (3 strings) ...<br />
<br />
Maybe you started working with doc--src--changelog--index, so the next step would be to work with<br />
<br />
* doc--src--changelog--1_x<br />
* doc--src--changelog--2_0<br />
<br />
So you finished a section, go [[Translation Check your work]].<br />
<br />
= Troubleshooting =<br />
<br />
Please post any question in [https://github.com/pgRouting/pgrouting/issues/200 issue 200]<br />
<br />
=== The :ref:`nameoflink` link is not translated ===<br />
<br />
Example<br />
<br />
<pre>en: The queries use the :ref:`sampledata` network.<br />
ja: 上記クエリは :ref:`sampledata` のネットワークを使用しています。 <br />
html: 上記クエリは Sample Data のネットワークを使用しています。</pre><br />
Thats and indication that the referenced page for Sample Data, isn't fully translated. If you can click on the link and navigate you are ok.<br />
<br />
=== The :ref:`nameoflink` link is the only thing that is translated ===<br />
<br />
Example<br />
<br />
<pre>en: The queries use the :ref:`sampledata` network.<br />
ja: The queries use the :ref:`sampledata` network.<br />
html: The queries use the サンプルデータ network.</pre><br />
Maybe you navigated into an untranslated page that has a reference to a translated page.<br />
<br />
=== I don't see the link but I can read :ref: in the html page ===<br />
<br />
This is a common problem when using the translation button.<br /><br />
Example<br />
<br />
<pre>en: The queries use the :ref:`sampledata` network.<br />
ja: 上記クエリは: ref:'sampledata'のネットワークを使用しています。 <br />
html: 上記クエリは: ref:'sampledata'のネットワークを使用しています。</pre><br />
The link's generated by the button need to be corrected, I suggest to copy the link together with its sorrounding spaces from the English version:<br />
<br />
<pre> -------------------<br />
en: The queries use the :ref:`sampledata` network.<br />
ja: 上記クエリは :ref:`sampledata` のネットワークを使用しています。 <br />
html: 上記クエリは サンプルデータ のネットワークを使用しています。<br />
or: 上記クエリは Sample Data のネットワークを使用しています。</pre><br />
<br />
=== WARNING: Inline literal start-string without end-string. ===<br />
<br />
You will get this error is when using ''tools/transifex/create_translations.sh''. Languages like Japanese that don't use spaces to separate words are more likely to have this error. Unfortunately the error is shown only in line 1.<br />
<br />
Inline literals [specs] (http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#inline-markup) require a space before and after. The inline literals we use the most are of the type ``inlineliteral`` like in:<br />
<br />
<pre>``int4`` id of the end point<br />
``int4``型の始点ノードのID &lt;--- this will generate the error<br />
``int4 `` 型の始点ノードのID &lt;--- this will also generate the error (a space is after the 4)<br />
``int4`` 型の始点ノードのID &lt;--- a space is (before as a new line and) after the inline literal</pre><br />
= Tools for the Reviewer =<br />
<br />
=== tools/transifex/download_translation.sh ===<br />
<br />
Use to update the <code>*.po</code> files that are in your system with the latest translation stored in Transifex.<br /><br />
Languages available:<br />
<br />
* es - Spanish<br />
* fr - French<br />
* ja - Japanese<br />
* de - German<br />
<br />
tools/transifex/download_translation.sh [es|ja|fr|de] [pgrouting.&lt;filename&gt;]<br />
<br />
To download all language translations:<br />
<br />
<pre>tools/transifex/download_translation.sh</pre><br />
To download all the translations of a particular language:<br />
<br />
<pre>tools/transifex/download_translation.sh [es|ja|fr|de]</pre><br />
To download the translation of a specific file you need to state the language also<br />
<br />
<pre>tools/transifex/download_translation.sh [es|ja|fr|de] [pgrouting.&lt;filename&gt;]</pre><br />
<br />
=== tools/transifex/create_translations.sh ===<br />
<br />
Use to create: html, man, pdf documentation of the languages based on the <code>*.po</code> files stored in your system. Languages available:<br />
<br />
* es - Spanish<br />
* fr - French<br />
* ja - Japanese<br />
* de - German<br />
<br />
To create the documentation of all the languages<br />
<br />
<pre>tools/transifex/create_translations.sh</pre><br />
To create the documentation of a particular language:<br />
<br />
<pre>tools/transifex/create_translations.sh [es|ja|fr|de]</pre><br />
The main index.html of the documentation will be located at:<br />
<br />
<pre>build/doc/html/[es|ja|fr|de]/doc/index.html</pre><br />
<br />
= Main wiki page =<br />
<br />
* [https://wiki.osgeo.org/wiki/OSGeoLive OSGeoLive Wiki]<br />
<br />
<br />
[[Category: OSGeoLive]]</div>Bakanikohttps://wiki.osgeo.org/w/index.php?title=File:OsgeoLive_translation_choosen_file.png&diff=113841File:OsgeoLive translation choosen file.png2018-02-28T20:08:20Z<p>Bakaniko: </p>
<hr />
<div></div>Bakanikohttps://wiki.osgeo.org/w/index.php?title=OSGeoLive_Translation_Process&diff=113836OSGeoLive Translation Process2018-02-27T21:29:29Z<p>Bakaniko: </p>
<hr />
<div><br />
This document is divided in two part, if you want to help us translate the OSGeoLive documentation, the first part will guide you through the Transifex platform. If you want to help us build it the second part will give you more technical information about Transifex, sphinx and the building process.<br />
<br />
__FORCETOC__<br />
<br />
= Translate on Transifex =<br />
<br />
Thanks for helping us translate the OSGeoLive project documentation !<br />
<br />
You can find us there: [https://www.transifex.com/osgeo/osgeolive/]<br />
<br />
== Available languages ==<br />
<br />
As for now (february 2018), there is 18 registered languages for the project. <br />
If your language is not in the list below (or on the updated list on Transifex),<br />
please make a request to add it !<br />
<br />
<br />
The list of [https://www.transifex.com/osgeo/osgeolive/languages/ Languages]:<br />
<br />
* Bengali<br />
* Catalan<br />
* Dutch<br />
* Finnish<br />
* French<br />
* German<br />
* Greek<br />
* Hindi<br />
* Hungarian<br />
* Italian <br />
* Japanese<br />
* Polish<br />
* Portuguese<br />
* Russian<br />
* Spanish<br />
* Mexican spanish<br />
<br />
<br />
== Connect to the Transifex platform == <br />
<br />
If you don't have an account, please create one and then go to the project page.<br />
<br />
Look for the language you want to help with (or ask to add it if it is not there already).<br />
<br />
For each languages, there is a list of '''resources''', it is the files to translate (actually 180 of them).<br />
<br />
[[File: Language resources.png | 600px ]]<br />
<br />
== Files to translate ==<br />
The list of [https://www.transifex.com/osgeo/osgeolive/content/ resources]<br />
are classified as:<br />
* ">>" Urgent - OSGeo-Live related files<br />
<br />
[[File: OSGEo-Live_transifex_01_index.png | 600px ]]<br />
<br />
* "^" High - Projects related files<br />
<br />
[[File: OSGEo-Live_transifex_02_second_priority.png | 600px ]]<br />
<br />
* "-" Normal - Deprecated projects files (not for translating)<br />
<br />
[[File: OSGEo-Live_transifex_03_retired_files.png | 600px ]]<br />
<br />
You can easily order them by Version (v11) and and descending priority<br />
<br />
[[File : OSGEo-Live_transifex_04_priority.png | 600px ]]<br />
<br />
Please note that the urgent files are the OSGeoLive project files, if you <br />
are more comfortable translating only the files of a project provided by OSGeoLive,<br />
it is perfectly ok. :)<br />
<br />
Please note each project has 2 files:<br />
* an overview prefixed with ''overview--<name of the project>''<br />
* a quickstart prefixed with ''quickstart--<name of the project>''<br />
<br />
== Translation ==<br />
<br />
Once you have choose a file to translate<br />
<br />
<br />
== Roles ==<br />
<br />
There is several roles where you can help us.<br />
<br />
=== Translator ===<br />
<br />
This role can translate strings, it is the most important job !<br />
<br />
=== Reviewer ===<br />
<br />
If your a confident enough in your languages and technical skills, you can become <br />
a reviewer and review strings to fix the possible typos. <br />
<br />
=== Language coordinator ===<br />
<br />
A coordinator can accept new Translator and grant Reviewer privileges. With a lot of different languages, <br />
it helps a lot the administrator.<br />
<br />
<br />
= Build the documentation =<br />
== The general process OSGeo-Live used for documentation: ==<br />
<br />
<ul><br />
<li>The developer use [http://docutils.sourceforge.net/docs/user/rst/quickstart.html ReStructuredText] syntax to write the documentation in English.</li><br />
<li>That documentation is then used with [http://sphinx-doc.org/contents.html Sphinx] to generate the english html, man, pdf, etc.</li><br />
<li>Also using [http://sphinx-doc.org/latest/intl.html Sphinx-intl] the <code>*.pot</code> files are generated.</li><br />
<li>Those <code>*.pot</code> files are used by [https://www.transifex.com/osgeo/osgeolive Transifex] and they contain only the strings that need to be translated.</li><br />
<li>Translator works with those strings using the process bellow.</li><br />
<li>When the translator finishes a language, the git hub mantainers proceed to download the generated <code>*.po</code> files that contain the translated strings and commit them in git hub and update the documentation page.</li><br />
<li><p>Users can create their translation using:</p><br />
<p>tools/transifex/create_translation.sh fr</p></li></ul><br />
<br />
Translations to French are going to be used as examples along this wiki, we choose French so you can focus on what is being translated and what is not.<br />
<br />
== Before you start ==<br />
<br />
=== Prepare your clone for documentation ===<br />
<br />
<pre><br />
## Prepare the directory<br />
git clone https://github.com/OSGeo/OSGeoLive-doc docClone<br />
cd docClone<br />
git checkout develop ## new things come into develop, then are merged into master<br />
mkdir build<br />
cd build<br />
<br />
## prepare the documentation for French (English is automatically build)<br />
cmake -DHTML=ON -DFR=ON .. <br />
## Build the doc<br />
make doc<br />
cd ..</pre><br />
<br />
=== Downloading translation ===<br />
<br />
* To download a particular file.<br />
<br />
Best when reviewing the file:<br />
<br />
<pre><br />
tx pull -l fr -r osgeolive.quickstart--ideditor_quickstart<br />
</pre><br />
<br />
* Download the latest translated <code>*.po</code> files of your language based on translation percentage.<br />
<br />
<pre><br />
tx pull -l fr --minimum-perc=100<br />
</pre><br />
<br />
<br />
* Ask for help:<br />
<br />
<pre><br />
tx pull --help<br />
</pre><br />
<br />
==== Checking the download ====<br />
<br />
<pre><br />
git status<br />
</pre><br />
<br />
A possible output:<br />
<br />
=== Have your language documentation html open. ===<br />
<br />
Viewing your language html will help to put strings in context and/or check the translation.<br />
<br />
<pre>tools/transifex/create_translations.sh fr</pre><br />
The French documentation would be in<br />
<br />
<pre>build/doc/html/fr/doc/index.html</pre><br />
<br />
=== Transifex files that are not accepting translations. ===<br />
<br />
Files not accepting translations are marked with a red dot, maybe the file belongs to a previous version of OSGeo-Live documentation, or it was moved from one directory to another. Those files are not erased from the system so any translated string can be reused.<br />
<br />
=== English spelling and grammar ===<br />
<br />
Sometimes the developers and the reviewers have typos in the English version, you will see spelling typos with a wavy red line, unfortunately it is too late to correct them for the current version. So proceed with the translation with the best of your ability. For the grammar, if you don't understand what is being told, please go to [https://github.com/pgRouting/pgrouting/issues/200 issue 200] to post a comment stating the file and pasting the English string. If a change has been considered, the string to be translated will be posted on the &quot;instructions&quot; for the string.<br />
<br />
== Working with small strings ==<br />
<br />
=== Choose the small files first. ===<br />
<br />
For &quot;small&quot; I mean the ones that have very few strings to be translated. That will start building up a bank of translated strings that can be used in larger files. To detect a &quot;small&quot; file go to the list of [resources] (https://www.transifex.com/projects/p/pgrouting/resources/) and choose a file with few words or few strings.<br />
<br />
=== Use &quot;translate&quot; button ===<br />
<br />
The &quot;translate button&quot; comes quite handy, you still have to check the translation, and there is an &quot;undo&quot; button if you think that its better for you to type the translation than to modify the machine's translation.<br />
<br />
Don't use &quot;translate&quot; button on stand alone references like<br />
<br />
<pre>en: :ref:`sample`<br />
ja: :ref:`サンプル` &lt;--- wrong</pre><br />
=== Use a &quot;suggestion&quot; ===<br />
<br />
When you work with transifex it builds up a translated string bank and it will show one or more suggestions. If the suggestion is very close to what is needed, use it, and change the translation to the final translation of the string. Example:<br />
<br />
<pre>en: :ref:`pgr_astar&lt;pgr_astar&gt;` - Shortest Path A*<br />
Use suggestion: pgr_astar - A*アルゴリズムを用いた最短経路探索<br />
Modify to: :ref:`pgr_astar&lt;pgr_astar&gt;` - A*アルゴリズムを用いた最短経路探索</pre><br />
=== Use &quot;copy button&quot; ===<br />
<br />
Copy the the stand alone references like<br />
<br />
<pre>en: :ref:`sample`<br />
ja: :ref:`sample`</pre><br />
=== Type a translation ===<br />
<br />
You can just type your translation.<br />
<br />
=== Go to the next string ===<br />
<br />
When you finished translating the string press &quot;tab&quot;, that way it get's saved, if you click to a different string, maybe because the next string is already translated, then it won't be saved (green/white stripes).<br />
<br />
=== Save your translation ===<br />
<br />
Make sure all strings using the &quot;Save all unsaved translations&quot; button.<br />
<br />
== Check your work ==<br />
<br />
This step is needed not to check the translation but to check that ReStructuredText in the translated strings is correct. Many things might be wrong, an extra space, a missing space or a missing character &quot;`&quot; .<br />
<br />
=== Download the translated file and recreate the translation ===<br />
<br />
If the file you modified in transifex is doc--src--changelog--index and want to check the Japanese translation<br />
<br />
<pre>tools/transifex/download_translation.sh ja pgrouting.doc--src--changelog--index<br />
tools/transifex/create_translations.sh ja</pre><br />
Navigate to the the translated file, for this example it would be<br />
<br />
<pre>build/doc/html/ja/doc/src/changelog/index.html</pre><br />
Notice the relation between names:<br />
<br />
<pre>Transifex name: pgrouting.doc--src--changelog--index<br />
Html Generated File: build/doc/html/ja/doc/src/changelog/index.html</pre><br />
And visualy compare the &quot;looks&quot; with the [English version] (http://docs.pgrouting.org/2.0/en/doc/index.html)<br />
<br />
=== Use the &quot;Approve translation&quot; button ===<br />
<br />
When the file is fully translated (except the navigation bar), you can are about to approve the translation, '''????????'''<br />
<br />
* Check the links first, example: there is a link to sample data.<br />
<br />
Example:<br />
<br />
<pre>html: 上記クエリは サンプルデータ のネットワークを使用しています。 &lt;-- sample data is translated<br />
or: 上記クエリは Sample Data のネットワークを使用しています。 &lt;--- sample data needs translation</pre><br />
If you can navigate the links, you are ok<br />
<br />
* When using create_translation script there was no &quot;inline&quot; error (see [[Translation Troubleshooting]] ), you are ok<br />
<br />
If you are ok, then choose a string and click the &quot;Approve translation&quot; button.<br />
<br />
== Which file is next ==<br />
<br />
=== Do doc--index last ===<br />
<br />
That way you can use the &quot;Use suggestion&quot; in this file.<br />
<br />
=== Work &quot;important&quot; files first ===<br />
<br />
All files are important, but the following files are the core of the project. Most of them have repeated strings, so the &quot;Use Suggestion&quot; tactic is perfect, and you can use the search box to find them.<br />
<br />
- your project files: you know that project certainly better than us, especially in your language; starting by the overview then the quickstart<br />
- OSGeoLive files: there is several core files for the OSgeoLive documentation:<br />
- index<br />
- overview--overview<br />
- overview--toc<br />
- quickstart--virtualization_quickstart<br />
- quickstart--usb_quickstart<br />
- quickstart--osgeolive_quickstart<br />
- copyright<br />
- contributors<br />
- translators<br />
- presentation<br />
- sponsors<br />
<br />
etc<br />
<br />
They are listed with a red double ">" priority sign<br />
<br />
=== Work the &quot;almost finished&quot; files ===<br />
<br />
After you finish a file, you can choose a file that is &quot;almost done&quot;. I found pretty uncomfortable the list placed at the left, so to choose an almost done file I recommend:<br />
<br />
* Click Documentation<br />
* Click on your language<br />
* click on the sorting button (sorts by % of termination)<br />
<br />
This is very useful when you have a lot of files already translated<br />
<br />
=== Work files that belong to a directory ===<br />
<br />
Based on the following files:<br />
<br />
* doc--src--changelog--1_x ... 150 words (25 strings) ...<br />
* doc--src--changelog--2_0 ... 277 words (26 strings) ...<br />
* doc--src--changelog--index ... 4 words (3 strings) ...<br />
<br />
Maybe you started working with doc--src--changelog--index, so the next step would be to work with<br />
<br />
* doc--src--changelog--1_x<br />
* doc--src--changelog--2_0<br />
<br />
So you finished a section, go [[Translation Check your work]].<br />
<br />
= Troubleshooting =<br />
<br />
Please post any question in [https://github.com/pgRouting/pgrouting/issues/200 issue 200]<br />
<br />
=== The :ref:`nameoflink` link is not translated ===<br />
<br />
Example<br />
<br />
<pre>en: The queries use the :ref:`sampledata` network.<br />
ja: 上記クエリは :ref:`sampledata` のネットワークを使用しています。 <br />
html: 上記クエリは Sample Data のネットワークを使用しています。</pre><br />
Thats and indication that the referenced page for Sample Data, isn't fully translated. If you can click on the link and navigate you are ok.<br />
<br />
=== The :ref:`nameoflink` link is the only thing that is translated ===<br />
<br />
Example<br />
<br />
<pre>en: The queries use the :ref:`sampledata` network.<br />
ja: The queries use the :ref:`sampledata` network.<br />
html: The queries use the サンプルデータ network.</pre><br />
Maybe you navigated into an untranslated page that has a reference to a translated page.<br />
<br />
=== I don't see the link but I can read :ref: in the html page ===<br />
<br />
This is a common problem when using the translation button.<br /><br />
Example<br />
<br />
<pre>en: The queries use the :ref:`sampledata` network.<br />
ja: 上記クエリは: ref:'sampledata'のネットワークを使用しています。 <br />
html: 上記クエリは: ref:'sampledata'のネットワークを使用しています。</pre><br />
The link's generated by the button need to be corrected, I suggest to copy the link together with its sorrounding spaces from the English version:<br />
<br />
<pre> -------------------<br />
en: The queries use the :ref:`sampledata` network.<br />
ja: 上記クエリは :ref:`sampledata` のネットワークを使用しています。 <br />
html: 上記クエリは サンプルデータ のネットワークを使用しています。<br />
or: 上記クエリは Sample Data のネットワークを使用しています。</pre><br />
<br />
=== WARNING: Inline literal start-string without end-string. ===<br />
<br />
You will get this error is when using ''tools/transifex/create_translations.sh''. Languages like Japanese that don't use spaces to separate words are more likely to have this error. Unfortunately the error is shown only in line 1.<br />
<br />
Inline literals [specs] (http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#inline-markup) require a space before and after. The inline literals we use the most are of the type ``inlineliteral`` like in:<br />
<br />
<pre>``int4`` id of the end point<br />
``int4``型の始点ノードのID &lt;--- this will generate the error<br />
``int4 `` 型の始点ノードのID &lt;--- this will also generate the error (a space is after the 4)<br />
``int4`` 型の始点ノードのID &lt;--- a space is (before as a new line and) after the inline literal</pre><br />
= Tools for the Reviewer =<br />
<br />
=== tools/transifex/download_translation.sh ===<br />
<br />
Use to update the <code>*.po</code> files that are in your system with the latest translation stored in Transifex.<br /><br />
Languages available:<br />
<br />
* es - Spanish<br />
* fr - French<br />
* ja - Japanese<br />
* de - German<br />
<br />
tools/transifex/download_translation.sh [es|ja|fr|de] [pgrouting.&lt;filename&gt;]<br />
<br />
To download all language translations:<br />
<br />
<pre>tools/transifex/download_translation.sh</pre><br />
To download all the translations of a particular language:<br />
<br />
<pre>tools/transifex/download_translation.sh [es|ja|fr|de]</pre><br />
To download the translation of a specific file you need to state the language also<br />
<br />
<pre>tools/transifex/download_translation.sh [es|ja|fr|de] [pgrouting.&lt;filename&gt;]</pre><br />
<br />
=== tools/transifex/create_translations.sh ===<br />
<br />
Use to create: html, man, pdf documentation of the languages based on the <code>*.po</code> files stored in your system. Languages available:<br />
<br />
* es - Spanish<br />
* fr - French<br />
* ja - Japanese<br />
* de - German<br />
<br />
To create the documentation of all the languages<br />
<br />
<pre>tools/transifex/create_translations.sh</pre><br />
To create the documentation of a particular language:<br />
<br />
<pre>tools/transifex/create_translations.sh [es|ja|fr|de]</pre><br />
The main index.html of the documentation will be located at:<br />
<br />
<pre>build/doc/html/[es|ja|fr|de]/doc/index.html</pre><br />
<br />
= Main wiki page =<br />
<br />
* [https://wiki.osgeo.org/wiki/OSGeoLive OSGeoLive Wiki]<br />
<br />
<br />
[[Category: OSGeoLive]]</div>Bakanikohttps://wiki.osgeo.org/w/index.php?title=File:Language_resources.png&diff=113835File:Language resources.png2018-02-27T21:28:24Z<p>Bakaniko: </p>
<hr />
<div></div>Bakanikohttps://wiki.osgeo.org/w/index.php?title=OSGeoLive_Translation_Process&diff=113834OSGeoLive Translation Process2018-02-27T21:25:02Z<p>Bakaniko: </p>
<hr />
<div><br />
This document is divided in two part, if you want to help us translate the OSGeoLive documentation, the first part will guide you through the Transifex platform. If you want to help us build it the second part will give you more technical information about Transifex, sphinx and the building process.<br />
<br />
__FORCETOC__<br />
<br />
= Translate on Transifex =<br />
<br />
Thanks for helping us translate the OSGeoLive project documentation !<br />
<br />
You can find us there: [https://www.transifex.com/osgeo/osgeolive/]<br />
<br />
== Available languages ==<br />
<br />
As for now (february 2018), there is 18 registered languages for the project. <br />
If your language is not in the list below (or on the updated list on Transifex),<br />
please make a request to add it !<br />
<br />
<br />
The list of [https://www.transifex.com/osgeo/osgeolive/languages/ Languages]:<br />
<br />
* Bengali<br />
* Catalan<br />
* Dutch<br />
* Finnish<br />
* French<br />
* German<br />
* Greek<br />
* Hindi<br />
* Hungarian<br />
* Italian <br />
* Japanese<br />
* Polish<br />
* Portuguese<br />
* Russian<br />
* Spanish<br />
* Mexican spanish<br />
<br />
<br />
== Connect to the Transifex platform == <br />
<br />
If you don't have an account, please create one and then go to the project page.<br />
<br />
Look for the language you want to help with (or ask to add it if it is not there already).<br />
<br />
<br />
<br />
<br />
== Files to translate ==<br />
The list of [https://www.transifex.com/osgeo/osgeolive/content/ resources]<br />
are classified as:<br />
* ">>" Urgent - OSGeo-Live related files<br />
<br />
[[File: OSGEo-Live_transifex_01_index.png | 500px ]]<br />
<br />
* "^" High - Projects related files<br />
<br />
[[File: OSGEo-Live_transifex_02_second_priority.png | 500px ]]<br />
<br />
* "-" Normal - Deprecated projects files (not for translating)<br />
<br />
[[File: OSGEo-Live_transifex_03_retired_files.png | 500px ]]<br />
<br />
You can easily order them by Version (v11) and and descending priority<br />
<br />
[[File : OSGEo-Live_transifex_04_priority.png | 500px ]]<br />
<br />
Please note that the urgent files are the OSGeoLive project files, if you <br />
are more comfortable translating only the files of a project provided by OSGeoLive,<br />
it is perfectly ok. :)<br />
<br />
Please note each project has 2 files:<br />
* an overview prefixed with ''overview--<name of the project>''<br />
* a quickstart prefixed with ''quickstart--<name of the project>''<br />
<br />
== Translation ==<br />
<br />
Once you have choose a file to translate<br />
<br />
<br />
== Roles ==<br />
<br />
There is several roles where you can help us.<br />
<br />
=== Translator ===<br />
<br />
This role can translate strings, it is the most important job !<br />
<br />
=== Reviewer ===<br />
<br />
If your a confident enough in your languages and technical skills, you can become <br />
a reviewer and review strings to fix the possible typos. <br />
<br />
=== Language coordinator ===<br />
<br />
A coordinator can accept new Translator and grant Reviewer privileges. With a lot of different languages, <br />
it helps a lot the administrator.<br />
<br />
<br />
= Build the documentation =<br />
== The general process OSGeo-Live used for documentation: ==<br />
<br />
<ul><br />
<li>The developer use [http://docutils.sourceforge.net/docs/user/rst/quickstart.html ReStructuredText] syntax to write the documentation in English.</li><br />
<li>That documentation is then used with [http://sphinx-doc.org/contents.html Sphinx] to generate the english html, man, pdf, etc.</li><br />
<li>Also using [http://sphinx-doc.org/latest/intl.html Sphinx-intl] the <code>*.pot</code> files are generated.</li><br />
<li>Those <code>*.pot</code> files are used by [https://www.transifex.com/osgeo/osgeolive Transifex] and they contain only the strings that need to be translated.</li><br />
<li>Translator works with those strings using the process bellow.</li><br />
<li>When the translator finishes a language, the git hub mantainers proceed to download the generated <code>*.po</code> files that contain the translated strings and commit them in git hub and update the documentation page.</li><br />
<li><p>Users can create their translation using:</p><br />
<p>tools/transifex/create_translation.sh fr</p></li></ul><br />
<br />
Translations to French are going to be used as examples along this wiki, we choose French so you can focus on what is being translated and what is not.<br />
<br />
== Before you start ==<br />
<br />
=== Prepare your clone for documentation ===<br />
<br />
<pre><br />
## Prepare the directory<br />
git clone https://github.com/OSGeo/OSGeoLive-doc docClone<br />
cd docClone<br />
git checkout develop ## new things come into develop, then are merged into master<br />
mkdir build<br />
cd build<br />
<br />
## prepare the documentation for French (English is automatically build)<br />
cmake -DHTML=ON -DFR=ON .. <br />
## Build the doc<br />
make doc<br />
cd ..</pre><br />
<br />
=== Downloading translation ===<br />
<br />
* To download a particular file.<br />
<br />
Best when reviewing the file:<br />
<br />
<pre><br />
tx pull -l fr -r osgeolive.quickstart--ideditor_quickstart<br />
</pre><br />
<br />
* Download the latest translated <code>*.po</code> files of your language based on translation percentage.<br />
<br />
<pre><br />
tx pull -l fr --minimum-perc=100<br />
</pre><br />
<br />
<br />
* Ask for help:<br />
<br />
<pre><br />
tx pull --help<br />
</pre><br />
<br />
==== Checking the download ====<br />
<br />
<pre><br />
git status<br />
</pre><br />
<br />
A possible output:<br />
<br />
=== Have your language documentation html open. ===<br />
<br />
Viewing your language html will help to put strings in context and/or check the translation.<br />
<br />
<pre>tools/transifex/create_translations.sh fr</pre><br />
The French documentation would be in<br />
<br />
<pre>build/doc/html/fr/doc/index.html</pre><br />
<br />
=== Transifex files that are not accepting translations. ===<br />
<br />
Files not accepting translations are marked with a red dot, maybe the file belongs to a previous version of OSGeo-Live documentation, or it was moved from one directory to another. Those files are not erased from the system so any translated string can be reused.<br />
<br />
=== English spelling and grammar ===<br />
<br />
Sometimes the developers and the reviewers have typos in the English version, you will see spelling typos with a wavy red line, unfortunately it is too late to correct them for the current version. So proceed with the translation with the best of your ability. For the grammar, if you don't understand what is being told, please go to [https://github.com/pgRouting/pgrouting/issues/200 issue 200] to post a comment stating the file and pasting the English string. If a change has been considered, the string to be translated will be posted on the &quot;instructions&quot; for the string.<br />
<br />
== Working with small strings ==<br />
<br />
=== Choose the small files first. ===<br />
<br />
For &quot;small&quot; I mean the ones that have very few strings to be translated. That will start building up a bank of translated strings that can be used in larger files. To detect a &quot;small&quot; file go to the list of [resources] (https://www.transifex.com/projects/p/pgrouting/resources/) and choose a file with few words or few strings.<br />
<br />
=== Use &quot;translate&quot; button ===<br />
<br />
The &quot;translate button&quot; comes quite handy, you still have to check the translation, and there is an &quot;undo&quot; button if you think that its better for you to type the translation than to modify the machine's translation.<br />
<br />
Don't use &quot;translate&quot; button on stand alone references like<br />
<br />
<pre>en: :ref:`sample`<br />
ja: :ref:`サンプル` &lt;--- wrong</pre><br />
=== Use a &quot;suggestion&quot; ===<br />
<br />
When you work with transifex it builds up a translated string bank and it will show one or more suggestions. If the suggestion is very close to what is needed, use it, and change the translation to the final translation of the string. Example:<br />
<br />
<pre>en: :ref:`pgr_astar&lt;pgr_astar&gt;` - Shortest Path A*<br />
Use suggestion: pgr_astar - A*アルゴリズムを用いた最短経路探索<br />
Modify to: :ref:`pgr_astar&lt;pgr_astar&gt;` - A*アルゴリズムを用いた最短経路探索</pre><br />
=== Use &quot;copy button&quot; ===<br />
<br />
Copy the the stand alone references like<br />
<br />
<pre>en: :ref:`sample`<br />
ja: :ref:`sample`</pre><br />
=== Type a translation ===<br />
<br />
You can just type your translation.<br />
<br />
=== Go to the next string ===<br />
<br />
When you finished translating the string press &quot;tab&quot;, that way it get's saved, if you click to a different string, maybe because the next string is already translated, then it won't be saved (green/white stripes).<br />
<br />
=== Save your translation ===<br />
<br />
Make sure all strings using the &quot;Save all unsaved translations&quot; button.<br />
<br />
== Check your work ==<br />
<br />
This step is needed not to check the translation but to check that ReStructuredText in the translated strings is correct. Many things might be wrong, an extra space, a missing space or a missing character &quot;`&quot; .<br />
<br />
=== Download the translated file and recreate the translation ===<br />
<br />
If the file you modified in transifex is doc--src--changelog--index and want to check the Japanese translation<br />
<br />
<pre>tools/transifex/download_translation.sh ja pgrouting.doc--src--changelog--index<br />
tools/transifex/create_translations.sh ja</pre><br />
Navigate to the the translated file, for this example it would be<br />
<br />
<pre>build/doc/html/ja/doc/src/changelog/index.html</pre><br />
Notice the relation between names:<br />
<br />
<pre>Transifex name: pgrouting.doc--src--changelog--index<br />
Html Generated File: build/doc/html/ja/doc/src/changelog/index.html</pre><br />
And visualy compare the &quot;looks&quot; with the [English version] (http://docs.pgrouting.org/2.0/en/doc/index.html)<br />
<br />
=== Use the &quot;Approve translation&quot; button ===<br />
<br />
When the file is fully translated (except the navigation bar), you can are about to approve the translation, '''????????'''<br />
<br />
* Check the links first, example: there is a link to sample data.<br />
<br />
Example:<br />
<br />
<pre>html: 上記クエリは サンプルデータ のネットワークを使用しています。 &lt;-- sample data is translated<br />
or: 上記クエリは Sample Data のネットワークを使用しています。 &lt;--- sample data needs translation</pre><br />
If you can navigate the links, you are ok<br />
<br />
* When using create_translation script there was no &quot;inline&quot; error (see [[Translation Troubleshooting]] ), you are ok<br />
<br />
If you are ok, then choose a string and click the &quot;Approve translation&quot; button.<br />
<br />
== Which file is next ==<br />
<br />
=== Do doc--index last ===<br />
<br />
That way you can use the &quot;Use suggestion&quot; in this file.<br />
<br />
=== Work &quot;important&quot; files first ===<br />
<br />
All files are important, but the following files are the core of the project. Most of them have repeated strings, so the &quot;Use Suggestion&quot; tactic is perfect, and you can use the search box to find them.<br />
<br />
- your project files: you know that project certainly better than us, especially in your language; starting by the overview then the quickstart<br />
- OSGeoLive files: there is several core files for the OSgeoLive documentation:<br />
- index<br />
- overview--overview<br />
- overview--toc<br />
- quickstart--virtualization_quickstart<br />
- quickstart--usb_quickstart<br />
- quickstart--osgeolive_quickstart<br />
- copyright<br />
- contributors<br />
- translators<br />
- presentation<br />
- sponsors<br />
<br />
etc<br />
<br />
They are listed with a red double ">" priority sign<br />
<br />
=== Work the &quot;almost finished&quot; files ===<br />
<br />
After you finish a file, you can choose a file that is &quot;almost done&quot;. I found pretty uncomfortable the list placed at the left, so to choose an almost done file I recommend:<br />
<br />
* Click Documentation<br />
* Click on your language<br />
* click on the sorting button (sorts by % of termination)<br />
<br />
This is very useful when you have a lot of files already translated<br />
<br />
=== Work files that belong to a directory ===<br />
<br />
Based on the following files:<br />
<br />
* doc--src--changelog--1_x ... 150 words (25 strings) ...<br />
* doc--src--changelog--2_0 ... 277 words (26 strings) ...<br />
* doc--src--changelog--index ... 4 words (3 strings) ...<br />
<br />
Maybe you started working with doc--src--changelog--index, so the next step would be to work with<br />
<br />
* doc--src--changelog--1_x<br />
* doc--src--changelog--2_0<br />
<br />
So you finished a section, go [[Translation Check your work]].<br />
<br />
= Troubleshooting =<br />
<br />
Please post any question in [https://github.com/pgRouting/pgrouting/issues/200 issue 200]<br />
<br />
=== The :ref:`nameoflink` link is not translated ===<br />
<br />
Example<br />
<br />
<pre>en: The queries use the :ref:`sampledata` network.<br />
ja: 上記クエリは :ref:`sampledata` のネットワークを使用しています。 <br />
html: 上記クエリは Sample Data のネットワークを使用しています。</pre><br />
Thats and indication that the referenced page for Sample Data, isn't fully translated. If you can click on the link and navigate you are ok.<br />
<br />
=== The :ref:`nameoflink` link is the only thing that is translated ===<br />
<br />
Example<br />
<br />
<pre>en: The queries use the :ref:`sampledata` network.<br />
ja: The queries use the :ref:`sampledata` network.<br />
html: The queries use the サンプルデータ network.</pre><br />
Maybe you navigated into an untranslated page that has a reference to a translated page.<br />
<br />
=== I don't see the link but I can read :ref: in the html page ===<br />
<br />
This is a common problem when using the translation button.<br /><br />
Example<br />
<br />
<pre>en: The queries use the :ref:`sampledata` network.<br />
ja: 上記クエリは: ref:'sampledata'のネットワークを使用しています。 <br />
html: 上記クエリは: ref:'sampledata'のネットワークを使用しています。</pre><br />
The link's generated by the button need to be corrected, I suggest to copy the link together with its sorrounding spaces from the English version:<br />
<br />
<pre> -------------------<br />
en: The queries use the :ref:`sampledata` network.<br />
ja: 上記クエリは :ref:`sampledata` のネットワークを使用しています。 <br />
html: 上記クエリは サンプルデータ のネットワークを使用しています。<br />
or: 上記クエリは Sample Data のネットワークを使用しています。</pre><br />
<br />
=== WARNING: Inline literal start-string without end-string. ===<br />
<br />
You will get this error is when using ''tools/transifex/create_translations.sh''. Languages like Japanese that don't use spaces to separate words are more likely to have this error. Unfortunately the error is shown only in line 1.<br />
<br />
Inline literals [specs] (http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#inline-markup) require a space before and after. The inline literals we use the most are of the type ``inlineliteral`` like in:<br />
<br />
<pre>``int4`` id of the end point<br />
``int4``型の始点ノードのID &lt;--- this will generate the error<br />
``int4 `` 型の始点ノードのID &lt;--- this will also generate the error (a space is after the 4)<br />
``int4`` 型の始点ノードのID &lt;--- a space is (before as a new line and) after the inline literal</pre><br />
= Tools for the Reviewer =<br />
<br />
=== tools/transifex/download_translation.sh ===<br />
<br />
Use to update the <code>*.po</code> files that are in your system with the latest translation stored in Transifex.<br /><br />
Languages available:<br />
<br />
* es - Spanish<br />
* fr - French<br />
* ja - Japanese<br />
* de - German<br />
<br />
tools/transifex/download_translation.sh [es|ja|fr|de] [pgrouting.&lt;filename&gt;]<br />
<br />
To download all language translations:<br />
<br />
<pre>tools/transifex/download_translation.sh</pre><br />
To download all the translations of a particular language:<br />
<br />
<pre>tools/transifex/download_translation.sh [es|ja|fr|de]</pre><br />
To download the translation of a specific file you need to state the language also<br />
<br />
<pre>tools/transifex/download_translation.sh [es|ja|fr|de] [pgrouting.&lt;filename&gt;]</pre><br />
<br />
=== tools/transifex/create_translations.sh ===<br />
<br />
Use to create: html, man, pdf documentation of the languages based on the <code>*.po</code> files stored in your system. Languages available:<br />
<br />
* es - Spanish<br />
* fr - French<br />
* ja - Japanese<br />
* de - German<br />
<br />
To create the documentation of all the languages<br />
<br />
<pre>tools/transifex/create_translations.sh</pre><br />
To create the documentation of a particular language:<br />
<br />
<pre>tools/transifex/create_translations.sh [es|ja|fr|de]</pre><br />
The main index.html of the documentation will be located at:<br />
<br />
<pre>build/doc/html/[es|ja|fr|de]/doc/index.html</pre><br />
<br />
= Main wiki page =<br />
<br />
* [https://wiki.osgeo.org/wiki/OSGeoLive OSGeoLive Wiki]<br />
<br />
<br />
[[Category: OSGeoLive]]</div>Bakanikohttps://wiki.osgeo.org/w/index.php?title=OSGeoLive_Translation_Process&diff=113833OSGeoLive Translation Process2018-02-27T21:19:36Z<p>Bakaniko: </p>
<hr />
<div><br />
This document is divided in two part, if you want to help us translate the OSGeoLive documentation, the first part will guide you through the Transifex platform. If you want to help us build it the second part will give you more technical information about Transifex, sphinx and the building process.<br />
<br />
__FORCETOC__<br />
<br />
= Translate on Transifex =<br />
<br />
Thanks for helping us translate the OSGeoLive project documentation !<br />
<br />
You can find us there: [https://www.transifex.com/osgeo/osgeolive/]<br />
<br />
== Available languages ==<br />
<br />
As for now (february 2018), there is 18 registered languages for the project. <br />
If your language is not in the list below (or on the updated list on Transifex),<br />
please make a request to add it !<br />
<br />
<br />
The list of [https://www.transifex.com/osgeo/osgeolive/languages/ Languages]:<br />
<br />
* Bengali<br />
* Catalan<br />
* Dutch<br />
* Finnish<br />
* French<br />
* German<br />
* Greek<br />
* Hindi<br />
* Hungarian<br />
* Italian <br />
* Japanese<br />
* Polish<br />
* Portuguese<br />
* Russian<br />
* Spanish<br />
* Mexican spanish<br />
<br />
<br />
== Connect to the Transifex platform == <br />
<br />
If you don't have an account, please create one and then go to the project page.<br />
<br />
Look for the language you want to help with (or ask to add it if it is not there already).<br />
<br />
<br />
<br />
<br />
== Files to translate ==<br />
The list of [https://www.transifex.com/osgeo/osgeolive/content/ resources]<br />
are classified as:<br />
* ">>" Urgent - OSGeo-Live related files<br />
<br />
[[File: OSGEo-Live_transifex_01_index.png | 500px ]]<br />
<br />
* "^" High - Projects related files<br />
<br />
[[File: OSGEo-Live_transifex_02_second_priority.png | 500px ]]<br />
<br />
* "-" Normal - Deprecated projects files (not for translating)<br />
<br />
[[File: OSGEo-Live_transifex_03_retired_files.png | 500px ]]<br />
<br />
You can easily order them by Version (v11) and and descending priority<br />
<br />
[[File : OSGEo-Live_transifex_04_priority.png | 500px ]]<br />
<br />
== Roles ==<br />
<br />
There is several roles where you can help us.<br />
<br />
=== Translator ===<br />
<br />
This role can translate strings, it is the most important job !<br />
<br />
=== Reviewer ===<br />
<br />
If your a confident enough in your languages and technical skills, you can become <br />
a reviewer and review strings to fix the possible typos. <br />
<br />
=== Language coordinator ===<br />
<br />
A coordinator can accept new Translator and grant Reviewer privileges. With a lot of different languages, <br />
it helps a lot the administrator.<br />
<br />
<br />
= Build the documentation =<br />
== The general process OSGeo-Live used for documentation: ==<br />
<br />
<ul><br />
<li>The developer use [http://docutils.sourceforge.net/docs/user/rst/quickstart.html ReStructuredText] syntax to write the documentation in English.</li><br />
<li>That documentation is then used with [http://sphinx-doc.org/contents.html Sphinx] to generate the english html, man, pdf, etc.</li><br />
<li>Also using [http://sphinx-doc.org/latest/intl.html Sphinx-intl] the <code>*.pot</code> files are generated.</li><br />
<li>Those <code>*.pot</code> files are used by [https://www.transifex.com/osgeo/osgeolive Transifex] and they contain only the strings that need to be translated.</li><br />
<li>Translator works with those strings using the process bellow.</li><br />
<li>When the translator finishes a language, the git hub mantainers proceed to download the generated <code>*.po</code> files that contain the translated strings and commit them in git hub and update the documentation page.</li><br />
<li><p>Users can create their translation using:</p><br />
<p>tools/transifex/create_translation.sh fr</p></li></ul><br />
<br />
Translations to French are going to be used as examples along this wiki, we choose French so you can focus on what is being translated and what is not.<br />
<br />
== Before you start ==<br />
<br />
=== Prepare your clone for documentation ===<br />
<br />
<pre><br />
## Prepare the directory<br />
git clone https://github.com/OSGeo/OSGeoLive-doc docClone<br />
cd docClone<br />
git checkout develop ## new things come into develop, then are merged into master<br />
mkdir build<br />
cd build<br />
<br />
## prepare the documentation for French (English is automatically build)<br />
cmake -DHTML=ON -DFR=ON .. <br />
## Build the doc<br />
make doc<br />
cd ..</pre><br />
<br />
=== Downloading translation ===<br />
<br />
* To download a particular file.<br />
<br />
Best when reviewing the file:<br />
<br />
<pre><br />
tx pull -l fr -r osgeolive.quickstart--ideditor_quickstart<br />
</pre><br />
<br />
* Download the latest translated <code>*.po</code> files of your language based on translation percentage.<br />
<br />
<pre><br />
tx pull -l fr --minimum-perc=100<br />
</pre><br />
<br />
<br />
* Ask for help:<br />
<br />
<pre><br />
tx pull --help<br />
</pre><br />
<br />
==== Checking the download ====<br />
<br />
<pre><br />
git status<br />
</pre><br />
<br />
A possible output:<br />
<br />
=== Have your language documentation html open. ===<br />
<br />
Viewing your language html will help to put strings in context and/or check the translation.<br />
<br />
<pre>tools/transifex/create_translations.sh fr</pre><br />
The French documentation would be in<br />
<br />
<pre>build/doc/html/fr/doc/index.html</pre><br />
<br />
=== Transifex files that are not accepting translations. ===<br />
<br />
Files not accepting translations are marked with a red dot, maybe the file belongs to a previous version of OSGeo-Live documentation, or it was moved from one directory to another. Those files are not erased from the system so any translated string can be reused.<br />
<br />
=== English spelling and grammar ===<br />
<br />
Sometimes the developers and the reviewers have typos in the English version, you will see spelling typos with a wavy red line, unfortunately it is too late to correct them for the current version. So proceed with the translation with the best of your ability. For the grammar, if you don't understand what is being told, please go to [https://github.com/pgRouting/pgrouting/issues/200 issue 200] to post a comment stating the file and pasting the English string. If a change has been considered, the string to be translated will be posted on the &quot;instructions&quot; for the string.<br />
<br />
== Working with small strings ==<br />
<br />
=== Choose the small files first. ===<br />
<br />
For &quot;small&quot; I mean the ones that have very few strings to be translated. That will start building up a bank of translated strings that can be used in larger files. To detect a &quot;small&quot; file go to the list of [resources] (https://www.transifex.com/projects/p/pgrouting/resources/) and choose a file with few words or few strings.<br />
<br />
=== Use &quot;translate&quot; button ===<br />
<br />
The &quot;translate button&quot; comes quite handy, you still have to check the translation, and there is an &quot;undo&quot; button if you think that its better for you to type the translation than to modify the machine's translation.<br />
<br />
Don't use &quot;translate&quot; button on stand alone references like<br />
<br />
<pre>en: :ref:`sample`<br />
ja: :ref:`サンプル` &lt;--- wrong</pre><br />
=== Use a &quot;suggestion&quot; ===<br />
<br />
When you work with transifex it builds up a translated string bank and it will show one or more suggestions. If the suggestion is very close to what is needed, use it, and change the translation to the final translation of the string. Example:<br />
<br />
<pre>en: :ref:`pgr_astar&lt;pgr_astar&gt;` - Shortest Path A*<br />
Use suggestion: pgr_astar - A*アルゴリズムを用いた最短経路探索<br />
Modify to: :ref:`pgr_astar&lt;pgr_astar&gt;` - A*アルゴリズムを用いた最短経路探索</pre><br />
=== Use &quot;copy button&quot; ===<br />
<br />
Copy the the stand alone references like<br />
<br />
<pre>en: :ref:`sample`<br />
ja: :ref:`sample`</pre><br />
=== Type a translation ===<br />
<br />
You can just type your translation.<br />
<br />
=== Go to the next string ===<br />
<br />
When you finished translating the string press &quot;tab&quot;, that way it get's saved, if you click to a different string, maybe because the next string is already translated, then it won't be saved (green/white stripes).<br />
<br />
=== Save your translation ===<br />
<br />
Make sure all strings using the &quot;Save all unsaved translations&quot; button.<br />
<br />
== Check your work ==<br />
<br />
This step is needed not to check the translation but to check that ReStructuredText in the translated strings is correct. Many things might be wrong, an extra space, a missing space or a missing character &quot;`&quot; .<br />
<br />
=== Download the translated file and recreate the translation ===<br />
<br />
If the file you modified in transifex is doc--src--changelog--index and want to check the Japanese translation<br />
<br />
<pre>tools/transifex/download_translation.sh ja pgrouting.doc--src--changelog--index<br />
tools/transifex/create_translations.sh ja</pre><br />
Navigate to the the translated file, for this example it would be<br />
<br />
<pre>build/doc/html/ja/doc/src/changelog/index.html</pre><br />
Notice the relation between names:<br />
<br />
<pre>Transifex name: pgrouting.doc--src--changelog--index<br />
Html Generated File: build/doc/html/ja/doc/src/changelog/index.html</pre><br />
And visualy compare the &quot;looks&quot; with the [English version] (http://docs.pgrouting.org/2.0/en/doc/index.html)<br />
<br />
=== Use the &quot;Approve translation&quot; button ===<br />
<br />
When the file is fully translated (except the navigation bar), you can are about to approve the translation, '''????????'''<br />
<br />
* Check the links first, example: there is a link to sample data.<br />
<br />
Example:<br />
<br />
<pre>html: 上記クエリは サンプルデータ のネットワークを使用しています。 &lt;-- sample data is translated<br />
or: 上記クエリは Sample Data のネットワークを使用しています。 &lt;--- sample data needs translation</pre><br />
If you can navigate the links, you are ok<br />
<br />
* When using create_translation script there was no &quot;inline&quot; error (see [[Translation Troubleshooting]] ), you are ok<br />
<br />
If you are ok, then choose a string and click the &quot;Approve translation&quot; button.<br />
<br />
== Which file is next ==<br />
<br />
=== Do doc--index last ===<br />
<br />
That way you can use the &quot;Use suggestion&quot; in this file.<br />
<br />
=== Work &quot;important&quot; files first ===<br />
<br />
All files are important, but the following files are the core of the project. Most of them have repeated strings, so the &quot;Use Suggestion&quot; tactic is perfect, and you can use the search box to find them.<br />
<br />
- your project files: you know that project certainly better than us, especially in your language; starting by the overview then the quickstart<br />
- OSGeoLive files: there is several core files for the OSgeoLive documentation:<br />
- index<br />
- overview--overview<br />
- overview--toc<br />
- quickstart--virtualization_quickstart<br />
- quickstart--usb_quickstart<br />
- quickstart--osgeolive_quickstart<br />
- copyright<br />
- contributors<br />
- translators<br />
- presentation<br />
- sponsors<br />
<br />
etc<br />
<br />
They are listed with a red double ">" priority sign<br />
<br />
=== Work the &quot;almost finished&quot; files ===<br />
<br />
After you finish a file, you can choose a file that is &quot;almost done&quot;. I found pretty uncomfortable the list placed at the left, so to choose an almost done file I recommend:<br />
<br />
* Click Documentation<br />
* Click on your language<br />
* click on the sorting button (sorts by % of termination)<br />
<br />
This is very useful when you have a lot of files already translated<br />
<br />
=== Work files that belong to a directory ===<br />
<br />
Based on the following files:<br />
<br />
* doc--src--changelog--1_x ... 150 words (25 strings) ...<br />
* doc--src--changelog--2_0 ... 277 words (26 strings) ...<br />
* doc--src--changelog--index ... 4 words (3 strings) ...<br />
<br />
Maybe you started working with doc--src--changelog--index, so the next step would be to work with<br />
<br />
* doc--src--changelog--1_x<br />
* doc--src--changelog--2_0<br />
<br />
So you finished a section, go [[Translation Check your work]].<br />
<br />
= Troubleshooting =<br />
<br />
Please post any question in [https://github.com/pgRouting/pgrouting/issues/200 issue 200]<br />
<br />
=== The :ref:`nameoflink` link is not translated ===<br />
<br />
Example<br />
<br />
<pre>en: The queries use the :ref:`sampledata` network.<br />
ja: 上記クエリは :ref:`sampledata` のネットワークを使用しています。 <br />
html: 上記クエリは Sample Data のネットワークを使用しています。</pre><br />
Thats and indication that the referenced page for Sample Data, isn't fully translated. If you can click on the link and navigate you are ok.<br />
<br />
=== The :ref:`nameoflink` link is the only thing that is translated ===<br />
<br />
Example<br />
<br />
<pre>en: The queries use the :ref:`sampledata` network.<br />
ja: The queries use the :ref:`sampledata` network.<br />
html: The queries use the サンプルデータ network.</pre><br />
Maybe you navigated into an untranslated page that has a reference to a translated page.<br />
<br />
=== I don't see the link but I can read :ref: in the html page ===<br />
<br />
This is a common problem when using the translation button.<br /><br />
Example<br />
<br />
<pre>en: The queries use the :ref:`sampledata` network.<br />
ja: 上記クエリは: ref:'sampledata'のネットワークを使用しています。 <br />
html: 上記クエリは: ref:'sampledata'のネットワークを使用しています。</pre><br />
The link's generated by the button need to be corrected, I suggest to copy the link together with its sorrounding spaces from the English version:<br />
<br />
<pre> -------------------<br />
en: The queries use the :ref:`sampledata` network.<br />
ja: 上記クエリは :ref:`sampledata` のネットワークを使用しています。 <br />
html: 上記クエリは サンプルデータ のネットワークを使用しています。<br />
or: 上記クエリは Sample Data のネットワークを使用しています。</pre><br />
<br />
=== WARNING: Inline literal start-string without end-string. ===<br />
<br />
You will get this error is when using ''tools/transifex/create_translations.sh''. Languages like Japanese that don't use spaces to separate words are more likely to have this error. Unfortunately the error is shown only in line 1.<br />
<br />
Inline literals [specs] (http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#inline-markup) require a space before and after. The inline literals we use the most are of the type ``inlineliteral`` like in:<br />
<br />
<pre>``int4`` id of the end point<br />
``int4``型の始点ノードのID &lt;--- this will generate the error<br />
``int4 `` 型の始点ノードのID &lt;--- this will also generate the error (a space is after the 4)<br />
``int4`` 型の始点ノードのID &lt;--- a space is (before as a new line and) after the inline literal</pre><br />
= Tools for the Reviewer =<br />
<br />
=== tools/transifex/download_translation.sh ===<br />
<br />
Use to update the <code>*.po</code> files that are in your system with the latest translation stored in Transifex.<br /><br />
Languages available:<br />
<br />
* es - Spanish<br />
* fr - French<br />
* ja - Japanese<br />
* de - German<br />
<br />
tools/transifex/download_translation.sh [es|ja|fr|de] [pgrouting.&lt;filename&gt;]<br />
<br />
To download all language translations:<br />
<br />
<pre>tools/transifex/download_translation.sh</pre><br />
To download all the translations of a particular language:<br />
<br />
<pre>tools/transifex/download_translation.sh [es|ja|fr|de]</pre><br />
To download the translation of a specific file you need to state the language also<br />
<br />
<pre>tools/transifex/download_translation.sh [es|ja|fr|de] [pgrouting.&lt;filename&gt;]</pre><br />
<br />
=== tools/transifex/create_translations.sh ===<br />
<br />
Use to create: html, man, pdf documentation of the languages based on the <code>*.po</code> files stored in your system. Languages available:<br />
<br />
* es - Spanish<br />
* fr - French<br />
* ja - Japanese<br />
* de - German<br />
<br />
To create the documentation of all the languages<br />
<br />
<pre>tools/transifex/create_translations.sh</pre><br />
To create the documentation of a particular language:<br />
<br />
<pre>tools/transifex/create_translations.sh [es|ja|fr|de]</pre><br />
The main index.html of the documentation will be located at:<br />
<br />
<pre>build/doc/html/[es|ja|fr|de]/doc/index.html</pre><br />
<br />
= Main wiki page =<br />
<br />
* [https://wiki.osgeo.org/wiki/OSGeoLive OSGeoLive Wiki]<br />
<br />
<br />
[[Category: OSGeoLive]]</div>Bakanikohttps://wiki.osgeo.org/w/index.php?title=OSGeoLive_Translation_Process&diff=113832OSGeoLive Translation Process2018-02-27T21:19:00Z<p>Bakaniko: </p>
<hr />
<div><br />
This document is divided in two part, if you want to help us translate the OSGeoLive documentation, the first part will guide you through the Transifex platform. If you want to help us build it the second part will give you more technical information about Transifex, sphinx and the building process.<br />
<br />
__FORCETOC__<br />
<br />
= Translate on Transifex =<br />
<br />
Thanks for helping us translate the OSGeoLive project documentation !<br />
<br />
You can find us there: [https://www.transifex.com/osgeo/osgeolive/]<br />
<br />
== Available languages ==<br />
<br />
As for now (february 2018), there is 18 registered languages for the project. <br />
If your language is not in the list below (or on the updated list on Transifex),<br />
please make a request to add it !<br />
<br />
<br />
The list of [https://www.transifex.com/osgeo/osgeolive/languages/ Languages]:<br />
<br />
* Bengali<br />
* Catalan<br />
* Dutch<br />
* Finnish<br />
* French<br />
* German<br />
* Greek<br />
* Hindi<br />
* Hungarian<br />
* Italian <br />
* Japanese<br />
* Polish<br />
* Portuguese<br />
* Russian<br />
* Spanish<br />
* Mexican spanish<br />
<br />
<br />
== Connect to the Transifex platform == <br />
<br />
If you don't have an account, please create one and then go to the project page.<br />
<br />
Look for the language you want to help with (or ask to add it if it is not there already).<br />
<br />
<br />
<br />
<br />
== Files to translate ==<br />
The list of [https://www.transifex.com/osgeo/osgeolive/content/ resources]<br />
are classified as:<br />
* ">>" Urgent - OSGeo-Live related files<br />
<br />
[[File: OSGEo-Live_transifex_01_index.png | 500px ]]<br />
<br />
* "^" High - Projects related files<br />
<br />
[[File: OSGEo-Live_transifex_02_second_priority.png | 500px ]]<br />
<br />
* "-" Normal - Deprecated projects files (not for translating)<br />
<br />
[[File: OSGEo-Live_transifex_03_retired_files.png | 500px ]]<br />
<br />
You can easily order them by Version (v11) and and descending priority<br />
<br />
[[File : OSGEo-Live_transifex_04_priority.png | 500px ]]<br />
<br />
== Roles ==<br />
<br />
There is several roles where you can help us.<br />
<br />
== Translator ==<br />
<br />
This role can translate strings, it is the most important job !<br />
<br />
== Reviewer ==<br />
<br />
If your a confident enough in your languages and technical skills, you can become <br />
a reviewer and review strings to fix the possible typos. <br />
<br />
== Language coordinator ==<br />
<br />
A coordinator can accept new Translator and grant Reviewer privileges. With a lot of different languages, <br />
it helps a lot the administrator.<br />
<br />
<br />
= Build the documentation =<br />
== The general process OSGeo-Live used for documentation: ==<br />
<br />
<ul><br />
<li>The developer use [http://docutils.sourceforge.net/docs/user/rst/quickstart.html ReStructuredText] syntax to write the documentation in English.</li><br />
<li>That documentation is then used with [http://sphinx-doc.org/contents.html Sphinx] to generate the english html, man, pdf, etc.</li><br />
<li>Also using [http://sphinx-doc.org/latest/intl.html Sphinx-intl] the <code>*.pot</code> files are generated.</li><br />
<li>Those <code>*.pot</code> files are used by [https://www.transifex.com/osgeo/osgeolive Transifex] and they contain only the strings that need to be translated.</li><br />
<li>Translator works with those strings using the process bellow.</li><br />
<li>When the translator finishes a language, the git hub mantainers proceed to download the generated <code>*.po</code> files that contain the translated strings and commit them in git hub and update the documentation page.</li><br />
<li><p>Users can create their translation using:</p><br />
<p>tools/transifex/create_translation.sh fr</p></li></ul><br />
<br />
Translations to French are going to be used as examples along this wiki, we choose French so you can focus on what is being translated and what is not.<br />
<br />
== Before you start ==<br />
<br />
=== Prepare your clone for documentation ===<br />
<br />
<pre><br />
## Prepare the directory<br />
git clone https://github.com/OSGeo/OSGeoLive-doc docClone<br />
cd docClone<br />
git checkout develop ## new things come into develop, then are merged into master<br />
mkdir build<br />
cd build<br />
<br />
## prepare the documentation for French (English is automatically build)<br />
cmake -DHTML=ON -DFR=ON .. <br />
## Build the doc<br />
make doc<br />
cd ..</pre><br />
<br />
=== Downloading translation ===<br />
<br />
* To download a particular file.<br />
<br />
Best when reviewing the file:<br />
<br />
<pre><br />
tx pull -l fr -r osgeolive.quickstart--ideditor_quickstart<br />
</pre><br />
<br />
* Download the latest translated <code>*.po</code> files of your language based on translation percentage.<br />
<br />
<pre><br />
tx pull -l fr --minimum-perc=100<br />
</pre><br />
<br />
<br />
* Ask for help:<br />
<br />
<pre><br />
tx pull --help<br />
</pre><br />
<br />
==== Checking the download ====<br />
<br />
<pre><br />
git status<br />
</pre><br />
<br />
A possible output:<br />
<br />
=== Have your language documentation html open. ===<br />
<br />
Viewing your language html will help to put strings in context and/or check the translation.<br />
<br />
<pre>tools/transifex/create_translations.sh fr</pre><br />
The French documentation would be in<br />
<br />
<pre>build/doc/html/fr/doc/index.html</pre><br />
<br />
=== Transifex files that are not accepting translations. ===<br />
<br />
Files not accepting translations are marked with a red dot, maybe the file belongs to a previous version of OSGeo-Live documentation, or it was moved from one directory to another. Those files are not erased from the system so any translated string can be reused.<br />
<br />
=== English spelling and grammar ===<br />
<br />
Sometimes the developers and the reviewers have typos in the English version, you will see spelling typos with a wavy red line, unfortunately it is too late to correct them for the current version. So proceed with the translation with the best of your ability. For the grammar, if you don't understand what is being told, please go to [https://github.com/pgRouting/pgrouting/issues/200 issue 200] to post a comment stating the file and pasting the English string. If a change has been considered, the string to be translated will be posted on the &quot;instructions&quot; for the string.<br />
<br />
== Working with small strings ==<br />
<br />
=== Choose the small files first. ===<br />
<br />
For &quot;small&quot; I mean the ones that have very few strings to be translated. That will start building up a bank of translated strings that can be used in larger files. To detect a &quot;small&quot; file go to the list of [resources] (https://www.transifex.com/projects/p/pgrouting/resources/) and choose a file with few words or few strings.<br />
<br />
=== Use &quot;translate&quot; button ===<br />
<br />
The &quot;translate button&quot; comes quite handy, you still have to check the translation, and there is an &quot;undo&quot; button if you think that its better for you to type the translation than to modify the machine's translation.<br />
<br />
Don't use &quot;translate&quot; button on stand alone references like<br />
<br />
<pre>en: :ref:`sample`<br />
ja: :ref:`サンプル` &lt;--- wrong</pre><br />
=== Use a &quot;suggestion&quot; ===<br />
<br />
When you work with transifex it builds up a translated string bank and it will show one or more suggestions. If the suggestion is very close to what is needed, use it, and change the translation to the final translation of the string. Example:<br />
<br />
<pre>en: :ref:`pgr_astar&lt;pgr_astar&gt;` - Shortest Path A*<br />
Use suggestion: pgr_astar - A*アルゴリズムを用いた最短経路探索<br />
Modify to: :ref:`pgr_astar&lt;pgr_astar&gt;` - A*アルゴリズムを用いた最短経路探索</pre><br />
=== Use &quot;copy button&quot; ===<br />
<br />
Copy the the stand alone references like<br />
<br />
<pre>en: :ref:`sample`<br />
ja: :ref:`sample`</pre><br />
=== Type a translation ===<br />
<br />
You can just type your translation.<br />
<br />
=== Go to the next string ===<br />
<br />
When you finished translating the string press &quot;tab&quot;, that way it get's saved, if you click to a different string, maybe because the next string is already translated, then it won't be saved (green/white stripes).<br />
<br />
=== Save your translation ===<br />
<br />
Make sure all strings using the &quot;Save all unsaved translations&quot; button.<br />
<br />
== Check your work ==<br />
<br />
This step is needed not to check the translation but to check that ReStructuredText in the translated strings is correct. Many things might be wrong, an extra space, a missing space or a missing character &quot;`&quot; .<br />
<br />
=== Download the translated file and recreate the translation ===<br />
<br />
If the file you modified in transifex is doc--src--changelog--index and want to check the Japanese translation<br />
<br />
<pre>tools/transifex/download_translation.sh ja pgrouting.doc--src--changelog--index<br />
tools/transifex/create_translations.sh ja</pre><br />
Navigate to the the translated file, for this example it would be<br />
<br />
<pre>build/doc/html/ja/doc/src/changelog/index.html</pre><br />
Notice the relation between names:<br />
<br />
<pre>Transifex name: pgrouting.doc--src--changelog--index<br />
Html Generated File: build/doc/html/ja/doc/src/changelog/index.html</pre><br />
And visualy compare the &quot;looks&quot; with the [English version] (http://docs.pgrouting.org/2.0/en/doc/index.html)<br />
<br />
=== Use the &quot;Approve translation&quot; button ===<br />
<br />
When the file is fully translated (except the navigation bar), you can are about to approve the translation, '''????????'''<br />
<br />
* Check the links first, example: there is a link to sample data.<br />
<br />
Example:<br />
<br />
<pre>html: 上記クエリは サンプルデータ のネットワークを使用しています。 &lt;-- sample data is translated<br />
or: 上記クエリは Sample Data のネットワークを使用しています。 &lt;--- sample data needs translation</pre><br />
If you can navigate the links, you are ok<br />
<br />
* When using create_translation script there was no &quot;inline&quot; error (see [[Translation Troubleshooting]] ), you are ok<br />
<br />
If you are ok, then choose a string and click the &quot;Approve translation&quot; button.<br />
<br />
== Which file is next ==<br />
<br />
=== Do doc--index last ===<br />
<br />
That way you can use the &quot;Use suggestion&quot; in this file.<br />
<br />
=== Work &quot;important&quot; files first ===<br />
<br />
All files are important, but the following files are the core of the project. Most of them have repeated strings, so the &quot;Use Suggestion&quot; tactic is perfect, and you can use the search box to find them.<br />
<br />
- your project files: you know that project certainly better than us, especially in your language; starting by the overview then the quickstart<br />
- OSGeoLive files: there is several core files for the OSgeoLive documentation:<br />
- index<br />
- overview--overview<br />
- overview--toc<br />
- quickstart--virtualization_quickstart<br />
- quickstart--usb_quickstart<br />
- quickstart--osgeolive_quickstart<br />
- copyright<br />
- contributors<br />
- translators<br />
- presentation<br />
- sponsors<br />
<br />
etc<br />
<br />
They are listed with a red double ">" priority sign<br />
<br />
=== Work the &quot;almost finished&quot; files ===<br />
<br />
After you finish a file, you can choose a file that is &quot;almost done&quot;. I found pretty uncomfortable the list placed at the left, so to choose an almost done file I recommend:<br />
<br />
* Click Documentation<br />
* Click on your language<br />
* click on the sorting button (sorts by % of termination)<br />
<br />
This is very useful when you have a lot of files already translated<br />
<br />
=== Work files that belong to a directory ===<br />
<br />
Based on the following files:<br />
<br />
* doc--src--changelog--1_x ... 150 words (25 strings) ...<br />
* doc--src--changelog--2_0 ... 277 words (26 strings) ...<br />
* doc--src--changelog--index ... 4 words (3 strings) ...<br />
<br />
Maybe you started working with doc--src--changelog--index, so the next step would be to work with<br />
<br />
* doc--src--changelog--1_x<br />
* doc--src--changelog--2_0<br />
<br />
So you finished a section, go [[Translation Check your work]].<br />
<br />
= Troubleshooting =<br />
<br />
Please post any question in [https://github.com/pgRouting/pgrouting/issues/200 issue 200]<br />
<br />
=== The :ref:`nameoflink` link is not translated ===<br />
<br />
Example<br />
<br />
<pre>en: The queries use the :ref:`sampledata` network.<br />
ja: 上記クエリは :ref:`sampledata` のネットワークを使用しています。 <br />
html: 上記クエリは Sample Data のネットワークを使用しています。</pre><br />
Thats and indication that the referenced page for Sample Data, isn't fully translated. If you can click on the link and navigate you are ok.<br />
<br />
=== The :ref:`nameoflink` link is the only thing that is translated ===<br />
<br />
Example<br />
<br />
<pre>en: The queries use the :ref:`sampledata` network.<br />
ja: The queries use the :ref:`sampledata` network.<br />
html: The queries use the サンプルデータ network.</pre><br />
Maybe you navigated into an untranslated page that has a reference to a translated page.<br />
<br />
=== I don't see the link but I can read :ref: in the html page ===<br />
<br />
This is a common problem when using the translation button.<br /><br />
Example<br />
<br />
<pre>en: The queries use the :ref:`sampledata` network.<br />
ja: 上記クエリは: ref:'sampledata'のネットワークを使用しています。 <br />
html: 上記クエリは: ref:'sampledata'のネットワークを使用しています。</pre><br />
The link's generated by the button need to be corrected, I suggest to copy the link together with its sorrounding spaces from the English version:<br />
<br />
<pre> -------------------<br />
en: The queries use the :ref:`sampledata` network.<br />
ja: 上記クエリは :ref:`sampledata` のネットワークを使用しています。 <br />
html: 上記クエリは サンプルデータ のネットワークを使用しています。<br />
or: 上記クエリは Sample Data のネットワークを使用しています。</pre><br />
<br />
=== WARNING: Inline literal start-string without end-string. ===<br />
<br />
You will get this error is when using ''tools/transifex/create_translations.sh''. Languages like Japanese that don't use spaces to separate words are more likely to have this error. Unfortunately the error is shown only in line 1.<br />
<br />
Inline literals [specs] (http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#inline-markup) require a space before and after. The inline literals we use the most are of the type ``inlineliteral`` like in:<br />
<br />
<pre>``int4`` id of the end point<br />
``int4``型の始点ノードのID &lt;--- this will generate the error<br />
``int4 `` 型の始点ノードのID &lt;--- this will also generate the error (a space is after the 4)<br />
``int4`` 型の始点ノードのID &lt;--- a space is (before as a new line and) after the inline literal</pre><br />
= Tools for the Reviewer =<br />
<br />
=== tools/transifex/download_translation.sh ===<br />
<br />
Use to update the <code>*.po</code> files that are in your system with the latest translation stored in Transifex.<br /><br />
Languages available:<br />
<br />
* es - Spanish<br />
* fr - French<br />
* ja - Japanese<br />
* de - German<br />
<br />
tools/transifex/download_translation.sh [es|ja|fr|de] [pgrouting.&lt;filename&gt;]<br />
<br />
To download all language translations:<br />
<br />
<pre>tools/transifex/download_translation.sh</pre><br />
To download all the translations of a particular language:<br />
<br />
<pre>tools/transifex/download_translation.sh [es|ja|fr|de]</pre><br />
To download the translation of a specific file you need to state the language also<br />
<br />
<pre>tools/transifex/download_translation.sh [es|ja|fr|de] [pgrouting.&lt;filename&gt;]</pre><br />
<br />
=== tools/transifex/create_translations.sh ===<br />
<br />
Use to create: html, man, pdf documentation of the languages based on the <code>*.po</code> files stored in your system. Languages available:<br />
<br />
* es - Spanish<br />
* fr - French<br />
* ja - Japanese<br />
* de - German<br />
<br />
To create the documentation of all the languages<br />
<br />
<pre>tools/transifex/create_translations.sh</pre><br />
To create the documentation of a particular language:<br />
<br />
<pre>tools/transifex/create_translations.sh [es|ja|fr|de]</pre><br />
The main index.html of the documentation will be located at:<br />
<br />
<pre>build/doc/html/[es|ja|fr|de]/doc/index.html</pre><br />
<br />
= Main wiki page =<br />
<br />
* [https://wiki.osgeo.org/wiki/OSGeoLive OSGeoLive Wiki]<br />
<br />
<br />
[[Category: OSGeoLive]]</div>Bakanikohttps://wiki.osgeo.org/w/index.php?title=OSGeoLive_Translation_Process&diff=113817OSGeoLive Translation Process2018-02-26T20:07:06Z<p>Bakaniko: </p>
<hr />
<div>__FORCETOC__<br />
<br />
= Translate on Transifex =<br />
<br />
Documentation and tests are work in progress.<br />
<br />
This documentation might need adjustments to focus on the OSGeo Live Project.<br />
<br />
The list of [https://www.transifex.com/osgeo/osgeolive/content/ resources]<br />
are classified as:<br />
* ">>" Urgent - OSGeo-Live related files<br />
<br />
[[File: OSGEo-Live_transifex_01_index.png | 500px ]]<br />
<br />
* "^" High - Projects related files<br />
<br />
[[File: OSGEo-Live_transifex_02_second_priority.png | 500px ]]<br />
<br />
* "-" Normal - Deprecated projects files (not for translating)<br />
<br />
[[File: OSGEo-Live_transifex_03_retired_files.png | 500px ]]<br />
<br />
You can easily order them by Version (v11) and and descending priority<br />
<br />
[[File : OSGEo-Live_transifex_04_priority.png | 500px ]]<br />
<br />
The list of [https://www.transifex.com/osgeo/osgeolive/languages/ Languages]<br />
* Finnish<br />
* French<br />
* German<br />
* Greek<br />
* Japanese<br />
* Polish<br />
* Spanish<br />
* Mexican spanish<br />
<br />
= Build the documentation =<br />
== The general process OSGeo-Live used for documentation: ==<br />
<br />
<ul><br />
<li>The developer use [http://docutils.sourceforge.net/docs/user/rst/quickstart.html ReStructuredText] syntax to write the documentation in English.</li><br />
<li>That documentation is then used with [http://sphinx-doc.org/contents.html Sphinx] to generate the english html, man, pdf, etc.</li><br />
<li>Also using [http://sphinx-doc.org/latest/intl.html Sphinx-intl] the <code>*.pot</code> files are generated.</li><br />
<li>Those <code>*.pot</code> files are used by [https://www.transifex.com/osgeo/osgeolive Transifex] and they contain only the strings that need to be translated.</li><br />
<li>Translator works with those strings using the process bellow.</li><br />
<li>When the translator finishes a language, the git hub mantainers proceed to download the generated <code>*.po</code> files that contain the translated strings and commit them in git hub and update the documentation page.</li><br />
<li><p>Users can create their translation using:</p><br />
<p>tools/transifex/create_translation.sh fr</p></li></ul><br />
<br />
Translations to French are going to be used as examples along this wiki, we choose French so you can focus on what is being translated and what is not.<br />
<br />
== Before you start ==<br />
<br />
=== Prepare your clone for documentation ===<br />
<br />
<pre><br />
## Prepare the directory<br />
git clone https://github.com/OSGeo/OSGeoLive-doc docClone<br />
cd docClone<br />
git checkout develop ## new things come into develop, then are merged into master<br />
mkdir build<br />
cd build<br />
<br />
## prepare the documentation for French (English is automatically build)<br />
cmake -DHTML=ON -DFR=ON .. <br />
## Build the doc<br />
make doc<br />
cd ..</pre><br />
<br />
=== Downloading translation ===<br />
<br />
* To download a particular file.<br />
<br />
Best when reviewing the file:<br />
<br />
<pre><br />
tx pull -l fr -r osgeolive.quickstart--ideditor_quickstart<br />
</pre><br />
<br />
* Download the latest translated <code>*.po</code> files of your language based on translation percentage.<br />
<br />
<pre><br />
tx pull -l fr --minimum-perc=100<br />
</pre><br />
<br />
<br />
* Ask for help:<br />
<br />
<pre><br />
tx pull --help<br />
</pre><br />
<br />
==== Checking the download ====<br />
<br />
<pre><br />
git status<br />
</pre><br />
<br />
A possible output:<br />
<br />
=== Have your language documentation html open. ===<br />
<br />
Viewing your language html will help to put strings in context and/or check the translation.<br />
<br />
<pre>tools/transifex/create_translations.sh fr</pre><br />
The French documentation would be in<br />
<br />
<pre>build/doc/html/fr/doc/index.html</pre><br />
<br />
=== Transifex files that are not accepting translations. ===<br />
<br />
Files not accepting translations are marked with a red dot, maybe the file belongs to a previous version of OSGeo-Live documentation, or it was moved from one directory to another. Those files are not erased from the system so any translated string can be reused.<br />
<br />
=== English spelling and grammar ===<br />
<br />
Sometimes the developers and the reviewers have typos in the English version, you will see spelling typos with a wavy red line, unfortunately it is too late to correct them for the current version. So proceed with the translation with the best of your ability. For the grammar, if you don't understand what is being told, please go to [https://github.com/pgRouting/pgrouting/issues/200 issue 200] to post a comment stating the file and pasting the English string. If a change has been considered, the string to be translated will be posted on the &quot;instructions&quot; for the string.<br />
<br />
== Working with small strings ==<br />
<br />
=== Choose the small files first. ===<br />
<br />
For &quot;small&quot; I mean the ones that have very few strings to be translated. That will start building up a bank of translated strings that can be used in larger files. To detect a &quot;small&quot; file go to the list of [resources] (https://www.transifex.com/projects/p/pgrouting/resources/) and choose a file with few words or few strings.<br />
<br />
=== Use &quot;translate&quot; button ===<br />
<br />
The &quot;translate button&quot; comes quite handy, you still have to check the translation, and there is an &quot;undo&quot; button if you think that its better for you to type the translation than to modify the machine's translation.<br />
<br />
Don't use &quot;translate&quot; button on stand alone references like<br />
<br />
<pre>en: :ref:`sample`<br />
ja: :ref:`サンプル` &lt;--- wrong</pre><br />
=== Use a &quot;suggestion&quot; ===<br />
<br />
When you work with transifex it builds up a translated string bank and it will show one or more suggestions. If the suggestion is very close to what is needed, use it, and change the translation to the final translation of the string. Example:<br />
<br />
<pre>en: :ref:`pgr_astar&lt;pgr_astar&gt;` - Shortest Path A*<br />
Use suggestion: pgr_astar - A*アルゴリズムを用いた最短経路探索<br />
Modify to: :ref:`pgr_astar&lt;pgr_astar&gt;` - A*アルゴリズムを用いた最短経路探索</pre><br />
=== Use &quot;copy button&quot; ===<br />
<br />
Copy the the stand alone references like<br />
<br />
<pre>en: :ref:`sample`<br />
ja: :ref:`sample`</pre><br />
=== Type a translation ===<br />
<br />
You can just type your translation.<br />
<br />
=== Go to the next string ===<br />
<br />
When you finished translating the string press &quot;tab&quot;, that way it get's saved, if you click to a different string, maybe because the next string is already translated, then it won't be saved (green/white stripes).<br />
<br />
=== Save your translation ===<br />
<br />
Make sure all strings using the &quot;Save all unsaved translations&quot; button.<br />
<br />
== Check your work ==<br />
<br />
This step is needed not to check the translation but to check that ReStructuredText in the translated strings is correct. Many things might be wrong, an extra space, a missing space or a missing character &quot;`&quot; .<br />
<br />
=== Download the translated file and recreate the translation ===<br />
<br />
If the file you modified in transifex is doc--src--changelog--index and want to check the Japanese translation<br />
<br />
<pre>tools/transifex/download_translation.sh ja pgrouting.doc--src--changelog--index<br />
tools/transifex/create_translations.sh ja</pre><br />
Navigate to the the translated file, for this example it would be<br />
<br />
<pre>build/doc/html/ja/doc/src/changelog/index.html</pre><br />
Notice the relation between names:<br />
<br />
<pre>Transifex name: pgrouting.doc--src--changelog--index<br />
Html Generated File: build/doc/html/ja/doc/src/changelog/index.html</pre><br />
And visualy compare the &quot;looks&quot; with the [English version] (http://docs.pgrouting.org/2.0/en/doc/index.html)<br />
<br />
=== Use the &quot;Approve translation&quot; button ===<br />
<br />
When the file is fully translated (except the navigation bar), you can are about to approve the translation, '''????????'''<br />
<br />
* Check the links first, example: there is a link to sample data.<br />
<br />
Example:<br />
<br />
<pre>html: 上記クエリは サンプルデータ のネットワークを使用しています。 &lt;-- sample data is translated<br />
or: 上記クエリは Sample Data のネットワークを使用しています。 &lt;--- sample data needs translation</pre><br />
If you can navigate the links, you are ok<br />
<br />
* When using create_translation script there was no &quot;inline&quot; error (see [[Translation Troubleshooting]] ), you are ok<br />
<br />
If you are ok, then choose a string and click the &quot;Approve translation&quot; button.<br />
<br />
== Which file is next ==<br />
<br />
=== Do doc--index last ===<br />
<br />
That way you can use the &quot;Use suggestion&quot; in this file.<br />
<br />
=== Work &quot;important&quot; files first ===<br />
<br />
All files are important, but the following files are the core of the project. Most of them have repeated strings, so the &quot;Use Suggestion&quot; tactic is perfect, and you can use the search box to find them.<br />
<br />
- your project files: you know that project certainly better than us, especially in your language; starting by the overview then the quickstart<br />
- OSGeoLive files: there is several core files for the OSgeoLive documentation:<br />
- index<br />
- overview--overview<br />
- overview--toc<br />
- quickstart--virtualization_quickstart<br />
- quickstart--usb_quickstart<br />
- quickstart--osgeolive_quickstart<br />
- copyright<br />
- contributors<br />
- translators<br />
- presentation<br />
- sponsors<br />
<br />
etc<br />
<br />
They are listed with a red double ">" priority sign<br />
<br />
=== Work the &quot;almost finished&quot; files ===<br />
<br />
After you finish a file, you can choose a file that is &quot;almost done&quot;. I found pretty uncomfortable the list placed at the left, so to choose an almost done file I recommend:<br />
<br />
* Click Documentation<br />
* Click on your language<br />
* click on the sorting button (sorts by % of termination)<br />
<br />
This is very useful when you have a lot of files already translated<br />
<br />
=== Work files that belong to a directory ===<br />
<br />
Based on the following files:<br />
<br />
* doc--src--changelog--1_x ... 150 words (25 strings) ...<br />
* doc--src--changelog--2_0 ... 277 words (26 strings) ...<br />
* doc--src--changelog--index ... 4 words (3 strings) ...<br />
<br />
Maybe you started working with doc--src--changelog--index, so the next step would be to work with<br />
<br />
* doc--src--changelog--1_x<br />
* doc--src--changelog--2_0<br />
<br />
So you finished a section, go [[Translation Check your work]].<br />
<br />
= Troubleshooting =<br />
<br />
Please post any question in [https://github.com/pgRouting/pgrouting/issues/200 issue 200]<br />
<br />
=== The :ref:`nameoflink` link is not translated ===<br />
<br />
Example<br />
<br />
<pre>en: The queries use the :ref:`sampledata` network.<br />
ja: 上記クエリは :ref:`sampledata` のネットワークを使用しています。 <br />
html: 上記クエリは Sample Data のネットワークを使用しています。</pre><br />
Thats and indication that the referenced page for Sample Data, isn't fully translated. If you can click on the link and navigate you are ok.<br />
<br />
=== The :ref:`nameoflink` link is the only thing that is translated ===<br />
<br />
Example<br />
<br />
<pre>en: The queries use the :ref:`sampledata` network.<br />
ja: The queries use the :ref:`sampledata` network.<br />
html: The queries use the サンプルデータ network.</pre><br />
Maybe you navigated into an untranslated page that has a reference to a translated page.<br />
<br />
=== I don't see the link but I can read :ref: in the html page ===<br />
<br />
This is a common problem when using the translation button.<br /><br />
Example<br />
<br />
<pre>en: The queries use the :ref:`sampledata` network.<br />
ja: 上記クエリは: ref:'sampledata'のネットワークを使用しています。 <br />
html: 上記クエリは: ref:'sampledata'のネットワークを使用しています。</pre><br />
The link's generated by the button need to be corrected, I suggest to copy the link together with its sorrounding spaces from the English version:<br />
<br />
<pre> -------------------<br />
en: The queries use the :ref:`sampledata` network.<br />
ja: 上記クエリは :ref:`sampledata` のネットワークを使用しています。 <br />
html: 上記クエリは サンプルデータ のネットワークを使用しています。<br />
or: 上記クエリは Sample Data のネットワークを使用しています。</pre><br />
<br />
=== WARNING: Inline literal start-string without end-string. ===<br />
<br />
You will get this error is when using ''tools/transifex/create_translations.sh''. Languages like Japanese that don't use spaces to separate words are more likely to have this error. Unfortunately the error is shown only in line 1.<br />
<br />
Inline literals [specs] (http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#inline-markup) require a space before and after. The inline literals we use the most are of the type ``inlineliteral`` like in:<br />
<br />
<pre>``int4`` id of the end point<br />
``int4``型の始点ノードのID &lt;--- this will generate the error<br />
``int4 `` 型の始点ノードのID &lt;--- this will also generate the error (a space is after the 4)<br />
``int4`` 型の始点ノードのID &lt;--- a space is (before as a new line and) after the inline literal</pre><br />
= Tools for the Reviewer =<br />
<br />
=== tools/transifex/download_translation.sh ===<br />
<br />
Use to update the <code>*.po</code> files that are in your system with the latest translation stored in Transifex.<br /><br />
Languages available:<br />
<br />
* es - Spanish<br />
* fr - French<br />
* ja - Japanese<br />
* de - German<br />
<br />
tools/transifex/download_translation.sh [es|ja|fr|de] [pgrouting.&lt;filename&gt;]<br />
<br />
To download all language translations:<br />
<br />
<pre>tools/transifex/download_translation.sh</pre><br />
To download all the translations of a particular language:<br />
<br />
<pre>tools/transifex/download_translation.sh [es|ja|fr|de]</pre><br />
To download the translation of a specific file you need to state the language also<br />
<br />
<pre>tools/transifex/download_translation.sh [es|ja|fr|de] [pgrouting.&lt;filename&gt;]</pre><br />
<br />
=== tools/transifex/create_translations.sh ===<br />
<br />
Use to create: html, man, pdf documentation of the languages based on the <code>*.po</code> files stored in your system. Languages available:<br />
<br />
* es - Spanish<br />
* fr - French<br />
* ja - Japanese<br />
* de - German<br />
<br />
To create the documentation of all the languages<br />
<br />
<pre>tools/transifex/create_translations.sh</pre><br />
To create the documentation of a particular language:<br />
<br />
<pre>tools/transifex/create_translations.sh [es|ja|fr|de]</pre><br />
The main index.html of the documentation will be located at:<br />
<br />
<pre>build/doc/html/[es|ja|fr|de]/doc/index.html</pre><br />
<br />
= Main wiki page =<br />
<br />
* [https://wiki.osgeo.org/wiki/OSGeoLive OSGeoLive Wiki]<br />
<br />
<br />
[[Category: OSGeoLive]]</div>Bakanikohttps://wiki.osgeo.org/w/index.php?title=OSGeoLive_Translation_Process&diff=113816OSGeoLive Translation Process2018-02-26T20:05:22Z<p>Bakaniko: /* The general process OSGeo-Live used for documentation: */</p>
<hr />
<div>__FORCETOC__<br />
<br />
= Translate on Transifex =<br />
<br />
Documentation and tests are work in progress.<br />
<br />
This documentation might need adjustments to focus on the OSGeo Live Project.<br />
<br />
The list of [https://www.transifex.com/osgeo/osgeolive/content/ resources]<br />
are classified as:<br />
* ">>" Urgent - OSGeo-Live related files<br />
<br />
[[File: OSGEo-Live_transifex_01_index.png | 500px ]]<br />
<br />
* "^" High - Projects related files<br />
<br />
[[File: OSGEo-Live_transifex_02_second_priority.png | 500px ]]<br />
<br />
* "-" Normal - Deprecated projects files (not for translating)<br />
<br />
[[File: OSGEo-Live_transifex_03_retired_files.png | 500px ]]<br />
<br />
You can easily order them by Version (v11) and and descending priority<br />
<br />
[[File : OSGEo-Live_transifex_04_priority.png | 500px ]]<br />
<br />
The list of [https://www.transifex.com/osgeo/osgeolive/languages/ Languages]<br />
* Finnish<br />
* French<br />
* German<br />
* Greek<br />
* Japanese<br />
* Polish<br />
* Spanish<br />
* Mexican spanish<br />
<br />
= Build the documentation =<br />
== The general process OSGeo-Live used for documentation: ==<br />
<br />
<ul><br />
<li>The developer use [http://docutils.sourceforge.net/docs/user/rst/quickstart.html ReStructuredText] syntax to write the documentation in English.</li><br />
<li>That documentation is then used with [http://sphinx-doc.org/contents.html Sphinx] to generate the english html, man, pdf, etc.</li><br />
<li>Also using [http://sphinx-doc.org/latest/intl.html Sphinx-intl] the <code>*.pot</code> files are generated.</li><br />
<li>Those <code>*.pot</code> files are used by [https://www.transifex.com/osgeo/osgeolive Transifex] and they contain only the strings that need to be translated.</li><br />
<li>Translator works with those strings using the process bellow.</li><br />
<li>When the translator finishes a language, the git hub mantainers proceed to download the generated <code>*.po</code> files that contain the translated strings and commit them in git hub and update the documentation page.</li><br />
<li><p>Users can create their translation using:</p><br />
<p>tools/transifex/create_translation.sh fr</p></li></ul><br />
<br />
Translations to French are going to be used as examples along this wiki, we choose French so you can focus on what is being translated and what is not.<br />
<br />
= Before you start =<br />
<br />
== Prepare your clone for documentation ==<br />
<br />
<pre><br />
## Prepare the directory<br />
git clone https://github.com/OSGeo/OSGeoLive-doc docClone<br />
cd docClone<br />
git checkout develop ## new things come into develop, then are merged into master<br />
mkdir build<br />
cd build<br />
<br />
## prepare the documentation for French (English is automatically build)<br />
cmake -DHTML=ON -DFR=ON .. <br />
## Build the doc<br />
make doc<br />
cd ..</pre><br />
<br />
== Downloading translation ==<br />
<br />
* To download a particular file.<br />
<br />
Best when reviewing the file:<br />
<br />
<pre><br />
tx pull -l fr -r osgeolive.quickstart--ideditor_quickstart<br />
</pre><br />
<br />
* Download the latest translated <code>*.po</code> files of your language based on translation percentage.<br />
<br />
<pre><br />
tx pull -l fr --minimum-perc=100<br />
</pre><br />
<br />
<br />
* Ask for help:<br />
<br />
<pre><br />
tx pull --help<br />
</pre><br />
<br />
=== Checking the download ===<br />
<br />
<pre><br />
git status<br />
</pre><br />
<br />
A possible output:<br />
<br />
== Have your language documentation html open. ==<br />
<br />
Viewing your language html will help to put strings in context and/or check the translation.<br />
<br />
<pre>tools/transifex/create_translations.sh fr</pre><br />
The French documentation would be in<br />
<br />
<pre>build/doc/html/fr/doc/index.html</pre><br />
<br />
== Transifex files that are not accepting translations. ==<br />
<br />
Files not accepting translations are marked with a red dot, maybe the file belongs to a previous version of OSGeo-Live documentation, or it was moved from one directory to another. Those files are not erased from the system so any translated string can be reused.<br />
<br />
== English spelling and grammar ==<br />
<br />
Sometimes the developers and the reviewers have typos in the English version, you will see spelling typos with a wavy red line, unfortunately it is too late to correct them for the current version. So proceed with the translation with the best of your ability. For the grammar, if you don't understand what is being told, please go to [https://github.com/pgRouting/pgrouting/issues/200 issue 200] to post a comment stating the file and pasting the English string. If a change has been considered, the string to be translated will be posted on the &quot;instructions&quot; for the string.<br />
<br />
= Working with small strings =<br />
<br />
== Choose the small files first. ==<br />
<br />
For &quot;small&quot; I mean the ones that have very few strings to be translated. That will start building up a bank of translated strings that can be used in larger files. To detect a &quot;small&quot; file go to the list of [resources] (https://www.transifex.com/projects/p/pgrouting/resources/) and choose a file with few words or few strings.<br />
<br />
== Use &quot;translate&quot; button ==<br />
<br />
The &quot;translate button&quot; comes quite handy, you still have to check the translation, and there is an &quot;undo&quot; button if you think that its better for you to type the translation than to modify the machine's translation.<br />
<br />
Don't use &quot;translate&quot; button on stand alone references like<br />
<br />
<pre>en: :ref:`sample`<br />
ja: :ref:`サンプル` &lt;--- wrong</pre><br />
== Use a &quot;suggestion&quot; ==<br />
<br />
When you work with transifex it builds up a translated string bank and it will show one or more suggestions. If the suggestion is very close to what is needed, use it, and change the translation to the final translation of the string. Example:<br />
<br />
<pre>en: :ref:`pgr_astar&lt;pgr_astar&gt;` - Shortest Path A*<br />
Use suggestion: pgr_astar - A*アルゴリズムを用いた最短経路探索<br />
Modify to: :ref:`pgr_astar&lt;pgr_astar&gt;` - A*アルゴリズムを用いた最短経路探索</pre><br />
== Use &quot;copy button&quot; ==<br />
<br />
Copy the the stand alone references like<br />
<br />
<pre>en: :ref:`sample`<br />
ja: :ref:`sample`</pre><br />
== Type a translation ==<br />
<br />
You can just type your translation.<br />
<br />
== Go to the next string ==<br />
<br />
When you finished translating the string press &quot;tab&quot;, that way it get's saved, if you click to a different string, maybe because the next string is already translated, then it won't be saved (green/white stripes).<br />
<br />
== Save your translation ==<br />
<br />
Make sure all strings using the &quot;Save all unsaved translations&quot; button.<br />
<br />
= Check your work =<br />
<br />
This step is needed not to check the translation but to check that ReStructuredText in the translated strings is correct. Many things might be wrong, an extra space, a missing space or a missing character &quot;`&quot; .<br />
<br />
== Download the translated file and recreate the translation ==<br />
<br />
If the file you modified in transifex is doc--src--changelog--index and want to check the Japanese translation<br />
<br />
<pre>tools/transifex/download_translation.sh ja pgrouting.doc--src--changelog--index<br />
tools/transifex/create_translations.sh ja</pre><br />
Navigate to the the translated file, for this example it would be<br />
<br />
<pre>build/doc/html/ja/doc/src/changelog/index.html</pre><br />
Notice the relation between names:<br />
<br />
<pre>Transifex name: pgrouting.doc--src--changelog--index<br />
Html Generated File: build/doc/html/ja/doc/src/changelog/index.html</pre><br />
And visualy compare the &quot;looks&quot; with the [English version] (http://docs.pgrouting.org/2.0/en/doc/index.html)<br />
<br />
== Use the &quot;Approve translation&quot; button ==<br />
<br />
When the file is fully translated (except the navigation bar), you can are about to approve the translation, '''????????'''<br />
<br />
* Check the links first, example: there is a link to sample data.<br />
<br />
Example:<br />
<br />
<pre>html: 上記クエリは サンプルデータ のネットワークを使用しています。 &lt;-- sample data is translated<br />
or: 上記クエリは Sample Data のネットワークを使用しています。 &lt;--- sample data needs translation</pre><br />
If you can navigate the links, you are ok<br />
<br />
* When using create_translation script there was no &quot;inline&quot; error (see [[Translation Troubleshooting]] ), you are ok<br />
<br />
If you are ok, then choose a string and click the &quot;Approve translation&quot; button.<br />
<br />
= Which file is next =<br />
<br />
== Do doc--index last ==<br />
<br />
That way you can use the &quot;Use suggestion&quot; in this file.<br />
<br />
== Work &quot;important&quot; files first ==<br />
<br />
All files are important, but the following files are the core of the project. Most of them have repeated strings, so the &quot;Use Suggestion&quot; tactic is perfect, and you can use the search box to find them.<br />
<br />
- your project files: you know that project certainly better than us, especially in your language; starting by the overview then the quickstart<br />
- OSGeoLive files: there is several core files for the OSgeoLive documentation:<br />
- index<br />
- overview--overview<br />
- overview--toc<br />
- quickstart--virtualization_quickstart<br />
- quickstart--usb_quickstart<br />
- quickstart--osgeolive_quickstart<br />
- copyright<br />
- contributors<br />
- translators<br />
- presentation<br />
- sponsors<br />
<br />
etc<br />
<br />
They are listed with a red double ">" priority sign<br />
<br />
== Work the &quot;almost finished&quot; files ==<br />
<br />
After you finish a file, you can choose a file that is &quot;almost done&quot;. I found pretty uncomfortable the list placed at the left, so to choose an almost done file I recommend:<br />
<br />
* Click Documentation<br />
* Click on your language<br />
* click on the sorting button (sorts by % of termination)<br />
<br />
This is very useful when you have a lot of files already translated<br />
<br />
== Work files that belong to a directory ==<br />
<br />
Based on the following files:<br />
<br />
* doc--src--changelog--1_x ... 150 words (25 strings) ...<br />
* doc--src--changelog--2_0 ... 277 words (26 strings) ...<br />
* doc--src--changelog--index ... 4 words (3 strings) ...<br />
<br />
Maybe you started working with doc--src--changelog--index, so the next step would be to work with<br />
<br />
* doc--src--changelog--1_x<br />
* doc--src--changelog--2_0<br />
<br />
So you finished a section, go [[Translation Check your work]].<br />
<br />
= Troubleshooting =<br />
<br />
Please post any question in [https://github.com/pgRouting/pgrouting/issues/200 issue 200]<br />
<br />
== The :ref:`nameoflink` link is not translated ==<br />
<br />
Example<br />
<br />
<pre>en: The queries use the :ref:`sampledata` network.<br />
ja: 上記クエリは :ref:`sampledata` のネットワークを使用しています。 <br />
html: 上記クエリは Sample Data のネットワークを使用しています。</pre><br />
Thats and indication that the referenced page for Sample Data, isn't fully translated. If you can click on the link and navigate you are ok.<br />
<br />
== The :ref:`nameoflink` link is the only thing that is translated ==<br />
<br />
Example<br />
<br />
<pre>en: The queries use the :ref:`sampledata` network.<br />
ja: The queries use the :ref:`sampledata` network.<br />
html: The queries use the サンプルデータ network.</pre><br />
Maybe you navigated into an untranslated page that has a reference to a translated page.<br />
<br />
== I don't see the link but I can read :ref: in the html page ==<br />
<br />
This is a common problem when using the translation button.<br /><br />
Example<br />
<br />
<pre>en: The queries use the :ref:`sampledata` network.<br />
ja: 上記クエリは: ref:'sampledata'のネットワークを使用しています。 <br />
html: 上記クエリは: ref:'sampledata'のネットワークを使用しています。</pre><br />
The link's generated by the button need to be corrected, I suggest to copy the link together with its sorrounding spaces from the English version:<br />
<br />
<pre> -------------------<br />
en: The queries use the :ref:`sampledata` network.<br />
ja: 上記クエリは :ref:`sampledata` のネットワークを使用しています。 <br />
html: 上記クエリは サンプルデータ のネットワークを使用しています。<br />
or: 上記クエリは Sample Data のネットワークを使用しています。</pre><br />
<br />
== WARNING: Inline literal start-string without end-string. ==<br />
<br />
You will get this error is when using ''tools/transifex/create_translations.sh''. Languages like Japanese that don't use spaces to separate words are more likely to have this error. Unfortunately the error is shown only in line 1.<br />
<br />
Inline literals [specs] (http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#inline-markup) require a space before and after. The inline literals we use the most are of the type ``inlineliteral`` like in:<br />
<br />
<pre>``int4`` id of the end point<br />
``int4``型の始点ノードのID &lt;--- this will generate the error<br />
``int4 `` 型の始点ノードのID &lt;--- this will also generate the error (a space is after the 4)<br />
``int4`` 型の始点ノードのID &lt;--- a space is (before as a new line and) after the inline literal</pre><br />
= Tools for the Reviewer =<br />
<br />
== tools/transifex/download_translation.sh ==<br />
<br />
Use to update the <code>*.po</code> files that are in your system with the latest translation stored in Transifex.<br /><br />
Languages available:<br />
<br />
* es - Spanish<br />
* fr - French<br />
* ja - Japanese<br />
* de - German<br />
<br />
tools/transifex/download_translation.sh [es|ja|fr|de] [pgrouting.&lt;filename&gt;]<br />
<br />
To download all language translations:<br />
<br />
<pre>tools/transifex/download_translation.sh</pre><br />
To download all the translations of a particular language:<br />
<br />
<pre>tools/transifex/download_translation.sh [es|ja|fr|de]</pre><br />
To download the translation of a specific file you need to state the language also<br />
<br />
<pre>tools/transifex/download_translation.sh [es|ja|fr|de] [pgrouting.&lt;filename&gt;]</pre><br />
<br />
== tools/transifex/create_translations.sh ==<br />
<br />
Use to create: html, man, pdf documentation of the languages based on the <code>*.po</code> files stored in your system. Languages available:<br />
<br />
* es - Spanish<br />
* fr - French<br />
* ja - Japanese<br />
* de - German<br />
<br />
To create the documentation of all the languages<br />
<br />
<pre>tools/transifex/create_translations.sh</pre><br />
To create the documentation of a particular language:<br />
<br />
<pre>tools/transifex/create_translations.sh [es|ja|fr|de]</pre><br />
The main index.html of the documentation will be located at:<br />
<br />
<pre>build/doc/html/[es|ja|fr|de]/doc/index.html</pre><br />
<br />
= Main wiki page =<br />
<br />
* [https://wiki.osgeo.org/wiki/OSGeoLive OSGeoLive Wiki]<br />
<br />
<br />
[[Category: OSGeoLive]]</div>Bakanikohttps://wiki.osgeo.org/w/index.php?title=OSGeoLive_Translation_Process&diff=113815OSGeoLive Translation Process2018-02-26T20:04:21Z<p>Bakaniko: /* WORK IN PROGRESS */</p>
<hr />
<div>__FORCETOC__<br />
<br />
= Translate on Transifex =<br />
<br />
Documentation and tests are work in progress.<br />
<br />
This documentation might need adjustments to focus on the OSGeo Live Project.<br />
<br />
The list of [https://www.transifex.com/osgeo/osgeolive/content/ resources]<br />
are classified as:<br />
* ">>" Urgent - OSGeo-Live related files<br />
<br />
[[File: OSGEo-Live_transifex_01_index.png | 500px ]]<br />
<br />
* "^" High - Projects related files<br />
<br />
[[File: OSGEo-Live_transifex_02_second_priority.png | 500px ]]<br />
<br />
* "-" Normal - Deprecated projects files (not for translating)<br />
<br />
[[File: OSGEo-Live_transifex_03_retired_files.png | 500px ]]<br />
<br />
You can easily order them by Version (v11) and and descending priority<br />
<br />
[[File : OSGEo-Live_transifex_04_priority.png | 500px ]]<br />
<br />
The list of [https://www.transifex.com/osgeo/osgeolive/languages/ Languages]<br />
* Finnish<br />
* French<br />
* German<br />
* Greek<br />
* Japanese<br />
* Polish<br />
* Spanish<br />
* Mexican spanish<br />
<br />
= The general process OSGeo-Live used for documentation: =<br />
<br />
<ul><br />
<li>The developer use [http://docutils.sourceforge.net/docs/user/rst/quickstart.html ReStructuredText] syntax to write the documentation in English.</li><br />
<li>That documentation is then used with [http://sphinx-doc.org/contents.html Sphinx] to generate the english html, man, pdf, etc.</li><br />
<li>Also using [http://sphinx-doc.org/latest/intl.html Sphinx-intl] the <code>*.pot</code> files are generated.</li><br />
<li>Those <code>*.pot</code> files are used by [https://www.transifex.com/osgeo/osgeolive Transifex] and they contain only the strings that need to be translated.</li><br />
<li>Translator works with those strings using the process bellow.</li><br />
<li>When the translator finishes a language, the git hub mantainers proceed to download the generated <code>*.po</code> files that contain the translated strings and commit them in git hub and update the documentation page.</li><br />
<li><p>Users can create their translation using:</p><br />
<p>tools/transifex/create_translation.sh fr</p></li></ul><br />
<br />
Translations to French are going to be used as examples along this wiki, we choose French so you can focus on what is being translated and what is not.<br />
<br />
= Before you start =<br />
<br />
== Prepare your clone for documentation ==<br />
<br />
<pre><br />
## Prepare the directory<br />
git clone https://github.com/OSGeo/OSGeoLive-doc docClone<br />
cd docClone<br />
git checkout develop ## new things come into develop, then are merged into master<br />
mkdir build<br />
cd build<br />
<br />
## prepare the documentation for French (English is automatically build)<br />
cmake -DHTML=ON -DFR=ON .. <br />
## Build the doc<br />
make doc<br />
cd ..</pre><br />
<br />
== Downloading translation ==<br />
<br />
* To download a particular file.<br />
<br />
Best when reviewing the file:<br />
<br />
<pre><br />
tx pull -l fr -r osgeolive.quickstart--ideditor_quickstart<br />
</pre><br />
<br />
* Download the latest translated <code>*.po</code> files of your language based on translation percentage.<br />
<br />
<pre><br />
tx pull -l fr --minimum-perc=100<br />
</pre><br />
<br />
<br />
* Ask for help:<br />
<br />
<pre><br />
tx pull --help<br />
</pre><br />
<br />
=== Checking the download ===<br />
<br />
<pre><br />
git status<br />
</pre><br />
<br />
A possible output:<br />
<br />
== Have your language documentation html open. ==<br />
<br />
Viewing your language html will help to put strings in context and/or check the translation.<br />
<br />
<pre>tools/transifex/create_translations.sh fr</pre><br />
The French documentation would be in<br />
<br />
<pre>build/doc/html/fr/doc/index.html</pre><br />
<br />
== Transifex files that are not accepting translations. ==<br />
<br />
Files not accepting translations are marked with a red dot, maybe the file belongs to a previous version of OSGeo-Live documentation, or it was moved from one directory to another. Those files are not erased from the system so any translated string can be reused.<br />
<br />
== English spelling and grammar ==<br />
<br />
Sometimes the developers and the reviewers have typos in the English version, you will see spelling typos with a wavy red line, unfortunately it is too late to correct them for the current version. So proceed with the translation with the best of your ability. For the grammar, if you don't understand what is being told, please go to [https://github.com/pgRouting/pgrouting/issues/200 issue 200] to post a comment stating the file and pasting the English string. If a change has been considered, the string to be translated will be posted on the &quot;instructions&quot; for the string.<br />
<br />
= Working with small strings =<br />
<br />
== Choose the small files first. ==<br />
<br />
For &quot;small&quot; I mean the ones that have very few strings to be translated. That will start building up a bank of translated strings that can be used in larger files. To detect a &quot;small&quot; file go to the list of [resources] (https://www.transifex.com/projects/p/pgrouting/resources/) and choose a file with few words or few strings.<br />
<br />
== Use &quot;translate&quot; button ==<br />
<br />
The &quot;translate button&quot; comes quite handy, you still have to check the translation, and there is an &quot;undo&quot; button if you think that its better for you to type the translation than to modify the machine's translation.<br />
<br />
Don't use &quot;translate&quot; button on stand alone references like<br />
<br />
<pre>en: :ref:`sample`<br />
ja: :ref:`サンプル` &lt;--- wrong</pre><br />
== Use a &quot;suggestion&quot; ==<br />
<br />
When you work with transifex it builds up a translated string bank and it will show one or more suggestions. If the suggestion is very close to what is needed, use it, and change the translation to the final translation of the string. Example:<br />
<br />
<pre>en: :ref:`pgr_astar&lt;pgr_astar&gt;` - Shortest Path A*<br />
Use suggestion: pgr_astar - A*アルゴリズムを用いた最短経路探索<br />
Modify to: :ref:`pgr_astar&lt;pgr_astar&gt;` - A*アルゴリズムを用いた最短経路探索</pre><br />
== Use &quot;copy button&quot; ==<br />
<br />
Copy the the stand alone references like<br />
<br />
<pre>en: :ref:`sample`<br />
ja: :ref:`sample`</pre><br />
== Type a translation ==<br />
<br />
You can just type your translation.<br />
<br />
== Go to the next string ==<br />
<br />
When you finished translating the string press &quot;tab&quot;, that way it get's saved, if you click to a different string, maybe because the next string is already translated, then it won't be saved (green/white stripes).<br />
<br />
== Save your translation ==<br />
<br />
Make sure all strings using the &quot;Save all unsaved translations&quot; button.<br />
<br />
= Check your work =<br />
<br />
This step is needed not to check the translation but to check that ReStructuredText in the translated strings is correct. Many things might be wrong, an extra space, a missing space or a missing character &quot;`&quot; .<br />
<br />
== Download the translated file and recreate the translation ==<br />
<br />
If the file you modified in transifex is doc--src--changelog--index and want to check the Japanese translation<br />
<br />
<pre>tools/transifex/download_translation.sh ja pgrouting.doc--src--changelog--index<br />
tools/transifex/create_translations.sh ja</pre><br />
Navigate to the the translated file, for this example it would be<br />
<br />
<pre>build/doc/html/ja/doc/src/changelog/index.html</pre><br />
Notice the relation between names:<br />
<br />
<pre>Transifex name: pgrouting.doc--src--changelog--index<br />
Html Generated File: build/doc/html/ja/doc/src/changelog/index.html</pre><br />
And visualy compare the &quot;looks&quot; with the [English version] (http://docs.pgrouting.org/2.0/en/doc/index.html)<br />
<br />
== Use the &quot;Approve translation&quot; button ==<br />
<br />
When the file is fully translated (except the navigation bar), you can are about to approve the translation, '''????????'''<br />
<br />
* Check the links first, example: there is a link to sample data.<br />
<br />
Example:<br />
<br />
<pre>html: 上記クエリは サンプルデータ のネットワークを使用しています。 &lt;-- sample data is translated<br />
or: 上記クエリは Sample Data のネットワークを使用しています。 &lt;--- sample data needs translation</pre><br />
If you can navigate the links, you are ok<br />
<br />
* When using create_translation script there was no &quot;inline&quot; error (see [[Translation Troubleshooting]] ), you are ok<br />
<br />
If you are ok, then choose a string and click the &quot;Approve translation&quot; button.<br />
<br />
= Which file is next =<br />
<br />
== Do doc--index last ==<br />
<br />
That way you can use the &quot;Use suggestion&quot; in this file.<br />
<br />
== Work &quot;important&quot; files first ==<br />
<br />
All files are important, but the following files are the core of the project. Most of them have repeated strings, so the &quot;Use Suggestion&quot; tactic is perfect, and you can use the search box to find them.<br />
<br />
- your project files: you know that project certainly better than us, especially in your language; starting by the overview then the quickstart<br />
- OSGeoLive files: there is several core files for the OSgeoLive documentation:<br />
- index<br />
- overview--overview<br />
- overview--toc<br />
- quickstart--virtualization_quickstart<br />
- quickstart--usb_quickstart<br />
- quickstart--osgeolive_quickstart<br />
- copyright<br />
- contributors<br />
- translators<br />
- presentation<br />
- sponsors<br />
<br />
etc<br />
<br />
They are listed with a red double ">" priority sign<br />
<br />
== Work the &quot;almost finished&quot; files ==<br />
<br />
After you finish a file, you can choose a file that is &quot;almost done&quot;. I found pretty uncomfortable the list placed at the left, so to choose an almost done file I recommend:<br />
<br />
* Click Documentation<br />
* Click on your language<br />
* click on the sorting button (sorts by % of termination)<br />
<br />
This is very useful when you have a lot of files already translated<br />
<br />
== Work files that belong to a directory ==<br />
<br />
Based on the following files:<br />
<br />
* doc--src--changelog--1_x ... 150 words (25 strings) ...<br />
* doc--src--changelog--2_0 ... 277 words (26 strings) ...<br />
* doc--src--changelog--index ... 4 words (3 strings) ...<br />
<br />
Maybe you started working with doc--src--changelog--index, so the next step would be to work with<br />
<br />
* doc--src--changelog--1_x<br />
* doc--src--changelog--2_0<br />
<br />
So you finished a section, go [[Translation Check your work]].<br />
<br />
= Troubleshooting =<br />
<br />
Please post any question in [https://github.com/pgRouting/pgrouting/issues/200 issue 200]<br />
<br />
== The :ref:`nameoflink` link is not translated ==<br />
<br />
Example<br />
<br />
<pre>en: The queries use the :ref:`sampledata` network.<br />
ja: 上記クエリは :ref:`sampledata` のネットワークを使用しています。 <br />
html: 上記クエリは Sample Data のネットワークを使用しています。</pre><br />
Thats and indication that the referenced page for Sample Data, isn't fully translated. If you can click on the link and navigate you are ok.<br />
<br />
== The :ref:`nameoflink` link is the only thing that is translated ==<br />
<br />
Example<br />
<br />
<pre>en: The queries use the :ref:`sampledata` network.<br />
ja: The queries use the :ref:`sampledata` network.<br />
html: The queries use the サンプルデータ network.</pre><br />
Maybe you navigated into an untranslated page that has a reference to a translated page.<br />
<br />
== I don't see the link but I can read :ref: in the html page ==<br />
<br />
This is a common problem when using the translation button.<br /><br />
Example<br />
<br />
<pre>en: The queries use the :ref:`sampledata` network.<br />
ja: 上記クエリは: ref:'sampledata'のネットワークを使用しています。 <br />
html: 上記クエリは: ref:'sampledata'のネットワークを使用しています。</pre><br />
The link's generated by the button need to be corrected, I suggest to copy the link together with its sorrounding spaces from the English version:<br />
<br />
<pre> -------------------<br />
en: The queries use the :ref:`sampledata` network.<br />
ja: 上記クエリは :ref:`sampledata` のネットワークを使用しています。 <br />
html: 上記クエリは サンプルデータ のネットワークを使用しています。<br />
or: 上記クエリは Sample Data のネットワークを使用しています。</pre><br />
<br />
== WARNING: Inline literal start-string without end-string. ==<br />
<br />
You will get this error is when using ''tools/transifex/create_translations.sh''. Languages like Japanese that don't use spaces to separate words are more likely to have this error. Unfortunately the error is shown only in line 1.<br />
<br />
Inline literals [specs] (http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#inline-markup) require a space before and after. The inline literals we use the most are of the type ``inlineliteral`` like in:<br />
<br />
<pre>``int4`` id of the end point<br />
``int4``型の始点ノードのID &lt;--- this will generate the error<br />
``int4 `` 型の始点ノードのID &lt;--- this will also generate the error (a space is after the 4)<br />
``int4`` 型の始点ノードのID &lt;--- a space is (before as a new line and) after the inline literal</pre><br />
= Tools for the Reviewer =<br />
<br />
== tools/transifex/download_translation.sh ==<br />
<br />
Use to update the <code>*.po</code> files that are in your system with the latest translation stored in Transifex.<br /><br />
Languages available:<br />
<br />
* es - Spanish<br />
* fr - French<br />
* ja - Japanese<br />
* de - German<br />
<br />
tools/transifex/download_translation.sh [es|ja|fr|de] [pgrouting.&lt;filename&gt;]<br />
<br />
To download all language translations:<br />
<br />
<pre>tools/transifex/download_translation.sh</pre><br />
To download all the translations of a particular language:<br />
<br />
<pre>tools/transifex/download_translation.sh [es|ja|fr|de]</pre><br />
To download the translation of a specific file you need to state the language also<br />
<br />
<pre>tools/transifex/download_translation.sh [es|ja|fr|de] [pgrouting.&lt;filename&gt;]</pre><br />
<br />
== tools/transifex/create_translations.sh ==<br />
<br />
Use to create: html, man, pdf documentation of the languages based on the <code>*.po</code> files stored in your system. Languages available:<br />
<br />
* es - Spanish<br />
* fr - French<br />
* ja - Japanese<br />
* de - German<br />
<br />
To create the documentation of all the languages<br />
<br />
<pre>tools/transifex/create_translations.sh</pre><br />
To create the documentation of a particular language:<br />
<br />
<pre>tools/transifex/create_translations.sh [es|ja|fr|de]</pre><br />
The main index.html of the documentation will be located at:<br />
<br />
<pre>build/doc/html/[es|ja|fr|de]/doc/index.html</pre><br />
<br />
= Main wiki page =<br />
<br />
* [https://wiki.osgeo.org/wiki/OSGeoLive OSGeoLive Wiki]<br />
<br />
<br />
[[Category: OSGeoLive]]</div>Bakanikohttps://wiki.osgeo.org/w/index.php?title=OSGeoLive_Translation_Process&diff=111122OSGeoLive Translation Process2017-11-22T19:27:20Z<p>Bakaniko: /* When more than one person is collaborating with the translation */</p>
<hr />
<div>__FORCETOC__<br />
<br />
= WORK IN PROGRESS =<br />
<br />
Documentation and tests are work in progress.<br />
<br />
This documentation might need adjustments to focus on the OSGeo Live Project.<br />
<br />
The list of [https://www.transifex.com/osgeo/osgeolive/content/ resources]<br />
are classified as:<br />
* ">>" Urgent - OSGeo-Live related files<br />
<br />
[[File: OSGEo-Live_transifex_01_index.png | 500px ]]<br />
<br />
* "^" High - Projects related files<br />
<br />
[[File: OSGEo-Live_transifex_02_second_priority.png | 500px ]]<br />
<br />
* "-" Normal - Deprecated projects files (not for translating)<br />
<br />
[[File: OSGEo-Live_transifex_03_retired_files.png | 500px ]]<br />
<br />
You can easily order them by Version (v11) and and descending priority<br />
<br />
[[File : OSGEo-Live_transifex_04_priority.png | 500px ]]<br />
<br />
The list of [https://www.transifex.com/osgeo/osgeolive/languages/ Languages]<br />
* Finnish<br />
* French<br />
* German<br />
* Greek<br />
* Japanese<br />
* Polish<br />
* Spanish<br />
* Mexican spanish<br />
<br />
= The general process OSGeo-Live used for documentation: =<br />
<br />
<ul><br />
<li>The developer use [http://docutils.sourceforge.net/docs/user/rst/quickstart.html ReStructuredText] syntax to write the documentation in English.</li><br />
<li>That documentation is then used with [http://sphinx-doc.org/contents.html Sphinx] to generate the english html, man, pdf, etc.</li><br />
<li>Also using [http://sphinx-doc.org/latest/intl.html Sphinx-intl] the <code>*.pot</code> files are generated.</li><br />
<li>Those <code>*.pot</code> files are used by [https://www.transifex.com/osgeo/osgeolive Transifex] and they contain only the strings that need to be translated.</li><br />
<li>Translator works with those strings using the process bellow.</li><br />
<li>When the translator finishes a language, the git hub mantainers proceed to download the generated <code>*.po</code> files that contain the translated strings and commit them in git hub and update the documentation page.</li><br />
<li><p>Users can create their translation using:</p><br />
<p>tools/transifex/create_translation.sh fr</p></li></ul><br />
<br />
Translations to French are going to be used as examples along this wiki, we choose French so you can focus on what is being translated and what is not.<br />
<br />
= Before you start =<br />
<br />
== Prepare your clone for documentation ==<br />
<br />
<pre><br />
## Prepare the directory<br />
git clone https://github.com/OSGeo/OSGeoLive-doc docClone<br />
cd docClone<br />
git checkout develop ## new things come into develop, then are merged into master<br />
mkdir build<br />
cd build<br />
<br />
## prepare the documentation for French (English is automatically build)<br />
cmake -DHTML=ON -DFR=ON .. <br />
## Build the doc<br />
make doc<br />
cd ..</pre><br />
<br />
== When more than one person is collaborating with the translation ==<br />
<br />
Download the latest translated <code>*.po</code> files of your language.<br />
<br />
<pre><br />
tx pull -l fr --minimum-perc=100<br />
</pre><br />
<br />
== Have your language documentation html open. ==<br />
<br />
Viewing your language html will help to put strings in context and/or check the translation.<br />
<br />
<pre>tools/transifex/create_translations.sh fr</pre><br />
The French documentation would be in<br />
<br />
<pre>build/doc/html/fr/doc/index.html</pre><br />
<br />
== Transifex files that are not accepting translations. ==<br />
<br />
Files not accepting translations are marked with a red dot, maybe the file belongs to a previous version of OSGeo-Live documentation, or it was moved from one directory to another. Those files are not erased from the system so any translated string can be reused.<br />
<br />
== English spelling and grammar ==<br />
<br />
Sometimes the developers and the reviewers have typos in the English version, you will see spelling typos with a wavy red line, unfortunately it is too late to correct them for the current version. So proceed with the translation with the best of your ability. For the grammar, if you don't understand what is being told, please go to [https://github.com/pgRouting/pgrouting/issues/200 issue 200] to post a comment stating the file and pasting the English string. If a change has been considered, the string to be translated will be posted on the &quot;instructions&quot; for the string.<br />
<br />
= Working with small strings =<br />
<br />
== Choose the small files first. ==<br />
<br />
For &quot;small&quot; I mean the ones that have very few strings to be translated. That will start building up a bank of translated strings that can be used in larger files. To detect a &quot;small&quot; file go to the list of [resources] (https://www.transifex.com/projects/p/pgrouting/resources/) and choose a file with few words or few strings.<br />
<br />
== Use &quot;translate&quot; button ==<br />
<br />
The &quot;translate button&quot; comes quite handy, you still have to check the translation, and there is an &quot;undo&quot; button if you think that its better for you to type the translation than to modify the machine's translation.<br />
<br />
Don't use &quot;translate&quot; button on stand alone references like<br />
<br />
<pre>en: :ref:`sample`<br />
ja: :ref:`サンプル` &lt;--- wrong</pre><br />
== Use a &quot;suggestion&quot; ==<br />
<br />
When you work with transifex it builds up a translated string bank and it will show one or more suggestions. If the suggestion is very close to what is needed, use it, and change the translation to the final translation of the string. Example:<br />
<br />
<pre>en: :ref:`pgr_astar&lt;pgr_astar&gt;` - Shortest Path A*<br />
Use suggestion: pgr_astar - A*アルゴリズムを用いた最短経路探索<br />
Modify to: :ref:`pgr_astar&lt;pgr_astar&gt;` - A*アルゴリズムを用いた最短経路探索</pre><br />
== Use &quot;copy button&quot; ==<br />
<br />
Copy the the stand alone references like<br />
<br />
<pre>en: :ref:`sample`<br />
ja: :ref:`sample`</pre><br />
== Type a translation ==<br />
<br />
You can just type your translation.<br />
<br />
== Go to the next string ==<br />
<br />
When you finished translating the string press &quot;tab&quot;, that way it get's saved, if you click to a different string, maybe because the next string is already translated, then it won't be saved (green/white stripes).<br />
<br />
== Save your translation ==<br />
<br />
Make sure all strings using the &quot;Save all unsaved translations&quot; button.<br />
<br />
= Check your work =<br />
<br />
This step is needed not to check the translation but to check that ReStructuredText in the translated strings is correct. Many things might be wrong, an extra space, a missing space or a missing character &quot;`&quot; .<br />
<br />
== Download the translated file and recreate the translation ==<br />
<br />
If the file you modified in transifex is doc--src--changelog--index and want to check the Japanese translation<br />
<br />
<pre>tools/transifex/download_translation.sh ja pgrouting.doc--src--changelog--index<br />
tools/transifex/create_translations.sh ja</pre><br />
Navigate to the the translated file, for this example it would be<br />
<br />
<pre>build/doc/html/ja/doc/src/changelog/index.html</pre><br />
Notice the relation between names:<br />
<br />
<pre>Transifex name: pgrouting.doc--src--changelog--index<br />
Html Generated File: build/doc/html/ja/doc/src/changelog/index.html</pre><br />
And visualy compare the &quot;looks&quot; with the [English version] (http://docs.pgrouting.org/2.0/en/doc/index.html)<br />
<br />
== Use the &quot;Approve translation&quot; button ==<br />
<br />
When the file is fully translated (except the navigation bar), you can are about to approve the translation, '''????????'''<br />
<br />
* Check the links first, example: there is a link to sample data.<br />
<br />
Example:<br />
<br />
<pre>html: 上記クエリは サンプルデータ のネットワークを使用しています。 &lt;-- sample data is translated<br />
or: 上記クエリは Sample Data のネットワークを使用しています。 &lt;--- sample data needs translation</pre><br />
If you can navigate the links, you are ok<br />
<br />
* When using create_translation script there was no &quot;inline&quot; error (see [[Translation Troubleshooting]] ), you are ok<br />
<br />
If you are ok, then choose a string and click the &quot;Approve translation&quot; button.<br />
<br />
= Which file is next =<br />
<br />
== Do doc--index last ==<br />
<br />
That way you can use the &quot;Use suggestion&quot; in this file.<br />
<br />
== Work &quot;important&quot; files first ==<br />
<br />
All files are important, but the following files are the core of the project. Most of them have repeated strings, so the &quot;Use Suggestion&quot; tactic is perfect, and you can use the search box to find them.<br />
<br />
- your project files: you know that project certainly better than us, especially in your language; starting by the overview then the quickstart<br />
- OSGeoLive files: there is several core files for the OSgeoLive documentation:<br />
- index<br />
- overview--overview<br />
- overview--toc<br />
- quickstart--virtualization_quickstart<br />
- quickstart--usb_quickstart<br />
- quickstart--osgeolive_quickstart<br />
- copyright<br />
- contributors<br />
- translators<br />
- presentation<br />
- sponsors<br />
<br />
etc<br />
<br />
They are listed with a red double ">" priority sign<br />
<br />
== Work the &quot;almost finished&quot; files ==<br />
<br />
After you finish a file, you can choose a file that is &quot;almost done&quot;. I found pretty uncomfortable the list placed at the left, so to choose an almost done file I recommend:<br />
<br />
* Click Documentation<br />
* Click on your language<br />
* click on the sorting button (sorts by % of termination)<br />
<br />
This is very useful when you have a lot of files already translated<br />
<br />
== Work files that belong to a directory ==<br />
<br />
Based on the following files:<br />
<br />
* doc--src--changelog--1_x ... 150 words (25 strings) ...<br />
* doc--src--changelog--2_0 ... 277 words (26 strings) ...<br />
* doc--src--changelog--index ... 4 words (3 strings) ...<br />
<br />
Maybe you started working with doc--src--changelog--index, so the next step would be to work with<br />
<br />
* doc--src--changelog--1_x<br />
* doc--src--changelog--2_0<br />
<br />
So you finished a section, go [[Translation Check your work]].<br />
<br />
= Troubleshooting =<br />
<br />
Please post any question in [https://github.com/pgRouting/pgrouting/issues/200 issue 200]<br />
<br />
== The :ref:`nameoflink` link is not translated ==<br />
<br />
Example<br />
<br />
<pre>en: The queries use the :ref:`sampledata` network.<br />
ja: 上記クエリは :ref:`sampledata` のネットワークを使用しています。 <br />
html: 上記クエリは Sample Data のネットワークを使用しています。</pre><br />
Thats and indication that the referenced page for Sample Data, isn't fully translated. If you can click on the link and navigate you are ok.<br />
<br />
== The :ref:`nameoflink` link is the only thing that is translated ==<br />
<br />
Example<br />
<br />
<pre>en: The queries use the :ref:`sampledata` network.<br />
ja: The queries use the :ref:`sampledata` network.<br />
html: The queries use the サンプルデータ network.</pre><br />
Maybe you navigated into an untranslated page that has a reference to a translated page.<br />
<br />
== I don't see the link but I can read :ref: in the html page ==<br />
<br />
This is a common problem when using the translation button.<br /><br />
Example<br />
<br />
<pre>en: The queries use the :ref:`sampledata` network.<br />
ja: 上記クエリは: ref:'sampledata'のネットワークを使用しています。 <br />
html: 上記クエリは: ref:'sampledata'のネットワークを使用しています。</pre><br />
The link's generated by the button need to be corrected, I suggest to copy the link together with its sorrounding spaces from the English version:<br />
<br />
<pre> -------------------<br />
en: The queries use the :ref:`sampledata` network.<br />
ja: 上記クエリは :ref:`sampledata` のネットワークを使用しています。 <br />
html: 上記クエリは サンプルデータ のネットワークを使用しています。<br />
or: 上記クエリは Sample Data のネットワークを使用しています。</pre><br />
<br />
== WARNING: Inline literal start-string without end-string. ==<br />
<br />
You will get this error is when using ''tools/transifex/create_translations.sh''. Languages like Japanese that don't use spaces to separate words are more likely to have this error. Unfortunately the error is shown only in line 1.<br />
<br />
Inline literals [specs] (http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#inline-markup) require a space before and after. The inline literals we use the most are of the type ``inlineliteral`` like in:<br />
<br />
<pre>``int4`` id of the end point<br />
``int4``型の始点ノードのID &lt;--- this will generate the error<br />
``int4 `` 型の始点ノードのID &lt;--- this will also generate the error (a space is after the 4)<br />
``int4`` 型の始点ノードのID &lt;--- a space is (before as a new line and) after the inline literal</pre><br />
= Tools for the Reviewer =<br />
<br />
== tools/transifex/download_translation.sh ==<br />
<br />
Use to update the <code>*.po</code> files that are in your system with the latest translation stored in Transifex.<br /><br />
Languages available:<br />
<br />
* es - Spanish<br />
* fr - French<br />
* ja - Japanese<br />
* de - German<br />
<br />
tools/transifex/download_translation.sh [es|ja|fr|de] [pgrouting.&lt;filename&gt;]<br />
<br />
To download all language translations:<br />
<br />
<pre>tools/transifex/download_translation.sh</pre><br />
To download all the translations of a particular language:<br />
<br />
<pre>tools/transifex/download_translation.sh [es|ja|fr|de]</pre><br />
To download the translation of a specific file you need to state the language also<br />
<br />
<pre>tools/transifex/download_translation.sh [es|ja|fr|de] [pgrouting.&lt;filename&gt;]</pre><br />
<br />
== tools/transifex/create_translations.sh ==<br />
<br />
Use to create: html, man, pdf documentation of the languages based on the <code>*.po</code> files stored in your system. Languages available:<br />
<br />
* es - Spanish<br />
* fr - French<br />
* ja - Japanese<br />
* de - German<br />
<br />
To create the documentation of all the languages<br />
<br />
<pre>tools/transifex/create_translations.sh</pre><br />
To create the documentation of a particular language:<br />
<br />
<pre>tools/transifex/create_translations.sh [es|ja|fr|de]</pre><br />
The main index.html of the documentation will be located at:<br />
<br />
<pre>build/doc/html/[es|ja|fr|de]/doc/index.html</pre><br />
<br />
= Main wiki page =<br />
<br />
* [https://wiki.osgeo.org/wiki/Live_GIS_Disc OSGeo-Live Wiki]</div>Bakaniko