[Qgis-community-team] QGIS Training Manual 2.0

Victor Olaya volayaf at gmail.com
Mon Nov 25 02:35:10 PST 2013


George

That sounds great. Working on the training manual is among our plans
at Boundless, so now that you are leading this effort, we will be
happy to collaborate. We basically had the same ideas that you listed,
so you can count on us and assign us whatever task you consider that
are relevant. We also wanted to incorporate the Processing training
manual as part of the QGIS manual (I see you haven't mentioned that),
but I guess that will go better once we improved the collaboration
process and the division in chapters.

My colleague Jeff (I have seen you have added him to this email) will
probably be happy to help on the sphinx related stuff, while I will be
probably be more useful on the QGIS side, rewriting text to adapt to
2.0, documenting new functionalities that were not available in 1.8,
preparing screenshots, etc

As I said, cound on us and feel free to contact us directly for
anything you might need. I am really lookign forward to working on
this, since I believe the QGIS training manual is a great document
that should be promoted as much as possible.

Cheers


2013/11/25 George Irwin <george at linfiniti.com>:
> Good morning all,
>
> Quick introduction: I’ve just started working with Tim Sutton at Linfiniti
> (although we’ve been working together on other projects on and off for a
> couple of years). I’m new to QGIS and all things GIS, but very much looking
> forward to getting involved and contributing what I can!
>
> My first task is to start work on porting the QGIS Training Manual to QGIS
> 2.0. Tim has filled me in on the broad requirements which make up that goal
> and this, very loosely, is what I’m setting out to achieve:
>
> 1. Collaborate with everyone who would like to be involved or has
> suggestions/recommendations/expectations for the manual.
> 2. Make the collaboration/sharing process a little easier by creating fabric
> scripts to deploy the Manual/Sphinx/latex etc in a Vagrant box.
> 3. Implement generic datasets (OSM and Natural Earth) with the ability (via
> scripts/tasks) for end-users to easily import localised cadastrals.
> 4. Organise, rename, and make pretty the screen grabs (more attractive maps,
> consistent GUI layout etc).
> 5. Check, clean and update the sample data as necessary.
> 6. Look at the license with regard to academic institutions and update as
> necessary.
> 7. Match QGIS.org styling and formatting conventions with the intention of
> embedding the manual in QGIS.org (not Linfiniti, as at present).
> 8. Look at creating an interface to allow end-users to generate custom
> manuals aimed at specific training sessions (i.e. to include specific
> chapters/data etc).
>
> I’m very aware that I have limited experience with QGIS itself and the
> community, so please do send me your thoughts/corrections/requirements on
> any of the above or anything which you think should be included! Renaming of
> the screen-grabs will certainly require input - if nothing else - especially
> when it comes to localisations…..
>
> As an aside, I plan to work in a branch of the repository on github, with
> nightly builds pushed to an accessible server - advice on this front also
> welcome!
>
> Looking forward to hearing from you
>
> George
>
>
>
>
> George Irwin
> Project and Client Manager
> Linfiniti Consulting
> http://www.linfiniti.com
> +27 (0)76 013 6355
> Skype: georgeirwin22
>
>
>
> _______________________________________________
> Qgis-community-team mailing list for organizing community resources such as
> documentation, translation etc..
> Qgis-community-team at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-community-team


More information about the Qgis-community-team mailing list