[postgis-users] The first release of the PostGIS Add-ons is out!

[Rémi Cura]

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.

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.
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?
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.


About test : Your idea being more for users than regular developpers, how
to ensure quality.
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).

Great idea anyway :-)

Cheers,

Rémi-C



2013/11/18 Pierre Racine <Pierre.Racine at sbf.ulaval.ca>

> 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 at lists.osgeo.org
> http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20131118/8bd747c0/attachment.html>