Firefox/Feature Brainstorming:Profiles

« Firefox/Feature Brainstorming

Specific features	References
Profile creation/switching Improve profile/user management and switching Make the profile manager accessible through the menu	n/a
Profile privacy Password-protected user profiles Encryption of all stored data and profiles	bug 16489 bug 19184
Profile data Profile export/import Remote profiles hosted on a server and available to multiple installations. Remote profiles able to save sessions too. 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	RFC 2244 - Application Configuration Access Protocol bug 31732 bug 147344
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 oppinion we gain nothing by showing an EULA, that only annoys users.	End-User License Agreement (EULA) Requirements for Firefox 2
Ability of corporatives integrations Make ability to _FORCE_ profile to be stored in some location like \\server\user_home\firefox (for windows) and /mnt/nfs/users/firefox (linux) (existing abilities for profiles storage are not useful for making corporatives defaults settings for whole groups of users - so it is impossible to switch massively users to Firefox with corporative policy and same setting for all) 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)
General tasks
n/a	n/a