Thanks Sean. FYI I have put back the ISO examples (r1708) in relative path. What's the updates setting(s) / cron frequency for the docs?
..Tom > -----Original Message----- > From: Sean Gillies [mailto:[email protected]] > Sent: Saturday, 05 February 2011 23:40 > To: Kralidis,Tom [Ontario] > Cc: gispython.org community projects > Subject: Re: [Community] OWSLib proposal: sphinx documentation > > Hi Tom, > > Here's the trunk docs: http://gispython.org/owslib/docs/en/trunk/. > > I had to comment out the sidebar line in conf.py and comment > out the included iso tests in index.rst to get it to build. > Docutils 0.7 and Sphinx 1.0.7 here. See r1707. > > Looks good. > > On Fri, Feb 4, 2011 at 7:15 AM, Kralidis,Tom [Ontario] > <[email protected]> wrote: > > > > Sean: any update on this one? FYI this has been ticketed > at http://trac.gispython.org/lab/ticket/241. Let me know if > you need any help. > > > > ..Tom > > > > > >> -----Original Message----- > >> From: [email protected] > >> [mailto:[email protected]] On Behalf Of Sean > >> Gillies > >> Sent: Monday, 25 October 2010 12:48 > >> To: gispython.org community projects > >> Subject: Re: [Community] OWSLib proposal: sphinx documentation > >> > >> Tom, > >> > >> I'll be happy to write and manage the cron scripts. My preference > >> would be for minimal Sphinx, not too many add-ons. > >> > >> On Sun, Oct 24, 2010 at 5:57 PM, Kralidis,Tom [Ontario] > >> <[email protected]> wrote: > >> > > >> > All: I have been working on developing sphinx [1] docs for > >> OWSLib documentation. > >> > > >> > Initial efforts have been based on what's on > >> > http://trac.gispython.org/lab/wiki/OwsLib, as well as my > >> own documentation notes for CSW. > >> > > >> > I propose we add these to svn trunk, under a 'docs/' dir. Notes: > >> > > >> > - I used the MapServer approach to outputting multilingual > >> > documentation (you can see in docs/Makefile) > >> > - output documentation online would be at > >> http://gispython.org/owslib/docs/index.html with listing > of versions > >> per release tag, i.e.: > >> > - http://gispython.org/owslib/docs/en/0.3.1/ > >> > - http://gispython.org/owslib/docs/en/x.y.z/ > >> > - svn trunk documentation would be at > >> http://gispython.org/owslib/docs/en/trunk/, and updated > via cron job, > >> which would be: > >> > - cd owslib/trunk/docs/ && make html > >> > - cp -rp build/html/en/ <gispython.org/owslib/docs/en/trunk/> > >> > > >> > Way forward: > >> > - upon consensus, I will svn add to trunk > >> > - create http://gispython.org/owslib/docs/en/0.3.1 and > >> > http://gispython.org/owslib/docs/en/trunk/ > >> > - setup cron script to output (say hourly?) to > >> > http://gispython.org/owslib/docs/en/trunk/ > >> > > >> > I offer to help out any way I can. > >> > > >> > Thoughts? I think sphinx is a simple and powerful way to > >> develop and maintain documentation to output to many formats. > >> > > >> > ..Tom > >> > > >> > [1] http://sphinx.pocoo.org/ > >> _______________________________________________ > >> Community mailing list > >> [email protected] > >> http://lists.gispython.org/mailman/listinfo/community > >> > > > > > > -- > Sean > _______________________________________________ Community mailing list [email protected] http://lists.gispython.org/mailman/listinfo/community
