Drupal Association members fund grants that make connections all over the world.
I've become interested in getting a number of Drupalcamp sites archived, in the UK we've had a lot of Drupacamps in the past year, and we're loosing valuable information because the sites are just 'disappearing'.
From reading around, I can see that a number of sites have been archived on the Drupal.org infrastructure, and are available at *.camps.drupal.org for example, this is discussed here:.
I'd like to help get sites archived and document the process, beyond the existing documentation here: http://drupal.org/node/27882
Inthere seems to be some discussion about domain names, specifically which one to use, in summary I think that:
- Having*.drupalcamp(s).org would be preferred and actually people could host the original site at this domain, and then cut over to a static version of the site after the camp without having to change the domain name.
Those domains are being squatted by people unwilling to give them to the Drupal community, at least this is the impression that I get from reading the issues about archiving sites. The drupalcamp.org domain has now been given to the Drupal community!
- As a fallback for now, the *.camps.drupal.org domains are being used, with the actual sites hosted on the Drupal.org infrastructure.
When reading all this and working out what was going on and what had been done, I did a couple of searches for domain names, drupalcamparchive.org turned out to be available, so I bought it. I'd like to make it clear that I'm super happy to transfer this domain to whomever within the Drupal project/association if its wanted.
So my main proposal has two main points:
- Use the drupalcamp.org domain to serve static copies of the Drupalcamp sites, and have a nice directory of the sites archived at the top level domain.
- Move the hosting off of the Drupal.org servers, to github.
I see the primary advantage of point 1 being security. If these sites are on the same domain as drupal.org, then obviously they will have access to the cookies, and so any code deployed to the static sites must be reviewed for security issues throughly. If they are being run from a different domain, then they won't have to be reviewed so thoroughly. I'm really happy to be told: "No, we're keeping them on camps.drupal.org" though.
My second proposal, would be to move the actual hosting of the static sites to use github pages. Now, I know that hosting static websites is significantly easier than maintaining the infrastructure for drupal.org itself, but it seems that if we can offload the sysadmin for these sites entirely, then we should do so.
Each site would be contained in it's own github repo owned by a 'drupal-static' organisation, this would make it incredibly easy for people to set up new sites. And we can easily have multiple administrators for setting up the sites.
If we get this right, then we should be expecting a lot of requests to archive static sites, and so I'd be interested in making this as simple as possible for people involved.
Please be kind and gentle with your feedback, if we're totally happy with the current setup, then I'd just like to document all of that.