On Thu, Dec 01, 2005 at 06:33:37PM +0000, Dominic Hargreaves wrote:
So I think we should move to a simple two level
system.
[Examples nusked]
Whether we want to enforce existing guides to switch over I don't know,
but we should at least put in redirects.
I'm wary of the URLs becoming too Byzantine when we start having to add in
extra layers to cope with regions, states and so on. I'd like to suggest
giving "naming precedence" to the largest city in a pair of cities with the
same name, for example:
-
london.openguides.org vs.
london-ontario.openguides.org
-
manchester.openguides.org vs
manchester-newhampshire.openguides.org
-
paris.openguides.org vs.
paris-texas.openguides.org
If there's not much to differentiate two cities (Smallville, PA vs
Smallville, AZ), then they should both have the state in their name
(
smallville-pennsylvania.openguides.org and
smallville-arizona.openguides.org, in this case).
It would be courteous for the larger guide of such a pair to offer a
prominent link to the smaller on its home page.
Currently
openguides.org is associated with
Earle's personal account
with
gandi.net. I suggest that we get an Openguides-specific account
with someone (them, or Black Cat Networks - my employer, I know we can
do this, for example). That would give us a web-based update interface
to which nominated individuals could have access.
I'm 100% for this. There shouldn't be an SPOF for our DNS (that is to say,
me!).
We then have a wiki page that documents the DNS
entries, who requested
them, when they were added, who by, etc etc, to keep track of things.
It's not a technically neat solution but is very easy to implement
WFM.
Cheers,
Earle.
--
Earle Martin
http://downlode.org/
http://purl.oclc.org/net/earlemartin/