In 2003, I could already tell that storing data in the cloud was the future. We didn't know to call it the cloud at that time, but the concept of storing documents such that they were accessible via any browser was already appealing.
Google Docs didn't exist yet. But Wikipedia did, and the software used to run it is open source. I set up wiki.prestonhunt.com and used it as my own private document management system. It was pretty useful, both in terms of having a place to store non-private documents (such as book reviews), but also for collaboration with others (planning a trip, for example). And writing in the wiki markup language was a lot less cumbersome than HTML.
Today, almost seven years later, I'm retiring wiki.prestonhunt.com. Spammers are one of the reasons. Like most wikis, it's possible to undo any unauthorized changes, but it's a huge hassle. (I need to write an essay later on why using off-the-shelf software like WikiMedia counter-intuitively opens a system up to more security vulnerabilities than a home-grown solution).
I'm in the middle of re-architecting prestonhunt.com anyway, most likely moving to either Google App Engine or Django, hosted entirely on the cloud. It's a pretty painful process, going through the site's functionality component by component and evaluating whether the value of each given component justifies the cost of migrating it. In the case of running one's own wiki, I would say definitely not!