Firefox/Feature Brainstorming:Profiles: Difference between revisions
< Firefox
Jump to navigation
Jump to search
m (reference edit, going to be doing some reorganization/reformatting) |
m (simplifying format, reorganizing) |
||
| Line 1: | Line 1: | ||
== Profile creation/switching == | |||
* Improve profile/user management and switching | * Improve profile/user management and switching | ||
** Make the profile manager accessible through the menu | ** Make the profile manager accessible through the menu | ||
== Profile privacy == | |||
* Password-protected user profiles | * Password-protected user profiles | ||
* Encryption of all stored data and profiles | * Encryption of all stored data and profiles | ||
; References | |||
[https://bugzilla.mozilla.org/show_bug.cgi?id=16489 bug 16489] | * [https://bugzilla.mozilla.org/show_bug.cgi?id=16489 bug 16489] | ||
[https://bugzilla.mozilla.org/show_bug.cgi?id=19184 bug 19184] | * [https://bugzilla.mozilla.org/show_bug.cgi?id=19184 bug 19184] | ||
== Profile data == | |||
* Profile export/import | * Profile export/import | ||
* Remote profiles hosted on a server and available to multiple installations. | * Remote profiles hosted on a server and available to multiple installations. | ||
* Remote profiles able to save sessions | * Remote profiles able to save sessions | ||
* Remote profiles should ''perhaps'' be versionable | * Remote profiles should ''perhaps'' be versionable | ||
* Remote profiles should support a plug-able backend, LDAP, WebDav, FTP, etc.. | * Remote profiles should support a plug-able backend, LDAP, WebDav, FTP, etc.. | ||
| Line 35: | Line 23: | ||
* Preference for where profile data is saved including settings, bookmarks, add-ons, passwords, etc.'' | * Preference for where profile data is saved including settings, bookmarks, add-ons, passwords, etc.'' | ||
* Platform-independence of remote profiles, share the same profile between installations on different operating systems | * Platform-independence of remote profiles, share the same profile between installations on different operating systems | ||
; References | |||
RFC 2244 - Application Configuration Access Protocol | * RFC 2244 - Application Configuration Access Protocol | ||
[https://bugzilla.mozilla.org/show_bug.cgi?id=31732 bug 31732] | * [https://bugzilla.mozilla.org/show_bug.cgi?id=31732 bug 31732] | ||
[https://bugzilla.mozilla.org/show_bug.cgi?id=147344 bug 147344] | * [https://bugzilla.mozilla.org/show_bug.cgi?id=147344 bug 147344] | ||
== EULA display on first run of new profile == | |||
* Display EULA (required for distribution opportunities) | * Display EULA (required for distribution opportunities) | ||
** ''This is probably not required for distribution opportunities, and is indeed probably a bad idea (reduces usability, no benefit). This is only required for programs having license clauses stronger than copyright law (e.g. no reverse engineering), and not for GPL/MPL/NPL-style licenses.'' | ** ''This is probably not required for distribution opportunities, and is indeed probably a bad idea (reduces usability, no benefit). This is only required for programs having license clauses stronger than copyright law (e.g. no reverse engineering), and not for GPL/MPL/NPL-style licenses.'' | ||
** Firefox binaries are not under the GPL/MPL or NPL, they are under the (linked) EULA, which has clauses <b>unrelated</b> to copyright law (e.g. trademarks). | ** Firefox binaries are not under the GPL/MPL or NPL, they are under the (linked) EULA, which has clauses <b>unrelated</b> to copyright law (e.g. trademarks). | ||
*** Such things need no EULA. Trademarks, patents, and trade secrets are protected be default. No EULA is required to protect them. (What, you think GPL/MPL/NPL suddenly gives up your trademark rights??? Where is that?) It's like the lame statements that I can't export to North Korea: your EULA makes no difference, because I can't do that anyway. | *** Such things need no EULA. Trademarks, patents, and trade secrets are protected be default. No EULA is required to protect them. (What, you think GPL/MPL/NPL suddenly gives up your trademark rights??? Where is that?) It's like the lame statements that I can't export to North Korea: your EULA makes no difference, because I can't do that anyway. | ||
*** According to [http://www.mozilla.org/foundation/trademarks/faq.html] Firefox binaries _are_ under the MPL. In my | *** According to [http://www.mozilla.org/foundation/trademarks/faq.html] Firefox binaries _are_ under the MPL. In my opinion we gain nothing by showing an EULA, that only annoys users. | ||
; References | |||
[[User:CBeard:Fx2_EULA_Requirements|End-User License Agreement (EULA) Requirements for Firefox 2]] | * [[User:CBeard:Fx2_EULA_Requirements|End-User License Agreement (EULA) Requirements for Firefox 2]] | ||
== Enterprise support == | |||
* Be able to force a profile to be stored in some location like \\server\user_home\firefox (for windows) and /mnt/nfs/users/firefox (linux) | |||
* | * Existing profile storage is not useful for making defaults settings for whole groups of users - so it is impossible to switch large groups of users to Firefox with shared policies and settings | ||
* Make ability to make sets for multiple users at one editing of profile - changing their profiles | * Make ability to make sets for multiple users at one editing of profile - changing their profiles | ||
* Ability to make MAIN profile. | * Ability to make MAIN profile. | ||
** If firefox configured to use MAIN profile, then it gets policy sets from this profile (so, user can't make "not allowed" changes, until he switch off using of MAIN profile in browser (so, needs ability for administrators to block switch off MAIN profile)) Example: all default sets getting from MAIN profile and then firefox apply user settings, if this allowed by the MAIN profile for this group of sets) | |||
If firefox configured to use MAIN profile, then it gets policy sets from this profile (so, user can't make "not allowed" changes, until he switch off using of MAIN profile in browser (so, needs ability for administrators to block switch off MAIN profile) ) | |||
Example: all default sets getting from MAIN profile and then firefox apply user settings, if this allowed by the MAIN profile for this group of sets) | |||
Revision as of 17:56, 24 October 2006
Profile creation/switching
- Improve profile/user management and switching
- Make the profile manager accessible through the menu
Profile privacy
- Password-protected user profiles
- Encryption of all stored data and profiles
- References
Profile data
- Profile export/import
- Remote profiles hosted on a server and available to multiple installations.
- Remote profiles able to save sessions
- Remote profiles should perhaps be versionable
- Remote profiles should support a plug-able backend, LDAP, WebDav, FTP, etc..
- Full profile sync, including bookmarks, history, passwords, cookies, add-ons, preferences, etc.
- Provide a more advanced export so bookmarks and bookmark settings as well as Toolbar settings are saved.
- Automatic Sync/backup of profile data using same plug-able backends as remote profiles.
- Built-in AutoFill, which allows users to save their web passwords with Fiefox (like Avant Browser)
- Encrypted during sync/transmission
- Preference for where profile data is saved including settings, bookmarks, add-ons, passwords, etc.
- Platform-independence of remote profiles, share the same profile between installations on different operating systems
- References
- RFC 2244 - Application Configuration Access Protocol
- bug 31732
- bug 147344
EULA display on first run of new profile
- Display EULA (required for distribution opportunities)
- This is probably not required for distribution opportunities, and is indeed probably a bad idea (reduces usability, no benefit). This is only required for programs having license clauses stronger than copyright law (e.g. no reverse engineering), and not for GPL/MPL/NPL-style licenses.
- Firefox binaries are not under the GPL/MPL or NPL, they are under the (linked) EULA, which has clauses unrelated to copyright law (e.g. trademarks).
- Such things need no EULA. Trademarks, patents, and trade secrets are protected be default. No EULA is required to protect them. (What, you think GPL/MPL/NPL suddenly gives up your trademark rights??? Where is that?) It's like the lame statements that I can't export to North Korea: your EULA makes no difference, because I can't do that anyway.
- According to [1] Firefox binaries _are_ under the MPL. In my opinion we gain nothing by showing an EULA, that only annoys users.
- References
Enterprise support
- Be able to force a profile to be stored in some location like \\server\user_home\firefox (for windows) and /mnt/nfs/users/firefox (linux)
- Existing profile storage is not useful for making defaults settings for whole groups of users - so it is impossible to switch large groups of users to Firefox with shared policies and settings
- Make ability to make sets for multiple users at one editing of profile - changing their profiles
- Ability to make MAIN profile.
- If firefox configured to use MAIN profile, then it gets policy sets from this profile (so, user can't make "not allowed" changes, until he switch off using of MAIN profile in browser (so, needs ability for administrators to block switch off MAIN profile)) Example: all default sets getting from MAIN profile and then firefox apply user settings, if this allowed by the MAIN profile for this group of sets)