#230: Clarify the ellipsoid used when presenting latitude/longitude to the user
in HTML
------------------------+---------------------------------------------------
Reporter: dom | Owner: Nobody
Type: defect | Status: new
Priority: normal | Milestone:
Component: openguides | Version: svn
Severity: normal | Keywords:
------------------------+---------------------------------------------------
Most of the places we present lat/long (RDF, google maps) have a well
specified WGS84 ellipsoid. However, the ellipsoid used is undefined when
displaying on the node page.
Some people will assume that it's WGS84 and be confused when it's not.
However it would be inappropriate to change the display format
unilaterally to wgs84 without making it clear to the user.
A compromise should be reached where we tell the user the format the data
is in.
--
Ticket URL: <http://dev.openguides.org/ticket/230>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#241: postgres isnt a good default
------------------------+---------------------------------------------------
Reporter: bob | Owner: Nobody
Type: defect | Status: new
Priority: normal | Milestone:
Component: openguides | Version: svn
Severity: normal | Keywords:
------------------------+---------------------------------------------------
i dont think postgres should be the default database if you dont answer
any questions. If it is it should at least fill in defaults for dbuser
and dbname
I think we should go with sqlite as a default
No existing configuration file found; assuming this is a new install.
See the message above if this isn't correct.
Skip OpenGuides configuration? [n] y
===========================================================================
Skipping OpenGuides configuration - any configuration options previously
saved will be used instead. You may tweak your configuration now by
editing the 'wiki.conf' file produced by this script.
===========================================================================
DBD::Pg is needed to run a postgres database at Build.PL line 86, <STDIN>
line 2.
--
Ticket URL: <http://dev.openguides.org/ticket/241>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#36: Separate out installation of the OpenGuides software from installing a
guide
-------------------------+--------------------------------------------------
Reporter: ivorw | Owner: Nobody
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: openguides | Version: 0.51
Severity: normal | Resolution:
Keywords: |
-------------------------+--------------------------------------------------
Comment (by bob):
All Build.Pl should say is that the user needs to run a separate script to
create a guide.
This will help with automatic testing.
the script that should probably ask the same questions as build.pl does
currently.
or take cli options.
It should also probably create the database.
I think all tests just use sqlite now in a local db this negates some of
the concerns above. these days openguides mostly relies on wiki::toolkit
to have tested your db connectivity .
--
Ticket URL: <http://dev.openguides.org/ticket/36#comment:8>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#36: Separate out installation of the OpenGuides software from installing a
guide
-------------------------+--------------------------------------------------
Reporter: ivorw | Owner: Nobody
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: openguides | Version: 0.51
Severity: normal | Resolution:
Keywords: |
-------------------------+--------------------------------------------------
Comment (by perigrin):
Having talked about this (again) with Bob and Earl on IRC. I'd like to
have a completely seperate create-openguide script or some such that
Build.pl could just call when it was done installing stuff. (I don't know
the intricacies of Build.pl but I do think I could figure it out using
Module::Install if you'd be willing to accept a patch large enough to
include changing the Build process).
This would as an added benefit leave a script lying about for those of us
who host multiple guides so that we could just run create-openguide to
build new guide installs.
--
Ticket URL: <http://dev.openguides.org/ticket/36#comment:7>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project