Page MenuHomePhabricator

Add PackagesPackage
ClosedPublic

Authored by epriestley on Jul 21 2016, 5:58 PM.
Tags
None
Referenced Files
F14056604: D16315.id39235.diff
Sat, Nov 16, 9:15 PM
F14036575: D16315.id39235.diff
Sun, Nov 10, 10:57 AM
F14036573: D16315.id.diff
Sun, Nov 10, 10:57 AM
F14036572: D16315.id39286.diff
Sun, Nov 10, 10:57 AM
F14036510: D16315.diff
Sun, Nov 10, 10:30 AM
F14036079: D16315.id39235.diff
Sun, Nov 10, 8:29 AM
F14026118: D16315.diff
Thu, Nov 7, 11:44 PM
F14012002: D16315.id39235.diff
Fri, Nov 1, 6:51 AM
Subscribers

Details

Summary

Ref T8116. A package has:

  • a publisher (like "Phacility"), from the previous revision;
  • a name (like "Arcanist");
  • a package key (like "arcanist").

The package key is immutable, like the publisher key.

This gives a package a full key like "phacility/arcanist".

Policy stuff:

  • You must be able to view a publisher to view a package (currently, everyone can always see all publishers).
  • You must be able to edit a publisher to create a new package inside it.
  • Packages have separate view/edit permissions.

This still does nothing interesting.

Test Plan

Screen Shot 2016-07-21 at 10.53.05 AM.png (970×1 px, 130 KB)

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Add PackagesPackage.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: chad.

generic concern: this might be confusing w.r.t. to Owners packages. Maybe we should call these 'Extensions' (though this is confusing w.r.t. the extensions/ directory)?

Here's my incredibly clever plan around that, at least for now: T5055#132849

chad edited edge metadata.
This revision is now accepted and ready to land.Jul 24 2016, 3:30 AM
This revision was automatically updated to reflect the committed changes.