Expert Drupal 6 Programmer

We are looking for a Drupal programmer who can work with us for an initial 2-3 month project. The technical project manager will be working very closely with you, providing specifications, doing testing/QA, and working with you to provide agile iterations for client review and acceptance. You MUST be strong with Drupal 6 install/config and with custom module development. For communications, you must be able to exchange email and/or chat via Skype. This will happen during the business day in California (Pacific time). Your English does not need to be perfect, but it should be clear and you should be comfortable writing in English. ## Deliverables What we need to know from you is your HOURLY rate for work, assuming that we will be doing 80-160 hours per month for 3 months. The project may continue indefinitely. After this initial bid, we will pay you via bonuses, based on timesheets. You will need to bid on this project. So for the purposes of starting off, please assume that the scope of work for this first bid includes: 1. Install and configure the latest Drupal 6 in our STAGE environment 2. Download, install and configure most popular modules 3. Set up all Clean URLs features, global redirect module, etc. for SEO optimizations 4. Configure the system user roles for multiple bloggers ("Experts") and for editors ("Senior Editors"). These will be system roles. Public users will also have profiles, but they will not have any access to the Drupal back office tools. 5. Add 2 taxonomies: 1) Geo Locations (initially cities in the USA, eventually cities outside the USA), 2) Travel Type (these are ad hoc categories such as "Business Only", "Girls Weekend", etc.) 6. Experts will author but not publish blog posts. They will need WYSIWYG editing, image uploading and insertion into posts, spellcheck, image resizing. All blog posts MUST go through a two step workflow, where the author actively submits the post for review and ONLY a Senior Editor can publish the blog post. There should be a) email notifications when a content item is submitted for review, b) a workflow queue where Senior Editors can see content items pending review. 7. Create one custom content type called a TravelPerk. This content item will also have a 2-step workflow as described for blog posts. It will have the following fields: Title (text), Body (html), URL, Geography (taxonomy of cities), Activity Category (taxonomy of categories), Start Date (date/time), End Date (date/time), Partner ID (text), IsActive (boolean) 8. Implement a public user registration system. Public users will NOT author content in the system. They will only have a basic profile to hold their preferences and eventually some other custom data. The registration system must require CAPTCHA, require a valid email address, support password recovery via email, require strong passwords (>= 6 characters, not a dictionary word), require the person's home city/state/country, require the person's age. 9. Expand the user profile to include an optional profile picture. The system should resize large user profile pictures to 85x85 pixels if they are larger. 10. Create a homepage view that shows the last 4 blog posts and the last 4 TravelPerks. We will be using SVN source control and a DEV/STAGE/PROD environment. Once you are ready for changes to be reviewed, you will check the code into SVN, create a change script in PHP if necessary, create a database patch if necessary. Once all these items are checked-in, we will apply them to the STAGE environment and perform QA and acceptance testing.