Skip to content
This repository has been archived by the owner on Feb 8, 2018. It is now read-only.

implement team member opt-in #3397

Closed
chadwhitacre opened this issue May 11, 2015 · 5 comments
Closed

implement team member opt-in #3397

chadwhitacre opened this issue May 11, 2015 · 5 comments

Comments

@chadwhitacre
Copy link
Contributor

With our new terms (#3390) we'll need all team members to re-accept the new terms in order to receive their takes.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@rohitpaulk
Copy link
Contributor

I'm thinking of decoupling team memberships from takes/payroll and creating a separate table named team_memberships.

@chadwhitacre
Copy link
Contributor Author

Not a bad idea. Changaco suggested this at one point (too busy to dig up the reference atm).

@webmaven
Copy link
Contributor

@rohitpaulk:

I'm thinking of decoupling team memberships from takes/payroll and creating a separate table named team_memberships.

Is this intended as a temporary measure? If not, you've implicitly created a category of 'third class citizens' who are members but have no take (however small).

@mattbk
Copy link
Contributor

mattbk commented Jul 23, 2015

Is this still relevant after removing payroll and Gratipay 2.0?

@chadwhitacre chadwhitacre modified the milestones: Payroll, Pivot Jul 30, 2015
@chadwhitacre
Copy link
Contributor Author

Is this still relevant after removing payroll and Gratipay 2.0?

This is relevant to bringing back payroll. However, I'm closing this as a ticket now that we have #3994 (the idea is captured there). This should reappear as a PR when the time is right.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants