Web   ·   Wiki   ·   Activities   ·   Blog   ·   Lists   ·   Chat   ·   Meeting   ·   Bugs   ·   Git   ·   Translate   ·   Archive   ·   People   ·   Donate
summaryrefslogtreecommitdiffstats
path: root/docs/permissions
diff options
context:
space:
mode:
Diffstat (limited to 'docs/permissions')
-rw-r--r--docs/permissions24
1 files changed, 24 insertions, 0 deletions
diff --git a/docs/permissions b/docs/permissions
new file mode 100644
index 0000000..ff04630
--- /dev/null
+++ b/docs/permissions
@@ -0,0 +1,24 @@
+== Problem: Activity Permissions == #2009
+
+ Rainbow needs to grok activity permissions.
+
+Situation:
+
+ We've got a preliminary example of a how required permissions might be
+ specified by a bundle.
+
+ Caveat: this attempt was designed while only thinking about code-carrying
+ bundles, so its reasoning may be invalid for data-only bundles and or
+ extended bundles.
+
+Plan:
+
+ Start locking down containers, then accrete permissions and their semantics
+ on a couple of sample activities.
+
+
+Followup:
+
+ F1. We need to think hard about how error handling is going to interact with
+ permissions. How on earth is a user going to find out that their activity
+ isn't working because of a permissions misconfiguration?