Learn more about these different git repos.
Other Git URLs
This page should be the first thing you see when you log in. It's different than your profile. There's information on your profile that doesn't necessarily have interest for you personally. See issue #84 for a discussion comparing the two.
<img alt="profile-vs-stream_stream-1.png" src="/fedora-hubs/issue/raw/4ca2a10867bb3ff5b4078e4a6c0f367aaf40e88c167740e77faafd28844098b9-profile-vs-stream_stream-1.png" />
Some discussion about this ticket happened at 13 Jul 2016 hubs-devel meeting.
Initial PR here: https://pagure.io/fedora-hubs/pull-request/231
This is almost entirely implemented at the moment, but we need changes in FMN to get the data that will populate the streams (basically: publish the generated notifications on fedmsg). @jcline is on it.
Metadata Update from @abompard: - Issue set to the milestone: Production
Metadata Update from @abompard: - Issue assigned to abompard (was: atelic)
OK, back to the (technical) drawing board on this one, because I misunderstood what the Streams page was supposed to show and how it would look.
Since that page must hold widgets, we must find a database schema that will allow this while keeping a difference between a users's public hub and that user's private stream page.
I have considered the following options:
Namespace the hub name (stream hubs will be called stream-<username>):
stream-<username>
Make a separate table for the widget-holder object:
hub_type
Rewrite the hubs table to use a numeric ID for the primary key, and have a unique index on the (name, hub_type) couple:
(name, hub_type)
/u/<user>
/t/<team>
/r/<region>
I think I'll go with option 3, it seems the best. I'll do the URL changes too, we can introduce redirects later if we really want to.
Commit 0d23e60 fixes this issue
Login to comment on this ticket.