You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@rave.apache.org by "Dennis van der Laan (Created) (JIRA)" <ji...@apache.org> on 2012/04/20 17:16:43 UTC
[jira] [Created] (RAVE-570) Option to choose if users can add
preview-status widgets
Option to choose if users can add preview-status widgets
--------------------------------------------------------
Key: RAVE-570
URL: https://issues.apache.org/jira/browse/RAVE-570
Project: Rave
Issue Type: Story
Components: rave-core, rave-web
Affects Versions: 0.10.1
Reporter: Dennis van der Laan
If Rave is used as a community open-social portal environment, users should be able to add their own gadgets/widgets and add these to their pages.
Users should be able to mark these widgets as public or private: can other users use these widgets also or not.
If public, administrators should be able to review such widgets and mark them as 'published', so other users can use these widgets also.
Alternatively, if Rave is used as a corporate portal environment, the corporation mihgt want to restrict unlimited registration of widgets. Users might still be able to provide new widgets to the store, but no user should be able to use these widgets, until an administrator has reviewed it and marked it 'published'.
The widget store should reflect these options: if a user is able to provide new widgets, the registration-page should explain if the user will be able to use the widget immediately, or an administrator will review the widget first. Also, if the first scenario applies, when registering a widget, the user should be able to mark the widget as public or private. A user must be able to distinguish between his/her own private widgets, public widgets under review, and widgets for common use.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (RAVE-570) Option to choose if users can add
preview-status widgets
Posted by "Dennis van der Laan (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RAVE-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis van der Laan updated RAVE-570:
-------------------------------------
Description:
If Rave is used as a community open-social portal environment, users should be able to add their own gadgets/widgets and add these to their pages.
Users should be able to mark these widgets as public or private: can other users use these widgets also or not.
If public, administrators should be able to review such widgets and mark them as 'published', so other users can use these widgets also.
Alternatively, if Rave is used as a corporate portal environment, the corporation might want to restrict unlimited registration of widgets. Users might still be able to provide new widgets to the store, but no user should be able to use these widgets, until an administrator has reviewed it and marked it 'published'.
The widget store should reflect these options: if a user is able to provide new widgets, the registration-page should explain if the user will be able to use the widget immediately, or an administrator will review the widget first. Also, if the first scenario applies, when registering a widget, the user should be able to mark the widget as public or private. A user must be able to distinguish between his/her own private widgets, public widgets under review, and widgets for common use.
was:
If Rave is used as a community open-social portal environment, users should be able to add their own gadgets/widgets and add these to their pages.
Users should be able to mark these widgets as public or private: can other users use these widgets also or not.
If public, administrators should be able to review such widgets and mark them as 'published', so other users can use these widgets also.
Alternatively, if Rave is used as a corporate portal environment, the corporation mihgt want to restrict unlimited registration of widgets. Users might still be able to provide new widgets to the store, but no user should be able to use these widgets, until an administrator has reviewed it and marked it 'published'.
The widget store should reflect these options: if a user is able to provide new widgets, the registration-page should explain if the user will be able to use the widget immediately, or an administrator will review the widget first. Also, if the first scenario applies, when registering a widget, the user should be able to mark the widget as public or private. A user must be able to distinguish between his/her own private widgets, public widgets under review, and widgets for common use.
> Option to choose if users can add preview-status widgets
> --------------------------------------------------------
>
> Key: RAVE-570
> URL: https://issues.apache.org/jira/browse/RAVE-570
> Project: Rave
> Issue Type: Story
> Components: rave-core, rave-web
> Affects Versions: 0.10.1
> Reporter: Dennis van der Laan
>
> If Rave is used as a community open-social portal environment, users should be able to add their own gadgets/widgets and add these to their pages.
> Users should be able to mark these widgets as public or private: can other users use these widgets also or not.
> If public, administrators should be able to review such widgets and mark them as 'published', so other users can use these widgets also.
> Alternatively, if Rave is used as a corporate portal environment, the corporation might want to restrict unlimited registration of widgets. Users might still be able to provide new widgets to the store, but no user should be able to use these widgets, until an administrator has reviewed it and marked it 'published'.
> The widget store should reflect these options: if a user is able to provide new widgets, the registration-page should explain if the user will be able to use the widget immediately, or an administrator will review the widget first. Also, if the first scenario applies, when registering a widget, the user should be able to mark the widget as public or private. A user must be able to distinguish between his/her own private widgets, public widgets under review, and widgets for common use.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira