User:Sj/Log/bundles, interfaces, and executables: Difference between revisions
m (...) |
m (Walter's rectum 22/Log/bundles, interfaces, and executables moved to User:Sj/Log/bundles, interfaces, and executables over redirect: revert) |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
The first notion of bundle is an executable collection of code and supporting material, along with the objects that it can read or store. Bundles are shared or distributed as a whole; objects they create can be shared or reused individually. |
The first notion of bundle is an executable collection of code and supporting material, along with the objects that it can read or store. Bundles are shared or distributed as a whole; objects they create can be shared or reused individually. |
||
There is also a notion of a [[generic bundle]] -- a simple way to throw a few objects together and label them, for the purposes of sharing. |
There is also a notion of a [[generic bundle]] -- a simple way to throw a few objects together and label them, for the purposes of sharing. It may be helpful to have a bundle manager activity, which helps find what exists (rather than the Journal, finding what people have done). |
||
Security discussions around bundles have focused on the idea that they are all executable. Generic bundles will likely not fall under this regime. We should think about an intermediate level of security that supports some sort of [[content stamping|group stamping]] by community groups. This would let anyone who wants to use and test and review new activities can play with a reasonable but not completely stable/approved set of activities. |
|||
Latest revision as of 15:43, 20 December 2009
The first notion of bundle is an executable collection of code and supporting material, along with the objects that it can read or store. Bundles are shared or distributed as a whole; objects they create can be shared or reused individually.
There is also a notion of a generic bundle -- a simple way to throw a few objects together and label them, for the purposes of sharing. It may be helpful to have a bundle manager activity, which helps find what exists (rather than the Journal, finding what people have done).
Security discussions around bundles have focused on the idea that they are all executable. Generic bundles will likely not fall under this regime. We should think about an intermediate level of security that supports some sort of group stamping by community groups. This would let anyone who wants to use and test and review new activities can play with a reasonable but not completely stable/approved set of activities.