avity
avity
avity  
avity avity
avity
avity
avity
avity
avity
avity
avity
avity
avity
avity
avity
 
 
 
Project: Value Added Fulfillment

Services: Web Design, Web Programming
IBM
 
  End Customer: IBM
Client: Value Added Fulfillment
Technologies: HTML, JavaScript, PHP, MySQL, PDF


In order to promote the Power PC platform, IBM sponsored a programming contest for porting and creating open source applications designed specifically for Linux running on the PPC architecture. Through the website front end, programmers register for the contest and submit code. The back end of the site has separate logins for the site administrator and judges. Administrator functions include: managing eligible programming ports, managing judges, sending individual and bulk emails to judges and contestants, FAQ content management, and selecting and notifying winners. Avity implemented site security for the judges using a combination of email, a verification code, and a uniquely generated URL.

  IBM
Avity
View project slideshow
The contest was broken into 3 types of entries. A Tier 1 entry consisted of an original Linux application written for the PPC architecture. Tier 2 and 3 entries were ports of existing applications. During the course of the contest, additional applications were added to the list through the admin interface. Once successfully completed, no further entries would be accepted for an application.
People registered for the contest in a three step process. After entering, reviewing, and submitting their information contestants received a confirmation email. Once registered, contestants could submit entries.
After a judge flagged an entry as successful, the site administrator would receive an email.
The site administrator could track the progress of the contest through the back end and select the tier 1 grand prize winner. The administrator also had the ability to disqualify an applicant or override a judge and select a winner for an individual port.
Avity implemented an email system that handled email content, bulk notifications, auto responses, and individual emails. Dynamic content was inserted into the email with special character strings. Here are some examples: {PARTICIPANT_EMAIL} Participant's Email Address {SUBMIT_PORT_APPLICATION_NAME} Selected Port's Application Name
The FAQ was maintainable through the back end. The site administrator could reduce workload by posting the answers to questions received through the contact form. The FAQ was segmented by categories, which were easily added or assigned to the questions in a single step.
Each application port has an associated judge. Judges received an email with a security code and activation URL where they could active the account and choose a password. Once registered judges would download the applications in FIFO order, review, and flag as successful or not. The first successful entry for that port was the winner. Judges could also be selected to score entries for original applications.