mahara-contributors team mailing list archive

[Nathan Lewis <nathan.lewis@xxxxxxxxxxxxx>]

Public bug reported:

This is a bug to keep track of the Activity Stream block that we are
implementing.

The activity stream block which can be placed in any page and will display different content depending on the viewer and the type of the page:
 - User dashboard: Show activities that are of interest to the user. Items shown here are affected by the user's Notification settings. Only items that the user has access to will be displayed.
 - User page: Shows activities that the page owner has performed. The contents of this block are filtered by the sharing permissions of the items relative to the viewer. The owner will see all actions they have performed. Any other user will show the actions that the owner performed, but only for items that are shared with them.
 - Group and Institution pages: Show activities that relate to the group or institution. The contents are filtered to only show items that are shared with the viewer. It assumes that the user viewing the stream has access to the group or institution.

This is a complicated patch, so here are some notes to help explain
things:

A 'homestream' notification plugin has been implemented. It is basically
a placeholder, as the processing of activities happens within the
activity stream block.

Activity types have to be updated to be able to be included in the
activity stream. We've got plans to implement a large set of new
activity types and refactor more of the existing activity types. This
first version (we intend to) only include refactors of two existing
activity types - "New page access" and "Feedback". Others will be
implemented after the initial patch is merged.

The code for selecting items to show in the activity streams is complex
and has been broken down into several smaller pieces to allow for
testing and easier maintenance. We've implemented a set of php units
tests to make sure that the correct activities are showing in the
correct streams. This testing is important because it ensures that users
will only see activities that they are entitled to see, to maintain
privacy.

All of the above is subject to change. Check the following comments.

** Affects: mahara
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1316324

Title:
  Add activity stream block

Status in Mahara ePortfolio:
  New

Bug description:
  This is a bug to keep track of the Activity Stream block that we are
  implementing.

  The activity stream block which can be placed in any page and will display different content depending on the viewer and the type of the page:
   - User dashboard: Show activities that are of interest to the user. Items shown here are affected by the user's Notification settings. Only items that the user has access to will be displayed.
   - User page: Shows activities that the page owner has performed. The contents of this block are filtered by the sharing permissions of the items relative to the viewer. The owner will see all actions they have performed. Any other user will show the actions that the owner performed, but only for items that are shared with them.
   - Group and Institution pages: Show activities that relate to the group or institution. The contents are filtered to only show items that are shared with the viewer. It assumes that the user viewing the stream has access to the group or institution.

  This is a complicated patch, so here are some notes to help explain
  things:

  A 'homestream' notification plugin has been implemented. It is
  basically a placeholder, as the processing of activities happens
  within the activity stream block.

  Activity types have to be updated to be able to be included in the
  activity stream. We've got plans to implement a large set of new
  activity types and refactor more of the existing activity types. This
  first version (we intend to) only include refactors of two existing
  activity types - "New page access" and "Feedback". Others will be
  implemented after the initial patch is merged.

  The code for selecting items to show in the activity streams is
  complex and has been broken down into several smaller pieces to allow
  for testing and easier maintenance. We've implemented a set of php
  units tests to make sure that the correct activities are showing in
  the correct streams. This testing is important because it ensures that
  users will only see activities that they are entitled to see, to
  maintain privacy.

  All of the above is subject to change. Check the following comments.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1316324/+subscriptions