I tell you what. In the interest of not flooding the market with stuff and ultimate community benefit. why don't I just discontinue development of peewee (it has been that way for a month already anyway) and help you guys out with PHPMock then. I am I right in thinking you've no source just for PHPMock? I couldn't see any in the svn browser.
Well, you can grab us on the PHPSpec-Devel mailing list -
http://www.phpspec.org redirects to our Google page.
I wouldn't actually ask you stop peewee development. There is quite a bit of room around for alternate (Unit/Other) Testing libraries. So the niche is fair game

. PHPMock is different from a testing/specing framework in that it focuses on just the one thing - mocking and self-validation. I'd certainly love to have someone take charge on it - at the moment I'm stuck on PHPSpec alone (we have our first two iterations set up for development), so catch up with me on the mailing list and we'll string some Mocking ideas around.
You're right in that we have no code for PHPMock yet, it was literally start PHPSpec, wonder if a Mocking library existed, finding it didn't, and off went PHPMock to Google Code. We haven't had time to do any planning for it yet so your timing would be impeccable

.
Hang on, I thought you both you and Travis are involved in the using more PHP 5 and re-writing the mock objects for SimpleTest? And now your going off and starting your own framework as well?
We're both SimpleTest users and developers/maintainers/infrequent bug solvers actually

. Travis is currently working towards the SimpleTest migration to subversion before the PHP5 fest starts. I think the reasoning for working on two or more frameworks is actually not as conflicting as you think.
SimpleTest, as far as I'm concerned, is the best TDD friendly UT framework existing for PHP (PHPUnit likes to think it is for some reason

). But we both also want a BDD framework. In fact we both also use the PHPT framework!

So we're jumping from tool to tool depending on any number of reasons. Personal preference, whether testing or TDD'ing, form of testing (Selenium/WebTests/Unit/Integration), current project standards (ZF requires PHPUnit - bleh!). PHPSpec is currently TDD'd using phpt even.
Anyway, after nattering on for too many words (again) - get onto the PHPSpec mailing list

. Keep peewee going as you wish - I would never suggest stopping development on something new and fresh.