Quantcast

grass manual translations

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

grass manual translations

Helena Mitasova
I got an interesting question - see below.
I asked for more details, but when looking at the man pages
there is only Copyright by GRASS Development Team and
no license and no email who to contact in case somebody
wants to use/distribute/reprint etc. the material. In fact the Intro
pages don't have anything.
Should we include Creative commons license for the manual
at each page with a link to explanation of what CC means?
Or should we protect the manual by a stricter license or copyright
and provide contact to person who will handle the request?
( first option looks much better to me)

Helena


A few months ago i started making a translation of the Grass manual  
and after a lot of changes I prepared a greek manual according to my  
student needs.

In the Greek manual I have allready referenced the grass manual but I  
didnt print it because i still dont have the right to translate the  
english manual.
Is there any way for me to print my book which is about Grass and  
Qgis???
I mean could I somehow take a letter from the Grass team in which  
they will say that I have the right to print my book using as  
basework their work in the english manual??


Nicolas Karanikolas
_______________________________________________
grass-psc mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-psc
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: grass manual translations

hamish-2
Helena Mitasova wrote:
> I got an interesting question - see below.
> I asked for more details, but when looking at the man pages
> there is only Copyright by GRASS Development Team and
> no license and no email who to contact in case somebody
> wants to use/distribute/reprint etc. the material.

The contact is the "GRASS Development Team". The email contact (if
there should be one) should be the -psc or -dev lists, but that is easy
to discover.

The GRASS module document license is the same as the rest of the
software distribution, ie the GPL >=v2.

> In fact the Intro pages don't have anything.

fixed in svn.

> Should we include Creative commons license for the manual
> at each page with a link to explanation of what CC means?
> Or should we protect the manual by a stricter license or copyright
> and provide contact to person who will handle the request?
> ( first option looks much better to me)

IMHO we should provide the entire grass .tar.gz release under a single
license. To do other wise would be a mess, especially since the header
sections of the module help pages are directly derived from the GPL'd
module source code. (GPL2 sec. 2b)

Other parts of the project can use different licenses as appropriate,
although for flexibility it would be nice to promote common licenses
and ask that copyright be given to the project so that content can be
used and relicensed around the project's deliverable outputs as needed.

The MediaWiki content has been licensed under the GNU Free
Documentation License 1.2.

The website screenshots have been licensed under the CC-Attribution
ShareAlike 2.5 license.

The website generally asserts copyright without specifying a license.

If copyright is asserted, but not license terms, it just means you have
to ask the project before you copy/modify/redistribute the content or
assume terms. That's not a bug.


[the fwd'd message]
> A few months ago i started making a translation of the Grass manual  
> and after a lot of changes I prepared a greek manual according to my
> student needs.

It is unclear to me which "Grass manual" is being refered to.
The module help pages? intro pages? N&M's GRASS book? Programmer's
manual?

Regardless, this clearly sounds like a derived work.

> In the Greek manual I have allready referenced the grass manual but I
> didnt print it because i still dont have the right to translate the  
> english manual.
> Is there any way for me to print my book which is about Grass and  
> Qgis???
> I mean could I somehow take a letter from the Grass team in which  
> they will say that I have the right to print my book using as  
> basework their work in the english manual??

If it is the module help pages, then derived works are covered under
the terms of the GPL >=v2.


Hamish



      ____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile.  Try it now.  http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ 


_______________________________________________
grass-psc mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-psc
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: grass manual translations

Helena Mitasova
Hamish, see my second email about this for answers to some of your  
questions.

If I don't hear more comments I will email Nicolas that he does not  
need a letter
from us, he can go ahead and print his material and read the GPL2 for
more details on how to handle it. And if he has any more questions,
he should email to GRASS_dev list ? (although I assume he does not  
not subscribe)

thanks,

Helena


On Feb 23, 2008, at 11:01 PM, Hamish wrote:

> Helena Mitasova wrote:
>> I got an interesting question - see below.
>> I asked for more details, but when looking at the man pages
>> there is only Copyright by GRASS Development Team and
>> no license and no email who to contact in case somebody
>> wants to use/distribute/reprint etc. the material.
>
> The contact is the "GRASS Development Team". The email contact (if
> there should be one) should be the -psc or -dev lists, but that is  
> easy
> to discover.
>
> The GRASS module document license is the same as the rest of the
> software distribution, ie the GPL >=v2.
>
>> In fact the Intro pages don't have anything.
>
> fixed in svn.
>
>> Should we include Creative commons license for the manual
>> at each page with a link to explanation of what CC means?
>> Or should we protect the manual by a stricter license or copyright
>> and provide contact to person who will handle the request?
>> ( first option looks much better to me)
>
> IMHO we should provide the entire grass .tar.gz release under a single
> license. To do other wise would be a mess, especially since the header
> sections of the module help pages are directly derived from the GPL'd
> module source code. (GPL2 sec. 2b)
>
> Other parts of the project can use different licenses as appropriate,
> although for flexibility it would be nice to promote common licenses
> and ask that copyright be given to the project so that content can be
> used and relicensed around the project's deliverable outputs as  
> needed.
>
> The MediaWiki content has been licensed under the GNU Free
> Documentation License 1.2.
>
> The website screenshots have been licensed under the CC-Attribution
> ShareAlike 2.5 license.
>
> The website generally asserts copyright without specifying a license.
>
> If copyright is asserted, but not license terms, it just means you  
> have
> to ask the project before you copy/modify/redistribute the content or
> assume terms. That's not a bug.
>
>
> [the fwd'd message]
>> A few months ago i started making a translation of the Grass manual
>> and after a lot of changes I prepared a greek manual according to my
>> student needs.
>
> It is unclear to me which "Grass manual" is being refered to.
> The module help pages? intro pages? N&M's GRASS book? Programmer's
> manual?
>
> Regardless, this clearly sounds like a derived work.
>
>> In the Greek manual I have allready referenced the grass manual but I
>> didnt print it because i still dont have the right to translate the
>> english manual.
>> Is there any way for me to print my book which is about Grass and
>> Qgis???
>> I mean could I somehow take a letter from the Grass team in which
>> they will say that I have the right to print my book using as
>> basework their work in the english manual??
>
> If it is the module help pages, then derived works are covered under
> the terms of the GPL >=v2.
>
>
> Hamish
>
>
>
>        
> ______________________________________________________________________
> ______________
> Be a better friend, newshound, and
> know-it-all with Yahoo! Mobile.  Try it now.  http://
> mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
>
>

_______________________________________________
grass-psc mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-psc
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: grass manual translations

hamish-2
Helena Mitasova wrote:
> If I don't hear more comments I will email Nicolas that he does not  
> need a letter from us, he can go ahead and print his material and
> read the GPL2 for more details on how to handle it.


So he (or his publisher) doesn't get a rude shock later, make sure he
understands the part in the GPL which states that the derived work must
give its recipients the same rights as he was given, ie it must be
covered by the GPL as well. If he doesn't want the non-GRASS derived
parts of his book to be covered by the GPL he must print it as two
separate booklets.

A letter could be as simple as "You may redistribute the GRASS manuals,
and works derived from them, under the terms of the GPL version 2 or
newer."


Hamish



      ____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile.  Try it now.  http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ 


_______________________________________________
grass-psc mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-psc
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

GRASS part of NCSU OSI initiative

Helena Mitasova
In reply to this post by hamish-2
I would like to ask for a permission to list GRASS GIS as a project  
that is part
of the NCSU Open Source Initiative launched at NCSU in collaboration  
with RedHat.
At this point it just means that the project is listed on the OSI web  
site
and I will be working with OIT to get GRASS installed in campus labs and
make it available to several universities and colleges through  
Virtual Computing System (VCL)
(which leads  me to a question whether I should wait for final  
GRASS63 release or
we can start testing at least VCL with GRASS63RC5)

here is the link to the relevant web sites
https://opensource.ncsu.edu/FrontPage
https://opensource.ncsu.edu/OpenSourceProjects

(well, I already listed GRASS and then I realized that it should  
probably go through PSC,
so here is the request).
I assume that we don't need a vote on this and as long as nobody  
objects I am fine,

thank you

Helena

Helena Mitasova
Associate Professor
Department of Marine, Earth
and Atmospheric Sciences
1125 Jordan Hall, Campus Box 8208
North Carolina State University
Raleigh NC 27695-8208
http://skagit.meas.ncsu.edu/~helena/




_______________________________________________
grass-psc mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-psc
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: GRASS part of NCSU OSI initiative

Michael Barton
Helena,

I see no problem with this. Sounds like it fits within the general  
license requirements.

Michael
____________________
C. Michael Barton, Professor of Anthropology
Director of Graduate Studies
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University

Phone: 480-965-6262
Fax: 480-965-7671
www: <www.public.asu.edu/~cmbarton>



On Mar 13, 2008, at 10:19 PM, Helena Mitasova wrote:

> I would like to ask for a permission to list GRASS GIS as a project  
> that is part
> of the NCSU Open Source Initiative launched at NCSU in  
> collaboration with RedHat.
> At this point it just means that the project is listed on the OSI  
> web site
> and I will be working with OIT to get GRASS installed in campus  
> labs and
> make it available to several universities and colleges through  
> Virtual Computing System (VCL)
> (which leads  me to a question whether I should wait for final  
> GRASS63 release or
> we can start testing at least VCL with GRASS63RC5)
>
> here is the link to the relevant web sites
> https://opensource.ncsu.edu/FrontPage
> https://opensource.ncsu.edu/OpenSourceProjects
>
> (well, I already listed GRASS and then I realized that it should  
> probably go through PSC,
> so here is the request).
> I assume that we don't need a vote on this and as long as nobody  
> objects I am fine,
>
> thank you
>
> Helena
>
> Helena Mitasova
> Associate Professor
> Department of Marine, Earth
> and Atmospheric Sciences
> 1125 Jordan Hall, Campus Box 8208
> North Carolina State University
> Raleigh NC 27695-8208
> http://skagit.meas.ncsu.edu/~helena/
>
>
>
>
> _______________________________________________
> grass-psc mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/grass-psc

_______________________________________________
grass-psc mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-psc
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: GRASS part of NCSU OSI initiative

Dylan Beaudette
In reply to this post by Helena Mitasova
On Thursday 13 March 2008, Helena Mitasova wrote:

> I would like to ask for a permission to list GRASS GIS as a project
> that is part
> of the NCSU Open Source Initiative launched at NCSU in collaboration
> with RedHat.
> At this point it just means that the project is listed on the OSI web
> site
> and I will be working with OIT to get GRASS installed in campus labs and
> make it available to several universities and colleges through
> Virtual Computing System (VCL)
> (which leads  me to a question whether I should wait for final
> GRASS63 release or
> we can start testing at least VCL with GRASS63RC5)
>
> here is the link to the relevant web sites
> https://opensource.ncsu.edu/FrontPage
> https://opensource.ncsu.edu/OpenSourceProjects
>
> (well, I already listed GRASS and then I realized that it should
> probably go through PSC,
> so here is the request).
> I assume that we don't need a vote on this and as long as nobody
> objects I am fine,
>
> thank you
>
> Helena

Looks ok to me. I wonder if UC Davis has something like this.... :)

Dylan

>
> Helena Mitasova
> Associate Professor
> Department of Marine, Earth
> and Atmospheric Sciences
> 1125 Jordan Hall, Campus Box 8208
> North Carolina State University
> Raleigh NC 27695-8208
> http://skagit.meas.ncsu.edu/~helena/
>
>
>
>
> _______________________________________________
> grass-psc mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/grass-psc



--
Dylan Beaudette
Soil Resource Laboratory
http://casoilresource.lawr.ucdavis.edu/
University of California at Davis
530.754.7341
_______________________________________________
grass-psc mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-psc
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: GRASS part of NCSU OSI initiative

Markus Neteler
In reply to this post by Michael Barton
Helena,

it looks good to me.

Markus

On Fri, Mar 14, 2008 at 5:25 PM, Michael Barton <[hidden email]> wrote:

> Helena,
>
>  I see no problem with this. Sounds like it fits within the general license
> requirements.
>
>  Michael
>  ____________________
>  C. Michael Barton, Professor of Anthropology
>  Director of Graduate Studies
>  School of Human Evolution & Social Change
>  Center for Social Dynamics & Complexity
>  Arizona State University
>
>  Phone: 480-965-6262
>  Fax: 480-965-7671
>  www: <www.public.asu.edu/~cmbarton>
>
>
>
>
>
>  On Mar 13, 2008, at 10:19 PM, Helena Mitasova wrote:
>
>
> > I would like to ask for a permission to list GRASS GIS as a project that
> is part
> > of the NCSU Open Source Initiative launched at NCSU in collaboration with
> RedHat.
> > At this point it just means that the project is listed on the OSI web site
> > and I will be working with OIT to get GRASS installed in campus labs and
> > make it available to several universities and colleges through Virtual
> Computing System (VCL)
> > (which leads  me to a question whether I should wait for final GRASS63
> release or
> > we can start testing at least VCL with GRASS63RC5)
> >
> > here is the link to the relevant web sites
> > https://opensource.ncsu.edu/FrontPage
> > https://opensource.ncsu.edu/OpenSourceProjects
> >
> > (well, I already listed GRASS and then I realized that it should probably
> go through PSC,
> > so here is the request).
> > I assume that we don't need a vote on this and as long as nobody objects I
> am fine,
> >
> > thank you
> >
> > Helena
> >
> > Helena Mitasova
> > Associate Professor
> > Department of Marine, Earth
> > and Atmospheric Sciences
> > 1125 Jordan Hall, Campus Box 8208
> > North Carolina State University
> > Raleigh NC 27695-8208
> > http://skagit.meas.ncsu.edu/~helena/
_______________________________________________
grass-psc mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-psc
Loading...