Skip to main content

The State of Plan 28

Yesterday, many readers will have received an email from PledgeBank informing them that the Plan 28 pledge drive had failed. In a narrow technical sense that's correct: I had hoped to get 10,000 people to pledge to donate $10/£10/€10 towards building Babbage's Analytical Engine. In the end 3,996 people from around the world pledged.

Thank you to everyone who expressed this interest in the project. Because of you the project is not going away.

Here's the current state of things:

1. I am in the process of setting up the charitable organization that will manage Plan 28. As I mentioned before I've joined forces with Doron Swade on this and we are actively working to get the project running. Tomorrow I am meeting with specialist lawyers who will handle the charity registration.

2. We are in active talks with the Science Museum about their participation in the project (we hope to build the Analytical Engine at the Science Museum). This has take much longer than anticipated because the Science Museum is a very large organization whose management hierarchy must be navigated. There is great enthusiasm about the project at the Science Museum and they have been very helpful in providing access to Babbage's machines. I hope to announce the final details of our cooperation with the Science Museum in the next couple of weeks.

3. Doron and I are also in active talks with the Computer Conservation Society about their participation in the project. They have done wonderful work on many other historic computer reconstructions (and are just starting on EDSAC). We expect to be able to talk about that in detail in early March.

4. I continue to receive offers in kind of help on the project and I am very grateful for these and we will, undoubtedly, be taking many of them up when the time comes.

5. Another round of publicity will be coming shortly. In this Thursday's Times there's the Eureka science supplement which contains a special feature on the Analytical Engine and Plan 28. And a couple of weeks back I was being photographed for a feature in Wired Magazine. This will be in an issue sometime in the next couple of months.

I know that many people would like to give me money right now. I've been holding off for two reasons: firstly, if I start accepting your money without a proper legal organization I'll find myself in tax hell (the tax people might think the donations are my personal income, and you won't be able to get any tax deduction, and Plan 28 won't be able to apply for Gift Aid).

Secondly, once I can announce that the first part of the project is going to happen (digitization of the entire Babbage archive) the money will actually be needed. I hope to be asking people to donate sometime in the next few weeks.

I realize also that many people are frustrated that project isn't already off and running. Unfortunately, there is a lot of ground work (such as setting up ties with various organizations, finalizing the plan of action, and mundane things like bank accounts) to ensure that Plan 28 has a really solid footing.

Nevertheless, we still hope to have the Analytical Engine complete by 2021. Thank you for your continued support.

PS I have created a mailing list so that people can get email updates on the project. Just send a mail to [email protected] to join.

Comments

bigshotprof said…
I'm in for the long haul!
Unknown said…
I thought that ACM (http://www.acm.org/) would be interested in the project. It's right up their alley.
Alan Taylor said…
Same!
Kip Kitto said…
I hope BBC's Horizon is making a documentary!
Unknown said…
I'm still in.
Jim said…
Get the charity set up ASAP; I want to throw money at this project.
Kompani said…
I'm still in.
Kompani said…
I am still with the project.
Unknown said…
I'll still donate, let us know when we can!
Nathan Zeldes said…
Babbage had the patience and perseverance... so do we. Just keep going! The pledge holds!
Unknown said…
Thanks for updates - your current work although mundane is essential - KBO!
dpeters11 said…
Building one of these things isn't like slapping a few parts together. We knew it would be a long process. We're here for the long haul.
HonkingWalrus said…
I'm in for the long haul too. Keep trying
koskol said…
I'm in for the long haul as well. Don't give up.
Simon said…
Please post a link to subscribe to your mailing list. In your mail via PledgeBank you asked supporters to subscribe to the 'plan28mailinglist' but how do I do that?

Simon
pilkster said…
This is going to be a long ride I guess, looking forward to it. Keep up the good work :)
zyphlar said…
Keep in mind the vast, worldwide community of do-ers: Hackerspaces, connected via publications like Make Magazine. You're not solving these problems alone :)
Unknown said…
I'll happily increase my donation in the hope you can still reach the original goal.
RICHARD said…
Many people say "Why?" I say "Why not?" Go for it!
Unknown said…
I'm still in.
Unknown said…
Head down a*se up & keep pushing! This is a must do and you have lots of support.
Brent Vardy said…
Hey John, sorry that pledgebank didn't work out however looking forward to donating some cash once the charity is setup. Awesome project can't wait to see real progress
Unknown said…
I'm looking forward for:

Jeopardy,
the Charles Babbage's Analytical Engine Edition

;-)
Unknown said…
I'd love to support this project :) Really great!

Popular posts from this blog

How to write a successful blog post

First, a quick clarification of 'successful'. In this instance, I mean a blog post that receives a large number of page views. For my, little blog the most successful post ever got almost 57,000 page views. Not a lot by some other standards, but I was pretty happy about it. Looking at the top 10 blog posts (by page views) on my site, I've tried to distill some wisdom about what made them successful. Your blog posting mileage may vary. 1. Avoid using the passive voice The Microsoft Word grammar checker has probably been telling you this for years, but the passive voice excludes the people involved in your blog post. And that includes you, the author, and the reader. By using personal pronouns like I, you and we, you will include the reader in your blog post. When I first started this blog I avoid using "I" because I thought I was being narcissistic. But we all like to read about other people, people help anchor a story in reality. Without people your bl

Your last name contains invalid characters

My last name is "Graham-Cumming". But here's a typical form response when I enter it: Does the web site have any idea how rude it is to claim that my last name contains invalid characters? Clearly not. What they actually meant is: our web site will not accept that hyphen in your last name. But do they say that? No, of course not. They decide to shove in my face the claim that there's something wrong with my name. There's nothing wrong with my name, just as there's nothing wrong with someone whose first name is Jean-Marie, or someone whose last name is O'Reilly. What is wrong is that way this is being handled. If the system can't cope with non-letters and spaces it needs to say that. How about the following error message: Our system is unable to process last names that contain non-letters, please replace them with spaces. Don't blame me for having a last name that your system doesn't like, whose fault is that? Saying "Your

The Elevator Button Problem

User interface design is hard. It's hard because people perceive apparently simple things very differently. For example, take a look at this interface to an elevator: From flickr Now imagine the following situation. You are on the third floor of this building and you wish to go to the tenth. The elevator is on the fifth floor and there's an indicator that tells you where it is. Which button do you press? Most people probably say: "press up" since they want to go up. Not long ago I watched someone do the opposite and questioned them about their behavior. They said: "well the elevator is on the fifth floor and I am on the third, so I want it to come down to me". Much can be learnt about the design of user interfaces by considering this, apparently, simple interface. If you think about the elevator button problem you'll find that something so simple has hidden depths. How do people learn about elevator calling? What's the right amount of