Update:Archive/2.0/Developers
Jump to navigation
Jump to search
Update: Home Page » Development »
Plan
Schedule
Responsibilities
Requirements
Goals and Priorities
Roles
Services
Application Infrastructure
Development
Staging
Production
DB Infrastructure
Development
Staging
Production
Project Standards
What language should we use?
Sticking with PHP seems to make the most sense at this time. We have that skill set (both on the development and systems side) and the alternatives are not particularly attractive. We considered both Perl and Java but decided against both at this time. The existing UMO service is currently scaling quite well with over 3 million unique clients a day across 3 servers.
What tools/frameworks will we use?
This is an ongoing discussion that will hopefully yield the "best tools for the job".
What about coding standards?
We are going to stick with the standard Mozilla coding standards where they apply and then develop our own where they do not.