Federated account info
Once an app gets account detail entered, it should check if other apps can use them too, and store them accordingly.
On the techs side, it probably should look like a library call passing the details and the library should handle everything else.
Apps could be polling the library to get the details for a service they need, passing the service name and receiving the details.
We also will need a Switchboard plug to control this.
User details can be stored via that library as well (btw they're stored somehow so apps can access them in GNOME2)
We have to look into the GNOME3 way of doing this (if there's any at all)
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Superseded
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- Sergey "Shnatsel" Davidoff
Related branches
Related bugs
Sprints
Whiteboard
I'm not sure about a wizard on first boot. Perhaps a wizard the first time an app that can access the settings tries to access empty settings? ~cassidyjames
I'd prefer to abstract this from the user completely; silently detect if there's a universal account present and
detect e.g. google accounts and store them accordingly ~shnatsel
I think the installer would be a good time to present this as a "here's stuff you can set up while you wait" and then also do shnatsel's more passive info storing. I'd like to expose it to users in the form of a plug so that they can go add and remove accounts if they please, but I think a wizard popping up would be kind of annoying ~DanRabbit
We can ask for account info during installation, ubiquity is very modular and customizable.
~shnatsel
