History of ProtectorPackage
Version 2 | Current version | |
---|---|---|
This page was linked from Release2, and should descruibe the features of the proposed Protector Package. Hopefully the developer of this package will share the plan for comments. (:mrgreen:) Added in line \lsces
''The basic plan for Protector was to provide a means of segregating content much as defined in this note. It works off the group selection, so all content is visible until it is assigned to a group. Once assigned to a group, only a member of that group can see it. The basic requirement was that all functions such as wiki, articles, fisheye and any other liberty content should be visible to anoymous users, but they only see a subset of content. Once registered, additional content can be seen, but with some groups of material still hidden. Only once a member is assigned to that group can that groups content be seen. An example 'sub-group' would be moderator, so that un-moderated content is hidden until it gets moved to another group. Approvel of articles would work the same way. This conflicts with the other approaches being taken to implement those facilities, but if the Protector code is implemented properly then any other package should be able to use it!''
| This page was linked from Release2, and should descruibe the features of the Protector Package. Hopefully the developer of this package will share the plan for comments. (:mrgreen:) Added in line \lsces - Protector is a service SEE ALSO ProtectorService for the documentation!
The basic plan for Protector was to provide a means of segregating content much as defined in this note. It works off the group selection, so all content is visible until it is assigned to a group. Once assigned to a group, only a member of that group can see it. The basic requirement was that all functions such as wiki, articles, fisheye and any other liberty content should be visible to anoymous users, but they only see a subset of content. Once registered, additional content can be seen, but with some groups of material still hidden. Only once a member is assigned to that group can that groups content be seen. An example 'sub-group' would be moderator, so that un-moderated content is hidden until it gets moved to another group. Approvel of articles would work the same way. This conflicts with the other approaches being taken to implement those facilities, but if the Protector code is implemented properly then any other package should be able to use it!
|