(New page: <!-- All fields on this form are required to be accepted by FESCo. We also request that you maintain the same order of sections so that all of the feature pages are uniform. --> <!-- Th...) |
No edit summary |
||
| (15 intermediate revisions by 2 users not shown) | |||
| Line 9: | Line 9: | ||
== Summary == | == Summary == | ||
<!-- A or sentence summarizing what this feature is and what it will do. This information is used for the overall feature summary page for each release. --> | <!-- A or sentence summarizing what this feature is and what it will do. This information is used for the overall feature summary page for each release. --> | ||
Provides applications with credentials for user's online accounts listed on online.gnome.org or stored in GConf. | |||
== Owner == | == Owner == | ||
| Line 16: | Line 17: | ||
== Current status == | == Current status == | ||
* Targeted release: [[Releases/ | * Targeted release: [[Releases/10| Fedora 10]] | ||
* Last updated: | * Last updated: 11/05/08 | ||
* Percentage of completion: | * Percentage of completion: 100% | ||
<!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. --> | <!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. --> | ||
| Line 24: | Line 25: | ||
== Detailed Description == | == Detailed Description == | ||
<!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. --> | <!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. --> | ||
Online Accounts is a new DBus service available at org.gnome.OnlineAccounts that desktop applications can use to create and retrieve user's online accounts (such as Google, Twitter, etc.). | |||
Online Accounts service | |||
* stores online account information in GConf and passwords in GNOME Keyring | |||
* gets the account information from online.gnome.org server if it is available, otherwise relies on GConf | |||
* provides a dialog for adding and removing online accounts, as well as supplying passwords for existing accounts | |||
* is currently used by Online Desktop's sidebar to get user's Google and Twitter accounts, but patches for other applications will be coming soon | |||
The list of supported account types is stored on online.gnome.org server and is easy to expand. | |||
== Benefit to Fedora == | == Benefit to Fedora == | ||
<!-- What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new feature, what capabilities does it bring? Why will Fedora become a better distribution or project because of this feature?--> | <!-- What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new feature, what capabilities does it bring? Why will Fedora become a better distribution or project because of this feature?--> | ||
* user only has to enter or update information for a particular account type once | |||
* desktop applications do not need to do own GConf and GNOME Keyring manipulations | |||
* desktop applications do not need to create a custom dialog | |||
* new applications can be recommended based on online accounts added by the user | |||
== Scope == | == Scope == | ||
<!-- What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | <!-- What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
'''Done:''' | |||
The Online Accounts DBus service is available at org.gnome.OnlineAccounts and can be used by the desktop applications to create and retrieve accounts with specific types. | |||
The Online Accounts service stores account information in GConf and passwords in GNOME Keyring. | |||
The Online Accounts service gets account information from the online.gnome.org server if it is available, otherwise just uses GConf. | |||
The Online Accounts service provides a stock dialog for adding and removing accounts, as well as supplying passwords for the accounts. The desktop applications can specify which account types should show up in the dialog. | |||
Supported account types are stored on the server and the list is easy to expand. Desktop applications can ensure that information about an account type they need is available by sending it to the Online Accounts service, so that it can be used if the server is not available or for testing before adding an account type on the server. | |||
Multiple accounts of the same type can be added on both the desktop and the server. Individual accounts can be disabled on the desktop, which means that they shouldn't be used by any application on a particular desktop. | |||
Desktop-data-model and online-desktop packages are available by default, and desktop-data-engine and web-login-driver processes are started automatically when a call is made to the Online Accounts service. | |||
Online Accounts service works well when the user is not signed in to online.gnome.org, and the stock dialog for managing accounts presents the user with options to enable storing accounts online and to sign in. | |||
The Online Accounts service is currently used by Bigboard to get user's Google and Twitter accounts. | |||
A patch was created for Twitux to use the Online Accounts DBus service to obtain user Twitter accounts. | |||
MyTime is using an earlier version of the Online Accounts service. | |||
== Test Plan == | == Test Plan == | ||
| Line 44: | Line 84: | ||
--> | --> | ||
Accounts entered by the user on online.gnome.org should be available to the desktop applications that request those accounts when the user signs in to online.gnome.org. | |||
The user should still be able to add, remove, and supply credentials for online accounts when they are not signed in to online.gnome.org | |||
== User Experience == | == User Experience == | ||
<!-- If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. --> | <!-- If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. --> | ||
The users will only notice the change if an application they use switches to using the Online Accounts DBus service. In which case, the application can use the stock dialog pictured for getting the online account credentials. The user may also be offered to log in to online.gnome.org and modify their online accounts information there. | |||
The dialog tab for providing account password, disabling, or removing an online account: | |||
[[Image:Online-Accounts.png]] | |||
The dialog tab for adding a new online account for one of the supported account types: | |||
[[Image:Online-Accounts-Add.png]] | |||
== Dependencies == | == Dependencies == | ||
<!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel feature)? --> | <!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel feature)? --> | ||
None. | |||
== Contingency Plan == | == Contingency Plan == | ||
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "None necessary, revert to previous release behaviour." Or it might not. If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --> | <!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "None necessary, revert to previous release behaviour." Or it might not. If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --> | ||
Online Accounts service not used by any of the applications in the regular GNOME session. | |||
== Documentation == | == Documentation == | ||
<!-- Is there upstream documentation on this feature, or notes you have written yourself? Link to that material here so other interested developers can get involved. --> | <!-- Is there upstream documentation on this feature, or notes you have written yourself? Link to that material here so other interested developers can get involved. --> | ||
http://marinaz.fedorapeople.org/OnlineAccountsReference/ | |||
http://online.gnome.org/accounts-learnmore | |||
http://mail.gnome.org/archives/online-desktop-list/2008-May/msg00043.html | http://mail.gnome.org/archives/online-desktop-list/2008-May/msg00043.html | ||
| Line 63: | Line 123: | ||
== Release Notes == | == Release Notes == | ||
<!-- The Fedora Release Notes inform end-users how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release. --> | <!-- The Fedora Release Notes inform end-users how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release. --> | ||
New feature, no upgrades necessary. | |||
== Comments and Discussion == | == Comments and Discussion == | ||
* See [[Talk:Features/ | * See [[Talk:Features/OnlineAccountsService]] <!-- This adds a link to the "discussion" tab associated with your page. This provides the ability to have ongoing comments or conversation without bogging down the main feature page --> | ||
---- | ---- | ||
[[Category: | [[Category:FeatureAcceptedF10]] | ||
<!-- When your feature page is completed and ready for review --> | <!-- When your feature page is completed and ready for review --> | ||
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler --> | <!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler --> | ||
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete--> | <!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete--> | ||
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process --> | <!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process --> | ||
Latest revision as of 07:09, 28 November 2008
Feature Name
Online Accounts Service
Summary
Provides applications with credentials for user's online accounts listed on online.gnome.org or stored in GConf.
Owner
- Name: Marina Zhurakhinskaya
Current status
- Targeted release: Fedora 10
- Last updated: 11/05/08
- Percentage of completion: 100%
Detailed Description
Online Accounts is a new DBus service available at org.gnome.OnlineAccounts that desktop applications can use to create and retrieve user's online accounts (such as Google, Twitter, etc.).
Online Accounts service
- stores online account information in GConf and passwords in GNOME Keyring
- gets the account information from online.gnome.org server if it is available, otherwise relies on GConf
- provides a dialog for adding and removing online accounts, as well as supplying passwords for existing accounts
- is currently used by Online Desktop's sidebar to get user's Google and Twitter accounts, but patches for other applications will be coming soon
The list of supported account types is stored on online.gnome.org server and is easy to expand.
Benefit to Fedora
- user only has to enter or update information for a particular account type once
- desktop applications do not need to do own GConf and GNOME Keyring manipulations
- desktop applications do not need to create a custom dialog
- new applications can be recommended based on online accounts added by the user
Scope
Done:
The Online Accounts DBus service is available at org.gnome.OnlineAccounts and can be used by the desktop applications to create and retrieve accounts with specific types.
The Online Accounts service stores account information in GConf and passwords in GNOME Keyring.
The Online Accounts service gets account information from the online.gnome.org server if it is available, otherwise just uses GConf.
The Online Accounts service provides a stock dialog for adding and removing accounts, as well as supplying passwords for the accounts. The desktop applications can specify which account types should show up in the dialog.
Supported account types are stored on the server and the list is easy to expand. Desktop applications can ensure that information about an account type they need is available by sending it to the Online Accounts service, so that it can be used if the server is not available or for testing before adding an account type on the server.
Multiple accounts of the same type can be added on both the desktop and the server. Individual accounts can be disabled on the desktop, which means that they shouldn't be used by any application on a particular desktop.
Desktop-data-model and online-desktop packages are available by default, and desktop-data-engine and web-login-driver processes are started automatically when a call is made to the Online Accounts service.
Online Accounts service works well when the user is not signed in to online.gnome.org, and the stock dialog for managing accounts presents the user with options to enable storing accounts online and to sign in.
The Online Accounts service is currently used by Bigboard to get user's Google and Twitter accounts.
A patch was created for Twitux to use the Online Accounts DBus service to obtain user Twitter accounts.
MyTime is using an earlier version of the Online Accounts service.
Test Plan
Accounts entered by the user on online.gnome.org should be available to the desktop applications that request those accounts when the user signs in to online.gnome.org.
The user should still be able to add, remove, and supply credentials for online accounts when they are not signed in to online.gnome.org
User Experience
The users will only notice the change if an application they use switches to using the Online Accounts DBus service. In which case, the application can use the stock dialog pictured for getting the online account credentials. The user may also be offered to log in to online.gnome.org and modify their online accounts information there.
The dialog tab for providing account password, disabling, or removing an online account:
The dialog tab for adding a new online account for one of the supported account types:
Dependencies
None.
Contingency Plan
Online Accounts service not used by any of the applications in the regular GNOME session.
Documentation
http://marinaz.fedorapeople.org/OnlineAccountsReference/
http://online.gnome.org/accounts-learnmore
http://mail.gnome.org/archives/online-desktop-list/2008-May/msg00043.html
http://live.gnome.org/OnlineDesktop/CreatingSidebarWidget
Release Notes
New feature, no upgrades necessary.
Comments and Discussion