; >>
>> >> giovanni
>> >>
>> >> 2012/3/26 Peter Borissow
>> >>
>> >>> Do you need to GPL all of SETANTE or just the glueware (e.g. QGIS
>> plugin)?
>> >>> In otherwords, is there a way to keep the SEXTANTE core MIT or L
here a way to keep the SEXTANTE core MIT or LGPL?
> >>>
> >>>
> >>> --
> >>> *From:* Victor Olaya
> >>> *To:* cavall...@faunalia.it
> >>> *Cc:* qgis-developer@lists.osgeo.org
> >>> *
-
>>> *From:* Victor Olaya
>>> *To:* cavall...@faunalia.it
>>> *Cc:* qgis-developer@lists.osgeo.org
>>> *Sent:* Monday, March 26, 2012 6:10 AM
>>> *Subject:* Re: [Qgis-developer] Directions needed for GSOC Proposal
>>>
>>> Then, I
;
>>
>> --
>> *From:* Victor Olaya
>> *To:* cavall...@faunalia.it
>> *Cc:* qgis-developer@lists.osgeo.org
>> *Sent:* Monday, March 26, 2012 6:10 AM
>> *Subject:* Re: [Qgis-developer] Directions needed for GSOC Proposal
>>
Ok, it's clear now Vincent.
The exception is only related to system libraries, while it doesn't apply
to code that executes inside a GPL application (which doesn't provide the
exception).
2012/3/26 G. Allegri
>
>> > > Generally, you can link to a non-free library from a GPL code if you
>> > >
>
>
> > > Generally, you can link to a non-free library from a GPL code if you
> > > deliver
> > > your GPL code with a specific exception for that non-free library.
>
I understand that you can link proprietary code IF you add a specific
exception.
I cannot grasp the point, but I give up for now
Hi,
> So, the statement "you can import/link proprietary code into gpl code,
> provided you have a license to do it." should be extended with "if you add
> an exception to the license", right?
No, it's a general statement, reread my post.
> So the problem is that QGis license should contain these
Thanks Vincent.
So, the statement "you can import/link proprietary code into gpl code,
provided you have a license to do it." should be extended with "if you add
an exception to the license", right?
So the problem is that QGis license should contain these exceptions on
behalf of all the plugins? I
Hi,
Well, this is not an easy topic, but everything is answered in the GNU FAQ on
licences :
http://www.gnu.org/licenses/gpl-faq.html
To shorten a bit and in relation to what has been said before.
There is an exception to the GPL licence for system libraries. It does not
apply here, as we are ta
I would really appreciate if you could explain me this point, seriously.
giovanni
2012/3/26 G. Allegri
> I apologize for my ignorance, could you explain me the differences?
> You say that I cannot do an import in python to load ArcGIS code, but here
> you say that I can import/link proprietary
I apologize for my ignorance, could you explain me the differences?
You say that I cannot do an import in python to load ArcGIS code, but here
you say that I can import/link proprietary code in GPL code.I see a
contradiction here.
I apologize again if I cannot get to the point...
giovanni
2012/3/
Il 26/03/2012 15:08, G. Allegri ha scritto:
> Have I misunderstood it?
yes
--
Paolo Cavallini - Faunalia
www.faunalia.eu
Full contact details at www.faunalia.eu/pc
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/ma
>
> you can import/link proprietary code into gpl code, provided you have a
> license to do it.
> all the best.
>
It's exactly the opposite of what you're saying on the other thread.
You're saying that it's illegal to import proprietary code into a qgis
python plugin. Have I misunderstood it?
gi
Il 26/03/2012 14:26, G. Allegri ha scritto:
> I would keep it LGPL. I'm not interested in wrapping it in proprietary code,
> but to
> use proprietary code through SEXTANTE...
you can import/link proprietary code into gpl code, provided you have a license
to do it.
all the best.
--
Paolo Cavalli
XTANTE core MIT or LGPL?
>
>
> --
> *From:* Victor Olaya
> *To:* cavall...@faunalia.it
> *Cc:* qgis-developer@lists.osgeo.org
> *Sent:* Monday, March 26, 2012 6:10 AM
> *Subject:* Re: [Qgis-developer] Directions needed for GSOC Proposal
>
>
AM
Subject: Re: [Qgis-developer] Directions needed for GSOC Proposal
Then, I guess there is no discussion. As I said, in this case there is
no difference from my point of view, so GPL is a good option for
SEXTANTE
Regards
___
Qgis-developer mailing
On Mon, 26 Mar 2012 14:43:50 +0530
"arunthe...@gmail.com" wrote:
> Hello all,
>
> On Mon, Mar 26, 2012 at 1:37 PM, Victor Olaya
> wrote:
>
> > If the work to do is based on SEXTANTE, then I am definitely
> > available, and really willing to do it :-)
>
> Thank you all. So, I think finally I h
2012/3/26 Vincent Picavet
> Hi,
>
> Le lundi 26 mars 2012 12:01:20, Paolo Cavallini a écrit :
> > Il 26/03/2012 12:01, G. Allegri ha scritto:
> > > I think the GPL code is mandatory for the "bridge", eventually. Not all
> > > the underlying code requires to be GPL. Am I wrong?
> >
> > I did some
Hi,
> > I did some research as well, and came to the same conclusion.
> > Studies have been done (by the zope group among others), and this is the
> > general final statement.
> >
> > Vincent
>
> We need to capture this knowledge along with backlinks to original
> articles as this is a topic tha
Hi
On Mon, Mar 26, 2012 at 12:09 PM, Vincent Picavet
wrote:
> Hi,
>
> Le lundi 26 mars 2012 12:01:20, Paolo Cavallini a écrit :
>> Il 26/03/2012 12:01, G. Allegri ha scritto:
>> > I think the GPL code is mandatory for the "bridge", eventually. Not all
>> > the underlying code requires to be GPL.
Then, I guess there is no discussion. As I said, in this case there is
no difference from my point of view, so GPL is a good option for
SEXTANTE
Regards
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinf
Hi,
Le lundi 26 mars 2012 12:01:20, Paolo Cavallini a écrit :
> Il 26/03/2012 12:01, G. Allegri ha scritto:
> > I think the GPL code is mandatory for the "bridge", eventually. Not all
> > the underlying code requires to be GPL. Am I wrong?
>
> I did some research on this, and the conclusion is th
Il 26/03/2012 12:01, G. Allegri ha scritto:
> I think the GPL code is mandatory for the "bridge", eventually. Not all the
> underlying code requires to be GPL. Am I wrong?
I did some research on this, and the conclusion is that import is functionally
and
legally equivalent to linking during comp
>
> Good to know. I think using qgis-python requires linking (importing) code
> to be GPL.
I think the GPL code is mandatory for the "bridge", eventually. Not all the
underlying code requires to be GPL. Am I wrong?
giovanni
2012/3/26 arunthe...@gmail.com
> Hello all,
>
> On Mon, Mar 26, 2012
Hello all,
On Mon, Mar 26, 2012 at 1:37 PM, Victor Olaya wrote:
>
>
> If the work to do is based on SEXTANTE, then I am definitely
> available, and really willing to do it :-)
>
>
Thank you all. So, I think finally I have got my answer :)
/me goes to write his proposal
--
Regards
Arunmozhi
Tw
>> I'm available, even though there may be more effective mentors for
>> this. I do not know if he's available, but in case you choose
>> sextante, Victor seems the natural choice.
If the work to do is based on SEXTANTE, then I am definitely
available, and really willing to do it :-)
Regards
On Mon, 26 Mar 2012 08:54:22 +0200
Paolo Cavallini wrote:
> Il 25/03/2012 13:21, Anne Ghisla ha scritto:
>
> > I would add:
> > - who is available to mentor it full time?
>
> I'm available, even though there may be more effective mentors for
> this. I do not know if he's available, but in case
Il 25/03/2012 23:53, Victor Olaya ha scritto:
> However, I selected MIT for the Java SEXTANTE code to allow for
> integration in any kind of software. Since this Python version is just
> developed to work with QGIS, GPL does not sound bad to me, in case the
> MIT license is an issue.
Good to know
Il 25/03/2012 13:21, Anne Ghisla ha scritto:
> I would add:
> - who is available to mentor it full time?
I'm available, even though there may be more effective mentors for this.
I do not know if he's available, but in case you choose sextante, Victor seems
the
natural choice.
All the best.
--
P
>> I would vote for the Framework. About deciding which of the two, I think
>> sextante
>> should be more mature, therefore a better candidate, so:
>> - please Victor share your feelings about that
>> - what is the license of sextante?
I had thought of a MIT license, but I have included some GPLe
> Date: Sat, 24 Mar 2012 23:20:34 +0530
> From: "arunthe...@gmail.com"
> Subject: [Qgis-developer] Directions needed for GSOC Proposal
> To: qgis-developer
> Message-ID:
>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hello all,
>
Hi
On Sat, Mar 24, 2012 at 7:57 PM, Paolo Cavallini wrote:
> Il 24/03/2012 18:50, arunthe...@gmail.com ha scritto:
>
>> Which one is going to be adopted? And is the one that will be adopted ready
>> to take
>> in a GSOC student and provide mentoring? While I have been a self-learner
>> for the
On Sat, 24 Mar 2012 18:57:49 +0100
Paolo Cavallini wrote:
> Il 24/03/2012 18:50, arunthe...@gmail.com ha scritto:
>
> > Which one is going to be adopted? And is the one that will be
> > adopted ready to take in a GSOC student and provide mentoring?
> > While I have been a self-learner for the m
Il 24/03/2012 18:50, arunthe...@gmail.com ha scritto:
> Which one is going to be adopted? And is the one that will be adopted ready
> to take
> in a GSOC student and provide mentoring? While I have been a self-learner
> for the
> most part, its still a serious thing when we talk about code goin
Hello all,
There have been prevoius discussions about this GSOC thing. Adding
analytical power to the software can be the best thing that can be done to
QGIS. Initially I was of the idea of porting fTools to C++, but then
realized the processing framework to be a better option. Now that there are
35 matches
Mail list logo
