|
|
| Line 549: |
Line 549: |
|
| |
|
|
| |
|
| The solution should provide functions for the following typical, reoccurring tasks: | | The solution should provide functions for the following typical, reoccurring management tasks: |
|
| |
|
| Monitor: | | Monitor: |
| Line 588: |
Line 588: |
| the other demands. | | the other demands. |
| | | |
|
| |
|
| |
| news on security risks /
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
| This way, mozilla and the firefox project shoot themself multiple times into the left, and also the right foot:
| |
|
| |
|
| |
| A very large group of people in (key) positions who:
| |
|
| |
| - decide on, support and influence the direction a decision pro/contra the use of firefox and
| |
|
| |
| - act as natural multipliers and advocats:
| |
|
| |
| -- influencing corporate decison which affects an prominent, important, often used application
| |
|
| |
| -- influencing private choice of employes:
| |
| ---indirectly through the corporate position, plans and decision
| |
| ---direcly by their personal opinions and feelings toward mozilla and firefox
| |
| -- as well as the overall impression and opinion employees get on mozilla, firefox as well as related projects and possibly opensource in general.
| |
| --
| |
|
| |
| And this can have quite grave, longterm consequences:
| |
|
| |
| Eg: a typical it staff / admin gets the task to evaluate a corporate switch to firefox on a 50 user network and provide an initial estimate on risk, required resources, etc.
| |
| currently would currently easely make the following expirience:
| |
| - no primary official site/portal found by google
| |
| - no resources covering questions an initial evaluation might bring up
| |
| - no reviews, success-stories etc.
| |
| - information is outdated, does not state the firefox versions it is verified for.
| |
| - there appears to be no dedicated active community (the enterprise working group
| |
| - tools and usage are scattered, requiring different levels of skills
| |
| - no tool-chain: tools have no direct connection to similar tools or those providing functions required for the next step in the repackage-process (eg, tool A: create custom xpis, tool B: repackaging of firefox),
| |
| -
| |
|
| |
|
| | | |
| Line 637: |
Line 599: |
| | | |
|
| |
|
| existance and non-existance of 'official' administration tools | | existance and non-existance of 'official' administration tools |
| | |
| | |
| | |
| | |
|
| |
|
| === possible design of a toolkit providing life-cycle management for distributed firefox installations in corporate or similar networks=== | | === possible design of a toolkit providing life-cycle management for distributed firefox installations in corporate or similar networks=== |