On 29/07/2013 8:25 AM, Hamish wrote:
Cameron:
I'm erring toward putting into the "Contents" page (which is of
less prominence than having its own tab). Any comments?
I agree.
a couple questions-
- how to note when we know it's wrong? (e.g. opencpn didn't abruptly die it
just moved to git and ohloh doesn't know about that yet)
There is quite a bit of work maintaining a list of statements noting
deficiencies or conclusions about the metrics. These statements will
likely need to be updated with each release as people change version
control repositories or processes.
Instead, I've left in a general "buyer beware" statement at the top:
/Note these metrics have know deficiencies (such as caused by
repositories moving), and only provide partial indications about the
project's status./
- how to detect if offline and/or javascript is disabled, and print a message
saying that instead of just a blank page?
I've added a statement noting that a connection to the internet is required.
I'm inclined to avoid a statement about javascript. A large proportion
of web pages these days require javascript. I expect most people have
browsers which support javascript. If they don't, they would already
know that many web pages are not working for them, and probably have
worked out they need to turn on javascript.
Also, a statement about requiring javascript will likely confuse some
non-technical readers of this page, who might not understand what
"require javascript" means.
I suggest: "Keep the description simple"
--
Cameron Shorter
Software and Data Solutions Manager
Tel: +61 (0)2 8570 5050
Mob: +61 (0)419 142 254
Think Globally, Fix Locally
Geospatial & Data Solutions enhanced with Open Standards and Open Source
http://www.lisasoft.com
_______________________________________________
Live-demo mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/live-demo
http://live.osgeo.org
http://wiki.osgeo.org/wiki/Live_GIS_Disc
