Menu
▾
▴
pyogclib-developers
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(27) |
Oct
(22) |
Nov
(1) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
|
From: Bernhard R. <ber...@in...> - 2007-12-11 09:12:04
|
On Sunday 09 December 2007 02:59, Bernhard Reiter wrote: > I have submitted a small patch for pyogclib > to add some error handling in case of url or connection problems. > (This bugged me playing around with the old thuban/Extension/wms which > uses pyogclib.) Sean informed me that pyogclib is abandoned. I suggest to state this on the webpage and point people to the active http://trac.gispython.org/projects/PCL/wiki/OwsLib Best, Bernhard =2D-=20 Managing Director - Owner: www.intevation.net (Free Software Company) Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com. Intevation GmbH, Osnabr=FCck, DE; Amtsgericht Osnabr=FCck, HRB 18998 Gesch=E4ftsf=FChrer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner |
|
From: Bernhard R. <ber...@in...> - 2007-12-09 01:59:23
|
Hi Sean, Hi Jean-Francois, a few minutes ago I have submitted a small patch for pyogclib to add some error handling in case of url or connection problems. (This bugged me playing around with the old thuban/Extension/wms which uses pyogclib.) http://sourceforge.net/tracker/index.php?func=3Ddetail&aid=3D1847088&group_= id=3D89925&atid=3D591903 Will someone apply it? If you like you can give my CVS write access and I might apply it myself. (my sf id is "ber".) Regards, Bernhard =2D-=20 Managing Director - Owner: www.intevation.net (Free Software Company) Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com. Intevation GmbH, Osnabr=FCck, DE; Amtsgericht Osnabr=FCck, HRB 18998 Gesch=E4ftsf=FChrer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner |
|
From: <ben...@id...> - 2004-05-25 07:58:05
|
Dear Open Source developer I am doing a research project on "Fun and Software Development" in which I kindly invite you to participate. You will find the online survey under http://fasd.ethz.ch/qsf/. The questionnaire consists of 53 questions and you will need about 15 minutes to complete it. With the FASD project (Fun and Software Development) we want to define the motivational significance of fun when software developers decide to engage in Open Source projects. What is special about our research project is that a similar survey is planned with software developers in commercial firms. This procedure allows the immediate comparison between the involved individuals and the conditions of production of these two development models. Thus we hope to obtain substantial new insights to the phenomenon of Open Source Development. With many thanks for your participation, Benno Luthiger PS: The results of the survey will be published under http://www.isu.unizh.ch/fuehrung/blprojects/FASD/. We have set up the mailing list fa...@we... for this study. Please see http://fasd.ethz.ch/qsf/mailinglist_en.html for registration to this mailing list. _______________________________________________________________________ Benno Luthiger Swiss Federal Institute of Technology Zurich 8092 Zurich Mail: benno.luthiger(at)id.ethz.ch _______________________________________________________________________ |
|
From: Jan-Oliver W. <ja...@in...> - 2003-11-12 08:41:16
|
Hi, [ this is posted to Thuban and pyogclib mailing lists ] I just checked a very coarse experimental proof-of-concept extension for WMS Layers into Thuban CVS :-) Those of you who know how to add extensions and feel adventerous may want to try it out. A default WMS server is offered pointing to Frida WMS (frida.intevation.org). So far, I found no other WMS server that works as well, but that is most likely due to the very coarse implementation of mine. You will need PyOGCLib 0.1.0 to run this, see the file Extensions/wms/wms.py for details. However, this demonstrates how you can add special layer types to Thuban as an Extension. All the best Jan -- Jan-Oliver Wagner http://intevation.de/~jan/ Intevation GmbH http://intevation.de/ FreeGIS http://freegis.org/ |
|
From: <Jea...@CC...> - 2003-10-29 15:03:44
|
Jan, First of all, thanks for adding this ti FreeGIS, might bring some publicity :) And I have to admit I don't think either of us really officially announced the first release ... I expected you would've seen the traffic about that on this list however? I know my plans for the next release are big enough that I'll probably try for a wider announcement of the next release ... Depends also on what Sean manages to do. As for the version, I agree completely, but like you pointed out, since the number of downloads is so low and nobody complained, I figured nobody would be the wiser if I just replaced it directly :) For sure when we get thousands of downloads I'll be more disciplined about this !! J.F. -----Original Message----- From: pyo...@li... [mailto:pyo...@li...]On Behalf Of Jan-Oliver Wagner Sent: Wednesday, October 29, 2003 5:46 AM To: pyo...@li... Subject: Re: [Pyogclib-developers] WFS/GML Updates, CVS Question Hi, On Fri, Oct 24, 2003 at 04:27:13PM -0400, Jea...@CC... wrote: > First of all just to let you know that I reuploaded the current 0.1.0 > release since apparently the Zope WFSAdapter stuff was missing. in principle it is not a good idea to publish different packages under the same version and filename. Now it may happen that people talk about version 1 and 2 of verion 0.1.0. Therefore, it would have been better to increase just the minor version number: 0.1.1. Of course, there have been not much downloads this time so far, but I made this comment for the future when there will be thousands of them right after new releases :-) Best Jan -- Jan-Oliver Wagner http://intevation.de/~jan/ Intevation GmbH http://intevation.de/ FreeGIS http://freegis.org/ ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Pyogclib-developers mailing list Pyo...@li... https://lists.sourceforge.net/lists/listinfo/pyogclib-developers |
|
From: Jan-Oliver W. <ja...@in...> - 2003-10-29 10:46:16
|
Hi, On Fri, Oct 24, 2003 at 04:27:13PM -0400, Jea...@CC... wrote: > First of all just to let you know that I reuploaded the current 0.1.0 > release since apparently the Zope WFSAdapter stuff was missing. in principle it is not a good idea to publish different packages under the same version and filename. Now it may happen that people talk about version 1 and 2 of verion 0.1.0. Therefore, it would have been better to increase just the minor version number: 0.1.1. Of course, there have been not much downloads this time so far, but I made this comment for the future when there will be thousands of them right after new releases :-) Best Jan -- Jan-Oliver Wagner http://intevation.de/~jan/ Intevation GmbH http://intevation.de/ FreeGIS http://freegis.org/ |
|
From: Jan-Oliver W. <ja...@in...> - 2003-10-25 10:24:53
|
Hi, I didn't notice, 0.1 is already released. The announcement was not send in cc to this list :-( However, I now added PyOGCLib to www.FreeGIS.org. How about maintaining a global ChangeLog now that the first release is out? I am having in mind the style that is used for many GNU software. Thuban uses the same format: http://www.intevation.de/cgi-bin/viewcvs-thuban.cgi/thuban/ChangeLog?rev=1.525&content-type=text/vnd.viewcvs-markup Furthermore, I am thinking of creating a Debian package for PyOGCLib. If not already someone else did? Best Jan -- Jan-Oliver Wagner http://intevation.de/~jan/ Intevation GmbH http://intevation.de/ FreeGIS http://freegis.org/ |
|
From: Sean G. <sgi...@fr...> - 2003-10-24 21:20:26
|
On Friday, October 24, 2003, at 02:27 PM,=20 Jea...@CC... wrote: > G'Day, > > First of all just to let you know that I reuploaded the current 0.1.0 > release since apparently the Zope WFSAdapter stuff was missing. This > apparently reset the download count though :( We were at whoping 6 ! = ;) > I left the dates and everything else the same, so it still looks like=20= > it > dates from october ... Nobody complained about the missing WFS Adapter=20= > , so > probably nobody cares (yet?). > > I've added the WFS Adapter to my Zope.org page, and wanted to fix this > before I submit a news item. > > I noticed some new forking and tags in the CVS ... whatch'a up to Sean=20= > ? > > The improvements to the GML module are progressing well. I've now=20 > finally > reached the point where I need to implement some tests, so I'm going = to > focus on that since I need them before work can keep progressing. > > How are things on the WMS front ? > > Cheers, > > Jean-Fran=E7ois Doyon > Internet Service Development and Systems Support > GeoAccess Division > Canadian Center for Remote Sensing > Natural Resources Canada > http://atlas.gc.ca > Phone: (613) 992-4902 > Fax: (613) 947-2410 > Hi J.F., I haven't been up to anything lately. The only tags I've done were for=20= the first release, shouldn't be any new branches unless I f'd something up. I haven't even been able to make the time for the #1 thing on my=20 PyOGCLib Todo list, which is to update ZMapServer to require PyOGCLib. Once I do this, the number of downloads should go up a bit. That is if I can ever make the time to add the new features to that software that will make folks want to upgrade. I had thought that the paying work I'm doing=20 might help the development of the WMS stuff in our package, but it turns out=20= that the WMS Client/Server model is not a great match for my client's=20 application. On another topic, what does the OGC have to say about geocoding? Would=20= this fall under WFS? Sean -- Sean Gillies sgillies at frii dot com http://www.frii.com/~sgillies= |
|
From: <Jea...@CC...> - 2003-10-24 20:28:34
|
G'Day, First of all just to let you know that I reuploaded the current 0.1.0 release since apparently the Zope WFSAdapter stuff was missing. This apparently reset the download count though :( We were at whoping 6 ! ;) I left the dates and everything else the same, so it still looks like = it dates from october ... Nobody complained about the missing WFS Adapter = , so probably nobody cares (yet?). I've added the WFS Adapter to my Zope.org page, and wanted to fix this before I submit a news item. I noticed some new forking and tags in the CVS ... whatch'a up to Sean = ? The improvements to the GML module are progressing well. I've now = finally reached the point where I need to implement some tests, so I'm going to focus on that since I need them before work can keep progressing. How are things on the WMS front ? Cheers, Jean-Fran=E7ois Doyon Internet Service Development and Systems Support GeoAccess Division Canadian Center for Remote Sensing Natural Resources Canada http://atlas.gc.ca Phone: (613) 992-4902 Fax: (613) 947-2410 |
|
From: Sean G. <sgi...@fr...> - 2003-10-11 01:05:25
|
Cool ideas, J.F., I'm going to re-read this tomorrow and try to post something constructive. You've seen the other psycopg geometry thing mentioned on the postgis-users list? cheers, Sean On Friday, October 10, 2003, at 04:57 PM,=20 Jea...@CC... wrote: > Gents, > > Alright, Sean's comments a while ago (About providing WFS Server > functionality in pyogclib) got me thinking about how one would go=20 > about this > .... > > I think I've got an idea down now that shoud work, and I need to put=20= > it down > before I forget it :) I'm also looking for comments of course! > > First of all, I need to support a wide range of datasources. I'm going=20= > to > start with PostGIS, though I hope to also use the python API to=20 > shapelib. > > The mental strugle I've been going through is how to handle the GML > reading/writing. I've decided that the GML module will be expanded to > handle WKT and/or WKB as input, as well as DOM nodes (Which it already > supports). This is very OGC'ish, and should provide a broad range of > support. This will allow the system to instanciate python geometry=20 > classes > from any data source that can be made to provide WKT/WKB. > > THEN, I will also add the functionality for each of the GML geometry=20= > classes > to be able to write themselves out as xml ( .toxml() ). > > And, finaly, I will have some sort of utility method that will wrap a=20= > python > DB 2.0 record and map it to a GML featureInstance, using the above > functionality. > > A side-effect of this work will be the inclusion in this project of=20 > some > code that will extend psycopg for support of the 'geometry' PostGIS > datatype. I've already done this successfully I'm glad to say! This=20 > will be > usable outside of PyOGCLib. > > Eventually I will have to abstract and separate all this functionality=20= > into > a sensible API architecture also of course, something I will keep in=20= > mind as > I go, and that will take form with time. I will be especially mindful=20= > of > the necessity to have the ability to write database drivers of some=20 > form in > order to support a wide range of underlying data sources. > > And finally (again), there's the configuration of things that aren't=20= > from > the datasource itself (server abstract and so on) ... This I wll=20 > probably > not touch and leave to implementers to handle, providing only utility > functions that would format/dump XML for them or something like that. =20= > There > would be no HTTP handling, GET/POST handling, or anything like that, = at > least not for now. > > Ideas, comments and constrcutive criticism welcome as always! > > Cheers, and have a good week-end ... > > Jean-Fran=E7ois Doyon > Internet Service Development and Systems Support > GeoAccess Division > Canadian Center for Remote Sensing > Natural Resources Canada > http://atlas.gc.ca > Phone: (613) 992-4902 > Fax: (613) 947-2410 > > > > ------------------------------------------------------- > This SF.net email is sponsored by: SF.net Giveback Program. > SourceForge.net hosts over 70,000 Open Source Projects. > See the people who have HELPED US provide better services: > Click here: http://sourceforge.net/supporters.php > _______________________________________________ > Pyogclib-developers mailing list > Pyo...@li... > https://lists.sourceforge.net/lists/listinfo/pyogclib-developers > |
|
From: <Jea...@CC...> - 2003-10-10 22:57:57
|
Gents, Alright, Sean's comments a while ago (About providing WFS Server functionality in pyogclib) got me thinking about how one would go about = this ... I think I've got an idea down now that shoud work, and I need to put it = down before I forget it :) I'm also looking for comments of course! First of all, I need to support a wide range of datasources. I'm going = to start with PostGIS, though I hope to also use the python API to = shapelib. The mental strugle I've been going through is how to handle the GML reading/writing. I've decided that the GML module will be expanded to handle WKT and/or WKB as input, as well as DOM nodes (Which it already supports). This is very OGC'ish, and should provide a broad range of support. This will allow the system to instanciate python geometry = classes from any data source that can be made to provide WKT/WKB. THEN, I will also add the functionality for each of the GML geometry = classes to be able to write themselves out as xml ( .toxml() ). And, finaly, I will have some sort of utility method that will wrap a = python DB 2.0 record and map it to a GML featureInstance, using the above functionality. A side-effect of this work will be the inclusion in this project of = some code that will extend psycopg for support of the 'geometry' PostGIS datatype. I've already done this successfully I'm glad to say! This = will be usable outside of PyOGCLib. Eventually I will have to abstract and separate all this functionality = into a sensible API architecture also of course, something I will keep in = mind as I go, and that will take form with time. I will be especially mindful = of the necessity to have the ability to write database drivers of some = form in order to support a wide range of underlying data sources. And finally (again), there's the configuration of things that aren't = from the datasource itself (server abstract and so on) ... This I wll = probably not touch and leave to implementers to handle, providing only utility functions that would format/dump XML for them or something like that. = There would be no HTTP handling, GET/POST handling, or anything like that, at least not for now. Ideas, comments and constrcutive criticism welcome as always! Cheers, and have a good week-end ... Jean-Fran=E7ois Doyon Internet Service Development and Systems Support GeoAccess Division Canadian Center for Remote Sensing Natural Resources Canada http://atlas.gc.ca Phone: (613) 992-4902 Fax: (613) 947-2410 |
|
From: Sean G. <sgi...@fr...> - 2003-10-06 21:23:52
|
I'm open to whatever release strategy works well with minimum fuss, so that I can spend time bringing the WMSClient up to the same level of completeness as WFSClient. Sean On Monday, October 6, 2003, at 11:27 AM, Jea...@cc... wrote: > Sean, > > OK, I've thrown in our first news item! > > As for the future, sure, I have no problem doing some of them. > > As for the script or list of files to include in a release, a good > idea, > just one concern: This assumes that we want to tag the latest version > ? What > if it's not the case? Maybe we should track the version of the file we > want > tagged also ? > > Have a file that lists the files/dirs we want released for that > specific > release. For example a file called "release-files-0_2_0.txt" that > contains: > > README.txt 1.3 > LICENCE.txt 1.4 > ogclib/__init__.py 1.3 > > etc ... ? > > A separate sed/awk/perl script can process them upon each release. > > Thoughts ? > J.F. > |
|
From: <Jea...@CC...> - 2003-10-06 17:28:08
|
Sean,
OK, I've thrown in our first news item!
As for the future, sure, I have no problem doing some of them.
As for the script or list of files to include in a release, a good idea,
just one concern: This assumes that we want to tag the latest version ? What
if it's not the case? Maybe we should track the version of the file we want
tagged also ?
Have a file that lists the files/dirs we want released for that specific
release. For example a file called "release-files-0_2_0.txt" that contains:
README.txt 1.3
LICENCE.txt 1.4
ogclib/__init__.py 1.3
etc ... ?
A separate sed/awk/perl script can process them upon each release.
Thoughts ?
J.F.
-----Original Message-----
From: Sean Gillies [mailto:sgi...@fr...]
Sent: Sunday, October 05, 2003 12:23 PM
To: Jea...@cc...
Cc: pyo...@li...
Subject: Re: PyOGCLib release candidate 1
J.F.,
I made the new release. Maybe you can do the next one? And would you
want to write the News item about the release? Maybe this would be a
good way to share the load: each release one of us makes the release
and one writes a news?
I wrote a sh script called tools/tagrel to help tag files for release.
We might in the future want to keep a text manifest of files for
release,
but for now they are just named in the script. The script takes a
single argument like '0-1-0' or '0-2' (maybe in the future we'd drop
the superfluous 0) and tags the files like
cvs tag rel-$1 ...
To make a release distribution, I did
cvs export -r rel-0-1-0 PyOGCLib
My mistake was 'checkout' rather than 'export' for RC1. Then tar and
gzip.
I'm not bothering with windows ZIP or Apple SIT files since in my
experience the common applications can handle tar.gz.
cheers,
Sean
On Saturday, October 4, 2003, at 06:15 PM,
Jea...@cc... wrote:
> Sean,
>
> Right on! Thanks for the work Sean :)
>
> A few little problems I noticed:
>
> - In the API docs the link for ogclib.GML.Coordinates is bad ... This
> is a
> new class, an edit I did earlier today ... probably will need to do a
> cvs
> add on it ... It replaces ogclib.GML.coordinates (lower "c").
>
> - The file PyOGCLib.txt isn't really necessary anymore as it's
> replaced by
> the README ... It can be removed from the CVS entirely I think.
>
> - The CVS subdirectory appears in the tarball ?? Did you do an export
> ? BTW,
> when it's longer an RC, maybe we should tag the tree for 0.1.0, and do
> a
> proper export without the CVS stuff ?
>
> If you want I can take care of it, I should maybe do my part ? :)
>
> Cheers,
> J.F.
>
> -----Original Message-----
> From: Sean Gillies
> To: pyo...@li...
> Cc: Jea...@cc...
> Sent: 04/10/2003 6:13 PM
> Subject: PyOGCLib release candidate 1
>
> All,
>
> I'm calling this RC 1, will replace it with pyogclib-0.1.0 first thing
> Monday AM unless we find any problems with it.
>
> Web page has also been updated:
>
> http://pyogclib.sourceforge.net
>
> Sean
>
|
|
From: Sean G. <sgi...@fr...> - 2003-10-05 16:22:37
|
J.F.,
I made the new release. Maybe you can do the next one? And would you
want to write the News item about the release? Maybe this would be a
good way to share the load: each release one of us makes the release
and one writes a news?
I wrote a sh script called tools/tagrel to help tag files for release.
We might in the future want to keep a text manifest of files for
release,
but for now they are just named in the script. The script takes a
single argument like '0-1-0' or '0-2' (maybe in the future we'd drop
the superfluous 0) and tags the files like
cvs tag rel-$1 ...
To make a release distribution, I did
cvs export -r rel-0-1-0 PyOGCLib
My mistake was 'checkout' rather than 'export' for RC1. Then tar and
gzip.
I'm not bothering with windows ZIP or Apple SIT files since in my
experience the common applications can handle tar.gz.
cheers,
Sean
On Saturday, October 4, 2003, at 06:15 PM,
Jea...@cc... wrote:
> Sean,
>
> Right on! Thanks for the work Sean :)
>
> A few little problems I noticed:
>
> - In the API docs the link for ogclib.GML.Coordinates is bad ... This
> is a
> new class, an edit I did earlier today ... probably will need to do a
> cvs
> add on it ... It replaces ogclib.GML.coordinates (lower "c").
>
> - The file PyOGCLib.txt isn't really necessary anymore as it's
> replaced by
> the README ... It can be removed from the CVS entirely I think.
>
> - The CVS subdirectory appears in the tarball ?? Did you do an export
> ? BTW,
> when it's longer an RC, maybe we should tag the tree for 0.1.0, and do
> a
> proper export without the CVS stuff ?
>
> If you want I can take care of it, I should maybe do my part ? :)
>
> Cheers,
> J.F.
>
> -----Original Message-----
> From: Sean Gillies
> To: pyo...@li...
> Cc: Jea...@cc...
> Sent: 04/10/2003 6:13 PM
> Subject: PyOGCLib release candidate 1
>
> All,
>
> I'm calling this RC 1, will replace it with pyogclib-0.1.0 first thing
> Monday AM unless we find any problems with it.
>
> Web page has also been updated:
>
> http://pyogclib.sourceforge.net
>
> Sean
>
|
|
From: <Jea...@CC...> - 2003-10-05 00:16:06
|
Sean, Right on! Thanks for the work Sean :) A few little problems I noticed: - In the API docs the link for ogclib.GML.Coordinates is bad ... This is a new class, an edit I did earlier today ... probably will need to do a cvs add on it ... It replaces ogclib.GML.coordinates (lower "c"). - The file PyOGCLib.txt isn't really necessary anymore as it's replaced by the README ... It can be removed from the CVS entirely I think. - The CVS subdirectory appears in the tarball ?? Did you do an export ? BTW, when it's longer an RC, maybe we should tag the tree for 0.1.0, and do a proper export without the CVS stuff ? If you want I can take care of it, I should maybe do my part ? :) Cheers, J.F. -----Original Message----- From: Sean Gillies To: pyo...@li... Cc: Jea...@cc... Sent: 04/10/2003 6:13 PM Subject: PyOGCLib release candidate 1 All, I'm calling this RC 1, will replace it with pyogclib-0.1.0 first thing Monday AM unless we find any problems with it. Web page has also been updated: http://pyogclib.sourceforge.net Sean |
|
From: Sean G. <sgi...@fr...> - 2003-10-04 22:13:11
|
All, I'm calling this RC 1, will replace it with pyogclib-0.1.0 first thing Monday AM unless we find any problems with it. Web page has also been updated: http://pyogclib.sourceforge.net Sean |
|
From: Sean G. <sgi...@fr...> - 2003-10-04 20:34:35
|
Alright, I'll run epydoc in a few minutes and upload the results. You've convinced me on the web site docs. I'll create a separate module called PyOGCLib-Htdocs and move the site files there. Sean On Friday, October 3, 2003, at 03:48 PM, Jea...@CC... wrote: > Sean, > > OK I've added and committed as many doctsrings as I'm going to for the > time > being, so you can run epydoc on the CVS contents and something much > better > should come out. > > Ah, a Mac user :) I didn't know OO 1.0 had DocBook support ... I > thought it > was new in 1.1 ... Can't speak as to how good or bad it is though, I > have it > at home, I'll give it a try! > > I 'm going to have to disgaree on the web site thing :) It's really > got > nothing to do with the code base people want, also it adds to the size > of > the download. And you never know, if this things starts getting a > following, the website could grow enough that it'll have a negative > impact > on the download ... It also may have contents you don't want just > anybody to > download as well. Better move it now than later ? > > Let me know how things go with the file release, or if you need any > help > with anything ! > > Have a good week-end, > J.F. > |
|
From: <Jea...@CC...> - 2003-10-04 19:59:01
|
Although for entirely different reasons, I agree with Sean, and am happy with the choice we've made license-wise. J.F. -----Original Message----- From: Sean Gillies To: Jan-Oliver Wagner Cc: pyo...@li... Sent: 04/10/2003 2:59 PM Subject: Re: [Pyogclib-developers] Releasing pyogclib On Thursday, October 2, 2003, at 09:37 AM, Jan-Oliver Wagner wrote: > On Thu, Oct 02, 2003 at 08:29:55AM -0600, Sean Gillies wrote: >> The WMSClient module is ready to go. Jan has said that he's already >> used it, and I'd like to release new versions of other software that >> would use the library. > > I'd appreciate an early release. > > BTW: Have you finally settled your mind regarding the license? > > Best > > Jan > Jan, sorry I overlooked this email! We'll stick with the current license. I'm sympathetic to the GPL and LGPL and it suits my _personal_ politics. I consider myself to be at least two standard deviations to the left of the US political center -- making me only marginally left in Europe, eh? :) However, I am stuck working in the US, and my clients are (presently) US companies. For the software that I am going to use in business, I think a less political license is best. I hope this choice won't prevent other developers from joining us. The Python programmer that J.F. and I are most interested on getting on board to start is Frank Warmerdam, and he seems to be pretty satisfied with the MIT-style license. cheers, Sean ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Pyogclib-developers mailing list Pyo...@li... https://lists.sourceforge.net/lists/listinfo/pyogclib-developers |
|
From: Sean G. <sgi...@fr...> - 2003-10-04 18:59:14
|
On Thursday, October 2, 2003, at 09:37 AM, Jan-Oliver Wagner wrote: > On Thu, Oct 02, 2003 at 08:29:55AM -0600, Sean Gillies wrote: >> The WMSClient module is ready to go. Jan has said that he's already >> used it, and I'd like to release new versions of other software that >> would use the library. > > I'd appreciate an early release. > > BTW: Have you finally settled your mind regarding the license? > > Best > > Jan > Jan, sorry I overlooked this email! We'll stick with the current license. I'm sympathetic to the GPL and LGPL and it suits my _personal_ politics. I consider myself to be at least two standard deviations to the left of the US political center -- making me only marginally left in Europe, eh? :) However, I am stuck working in the US, and my clients are (presently) US companies. For the software that I am going to use in business, I think a less political license is best. I hope this choice won't prevent other developers from joining us. The Python programmer that J.F. and I are most interested on getting on board to start is Frank Warmerdam, and he seems to be pretty satisfied with the MIT-style license. cheers, Sean |
|
From: <Jea...@CC...> - 2003-10-03 21:48:40
|
Sean, OK I've added and committed as many doctsrings as I'm going to for the time being, so you can run epydoc on the CVS contents and something much better should come out. Ah, a Mac user :) I didn't know OO 1.0 had DocBook support ... I thought it was new in 1.1 ... Can't speak as to how good or bad it is though, I have it at home, I'll give it a try! I 'm going to have to disgaree on the web site thing :) It's really got nothing to do with the code base people want, also it adds to the size of the download. And you never know, if this things starts getting a following, the website could grow enough that it'll have a negative impact on the download ... It also may have contents you don't want just anybody to download as well. Better move it now than later ? Let me know how things go with the file release, or if you need any help with anything ! Have a good week-end, J.F. -----Original Message----- From: Sean Gillies [mailto:sgi...@fr...] Sent: Thursday, October 02, 2003 5:27 PM To: Jea...@cc... Cc: pyo...@li... Subject: Re: [Pyogclib-developers] Releasing pyogclib Now that you mention it, the epydocs aren't so useful unless they are on a server, so let's not distribute them except through the website. And let's don't worry about nightly epydocs. IMO people who are using CVS can use pydoc to see the package/module/class structure of the library and can read the source directly. I've heard poor reviews of OpenOffice's DocBook support, maybe it's improved in 1.1? That'd be great. All it needs now is to run in Darwin without X :) I think it's OK for the web site to be in the CVS, we'll be sure to exclude it from the releases when we make the tarball. I will use the sourceforge file release and then for the next one, maybe we can get together on IRC and I can show you through it. Sean On Thursday, October 2, 2003, at 03:09 PM, Jea...@cc... wrote: > Sean, > > You mean in order to include epydoc in the release itself ? > > I don't know you have more experience with sourceforge than I do. I > know > they have a File Release process mechanism ... Is it worth using ? If > so, > I'd suggest we put the epydoc pages in the CVS and make it part of > what we > want released. Would it be possible to maintain epydoc's for each > release > versions in the CVS, both for the purposes of publishing to our > website AND > including in a file release ? that would be ideal, would it not ? > > The only problem would be generating epydocs for the CVS/Development > version. As you mentionned, SF doesn't have epydoc on their server. > We have > a few options ... I have reliable servers here at work. I could make a > job > that downloads the CVS version, generates the epydocs and posts it > back up, > say every night or something like that ... ? That way any user > interested in > the CVS version of the code would get API docs current to last night. > > As far as DocBook goes, I'm not really thinking about that just yet, > and > definitely not for this release. I'd like to get a decent README done > first > :) > I use DocBook straight from XML Spy on my workstation, and apparently > OpenOffice 1.1 can export docbook, so that might be fun to try out. > Thought > this means I don't realy on python or any server-side stuff to > generate my > docbook, or the HTML transformation results. > > On a side note, currently the www site is in the PyOGCLib cvs > directory, > which means that people that checkout the source get the website ... > Maybe > it should be moved into our CVSROOT to avoid this ? > > J.F. > > -----Original Message----- > From: Sean Gillies [mailto:sgi...@fr...] > Sent: Thursday, October 02, 2003 3:35 PM > To: Jea...@cc... > Cc: pyo...@li... > Subject: Re: [Pyogclib-developers] Releasing pyogclib > > > Monday sounds good to me. I'll move the web page and over the weekend > will > make a build script that will run epydoc and convert future DocBook > docs to > HTML. > > Since sourceforge hasn't epydoc, how about if I make the release > tarball on > my machine and then upload it to the sourceforge site? I've got the > tools > to process DocBook as well, using the Ft.Xml.Xlst module from 4thought. > > Sean > > On Thursday, October 2, 2003, at 09:41 AM, > Jea...@cc... wrote: > >> Sean, >> >> Agreed, we should release something, and 0.1 sounds like a good place >> to >> start :) ! >> >> I've started adding a variety of doc strings in my code, just haven't >> commited any of it yet, once that's done, I'll be ok with a first >> release. >> >> Hopefully that will happen before the end of the week. >> >> I'm already on a feature freeze for WFSClient anyways ... And I agree >> that >> for now the API docs should be ok. We should just adjust the website >> so >> that it work as expected (i.e. the home page is indeed the home page, >> instead of under foo/ ). >> >> How does next monday sound for a release ? that way if I can't find >> time to >> do it at work I'll have the week-end to catch up. >> >> J.F. >> >> -----Original Message----- >> From: Sean Gillies [mailto:sgi...@fr...] >> Sent: Thursday, October 02, 2003 10:30 AM >> To: pyo...@li... >> Subject: [Pyogclib-developers] Releasing pyogclib >> >> >> Let's make a first release of the library. >> >> The WMSClient module is ready to go. Jan has said that he's already >> used it, and I'd like to release new versions of other software that >> would use the library. >> >> The WMSServer module remains in a state that is really only useful >> with MapServer, but I think that we shouldn't let this hold up a >> release. If we call this 0.1, I think I'd rather wait till 0.2 to >> have a more generally useful WMSServer. My plan for that is to have >> a small set of classes that would allow a WMS Server to be easily >> constructed from something as basic as Python's cgi library + GDAL. >> This will take some time. >> >> J.F., I know that you wanted to write some user docs before a first >> release, but how about for now we focus on documentation in the code >> and keep the user docs very simple? I have picked up the DocBook >> distribution. Since you're using 4.1.2 with MapServer, would you >> prefer to stay with that? Any reason to go to 4.2? >> >> Can we set a date for a code freeze and then a date for release? >> >> Sean >> >> >> >> ------------------------------------------------------- >> This sf.net email is sponsored by:ThinkGeek >> Welcome to geek heaven. >> http://thinkgeek.com/sf >> _______________________________________________ >> Pyogclib-developers mailing list >> Pyo...@li... >> https://lists.sourceforge.net/lists/listinfo/pyogclib-developers >> > |
|
From: Sean G. <sgi...@fr...> - 2003-10-02 21:26:30
|
Now that you mention it, the epydocs aren't so useful unless they are on a server, so let's not distribute them except through the website. And let's don't worry about nightly epydocs. IMO people who are using CVS can use pydoc to see the package/module/class structure of the library and can read the source directly. I've heard poor reviews of OpenOffice's DocBook support, maybe it's improved in 1.1? That'd be great. All it needs now is to run in Darwin without X :) I think it's OK for the web site to be in the CVS, we'll be sure to exclude it from the releases when we make the tarball. I will use the sourceforge file release and then for the next one, maybe we can get together on IRC and I can show you through it. Sean On Thursday, October 2, 2003, at 03:09 PM, Jea...@cc... wrote: > Sean, > > You mean in order to include epydoc in the release itself ? > > I don't know you have more experience with sourceforge than I do. I > know > they have a File Release process mechanism ... Is it worth using ? If > so, > I'd suggest we put the epydoc pages in the CVS and make it part of > what we > want released. Would it be possible to maintain epydoc's for each > release > versions in the CVS, both for the purposes of publishing to our > website AND > including in a file release ? that would be ideal, would it not ? > > The only problem would be generating epydocs for the CVS/Development > version. As you mentionned, SF doesn't have epydoc on their server. > We have > a few options ... I have reliable servers here at work. I could make a > job > that downloads the CVS version, generates the epydocs and posts it > back up, > say every night or something like that ... ? That way any user > interested in > the CVS version of the code would get API docs current to last night. > > As far as DocBook goes, I'm not really thinking about that just yet, > and > definitely not for this release. I'd like to get a decent README done > first > :) > I use DocBook straight from XML Spy on my workstation, and apparently > OpenOffice 1.1 can export docbook, so that might be fun to try out. > Thought > this means I don't realy on python or any server-side stuff to > generate my > docbook, or the HTML transformation results. > > On a side note, currently the www site is in the PyOGCLib cvs > directory, > which means that people that checkout the source get the website ... > Maybe > it should be moved into our CVSROOT to avoid this ? > > J.F. > > -----Original Message----- > From: Sean Gillies [mailto:sgi...@fr...] > Sent: Thursday, October 02, 2003 3:35 PM > To: Jea...@cc... > Cc: pyo...@li... > Subject: Re: [Pyogclib-developers] Releasing pyogclib > > > Monday sounds good to me. I'll move the web page and over the weekend > will > make a build script that will run epydoc and convert future DocBook > docs to > HTML. > > Since sourceforge hasn't epydoc, how about if I make the release > tarball on > my machine and then upload it to the sourceforge site? I've got the > tools > to process DocBook as well, using the Ft.Xml.Xlst module from 4thought. > > Sean > > On Thursday, October 2, 2003, at 09:41 AM, > Jea...@cc... wrote: > >> Sean, >> >> Agreed, we should release something, and 0.1 sounds like a good place >> to >> start :) ! >> >> I've started adding a variety of doc strings in my code, just haven't >> commited any of it yet, once that's done, I'll be ok with a first >> release. >> >> Hopefully that will happen before the end of the week. >> >> I'm already on a feature freeze for WFSClient anyways ... And I agree >> that >> for now the API docs should be ok. We should just adjust the website >> so >> that it work as expected (i.e. the home page is indeed the home page, >> instead of under foo/ ). >> >> How does next monday sound for a release ? that way if I can't find >> time to >> do it at work I'll have the week-end to catch up. >> >> J.F. >> >> -----Original Message----- >> From: Sean Gillies [mailto:sgi...@fr...] >> Sent: Thursday, October 02, 2003 10:30 AM >> To: pyo...@li... >> Subject: [Pyogclib-developers] Releasing pyogclib >> >> >> Let's make a first release of the library. >> >> The WMSClient module is ready to go. Jan has said that he's already >> used it, and I'd like to release new versions of other software that >> would use the library. >> >> The WMSServer module remains in a state that is really only useful >> with MapServer, but I think that we shouldn't let this hold up a >> release. If we call this 0.1, I think I'd rather wait till 0.2 to >> have a more generally useful WMSServer. My plan for that is to have >> a small set of classes that would allow a WMS Server to be easily >> constructed from something as basic as Python's cgi library + GDAL. >> This will take some time. >> >> J.F., I know that you wanted to write some user docs before a first >> release, but how about for now we focus on documentation in the code >> and keep the user docs very simple? I have picked up the DocBook >> distribution. Since you're using 4.1.2 with MapServer, would you >> prefer to stay with that? Any reason to go to 4.2? >> >> Can we set a date for a code freeze and then a date for release? >> >> Sean >> >> >> >> ------------------------------------------------------- >> This sf.net email is sponsored by:ThinkGeek >> Welcome to geek heaven. >> http://thinkgeek.com/sf >> _______________________________________________ >> Pyogclib-developers mailing list >> Pyo...@li... >> https://lists.sourceforge.net/lists/listinfo/pyogclib-developers >> > |
|
From: <Jea...@CC...> - 2003-10-02 21:10:04
|
Sean, You mean in order to include epydoc in the release itself ? I don't know you have more experience with sourceforge than I do. I know they have a File Release process mechanism ... Is it worth using ? If so, I'd suggest we put the epydoc pages in the CVS and make it part of what we want released. Would it be possible to maintain epydoc's for each release versions in the CVS, both for the purposes of publishing to our website AND including in a file release ? that would be ideal, would it not ? The only problem would be generating epydocs for the CVS/Development version. As you mentionned, SF doesn't have epydoc on their server. We have a few options ... I have reliable servers here at work. I could make a job that downloads the CVS version, generates the epydocs and posts it back up, say every night or something like that ... ? That way any user interested in the CVS version of the code would get API docs current to last night. As far as DocBook goes, I'm not really thinking about that just yet, and definitely not for this release. I'd like to get a decent README done first :) I use DocBook straight from XML Spy on my workstation, and apparently OpenOffice 1.1 can export docbook, so that might be fun to try out. Thought this means I don't realy on python or any server-side stuff to generate my docbook, or the HTML transformation results. On a side note, currently the www site is in the PyOGCLib cvs directory, which means that people that checkout the source get the website ... Maybe it should be moved into our CVSROOT to avoid this ? J.F. -----Original Message----- From: Sean Gillies [mailto:sgi...@fr...] Sent: Thursday, October 02, 2003 3:35 PM To: Jea...@cc... Cc: pyo...@li... Subject: Re: [Pyogclib-developers] Releasing pyogclib Monday sounds good to me. I'll move the web page and over the weekend will make a build script that will run epydoc and convert future DocBook docs to HTML. Since sourceforge hasn't epydoc, how about if I make the release tarball on my machine and then upload it to the sourceforge site? I've got the tools to process DocBook as well, using the Ft.Xml.Xlst module from 4thought. Sean On Thursday, October 2, 2003, at 09:41 AM, Jea...@cc... wrote: > Sean, > > Agreed, we should release something, and 0.1 sounds like a good place > to > start :) ! > > I've started adding a variety of doc strings in my code, just haven't > commited any of it yet, once that's done, I'll be ok with a first > release. > > Hopefully that will happen before the end of the week. > > I'm already on a feature freeze for WFSClient anyways ... And I agree > that > for now the API docs should be ok. We should just adjust the website > so > that it work as expected (i.e. the home page is indeed the home page, > instead of under foo/ ). > > How does next monday sound for a release ? that way if I can't find > time to > do it at work I'll have the week-end to catch up. > > J.F. > > -----Original Message----- > From: Sean Gillies [mailto:sgi...@fr...] > Sent: Thursday, October 02, 2003 10:30 AM > To: pyo...@li... > Subject: [Pyogclib-developers] Releasing pyogclib > > > Let's make a first release of the library. > > The WMSClient module is ready to go. Jan has said that he's already > used it, and I'd like to release new versions of other software that > would use the library. > > The WMSServer module remains in a state that is really only useful > with MapServer, but I think that we shouldn't let this hold up a > release. If we call this 0.1, I think I'd rather wait till 0.2 to > have a more generally useful WMSServer. My plan for that is to have > a small set of classes that would allow a WMS Server to be easily > constructed from something as basic as Python's cgi library + GDAL. > This will take some time. > > J.F., I know that you wanted to write some user docs before a first > release, but how about for now we focus on documentation in the code > and keep the user docs very simple? I have picked up the DocBook > distribution. Since you're using 4.1.2 with MapServer, would you > prefer to stay with that? Any reason to go to 4.2? > > Can we set a date for a code freeze and then a date for release? > > Sean > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Pyogclib-developers mailing list > Pyo...@li... > https://lists.sourceforge.net/lists/listinfo/pyogclib-developers > |
|
From: Sean G. <sgi...@fr...> - 2003-10-02 19:34:13
|
Monday sounds good to me. I'll move the web page and over the weekend will make a build script that will run epydoc and convert future DocBook docs to HTML. Since sourceforge hasn't epydoc, how about if I make the release tarball on my machine and then upload it to the sourceforge site? I've got the tools to process DocBook as well, using the Ft.Xml.Xlst module from 4thought. Sean On Thursday, October 2, 2003, at 09:41 AM, Jea...@cc... wrote: > Sean, > > Agreed, we should release something, and 0.1 sounds like a good place > to > start :) ! > > I've started adding a variety of doc strings in my code, just haven't > commited any of it yet, once that's done, I'll be ok with a first > release. > > Hopefully that will happen before the end of the week. > > I'm already on a feature freeze for WFSClient anyways ... And I agree > that > for now the API docs should be ok. We should just adjust the website > so > that it work as expected (i.e. the home page is indeed the home page, > instead of under foo/ ). > > How does next monday sound for a release ? that way if I can't find > time to > do it at work I'll have the week-end to catch up. > > J.F. > > -----Original Message----- > From: Sean Gillies [mailto:sgi...@fr...] > Sent: Thursday, October 02, 2003 10:30 AM > To: pyo...@li... > Subject: [Pyogclib-developers] Releasing pyogclib > > > Let's make a first release of the library. > > The WMSClient module is ready to go. Jan has said that he's already > used it, and I'd like to release new versions of other software that > would use the library. > > The WMSServer module remains in a state that is really only useful > with MapServer, but I think that we shouldn't let this hold up a > release. If we call this 0.1, I think I'd rather wait till 0.2 to > have a more generally useful WMSServer. My plan for that is to have > a small set of classes that would allow a WMS Server to be easily > constructed from something as basic as Python's cgi library + GDAL. > This will take some time. > > J.F., I know that you wanted to write some user docs before a first > release, but how about for now we focus on documentation in the code > and keep the user docs very simple? I have picked up the DocBook > distribution. Since you're using 4.1.2 with MapServer, would you > prefer to stay with that? Any reason to go to 4.2? > > Can we set a date for a code freeze and then a date for release? > > Sean > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Pyogclib-developers mailing list > Pyo...@li... > https://lists.sourceforge.net/lists/listinfo/pyogclib-developers > |
|
From: <Jea...@CC...> - 2003-10-02 15:41:29
|
Sean, Agreed, we should release something, and 0.1 sounds like a good place to start :) ! I've started adding a variety of doc strings in my code, just haven't commited any of it yet, once that's done, I'll be ok with a first release. Hopefully that will happen before the end of the week. I'm already on a feature freeze for WFSClient anyways ... And I agree that for now the API docs should be ok. We should just adjust the website so that it work as expected (i.e. the home page is indeed the home page, instead of under foo/ ). How does next monday sound for a release ? that way if I can't find time to do it at work I'll have the week-end to catch up. J.F. -----Original Message----- From: Sean Gillies [mailto:sgi...@fr...] Sent: Thursday, October 02, 2003 10:30 AM To: pyo...@li... Subject: [Pyogclib-developers] Releasing pyogclib Let's make a first release of the library. The WMSClient module is ready to go. Jan has said that he's already used it, and I'd like to release new versions of other software that would use the library. The WMSServer module remains in a state that is really only useful with MapServer, but I think that we shouldn't let this hold up a release. If we call this 0.1, I think I'd rather wait till 0.2 to have a more generally useful WMSServer. My plan for that is to have a small set of classes that would allow a WMS Server to be easily constructed from something as basic as Python's cgi library + GDAL. This will take some time. J.F., I know that you wanted to write some user docs before a first release, but how about for now we focus on documentation in the code and keep the user docs very simple? I have picked up the DocBook distribution. Since you're using 4.1.2 with MapServer, would you prefer to stay with that? Any reason to go to 4.2? Can we set a date for a code freeze and then a date for release? Sean ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Pyogclib-developers mailing list Pyo...@li... https://lists.sourceforge.net/lists/listinfo/pyogclib-developers |
|
From: Jan-Oliver W. <ja...@in...> - 2003-10-02 15:37:13
|
On Thu, Oct 02, 2003 at 08:29:55AM -0600, Sean Gillies wrote: > The WMSClient module is ready to go. Jan has said that he's already > used it, and I'd like to release new versions of other software that > would use the library. I'd appreciate an early release. BTW: Have you finally settled your mind regarding the license? Best Jan -- Jan-Oliver Wagner http://intevation.de/~jan/ Intevation GmbH http://intevation.de/ FreeGIS http://freegis.org/ |
