Page MenuHomePhabricator

Give Phortune merchants explicit members
ClosedPublic

Authored by epriestley on Oct 11 2014, 6:26 PM.
Tags
None
Referenced Files
F15416596: D10681.id25675.diff
Thu, Mar 20, 12:21 PM
F15413796: D10681.id.diff
Wed, Mar 19, 9:26 PM
F15412969: D10681.id25649.diff
Wed, Mar 19, 4:04 PM
F15403524: D10681.diff
Tue, Mar 18, 3:43 AM
F15399009: D10681.id25675.diff
Mon, Mar 17, 2:25 AM
F15382393: D10681.id25675.diff
Fri, Mar 14, 12:08 PM
F15337113: D10681.diff
Sun, Mar 9, 4:08 AM
F15334112: D10681.diff
Sat, Mar 8, 6:49 AM
Subscribers

Details

Summary

Ref T2787. Make this a little more concrete with explicit membership instead of a general edit policy. In particular, we need to know who to email when orders happen, and can't reasonably do that with an edit policy.

I imagine this might eventually get more nuanced (e.g., users who can only approve orders vs users who can manage the merchant itself) but that's a long ways away.

Test Plan

Screen_Shot_2014-10-11_at_11.23.01_AM.png (1×1 px, 154 KB)

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Give Phortune merchants explicit members.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: btrahan.
btrahan edited edge metadata.

I could also imagine a project members being merchant members.

This revision is now accepted and ready to land.Oct 13 2014, 5:33 PM
This revision was automatically updated to reflect the committed changes.