FAS3: * Problem split account management from the workflow * Split Fedora-only stuff out * Back with LDAP? Manage user accounts that are real? API to manage Users and Groups CLA is just a group * metadata that may traditionally be separate from the account * Make passwords and security things as small as possible * queue of users should be separate from those that are approved * FAS as API rather than a website * Requirement: passwords only get entered into FAS-Core (single page, like openid, kerberos) LDAP + sponsorship + authentication for apps (openid or similar) LDAP has its own permissions already. * active/inactive users two different tables * User interface -- - Where does Fedora stuff live? - FPCA signing - Dependencies among groups - Sponsorship - Queue - Certs - Yubikey - Invite-only - rpmfusion Uses non-invite-only as well - asterisk - ?Can we get rid of special groups? - Want to have people get a single page with all of the information that they can add module that a user can request that they want to get access to certain groups. This request gets forwarded to the sponsors. The request should have information on why you're applying. Notification -- email, file a trac ticket, queue. Users currently have app-to-app communication, system-to-system communication, as well as user communication. Qpid? FAS should be able to rename account, remove account, and the same with groups * We do not want: group of group dependencies. * Do not need to have three levels (user, sponsor, admin), User + admin is fine. simo -- what could we do with freeipa freeipa , kerb -- widely used. nice api. but pulls in a lot of stuff. Oauth/samba4/kerb5/web auth -- lighter weight, larger community * Use current launchpad and review of best practices for dealing with binary data in Ruby with Memcached and RabbitMQ review of best practices for dealing with binary data in Ruby with Memcached and RabbitMQ stance * Use drupal * mediawiki * DJango * TurboGears2 * Pyramid * Use our own launchpad # ACTION work on the road map for fas2 from what we've talked about for fas3. ie: which small features will we implement for fas2? * Toshio: FPCA signing * Xavier: Start work on the roadmap and diagram. Split Fedora-only stuff out. Notifications Problem split account management from the workflow. Make CLA as an optional option in fas.cfg. Admin page (build a POC for the team)? * Ricky: Prescott Ogden