It has been about a year and a half since the most recent "official" release of AdvoKit - 0.9.9 - was tagged and announced. Frankly, I had largely given up hope of seeing any further development. The original development team had largely disbanded and were pursuing other interests, myself included.
Recently though, there has been a resurgence of interest in AdvoKit.

Thanks in large part to a flurry of development activity by David Donachie, working for the Scottish National Party to adapt and improve AdvoKit for their own purposes, I have had the chance to incorporate many bug fixes and enhancements into AdvoKit over the past several weeks.
These include, but are not limited to:

• Mysterious SQL bug that in the past could only be solved by assuming a job is now gone
• Adding 2nd and subsequent campaign leaders no longer causes SQL errors
• Editing a voter no longer corrupts or loses address data
• Self registered users email improvements
• Admins can add users without SQL errors
• Fixed MakeRandomContactListAction so that contacts are not duplicated in an operation when there are more than one operation
• Enabled filtering voters by questionnaire response and contact status
• Various fixes to contact list display
• Numerous fixes to task browsing, viewing and editing - they are now functional!
• Changed "breadcrumb" links so that if you aren't allowed to view an upline team, you don't get a link to it
• More graceful handling of handling adding new users who try to use an existing username
• Eliminated mysterious blank-page problem on browser displays
• Much improved browse activists display
• Removed extraneous controls from Jobs display
• Removed ability to create multiple campaigns
• Added voter browsing to the sidebar for any leader at the operation level or lower (subject to voter filters)
• Enabling "Group by household" on voter browsing now produces useful behaviors (e.g. click one member of household and automatically select them all)

With all these improvements, I think we should take advantage of the moment to tie up all the lose threads and announce version 1.0. Here is what is on my "To Do List":

• Review bugzilla and make list of bugs that we can try to fix for 1.0
• Version 1.0 requirements:
• Link to download page in screen-footer.tpl
• Documentation
  Help Screens (commit to sql tables in cvs)
• Review documentation in installer
• Web site doc review
• Branch code in cvs for 1.2
• Figure out how to provide anonymous (read only) access to cvs.
• Create download page on advokit.net and advokit.net/community:
• links to latest stable 1.0 release
• current 1.0 snapshot
• webcvs
• head snapshot (v1.2?)
• instructions for anonymous cvs access
• Fix demo site
• upgrade to current code
• set up clean db and help
• set up clean backup db and cron restore from backup (daily, weekly?)
• Should we announce "1.0 beta" and take a few weeks of testing?
• Others

Perhaps this should be called a "wish list", but at least it provides a kind of map to get to a 1.0 release.

I would really like to get some help to knock some of these off. Working on the documentation especially would be a huge value to the community.

Let me know if you can help! (pat at pdcarto dot com) Thanks.