Never rely on a one-person project unless you can support the code yourself if you find significant bugs. If that one person is busy or just plain unavailable and you can't investigate and possibly fix the problem yourself, you are out of luck.
Obviously there are a few exceptions to that, for instance if the project is very widely used then you will get good support from the wider community (though in most cases like that the official devloper pool has grown beyond one by this point too).
I'm not saying the above to put down single-person projects or their creators: there are some brilliant people out there working on them. But brilliant people are often busy and are not immune to illness, needing to work on other things to pay the bills, family matters, or just have other interests that sap their time, and sod's law says they will be otherwise occupied just when you need their attention most!
Now, clearly, supporting the code yourself will not always be an option or a good choice; it's just much more likely to be viable with a one-person project.
Many complaints about open source projects that go stagnant are due to people not doing this, and being stuck using something they can't enhance/fix because they don't have (and can't afford to buy) the expertise.
We'll then be sending out regular emails with new suggested projects for people to work on.
Thanks for the idea and best of luck in having it move forward.
Now someone gift suhosin code for php 5.4 https://github.com/stefanesser/suhosin/
I am starting to fear one-person projects no matter how great.