[
https://issues.apache.org/jira/browse/RAVE-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177658#comment-13177658
]
Matt Franklin commented on RAVE-403:
------------------------------------
IMO this is absolutely a fit for the overall architecture and is a major goal
of the project. We currently have an open ticket to develop shared "spaces"
(https://issues.apache.org/jira/browse/RAVE-103). A common team page could be
one of the many ways we leverage these spaces.
As you noted, the real barrier at the moment to developing first class spaces
that include OpenSocial gadgets is that there is currently no notion of group
ownership in the spec. However, this is something that is being addressed via
spec, Shindig and Rave patches
(http://docs.opensocial.org/display/OSD/Space+Proposal,
http://markmail.org/message/3lfbnf4xhxfxkcc4)
Internally, we have put together a simple workaround that has a static list of
gadgets that are rendered in specific locations. This is limited as they are
not actual widget instances in the database and are thus unable to leverage
preferences or app data. Additionally, we have only done this for a single
shared page of gadgets, but it could feasibly be modified to work for a larger
set. Of course, this will be replaced with a true spaces based implementation
for common pages when it is available. We are going to be committing this work
back to the Rave sandbox in SVN, as it is really just a workaround and not
something we want to see as part of the core.
> Project Gadget Dashboard View for entire team
> ---------------------------------------------
>
> Key: RAVE-403
> URL: https://issues.apache.org/jira/browse/RAVE-403
> Project: Rave
> Issue Type: Story
> Components: rave-portal
> Affects Versions: 0.6-INCUBATING, 0.7-INCUBATING
> Reporter: William Hayes
>
> We can offer a Bounty of $4000 to add this feature to the portal in a
> sustainable way - e.g. submitted and accepted into the project codebase. We
> would execute the bounty via eLance. (If this is inappropriate to propose -
> please let me know.)
> Background:
> We want to be able to deploy a portal for an entire project team such that it
> will show the same set of Gadgets to everyone. Right now the portal is
> personalized which is great, but in some cases, we want to setup a dashboard
> of gadgets that everyone in the project will see. We plan to deploy this
> inside Sharepoint or other websites in our intranet.
> We can restrict access via the website or Sharepoint site (e.g. embedding it
> in an iFrame in Sharepoint) - though having group authenticated access to a
> shared Dashboard would be useful.
> I'm not sure what the best way to add this feature. As long as someone can
> set up a gadget portal with Gadgets already laid out and then 'lock' it for
> other users, that will take care of our use case. We can set up a separate
> user account for this purpose so there aren't any OAUTH issues with personal
> logins.
--
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
