Skip to content
This repository was archived by the owner on Aug 6, 2021. It is now read-only.

Conversation

@pellaeon
Copy link
Member

This is a work in progress, PR is used to track todos.

Feedbacks welcome

ps. social user = staff, login via oauth

  • social user permission (need review submission permission)
    • group fixtures: submitter, staff, agenda-staff
    • add user to group -> which pipeline stage?
  • social user source group - should it be preserved? -> NO
  • submitter form should use fancy edit
  • check that access_token is revoked when logging out

Pipeline stage get_user_detail:

  • photo
  • get & set groups -> all users logged in via oauth goes to staff group

FIxtures:

  • staff: view & rate submission
  • agenda-staff: staff perm + edit submission
  • agenda-staff(?): edit timeslot, activity

pipeline step will fail, due to:
1. first time `social_user` step has no associated social user
2. first time running `associate_user` to create and associate social
user will do nothing
3. second time logging in it can't find user.social_user
@pellaeon pellaeon self-assigned this Nov 29, 2015
@pcchou pcchou force-pushed the cfp-dev branch 4 times, most recently from 125dd61 to d65865d Compare January 3, 2016 03:01
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants