Closed
Bug 638263
Opened 14 years ago
Closed 14 years ago
[tracker] Activity streams for users
Categories
(support.mozilla.org :: Users and Groups, task, P1)
support.mozilla.org
Users and Groups
Tracking
(Not tracked)
VERIFIED
FIXED
2.7
People
(Reporter: jsocol, Unassigned)
References
Details
We need streams of activity a user might care about. We want these to be small, fast, and flexible. Think of the Github dashboard. These will show up on users' "Review" dashboards.
We'll need:
* A model for the activity (sketch below)
* A way of sending the activity to the correct users (offline)
* A way of viewing it (the dashboard)
The basic idea is to generate an "inbox" for each user of the activity they care about. We don't need to store historic data forever. We could consider limiting it to 1-3 months, or between 20-200 per user, or other methods.
Sketch of a model:
class Activity(ModelBase):
user = ForeignKey
created = DateTime
title = Char
url = URL(null)
description = Char(null)
object = GenericForeignKey(null) # for cascading deletes
Then each object for a user is basically put into this template:
<li>
<a href="{{ a.url }}">{{ a.title }}</a>
<p>{{ a.description }}</p>
<datetime>{{ a.created }}</datetime>
</li>
For example, if someone replied to a discussion forum thread, we might write to the activity log of everyone else who'd posted in that thread so far.
By doing it this way, we can do things like localize the title/description for everyone. There will probably be some overlap with notifications but let's wait until we know what the extent of that is before jumping on to anything, especially given the goal of liberating notifications.
| Reporter | ||
Updated•14 years ago
|
| Reporter | ||
Updated•14 years ago
|
Comment 1•14 years ago
|
||
See the etherpad, too: http://etherpad.mozilla.org:9000/sumo-users-and-groups
Comment 2•14 years ago
|
||
No open blockers, so win, afaict! Reopen if I'm missing something.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•