Hi All, In regards to reusing tutorial content I will state the obvious.
With community wikis content usually ends up a collection of text from all over the place. Most if not all is not attributed to the original authors. Although this is not unusual a tutorial by a particular person may be considered more valuable, more authoritative or useful than others, and some authors, and I must admit I fall into this category, like to have their work attributed. For most of my reports I tend to create documents that can be freely distributed but avoid derivatives or use of the work commercially. The avoiding of derivatives comes form the fact that I take the time to carefully research what I release but the author of a derived work may not take as much care. The avoiding of use of works for commercial purposes stems from the fact that this is an open community effort and people should not derive money from reselling community supplied content. This generally falls into Creative Commons Attribution-Non-Commercial-No Derivative Works. What do others think about this? A good example is Anna. She has contributed a manual for survey and gis using gvSIG. Should this be sucked into a wiki then edited by all and sundry, with no recognition to the original author? Personally I believe her personal effort should be recognized for all the reasons mentioned above. Cheers Simon Simon Cropper Botanicus Australia Pty Ltd PO Box 160, Sunshine, Victoria 3020. P: 9311 5822. M: 041 830 3437. mailto: [email protected] <mailto:[email protected]> web: www.botanicusaustralia.com.au <http://www.botanicusaustralia.com.au> On 22/01/2010 10:07 AM, Juan Lucas Dominguez Rubio wrote: > > Hello, > I especially like that quick guide with its minimalistic but elegant > layout > which I think corresponds to LaTeX's true spirit. Sorry if I sound > shallow :) > > > Regards, > > Juan Lucas Domínguez Rubio > --- > Prodevelop SL, Valencia (España) > Tlf.: 96.351.06.12 -- Fax: 96.351.09.68 > http://www.prodevelop.es > --- > > > > -----Original Message----- > From: [email protected] on behalf of > Wolfgang Qual > Sent: Thu 21/01/2010 21:47 > To: Anna Hodgkinson; Users and Developers mailing list > Subject: Re: [Gvsig_english] FEEDBACK gvSIG 1.9 (BN 1253) -- use of > gvSIG in production environment > > Hi Anna, > I translated the OA digital quickstart guide into German and adapted it > to 1.9. It's available on the German gvSIG-Wiki [1]. Maybe interesting > for other users? > > Best, > Wolfgang > > [1] > http://webmapping.info/mwgvsig/index.php?title=Datei:Kurzanleitung_gvSIG_1_9.pdf > > > > > > Am Donnerstag, den 21.01.2010, 16:38 +0000 schrieb Anna Hodgkinson: > > I agree that there should be a Wiki. Especially if everybody > contributes what they have already written there should be a basis for > expansion in no time. > > > > In addition, many tools work the same way in 1.9 as in the older > version so there should be nothing wrong with extracting the tutorials > on these from existing documentation. > > > > I recently produced this Survey and GIS guide available here: > > http://openarchaeology.net/project/survey-and-gis-manual > > It is based on gvSIG 1.1.2, but one task is specific for 1.9 and > most other chapters are transferable. > > > > Anna > > > > > > ----- Original Message ----- > > From: "Agustin Diez Castillo" <[email protected]> > > To: "Users and Developers mailing list" > <[email protected]> > > Sent: Thursday, 21 January, 2010 15:50:27 GMT +00:00 GMT Britain, > Ireland, Portugal > > Subject: Re: [Gvsig_english] FEEDBACK gvSIG 1.9 (BN 1253) -- use of > gvSIG in production environment > > > > Maybe a good idea is to put hands on the wikis. Certainly a 500 > pages books is a hard task but if each us write one or two pages we > can reach a 40 pages booklet in no time. > > I myself have some wikis (in Spanish) here [1] and there [2] to help > out my students, some have already been translated into English [3] by > others but, as far as they don't have tons of text, I myself can do an > english version that can be proofread easily in doowikis. > > [1] http://www.doowikis.com/m/GjViWfIBz4 > > [2] http://www.doowikis.com/m/uXwFgF6TZd > > [3] http://www.doowikis.com/m/i5eNy43OTL > > > > On Jan 21, 2010, at 4:11 PM, Chris Puttick wrote: > > > > > > > > ----- "silvio grosso" <[email protected]> wrote: > > > > > >> Hi Ben, > > >> > > >>> ... and now I am starting to regret that there is no gvSIGWiki! > > >> > > >> The Wiki, for gvSIG, would be really useful. > > >> Wolfgang Qual and others proposed it in the past but, in the end, > this > > >> suggestion has never been applied. > > >> Luckily for us, gvSIG's development is proceeding so fast that any > > >> tutorial proposed becomes outdated in no time :-) > > > > > > A wiki is just the right documentation tool for such a product! We > could build a gvSIG wiki on wikidot real fast. In fact, unless someone > wants to say why not, I'll set the w(iki)heels in motion... > > +1 > > > > > > Cheers > > > > > > Chris > > > > > > > > > ------ > > > Files attached to this email may be in ISO 26300 format (OASIS > Open Document Format). If you have difficulty opening them, please > visit http://iso26300.info for more information. > > > > > > _______________________________________________ > > > Gvsig_internacional mailing list > > > [email protected] > > > http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional > > > > > > > _______________________________________________ > > Gvsig_internacional mailing list > > [email protected] > > http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional > > > > > > > _______________________________________________ > Gvsig_internacional mailing list > [email protected] > http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional > > > _______________________________________________ > Gvsig_internacional mailing list > [email protected] > http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional > _______________________________________________ Gvsig_internacional mailing list [email protected] http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional
