Call Me Al

I started writing UMO 2.0 in November 2004. Yes, 2004. The problem is that I don't know a lot of PHP. I understand a lot of the basics, just not enough. I figured that the community would be willing to help me with that. And they were. They were very eager for me to hand out projects.

Then the PTBs decided that UMO must be more robust and able to survive a slashdotting. Scott Kveton was brought in to lead this endeavor since he has a background in projects like this. He and OSL performed a security audit, made some fixes and a few rewrites, and then set out to create a UMO 2.0 plan.

And then it stopped. I've seen snails move faster.

There were weekly conference calls. Except they weren't weekly. And even those stopped in April.

So why don't I start coding again? The Best Practices document is outdated and I'm not qualified to update it. Not only that, but the Development Plan has also gone stale.

Instead of patching the existing code little by little, what will it take to get things moving? Where is the driving force of the project owner? I realize that these are volunteer resources, and like me, other volunteers can get busy for weeks or months. There are plenty of eager people just waiting for something to do.

Where is the Mozilla Foundation in this? Wasn't it their priority to get things moving? Or are they happy with the status quo? The reason I don't just start coding things myself is that I neither have the experience, nor do I have the motivation. Why should I start coding if I feel like its going to just get rejected later?

Update 1: I have an "official" development environment.