Define what should be displayed on the user's Activity tab [#1227158]

We are working on creating a Activity tab on each user/X. The purpose of this page is to display the activity of that user, to get a greater sense what someone is working on. In many ways this issue is the start of a larger plan to create activity streams for users, projects, topics and more.

This issue focuses on defining what should be displayed, not how it should be displayed.

Some examples of information we could display:

New comments
Revisions or creating new nodes (documentation, issues)
Git activity, like commits or new sandboxes

We can currently access all the data below. The question is: What, if anything, are we missing. (Note: We are limited to data from drupal.org and cannot access data from other *.drupal.org sites).

I suspect we'll also need to decide what should be enabled and how it should be configured for Drupal.org.

Comment	File	Size	Author
#5	GitHub-user_activity.png	90.93 KB	eliza411
	drupal-activity_stream-individual.png	126.29 KB	eliza411
	drupal-activity_stream-admin_project.png	144.05 KB	eliza411

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

Bojhan CreditAttribution: Bojhan commented 22 July 2011 at 22:13

Title:

Define data that should be displayed on the user's Activity tab

» Define what should be displayed on the user's Activity tab

Comment #1.0

Bojhan CreditAttribution: Bojhan commented 22 July 2011 at 22:13

Issue summary:

View changes

Updated issue summary.

Comment #1.1

Bojhan CreditAttribution: Bojhan commented 22 July 2011 at 22:29

Issue summary:

View changes

Updated issue summary.

Comment #2

eliza411 CreditAttribution: eliza411 commented 22 July 2011 at 22:33

Currently available data:

Project release

Token	Replacement value
[project_release_pid]	A release's project nid
[project_release_project_title]	A release's project title
[project_release_project_title-raw]	A release's project title raw
[project_release_project_shortname]	A release's project short name
[project_release_version]	A release's version string
[project_release_version_major]	A release's major version number
[project_release_version_minor]	A release's minor version number
[project_release_version_patch]	A release's patch version number
[project_release_version_extra]	A release's extra version identifier
[project_release_version_api_tid]	A release's Core compatibility term ID
[project_release_version_api_term]	A release's Core compatibility term name
[project_release]	Link to project release

Project issue

Token	Replacement value
[project_issue_pid]	The issue's project nid
[project_issue_project_title]	The issue's project title
[project_issue_project_title-raw]	The issue's project title raw
[project_issue_project_shortname]	The issue's project short name
[project_issue_category]	The issue's category (bug, feature)
[project_issue_component]	The issue's component
[project_issue_priority]	The issue's priority
[project_issue_version]	The issue's version (if any)
[project_issue_assigned]	Link to the user the issue is assigned to
[project_issue_status]	The issue's status
[project_issue]	Link to project issue
[project_issue_assigned_name]	The name of the user an issue is assigned to

Project

Token	Replacement value
[project_shortname]	A project's short name
[project_homepage]	Link to a project's home page
[project_changelog]	Link to a project's changelog
[project_demo]	Demonstration link for a project
[project_documentation]	Link to a project's documentation
[project_screenshots]	Link to a project's screenshots
[project_license]	Link to a project's license
[activity-node-link]	Link to the node
[activity-node-creator-link]	Link to the node creator

User

Token	Replacement value
[activity-user-link]	Link to the user. Used only when doing user based activity (i.e 'login' 'update' etc)

Node

Token	Replacement value
[activity-node-link]	Link to the node
[activity-node-creator-link]	Link to the node creator

Comment

Token	Replacement value
[activity-comment-author-link]	Link to the author of the comment
[comment-link]	Link to the comment

Comment #3

rfay

English

Palisade, CO, USA

CreditAttribution: rfay commented 23 July 2011 at 21:18

This will be a great step forward.

It's easy to do, easy to improve, and offers a lot of value.

Comment #4

yoroy CreditAttribution: yoroy commented 25 July 2011 at 13:55

Subscribble

Comment #5

eliza411 CreditAttribution: eliza411 commented 25 July 2011 at 16:15

File	Size
GitHub-user_activity.png	90.93 KB

We're missing user pictures. They're arguably less critical for the User activity stream since most actions have the same image, but on GitHub for example, the "follow" action displays the picture of the user being followed and commit actions display the three previous commits and the committer's picture.

I don't *think* this crosses the line from what is displayed to how ... I do think user pictures are an important "what" in activity streams.

Also worth noting, user pictures aren't currently enabled on d.o.

Related issues:
#528928: User Picture Token Support

Comment #6

sirkitree CreditAttribution: sirkitree commented 11 August 2011 at 13:20

So what do we have built so far, in terms of message templates? From (http://dev_activity-drupal.redesign.devdrupal.org/user/46549/activity) looks like:

Issues:
[user] added a new issue [issue-title] to project [project-name].
[user] submitted a new [issue-type] [issue-title].

Releases:
[user] updated release [project_shortname] [release-name] for project [project-name].

Projects:
[user] updated the project [project-name].
[user] made [user] a maintainer of [project-name].
[user] created the project [project-name].

Comments:
[user] commented on [issue-title].

Comment #7

dww

we/he/they

CreditAttribution: dww commented 11 August 2011 at 15:30

This is all looking really cool!

For these:

[user] commented on [issue-link] ([project-link])

I think we should just use [comment-link] instead of [issue-link]. The comment links are themselves issue links (assuming they use the title of the issue instead of the subject of the comment), they just have a fragment id going to the right comment anchor. If you're looking at the stream and want to follow the activity, you want to see the activity (the comment) not necessarily the original post. Furthermore, if you land on the comment and need to scroll back up to the original post, that's easy, whereas if you land on the post, it's harder to find the comment (impossible currently since there's nothing to say the comment title or anything).

I think I'd prefer this to further complicating the stream with something more verbose like:

[user] added comment [comment-title/link] to [issue-link] ([project-link])

Anyway, I'm not 100% sure what the existing tokens actually provide, how easy it is to add others, etc. I'm just registering my request that when comments hit the stream, you somehow get a link to the comments themselves. ;)

Thanks,
-Derek

Comment #8

lisarex CreditAttribution: lisarex commented 13 August 2011 at 23:26

Is the Node token able to include forum activity, e.g. creating forum posts and creating other node types e.g. Book or Organization?

+1 to user pictures.

Comment #8.0

lisarex CreditAttribution: lisarex commented 13 August 2011 at 23:26

Issue summary:

View changes

Updated issue summary.

Comment #9

mgifford

he/him

English

CreditAttribution: mgifford commented 12 January 2014 at 18:44

This issue has been basically silent for over 2 years.

There are lots of good ideas here which we should be able to implement that will help build our community.

Comment #10

drumm

he/him

NY, US

CreditAttribution: drumm at Drupal Association commented 17 April 2015 at 18:50

Version:	6.x-3.x-dev	» 7.x-3.x-dev
Category:	Task	» Feature request
Issue summary:	View changes
Issue tags:		+drupal.org profile improvements
Related issues:		+#2281763: Make Drupal.org user profiles more robust