Re: [Gvsig_english] About community documentation space

2010-01-27 Thread Marie-Claude DEMOULIN
Hi all, Hi Mario, I also prefer this option. Cheers, Marie-Claude Le 27/01/2010 00:17, Simon Cropper (Botanicus Australia Pty Ltd) a écrit : > Hi Jorge Gaspar, > > I also support this option. > > 1. I like the concept of important documentation being managed and > retained by the core organizat

Re: [Gvsig_english] About community documentation space

2010-01-27 Thread Jordi Torres
Hi Jorge and Simon, Well it's pretty easy, go to freenode [1] and select a nickname and > the "gvsig" channel. I usually try to be there (mostly alone), but I'm > not always available of course. > > Of course you can configure a desktop client, for Linux I like xchat > > You can use chatzilla[1].I

Re: [Gvsig_english] About community documentation space

2010-01-27 Thread Jorge Gaspar Sanz Salinas
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 27/01/10 00:17, Simon Cropper (Botanicus Australia Pty Ltd) wrote: > Hi Jorge Gaspar, > > I also support this option. > > 1. I like the concept of important documentation being managed and > retained by the core organization responsible for creat

Re: [Gvsig_english] About community documentation space

2010-01-26 Thread Simon Cropper (Botanicus Australia Pty Ltd)
Rory, "Tutorials" and "How to Guides" are where I am coming from, although I am happy to contribute to a standard manual. As I think Anna Hodgkinson said many posts ago together we could create a valuable "basis for expansion in no time". I agree. Personally though, my immediate focus is writi

Re: [Gvsig_english] About community documentation space

2010-01-26 Thread Rory Hill
Hi all, Following this thread I thought it might be a nice idea for those who can to produce some tutorials on how to use gvSIG in their particular sector, e.g. whether it's environmental management, cartography, archaeology, transport, etc, etc. Simon I think you said a while back that you di

Re: [Gvsig_english] About community documentation space

2010-01-26 Thread Simon Cropper (Botanicus Australia Pty Ltd)
Hi Jorge Gaspar, I also support this option. 1. I like the concept of important documentation being managed and retained by the core organization responsible for creation of the OS product in the first place. If gvSIG is willing to create and host a facility I would prefer this. 2. Having pla

Re: [Gvsig_english] About community documentation space

2010-01-26 Thread Antonio Falciano
Il 26/01/2010 14.03, Mario Carrera ha scritto: > > Hi Antonio, > > it's possible the best option. It'd work like in the documentation > section of the gvsig.org website, so tutorials will be able to be > translated to other languages. Hi Mario, imho this is really the best option, because internat

Re: [Gvsig_english] About community documentation space

2010-01-26 Thread Mario Carrera
Hi Antonio, it's possible the best option. It'd work like in the documentation section of the gvsig.org website, so tutorials will be able to be translated to other languages. About the translations of the gvSIG 1.9 manual, there's no problem. I'll confirm you the chapters to translate becaus

Re: [Gvsig_english] About community documentation space

2010-01-26 Thread Chris Puttick
Everything is just next door on the web... - "silvio grosso" wrote: > Hello everybody, > > Gertrude Pieper: > > I think this is a good idea, perfect for documentation in different > > > languages, and everything close to the source code. > > I agree. > The gvSIG's Plone worked fine when

Re: [Gvsig_english] About community documentation space

2010-01-26 Thread Jorge Gaspar Sanz Salinas
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 26/01/10 13:52, Chris Puttick wrote: > For easiest access for the greatest number of users, wouldn't a wiki be > easier? > > Chris > As Mario said in his initial mail (it was wrote by he and me) that decision is up to you. We don't have a wiki

Re: [Gvsig_english] About community documentation space

2010-01-26 Thread silvio grosso
Hello everybody, Gertrude Pieper: > I think this is a good idea, perfect for documentation in different > languages, and everything close to the source code. I agree. The gvSIG's Plone worked fine when we translated the Italian manual. Having all the most important documentation, close to the s

Re: [Gvsig_english] About community documentation space

2010-01-26 Thread Chris Puttick
For easiest access for the greatest number of users, wouldn't a wiki be easier? Chris - "Jorge Gaspar Sanz Salinas" wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 26/01/10 11:13, Antonio Falciano wrote: > > Il 25/01/2010 16.39, Mario Carrera ha scritto: > >> Hi all > > >

Re: [Gvsig_english] About community documentation space

2010-01-26 Thread Jorge Gaspar Sanz Salinas
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 26/01/10 11:13, Antonio Falciano wrote: > Il 25/01/2010 16.39, Mario Carrera ha scritto: >> Hi all > > Hi Mario, > >> The gvSIG team have been discussing this morning about the best approach >> to give you the most useful resources. >> >> The firs

Re: [Gvsig_english] About community documentation space

2010-01-26 Thread Gertrude Pieper
ry 25, 2010 10:39 PM Subject: [Gvsig_english] About community documentation space Hi all The gvSIG team have been discussing this morning about the best approach to give you the most useful resources. The first option for us is to use our portal (http://www.gvsig.org). The main plone i

Re: [Gvsig_english] About community documentation space

2010-01-26 Thread Antonio Falciano
Il 25/01/2010 16.39, Mario Carrera ha scritto: > Hi all Hi Mario, > The gvSIG team have been discussing this morning about the best approach > to give you the most useful resources. > > The first option for us is to use our portal (http://www.gvsig.org). The > main plone instance is our first doc

[Gvsig_english] About community documentation space

2010-01-25 Thread Mario Carrera
Hi all The gvSIG team have been discussing this morning about the best approach to give you the most useful resources. The first option for us is to use our portal (http://www.gvsig.org). The main plone instance is our first documentation resource and can not be used as a community reposito