Re: [postgis-users] The first release of the PostGIS Add-ons is out!
I would have gone with a license saying You can modify and redistribute as long as the derived work is also under an open license, not necessarily GPL. Does that make sense? Does that exist? http://en.wikipedia.org/wiki/WTFPL Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ___ postgis-users mailing list postgis-users@lists.osgeo.org http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
Re: [postgis-users] The first release of the PostGIS Add-ons is out!
Not really the same thing as I said... ;-) I would prefer You just DO WHAT THE FUCK YOU WANT TO as long as it stay open... -Original Message- From: postgis-users-boun...@lists.osgeo.org [mailto:postgis-users- boun...@lists.osgeo.org] On Behalf Of Mateusz Loskot Sent: Wednesday, November 20, 2013 9:52 AM To: PostGIS Users Discussion Subject: Re: [postgis-users] The first release of the PostGIS Add-ons is out! I would have gone with a license saying You can modify and redistribute as long as the derived work is also under an open license, not necessarily GPL. Does that make sense? Does that exist? http://en.wikipedia.org/wiki/WTFPL Best regards, -- Mateusz Loskot, http://mateusz.loskot.net ___ postgis-users mailing list postgis-users@lists.osgeo.org http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users ___ postgis-users mailing list postgis-users@lists.osgeo.org http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
Re: [postgis-users] The first release of the PostGIS Add-ons is out!
On Wed, Nov 20, 2013 at 09:56:56AM -0500, Pierre Racine wrote: Not really the same thing as I said... ;-) I would prefer You just DO WHAT THE FUCK YOU WANT TO as long as it stay open... That's GPL, really. The only reason for people NOT to like it is when they want to craft some piece of closed source and still use what you send out to the world as an open component. --strk; ___ postgis-users mailing list postgis-users@lists.osgeo.org http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
Re: [postgis-users] The first release of the PostGIS Add-ons is out!
There is a very big difference between :' i tweak one of your function, so my tweak must be open source' and 'i use one of your function, so my code must be open source'. Unfortunately GPL imposes both. Cheers, Rémi-C 2013/11/20 Sandro Santilli s...@keybit.net On Wed, Nov 20, 2013 at 09:56:56AM -0500, Pierre Racine wrote: Not really the same thing as I said... ;-) I would prefer You just DO WHAT THE FUCK YOU WANT TO as long as it stay open... That's GPL, really. The only reason for people NOT to like it is when they want to craft some piece of closed source and still use what you send out to the world as an open component. --strk; ___ postgis-users mailing list postgis-users@lists.osgeo.org http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users ___ postgis-users mailing list postgis-users@lists.osgeo.org http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
Re: [postgis-users] The first release of the PostGIS Add-ons is out!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 20/11/2013 16:32, Rémi Cura ha scritto: There is a very big difference between :' i tweak one of your function, so my tweak must be open source' and 'i use one of your function, so my code must be open source'. Unfortunately GPL imposes both. from my point of view, this is a Very Good Thing - -- Paolo Cavallini - www.faunalia.eu Corsi QGIS e PostGIS: http://www.faunalia.eu/training.html -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.15 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlKM1r4ACgkQ/NedwLUzIr5SaACgoM78J5gKMoo2lFG/Qqx24hCJ UUoAoKgOIIakZ/HvbL94jT4gGVoWFQis =iyTi -END PGP SIGNATURE- ___ postgis-users mailing list postgis-users@lists.osgeo.org http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
Re: [postgis-users] The first release of the PostGIS Add-ons is out!
On Wed, Nov 20, 2013 at 04:32:12PM +0100, Rémi Cura wrote: There is a very big difference between :' i tweak one of your function, so my tweak must be open source' and 'i use one of your function, so my code must be open source'. Unfortunately GPL imposes both. It's not unfortunate, it's the price some free software authors want to attach to their products. They don't want a profit for themselves but for the community at large, in form of more free software availability. --strk; ___ postgis-users mailing list postgis-users@lists.osgeo.org http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
Re: [postgis-users] The first release of the PostGIS Add-ons is out!
This is not as simple, Many open source software are not GPL (starting from standard implementing api ), including postgres ! GPL is not always the answer, and here I don't think it is. For me it should be a more open license, and the project should be hosted on the postgis github. Cheers, Rémi-C 2013/11/20 Sandro Santilli s...@keybit.net On Wed, Nov 20, 2013 at 04:32:12PM +0100, Rémi Cura wrote: There is a very big difference between :' i tweak one of your function, so my tweak must be open source' and 'i use one of your function, so my code must be open source'. Unfortunately GPL imposes both. It's not unfortunate, it's the price some free software authors want to attach to their products. They don't want a profit for themselves but for the community at large, in form of more free software availability. --strk; ___ postgis-users mailing list postgis-users@lists.osgeo.org http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users ___ postgis-users mailing list postgis-users@lists.osgeo.org http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
Re: [postgis-users] The first release of the PostGIS Add-ons is out!
Hi, I would prefer You just DO WHAT THE FUCK YOU WANT TO as long as it stay open... That's GPL, really. The only reason for people NOT to like it is when they want to craft some piece of closed source and still use what you send out to the world as an open component. Another reason is when the GPL itself is not clear on how it can be applied to some code, because it has been written for compiled code initially. If someone can explain clearly how GPL terms apply to Pl/PgSQL code, I would be glad to hear it. Otherwise it is just adding confusion to something which should be simple, and first people concerned are not proprietary software developers, but opensource developers and wannabe contributors. And last reason is the kind of reason we just had with SFCGAL : incompatibilities between opensource licence. If you begin to annoy opensource developers wanting to do some opensource code, you just reach the opposite goal of your initial intent. This does harm. Vincent ___ postgis-users mailing list postgis-users@lists.osgeo.org http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
Re: [postgis-users] The first release of the PostGIS Add-ons is out!
On Nov 20, 2013, at 3:48 PM, Pierre Racine wrote: Salut Pierre, Thanks Vincent for this input. I'll go for GPL for now as it's that a nightmare to change afterward if, really, someone complains. I'm agree with Remi and Vincent points. And i don't see there, any coming code valuable enough to be protected against monsters. Pl/PgSQL codes, as an interpreted language, are not designed to implement real data treatment, and Pl/PgSQL code will be too close to PostgreSQL and PostGIS to be reused in some other project than PostGIS itself So what ? P.S: Anyhow launching a new app with a licence flame could be also a way to make people talk about it... ^^ O. ___ postgis-users mailing list postgis-users@lists.osgeo.org http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
Re: [postgis-users] The first release of the PostGIS Add-ons is out!
I knew we would fall into a license nightmare... So far we've got suggestions for No rights reserved, BSD, Creative Common Zero, GPL, LGPL, MIT... Any of these license would make it hard to move a function from the Add-ons to PostGIS core? That would be a good candidate for elimination. Why people do not like the PostGIS GPL? Pierre -Original Message- From: postgis-users-boun...@lists.osgeo.org [mailto:postgis-users- boun...@lists.osgeo.org] On Behalf Of Mathieu Basille Sent: Monday, November 18, 2013 2:04 PM To: PostGIS Users Discussion Subject: Re: [postgis-users] The first release of the PostGIS Add-ons is out! Le 11/18/2013 12:25 PM, Stephen Woodbridge a écrit : On 11/18/2013 12:20 PM, Mateusz Loskot wrote: On 18 November 2013 17:13, Pierre Racine pierre.rac...@sbf.ulaval.ca wrote: I'm a license ignorant. Release it into the public domain and include a statement that you release all rights adding No rights reserved. Best regards, +1 on this because it is the most friendly and can be used by everyone regardless of license that they are using. It absolutely has no license conflicts. Although I'm a very big fan of public domain, it has its own limitations. For instance, some countries (randomly picked: France) do not allow one to declare its creation in the public domain. This is something that's granted from its nature (e.g. a representative speech or a math formula) or that is gained after a couple of decades after the death of the author (which is quite unlikely for PostGIS). Instead, I would much favor explicit licenses, such as the much simple (2-clauses) BSD [1] or the Creative Common Zero [2]. Both of them give the user the maximum flexibility and make sure there is no license conflict afterwards. The BSD, my favorite, is also super easy to read and understand. Sincerely, Mathieu. [1] http://opensource.org/licenses/BSD-2-Clause [2] https://creativecommons.org/publicdomain/zero/1.0/ Best, -Steve ___ postgis-users mailing list postgis-users@lists.osgeo.org http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users -- ~$ whoami Mathieu Basille, PhD ~$ locate --details University of Florida \\ Fort Lauderdale Research and Education Center (+1) 954-577-6314 http://ase-research.org/basille ~$ fortune « Le tout est de tout dire, et je manque de mots Et je manque de temps, et je manque d'audace. » -- Paul Éluard ___ postgis-users mailing list postgis-users@lists.osgeo.org http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users ___ postgis-users mailing list postgis-users@lists.osgeo.org http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
Re: [postgis-users] The first release of the PostGIS Add-ons is out!
I guess the fact that PL/pgSQL is not compiled and hence is open by nature should have an incidence on the choice of the license. No? I bend toward GPL in any case... -Original Message- From: postgis-users-boun...@lists.osgeo.org [mailto:postgis-users- boun...@lists.osgeo.org] On Behalf Of Pierre Racine Sent: Tuesday, November 19, 2013 1:45 PM To: PostGIS Users Discussion Subject: Re: [postgis-users] The first release of the PostGIS Add-ons is out! I knew we would fall into a license nightmare... So far we've got suggestions for No rights reserved, BSD, Creative Common Zero, GPL, LGPL, MIT... Any of these license would make it hard to move a function from the Add- ons to PostGIS core? That would be a good candidate for elimination. Why people do not like the PostGIS GPL? Pierre -Original Message- From: postgis-users-boun...@lists.osgeo.org [mailto:postgis-users- boun...@lists.osgeo.org] On Behalf Of Mathieu Basille Sent: Monday, November 18, 2013 2:04 PM To: PostGIS Users Discussion Subject: Re: [postgis-users] The first release of the PostGIS Add-ons is out! Le 11/18/2013 12:25 PM, Stephen Woodbridge a écrit : On 11/18/2013 12:20 PM, Mateusz Loskot wrote: On 18 November 2013 17:13, Pierre Racine pierre.rac...@sbf.ulaval.ca wrote: I'm a license ignorant. Release it into the public domain and include a statement that you release all rights adding No rights reserved. Best regards, +1 on this because it is the most friendly and can be used by everyone regardless of license that they are using. It absolutely has no license conflicts. Although I'm a very big fan of public domain, it has its own limitations. For instance, some countries (randomly picked: France) do not allow one to declare its creation in the public domain. This is something that's granted from its nature (e.g. a representative speech or a math formula) or that is gained after a couple of decades after the death of the author (which is quite unlikely for PostGIS). Instead, I would much favor explicit licenses, such as the much simple (2-clauses) BSD [1] or the Creative Common Zero [2]. Both of them give the user the maximum flexibility and make sure there is no license conflict afterwards. The BSD, my favorite, is also super easy to read and understand. Sincerely, Mathieu. [1] http://opensource.org/licenses/BSD-2-Clause [2] https://creativecommons.org/publicdomain/zero/1.0/ Best, -Steve ___ postgis-users mailing list postgis-users@lists.osgeo.org http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users -- ~$ whoami Mathieu Basille, PhD ~$ locate --details University of Florida \\ Fort Lauderdale Research and Education Center (+1) 954-577-6314 http://ase-research.org/basille ~$ fortune « Le tout est de tout dire, et je manque de mots Et je manque de temps, et je manque d'audace. » -- Paul Éluard ___ postgis-users mailing list postgis-users@lists.osgeo.org http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users ___ postgis-users mailing list postgis-users@lists.osgeo.org http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users ___ postgis-users mailing list postgis-users@lists.osgeo.org http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
Re: [postgis-users] The first release of the PostGIS Add-ons is out!
How could we avoid a license discussion... :) . I think there are two relevant points from the discussion: 1) It should be licensed such that it can go into core if such an option for some or all functions reveals itself in the future 2) It should be flexible enough for wide reuse. #1 precludes all licenses not GPL compatible. #2 precludes the GPL. IMHO, It's fine (actually wonderful) that postgis is in the GPL, it protects the project and does not really limit its use in any substantive way. It's big enough to stand on its own. But re: #2 GPL would limit the wide use of these scripts. If all the above is true, then what are the options? MIT and CC-0? I don't know, but someone on this list does... . Best, Steve On Tue, Nov 19, 2013 at 2:13 PM, Pierre Racine pierre.rac...@sbf.ulaval.cawrote: I guess the fact that PL/pgSQL is not compiled and hence is open by nature should have an incidence on the choice of the license. No? I bend toward GPL in any case... -Original Message- From: postgis-users-boun...@lists.osgeo.org [mailto:postgis-users- boun...@lists.osgeo.org] On Behalf Of Pierre Racine Sent: Tuesday, November 19, 2013 1:45 PM To: PostGIS Users Discussion Subject: Re: [postgis-users] The first release of the PostGIS Add-ons is out! I knew we would fall into a license nightmare... So far we've got suggestions for No rights reserved, BSD, Creative Common Zero, GPL, LGPL, MIT... Any of these license would make it hard to move a function from the Add- ons to PostGIS core? That would be a good candidate for elimination. Why people do not like the PostGIS GPL? Pierre -Original Message- From: postgis-users-boun...@lists.osgeo.org [mailto:postgis-users- boun...@lists.osgeo.org] On Behalf Of Mathieu Basille Sent: Monday, November 18, 2013 2:04 PM To: PostGIS Users Discussion Subject: Re: [postgis-users] The first release of the PostGIS Add-ons is out! Le 11/18/2013 12:25 PM, Stephen Woodbridge a écrit : On 11/18/2013 12:20 PM, Mateusz Loskot wrote: On 18 November 2013 17:13, Pierre Racine pierre.rac...@sbf.ulaval.ca wrote: I'm a license ignorant. Release it into the public domain and include a statement that you release all rights adding No rights reserved. Best regards, +1 on this because it is the most friendly and can be used by everyone regardless of license that they are using. It absolutely has no license conflicts. Although I'm a very big fan of public domain, it has its own limitations. For instance, some countries (randomly picked: France) do not allow one to declare its creation in the public domain. This is something that's granted from its nature (e.g. a representative speech or a math formula) or that is gained after a couple of decades after the death of the author (which is quite unlikely for PostGIS). Instead, I would much favor explicit licenses, such as the much simple (2-clauses) BSD [1] or the Creative Common Zero [2]. Both of them give the user the maximum flexibility and make sure there is no license conflict afterwards. The BSD, my favorite, is also super easy to read and understand. Sincerely, Mathieu. [1] http://opensource.org/licenses/BSD-2-Clause [2] https://creativecommons.org/publicdomain/zero/1.0/ Best, -Steve ___ postgis-users mailing list postgis-users@lists.osgeo.org http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users -- ~$ whoami Mathieu Basille, PhD ~$ locate --details University of Florida \\ Fort Lauderdale Research and Education Center (+1) 954-577-6314 http://ase-research.org/basille ~$ fortune « Le tout est de tout dire, et je manque de mots Et je manque de temps, et je manque d'audace. » -- Paul Éluard ___ postgis-users mailing list postgis-users@lists.osgeo.org http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users ___ postgis-users mailing list postgis-users@lists.osgeo.org http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users ___ postgis-users mailing list postgis-users@lists.osgeo.org http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users ___ postgis-users mailing list postgis-users@lists.osgeo.org http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
Re: [postgis-users] The first release of the PostGIS Add-ons is out!
IMHO, It's fine (actually wonderful) that postgis is in the GPL, it protects the project and does not really limit its use in any substantive way. It's big enough to stand on its own. But re: #2 GPL would limit the wide use of these scripts. How would GPL limit the wide use of these scripts? I find it's ok that any derivative be licensed the same way. It doesn't force a using software to be completely under GPL, just the derivative scripts of those scripts. It seems to me that the fact that PL/pgSQL is open by nature makes it very easy to redistribute these files or any derivative with the same license without limiting the rest of the software to be under any other kind of license. Does that make sense? Pierre ___ postgis-users mailing list postgis-users@lists.osgeo.org http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
Re: [postgis-users] The first release of the PostGIS Add-ons is out!
Oh, I prefer GPL, and in this case, since it's uncompiled code it probably doesn't matter. I just know lots of people belly ache about the GPL, so I'm trying to insert that perspective... . :) On Tue, Nov 19, 2013 at 2:42 PM, Pierre Racine pierre.rac...@sbf.ulaval.cawrote: IMHO, It's fine (actually wonderful) that postgis is in the GPL, it protects the project and does not really limit its use in any substantive way. It's big enough to stand on its own. But re: #2 GPL would limit the wide use of these scripts. How would GPL limit the wide use of these scripts? I find it's ok that any derivative be licensed the same way. It doesn't force a using software to be completely under GPL, just the derivative scripts of those scripts. It seems to me that the fact that PL/pgSQL is open by nature makes it very easy to redistribute these files or any derivative with the same license without limiting the rest of the software to be under any other kind of license. Does that make sense? Pierre ___ postgis-users mailing list postgis-users@lists.osgeo.org http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users ___ postgis-users mailing list postgis-users@lists.osgeo.org http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
Re: [postgis-users] The first release of the PostGIS Add-ons is out!
Its your code, pick the one you want. +1. If there was one true answer to the licensing question, this would be it. -bborie ___ postgis-users mailing list postgis-users@lists.osgeo.org http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
Re: [postgis-users] The first release of the PostGIS Add-ons is out!
Sorry to be a little bit late in the discussion, but in my opinion, there are really two sensible solutions: 1) Use the most simple and liberal (permissive) license. No license is not an option, since it means copyright by default, and public domain is not a good option due to specific issues in some countries. With this approach, the BSD is probably the best choice: the license is very short, and very easy to read and understand. This would basically allow anybody to reuse parts or whole of the code in open source or proprietary projects. 2) Stick to the PostGIS license as you suggest. This can be justified by the fact that the code would be hard to reuse without PostGIS itself, so that it's not such a big deal to restrict the reuse of the code... As the others said, if you're more comfortable with it, stick to it! However, keep in mind, that, if you have many contributions, it would make a latter change to a more liberal license all the more difficult (every other authors would have to give his agreement). This doesn't make it a bad choice, though, but it's better to know the pros and cons in advance! Mathieu. Le 11/19/2013 03:48 PM, Pierre Racine a écrit : 1. If it is GPL and I add it to my code them my code has to be licensed undr GPL. This is problematic for most business. If I have a proprietary product that I'm spent 100's of thousands of hours to develop and believe that it is critical to my success, there is no way that I can afford to allow GPL code into it. This is not a judgement call on the correctness of this thinking. And the GPL advocates will have similar arguments from their point of view. My point is that, if you want to integrate it with something more restrictive, it is always very easy to separate them in different files with a different licensing scheme mostly because PL/pgSQL is not compiled. I'm going with GPL... Pierre ___ postgis-users mailing list postgis-users@lists.osgeo.org http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users -- ~$ whoami Mathieu Basille, PhD ~$ locate --details University of Florida \\ Fort Lauderdale Research and Education Center (+1) 954-577-6314 http://ase-research.org/basille ~$ fortune « Le tout est de tout dire, et je manque de mots Et je manque de temps, et je manque d'audace. » -- Paul Éluard ___ postgis-users mailing list postgis-users@lists.osgeo.org http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
[postgis-users] The first release of the PostGIS Add-ons is out!
Hey! I'm glad today to launch the PostGIS Add-ons. This new PostGIS extension aims at providing a quick, more Agile way to release pure PL/pgSQL functions developed by the PostGIS user community. It includes 15 new functions. Among them, two functions to aggregate raster/vector overlay statistics, one to extract values from a vector coverage to a raster, one to generate random points inside a polygon and two new aggregates functions helping removing overlaps in a table of geometry. Read more about the PostGIS Add-ons at http://geospatialelucubrations.blogspot.ca/2013/11/launching-postgis-add-ons-new-postgis.html Pierre ___ postgis-users mailing list postgis-users@lists.osgeo.org http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
Re: [postgis-users] The first release of the PostGIS Add-ons is out!
Good point. I'm such not a license guy Should be the same as PostGIS (GPL). I will add license notice in the next release (very soon!). Pierre -Original Message- From: postgis-users-boun...@lists.osgeo.org [mailto:postgis-users- boun...@lists.osgeo.org] On Behalf Of Rémi Cura Sent: Monday, November 18, 2013 11:49 AM To: PostGIS Users Discussion Subject: Re: [postgis-users] The first release of the PostGIS Add-ons is out! Very cool idea. I have a lot of plpgsql functions. One more detail : what about licenses? Cheers, Rémi-C 2013/11/18 Pierre Racine pierre.rac...@sbf.ulaval.ca Hey! I'm glad today to launch the PostGIS Add-ons. This new PostGIS extension aims at providing a quick, more Agile way to release pure PL/pgSQL functions developed by the PostGIS user community. It includes 15 new functions. Among them, two functions to aggregate raster/vector overlay statistics, one to extract values from a vector coverage to a raster, one to generate random points inside a polygon and two new aggregates functions helping removing overlaps in a table of geometry. Read more about the PostGIS Add-ons at http://geospatialelucubrations.blogspot.ca/2013/11/launching-postgis- add-ons-new-postgis.html Pierre ___ postgis-users mailing list postgis-users@lists.osgeo.org http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users ___ postgis-users mailing list postgis-users@lists.osgeo.org http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
Re: [postgis-users] The first release of the PostGIS Add-ons is out!
Sorry for the license, I needed a clear answer :-) I personnaly would prefere LGPL, like postgres. can you consider to use a template doc (wiki in github?, or pure markdown) , more detailled than just in code comment? I feel the current PostGIS doc per function should be a lower limit of documentation. Also important : you may quickely go to several dozens of functions, why not decide now for an architecture (classifying the contrib), maybe with label, maybe with classical folders? Like raster, util, rewrite, etc etc. Last : what is the process for a contrib to be accepted? Surely it should be tested by another personn than dev before being added? Cheers, Rémi-C 2013/11/18 Pierre Racine pierre.rac...@sbf.ulaval.ca Good point. I'm such not a license guy Should be the same as PostGIS (GPL). I will add license notice in the next release (very soon!). Pierre -Original Message- From: postgis-users-boun...@lists.osgeo.org [mailto:postgis-users- boun...@lists.osgeo.org] On Behalf Of Rémi Cura Sent: Monday, November 18, 2013 11:49 AM To: PostGIS Users Discussion Subject: Re: [postgis-users] The first release of the PostGIS Add-ons is out! Very cool idea. I have a lot of plpgsql functions. One more detail : what about licenses? Cheers, Rémi-C 2013/11/18 Pierre Racine pierre.rac...@sbf.ulaval.ca Hey! I'm glad today to launch the PostGIS Add-ons. This new PostGIS extension aims at providing a quick, more Agile way to release pure PL/pgSQL functions developed by the PostGIS user community. It includes 15 new functions. Among them, two functions to aggregate raster/vector overlay statistics, one to extract values from a vector coverage to a raster, one to generate random points inside a polygon and two new aggregates functions helping removing overlaps in a table of geometry. Read more about the PostGIS Add-ons at http://geospatialelucubrations.blogspot.ca/2013/11/launching-postgis- add-ons-new-postgis.html Pierre ___ postgis-users mailing list postgis-users@lists.osgeo.org http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users ___ postgis-users mailing list postgis-users@lists.osgeo.org http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users ___ postgis-users mailing list postgis-users@lists.osgeo.org http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
Re: [postgis-users] The first release of the PostGIS Add-ons is out!
Humm.. Lots of requirements... Sorry for the license, I needed a clear answer :-) I personnaly would prefere LGPL, like postgres. Doesn't seems like a good idea to make it different than PostGIS. How is LGPL different from LPG? I'm a license ignorant. can you consider to use a template doc (wiki in github?, or pure markdown) , more detailled than just in code comment? I feel the current PostGIS doc per function should be a lower limit of documentation. There is a quick list of available functions at the beginning of the file. I would rather go for less maintenance as possible. If you want to copy/remove the doc from the file to the wiki. Feel free to do it. Also important : you may quickely go to several dozens of functions, why not decide now for an architecture (classifying the contrib), maybe with label, maybe with classical folders? Like raster, util, rewrite, etc etc. A small step at a time... Last : what is the process for a contrib to be accepted? Surely it should be tested by another personn than dev before being added? I wrote some criterias at the beginning of the file. It goes like this: -your function is written in pure PL/pgSQL (no C!), -your function is generic enough to be useful to other PostGIS users, -you follow functions and variables naming and indentation conventions already in use in the files, -you document your function like the ones already provided, -you provide some tests in the postgis_addons_test.sql file, -you add the necessary DROP statements in the postgis_addons_uninstall.sql file. Pierre ___ postgis-users mailing list postgis-users@lists.osgeo.org http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
Re: [postgis-users] The first release of the PostGIS Add-ons is out!
Rémi, About license : if you use GPL function, your code becomes GPL, this might be a problem if using it inside company. If you use LGPL, you can do basically what you want. I think about going like Mateusz and Stephen suggested. What do you think? Using PostGIS everyday, I already find it hard to find the functions I need. I feel there is no point to provide additionnal functions if you have to know them to use them. Every function is preceded with a description of the parameters and a self-contained and a typical example. The question is: Should this documentation be: 1) embedded in the .sql file 2) in the readme 3) in the wiki? for now I thought that embedding it in the file, beside the code, with a quick list at the beginning like the one in the PostGIS doc, was the most simple way. Say I'm developping and I need a function, how would I know you have a function I might use, by searching trough all the functions name? You look in the quick list at the beginning. I understand your maintenance concern, yet it could be mandatory to document new function in markdown or in wiki when someone contribute, thus eanbling a google search. It could be. I tried to put as less barrier as possible to new contributors. About test : Your idea being more for users than regular developpers, how to ensure quality. There is a .sql test file to be executed manually. Please give it a try. I may be totally wrong, but I fear it will become like many open source graveyard of non-maintained poorly written functions (I include myself in people whose code have to be reviewed). I engage to be the guardian of quality for a while. Hopefully you're wrong and I suggest you be the first contributor... ;-) For myself I had most of those functions written since a while and they were spread in many files. I had to clean them so they are easier to find and install for my users. Pierre ___ postgis-users mailing list postgis-users@lists.osgeo.org http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
