Add a 'latin_name' field to the user profile so we can better support
those developers with names in non-Latin scripts, and yet still show a
Latin name as necessary on the developer profile page. This field only
shows up if populated.
Also, use consistent sorting everywhere- rather than using username,
always use first_name and last_name fields.
Signed-off-by: Dan McGee <dan@archlinux.org>
For a Package object query, we almost always did .select_related('arch',
'repo). Refactor this into the manager as a 'normal()' method so we can
avoid sprinkling the same logic everywhere.
Signed-off-by: Dan McGee <dan@archlinux.org>
I was getting sick of seeing the *-i18n packages completely blow away
anything else useful out of the recent updates sidebar. Revamp the logic
here again to do something about it. As we did before, grab packages
from the database and attempt to group them, but this time do it by only
repo and pkgbase.
From there, if we have packages in the group with a pkgname matching
pkgbase, we will link just those. If not, we will create some stub
objects that link to our relatively new virtual package overview screen.
Signed-off-by: Dan McGee <dan@archlinux.org>
Instead of having the '15 most recent' bit hardcoded, specify it as the
default but allow value to be overridden by any caller. We don't make
use of this yet, but it is not hard to do.
Signed-off-by: Dan McGee <dan@archlinux.org>
Don't use dotted notation now that we have less-than implemented methods
on the respective objects (which also allows this code to work under
PyPy). Switch a lambda call to use attrgetter as well.
Signed-off-by: Dan McGee <dan@archlinux.org>
We had this set up as a unique ForeignKey before, which adds some
indirection due to the RelatedManager object being there. By making it a
OneToOneField, we can get the profile object directly, enforce uniqueness,
and also use it in select_related() calls to make our profiles page a bit
more efficient.
Signed-off-by: Dan McGee <dan@archlinux.org>
South actually makes this relatively painless if you get everything right,
so might as well start getting these out of the legacy main application to
eventually eliminate models being separate from their views.
Signed-off-by: Dan McGee <dan@archlinux.org>
We had a bunch of extra imports, non-conventional variable names, spacing
issues, etc. that were relatively low-hanging fruit to clean up. Fix them
and make the code a bit cleaner in the process.
Signed-off-by: Dan McGee <dan@archlinux.org>
Get this working by doing some class business with CSS in order to highlight
the correct tab. I had to add some stuff to a variety of pages but it should
be working correctly now. Addresses FS#19591.
Signed-off-by: Dan McGee <dan@archlinux.org>
Rather than our home-baked roles field, which is free text so we really
shouldn't be checking against anyway. It also prevents people from being
both a developer and a TU.
Signed-off-by: Dan McGee <dan@archlinux.org>
Instead of doing slicing and ugly table-based layout, move to a CSS-based
organization of the donor list. Shoot for 4 columns but should degrade
gracefully to fewer, and will look just fine with no CSS at all (one big
tall list).
Signed-off-by: Dan McGee <dan@archlinux.org>
Sometimes http was first, other times ftp was first. Add an order by clause
to ensure it is the same for all mirrors.
Signed-off-by: Dan McGee <dan@archlinux.org>
Instead of linking the package name, link the architecture. This will
prevent the lost links we had when we collapsed the list to show multiple
architectures at the same time.
Signed-off-by: Dan McGee <dan@archlinux.org>
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>
Especially when looking at packages, we always want the arch and repo.
Another big hunk of changes deals with the very inefficient signoffs code.
Signed-off-by: Dan McGee <dan@archlinux.org>
The addition of a models.py file in public app is needed for django to
recognize it as an application for testing.
Signed-off-by: Ismael Carnales <icarnales@gmail.com>
We should always highlight 'Home' when on the Django site. The sole
exception is the download page which has its own special place.
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
