It isn't the most elegant operation in the world, but attempt to only show
one line per package, grouping by architecture if multiple were updated in
the same go. This makes the recent packages view a bit more useful as a
heads up view. Implements FS#17304.
Signed-off-by: Dan McGee <dan@archlinux.org>
Make the feed framework a lot more flexible and give the possibility to have
a feed for each architecture. You can drill down even more than also get a
feed for a particular repo; some might find this helpful for something like
tracking [testing]. Implements FS#12939.
I also bumped up the number of items available in each of these feeds; since
it is full of a bunch of small items it might be more helpful to have more
available and it should also prevent fewer ones from being missed.
The UI isn't exactly spectacular, but I figured some sort of page is better
than none listing all the various feeds you can pull from.
Signed-off-by: Dan McGee <dan@archlinux.org>
Quite a few changes here. Unify the developer view pages into one actual
django view and template, and use different dispatches from urls.py to set
up the three different queries for who to display and what message and group
name to show.
Signed-off-by: Dan McGee <dan@archlinux.org>
* Use {% with %} to make getting things out of the profile easier
* Remove HTML exemption as it was causing unescaped entities to get through
to the page
* Link URLs instead of just printing them to the page
Signed-off-by: Dan McGee <dan@archlinux.org>
Guaranteed unique, and also a whole lot less likely to break validation
given we have several users with special characters (and even spaces) in
their first names.
Signed-off-by: Dan McGee <dan@archlinux.org>
RequestContexts are needed to check if the user is logged in
NOTE: Generic views as direct_to_template and object_list always return
a request context, so is good to use them :)
Later will add a render_template shortcut that adds the RequestContext
automatically
