Changes: general, requirements

• "Change" can reflect both user-level requirements, or system-level design
• Requirements and design inherit from original codebases: Netscape 5 and post-rewrite NGLayout
• Requirements and design are largely decided on a need-to-change basis
• "Open Requirements": proxied by parties that need them, both commercial participants and user requests
• Requirements process may result in need to implement change:
  - "feel free to submit patches"
• Problem area: User Interface, where design by committee isn't very effective; others?