#39: Spell checker
------------------------+---------------------------------------------------
Reporter: dom | Owner: dom
Type: enhancement | Status: new
Priority: normal | Component: openguides
Version: | Severity: normal
Keywords: |
------------------------+---------------------------------------------------
From http://oxford.openguides.org/wiki/?Comments:
James: My spelling is bad I know. Is it possible to add some sort of spell
check? Even if it's just a list of mispelled words so I can go back and
re-edit the entry?
* Not my itch; patches welcome :) --Kake
--
Ticket URL: <http://dev.openguides.org/ticket/39>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#56: Config options for license data
------------------------+---------------------------------------------------
Reporter: earle | Owner: dom
Type: enhancement | Status: new
Priority: normal | Component: openguides
Version: 0.51 | Severity: normal
Keywords: config |
------------------------+---------------------------------------------------
We should have config options called licence_url and licence_info_url. The
former would be used to link to the canonical page about a licence (e.g.
something on creativecommons.org); the latter a local page about the
licecse (like "Site Licence" on London).
--
Ticket URL: <http://dev.openguides.org/ticket/56>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#54: RSS redirect breaks username= parameter
-------------------+--------------------------------------------------------
Reporter: dom | Owner: dom
Type: defect | Status: new
Priority: normal | Component: openguides
Version: | Severity: normal
Keywords: |
-------------------+--------------------------------------------------------
action=rss;username=Foo should redirect to
action=rc;format=rss;username=Foo
but it redirects to action=rc;format=rss.
--
Ticket URL: <http://dev.openguides.org/ticket/54>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#42: "About" output
------------------------+---------------------------------------------------
Reporter: earle | Owner: earle
Type: enhancement | Status: new
Priority: low | Component: openguides
Version: | Severity: minor
Keywords: rdf |
------------------------+---------------------------------------------------
There should be an "action=about" method in wiki.cgi that produces an
"About this guide" page, with information about the OpenGuides install
(version number, logo, link to website, etc). I figure a link to this
could replace the standard OpenGuides link at the bottom of every page.
There should also be a link on that page to "action=about;format=rdf"
which would produce [http://usefulinc.com/doap/ DOAP] output about the
software.
--
Ticket URL: <http://dev.openguides.org/ticket/42>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#46: Google maps integration
------------------------+---------------------------------------------------
Reporter: dom | Owner: dom
Type: enhancement | Status: new
Priority: normal | Component: openguides
Version: | Severity: normal
Keywords: |
------------------------+---------------------------------------------------
Google maps as an index type, on nodes and search results would be cool.
Like http://boston.openguides.org/ has, in fact.
--
Ticket URL: <http://dev.openguides.org/ticket/46>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#52: "Locales" to be renamed "Areas"
--------------------------------+-------------------------------------------
Reporter: earle | Owner: dom
Type: enhancement | Status: new
Priority: normal | Component: openguides
Version: 0.51 | Severity: normal
Keywords: templates internals |
--------------------------------+-------------------------------------------
As discussed on IRC on Nov 28, the name "Locales" should be replaced - at
least in the user view, internally is not that important* - with "Areas".
* Or is it? Am I being lazy here? Maybe changing the name internally is a
good idea to avoid future confusion, bit rot, etc.
--
Ticket URL: <http://dev.openguides.org/ticket/52>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#36: Separate out installation of the OpenGuides software from installing a
guide
------------------------+---------------------------------------------------
Reporter: ivorw | Owner:
Type: enhancement | Status: new
Priority: normal | Version: 0.51
Severity: normal | Keywords:
------------------------+---------------------------------------------------
Currently, the install of [http://search.cpan.org/~dom/OpenGuides/
OpenGuides] is tricky, and doesn't allow a great deal of flexibility:
* Running more than one guide on the same host
* Upgrading the software
It is proposed that the install process be split into two distinct steps:
./Build install # install the software, run as root
./Build guide # Ask all the config questions about setting up a guide
# Set up the wiki.conf, CGI and database tables, run as www-data
Thus a CPAN(PLUS) or Debian apt-get install will only install the
software, and not any guides.
This exact mechanism can be used for software upgrades with the minimum of
human effort.
As a side effect, the test suite will need revising, as the answers to the
config questions about databases will not be known at this point.
Currently, the test suite is run against all the supported database
drivers found (MySQL, pg, SQLite). These are destructive tests that are
run against the databases concerned, and could have a devastating effect
if run against the real production database.
I propose that instead, there are two options for running the test suite,
either minimally via an SQLite throwaway database (the default), or
running the tests against the full range of databases on the target
machine - a full test. To do this will involve another new build target:
./Build testconfig # probe system for database drivers, and get
authentification info
Once testconfig has been run, the test suite will run against all test
databases, and the schemae and test data will be torn down on completion,
and also at the beginning if the databases appear non-empty.
A full test with testconfig against all database platforms is recommended
before shipping releases.
Note, this change will also insist on making DBD::SQLite a prerequisite
module.
--
Ticket URL: <http://dev.openguides.org/ticket/36>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#58: OpenGuides RSS Spits out link to RSS feed as <link>
-------------------------------+--------------------------------------------
Reporter: ChristopherSchmidt | Owner: dom
Type: defect | Status: new
Priority: normal | Component: openguides
Version: | Severity: normal
Keywords: |
-------------------------------+--------------------------------------------
<link> field for the <channel> element should be a link to the guide URL,
not the RSS feed.
--
Ticket URL: <http://dev.openguides.org/ticket/58>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#50: rdf output - minor nitpicking
------------------------+---------------------------------------------------
Reporter: maks | Owner: dom
Type: enhancement | Status: new
Priority: low | Component: openguides
Version: 0.50 | Severity: minor
Keywords: rdf |
------------------------+---------------------------------------------------
a friend of mine looked at the rdf output of london.o.o and vienna.o.o, he
found 2 minor issues:
A) <rdf:Description rdf:about="">
the about should contain a link to the doc itself
as the link will not change or should not change.
(Remark on irc: <@hex> BTW, as far as I know rdf:about="" is equivalent to
rdf:about="URI-of-this-document", that's certainly how the RDF validator
seems to interpret it.)
B) the other issue concerns <dc:contributor>Anonymous</dc:contributor>
it should be:
<dc:contributor><foaf:nick>Anonymous</foaf:nick></dc:contributor>
see -> http://xmlns.com/foaf/0.1/
you can of course choose another FOAF Basics.
--
Ticket URL: <http://dev.openguides.org/ticket/50>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project