Project Goal

To create a download manager that optimizes worldwide Mozilla bandwidth utilization based on Geological location.

Ancillary Project Goals

• Develop a central ip->geolocation management system.
• Standardize and document the process in hopes of expanding project scope to the global level.

Focal Points

• Spread load across mirrors
• Use geo-location to redirect users to closer mirrors
• Generate usage statistics, referrer, counts, etc on downloads
• Ability to grow/scale into new applications (deep space is the limit – sky is too narrow)

Immedeate Goals

What does Mozilla want?

• Redirect the majority of European traffic automatically to EU mirrors to free up North American bandwidth and reduce load

What can we do with what we have?

• Will we be able to meet the requirements given with the resources we have? - Yes
• If yes, develop a timeline. If not, what do we need to get this thing rolling? - see Bouncer 1 Timeline
• Hardware? - existing
• Software? - existing (PHP, MySQL, AOL 9.0 Optimized (tm) )
• Additional help / direction? (polvi, with geo stuff)

How are we going to do this?

• Once we have gathered our resources and outlined our expectations from Mozilla and our project team, we need to whiteboard the big picture.
  • Has it been done before? What can we take from previous projects (if any)?
  • Database considerations
  • Geo-location methodologies
  • Auth module
  • Application structure
  • Classes / Libraries?
• Define reasonable milestones.
  • Prioritize our hitlist.
  • What should we expect to see in v1.0?
  • What is non-vital and should be saved until later?

... see Bouncer:Bouncer 1 Plan

Start doing it.

... see [TODO]

Test it, release it, improve it.

• Establish dev, staging and production environments.
  • This will be on dev1. Working dirs in home/username/...
• Manage bug reports in a timely fashion... take care of that when we get there.