[Qgis-psc] Fwd: proposal for a QGIS documentation web infrastructure development sprint @ 7th QGIS Developer Meeting in Lyon 2012

[Tim Sutton]

Hi


On Thu, Mar 15, 2012 at 6:12 PM, Paolo Cavallini <cavallini at faunalia.it> wrote:
> Hi all.
> I'm forarding this proposal by Paolo Corti.
> I think it is very interesting, but I leave the decision to the psc.
> All the best.
>
> -------- Messaggio originale --------
> Hello
>
> in the context of the 7th QGIS Developer Meeting in Lyon 2012, my idea
> is to make a sprint for the development and deployment of a
> documentation web infrastructure for the QGIS project.
>
> The steps I intend to follow, for developing such an architecture, are:
>
> * configuration of the environment (virtualenv with Python 2.7, Django
> 1.3 [1], Translate Toolkit 2.9 [2], Sphinx 1.1 [3]
> * installation and setup of Pootle [4]
> * creation and configuration of the Sphinx project
> * setup of the initial rst documentation pages for the QGIS manual
> (rst pages will be committed to git automatically)
> * creation of the sync mechanism between the Pootle application and
> the Sphinx project: as soon as a documentation editor x for the
> language y will commit to git his/her modifications, the Sphinx
> project will be automatically rebuilt and web site updated with this
> build
> * deployment of the infrastructure to the QGIS production web site
>
> I am planning to attend to the meeting for 3/4 days, still in doubt
> between 12/13/14/15 or 14/15/16 of April
> I will arrive in Lyon from Milan, Italy, by plane.
>
> Therefore I need the following reimbursements:
>
> * 3/4 nights for the hotel: still not sure which one, but I guess it
> will be someting around 50 euro per night, so a total of 150/200 euro
> * easyjet flight ticket, around 50 euro for both ways as of today
> * around 50 euro for airport and city transfers


I'd be happy to +1 that assuming we have the funds. I have two
comments on the notes above:

1) Please liase with Otto, Yves and others already interested to make
sure this is the right route we want to follow (I think it is but
others may differ)
2) If we are building on django, I would prefer we extend the existing
QGIS django app (https://github.com/qgis/qgis-django) to further the
goal of reduction of proliferation of things we have to manage.

I have been using sphinx quite a lot lately too and am convinced this
will be a good route for us to follow. I would be interested in
merging the various documentation assets we maintain (either using
intersphinx or by combining them into a super project):

- coding guide
- gentle intro latex port
- user guide
- python cookbook
- qgis governance (fledgling)
- qgis interactive context help


Regards

Tim

>
> Thanks for your kind consideration
> Paolo
>
> [1] https://www.djangoproject.com/
> [2] http://translate.sourceforge.net/wiki/toolkit/index
> [3] http://sphinx.pocoo.org/
> [4] http://translate.sourceforge.net/wiki/pootle/index
>
> --
> Paolo Corti
> Geospatial software developer
> web: http://www.paolocorti.net
> twitter: @capooti
> skype: capooti
> _______________________________________________
> Qgis-psc mailing list
> Qgis-psc at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-psc



-- 
Tim Sutton - QGIS Project Steering Committee Member (Release  Manager)
==============================================
Visit http://linfiniti.com to find out about:
 * QGIS programming services
 * Mapserver and PostGIS based hosting plans
 * FOSS Consulting Services
Skype: timlinux Irc: timlinux on #qgis at freenode.net
==============================================