[SQLObject] SQLObject needs your help!

Hello, everyone! In his yesterday's post
http://www.ianbicking.org/blog/2014/02/saying-goodbye-to-python.html
Ian Bicking mentioned me as the person who saved him from the burden of
maintaining SQLObject. Thank you, Ian! It was an interesting experience
(and an urgent business need at that time).
   Unfortunately now is the worst time to praise me for working on
SQLObject. As everyone can see I wasn't very active the last year(s) and
this year the work stopped completely. I must apologize and explain
myself.
   I failed to build an active community. I am sorry. My communication
skills are perhaps not so good. And I certainly lack community-building
skills.
   Currently I am involved in three big projects, only one of them uses
SQLObject. I am tired and seldom have power to do anything besides my
work. Even worse, said project doesn't generate enough revenue and my
bosses decided to cut it in a month or two. After that I will have even
less incentive to work on SQLObject. I am very very sorry.
   It would be best for SQLObject and the community if someone takes
over the project and revives it. If you'd like, please step up.
   Or, if nobody wants to take the lead, I can continue working as the
integrator. Please send your patches (SourceForge tracker, mail list,
private mail directly to me), I'll test them, apply them and will
release new versions. I can help converting the repository to Mercurial
or git (I prefer git) if there are developers who are interested in
working with a distributed VCS.
   But without your work, dear developers, SQLObject is doomed.

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.