AllHands/2Q2006/Corporate Deployment

What do corporate deployers need/want?

• MSI installers
  • Includes (implies?) IT control of upgrade
• Group Policy defaults and lockdown
• Long-term support/maintenance (?)
• Early testing of new releases
• Communication

See raccettura's blogpost.

What can we actually provide? Will it be sufficient? What are the costs?

• Engineering
  • MSI installer building
  • Group Policy support
• Build/release
  • MSI release engineering
• QA
  • Testing of MSI releases
  • Testing of GP support
  • Beta/RC communication to IT deployers for early testing

Decisions and Action Items

• Mozilla does not have the personnel resources to do market studies of the corporate deployment space (general agreement)
• Mozilla should document existing resources such as the Mission Control Desktop which have already been used for corporate deployment (mscott, bienvenu)
• Mozilla Developer Center should have a corporate deployment section (talk to deb)
• Incremental development of features that are important to corporate deployment must develop organically; especially take contributions from the community
• Implement discussion/announce group for communication with/between corporate deployers (bsmedberg to talk to gerv/justdave)
• An official Mozilla MSI may happen for FF3 but is not a priority (robstrong)