|resources:||Home Mailing List Documentation Download Source Code Project Plan SOC Specific|
The aim of the MultExI project is to create a method for installing
Mozilla/Firefox extensions across multiple machines.
MultExI is one of ten MozDev.org projects taking part on Google's Summer of Code program.
|09.16.2005||Implementation of Feature List 4||-||-|
|08.20.2005||Complete development with a buffer for bugs and missing features.||X||-|
|08.15.2005||Test system on multiple clients.||X||-|
|08.14.2005||Implementation of feature list 3.||X||See feature list 3|
|08.11.2005||Finish first test phase.||X||-|
|08.10/11.2005||Implementation of feature list 2.||X||See feature list 2|
|08.05.2005||First code commit to CVS. / Status letter||X||See feature list 1|
|08.02.2005||Start of development.||X||-|
Feature ListsThe following list shows the features that will be implemented in all steps defined in Milestones .
MSC : MultExI Client Component
MCC : MultExI Server Component
Feature list 4General:
- Reorganization of organization (e.g. this includes improvement administration of these features lists)
- Extend user documentation
- Compose a developer docoumentation
- Error message if server can't be contacted.
- Make restart of Firefox after extension install optional (depending on server configuration)
- Possibility to update configuration defined on server
- Implement White/Blacklists
- Define white and blacklists for extensions
- Automatically update out-dated extensions
Feature list 3MCC:
- Create some nice logos and so on.
- Implement a method to exit (restart) the whole firefox process after download/update (Depending of mcc_config.xml)
- List clients which are probably out of date
- Optional: Implement some install/configuration code
Feature list 2MCC:
- Establish a method to install extensions/updates without the ackknowledgement of the user (don't know if thats possible that easy)
- Integrate more interaction with the user through dialogs
- Integrate user based (BASIC) authentication
- Administrate extensions to install through easy to handle web interface
Feature list 1MCC:
- Read mcc_config.xml (MulteXi Client Component _ Configuration), parse it and store properties in Firefox preferences
- Download edf.xml (extensions definition file - file that defines extensions that have to be installed) and parse it.
- For testing, half-automatic installation and updating of extensions defined in edf.xml by MultExI extension through common update/install user dialogs.
- Autmatic configuration of mcc_config.xml
- Pack MultExI distribution and publish it (with modified mcc_config.xml) under multexi.xpi in local web deployment