Re: Feedback on Package overview page - Distro tracker

[Chirath R <chirath.02@gmail.com>]

Hi Raphael,

Thank you for the detailed feedback.

 

I find the table layout more useful.

Yes, table layout works better :)

 

As a team contributor, I want to check what packages need to be worked on.
In this situation you want all relevant informations of the work to be
done:
- the action items should be easily accessible at least in the expanded
  view, the number of action items by severity would thus be interesting

Can I know what an action item here represents. Is it something like a `Newer upstream version`?

 

- the bugs data
- the lintian data
- the availability of a new upstream release
- the status wrt what's in the VCS

Status of VCS, as in commits ahead of release version? 

 

- the grouping by "status/action needed" makes it easy to find a package
  with a specific issue to fix and offers a sort of "process pipeline"
  where the package progresses from group to group until's ready for
  upload

It would be nice to highlight packages that are added to a grouping recently(maybe after last visit). What do you think?

 

As an outsider, I want to check what packages are maintained by the team,
the versions availables and what all those packages are about and why they
are there.
- the grouping should be gone, or should be by team-specific categories
  which are meaningful for the end user
- all the version data is interesting
- we want the description too
- etc

I can use tooltips and bootstrap pop overs to display some of this data.

 

It's not clear that both use cases can be met with a single version of the
page.

Depending on whether the logged in user is a part of the team we can show two different views and add a toggle button just in case if the user wants to see the other information as well.