Looking for A vbulletin Coder

This thread from @aeroguy asking for a reputable vBulletin coder is exactly the sort of request that gets faster, higher-quality replies when the job post is specific. @Dani's suggestion to move this to the job/offers area is sensible; the missing piece is a clear scope and vetting checklist so responders can give accurate bids.

Essential details to include in a job posting:

• exact vBulletin version and current license status
• hosting environment (OS, PHP and MySQL versions, control panel)
• list of installed modifications/plugins and any custom templates
• precise feature list or bug list with screenshots or steps to reproduce
• access that will be provided (staging server, FTP, DB dump)
• expected deliverables (installable plugin, patch file, uninstall steps, documentation)
• timeline, acceptance tests, and preferred payment/milestone plan

How to vet and manage a vBulletin developer:

• request a portfolio of recent vBulletin-specific work or links to contributed vB mods
• prefer work implemented through vBulletin hooks/plugins rather than editing core files (easier upgrades)
• require code comments, an uninstall/rollback plan, and SQL backups for any schema changes
• insist on work being done on a staging server and a clear testing/acceptance procedure
• use milestone payments or escrow for larger jobs and get the scope in writing

Final cautions: avoid very low bids that propose direct core edits, insist on basic security hygiene (sanitized inputs, prepared statements where applicable), and make sure ownership/licensing of delivered code is explicit. Posting the full environment and a clear acceptance checklist will cut down on back-and-forth and attract coders who can actually finish the job.