On 11/05/2016 04:55 AM, Lukas Fleischer wrote:
> I actually wanted to implement this a while ago but deferred it because
> I had problems finding a good UI. The two straightforward options are:
> 
> 1. Adjust the maintainer filter such that it also looks for
>    co-maintainers... Which would essentially result in packages you
>    co-maintain being listed under "My Packages".
> 
> 2. Add a new co-maintainer filter. Then, in addition to "My Packages",
>    add a "Packages I Co-Maintain" link.
> 
> I do not like the first option because packages you co-maintain differ
> from "your" packages. Co-maintainers do not have the same privileges as
> maintainers.
> 
> I also do not really like the second option. Adding more and more
> options and links clutters the UI and makes things inconvenient. For
> example, we added a filter for exact package name searches in commit
> 1c55e6b (Add option to search for exact name matches only (fixes
> FS#23556)., 2011-04-06). I wish we had implemented it the way archweb
> does it [1] back then. It is much more intuitive and clear.
> 
> Transferring this idea to co-maintainer search, maybe the "My Packages"
> page should have two sections: A list with packages one maintains,
> followed by a second table of packages one co-maintains. It is not
> entirely clear how to implement this as part of the package search,
> especially when it comes to pagination. So, many topics to discuss
> before coming up with a patch...
> 
> [1] https://www.archlinux.org/packages/?q=linux
> 

That (split results view) sounds like a good way of doing it. A search
for maintainers could return co-maintainers as well, but separated. As
for pagination, just return co-maintainers at the end (the last page)...
I assume since co-maintained packages are "lesser", people will be less
interested in them.

There is no need to restrict the co-maintainers search to your own
packages only, so it has nothing to do with "My Packages" as opposed to
the maintainer search it is a shortcut for.

...

Methinks now is a good time to move the discussion to [aur-dev]...

-- 
Eli Schwartz

Reply via email to