Chicken domains revamp

[Mario Domenech Goulart]

Felix and chicken hackers

We've been discussing on IRC about restructuring the infrastructure so we can have a better organization for the project. One of the topics is the domain names related to chicken.

Currently we have too many domain names related to chicken: call-with-current-continuation.org, callcc.org, chicken.wiki.br, 3e8.org/chickadee, irp.oist.jp (trac) and some domains owned by elf which are not currently in use (chicken-scheme.{com,org} IIRC). I hopefully could remove all the traces of galinha.ucpel.tche.br from our wiki.

It's consensus that we need something simpler and clearer.

An initial proposal would be having a single domain name and subdomains to hold things like wiki, trac, chickadee and such things. We thought about asking Toby to give us the callcc.org domain, so we'd have:

• [www.]callcc.org: the main page for Chicken. Would be a splash page about the project, containing quick info about the project, like a a brief description, links to the wiki, bug tracking, chickadee, mailing lists and chicken tarballs and sources. www.call-with-current-continuation.org and chicken-scheme.{org,com} would redirect to it.

• wiki.callcc.org: would point to the wiki machine. chicken.wiki.br would point to wiki.callcc.org. Maybe chicken.wiki.br can be deprecated in the future.

• bugs.callcc.org: our bug tracking system. Would point to Ivan's machine.

• docsearch.callcc.org (or chickadee.callcc.org): would point to Jim's machine.

Open questions:

• Does this basic proposal sound ok?

• Should (can) we use callcc.org? It sounds good because it's a short form for call-with-current-continuation.org. Besides that, it's owned by Toby, which uses it for his doc search tool (which is outdated). Chickadee does what the current callcc.org search tool does. Another domain suggestion or B plan (in case we decide for callcc.org but Toby has other plans for it)? call.cc has been suggested too, but we'd have to buy it.

[Jim Ursetto]

call-cc.org was the other domain suggestion. We would have to buy this one. Although if we took over Toby's domain we probably have to buy that anyway.

All machines hanging off callcc.org should use relative URLs or take the Host: header into account -- in other words, act like virtual hosts.

We're not sure how this will work with SSL, although currently, everyone is using self-signed certs.

It is possible we could get a dedicated server to run one or more of these domains/pages. A VPS is not that expensive. But, if domains are set up in the manner suggested, that should be transparent to users.

It's also possible to use subdirectories instead of domains to distinguish among machines (callcc.org/chickadee, callcc.org/wiki). It requires proxying though and setup on the root webserver. Ultimately subdomains are easier and probably better.

[Jim Ursetto]

Oh. Domains are like $8/yr (call-cc.org is available from name.com for $7.49/yr) so I would suggest picking one we really like rather than settling.

[Mario Domenech Goulart]

Replying to zbigniew:

It is possible we could get a dedicated server to run one or more of these domains/pages. A VPS is not that expensive. But, if domains are set up in the manner suggested, that should be transparent to users.

Just to make clear: we do have a quite decent machine waiting for infrastructure software to be deployed. This machine will replace the current galinha. It's dedicated to chicken and available for whatever infrastructure software you need for chicken.

[Jim Ursetto]

I had no idea! That is great.

[felix winkelmann]

Mario, this sounds good. Don't forget git.callcc.org.

[Mario Domenech Goulart]

I've registered call-cc.org. So far we have call-cc.org and wiki.call-cc.org pointing to the same place (the new wiki machine).

[felix winkelmann]

This can be closed now, I think.

[Mario Domenech Goulart]

I'm closing this ticket, since we've migrated services to call-cc.org.