The first release candidate of of Drupal 4.6 is available. You can already check out the soon-to-be-released new version of Drupal, but bear in mind that some bugs and issues will have to be resolved until the final release.
There will be some great new features and improvements, check out the ChangeLog.
Yes, 1984 seems a lot like a reality. Nowadays even your garbage cans spy on you.
Seems like I'm a bit fanatic about maps lately... Here's a world map of where the Debian developers live:
It's generated from anonymized location data of the developers using the xplanet package.
Joey Hess, a fellow Debian developer, keeps his life in subversion:
For the past five years, I've checked every file I've created and worked on, every email I've sent or received, and every config file I've tweaked into revision control.
He has done this for an even longer time using CVS (see his other article "CVS homedir") and explains the advantages of using SVN over CVS. He successfully converted his CVS repositories to SVN and they now amount to several gigabytes of content.
I'm quite impressed with this, and - having already used SVN for several code projects - decided to use it for my homedir now, too. Today, I checked in my .bashrc, .bash_logout, .bash_profile, .procmailrc, .muttrc, .slrnrc, .xsession, .vimrc, .signature and a few other files into SVN, more will follow later.
Also, quite important for me, my local .todo file (currently a 130 KB plain-text file with more or less important TODO items) is now in SVN. I imagine I'll have a lot of fun when I browse the history of my .todo file in a few years ;-)
One thing I already have in SVN for quite some time is my websites. Before uploading any file (via FTP, scp, whatever) I check it in on my local computer. As most of my sites are database-driven (using wikis or CMSes), I also periodically get the database dumps and check them into SVN.
This provides me with the additional benefit, that I can test any changes to my websites on my local computer, before they become public. If I mess up, I can always restart with a simple
rm -rf foo && svn up foo.
For the future I plan to also put my /etc directory as well as the /etc of my server(s) into version control.
I have just created a small checklist in my security section about how to secure an Apache webserver.
Note that this is work in progress and will be improved as my time permits. Any comments or suggestions are highly welcome, though.