(Add features list) |
(Update features details) |
||
| Line 22: | Line 22: | ||
==== Groups and people visibility ==== | ==== Groups and people visibility ==== | ||
No need to log in to | No need to log in anymore to review groups and people's profile. | ||
==== RESTful API | ==== RESTful API ==== | ||
Provide a dedicated ENDPOINT to retrive accounts' data. | |||
Access to this API requires a generated token that people can get from their | |||
profile's page. | |||
==== Profile | ==== Profile Avatar ==== | ||
People will be able to add an avatar to their profile | People will be able to add an avatar to their profile (from a 3rd party service) | ||
This avatar will be available to 3rd-party which can use it in their views | This avatar will be available to 3rd-party which can use it in their views or more. | ||
==== Profile Bio ==== | ==== Profile Bio ==== | ||
People | People would be able to write their bio and will be view-able from their | ||
profile's page. | profile's page. | ||
Also available from the API | |||
==== Group binding ==== | ==== Group 3rd-party binding ==== | ||
As we (Fedora project) has a specific way of using group (i.e providing VCS access and the like) | |||
group will provide a way to bind its ACLs to 3rd party in order to retrieve people or to give people | |||
some rights to this 3rd party if its members exist from this 3rd party. | |||
Current target for now is: | |||
* GitHub organization | * GitHub organization | ||
Admin or group's admin could bind a group to a github organization's team. | : Admin or group's admin could bind a group to a github organization's team. | ||
: Which, create github's team if not exist and add its members to it if its members exist on github. | |||
: If group is VCS related, create a github's repo if not exist already and give its members commit access. | |||
==== Group ownership ==== | ==== Group ownership ==== | ||
Group's owner has been renamed to "principal Administrator" as group's admin can now | |||
pass along their group's ownership to another admin of the same group. | |||
Account's administrator can do the same. | |||
==== Settings panel ==== | ==== Settings panel ==== | ||
| Line 53: | Line 67: | ||
manage account related elements | manage account related elements | ||
* people management | * people management | ||
** Remove an account | |||
** Block, disable or archive account | |||
* groups management | * groups management | ||
** Add, edit and remove groups | |||
** Block or archive groups | |||
* groups' types management | * groups' types management | ||
* license agreement management | * license agreement management | ||
** Add, edit and remove Licenses | |||
** Enable license at sign-up which flag the license signing as mandatory | |||
* private API access management | * private API access management | ||
** Generate private token for trusted applications | |||
==== Account activities ==== | ==== Account activities ==== | ||
| Line 66: | Line 87: | ||
* Github | * Github | ||
Allow people to connect their github account and share | : Allow people to connect their github account and share their public infos with Fedora services. | ||
* Twitter | |||
: Allow people to connect their twitter account and share their public infos with Fedora service. | |||
==== 2 factors authentication ==== | ==== 2 factors authentication ==== | ||
| Line 84: | Line 104: | ||
==== LDAP backend ==== | ==== LDAP backend ==== | ||
Change SQL backend to LDAP's for groups and people | Change SQL backend to LDAP's for groups and people management. | ||
== Ideas == | == Ideas == | ||
Revision as of 19:19, 17 March 2015
This is a draft of potential features for FAS v3.0. It is meant to spawn discussion and will most likely evolve in the future.
Mockups
Status
Goals
- Move web framwork from TurboGears 1 to Pyramid
- A real endpoint API
- Better membership workflows
- Improved database model
- Make it more Fedora agnostic
- Bring new features
Features
Groups and people visibility
No need to log in anymore to review groups and people's profile.
RESTful API
Provide a dedicated ENDPOINT to retrive accounts' data. Access to this API requires a generated token that people can get from their profile's page.
Profile Avatar
People will be able to add an avatar to their profile (from a 3rd party service) This avatar will be available to 3rd-party which can use it in their views or more.
Profile Bio
People would be able to write their bio and will be view-able from their profile's page. Also available from the API
Group 3rd-party binding
As we (Fedora project) has a specific way of using group (i.e providing VCS access and the like) group will provide a way to bind its ACLs to 3rd party in order to retrieve people or to give people some rights to this 3rd party if its members exist from this 3rd party.
Current target for now is:
- GitHub organization
- Admin or group's admin could bind a group to a github organization's team.
- Which, create github's team if not exist and add its members to it if its members exist on github.
- If group is VCS related, create a github's repo if not exist already and give its members commit access.
Group ownership
Group's owner has been renamed to "principal Administrator" as group's admin can now
pass along their group's ownership to another admin of the same group.
Account's administrator can do the same.
Settings panel
Account's admin will have a dashboard where they could manage account related elements
- people management
- Remove an account
- Block, disable or archive account
- groups management
- Add, edit and remove groups
- Block or archive groups
- groups' types management
- license agreement management
- Add, edit and remove Licenses
- Enable license at sign-up which flag the license signing as mandatory
- private API access management
- Generate private token for trusted applications
Account activities
A new page where people can review their account's activities with datetime, events and locations.
Connected applications
- Github
- Allow people to connect their github account and share their public infos with Fedora services.
- Allow people to connect their twitter account and share their public infos with Fedora service.
2 factors authentication
- Gauth token
Optional 2nd auth wihch once activated, will ask people after entered a valid login+password their Gauth token to let them in.
- Yubikey
This one will not be added as a 2nd auth but as a combo with the login and password (i.e login+password+otp) (as discussed last flock).
LDAP backend
Change SQL backend to LDAP's for groups and people management.