<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ticket search results</title><link>https://forge-allura.apache.org/p/allura/tickets/</link><description>You searched for labels:"activitystreams"</description><language>en</language><lastBuildDate>Fri, 19 Oct 2018 18:52:59 -0000</lastBuildDate><item><title>Activitystream needs ming config option NEEDS INI</title><link>https://forge-allura.apache.org/p/allura/tickets/8015/</link><description>Allura uses the Activitystreams library and choses to use its Ming backend (specified in `Allura/setup.py`).  Ming's `auto_ensure_indexes` setting defaults to true, but we should have a way to specify that as false for Activitystream.

Ideally we'd be able to pass through any additional params, just like the regular ming configuration that Allura uses for its own allura &amp; project-data connections.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Mon, 30 Nov 2015 15:35:20 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8015/</guid></item><item><title>Large timeline performance issue in activity stream</title><link>https://forge-allura.apache.org/p/allura/tickets/8006/</link><description>When an activity happens on a project and the `create_timelines` task is run, that executes ActivityStream's `Aggregator.create_timeline`.  In a case where there are no new records for some reason, then it calls `get_timeline`.  This can be a problem because the pre-computed "timeline" there could potentially be thousands or millions of records.  This takes a while and can take up a ton of memory which doesn't get reclaimed after the task is done.

We should evaulate if that behavior is correct.  If it is needed, we should pass a `limit` parameter in.

Also perhaps see if we can figure out why these records aren't being garbage collected.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 12 May 2016 18:51:47 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8006/</guid></item><item><title>Activity page fixes</title><link>https://forge-allura.apache.org/p/allura/tickets/7978/</link><description>* need `@with_trailing_slash` for activity tool, otherwise things don't load right and you can't "follow"
* it's not clear what following does.  A few simple things to make the unified activity timeline page /u/&lt;your-own-username&gt;/activity easier to understand would help that.
    * We should add more links to that page  E.g. from every activity page, from your profile or settings
    * And adjust the title of that page so its clear</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Mon, 14 Dec 2015 16:10:51 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7978/</guid></item><item><title>Incorrect commit attributions in activitystreams</title><link>https://forge-allura.apache.org/p/allura/tickets/7248/</link><description>[forge:site-support:#6860]
[forge:site-support:#7009]

If a user commits using an unrecognized email address, it'll fall back to the commit author username, which can link it to the wrong username. Better to not have that fallback and just leave it unassociated with a specific account.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Tsai</dc:creator><pubDate>Mon, 21 Mar 2016 18:44:52 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7248/</guid></item><item><title>User profile 500s if activity has a commit ref</title><link>https://forge-allura.apache.org/p/allura/tickets/7229/</link><description>Would be nice if each section on the profile page could fail gracefully, in addition to fixing root error here.

~~~~
File '/var/local/allura/Allura/allura/ext/user_profile/templates/user_index.html', line 20 in top-level template code
  {% extends g.theme.master %}
File '/var/local/allura/Allura/allura/templates/jinja_master/master.html', line 102 in top-level template code
  {% block content_base %}
File '/var/local/allura/Allura/allura/ext/user_profile/templates/user_index.html', line 49 in block "content_base"
  {{ section.display() }}
File '/var/local/allura/Allura/allura/ext/user_profile/user_main.py', line 268 in display
  'auth': AuthenticationProvider.get(request),
File '/var/local/allura/ForgeActivity/forgeactivity/main.py', line 268 in prepare_context
  activity.obj.project = activity_obj.project if activity_obj else None
AttributeError: 'Commit' object has no attribute 'project'
~~~~</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:00 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7229/</guid></item><item><title>"Created ticket" activities should include the tracker name</title><link>https://forge-allura.apache.org/p/allura/tickets/7227/</link><description>Instead of just saying "User created ticket #4" or "Created ticket #4," the activity text should include which tracker the ticket was created on, e.g. "User created ticket #4 on Support Requests"</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Cory Johns</dc:creator><pubDate>Fri, 19 Oct 2018 18:52:59 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7227/</guid></item><item><title>Clean up profile activity stream</title><link>https://forge-allura.apache.org/p/allura/tickets/7205/</link><description>Split out from [#7097]:

Remove redundant data from user activity stream (icon &amp; username), and add project name.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tim Van Steenburgh</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:00 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7205/</guid></item><item><title>Make activity widgets show 5 items if possible</title><link>https://forge-allura.apache.org/p/allura/tickets/7164/</link><description>If you fetch 5 activities, some or all of them may be filtered out after perm checks. Better to fetch more than you need (like 100), and take the first 5 of those.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tim Van Steenburgh</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:00 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7164/</guid></item><item><title>Create read perms on ForgeActivity app - NEEDS MONGO CMD</title><link>https://forge-allura.apache.org/p/allura/tickets/7163/</link><description>"...menu problem is that ForgeActivityApp doesn't define any permissions or set them in install(), so app.is_visible_to(c.user) fails due to lack of read perm"

Since we have lots of activity apps installed with no acls, let's delete them all and let them be reinstalled as anchored tools.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tim Van Steenburgh</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:00 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7163/</guid></item><item><title>Turn on activitystreams by default, remove cookie config</title><link>https://forge-allura.apache.org/p/allura/tickets/7156/</link><description>Now that activity streams tool is pretty stable and "production-ready" we should turn it on in development.ini and remove the per-cookie controls that were useful to expose the Activity tool to limited users.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:00 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7156/</guid></item><item><title>error on activity rss feed for users</title><link>https://forge-allura.apache.org/p/allura/tickets/7085/</link><description>~~~~
File '/var/local/allura/ForgeActivity/forgeactivity/main.py', line 120 in feed
  'title': 'Activity for %s' % data['followee'].shortname,
AttributeError: 'User' object has no attribute 'shortname'
~~~~</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:00 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7085/</guid></item><item><title>Filter deleted, unmoderated, or spam artifacts from Activity Stream</title><link>https://forge-allura.apache.org/p/allura/tickets/7082/</link><description>Unmoderated or spam comments, and deleted tickets show up on the Activity Stream.  They should be filtered by adding a `has_activity_access()` method / test.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Cory Johns</dc:creator><pubDate>Thu, 20 Aug 2015 22:06:09 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7082/</guid></item><item><title>Standardize 'eye' or 'star' for following/watching</title><link>https://forge-allura.apache.org/p/allura/tickets/7081/</link><description>Sometimes we use an eye and sometimes we use a star for activity streams.  I think we should be consistent.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:10 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7081/</guid></item><item><title>Require POST for follow/unfollow actions</title><link>https://forge-allura.apache.org/p/allura/tickets/7026/</link><description>`def follow` in `forgeactivity/main.py` should require POST.  And templates and tests should be changed to send posts (and don't forget the csrf token).</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:10 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7026/</guid></item><item><title>Show activity preview on user profile</title><link>https://forge-allura.apache.org/p/allura/tickets/7002/</link><description>User profile pages should show a few of the most recent activities (currently plenty of room on the right).

We could look at moving the SF-internal summary page's activity.js to Allura since it does basically the same thing.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:10 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7002/</guid></item><item><title>Filter activites by type</title><link>https://forge-allura.apache.org/p/allura/tickets/6998/</link><description>It would be nice to filter activities by type.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 11 Oct 2018 08:50:36 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/6998/</guid></item><item><title>Metadata events</title><link>https://forge-allura.apache.org/p/allura/tickets/6997/</link><description>Create events for:

* new project
* add member to project
* add screenshots
* update project categories, description, etc (don't want to get too detailed, probably)
* user profile changes</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Tue, 31 Mar 2015 10:11:52 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/6997/</guid></item><item><title>Fix avatar/summary alignment on activity timeline in FF</title><link>https://forge-allura.apache.org/p/allura/tickets/6970/</link><description/><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tim Van Steenburgh</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:10 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/6970/</guid></item><item><title>Create commit activity even if user not found</title><link>https://forge-allura.apache.org/p/allura/tickets/6964/</link><description>Right now we only create a commit activity if we can look up an Allura user for the commit author's email address. Instead, we should create an activity regardless.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tim Van Steenburgh</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:00 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/6964/</guid></item><item><title>Disable activity creation during imports</title><link>https://forge-allura.apache.org/p/allura/tickets/6963/</link><description>Also, create an activity for the import itself, once it finishes.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tim Van Steenburgh</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:10 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/6963/</guid></item><item><title>Two activity events created for updated ticket</title><link>https://forge-allura.apache.org/p/allura/tickets/6947/</link><description>One activity is created for the ticket update, and one for the comment that is automatically created when a ticket is updated. Should consolidate this down to just one activity per ticket update.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tim Van Steenburgh</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:10 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/6947/</guid></item><item><title>Create activity events for commits</title><link>https://forge-allura.apache.org/p/allura/tickets/6941/</link><description/><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tim Van Steenburgh</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:10 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/6941/</guid></item><item><title>Show preview of activities on PSP</title><link>https://forge-allura.apache.org/p/allura/tickets/6831/</link><description>1. Expose a feed (json/atom/whatever) via the ForgeActivity tool.
2. Consume the feed via JS on the PSP. Possibly useful: http://jquery-plugins.net/FeedEk/FeedEk.html</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tim Van Steenburgh</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:10 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/6831/</guid></item><item><title>Change url routing for /p/&lt;myproject&gt;/</title><link>https://forge-allura.apache.org/p/allura/tickets/6830/</link><description>Currently this routes to ForgeActivity.index() (the project's activity timeline) if the tool is installed and activitystream is enabled.

Remove this logic (revert to previous behavior). Also make sure ForgeActivity tool is not visible in menu (for SF only).</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tim Van Steenburgh</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:10 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/6830/</guid></item><item><title>Make activitystream timeline look better</title><link>https://forge-allura.apache.org/p/allura/tickets/6829/</link><description>Do some styling of the timeline served by ForgeActivity.index()</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tim Van Steenburgh</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:10 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/6829/</guid></item></channel></rss>