#8: Pluggable authentication
-------------------------+--------------------------------------------------
Reporter: dom | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: openguides | Version:
Severity: normal | Resolution:
Keywords: |
-------------------------+--------------------------------------------------
Changes (by dom):
* summary: Basic auth integration => Pluggable authentication
Comment:
We probably will want to support at least basic auth and OpenID.
--
Ticket URL: <http://dev.openguides.org/ticket/8>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#59: Design improvements
------------------------+---------------------------------------------------
Reporter: dom | Owner: dom
Type: enhancement | Status: new
Priority: normal | Component: oxford.openguides.org
Version: | Severity: normal
Keywords: |
------------------------+---------------------------------------------------
Get a classic dreaming spires photo up as a banner with some nice title
text. I have a suitable photo. Will require hacking CSS/templates too.
--
Ticket URL: <http://dev.openguides.org/ticket/59>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#57: Dependencies for tickets
------------------------+---------------------------------------------------
Reporter: earle | Owner: dom
Type: enhancement | Status: new
Priority: normal | Component: trac
Version: | Severity: normal
Keywords: tickets |
------------------------+---------------------------------------------------
Since Trac doesn't seem to have a concept of tickets relying on each
other, could we have a custom text field (see TracTicketsCustomFields) on
tickets to enter the numbers of other tickets that need to be fixed first?
--
Ticket URL: <http://dev.openguides.org/ticket/57>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#49: Remove obsolete metadata item "Map Link"
------------------------+---------------------------------------------------
Reporter: ivorw | Owner: dom
Type: enhancement | Status: new
Priority: normal | Component: openguides
Version: | Severity: normal
Keywords: |
------------------------+---------------------------------------------------
The "Map Link" field was originally put in as part of the migration from
UseModWiki for GrubStreet. This was before the geo coordinates were
abstracted out as separate metadata.
As it is, "Map Link" usually does not convey any useful information which
does not appear elsewhere in the metadata, and is not present in the RDF,
hence cannot be mirrored. The exception to this might be sites that have
their own custom "how to get there" page, but these are few and far
between, and of limited use.
Each site can generate its own map links by processing the lat/long,
OS_X/OS_Y or postcode, into a URL to an external mapping site. We can do
much better than this, as is apparent on [http://boston.openguides.org].
This could easily be turned into a plugin, or probably just as easily be
done in template logic.
--
Ticket URL: <http://dev.openguides.org/ticket/49>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#43: Show priority in tickets-ordered-by-last-change report
-------------------+--------------------------------------------------------
Reporter: earle | Owner: dom
Type: task | Status: new
Priority: normal | Component: trac
Version: | Severity: normal
Keywords: |
-------------------+--------------------------------------------------------
It would be nice if [http://dev.openguides.org/report/9 this report] could
have a "priority" column.
--
Ticket URL: <http://dev.openguides.org/ticket/43>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#38: Link styles are ugly
-------------------+--------------------------------------------------------
Reporter: dom | Owner: dom
Type: defect | Status: new
Priority: normal | Component: openguides
Version: | Severity: normal
Keywords: |
-------------------+--------------------------------------------------------
From http://oxford.openguides.org/wiki/?Comments:
Square brackets around links to external pages look ugly. Is there any
chance of preventing them from being displayed? -- James
* Not that I know of. I actually disagree in any case; it's a useful way
of distinguishing between internal and external links, so I'd rather the
convention was kept. --Dom
* Couldn't that be done within the stylesheet? --James
* Stylesheet sounds like the best plan. I'll look into it unless someone
else does first. --Kake
--
Ticket URL: <http://dev.openguides.org/ticket/38>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project
#37: No CSS file in distribution
-------------------+--------------------------------------------------------
Reporter: dom | Owner:
Type: defect | Status: new
Priority: normal | Version:
Severity: normal | Keywords:
-------------------+--------------------------------------------------------
We really need a decent neat, not too flashy stylesheet to distribute so
that the default install isn't so fugly. The specification for the CSS
classes and ids is source:trunk/README.CSS.
--
Ticket URL: <http://dev.openguides.org/ticket/37>
OpenGuides <http://openguides.org/>
The OpenGuides city guides project